Calterm errors out on Dodge reads if i remember correctly. But yes, it can be done via 1939. Via underhood connector or OBD connector. Takes about 10 min.
Type: Posts; User: Chavez91; Keyword(s):
Calterm errors out on Dodge reads if i remember correctly. But yes, it can be done via 1939. Via underhood connector or OBD connector. Takes about 10 min.
Its been a long while. But IIRC theres some comms spoofing that needs to be done. Had an arduino setup a few years ago that did it. I think it was TCM and BCM comms? Id honestly have to dig in the...
I'm not sure if it was forgotten about.... But AL5 FULL flashing is still missing from V8.
The only real time that LLYs die is during the LOCKER patch.... If its a stock full flash or a full flash that isn't locking the ECM to the V2/V3, I've stopped many of full flashes mid flash without...
7A5.cax: No [A40] entry in C:\Program Files (x86)\EFILiveProduction\V8\V7toV8_Segments.ini
Is the naming scheme for V8 different for A40? Or do I just need to convert it over by hand?
Could you do A50, E98, T87 and E35A&B whenever you have a chance? :D
Then I can get to town testing out V8 Editor! :D
Does this update include the ability to load CAX8 files without a CAM file?
Ok, Makes complete sense.
So I guess this is where it gets weird because my range is 0 - 65535. Can guarantee that it didn't make it that far in about 3 hrs. I can break it up smaller than that....
Giving this a try.
I did get it going, but after about 2225 keys it said "Locked with custom Key" So i checked the "Restart" box and now its just running like if you have "Try Stock Key"...
Is it possible to have the Try Key Range for unlocking LLY and LB7 controllers accept a hex value? It seems to only take decimal. But if you enter a Hex value, you get no error, and it just resorts...
What ross said. Ran the latest RC then updated firmware. Dont have my v2 with me so i cant confirm exact version. Its whatever is in RC3.
Had this same issue.. Make sure that your firmware is updated. That solved my problem
Thanks! :thumb_yello:
On the CAX8 stuff... It seems like it requires a .CAM file for the file to even be recognized in the v8 editor even if there is a CAX8 file definition. There was some AL5...
It would be useful for the Alternate Firing order guys instead of having to repin the harness. I had seen it and was like "OOH! That was on my list of things to hunt down. SWEET!" It looked like it...
I was looking at the E60 in V8. Noticed some cool new params. lol
B9903 - Injector Assignment seems to be referencing the wrong address though. :(
I have the correct one if you need it. I can PM...
Thanks! Investigating. :thumb_yello:
Any Idea why when I bring in a bone stock IA80012.04 file into V7.5.... I get an incorrect checksum? Even converted from XCAL using yalls tool... same problem... V8 too using the files from above.
This thread is the true origin of the Corona Virus ..... Lol
Thats much better!
Thanks! :D
Paul, another bug...
When Caxing 1D table that is 8 bit, if its a single ROW, it decides to skip bytes for fun. lol
Here is where it gets odd, define the 2nd row and now you can see the skipped...
Lol you just beat me to the punchline. I was just writing about that. Gotta love windows programmers lol that definitely got annoying quick
Hey Paul,
Here's a funny bug.
Lets say you are building a CAX. If you use windows calculator in programmer mode (windows 10), type in an address, (using just your keyboard) hit '+' and add your...
Ahhh.... That makes sense! haha. Well thanks for figuring it out! :D
If there is anything you need from me for the DMA issue, let me know.
Thanks again Paul!
Paul,
Has the 32 bit limit on PKT PIDs been lifted yet?
I also might have a problem with E98 DMA pids as welll.
Example.
If requesting address 0x400134E8, when its verifying the PIDS,...
I know that some ecms get pissy with out trailing zeros for some things, ie they expect certain data lengths of 7 or 8 bytes..... but i would assume mode 22 works? I was under the impression that...