Resolve J2534 WriteMsgs ret=9
Budget: $10 – $30 USD
I’m writing a Windows-based diagnostic tool in Python through the J2534 PassThru API. The interface is a Scanmatik 2 Pro and I drive it with the Python-OBD library. Connection is solid—the device enumerates correctly—but every call to WriteMsgs ends with the return code 9 and the UDS frame never leaves the buffer.
I’m looking for someone who truly understands the J2534 spec, Scanmatik firmware quirks and low-level UDS transport. Your task is to pinpoint why ret = 9 is triggered and guide me to a clean, repeatable fix. A short, commented code snippet or configuration tweak that lets a simple UDS request (e.g., 0x10 0x01) reach the ECU without error will be considered success. Remote debugging via screen-share is fine, and I can run any diagnostic utilities you recommend.
If you have solved similar issues with Scanmatik or other PassThru devices before, I’d like to get this resolved quickly so I can move on with the rest of the stack.
I’m looking for someone who truly understands the J2534 spec, Scanmatik firmware quirks and low-level UDS transport. Your task is to pinpoint why ret = 9 is triggered and guide me to a clean, repeatable fix. A short, commented code snippet or configuration tweak that lets a simple UDS request (e.g., 0x10 0x01) reach the ECU without error will be considered success. Remote debugging via screen-share is fine, and I can run any diagnostic utilities you recommend.
If you have solved similar issues with Scanmatik or other PassThru devices before, I’d like to get this resolved quickly so I can move on with the rest of the stack.