Undocumented AT functions

[jonathan]

I've written a python library to control the emulator, but after examining the source for the shipped control program, there are a few things I don't understand, specifically what ATINF0 does, and what ATSET 0101=0x00,0x07,0xff,0x00 (aka pushReadiness()) does.

Found device /dev/ttyUSB1
S> ATE0
R> OK
S> ATINF0
R> OK
S> ATACC1
R> OK
S> ATSET 0101=0x00,0x07,0xff,0x00
R> OK
S> ATCLR DTC
R> OK
S> ATVIN1
R> OK
S> ATSET VIN=44444444444444444
R> OK
S> ATSET 010C=256
R> OK
S> ATGET 010C
R> 010C=04 00
1024

[sagar0810]

Hi Jonathan,

Can you share some detail about your library. I have tried to browse about writing script for AT command but not able to figure out proper tutorial. Do you have any reference link where i can read and write script which will execute AT commands on emulator.
I don't have any background on Serial Command Interface.

Thank you.

[jonathan]

You can view my library here: https://github.com/JonnoFTW/py-obd-ii-emulator

The Emulator AT Commands are listed in full here: http://freematics.com/pages/products/fr ... mmand-set/

[sagar0810]

Thanks Jonathan for your response.
I have a query. When we trigger Ignition off from emulator and trigger Ignition On again then dongle are not able to receive Ignition On event. We need to power cycle dongle to trigger Ignition ON event, have you faced similar problem or for you ignition on/off event are working fine without emulator power cycle.

Thanks in advance.

[jonathan]

Setting ignition off and then on again within the same power cycle of the emulator worked for me. Additionally, the freematics one logger stopped and started logging appropriately.