Our ECUs can have eight sets of maps...
#98
Evolved Member
iTrader: (12)
This answers my "How do I have a Gas and E85 tune"
This opens alot of possibilities..
Race map, Street Map, Valet Map
Failsafe map, Nitrous Map, etc..
At this point you would need a spare input for a map switch.. a rheostat or input might work well if it had detents..
Even if the maps are in rom, this is a huge deal.
This opens alot of possibilities..
Race map, Street Map, Valet Map
Failsafe map, Nitrous Map, etc..
At this point you would need a spare input for a map switch.. a rheostat or input might work well if it had detents..
Even if the maps are in rom, this is a huge deal.
can't we also delete some of these and have like a 64x64 map?
#99
EvoM Guru
iTrader: (5)
O2 sensors don't work that way... the O2 sensor reads a lambda value, not AFR, AFR is a number for humans to understnd. Stoich for any fuel will be roughly the same voltage output from the sensor. This is good for closed loop, assuming there was enough adjustment in fuel trims, it could accomodate it. However handling it automatically is more complex for open loop, especially when you want to make optimum power too, now you have boost and timing to take into account. GM Flex fuel vehicles have fuel composition sensors that can be used, but then there is some engineering and programming involved.
#101
EvoM Guru
iTrader: (6)
hrmm just resurrecting an old thread...
So I went to implement the injector scaling + latency (do we even need dual latency maps??) today, and have hit a snag...
The ecu doesn't use a pointer to the table, it uses the address of the table itself. This is a bit annoying as its harder to do a "shifty swap" like I am doing for Fuel+Timing...
So I have to think of a good way of doing it, maybe re-writting the block of code that references the injector tables... its not that much code but the thought of doing it for every ROMID is killing it for me
So I guess how important is injector scaling+latency swapping, I know for E85 its imperative, but for all you other guys would you need it?
So I went to implement the injector scaling + latency (do we even need dual latency maps??) today, and have hit a snag...
The ecu doesn't use a pointer to the table, it uses the address of the table itself. This is a bit annoying as its harder to do a "shifty swap" like I am doing for Fuel+Timing...
So I have to think of a good way of doing it, maybe re-writting the block of code that references the injector tables... its not that much code but the thought of doing it for every ROMID is killing it for me
So I guess how important is injector scaling+latency swapping, I know for E85 its imperative, but for all you other guys would you need it?