aplicom A9

Hi,

Trying to get the above device to send in data. I can see the data being sent in the log file but nothing in the application gets picked up.

Log file content:

2017-06-27 13:17:41 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:18:11 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:18:30 DEBUG: [yyy: 12369 < xxx] HEX: 44c2014456350830bf001d00309f080000550063f800000000000000000000000000000000000000000001
2017-06-27 13:18:32 DEBUG: [yyy: 12369 < xxx] HEX: 44c2014456350830bf001d00309f6e0000550063fb00000000000000000000000000000000000000000002
2017-06-27 13:18:47 DEBUG: [yyy: 12369 < xxx] HEX: 44c2014456350830bf001d00309f0700005500640900000000000000000000000000000000000000000003
2017-06-27 13:19:17 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:19:47 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:20:17 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:20:32 DEBUG: [yyy: 12369 < xxx] HEX: 44c2014456350830bf001d00309f6e00005500647300000000000000000000000000000000000000000004
2017-06-27 13:21:02 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:21:32 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:22:02 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:22:32 DEBUG: [yyy: 12369 < xxx] HEX: 44c2014456350830bf001d00309f6e0000550064eb00000000000000000000000000000000000000000005
2017-06-27 13:23:02 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:23:32 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:24:02 DEBUG: [yyy: 12369 < xxx] HEX: 333536363132303234333136303935
2017-06-27 13:24:32 DEBUG: [yyy: 12369 < xxx] HEX: 44c2014456350830bf001d00309f6e00005500656300000000000000000000000000000000000000000006

Please advice!

Do you have protocol documentation for the device?

Its using the D protocol which I guess is the one implemented in Traccar?

You had a discussion a while back (https://www.traccar.org/forums/topic/aplicom/) and the tracker in question is the same as the one I am using.

I have checked the Aplicom D protocol and what your device sends doesn't match it.

Hmm.. That's wierd seeing that its an Aplicom unit configured with the Aplicom congigurator. I think there are multiple protocol versions. Let me try a few things and see if I can get it working.

Thanks for helping!

I think there is some device malfunction.

It seems that it could be related to the protocol implementation as in the configurator I am able to chose which parameters to send - when sending them all then the datapackage is read correctly. I can now see the unit as only but the coordinates are wrong somehow...

Examples:

2017-06-28 13:25:49 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 4482014456350830bf002b0700005500626100000000000000000000000000000000811bb80000000000000000000000000000000000
2017-06-28 13:25:49  INFO: [77D7BF3D] id: 356612024316095, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2017-06-28 13:25:49  INFO: [D4044EFD] connected
2017-06-28 13:25:49 DEBUG: [D4044EFD: 12369 < yyy] HEX: 504f5354202f20485454502f312e310d0a436f6e74656e742d4c656e6774683a203131380d0a557365722d4167656e743a2041392f3335363631323032343331363039350d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a486f73743a2037372e3234372e36372e3136323a31323336390d0a0d0a
2017-06-28 13:25:50 DEBUG: [D4044EFD: 12369 < yyy] HEX: 4465766963655f49643d33353636313230323433313630393526436f6e6669675f4e616d653d5454332b41392b5465737426436f6e6669675f56657273696f6e3d312e302e302e312653575f56657273696f6e3d322e31302e322651756572795f526561736f6e3d6576656e74494425323837253239
2017-06-28 13:26:19 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 333536363132303234333136303935
2017-06-28 13:26:37 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 4482014456350830bf002b6e00005500629300000000000000000000000000000000811bb80000000000000000000000000000000000
2017-06-28 13:27:07 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 333536363132303234333136303935
2017-06-28 13:27:37 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 333536363132303234333136303935
2017-06-28 13:28:07 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 333536363132303234333136303935
2017-06-28 13:28:37 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 4482014456350830bf002b6e00005500630b00000000000000000000000000000000811bb80000000000000000000000000000000000
2017-06-28 13:29:07 DEBUG: [77D7BF3D: 12369 < yyy] HEX: 333536363132303234333136303935

I still think it's a device malfunction. Every message should start with "44" (which "D" in ASCII), but as you can see, it's not the case for your device.

Hmm... Ok - I will try and investigate further. Thanks again!