Current version of the OpenAuto Pro is 12
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OBDLink SX USB no data
#1
Brick 
Hi Daniel,

I am not getting obd2 data on the gauges. I am connected to an OBDlink SX USB at /dev/ttyUSB0 and have successfully tested AT commands at the command line.

The openauto.log seems to show that it is connected. the last entry is ATZ but does not show subsequent AT commands, I don't know if it should.

[2020-08-16 09:25:25.128396] [0xb0a60010] [debug]  [OpenAuto] [ObdManager] start.
[2020-08-16 09:25:30.128714] [0x97c3a140] [debug]  [OpenAuto] [ObdManager] device is not active. Trying open.
[2020-08-16 09:25:30.140315] [0x97c3a140] [info]    [OpenAuto] [ObdSerialTransport] open result: true
[2020-08-16 09:25:30.140369] [0x97c3a140] [info]    [OpenAuto] [ObdDevice] initializing.
[2020-08-16 09:25:30.140409] [0x97c3a140] [debug]  [OpenAuto] [ObdDevice] executing init command: ATZ


My system.ini looks like this:

[Obd]
ObdAdapterStartupSequence=ATZ;ATE0;ATS0;ATL0;ATH0;ATSP0
ObdAdapterDescriptor=/dev/ttyUSB0
ObdAdapterBaudrate=115200
ObdProbePeriod=5
ObdDeviceType=1
ObdAdapterRfCommAddress=
ObdAdapterRfCommChannel=1
ObdMaxNoDataResponseCount=100


Any ideas?
Thanks!
Reply
#2
Looks like your adapter does not respond to the ATZ (reset) command. Did you select correct baudrate?

Edit: Is this adapter ELM327 based (or compatible)? We did not find such information on manufacturer site.
Reply
#3
It does appear to never receive a response.
To confirm, this is the adapter: https://www.scantool.net/obdlink-sx.
It does respond to all commands from the command line, using cu -l /dev/ttyUSB0. It is elm327-compatible and has a default baud rate of 115200. I don't think it is a protocol issue because the same adapter worked with different android apps previous to trying with openauto.

I tried a scantool obdlink mx+ bluetooth adapter and it works fine with openauto, so I'll use it until I recall why I switched to the USB version, I think it was not powering down and killing the battery.
Reply
#4
I am still trying to connect a usb obd scanner without success. I have a different one to try but same result:

pi@e:~ $ grep Obd /home/pi/.openauto/cache/openauto.log
[2020-09-24 14:29:31.378772] [0xb0ac1010] [debug] [OpenAuto] [ObdManager] start.
[2020-09-24 14:29:36.383233] [0x97c3a140] [debug] [OpenAuto] [ObdManager] device is not active. Trying open.
[2020-09-24 14:29:36.395526] [0x97c3a140] [info] [OpenAuto] [ObdSerialTransport] open result: true
[2020-09-24 14:29:36.395629] [0x97c3a140] [info] [OpenAuto] [ObdDevice] initializing, sequence: ATZ;ATE0;ATS0;ATL0;ATH0;ATSP0
pi@e:~ $

And that is the last log entry grepping "Obd". Everything else is working fine.
I have tried both adapters at baud rates 115200, 38400 and 9600.
Is anyone successfully using a usb obd scanner? Can you look in your log for what Obd* entries come after the initialization sequence?

Thank you

I looked at my log for what happens when the Bluetooth adapter succesfully connects...

[2020-09-24 15:21:47.443097] [0x97c3a140] [info] [OpenAuto] [ObdDevice] initializing, sequence: ATZ;ATE0;ATS0;ATL0;ATH0;ATSP0
[2020-09-24 15:44:56.304832] [0x97c3a140] [debug] [OpenAuto] [ObdDevice] initialization done
[2020-09-24 15:45:01.152426] [0x97c3a140] [info] [OpenAuto] [ObdDevice] query available pids result: SEARCHING...4100BFBEB993
[2020-09-24 15:45:01.152617] [0x97c3a140] [info] [OpenAuto] [ObdDevice] activated.
[2020-09-24 15:45:01.152669] [0x97c3a140] [info] [OpenAuto] [ObdManager] device opened.

It does appear that the USB adapters are not initializing. The AT commands all look valid.
So, same question. Is anyone else using a USB adapter successfully?
Reply
#5
(09-24-2020, 09:54 PM)taisau Wrote: I am still trying to connect a usb obd scanner without success. I have a different one to try but same result:

