Traccar 3.15 - Result command

Jose B7 years ago

Hello Anton,

Today I sent some custom command to some tracker and it was ok (“Command has been sent").

I would like to know where it is stored the "Command Result".

I tried find in anywhere inside on web UI ( reports, ecc) , but I did not find.

Is it works on Traccar 3.15, isn´t? Could you help me?

Regards

JB

Veerendra7 years ago

Hi @Jose B
Command Result are stored in events. It will give notification if you have selected for notification in notification list.

Jose B7 years ago

Hi Veerendra, thank you for feedback!

So, I already have selected in notification (ALL, web and email flags) but I never received nothing especific of return command.
As well as, I search on reports and it does not have any data stored of it -always empty.

For this is my question.

JB

Veerendra7 years ago

Then you check traccar logs.
I tried to send custom command and got result.( I edited id)

2018-03-22 03:48:29  INFO: [5F88450D] id: 888888888888888, command type: custom sent
2018-03-22 03:48:29 DEBUG: [5F88450D: 5023 > 42.111.26.199] HEX: 787813800d000000002336363636234f46230000a7e50d0a
2018-03-22 03:48:42 DEBUG: [5F88450D: 5023 < 42.111.26.199] HEX: 7878181510000000002336363636234f46232d4f4b000203d083010d0a
2018-03-22 03:48:42 DEBUG: [5F88450D: 5023 > 42.111.26.199] HEX: 7878051503d0d2440d0a
2018-03-22 03:48:43  INFO: [5F88450D] id: 888888888888888, time: 2018-03-22 03:47:39, lat: 28.62200, lon: 77.37627, speed: 0.0, course: 192.0, result:    #6666#OF#-OK
2018-03-22 03:48:51 DEBUG: [5F88450D: 5023 < 42.111.26.199] HEX: 78780a13440604000203d141310d0a
2018-03-22 03:48:51 DEBUG: [5F88450D: 5023 > 42.111.26.199] HEX: 7878051303d115140d0a
2018-03-22 03:48:51  INFO: [5F88450D] id: 888888888888888, time: 2018-03-22 03:47:39, lat: 28.62200, lon: 77.37627, speed: 0.0, course: 192.0
2018-03-22 03:49:33  INFO: [5F88450D] id: 888888888888888, command type: custom sent
2018-03-22 03:49:33 DEBUG: [5F88450D: 5023 > 42.111.26.199] HEX: 787813800d000000002336363636234346230000d0d50d0a
2018-03-22 03:49:41 DEBUG: [5F88450D: 5023 < 42.111.26.199] HEX: 7878181510000000002336363636234346232d4f4b000203d279a60d0a
2018-03-22 03:49:41 DEBUG: [5F88450D: 5023 > 42.111.26.199] HEX: 7878051503d2f1560d0a
2018-03-22 03:49:41  INFO: [5F88450D] id: 888888888888888, time: 2018-03-22 03:47:39, lat: 28.62200, lon: 77.37627, speed: 0.0, course: 192.0, result:    #6666#CF#-OK
Turbovix7 years ago

Hi Veerendra, Did you use the tool to decode the HEX information contained in your log file?

https://www.traccar.org/hex-decoder/

Veerendra7 years ago

Hi Turbovix,

This is traccar log file without any changes other than id. No hex-decoder is used.

Turbovix7 years ago

So it looks like your device is not properly configured or is not sending the correct information to the Traccar server.
Is the configured port the port for the protocol used by the machine?

Veerendra7 years ago

Device is sending information as per device manual.and working fine with traccar server.