how to extend fuel maps in uberdata
08-05-2005, 12:00 PM
#24
3.0 BAR
Join Date: Apr 2003
Posts: 2,260
Re: how to extend fuel maps in uberdata
My B16 will be revving to 9500-9600... 13.2:1 compression with Skunk2 stage 3 cams and ITBs.. there is a need for it sometimes. 
...but like JD said, you have to mod the code. I haven't looked at UD for a while, Blake may have an interface for RPM scalars. You'd have to use the P72 codebase, as the P75 has an 8000 rpm limit. I don't know what the high cam limit is... I'll run the numbers, and let you all know.
...but like JD said, you have to mod the code. I haven't looked at UD for a while, Blake may have an interface for RPM scalars. You'd have to use the P72 codebase, as the P75 has an 8000 rpm limit. I don't know what the high cam limit is... I'll run the numbers, and let you all know.
08-05-2005, 02:34 PM
#25
0.5 BAR
Thread Starter
Join Date: Jul 2005
Posts: 148
Re: how to extend fuel maps in uberdata
yea my b18c will have something like 11.6:1 ish compression with skunk2 stage 2 cams. and the cams make power at 9k+ so ill utilize it.
no turbo here guys, lol.
if you could find out how to extend the maps that would be great. i assume what you mean about modding the code is that you will have to change the intervals between the rpms? or physically adding more tables?
no turbo here guys, lol.
if you could find out how to extend the maps that would be great. i assume what you mean about modding the code is that you will have to change the intervals between the rpms? or physically adding more tables?
08-05-2005, 02:49 PM
#26
3.0 BAR
Join Date: Apr 2003
Posts: 2,260
Re: how to extend fuel maps in uberdata
Well, Honda made provisions in the map lookup routine that compares to an "RPM scalar". Basically, a number that disctates what rpm each row in the table is. Due to the scalar being an 8-bit number and the formulas used to change the human readable number into the correct 8-bit hex value, you're limited on the possibilities you have. 0x00 being the lowest, and 0xFF being the highest. I know on the low cam, and P75 ROMs, the max for 0xFF is 8000... the high cam will have a similar cap, but a little higher because of a different formula.
Now, you can mod those scalars to thier max, and it will still work within the realm of the stock Honda code. If you would want to go any higher, however, you would need to rewrite the table lookup routine to add more rows, or devise a different formula for the ECU to equate the human readable numbers, into a different measurement for the hex.
As far as I remember, Uberdata only lets you modify the STOCK rpm scalars... where as, Crome, has a plugin that rewrites the tables, and lets you get more RPMs out of the high cam...
Now, you can mod those scalars to thier max, and it will still work within the realm of the stock Honda code. If you would want to go any higher, however, you would need to rewrite the table lookup routine to add more rows, or devise a different formula for the ECU to equate the human readable numbers, into a different measurement for the hex.
As far as I remember, Uberdata only lets you modify the STOCK rpm scalars... where as, Crome, has a plugin that rewrites the tables, and lets you get more RPMs out of the high cam...
08-05-2005, 07:00 PM
#27
3.0 BAR
Join Date: Apr 2003
Posts: 2,260
Re: how to extend fuel maps in uberdata
...ya, it's what I thought..
High cam only goes to 8925... You'll have to mod the code for it to go any higher..
(35 * RPMScalar) = RPM for row
(35 * 0xFF) = 8925 ..(0xFF = 255 in Dec). So, what have we learned? I stated it in the second post of this thread.
High cam only goes to 8925... You'll have to mod the code for it to go any higher..
(35 * RPMScalar) = RPM for row
(35 * 0xFF) = 8925 ..(0xFF = 255 in Dec). So, what have we learned? I stated it in the second post of this thread.
Thread
Thread Starter
Forum
Replies
Last Post
Turblow
Engine Management
2
03-15-2006 10:24 AM
