pcmhacking.net

Hi all, just read this thread from start to finish and what an amazing result by VL400 and others of course.

I picked out a selection of posts outlining where I would get into trouble.

I need to save the CAL file first which contains the ‘tune’.

Do you just import 12Pv112 over the top of the existing bin?

Does 12Pv112 contain a CAL file which I could change minimum settings such as spark reference angle, injector rates, map setting etc just as a test or do I need to import the old CAL file at this point.

If after this it still doesn’t run I can just import the old CAL file back over the new bin and use the migration tool to make it compatible.

Thanks

Post by Holden202T » Tue May 18, 2010 8:48 am
well depending what version your running you should be able to upload the new bin file without removing the nvram .... so in that case my normal process...

* extract current cal file from 808
* upload latest release of 12P bin file to 808
* migrate step 1 cal file to suit new bin
* upload to 808


The FlashTool V1.33
Report Quote
Post by stevedarman » Sun Apr 17, 2011 11:03 am
Can some one explain the migrate option what it does and what it converts to I see a drop down list that i dont understand

Re: The FlashTool V1.33
Report Quote
Post by VL400 » Sun Apr 17, 2011 11:13 am
Its used for updating ose 12P cal files when I release new versions of 12P. Can then easily use your own tuned cal rather than starting from scratch and manually transferring over all the tables and scalars

e: The FlashTool V1.33
Report Quote
Post by antus » Sun Apr 17, 2011 12:58 pm
It will detect what version the cal you have is, and the what you pick is the version want it to convert it to (usually the latest, currently v1.1.1).

I think to run with 202s suggestion, you would need to start fresh with a clean 12p bin.
So load up a new 12p bin in Tunerpro, and load up the bin you saved from the ute as a Compare bin.
Then go down the list of Scalars, Flags and Tables, and compare the new 12p bin to the Compare bin.
Then change just the bare minimum, such as the spark reference angle, KINJ and any others you think will be absolutely necessary to get a start. Probably don’t worry about changing any Tables at this stage.
Then save that bin, and load it up using OSE Flashtool.

Once it’s loaded, try for a start. If it runs in any sort of fashion, I guess make a call as to whether you think the issue was with the NVRAM or still a mechanical issue.
Assuming it was all the NVRAM, go back into Tunerpro, and copy across the Scalars. Flags and Tables such as ignition and fuel maps.
But work your way down the list of Scalars, Flags and Tables, just comparing the new bin to what you did have in there. Basically setting it up from scratch.
Then save that bin, and load it up using OSE Flashtool again, and see how it goes.
Ideally it will run as good as what it did before.

I know all this is easy from the sidelines and a lot harder at the coal face. Fingers crossed.
I think we are all pretty keen to see this up and running again!

Thanks Brindo thats very helpful, so Tunerpro will save a copy of the full Bin file that I can then import to the NVRAM via the Flashtool? I thought it only saved the CAL part of the bin file.

Just load up that bin file you posted on page 139 as the compare bin.
That way, when you look at the Scalars, Flags and Tables, you can then just copy it from that original bin that you are comparing.
Just start by making the bare minimum of changes though.

Ok thanks for the advice

I don't think it is the bin file with TunerPro identifying the program as a 6 cylinder but the info provided by the Nvram saying it's a 4 cyl. I'd be burning your bin file to a VR 6 cyl memcal and seeing what happens then.

Charlescrown wrote: ↑Thu Jan 30, 2025 7:33 am I don't think it is the bin file with TunerPro identifying the program as a 6 cylinder but the info provided by the Nvram saying it's a 4 cyl. I'd be burning your bin file to a VR 6 cyl memcal and seeing what happens then.

Thanks Charles, i understand what you are saying but I still need to check that the jumpers haven’t moved. Unfortunately I haven’t had much luck burning memcals in the past so not a practical option for me at the moment.

It appears there are a few options for getting a new bin loaded.

If it is in 4 cylinder mode which it looks to be in that log it will fire cylinders at the wrong time and the injectors the wrong amount of times no wonder it runs bad lol

delcowizzid wrote: ↑Thu Jan 30, 2025 9:19 pm If it is in 4 cylinder mode which it looks to be in that log it will fire cylinders at the wrong time and the injectors the wrong amount of times no wonder it runs bad lol

Thanks for confirming Charles’ observation, it does seem to describe exactly what I am experiencing being a severe misfire.


So is the only way this would be occurring is from a problematic NVRAM and not a Bin corruption?

If the jumpers are in the right spot and connected properly then I would just need a new NVRAM?

Cheers

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