Response seems to be OK
in both cases, so I think there is some problem with the device.
I'm going to test on another platform to see what happens. By sms works correctly.
Anton,
I decoded the HEX so you can see if anything is wrong.
Engine Stop sent
*HQ,865205031071243,S20,030155,1,3,10,3,5,5,3,5,3,5,3,5#
Engine Resume sent
*HQ,865205031071243,S20,030752,0,0#
2018-09-29 00:01:55 INFO: [7f71434d] id: 865205031071243, command type: engineStop sent
2018-09-29 00:01:55 DEBUG: [7f71434d: 5013 > 200.178.248.108] HEX: 2a48512c3836353230353033313037313234332c5332302c3033303135352c312c332c31302c332c352c352c332c352c332c352c332c3523
2018-09-29 00:01:56 DEBUG: [7f71434d: 5013 < 200.178.248.108] HEX: 2a48512c3836353230353033313037313234332c56342c5332302c4f4b2c3033303135352c3033303135352c412c323032372e33303737332c532c3034323339
2018-09-29 00:01:56 DEBUG: [7f71434d: 5013 < 200.178.248.108] HEX: 2e39373334352c572c302e30302c302c3239303931382c4646464546424646230d0a
2018-09-29 00:01:56 INFO: [7f71434d] id: 865205031071243, time: 2018-09-29 00:01:55, lat: -20.45513, lon: -42.66622, course: 0.0, result: S20,OK,030155
2018-09-29 00:03:57 DEBUG: [7f71434d: 5013 < 200.178.248.108] HEX: 2a48512c3836353230353033313037313234332c48544254230d0a
2018-09-29 00:05:57 DEBUG: [7f71434d: 5013 < 200.178.248.108] HEX: 2a48512c3836353230353033313037313234332c48544254230d0a
2018-09-29 00:07:52 INFO: [7f71434d] id: 865205031071243, command type: engineResume sent
2018-09-29 00:07:52 DEBUG: [7f71434d: 5013 > 200.178.248.108] HEX: 2a48512c3836353230353033313037313234332c5332302c3033303735322c302c3023
2018-09-29 00:07:54 DEBUG: [7f71434d: 5013 < 200.178.248.108] HEX: 2a48512c3836353230353033313037313234332c56342c5332302c4f4b2c3033303735322c3033303735322c412c323032372e33303737332c532c30343233392e39373334352c572c302e30302c302c3239303931382c4646464546424646230d0a
2018-09-29 00:07:54 INFO: [7f71434d] id: 865205031071243, time: 2018-09-29 00:07:52, lat: -20.45513, lon: -42.66622, course: 0.0, result: S20,OK,030752
You need to ask your device vendor if the format is correct.
Link
Look at this part of the document and compare it with the previous part that I sent.
For Example (Disable Fuel Command):
Command: *HQ,865205030330012,S20,130305,1,1#
Reply: *HQ,865205030330012,V4,S20,DONE,130305,050316,A,2212.8745,N,11346.6574,E,14.28,028,220902,F7FFFBFF#
For Example (Enable fuel Command):
Comamnd: *HQ,865205030330012,S20,130305,1,0#
Reply: *HQ,865205030330012,V4,S20,OK,130305,050316,A,2212.87450,N,11346.65740,E,14.28,028,220902,F7FFFBFF#
Anton, you can add this document to the traccar database for "Cantrack " devices. (H02)
I sent a custom command and it worked correctly. Does the time in the command influence anything?
Added protocol document.
Hi Jean,
I'm using ST-901 device works on H02 protocol, but I'm unable to figure out the commands format. I have been given 2-3 different protocol guides by the vendor, but none of them are clear. Can you help me by sharing a few commands which can be set from the Traccar web commands section?
Possibly if you can share a commands guide. I know ST-901 doesn't support engine start/stop, but I have another model on h02 which has a relay and will accept engine start/stop cmds. Even other commands will be quite worthwhile.
Nick, traccar has a doc database: Link
The vendor of my device sent me a document and it's on the page with name: h02_cantrack_secumore.pdf.
Thanks Jean,
I will check if the commands in this guide are compatible with my devices.
yo tengo secumore g900 pero no me funciona, que comando debo enviar gracias //I have secumore g900 but it doesn't work for me, what command should I send thanks
How Can I get the status of the engine stop/resume in Api Response which will be stored in the Database too as a record ???
I have a G05 tracker secumore. Can someone help me?