SECONS ELM327 device failing on ATS0 command

[systems27]

Greetings,
I'm a new user here and just got my OpenAuto Pro set up and running. The responsiveness of the interface is impressive. The OBDII functionality was the primary reason for getting the software but I'm having troubles getting it configured. So far I've narrowed it down to the ATS0 initialization sequence command. From the logs I see:

[2021-10-09 11:47:48.010160] [0x57cd2140] [info]    [OpenAuto] [ObdDevice] initializing, sequence: ATZ;ATE0;ATS0;ATL0;ATH0;ATSP0
[2021-10-09 11:47:48.015209] [0x57cd2140] [error]   [OpenAuto] [ObdDevice] read failed, data: ?
[2021-10-09 11:47:48.015317] [0x57cd2140] [info]    [OpenAuto] [ObdDevice] executing command: ATS0, response read failed

So I established a serial connection to the ELM-USB device to try each command one by one to observe the results, and it seems indeed the ATS0 command is not recognized:

>ATZ
ELM327/ELM-USB v1.0 (c) SECONS Ltd.
>ATS0
?
>

I used a baud rate of 115200, though I'm not sure that's important here. Looking at the ELM docs/spec information it seems that in version 1.3 the S0/S1 commands were added for disabling/enabling the printing of spaces. Since this is in the initialization sequence of the OBD module I assume the data processing requires the removal of spaces for the code to work as expected. Given I cannot change the device behavior is there any workaround within the OBD module of OpenAuto Pro to get things working? All the other initialization commands seemingly work/are recognized by my device. 

In case it is useful information the device I have is this one.


Thanks in advance for any constructive assistance.

[BlueWave]

According to the ELM327 doc https://www.elmelectronics.com/wp-conten...M327DS.pdf

AT S0, S1 Printing of spaces off, or on

Is your ELM327 adapter genuine one? ATSx command is part of the standard set which should be supported by any genuine ELM327 adapter. Try to remove this command from the startup sequence and check if that helps. Check this post https://www.bluewavestudio.io/community/...1#pid11931 for more details about editing startup sequence.

[systems27]

The manufacturer claims, "ELM-USB is ELM323/ELM327 compatible OBD-II diagnostic interface," but it doesn't seem they support full compliance, or not up to at least version 1.3. 

I tried removing the ATS0 command in the initialization sequence and now there's data showing for the gauges. I believe that resolves this specific issue. Appreciate the help.