So far im come to this


KrsZG_DNZielMaxNRegEin_ko
Maximalwert fuer Zieldrehzahldifferenz, ab dem der Wunschdrehzahlregler aktiviert wird
Maximum value for target speed difference from which the desired speed controller is activated
val 0
?

KrsZG_GangMax_ko[Tip]
Zielgang unterhalb dem, keine ZG-Schaltungen mehr im Tiptronic-Betrieb mцglich sind
Target gear below which ZG shifts are no longer possible in Tiptronic mode
val 1
*seems ok if translated properly


KrsZG_FpMax_kf
max. Fahrpedalwinkel i.A. Letztgang und Synchrondrehzahl fьr Freigabe einer ZG-Schaltung
Max. accelerator pedal angle i.A. last gear and synchronous speed for release of a ZG circuit
val 40
*seems ok for me

KrsZG_MMotMax_kf
max. Motormomet i.A. Letztgang und Synchrondrehzahl fьr Freigabe einer ZG-Schaltung
Max. engine torque i.A. last gear and synchronous speed for enabling a ZG circuit
val ~170
*also seems ok

KrsZG_MAbbruchZuschiessen_ko
max. Moment auf Gehender beim Abbruch des Zuschiessens bei einer ZG-Schaltung
Max. moment of walking when aborting closing with a ZG circuit
val -100
*idk what is it

Bringing this tread back. I have a 022906032KR that I am trying to control rev-matching on.  I am sending messages over 0X540 per below.

540[0] = activate Zwischengas
540[3] = Define sync RPM
540[4] = Define inverse sync RPM
540[5] = Define sync time in ms

I haven't been able to control RPM using these controls and am sure I'm missing something.  The documents I have don't really go into all of the qualifiers for enabling this. Does anyone have any additional info they could share. Thanks in advance.

Hi,

is anyone else interested in trying to figure out a way to make this work?

I'm revisiting my project and have begun emulating signals to the gearbox. I'm emulating these, maybe not all required but the TCU now sends a ZG request to the engine to action.

ZG EMUL — 0x280 CAN A→B:

D2 miistc — actual indicated torque %, rises 80ms, holds 120ms, decays 80ms, peak = 0.047×RPM+4Nm
D5 mifab — base torque, peak = miistc×0.55
D8 mivbeg — driver demand torque, peak = miistc×0.85
D1 bit6 B_stgek — ECU-TCU coordination active, set +12ms after paddle trigger

ZG EMUL — 0x380 CAN A→B:

D8 wdkba_TCU — throttle angle for MED9.1 TCU, D3 permanently mirrored + ZG blip on top

MOMINTEREST — 0x488 CAN A→B:

D4 — config byte forced constant 0x7C
D5 — config byte forced constant 0xA6
D6 mominterest — motor intervention availability 0xFF=100%, profile-controlled ramp during overrun ZG shift
D7 bz_mot6 — OBD multiplex: code 0=load, 1=throttle, 2=coolant 85°C, 3=abs load, 4=pedal, 5-15=0xFF
D8 — dual nibble counter, high nibble 0-F, low nibble alternates 0x0/0x4

the result of this emulation so far is rather than a delay from paddle press to a lethargic shub shift maybe 1s after with a slow ramp up I now have an immediate clutch drop, engine speed drops before ending ultimately in a schub shift.

with the emulation to the gearbox, it now sends me 0x540 D1 bit3 — B_zges high rather than never sending as it did before emulation. I have noticed that if i press for a downshift then quickly stab the throttle, the shift completes quite quickly, if i don't add tht throttle it continues to the schub shift after a delay.

if we assume I have to keep my emulator between main canbus and the TCU, is there any easier way to add a throttle blip % versus engine rpm for the duration that the pin is high or pulled low. just thinking out loud.

is there a more rudimentry way this emulation can be added to the calibration, rather than implementing the full VAG strategy. I don't think i yet have the skills for this hence asking here.

Yes, nsyw request is there b_zges goes high too and tsyn time is sent.

I have attached a log from my car, it is labelled and sorted to be easily viewed in ecuxplot. Will need sample on X axis and filter turned off.

Unfortunately I do not have the skills to patch something in the ECU to get it to respond for downshift blip, but maybe having my man in the middle makes for a bit less work in the ECU patching? it's bidirectional so the ECU should be able to see those requests, but obviously doesn't act upon it.

I have found if I initiate the shift then quickly push the throttle pedal myself it helps the shift complete quickly. As soon as I initiate the shift you can feel the clutch drop.

I logged a native dsg med9.1 tfsi car and made the controller mimic its actions during the downshift, all but actually opening the throttle as no SY_ASG

06A906032TL is manual VW polo isn’t it, I have flash and eeprom if you need. I have A2L available for this version too. I’m keen to try and solve this but not sure which way to go about it

I’m running 06A906032HF at the moment,

Here's 06A906032TF Hex and a2l. In A2L shows SY_ASG = 0

I assume that means it will not respond to sync request, but i do see a lot of nsys related stuff in the A2L