PCM NVRAM not connecting

[gasxp]

bin read from nvram.bin

(128 KiB) Downloaded 54 times

[gasxp]

Successfully connected and read bin. No issues with connection.

[SoullessShadow]

So you can connect and receive live data okay until you crank or start the car is that correct?

You don't have non resisted spark plugs in it or anything odd like that?

[gasxp]

Will always get errors when connected but increases rapidly when cranking.
Resisted plugs fitted.
This a track car, so the only things in the car are a fuel pump and engine fans which are on a separate switch( not ecu controlled ).
It will continuously error even with the fuel pump disconnected.
Car will start and run with previous memcal with data viewable on scan tool with no faults even during start.
Car wont run on nvram and has data errors whilst connected.

[antus]

Did the ose flash tool report errors and re-trys while it pulled that bin? Or did it just tick over and pull it off the car? It sounds like maybe you just have the wrong settings or the wrong ADX loaded in Tunerpro. Like echo not selected. It sounds like the nvram and the comms are fine. Can you send a screen shot of tunerpro with the errors coming up that shows what files you have? and one that shows the config you have in oseplugin?

[gasxp]

Ose falsh tool connected and read the bin file with no faults.
Bin,xdf and adx all all from the file gareth sent and have tried before.
Echo setting has been switched both ways with no difference.
I will get screen shots tomorrow when i get back to work.
Still does not explain why it wont run.
Are you able to look at the bin file that i pulled off the memcal that works. It comes up unknown in the id tool. Maybe it could help get this thing running at least.

[antus]

looks ok, has the version "pcmhacking.net 51HE 1.0 VSV6 AT" in it, which matches up to the VS SC V6.

Here is a thought, have you turned off VATS since you dont have a BCM? It could be the PCM asking the BCM if its seen the key over and over and confusing tunerpro?

Ok, so I checked your bin, "Anti Theft Module Disabled" was not set. You can do this yourself on the NVRAM from Tunerpro, just keep changing it while "emulating" until it gets through the key request from the PCM and saves. Then everything should start working. You can also upload the cal with ose flash tool. Just look for *.bin so it sees the bin and then it'll upload it as calibration.

Or.... I disabled it for you in this copy of the bin. So you can load that in a programmer and get to the same starting point.

[gasxp]

Antus you nailed it. Loaded the bin file, started immediately and flawless comms. Thankyou very much.

[SoullessShadow]

Never doubted this would get sorted. So many crazy knowledgeable people on here that are so willing to help out when there is a problem.

[antus]

good to hear