-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Freematics OBD-II UART Adapter V2.1 CANNOT Initialize! #70
Comments
It's because the code hasn't been updated in years. I've never gotten it to work and just use Tunerview. |
@mitchschaft Thank you for the timely reply! Could you link me to that library? |
@ALEEF02 According to the displayed messages your adapter itself works so far but it can't communicate with the car. |
@firepower2k11 My car uses the SAE J1850 VPW protocol, which I learned in an email thread with @stanleyhuangyc. Since then he has stopped replying to said emails. I was at first wondering if I could get a refund, at which he stopped replying. Now I am wondering if there is a hardware or software modification that can be made to the adapter so that it can use the SAE J1850 VPW protocol. I tried modifying the library by adding PROTO_SAE_VPW = 2 to the OBD_PROTOCOLS list, but that did not help. If you have any ideas for this, that would be wonderful. Thanks :D |
Hi, I spent over a month waiting for this item to arrive at my doorstep due to constant package delays. I am now extremely frustrated because I cannot get the OBD reader to initialize. I have double-checked all the connections and am trying to debug the reader and why
obd.init()
keeps failing. I am using a slightly modified version of the obd_uart_test, which just replaces the Serial outputs with screen output. Everything appears fine until the commands0100
,010C
, and0902
are sent. Those returnUNABLE TO CONNECT
. Mems afterwords still returnsYes
. From there on, I am stuck in a loop, waiting for the reader to initialize. I'm kinda lost here, so any and all help would be welcome. Thanks!The text was updated successfully, but these errors were encountered: