VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Conversion
- JA2Z
- Posts: 76
- Joined: Tue Mar 08, 2016 9:59 am
- cars: - WH II 5.7L Statesman (daily)
- VT 5.0L Calais
- 1994 Ford Probe V6 DOHC
- 2007 Ford Focus TDCI 2.0 - Location: East Gippsland, Victoria
- Contact:
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
So my current Bin version is still the version The1 shipped it with when I got it March 2016 - Version 0.91
After talking with The1, he advised that only just now in version 1.00 did Wideband/MAP pin input support get added to the VT V8 Enhanced Bin.
I had downloaded and updated my working Bin, XDF & ADX in TP5, but I haven't since uploaded that bin to the NVRAM... hence why I have no pin input logging showing up in TP5.
Today I'll update the bin and test.
After talking with The1, he advised that only just now in version 1.00 did Wideband/MAP pin input support get added to the VT V8 Enhanced Bin.
I had downloaded and updated my working Bin, XDF & ADX in TP5, but I haven't since uploaded that bin to the NVRAM... hence why I have no pin input logging showing up in TP5.
Today I'll update the bin and test.
- JA2Z
- Posts: 76
- Joined: Tue Mar 08, 2016 9:59 am
- cars: - WH II 5.7L Statesman (daily)
- VT 5.0L Calais
- 1994 Ford Probe V6 DOHC
- 2007 Ford Focus TDCI 2.0 - Location: East Gippsland, Victoria
- Contact:
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
So an update,
I bricked my NVRAM by updating to version 1.00 - from 0.91
I uploaded a 1.00 bin and now I don't have any fuelling or comms with the NVRAM.
After messaging The1, he advised I'll have to upload version 1.00 onto the NVRAM because you can't load a 1.00 (cal) bin onto a 0.91 version NVRAM
So Now that I've had to order a programmer to sort this,
Here is a video of me milling the intake today for the blower.
[youtube]https://www.youtube.com/watch?v=2cvV1ipTNLI[/youtube]
I bricked my NVRAM by updating to version 1.00 - from 0.91
I uploaded a 1.00 bin and now I don't have any fuelling or comms with the NVRAM.
After messaging The1, he advised I'll have to upload version 1.00 onto the NVRAM because you can't load a 1.00 (cal) bin onto a 0.91 version NVRAM
So Now that I've had to order a programmer to sort this,
Here is a video of me milling the intake today for the blower.
[youtube]https://www.youtube.com/watch?v=2cvV1ipTNLI[/youtube]
Last edited by JA2Z on Wed Sep 06, 2017 11:43 am, edited 1 time in total.
- vlad01
- Posts: 7801
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
Those programmers are so worth having, not for just getting you our of trouble but worth it for other stuff.
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
- JA2Z
- Posts: 76
- Joined: Tue Mar 08, 2016 9:59 am
- cars: - WH II 5.7L Statesman (daily)
- VT 5.0L Calais
- 1994 Ford Probe V6 DOHC
- 2007 Ford Focus TDCI 2.0 - Location: East Gippsland, Victoria
- Contact:
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
Yep, a few blokes kindly offered to help with programming for me. (and I may yet take up their help, if/when I get stuck)
But I opted to buy a GQ4x4 and will find good use for it for both the NVRAMs and memcals I have.
But I opted to buy a GQ4x4 and will find good use for it for both the NVRAMs and memcals I have.
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
yep am happy to reprogram for free anytime just cover postage. But having your own burner is worth it, those GQ burners do just about anything.
- JA2Z
- Posts: 76
- Joined: Tue Mar 08, 2016 9:59 am
- cars: - WH II 5.7L Statesman (daily)
- VT 5.0L Calais
- 1994 Ford Probe V6 DOHC
- 2007 Ford Focus TDCI 2.0 - Location: East Gippsland, Victoria
- Contact:
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
So... The GQ4x4 arrived today
Loaded the software and drivers
Read and backed up the suspected corrupted bin on the VT V8 NVRAM
Wrote the latest version 1.00 Enhanced Mod bin to the VT V8 NVRAM
Verified the bins to confirm successful write using HxD
Installed into the VT and Loaded TP5
Powered vehicle....and SUCCESS!!!!! Voltage on pins A5 & B10 !!!!!
Loaded the software and drivers
Read and backed up the suspected corrupted bin on the VT V8 NVRAM
Wrote the latest version 1.00 Enhanced Mod bin to the VT V8 NVRAM
Verified the bins to confirm successful write using HxD
Installed into the VT and Loaded TP5
Powered vehicle....and SUCCESS!!!!! Voltage on pins A5 & B10 !!!!!
- JA2Z
- Posts: 76
- Joined: Tue Mar 08, 2016 9:59 am
- cars: - WH II 5.7L Statesman (daily)
- VT 5.0L Calais
- 1994 Ford Probe V6 DOHC
- 2007 Ford Focus TDCI 2.0 - Location: East Gippsland, Victoria
- Contact:
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
Now a question for Antus and VL400, or anyone else that knows...
Should the VS V8 NVRAM bin that I read from the NVRAM Antus just sent me in the mail only weeks ago vary from the "OSE 11p V104 BLCC Stacked" bin I downloaded from 11p thread?
Total n00b to this programming in assembly language thing, but I wonder why they vary?
Should the VS V8 NVRAM bin that I read from the NVRAM Antus just sent me in the mail only weeks ago vary from the "OSE 11p V104 BLCC Stacked" bin I downloaded from 11p thread?
Total n00b to this programming in assembly language thing, but I wonder why they vary?
- antus
- Site Admin
- Posts: 8253
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
It is possible thats an error on my part. Did I set the PCM jumper before shipping? If the PCM jumper is not set, I can send you one (or if you have one, you can just add it). If it is set then it could be because the start of the nvram maps over the top of RAM, and the ECM has written to that address which has been stored on the NVRAM as well as RAM. Is that the only difference? addresses lower than 0x1000 can be ignored (and are, from the pcms point of view). As there are two banks on the nvram, the same is true of 0x10000->0x11000 for the other bank. Its also possible that is they byte 11P uses to check if an NVRAM is installed when it starts up. I know it does a test write/read cycle, I am not sure of the address. It could make sense that it is there.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: VT V8 304 MAF NVRAM -> VS V8 MAP NVRAM + M122 SC Convers
How different are they? In which locations?