Links to jcsbanks' Speed Density patches
Newbie
Joined: Feb 2007
Posts: 5
Likes: 0
From: UK
I don't know if this will help, but John already has a version of the live map app with SD table editing included :-
http://banks.myzen.co.uk/88570008release.zip
I've managed to use the charting live map app that was posted with 96530006 on a 96260009 ECU by changing the settings for the ROM address, RAM address and Logging address on the front settings screen, so it might be worth giving this verison a go. As far as I can tell, the live map app is 'universal' to all ROMS, as long as you know the correct addresses.
Eventually once I have everything sorted I will be swapping to the SD version of the 96530706 ROM, so it would be good to see all the live map stuff and SD tuning all working as I find it really speeds up the process of getting things dialled in.
Maybe we can persuade John to combine the SD version and the charting version together, if we can prise him away from dissassembling the GTR ECU
http://banks.myzen.co.uk/88570008release.zip
I've managed to use the charting live map app that was posted with 96530006 on a 96260009 ECU by changing the settings for the ROM address, RAM address and Logging address on the front settings screen, so it might be worth giving this verison a go. As far as I can tell, the live map app is 'universal' to all ROMS, as long as you know the correct addresses.
Eventually once I have everything sorted I will be swapping to the SD version of the 96530706 ROM, so it would be good to see all the live map stuff and SD tuning all working as I find it really speeds up the process of getting things dialled in.
Maybe we can persuade John to combine the SD version and the charting version together, if we can prise him away from dissassembling the GTR ECU
Thanks. I was up until 3am last night trying to update the source code that I have to include what he has here. 
I had it almost done, except I was having a couple problems with the datgridview objects for the new tables. I would like to see the source of this release if you have it. I'm pretty sure I know what I'm doing now, but again, maybe not.
I had it almost done, except I was having a couple problems with the datgridview objects for the new tables. I would like to see the source of this release if you have it. I'm pretty sure I know what I'm doing now, but again, maybe not.
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Don't really have much chance to develop or test this further, but do feel free to share any files publically, even ones I've emailed.
Do not rely on files being on my webspace forever (although I have no plans to remove them if I changed ISP in future they may disappear).
Bottom line is take ownership of this as I'm glad you are doing, mirror/store the files as you see fit, tidy it up, improve it, document it and enjoy!
The setup for 88570008 I was very pleased with, all the ECU work had been done and all the puzzles solved. The only wish list was to remove the quick and dirty hard coding with the graphing and just make things a bit more configurable/trap errors etc.
Do not rely on files being on my webspace forever (although I have no plans to remove them if I changed ISP in future they may disappear).
Bottom line is take ownership of this as I'm glad you are doing, mirror/store the files as you see fit, tidy it up, improve it, document it and enjoy!
The setup for 88570008 I was very pleased with, all the ECU work had been done and all the puzzles solved. The only wish list was to remove the quick and dirty hard coding with the graphing and just make things a bit more configurable/trap errors etc.
5) Compatibility with patch to remove MAF load limit. A few months before the SD patch came out, jcsbanks came up with a trick to disable the MAF 380 load limit. The patch consists of changing one line of code to 0x0009. This patch is *not compatible* with the SD patch, so it should not be applied.
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Restore (to original) the changes you made to remove the MAF based load and IPW limits before applying the SD patch.
SD patch has no load or IPW limit.
Tech bit:
They both use very closely related parts of the same routines, but in terms of the code do the opposite to achieve it. The MAF load and IPW limit removal stops limits overwriting our load and IPW if the values are higher than the limits. The SD patch calculates a simulated airflow and places it in what used to be the limits and then we force the limits to overwrite the MAF based values. It was just the most elegant way to patch the code without doing lots of rewriting of code. By adding NOP (no operation) in strategic places you can reroute the code and bend it to your will
SD patch has no load or IPW limit.
Tech bit:
They both use very closely related parts of the same routines, but in terms of the code do the opposite to achieve it. The MAF load and IPW limit removal stops limits overwriting our load and IPW if the values are higher than the limits. The SD patch calculates a simulated airflow and places it in what used to be the limits and then we force the limits to overwrite the MAF based values. It was just the most elegant way to patch the code without doing lots of rewriting of code. By adding NOP (no operation) in strategic places you can reroute the code and bend it to your will
Restore (to original) the changes you made to remove the MAF based load and IPW limits before applying the SD patch.
SD patch has no load or IPW limit.
Tech bit:
They both use very closely related parts of the same routines, but in terms of the code do the opposite to achieve it. The MAF load and IPW limit removal stops limits overwriting our load and IPW if the values are higher than the limits. The SD patch calculates a simulated airflow and places it in what used to be the limits and then we force the limits to overwrite the MAF based values. It was just the most elegant way to patch the code without doing lots of rewriting of code. By adding NOP (no operation) in strategic places you can reroute the code and bend it to your will
SD patch has no load or IPW limit.
Tech bit:
They both use very closely related parts of the same routines, but in terms of the code do the opposite to achieve it. The MAF load and IPW limit removal stops limits overwriting our load and IPW if the values are higher than the limits. The SD patch calculates a simulated airflow and places it in what used to be the limits and then we force the limits to overwrite the MAF based values. It was just the most elegant way to patch the code without doing lots of rewriting of code. By adding NOP (no operation) in strategic places you can reroute the code and bend it to your will
Warning: there was an error in post #166. The location of the "tephra adjustment #2" table was incorrect. If you haven't already made any changes to support live mapping, just follow the directions as posted. If you've already updated your ROM, add the following to the Tephra v7t6 XML:
Change the original "tephra adjustment #2 (DEADloc)" back to "FFFF" and "841C" (not 841E, like the new location is, but 841C, like it was when you first changed it).
Then, pull up the new "FIXED tephra adjustment #2 (DEADloc)" table, and change it from "FFFF" and "841E" to "FFFF" and "A800".
When you're done, you can delete the old table from the XML, and rename the new one in it's place, if you're obsessive compulsive.
Hopefully that's clear enough. Thanks VERY MUCH to l2r99gst for finding the problem!
Code:
<table name="FIXED tephra adjustment #2 (DEADloc)" category="DMA Logging/Mapping" address="3e638" type="2D" scaling="Hex16"> <table name="Address" type="Static X Axis" elements="2"> <data>0x3E638</data> <data>0x3E85A</data> </table> </table>
Then, pull up the new "FIXED tephra adjustment #2 (DEADloc)" table, and change it from "FFFF" and "841E" to "FFFF" and "A800".
When you're done, you can delete the old table from the XML, and rename the new one in it's place, if you're obsessive compulsive.
Hopefully that's clear enough.
Thanks VERY MUCH to l2r99gst for finding the problem!
I have a couple questions; the first one is why does my RPM VE show up as a vertical table when everyone else's is horizontal?
The second question is this: I have updated my 94170015 XML w/ the MAT & SD additions and patched my ROM, then flashed to the car. The car will crank and try to start, but then dies off. Even w/ the base settings I copied over I figured the car would start/idle, but no luck. Any ideas on whether it has something to do w/ the SD settings or could I have botched something in the patching & XML additions. I'm pretty experienced in patching and XML changes, but I'm at a loss. I have triple checked that I copied everything correctly as well. Any suggestions are appreciated
The second question is this: I have updated my 94170015 XML w/ the MAT & SD additions and patched my ROM, then flashed to the car. The car will crank and try to start, but then dies off. Even w/ the base settings I copied over I figured the car would start/idle, but no luck. Any ideas on whether it has something to do w/ the SD settings or could I have botched something in the patching & XML additions. I'm pretty experienced in patching and XML changes, but I'm at a loss. I have triple checked that I copied everything correctly as well. Any suggestions are appreciated
My table is vertical, too.
For the no starting/stalling issue: Do you have the load limiter removal patch applied? That one where you put 0x0009 in place of something? If so, get rid of that and put back to stock value.
I thought you were already running SD, since you had the Dejon intake and 4090 installed? Or was this in preparation for SD?
For the no starting/stalling issue: Do you have the load limiter removal patch applied? That one where you put 0x0009 in place of something? If so, get rid of that and put back to stock value.
I thought you were already running SD, since you had the Dejon intake and 4090 installed? Or was this in preparation for SD?
My table is vertical, too.
For the no starting/stalling issue: Do you have the load limiter removal patch applied? That one where you put 0x0009 in place of something? If so, get rid of that and put back to stock value.
I thought you were already running SD, since you had the Dejon intake and 4090 installed? Or was this in preparation for SD?
For the no starting/stalling issue: Do you have the load limiter removal patch applied? That one where you put 0x0009 in place of something? If so, get rid of that and put back to stock value.
I thought you were already running SD, since you had the Dejon intake and 4090 installed? Or was this in preparation for SD?
. I already removed the load limiter and IPW lines of code from the XML as well.
Just went out and tested again; w/ the SD patched ROM flashed to the car it will start up fine w/ the MAF still plugged in. When the car is running it should also run w/o the MAF plugged in, but dies on me if I pull the plug. Any ideas what's causing this? I'm using a Tephra V5.1 version of 94170015
When you said you removed the load limiter from the XML....did you change the value back to what it was stock?
You don't have to remove the defs from the XML. You just have to 'undo' that patch and change the 0009 to what it was before.
You don't have to remove the defs from the XML. You just have to 'undo' that patch and change the 0009 to what it was before.