NefMoto

So the development of lookup functions for things like multi map switching and the launch controls etc. Got me to thinking if its possible to have functions dependent up on gear.

I am fairly certain the ECU has a gear change counter than monitors what gear the car is in. Would it be possible to have one of these tables look up a different LDRXN table to limit wheel spin or what ever you wanted the ecu to do?

I know this is beyond me and I have little use for it, but I find the concept interesting.

subbed.  this concept is long overdue.  major issue, not sure i know the solution:  how will the different maps potentially effect the PID?  will any of the PID maps theoretically need to have gear-specific tables?  this question is for you, but also directed at nye, prj, snowtrooper, rick, etc etc.

There is already a table that limits load by gear.

Theres a few ways to do this with stock code and tables.

Out of curiosity, is it enabled by default in the m-box?  I've always wondered why first gear always seems to have a lower requested load.

I just looked through the entire 'limitation for cylinder charge path' routine in the 'M box' and it does not restrict anything in 1st gear, in any gear in fact.

That isnt to say that some other routine outside of 'limitation for cylinder charge path' isnt.

Exactly, the entire function is basically disabled in the stock M box.

Load is lower in first gear due to physics, not anything in the ECU. There's basically not enough actual load on the motor to spool the turbos like there is in 2nd and up.

That I know, I just didn't know if there was component protection or torque management from the factory attempting to keep drivetrain components together.

gear identification maps:

NVQUOT1O - gear 1 over (rpm / km/h)
NVQUOT1U - gear 1 under(rpm / km/h)
NVQUOT2O - gear 2 over (rpm / km/h)
NVQUOT2U - gear 2 under(rpm / km/h)
NVQUOT3O - gear 3 over (rpm / km/h)
NVQUOT3U - gear 3 under(rpm / km/h)
NVQUOT4O - gear 4 over (rpm / km/h)
NVQUOT4U - gear 4 under(rpm / km/h)
NVQUOT5O - gear 5 over (rpm / km/h)
NVQUOT5U - gear 5 under(rpm / km/h)
NVQUOT6O - gear 6 over (rpm / km/h)
NVQUOT6U - gear 6 under(rpm / km/h)

IGESGA - gear mapping(1=1, 2=2 and so on.)


torque limit based on gears:

KFMDBGRG - rpm/gear (allowed torque%)

the KFMDBGRG map is active when engine temp is above TMMIBGR and vehicle speed is above VMIBGR.

i think there is also a CW or something to enable/disable the function entirely..

As i saw VMIBGR(318.75kh/h) and TMMIBGR (143.25Celsious) are way too high on 1.8T 20V, so this function its disabled from factory. Looks very promising.

Each NVQUOTxO/U map has four (y={0,3}) NVQUOTxO/U_y_A defines.

No codeword. Maps are FF'ed and mimax/mifafu multiplier is ~2 (M box)

Also there is MDBGRGA - always active (gangi only)

This function outputs mibgrl_w (iirc) which is considered in milsol_w (for KFMIRL) through a min function.

phila_dot: thanks for clarifying, as allways  :)

professor: please try not to use "1.8T 20V" as a generic term, as it refers to ~25-30ish or more different engines, where some of them have this function activated in the oem software..  :)

Man in theory that torque limit by gear could be used to really dial in launch control...

@sn00k
You are right of course  :). Allow me to add that on 032HN, 032MJ and 032RP values are as said before.

Interesting topic. All of the hidden/disabled functionality in certain versions of ME7 are intriguing.