The stock ECU has gear dependent boost control!
If you go over the end of the map it just uses the last value when you use the ECU's usual interpolation routines.
The speed reading is very coarse indeed. I wonder if you might be better using speed as an input to a gear number map, and then using gear number as a lookup for your boost table. This will make the gear judge discrete rather than continuous. If for some odd reason someone had large gaps between two adjacent gears this would then avoid hunting and poor boost control. The beauty is that all the ECU code to do these stages of lookup is there, just load up the registers with your addresses and write the correct headers in your lookup maps.
The speed reading is very coarse indeed. I wonder if you might be better using speed as an input to a gear number map, and then using gear number as a lookup for your boost table. This will make the gear judge discrete rather than continuous. If for some odd reason someone had large gaps between two adjacent gears this would then avoid hunting and poor boost control. The beauty is that all the ECU code to do these stages of lookup is there, just load up the registers with your addresses and write the correct headers in your lookup maps.
right guys.
slight problem.
the RPM/Speed variable isn't all that accurate, ie it can be several points of. Now this is fine for the in between interpolation, but what happens at the extents of the map?
ie if our last column is 6th gear, which is roughly 25rpm_per_kph, now for whatever reason the RPM/Speed variable is reading 20, how does the ECU interpolate past the end of the map?
slight problem.
the RPM/Speed variable isn't all that accurate, ie it can be several points of. Now this is fine for the in between interpolation, but what happens at the extents of the map?
ie if our last column is 6th gear, which is roughly 25rpm_per_kph, now for whatever reason the RPM/Speed variable is reading 20, how does the ECU interpolate past the end of the map?
Actually the system seems to be working quiet well.
Doing another run this morning so I will post up my log and WGDC table.
Yeah it wasn't hard to add the 3d table, especially since I already had done the Tephramod stuff.
Release will be pretty soon
Doing another run this morning so I will post up my log and WGDC table.
Yeah it wasn't hard to add the 3d table, especially since I already had done the Tephramod stuff.
Release will be pretty soon
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
No prob to use psi-based control.
I have a graph to post up - just busy atm.
I will setup the tables as per original rom (ie load), it will be upto the user to change to PSI... Should be fairly easy (just scaling change)
I will setup the tables as per original rom (ie load), it will be upto the user to change to PSI... Should be fairly easy (just scaling change)
voila:

There is some uppy-downy ness due to the rpm's droping, presumably just bad shifting on my behalf.
Thoughts?
I can post the full XLS if anyone likes!
edit - thats a 1st, 2nd, 3rd log, ie first 3 columns of 3dmap.

There is some uppy-downy ness due to the rpm's droping, presumably just bad shifting on my behalf.
Thoughts?
I can post the full XLS if anyone likes!
edit - thats a 1st, 2nd, 3rd log, ie first 3 columns of 3dmap.
Last edited by tephra; Nov 24, 2008 at 07:35 PM.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Sorry, yeah it was a consecutive upshift rather than breaking down to 2500 todo a pull per gear.
If you want I can do:
1st - 2500 - 7000
2nd - 2500 - 7000
3rd - 2500 - 7000
If you want I can do:
1st - 2500 - 7000
2nd - 2500 - 7000
3rd - 2500 - 7000



