Hello, im playing with euro Outlander turbo 2006. It has some very first type of ETC(electronic throttle), cable goes into enginebay, where is TPS sensor remote mounted and than ecu driving ETC trhottlebody on intake manifold.

Respons on throttle pedal is ok on idle revving, when car not moving. When it pass say 10kmh it starts to be very laggy. I read some ralliart colt and evoX threads about modifiing throttle maps.
I just found one similar map in this ecu (C728009/10/11) at 0x744f (8x27), but editing it to zero first row then 255 , doesnt have influence on anything.

There is just very basic xml on evoscan. Also colt xmls has throttle maps defined wrong.

http://www.evoscan.com/roms/mitsubis...T_C7280009.hex
http://www.evoscan.com/roms/mitsubis...6/C7280009.xml

thanks for reading

 

Probably nobody interested here...

After some hours, i found one 16bit 17x17 table very similar to throttle maps in colt/evox. But it goes only up to 50% - same as colt half limpmode and there is just this single 16bit "throttle" shaped map in outlander rom.
Also my experience driving in limp mode(check light) throttle response feels still the same.

I will test it soon.

 

Are you just looking for pretty pictures in maps address range or actually reading code?
Because as far as I know map at 0x744f isn't referenced anywhere in program code.

There are several maps that control accelerator pedal position to target throttle position translation (low/mid/high gear) but they are more like 10x27 8-bit, where _simplified_ target_throttle_position = map(rpm, apps) * apps.

P.S. What does "throttle" shaped map look like?

 

Thanks for reaction.

I dont have skills for reading cpu code. So i just comparing similar roms with know adresses in hex file.

Table what im talking now is at 0x53c2. As said, i didnt found any similar one in this rom - to see 100%. I think this table can be divided by 2 for some reason (50 here means 100% in real, also evoscan logging throttle position from cca 52% to 100% , not from 0%)? Using "throttle opening scalling" , axis are uknown for me of course.


Just before it is there some two 16bit tables, probably tps scalling, because are only 2D incremental... not needed for me i think?
If you are capable of reading code, so you can help me for what im looking for?

 

I didnt see any other tables 8bit tables, with zeroed first row/collumn and graduated to FF, than first table i tested (0x744f).

There are two small tables 7x10 at 0x4161 and 8x10 at 0x41af , which have zeroes, but from shape i think are for something another than trhrottle(but only comparing to know tables from colt and evox)

 

My experience tells me that maps shaped like this translate rpm x torque_request to target_throttle_position and are used either for ASC or for AT (CVT, SST, whatever). Outlander Turbo has neither and this map isn't used.

I have already submitted c72800xx xml description to Tactrix for public release 30 days ago.

 

Ok, i send you PM.

So may i dont mess with this 16bit table?

I need to know location + modify translation tables (low/mid/high gear = 3 tables?) you mentioned to "fix" throttle lag while driving, right?
Throttle tables from 39670060 - (Main/half limp/ full limp) are something other?

 

apps->target_throttle_position table won't affect transient throttle control. I guess the easiest way to get rid of "throttle lag" would be to zero out 4 bytes at 0x79e0.

 

Interesting, i dont ask(but i would like of course ) what these bytes doing. I will kill them tommorow. Thank you.

Manipulating "throttle 1/2/3/4/5 maps" in evoX for better response is just due lack of knowledge or due newer ecu code?

 

Both. and lack of better sense .

 

To complete this thread... it works thank for sharing your knowledge Rcus.

 

nice thread and thanks all for good throttle response.can you share stationary rev limit map.