Hi, when we will be able to write in dodge
Printable View
Hi, when we will be able to write in dodge
Reading fails with a checksum error on my 2006 SRT8 Magnum. Where and how (are there log files anywhere?) do I report bugs?
Thanks.
If you get a checksum error, that means that it actually read the file. The Checksum error either means A) The file is corrupt, or perhaps a modified tune that does not have the correct checksum, or B) we do not have a definition done for this OS yet. This is probably the reason you are getting the error. Send the .HPT file to support.
So how far are we from public release?
Thanks
VCM Suite 2.26 is many months out still.
Unfortunately we will be unable to merge Dodge support into the stable 2.24, so it will have to remain in "beta" for now until .26 is ready.
At this point though, the only known bugs/issues with Dodge are some minor cosmetic things in VCM Editor that I hope to have resolved soon. "soon". :p
Really good good good news for me!
Looking to buy an SRT CHerokee, so I'll be watching this like a hawk.
Will the "checksum" guys need to wait for .26, or will that more likely be repaired in a .25x ?
noticed i can "add to cart" Dodge credits
can they be used on anything yet?
Nice! Sooooo can they be edited as well?
So, any jtec mapped yet? Also, as far as jtec, will your software be able to overwrite vins on these units that have the "burned in" vin numbers? (I ask because even Chrysler tools can not overwrite some, but I know there are people out there that have some trick or something to do so)
What's up with the odd labels on the tables?
The tables had normal RPM and MAP labels in 2.23.
The axis label issue is the reason why we haven't announced Dodge beta yet. I'm working to fix that.
Tomorrows beta will have the axis values fix.
after 6 years and 211,000 views I think its time to put this one down, dodge you have been a tough battle but I can see the light :)