It all started when I decided my JDM B16 swapped CRX wasn't fast enough and needed some tuning. I cracked the OBD0 programming and started an editor to make changes to the program. Experimenting with ignition timing and fuel I picked up the basics of tuning and in no time at all it clicked.

I brought OBD1 into the mix soon after with the purchase of a 94 Civic DX Coupe for testing and later a 94 DX Hatchback with a GSR swap and a 94 Integra GSR. OBD1 Honda code is by far my favorite so far, though they did do some odd things. I became fluent in the language and started writing custom code to do whatever I wanted, within the capabilities of the stock ECU. I had no idea then that NepTune would raise the bar for OBD1 tuning capabilities and force other software developers to step up their game.

I tuned my first forced induction vehicle, a fully built 2.3L turbo in a show truck, quite some time ago. I taught myself to tune by trial and error. Facts can only take you so far, it's experience that really gives you a clear understanding of it all. Since then I've done full tuning on many NA and forced induction cars, mostly Hondas. That experience is what has helped me create some great feature sets in NepTune. Created for tuners by a tuner himself.

Geared towards automotive engineering, I plan on creating many great tools to use in this industry.

What's next for HRTuning?


The NepTune RTP system.



The NepTune TunerView.



What does the future hold for HRTuning? I'd like to expand into other vehicle types. I'm currently looking into BMW, Nissan/Infinity, Mitsubishi, and Subaru applications. Bringing the powerful features of NepTune to those platforms would be beneficial to everyone. Stay tuned for updates and possible announcements.

Please visit the web site for more information. http://hrtuning.com

Message Me
Add Me
Join The Myspace Group
Pictures
Blogs
Friends