SD - first test success
also if possible could you please port to v 5.7 tephra mods not v 5.10 as there are issues with 5.10
cheeky I know lol
Will this be easily ported into the Evo VIII roms? I'm currently running speed density with MaftPro on 94170015 and would love to ditch the MaftPro. I'm already set up to test with MAP sensor and MAT, so I'd be happy to test the system. Unfortunately, I have no disassembly skills, so I won't be much help in that arena.
-Paul
-Paul
I *might* attempt to look at the changes necesarry for either 96940011 or 96530006, but most likely will have to wait for someone else to port the patch over. I think this might finally be the reason for me to switch to the 96530006 ROM, so maybe I won't even look at 96940011.
Last edited by l2r99gst; Feb 11, 2009 at 12:19 PM.
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
http://banks.myzen.co.uk/90550001-v5.10fix-mods-SD.zip
If you want to apply it to another ROM just copy all the SD tables in Ecuflash.
You need to have MAP sensor logging working on request ID 38 (on its original FFFF8823 address in your MUT table) for my patch to work, unless you want to edit (in MAP calibration header 1) the FFFF8822 to another word location where your MAP sensor variable is).
This patch has 8 bit MAP sensor scaling (1.334x) since there is no simple way to get 10 bits. 8 bits ran fine on my engine. If you have a GM 3 bar change the scaling for the top row in the MAP VE table to 1.22x and then correct the values in the top row to match what they were set to before.
These patches do require disassembly to find the locations. It took me about 90 mins to do 90550001 from having no disassembly to start with, to checking it. There are some fiddly bits to find and relocate.
If you want to apply it to another ROM just copy all the SD tables in Ecuflash.
You need to have MAP sensor logging working on request ID 38 (on its original FFFF8823 address in your MUT table) for my patch to work, unless you want to edit (in MAP calibration header 1) the FFFF8822 to another word location where your MAP sensor variable is).
This patch has 8 bit MAP sensor scaling (1.334x) since there is no simple way to get 10 bits. 8 bits ran fine on my engine. If you have a GM 3 bar change the scaling for the top row in the MAP VE table to 1.22x and then correct the values in the top row to match what they were set to before.
These patches do require disassembly to find the locations. It took me about 90 mins to do 90550001 from having no disassembly to start with, to checking it. There are some fiddly bits to find and relocate.
Last edited by jcsbanks; Feb 11, 2009 at 02:24 PM.
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
I just went to look at 96530006 and they have done it differently! Not much space in the main routine we have been altering. It can be done but needs more thought, and soon I am away on vacation.
Evolved Member
Joined: Aug 2007
Posts: 569
Likes: 1
From: UK
http://banks.myzen.co.uk/90550001-v5.10fix-mods-SD.zip
If you want to apply it to another ROM just copy all the SD tables in Ecuflash.
You need to have MAP sensor logging working on request ID 38 (on its original FFFF8823 address in your MUT table) for my patch to work, unless you want to edit (in MAP calibration header 1) the FFFF8822 to another word location where your MAP sensor variable is).
This patch has 8 bit MAP sensor scaling (1.334x) since there is no simple way to get 10 bits. 8 bits ran fine on my engine. If you have a GM 3 bar change the scaling for the top row in the MAP VE table to 1.22x and then correct the values in the top row to match what they were set to before.
These patches do require disassembly to find the locations. It took me about 90 mins to do 90550001 from having no disassembly to start with, to checking it. There are some fiddly bits to find and relocate.
If you want to apply it to another ROM just copy all the SD tables in Ecuflash.
You need to have MAP sensor logging working on request ID 38 (on its original FFFF8823 address in your MUT table) for my patch to work, unless you want to edit (in MAP calibration header 1) the FFFF8822 to another word location where your MAP sensor variable is).
This patch has 8 bit MAP sensor scaling (1.334x) since there is no simple way to get 10 bits. 8 bits ran fine on my engine. If you have a GM 3 bar change the scaling for the top row in the MAP VE table to 1.22x and then correct the values in the top row to match what they were set to before.
These patches do require disassembly to find the locations. It took me about 90 mins to do 90550001 from having no disassembly to start with, to checking it. There are some fiddly bits to find and relocate.
many thanks JOHN really appreciate this
Evolved Member
Joined: Aug 2007
Posts: 569
Likes: 1
From: UK
I haven't personally noticed this issue, as my wideband reads the same when I switch maps, and the car runs fine.
But BarryC has noticed it, and I think GrayW has also noticed it on an EDM Evo 8 rom.
I will log my car tommorrow and see if it does stop responding on the ALT map.
when I used alt maps in 5.10 for my E85 conversion the front O2 stopped reading back it just sat there frozen at 0.01v and the car ran very badly
changed the sensor and didnt make any difference flashed the rom in again
no difference
changed to 5.7 and everything was perfect front 02 again
I will wait until this is finalized and read the "Speed Density Conversion for Dummies" thread that it is made. 
Great work by everyone in this thread thus far, though.
Great work by everyone in this thread thus far, though.
yeah Dave sent ya an email on it mate
when I used alt maps in 5.10 for my E85 conversion the front O2 stopped reading back it just sat there frozen at 0.01v and the car ran very badly
changed the sensor and didnt make any difference flashed the rom in again
no difference
changed to 5.7 and everything was perfect front 02 again
when I used alt maps in 5.10 for my E85 conversion the front O2 stopped reading back it just sat there frozen at 0.01v and the car ran very badly
changed the sensor and didnt make any difference flashed the rom in again
no difference
changed to 5.7 and everything was perfect front 02 again
take it offline not to clog up this thread
http://banks.myzen.co.uk/90550001-v5.10fix-mods-SD.zip
If you want to apply it to another ROM just copy all the SD tables in Ecuflash.
You need to have MAP sensor logging working on request ID 38 (on its original FFFF8823 address in your MUT table) for my patch to work, unless you want to edit (in MAP calibration header 1) the FFFF8822 to another word location where your MAP sensor variable is).
This patch has 8 bit MAP sensor scaling (1.334x) since there is no simple way to get 10 bits. 8 bits ran fine on my engine. If you have a GM 3 bar change the scaling for the top row in the MAP VE table to 1.22x and then correct the values in the top row to match what they were set to before.
These patches do require disassembly to find the locations. It took me about 90 mins to do 90550001 from having no disassembly to start with, to checking it. There are some fiddly bits to find and relocate.
If you want to apply it to another ROM just copy all the SD tables in Ecuflash.
You need to have MAP sensor logging working on request ID 38 (on its original FFFF8823 address in your MUT table) for my patch to work, unless you want to edit (in MAP calibration header 1) the FFFF8822 to another word location where your MAP sensor variable is).
This patch has 8 bit MAP sensor scaling (1.334x) since there is no simple way to get 10 bits. 8 bits ran fine on my engine. If you have a GM 3 bar change the scaling for the top row in the MAP VE table to 1.22x and then correct the values in the top row to match what they were set to before.
These patches do require disassembly to find the locations. It took me about 90 mins to do 90550001 from having no disassembly to start with, to checking it. There are some fiddly bits to find and relocate.