Freematics Forum

After receiving my Freematics OBD2-UART and getting it running on a Mega I was unable to connect with my ISO 9141-2 OBD2 protocol vehicle (2001 Honda Insight). I should have seen this coming as the product page does specifically imply that the product does not fully support this protocol.
I'm getting somewhat close and I see a response to the 010C command running the obd2_uart_test example file in the OBDUART library. The code gets stuck in the obd.init() loop. I've tried other's suggestions without luck, below is my serial output for reference.

Searching this forum I found dozens of other customers with this exact issue. Clearly there is a demand for compatibility with this older OBD2 protocol however it became apparent that Freematics has no interest in supporting ISO 9141-2 vehicles which is disappointing. One of the reasons I went with Freematics over the ELM327 alternatives is that there is a great library and starter code made available. It's unfortunate that the developer refuses to spend time to support their existing products. Maybe Freematics will someday fully support ISO 9141-2, but for now us ISO folks are fresh out of luck

--Serial out data--
Freematics OBD-II Adapter Ver. 1.1
Sending ATZ

ELM327 v1.5
>
Sending ATI

OBD2USART V1.1
>
Sending ATH0

OK
>
Sending ATRV

12.05V
>
Sending 0100

NO DATA
>
Sending 010C

41 0C 00 00
>
Sending 0902

NO DATA
>

MEMS:Yes
Init...
Init...
Init...
Init...
Init...

Since you already get a response from 010C, you can try bypassing checking result of init(). Let me know if this works for you.

I just made a minor change to OBD2UART library so init() still return true when PID maps cannot be loaded. Please update and try.