If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
proceed to the Forums area and select the forum that you want to visit.
Yeah I'm not worried... HPTuners and DHP are very viable solutions, and HPtuners seems to have a good chunk of the crowd covered, even if they left out 96.
Yeah,looks to be 1500$ I remember it being 2500 with the package including the roadrunner (by itself $600 plus the cables you need..)
You have to own the roadrunner setup to buy though.(not sure of cost)
And the list of vehicles on there you can tune UNLIMITED,with no licensing.
Do some quick addition and you'll see why it's worth it after putting your time towards learning how to tune.
You can quickly pay for it if you know what your doing,heck you can pay for it easily just doing reprograms for tire/rim shops and I make alot of money from different mech shops and muffler shops for quick changes.
It's one time purchase,no more spending $100 just to flash a vin after you spent all that cash on the setup.
Here's a list of what's available right now,though VDF editors are available and some people are working on more definitions now that it's been okay'ed by John.
What people don't realize is that package is geared toward a shop that provides dyno tuning... NOT the average user. They have other packages that allow you to tune 1-3 vehicles and such, for a very comparable price of 499 or so.
Bottom line I paid 499 for my DHP unit... I'm able to tune ANYTHING that DHP has a supported file for... so in retrospect I got one HELL of a deal.
Now if someone could come up with a programming/reading software that would allow you to do files that were not supported in DHP's software, yet use the same hardware, the possibilities would be endless.
I can read any file, and save a bin, but I can't edit them if the OSID's are not recognized by any software, and then within DHP's programming software I can't program an ECM with an unrecognized OSID. That's the biggest limitation.
My wifes car had a calibration/OSID that was unrecognized by my VDF file,I just added it to the cal file in the VDF dat file and it was all groovy.
Actually I emailed John and he got a patch right out to me but it was corrupted so I did it manually once I figured it out.
We can build/alter our own definition files if we want
(Duramax/6.5d files were just released,$100! tune all the vins you want-same software Wester's uses [he built the VDF file] )
I'll need to check out this DHP,sounds pretty cool also.
Comment