Holden202T wrote: ↑Fri Jan 31, 2025 1:09 pm
well those jumpers are to connect / disconnect an array of resistors to determine cylinder, so i guess its probably rare a resistor would fail but not impossible, would be more likely the jumper is loose or off all together .... rip the top off the ecu and you'll soon find out ....
verify all the jumpers, because there is a jumper option for memcal or jumper, if its on memcal, it uses the memcal plugged into the side of the nvram board to determine cylinder select, if its set to jumper then it uses the jumpers 4/6/8
Thanks for that explanation, I will be taking a photo that's for sure.
hope that's it but I don't care if I need to replace the NVRAM, I just need to move on from this and get to the dragstrip.
Charlescrown wrote: ↑Fri Jan 31, 2025 4:36 pm
It may sound stupid but do these NVram's have a permanet battery supply? Maybe take it out, give it some downtime and start again. Just a thought.
Yes they do Charles and its close to its 10 year lifespan but I reckon some people have run them longer. Not sure if you can get them out. Someone else will know.
Bad news the jumper hadn’t moved and is still firmly on 6cyl si I will try a burn the bin onto an eeprom.
I got out the burner and eeproms and could erase and write a bin ok as a test but just need to stack the bin as I have a 512 chip and this is where I came unstuck last time as I couldn’t get the chip to run.
I would stack 2 bins for a 512 chip, correct ?
The guide says it’s easiest to stack the the bins in tunerpro but should I get the bin using the flash tool?
I have never stacked a bin file. I just start the write at 8000 (from memory) and it works fine. Did you do a blank check after erasing the memcal? I use flash chips and have found it sometimes dosn't fully erase the chip so I do it twice before writing. Also slow down the write speed may help.
Gday all, does someone mind having a look at this log file for me.
I removed the NVRAM and installed a memcal with the burnt bin file and no difference and perhaps even worse as I couldn't even get it to idle at all but that could be fouled plugs.
I assume I am doing this right I downloaded the bin file from the emulator (i assume now memcal) to tunerpro and checked that the spark reference was 9.84 and that the boost tables were the modified ones and all good.
Does this now rule out a problem with the NVRAM? if so I will put it back in and import a fresh 12P bin via the OSE flashtool.
Charlescrown wrote: ↑Sun Feb 02, 2025 8:15 am
Well at least it's detecting the correct memcal. Have you gone back and checked the base timing with the memcal?
That’s great so you can see that from the log? I don’t know how to view any reports from it. I loaded the log file on another laptop and it plays and that’s it. I looked in the tunerpro help menu but couldn’t find much.
