OBD AT Init commands

[unnormal]

I have a JDM Toyota ECU from the early 2000's that doesn't exactly conform to the OBD2 standard. From what I can tell it uses a form of ISO 14230-4 KWP. Using the Torque OBD App I can successfully communicate to the ECU over BT by adding the following INIT commands:

ATIB 96 \n ATIIA 13 \n ATSH8113F1 \n ATSP A4 \n ATSW00

Ref: http://torque-bhp.com/wiki/Custom_Init

This basically changes the Baud rate to 9600, set the ISO Init Address to 13, sets the Header t 81 13 F1, sets OBD protocol to 4 (ISO 14230-4 KWP), and stops the wakeup interval.

Is there any way to add these AT codes to HLT for android? OR otherwise configure these settings?
I noticed you added an initialization option in the sensors list but it is asking for ASCII.

Thanks

[Harry]

The initialisation option is the only place to add something like your custom initialisation. The problem will be it is sent to the adapter before starting the standard sequence - which has an ATZ in the beginning. This in turn will probably reset some of the values you configure. But please try. Not sure you can enter newlines, so you may use the combined form of AT commands (something like ATIB 96 IIA 13 ATSH...).

The ATSPA command can be set in LapTimer's Expert Setting (OBD Tweaks, Protocol selection).

To see if your command is well formed and accepted by the adapter, you may want to log the OBD communication following the description in viewtopic.php?f=39&t=1500

The initialisation stuff is a generic feature for all sensors not used a lot. In case you go deeper into ELM communication, you may check if ATZ and ATWS both reset the configuration or if ATZ is doing this only. I may skip the ATZ command in a future update in case an initialisation sequence is given...

- Harry

[unnormal]

If I want to try adding initialization code under the sensors section, do I enter it just as text with spaces (ex. ATIB96 IIA13 SH8113F1 SW00) or does it need to be converted to ASCII with spaces (ex. 065 084 073 066 057 054 032 073 073 065 049 051 032 083 072 056 049 049 051 070 049 032 083 087 048 048) for HLP to recognize it?

[Harry]

ASCII means plain text, not hex encoded text. So yes, enter ATI etc

[unnormal]

I tried entering the init code as:
ATIB96 IIA13 SH8113F1 SW00,

as: ATIB 96 \n ATIIA 13 \n ATSH8113F1 \n ATSP A4 \n ATSW00,

and also as:
ATIB 96
ATIIA 13
ATSH8113F1
ATSP A4
ATSW00,
but no luck.

I sent you the log file and screen shot if you have any ideas.
Thanks

[Harry]

Hi,

I have tested the AT syntax using a OBDLink MX today, I have checked the reset behaviour of the ATZ command in addition.

1) AT commands cannot be combined as I thought. While modems usually support it, the ELM standard does not. This means instead of ATIB96IIA13... one really needs to add them line by line with carriage returns in-between.
2) ATZ is defined as "This command causes the chip to perform a complete reset as if power were cycled off and then on again. All settings are returned to their default values, and the chip will be put into the idle state, waiting for characters on the RS232 bus." This in turn means any initialisation entered will be superseded by the following ATZ command.

2) is the deal breaker currently, I need to find a different initialisation approach for ELM interpreters here. What happens is that LapTimer send the custom initialisation first, issues an ATZ, and issues its own AT initialisation afterwards before going into the "working" mode requesting PIDs. I need to switch this to issue ATZ first, continue with LapTimer's own AT initialisation, and add the custom information next. I plan to fully focus on several sensor topics in September and have added this change to the list.

- Harry

[unnormal]

Understood.

Thank you for looking into this and adding it to the request list. I look forward to trying a new release when you have time to work on it. Let me know if there is anything I can provide to help.

Cheers,
Adam