Do you have protocol documentation? Do you have any message samples?
I don’t but I’ll try to find this out.
These are samples samples from QT500
2017-12-16 23:42:07 DEBUG: [D07D4799: 5039 < 186.167.250.135] HEX: 283038383034363537353836314252303031373132313741313033352e333937394e30373133382e36313636573030302e303034343230363030302e303030303030303030304c303034433832413329
2017-12-16 23:44:08 DEBUG: [D07D4799: 5039 < 186.167.250.135] HEX: 283038383034363537353836314252303031373132313741313033352e333937394e30373133382e36313636573030302e303034343430383030302e303030303030303030304c303034433832413329
2017-12-16 23:46:09 DEBUG: [D07D4799: 5039 < 186.167.250.135] HEX: 283038383034363537353836314252303031373132313741313033352e333937394e30373133382e36313636573030302e303034343630393030302e303030303030303030304c303034433832413329
2017-12-16 23:48:10 DEBUG: [D07D4799: 5039 < 186.167.250.135] HEX: 283038383034363537353836314252303031373132313741313033352e333937394e30373133382e36313636573030302e303034343831303030302e303030303030303030304c303034433832413329
This is hexa decode from first line
(088046575861BR00171217A1035.3979N07138.6166W000.0044206000.0000000000L004C82A3)
283038383034363537353836314252303031373132313741313033352e333937394e30373133382e36313636573030302e303034343230363030302e303030303030303030304c303034433832413329
Look like TK103
I'll try it.
YOBA YOBA YOBA!!!!! I did.
Brand: Quiktrak
Model: QT500
Protocol: tk103
Port: 5002
The problem was at Identification number. It shown up to the server a little diferent with the last 12 digits.
Thanks for Troubleshooting guide.
Could someone help me out with the protocol from this device I have tried 5064 and many others but it didn’t connect with Traccars system.