G400 - Huabao Protocol Lock Status

We have a device that is using the Huabao protocol, which has basic functionality working with traccar.

However we are having issue detecting lock / unlock events of the device. It is a padlock / tracking device.

Protocol of device:

https://ufile.io/3g3jb

See lock Status Description section page 9.

Thanks.

Please provide HEX samples from your logs.

Here you go:

2017-12-14 10:10:27  INFO: [5E1D9575] connected
2017-12-14 10:10:29 DEBUG: [5E1D9575: 5015 < 46.11.240.113] HEX: 7e02000054093037612710000400000000000000010223aca000dc9dd800000000000017121417102933362a4d30302c34352c31313336393030383030313233303026303030303030303030303030263132333435363738393031323334353623f27e
2017-12-14 10:10:29  INFO: [5E1D9575] id: 093037612710, time: 2017-12-14 10:10:29, lat: 35.89238, lon: 14.45833, speed: 0.0, course: 0.0
2017-12-14 10:12:05 DEBUG: [5E1D9575: 5015 < 46.11.240.113] HEX: 7e02000044093037612710000500000000000000010223aca000dc9dd800000000000017121417120533262a4d30302c32392c313033363830433830303133393339263030303030303030303030302623a37e
2017-12-14 10:12:05  INFO: [5E1D9575] id: 093037612710, time: 2017-12-14 10:12:05, lat: 35.89238, lon: 14.45833, speed: 0.0, course: 0.0
2017-12-14 10:12:07 DEBUG: [5E1D9575: 5015 < 46.11.240.113] HEX: 7e02000044093037612710000600000000000000010223aca000dc9dd800000000000017121417120733262a4d30302c32392c303033363830313830303133393339263030303030303030303030302623d17e
2017-12-14 10:12:07  INFO: [5E1D9575] id: 093037612710, time: 2017-12-14 10:12:07, lat: 35.89238, lon: 14.45833, speed: 0.0, course: 0.0
2017-12-14 10:12:22 DEBUG: [5E1D9575: 5015 < 46.11.240.113] HEX: 7e02000054093037612710000700000000000000010223aca000dc9dd800000000000017121417122133362a4d30302c34352c31313336393042383030313233303026303030303030303030303030263132333435363738393031323334353623897e
2017-12-14 10:12:22  INFO: [5E1D9575] id: 093037612710, time: 2017-12-14 10:12:21, lat: 35.89238, lon: 14.45833, speed: 0.0, course: 0.0

I have checked source code and it looks like Traccar only supports basic location data for Huabao protocol at the moment. If you need help with implementing additional parameters please send and email to support address to discuss it.

Thanks, I sent an email to support regarding the implementation of additional parameters.

However back to the basic location data... if you have a look at table 4, you can see bits 9 and 10 of the Alert Identifier, indicate alarms for Seal / Unseal operations. All this is part of the basic location data.

Could you kindly check if this is implemented and working as expected?

Thanks

Basic location data is what you get from GPS module (e.g. time, coordinates, speed etc). Anything else is NOT basic location data.

Anton, I have already sent a email to you and now only seeing this thread. Can u please suggest that above protocol with lock and unlock status is available in latest traccar release...

Traccar does support engine stop/resume command for Huabao protocol, if that's what you are asking.

Hi please put protocol for padlock

Dear Sir,

Please provide HDD G-400 Padlock communication protocol.

Regards,
Tectronix Global Telematics Pvt Ltd