hi,

i have an Argentine 408 (AEE2004.full) without TPMS and i would like to add a computer to it that acts as an indirect TPMS.

inputs

• individual wheel speeds (from ABS and stabilization sensors - required)
• break pedal (optional)
• steering wheel position, heading, gyroscope rate (optional)
• GPS info (optional)

relative tire inflation can be inferred from the relative speeds of the wheels alone. underinflation of only some wheels can always be detected this way. break info can optionally be used to help halt calculations when breaking to allow for skidding (but wheel locking/skidding can be inferred by sudden high rotational acceleration alone). steering wheel/heading/gyro rate can optionally be included in the calculations to compensate for the expected difference in wheel speeds when turning (but turning can be inferred from wheel speed alone too). GPS info can optionally be included to detect simultaneous underinflation of all wheels.

outputs

• audible alert: a speaker can be trivially added
• dashboard alert: AEE2004.full/LS.CONF/168 can be used to force display of underinflation/puncture alerts (but without particular wheel indication).
• entertainment unit display: can display individual tire pressures, when configured appropriately.

questions

1. the main question is: do you know how to obtain separate wheel speeds from the buses? it seems it can be done according to this, but i don't know the format of the downloadable binary config (.REF) files. i suppose wheel speeds are reported on the
   HS.IS bus, but using which message(s)?
2. it is enough to trigger the TPMS dashboard alarm, but it would be nice to also be able to report inferred tire pressures for each wheel via the entertainment unit display. any idea of the involved messages?

thank you very much for your help.

This one is probably the most complex format that is still needed in DBMUXE, the KWP2K/UDS diagnostics data.

This covers:

• Read/write data by ID
• DTCs
• I/O by ID
• Other things?

DBMUXE yaml definition doesn't exist yet for VAN frames, TODO.

DBMUXE definition doesn't exist yet for ISOTP/CAN-TP/"multi frame" data, this is used for some EMF/RADIO frames

hi,

given the data in this table, it looks like the format of 0x60F as a bit string is as follows:

00 PFL(Pressure Front Left) PFR PRL PRR 111111 00 DFL(Deflation Front Left) DFR DRL DRR 111111

Pxx and Dxx are 6-bit integer values expressed in decibar. note that 35 PSI ≃ 24.13165 dbar.

Pxx is the current pressure (possibly corrected for wheel temperature), and Dxx is the current difference from some maximum value observed earlier.

thanks.

To browse and view the data, it would be very useful to have a web-app available that parses the yml files.

Unfortunately, i don't have any (front) web dev experience, so this is a todo (until i learn vuejs or somebody help on it) issue.