GCU allows using full auto mode. It means that GCU will use values from tables to determine when to execute up-shifts and downshifts.
- Auto mode activation :
- Setup inputs and assign them in IO Assignments (Shift + A) to Shifter and transition map like in example below
Second photo presents Shifter assignments if preset is selected – objects are assigned automatically. - Compose Available mode transitions table in a way to engage auto (DRIVE) mode in preferred way.
- Setup inputs and assign them in IO Assignments (Shift + A) to Shifter and transition map like in example below
- Auto mode tables setup :
- it is possible to define custom axis of the tables for auto mode in GCU -> General Settings.
- Custom input – allows picking up any GCU input (f. eg. external TRQ signal)
- Current gear
- Temperature
- Engine torque – GCU calculated torque (to use external source of TRQ select custom input)
- Calculated VSS – GCU calculated speed
- Engine acceleration – rate of engine RPM increase or decrease
- Engine RPM: simplest method. Example values below :WARNING: this method is UNUSABLE in TCC transmissions in scenarios that lockup is disengaged as engine RPM does not reflect vehicle speed directly.
- VEHICLE SPEED – CALCULATED : -preferred method.
HINT: undriven wheels speed sensors are preferred to avoid auto-upshifts/downshift at wheel speed / lock - VEHICLE SPEED – RAW inputs
- VEHICLE SPEED – CALCULATED : -preferred method.
- Two sets of tables: GCU has 2 sets of auto mode tables that can be suite to user needs freely. Example sets :
- Normal / Sport mode – just normal switch for different mood 😉
- Deceleration rate – depending on how quickly car decelerates / brake strength. While auto-upshift point is easily adjustable according to driver’s wish via PPS (accelerator pedal position sensor) – higher PPS values result in higher RPM shift points, at the same time downshift needs additional input so it can be tuned properly – braking pressure or vehicle deceleration rate (GCU calculated deceleration rate coming in near updates) – higher brake pressures should trigger downshifts sooner (higher trigger RPM). Idea is to create #1 table for normal, slow driving scenario and #2 for full braking scenario.
- TCC on / off – one for drive modes with TCC engaged or permanently off.
- Table sets blending: GCU allows to blend sets of tables in user defined characteristics on user defined axis variable. — **ARTICLE TO COME**
- Delays:
- Defines how long in milliseconds value has to be in range specified in the table to shift the gear.
- it is possible to define custom axis of the tables for auto mode in GCU -> General Settings.
- auto-UPshift schedule
Defines above what value at current gear UP-shift is triggered. - auto-DOWNshift schedule
Defines below what value at current gear DOWN-shift is triggered.