Nvram issue

[maverickpug666]

Ok so installed my nvram in my vr ss auto downloaded the 11p package soldered the jumper wire as per instructions im using an envyous customs aldl cable for the logging now my issue is the nvram comnects etc to tuner pro rt with the associated xdfs bins and adx files loaded but i keep getting a data error every 2 seconds or so and i cant figure out what it is thats causing it any help would be appreciated

[Gareth]

I don't know what the exact cause of those errors are but as far as I am aware that's normal.

[Tazzi]

Ok so installed my nvram in my vr ss auto downloaded the 11p package soldered the jumper wire as per instructions im using an envyous customs aldl cable for the logging now my issue is the nvram comnects etc to tuner pro rt with the associated xdfs bins and adx files loaded but i keep getting a data error every 2 seconds or so and i cant figure out what it is thats causing it any help would be appreciated

Depends on the ADX file used for logging, different definition files have different timeout differences then others ect. Likely be the definition file requests an update from the ECU faster than the ECU can keep up with or the timeout for waiting for a reply is too small.

My old VY V6 use to miss a response every so often as the ADX file was requesting information faster than the ECU was responding.

Hope that helps explain the logging scenario!

[Dylan]

When they error, are any packets missed? Or is the displayed error count just a visual notification?

[maverickpug666]

Its the connection box where it says connected itll connect then be right for a few seconds then turn red data error goes on in this cycle till i stop connection ill be checking the aldl config tommorow aswell as double checking my xdf and associated files surely there is somthing ive missed or havent unticked new to this so

[Wade]

Does the echo box need to be ticked or unticked?

[Wade]

Sounds like his having a data connection issue with the aldl cable when in TunerPro

[antus]

With pcmhacking interfaces its with echo....
Error denotes a checksum failure or timeout. Its more likely to be checksum failure, they dont really timeout for individual packets unless there is no comms at all. Wrong echo setting would cause heaps of problems from the get go.

[maverickpug666]

So echo needs to be enabled in both prefrence windows and in adx edit tick the rs232 echo aswell?? How do you see a checksum problem?

[Ken]

After a couple of years of not playing around with this side of tuning, I recently figured I was ready for another tinker, ran through the process of setting everything up on the new laptop I have, connected to the sons new ride, & noticed the same, intermittent disconnects where the coloured notification on the bottom where it says [ DA: Not Connected ] or [ DA: Connected ] was constantly changing status from connected to not connected, then connected again..
After triple checking everything I took the last resort of dumping the contents of the nvram & comparing it to the getrag version I downloaded from here & flashed to it a few weeks ago, not sure how, but it was altered, even though I'd not attempted to alter any of the tune yet.
I reflashed the nvram, & have yet to see it ever randomly disconnect again..
Not saying it's your problem, but it fixed my intermittent disconnect/reconnect situation..