SD - first test success
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I've done all the recoding work. You're just copying the code (in the form of hex tables) from the example ROM to the working ROM. To see the code, you add some definitions to the ROM xml file. Then just open the example ROM and working ROM in ECUFlash and copy/ paste the hex data in the tables. The number one mistake that people make is that they miss an item that needs to be copied, so take your time and make sure you don't overlook any of the items that need to be moved over.
I've done all the recoding work. You're just copying the code (in the form of hex tables) from the example ROM to the working ROM. To see the code, you add some definitions to the ROM xml file. Then just open the example ROM and working ROM in ECUFlash and copy/ paste the hex data in the tables. The number one mistake that people make is that they miss an item that needs to be copied, so take your time and make sure you don't overlook any of the items that need to be moved over.
Thanks again guys
aaron
Finally got the 5bar sensor working with the stock 2.0L motor the way i like it. RPM VE is very close to what banks set it to but the map vs load is definitely different. It seems that this particular car liked a value that was quite a bit less at lower loads than a 1 to 1 ratio.
Attached is my xml file and rom setup for a FP Red and e85.
You will need 7zip to open the file i just zipped it so EvoM would take it..
Attached is my xml file and rom setup for a FP Red and e85.
You will need 7zip to open the file i just zipped it so EvoM would take it..
Ok guys, I have read thur this thread and there is alot of info here. I think I just confuse myself a little more each time I read it. 
I have the Omni 4 bar map sensor installed. When I installed the SD patch I changed the settings like it says in the post for the Omni sensor. I also installed the patch to log boost with the jdm sensor, I setup everything just like it says in each post. If I log the jdm map on ecuflash, it is ~7-8psi lower than my actual gauge. What box do I need to be changing to get this inline? MAP Scaling?
Also when it comes to tuning, what is the "proper" method, I got a little bit done tonight before the rain came. Mr Bradly sent me a 35r base map and I used his Map Sensor VE and Calibration settings and his RPM VE settings. I have not messed with these settings. On my first wide open pull the car was very very lean, so I just started tuning the fuel maps, I have the a/f and timing dialed in already but my fuel map is way way "richer" than it was before. Should I put the fuel map back to where it was, and adjust the RPM VE table until the a/fs are close then fine tune with the fuel map?
Btw, my car is a 35r powered, e85 car, fp4r cams. This thing idles better then it EVER has with the maf! Very good work to all the people who figured this stuff out.
Thanks
Fathouse

I have the Omni 4 bar map sensor installed. When I installed the SD patch I changed the settings like it says in the post for the Omni sensor. I also installed the patch to log boost with the jdm sensor, I setup everything just like it says in each post. If I log the jdm map on ecuflash, it is ~7-8psi lower than my actual gauge. What box do I need to be changing to get this inline? MAP Scaling?
Also when it comes to tuning, what is the "proper" method, I got a little bit done tonight before the rain came. Mr Bradly sent me a 35r base map and I used his Map Sensor VE and Calibration settings and his RPM VE settings. I have not messed with these settings. On my first wide open pull the car was very very lean, so I just started tuning the fuel maps, I have the a/f and timing dialed in already but my fuel map is way way "richer" than it was before. Should I put the fuel map back to where it was, and adjust the RPM VE table until the a/fs are close then fine tune with the fuel map?
Btw, my car is a 35r powered, e85 car, fp4r cams. This thing idles better then it EVER has with the maf! Very good work to all the people who figured this stuff out.
Thanks
Fathouse
mrfred, I assume the MAT scaling is correct in your 96530706 SD patch? I found a difference between your MAT patch and the one in Tephra's v7 96530706 patch. There was a 100 degree difference between the MAT patch (being lower temp) and Tephra's patch (being higher temp).
Also does your SD patch have the immobilizer issue solved? I assumed so but, thought I'd ask. I've used the SD patch on only 96530006 cars so far but, but have a few 94170015 cars to do and want to confirm this before I start the work. Thanks for all your hard work on this, as usual!!!
Also does your SD patch have the immobilizer issue solved? I assumed so but, thought I'd ask. I've used the SD patch on only 96530006 cars so far but, but have a few 94170015 cars to do and want to confirm this before I start the work. Thanks for all your hard work on this, as usual!!!
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
mrfred, I assume the MAT scaling is correct in your 96530706 SD patch? I found a difference between your MAT patch and the one in Tephra's v7 96530706 patch. There was a 100 degree difference between the MAT patch (being lower temp) and Tephra's patch (being higher temp).
Also does your SD patch have the immobilizer issue solved? I assumed so but, thought I'd ask. I've used the SD patch on only 96530006 cars so far but, but have a few 94170015 cars to do and want to confirm this before I start the work. Thanks for all your hard work on this, as usual!!!
Also does your SD patch have the immobilizer issue solved? I assumed so but, thought I'd ask. I've used the SD patch on only 96530006 cars so far but, but have a few 94170015 cars to do and want to confirm this before I start the work. Thanks for all your hard work on this, as usual!!!
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
ok, if you've done everything correctly for SD, then the MAT values going into the SD algorithm are correct. Can you explain how you are reading MAT with the SD setup? Are you using tephra's MAT RAM variable and then reading the IAT (MAT for SD) value at the same time?
Let me clarify this first, I found the error prior to your SD patch for 96530706 as I noticed it while converting a 96530006 to Tephra's 96530706 v7.
I was having issues getting the car to run. I patched the v7 ROM with your MAt .xml definitions and was able to cure the issues with the car. I found the temperatures to be 100 degrees different between your MAT patched scaling and Tephra's v7 (96530706) scaling. I noticed in your SD 96530706 patch the scaling is the same as Tephra's v7 96530706 patch.
I haven't noticed an issue with SD cars running 96530706 but, I thought I'd bring it up as I never heard back from Tephra if it was in fact an issue to be concerned with.
I was having issues getting the car to run. I patched the v7 ROM with your MAt .xml definitions and was able to cure the issues with the car. I found the temperatures to be 100 degrees different between your MAT patched scaling and Tephra's v7 (96530706) scaling. I noticed in your SD 96530706 patch the scaling is the same as Tephra's v7 96530706 patch.
I haven't noticed an issue with SD cars running 96530706 but, I thought I'd bring it up as I never heard back from Tephra if it was in fact an issue to be concerned with.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
NM. I looked at tephra's ROM. It looks like there is an error in his output table. There should be an offset of 40(°C) in the table that I think he forgot to add. I'll mention it to him to confirm.
Ok thanks. I assume you'll SD patch will reflect the change as well if what you suspect is in fact the problem?
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR







