|
Title: Having the hardest time trying to accomplish something very simple: Read RPMs Post by: psyko on February 03, 2025, 05:06:29 PM Hi there,
I have been banging my head about this one for days now, would appreciate any help. I have a 2020 BMW M340i (Bosch MG01 I believe...) which I am simply trying to read the RPM from through the OBD-II port. My setup is simple, I have a microcontroller or a computer hooked up to the ENET cable and I make a TCP connection to the ZGW (Port 6801 IP 169.254.84.119) and then send a UDS message for request by identifier. For example, if I want to get the VIN, I send: 00 00 00 05 00 01 f4 10 22 F1 90 (F1 90 being the VIN identifier) and the ZGW responds back with the correct data! However, when changing the identifier to anything else of value, like RPM... I get back a negative response with out of range error... I have no idea why. I even tried bench unlocking the DME and it's still giving the same error. I tried starting a diagnostic session before requesting the RPM but still I get the same error. I have a software doc (in german) for the ECU which says the RPM is at 58 0C, but I have seen online that it should also be at F4 0C... I have tried so many identifiers but cannot seem to get/find RPM. This should be really easy, but I am stuck... any tips please? Thank you!! Title: Re: Having the hardest time trying to accomplish something very simple: Read RPMs Post by: jcsbanks on February 04, 2025, 03:34:46 AM Is 0x10 the correct address for the DME on this platform? It is years since I touched BMWs and I only briefly looked at HSFZ on early F series ECU/gateway on the bench.
Title: Re: Having the hardest time trying to accomplish something very simple: Read RPMs Post by: prj on February 04, 2025, 05:19:30 AM Is 0x10 the correct address for the DME on this platform? It is years since I touched BMWs and I only briefly looked at HSFZ on early F series ECU/gateway on the bench. Nah. 0x12 master, 0x13 slave on UDS. Title: Re: Having the hardest time trying to accomplish something very simple: Read RPMs Post by: psyko on February 04, 2025, 09:54:08 AM I knew you guys could help, thank you!! It was simply the wrong ECU ID... 0x10 replaced by 0x12 fixed it... man ;D ;D
|