pi@e:~ $ grep Obd /home/pi/.openauto/cache/openauto.log
[2020-09-24 14:29:31.378772] [0xb0ac1010] [debug]  [OpenAuto] [ObdManager] start.
[2020-09-24 14:29:36.383233] [0x97c3a140] [debug]  [OpenAuto] [ObdManager] device is not active. Trying open.
[2020-09-24 14:29:36.395526] [0x97c3a140] [info]    [OpenAuto] [ObdSerialTransport] open result: true
[2020-09-24 14:29:36.395629] [0x97c3a140] [info]    [OpenAuto] [ObdDevice] initializing, sequence: ATZ;ATE0;ATS0;ATL0;ATH0;ATSP0
pi@e:~ $

And that is the last log entry grepping "Obd". Everything else is working fine.
I have tried both adapters at baud rates 115200, 38400 and 9600.
Is anyone successfully using a usb obd scanner? Can you look in your log for what Obd* entries come after the initialization sequence?

Thank you

I looked at my log for what happens when the Bluetooth adapter succesfully connects...

[2020-09-24 15:21:47.443097] [0x97c3a140] [info]    [OpenAuto] [ObdDevice] initializing, sequence: ATZ;ATE0;ATS0;ATL0;ATH0;ATSP0
[2020-09-24 15:44:56.304832] [0x97c3a140] [debug]  [OpenAuto] [ObdDevice] initialization done
[2020-09-24 15:45:01.152426] [0x97c3a140] [info]    [OpenAuto] [ObdDevice] query available pids result: SEARCHING...4100BFBEB993
[2020-09-24 15:45:01.152617] [0x97c3a140] [info]    [OpenAuto] [ObdDevice] activated.
[2020-09-24 15:45:01.152669] [0x97c3a140] [info]    [OpenAuto] [ObdManager] device opened.

It does appear that the USB adapters are not initializing. The AT commands all look valid.
So, same question. Is anyone else using a USB adapter successfully?

You could try to hook it up to a powered USB hub?
Reply
#6
Thanks for the thought, jennmike2, it has been on a powerd hub.
OAP opens the USB adapter, sends the AT codes, then the next thing from OAP should be "initialization done".
One thing I see is the first time I tried this, OAP seemed to only send the first command, ATZ, then stopped. It is now sending the entire string of commands. Does OAP wait for a response for each AT command? I'm not familiar enough to know what to try next, so I'll just keep using the Bluetooth adapter. The reason I wanted to use USB was because my first Bluetooth adapter did indeed not turn off on its own and would drain the battery, but a newer one, the obdlink MX+ has not done that so far.
Reply
#7
(09-25-2020, 03:47 AM)taisau Wrote: Thanks for the thought, jennmike2, it has been on a powerd hub.
OAP opens the USB adapter, sends the AT codes, then the next thing from OAP should be "initialization done".
One thing I see is the first time I tried this, OAP seemed to only send the first command, ATZ, then stopped. It is now sending the entire string of commands. Does OAP wait for a response for each AT command? I'm not familiar enough to know what to try next, so I'll just keep using the Bluetooth adapter. The reason I wanted to use USB was because my first Bluetooth adapter did indeed not turn off on its own and would drain the battery, but a newer one, the obdlink MX+ has not done that so far.
We did not find any information about compatibility with ELM327. Are you sure it is compatible and support all set of AT commands of ELM327? There is no info on manufacturer web page https://www.obdlink.com/sxusb/
Reply
#8
Obdlink is a brand of Scantool, which has made their own series of elm327-compatible chips:
quote: STN1110 is a multiprotocol OBD to UART interpreter ("OBD chip") that supports all OBD-II protocols, and is fully compatible with the ELM327 command set, while outperforming the original ELM327 IC in every category: stability, performance, features, and price.

According to https://www.scantool.net/downloads/98/stn1100-frpm.pdf,
the SX (USB) uses a STN1130 chip.
The MX+ (Bluetooth), which works fine, uses a latest and greatest STN2255 chip.

But they all are said to be fully elm327-compatible, that is their intended use.
As noted above, I am getting a similar result using this non-Obdlink adapter: https://www.amazon.com/gp/product/B07MNX424C

BlueWave, can you share the exact model of USB adapter that was used for testing? They are cheap enough that I can see if I can get it to work.
Reply
#9
We tested OBD-II with adapter similar to this https://www.amazon.com/Scanner-FORScan-A...465&sr=8-4 (at least case is the same).
Reply
#10
Thanks for sharing that. It is the same Forscan type I have tried also. I understand there are a multitude of ways the interfaces can not work, or even partially work because of all of the different car buses and protocols and ways adapters try to match up to some or all. Thank goodness for Amazon's return policy, I can try them all.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)