Not displaying the device location
That's not from your device.
Dear Concern,
Please find out the server log for school ID card tracker device which we are trying to connect it to the traccar server. Note that as per the communication protocol doc which we have received from supplier it match the traccar H02 protocol. However we follow the procedure that mentioned in the traccar doc; and still no luck to see the tracker location in the web dashboard.
Here is the log
2018-12-24 11:59:00 INFO: [d9369f13] connected
2018-12-24 11:59:01 INFO: [d9369f13: 8082 < 172.18.10.17] HEX: 2a48512c3335363332373038313030313232312c58542c3123
2018-12-24 11:59:02 INFO: [c05aa4cc] connected
2018-12-24 11:59:02 INFO: [c05aa4cc] disconnected
2018-12-24 11:59:02 INFO: [d9369f13: 8082 < 172.18.10.17] HEX: 2a68712c3335363332373038313030313232312c414750532c34373023
2018-12-24 11:59:02 INFO: [c4ad2250] connected
2018-12-24 11:59:02 INFO: [c4ad2250] disconnected
2018-12-24 11:59:07 INFO: [993f7e73] connected
2018-12-24 11:59:07 INFO: [993f7e73] disconnected
2018-12-24 11:59:07 INFO: [afd93067] connected
2018-12-24 11:59:07 INFO: [afd93067] disconnected
2018-12-24 11:59:11 INFO: [1d33822a: 8082 < 172.18.10.17] HEX: 2a68712c3335363332373038313030313233392c5650312c562c3437302c3030322c39322c333536352c305939322c31393433332c33305939322c313334302c323923
2018-12-24 11:59:12 INFO: [91eff843] connected
2018-12-24 11:59:12 INFO: [91eff843] disconnected
2018-12-24 11:59:12 INFO: [86b83e5e] connected
2018-12-24 11:59:12 INFO: [86b83e5e] disconnected
2018-12-24 11:59:17 INFO: [ed7074d7] connected
2018-12-24 11:59:17 INFO: [ed7074d7] disconnected
2018-12-24 11:59:17 INFO: [c474fa25] connected
2018-12-24 11:59:17 INFO: [c474fa25] disconnected
2018-12-24 11:59:22 INFO: [8b0428fe] disconnected
2018-12-24 11:59:22 INFO: [08903cfa] connected
2018-12-24 11:59:22 INFO: [08903cfa] disconnected
2018-12-24 11:59:22 INFO: [1973a296] connected
2018-12-24 11:59:22 INFO: [1973a296] disconnectedDear Concern,
Please support me why i am still unable to see the tracker device in the web dashboard.
After decode the HEX data i have found out following
*hq,356327081001239,VP1,V,470,002,92,3565,0Y92,19433,30Y92,1340,29#Please let me know where is the issue. However as per your protocol identification guide i have found that there is a sample protocol format of H02 is the following
'h02' : '*HQ,123456789012345,V1,121300,A,6000.0000,N,13000.0000,E,0.00,0.00,010112,ffffffff,000000,000000,000000,000000#',Mean the first field which is IHRD seems different; in the sample it mentioned caps lock "HQ" where as i am receiving small caps of "hq" from the device.
Please let me know will it be an issue; if so then please guide me how to resolve it. Moreover do i need to use the port address 5013 of H02 protocol or i can change it to any other port while i have configured my own server.
Thank you
The sample that you provided doesn't have any location data.
Hi Anton,
Please can you let me know is there any issue with H02 Protocol Frame Decoder, cos the data which we are receiving from the device it cannot decoded by the traccar server. In the log file we found that following
2018-12-24 11:59:01 INFO: [d9369f13: 8082 < 172.18.10.17] HEX: 2a48512c3335363332373038313030313232312c58542c3123
2018-12-24 11:59:02 INFO: [c05aa4cc] connected
2018-12-24 11:59:02 INFO: [c05aa4cc] disconnected
2018-12-24 11:59:02 INFO: [d9369f13: 8082 < 172.18.10.17] HEX: 2a68712c3335363332373038313030313232312c414750532c34373023
2018-12-24 11:59:02 INFO: [c4ad2250] connected
2018-12-24 11:59:02 INFO: [c4ad2250] disconnected
2018-12-24 11:59:07 INFO: [993f7e73] connected
2018-12-24 11:59:07 INFO: [993f7e73] disconnected
2018-12-24 11:59:07 INFO: [afd93067] connected
2018-12-24 11:59:07 INFO: [afd93067] disconnected
2018-12-24 11:59:11 INFO: [1d33822a: 8082 < 172.18.10.17] HEX: 2a68712c3335363332373038313030313233392c5650312c562c3437302c3030322c39322c333536352c305939322c31393433332c33305939322c313334302c323923
2018-12-24 11:59:12 INFO: [91eff843] connected
2018-12-24 11:59:12 INFO: [91eff843] disconnected
2018-12-24 11:59:12 INFO: [86b83e5e] connectedNeed your advise and support.
Thank you
Rabi
Still no location data.
Hi Anton
I have found out the clue my School ID card tracker is sending the LBS data instead of GPS data; hence may for this reason the traccar server could not decode the Hex data.
Now advise me how i can decode this hex data by using traccar server.
Data sample is as below
HEX: 2a68712c3335363332373038313030313233392c5650312c562c3437302c3030322c39322c333536352c305939322c313334302c33345939322c31393433332c323823If we decode the above data using Hex converter the following info come
*hq,356327081001239,VP1,V,470,002,92,3565,0Y92,19433,30Y92,1340,29#In the above "V" means the LBS data.
Please help me resolve this so that traccar server can convert the LBS data and plot in the web interface.
Thank you
Rabi
I guess it's not supported yet.
Hi Anton,
Thank you for your reply. Is there any way that we can develop the decoder; so that it can support the LBS data.
If you have any please advise us or suggest us to develop it.
Thank you
Rabi
Of course decoder can be extended to support LBS data. Email to support if you need help with it.
Dear Concern,
I am getting the tracker device data in the server as per the mentioned server log.
However but the device location in not visible in the website display board, it seems offline.
Please need your support. here is the server log