The only thing missing there are the conversion formulas, but I have most of them. I have a DBC-File with all the signals, factors, offsets, units and etc, but there no can messages... so what I'm doing right now is creating the CAN messages and adding proper signals to the messages.
Check this:
grafik.png (17.49 KiB) Viewed 8261 times
And this, this is CAN-ID 0x0B5:
grafik.png (27.99 KiB) Viewed 8261 times
0x0B5 is fully decoded. I will update the DBC-File in my github and description.
PS: INPA did not connect to TCU via RE as man-in-the-middle, some extra messages would need to be relayed to get that working I guess. Hopefully that would not be not hard to figure out - I would just need to see what new CAN packets appear on the bus when INPA is active.
BMW F-series are using diagnostic over ethernet, and not k-line like out E-Series.
I've just looked in my log files, I don't have 0x612 or 0x618 there. It really seems to have something to do with the diagnostics.The 0x6xx number range is for "services", it starts at 0x580.
BMW F-series are using diagnostic over ethernet, and not k-line like out E-Series.
E-Series ECU and TCU diagnostics seems to be CAN, it's gateway which does k-line translation. Might be similar story with F-series not that we care for our purposes at this point.
Need to relay kick-down flag because I think I've lost kick-down without it Open issue - no "R/P/N" messages only see packets for forward gears for whatever reason.