Are you using latest version of Traccar? Please provide protocol documentation for your device.
Sure, 4.1 (with cam customization you made for me). Protocol documentation has been already sent by email
I have also provided you access to my server (yesterday mail)
I have compared OBD message format and it's somewhat different from what we have implemented at the moment. This would require some code changes.
The same device moved to different car (Ford Mondeo) particulary works. But no information abut fuel level or fuel consumption are decoded.
2018-11-02 06:41:00 INFO: [f7ad6cc1: 37493 < 46.135.67.192] HEX: 2b524553503a4754494e462c3146303130372c3836323139333032323030313433322c57463047585847424247424d32363530332c2c32322c38393432303331303137343432313233393333662c32352c302c312c31333235362c2c342e322c302c302c2c2c32303138313130323035343035382c2c2c2c2c2c2b303030302c302c32303138313130323035343130322c4237374124
2018-11-02 06:41:00 INFO: [f7ad6cc1] id: 862193022001432, time: 2018-11-02 06:40:43, lat: 50.13996, lon: 14.11793, speed: 12.5, course: 324.0
2018-11-02 06:41:02 INFO: [f7ad6cc1: 37493 < 46.135.67.192] HEX: 2b41434b3a47544842442c3146303130372c3836323139333032323030313433322c2c32303138313130323035343130342c4237374224
2018-11-02 06:41:02 INFO: [f7ad6cc1: 37493 > 46.135.67.192] HEX: 2b5341434b3a47544842442c3146303130372c4237374224
2018-11-02 06:41:08 INFO: [f7ad6cc1: 37493 < 46.135.67.192] HEX: 2b524553503a47544652492c3146303130372c3836323139333032323030313433322c57463047585847424247424d32363530332c2c31333037382c34302c312c312c302e302c3333302c3339392e322c31342e3131373632312c35302e3134303332332c32303138313130323035343130372c2c2c2c2c2c313433352e372c30303031323a32343a34342c2c2c39372c3232303030302c3830312c34312e392c2c3230313831313032303534313130
2018-11-02 06:41:08 INFO: [f7ad6cc1: 37493 < 46.135.67.192] HEX: 2c4237374324
2018-11-02 06:41:08 INFO: [f7ad6cc1] id: 862193022001432, time: 2018-11-02 06:41:07, lat: 50.14032, lon: 14.11762, course: 330.0
2018-11-02 06:41:28 INFO: [f7ad6cc1: 37493 < 46.135.67.192] HEX: 2b524553503a47545354542c3146303130372c3836323139333032323030313433322c57463047585847424247424d32363530332c2c32312c302c302e302c3333302c3339392e322c31342e3131373632312c35302e3134303332332c32303138313130323035343132352c2c2c2c2c2c32303138313130323035343133302c4237374424
2018-11-02 06:41:28 INFO: [f7ad6cc1] id: 862193022001432, time: 2018-11-02 06:41:25, lat: 50.14032, lon: 14.11762, course: 330.0
2018-11-02 06:42:53 INFO: [f7ad6cc1: 37493 < 46.135.67.192] HEX: 2b524553503a47545354502c3146303130372c3836323139333032323030313433322c57463047585847424247424d32363530332c2c2c2c302c302e302c3333302c3339392e322c31342e3131373632312c35302e3134303332332c32303138313130323035343235322c2c2c2c2c2c313433352e372c32303138313130323035343235352c4237374524
2018-11-02 06:42:53 INFO: [f7ad6cc1] id: 862193022001432, time: 2018-11-02 06:42:52, lat: 50.14032, lon: 14.11762, course: 330.0
2018-11-02 06:44:53 INFO: [f7ad6cc1] timed out
2018-11-02 06:44:53 INFO: [f7ad6cc1] disconnected
Also problem with decoding CAN messages from Queclink GV300. Will you have a time to enhance gl200 protocol to support CAN and OBD messages please?
2018-11-02 18:50:49 INFO: [d588d9dc] connected
2018-11-02 18:50:49 INFO: [d588d9dc: 37493 < 46.135.68.77] HEX: 2b41434b3a47544842442c3442303230312c3836373939353033303030313537352c2c32303138313130323137353035302c3037323824
2018-11-02 18:50:49 INFO: [d588d9dc: 37493 > 46.135.68.77] HEX: 2b5341434b3a47544842442c3442303230312c3037323824
2018-11-02 18:50:49 INFO: [d588d9dc: 37493 < 46.135.68.77] HEX: 2b524553503a475443414e2c3442303230312c3836373939353033303030313537352c2c31302c302c43303346464646462c2c302c48302c2c2c2c2c2c2c2c2c2c302e30302c302e30332c2c2c2c302c2c302c2c2c302c302e302c3331302c3339362e362c31342e3131373835352c35302e3134303239352c32303138313130323137343630332c303233302c303030332c394231342c363541352c30302c32303138313130323137353034392c3037323724
2018-11-02 18:50:49 WARN: [d588d9dc] error - empty String - NumberFormatException (... < Gl200TextProtocolDecoder:595 < *:1102 < Gl200ProtocolDecoder:46 < ExtendedObjectDecoder:51 < ...)
2018-11-02 18:50:49 INFO: [d588d9dc] disconnected
messages from OBDII tracker Queclink gv500
+RESP:GTOSM - OBDII Status Monitor Report
+RESP:GTFRI - Fixed Report Information
+RESP:GTOBD - OBDII Information Report
2018-11-04 09:07:05 INFO: [e85c9e4b: 37493 < 46.135.13.253] HEX: 2b524553503a47544f534d2c3146303330312c3836323139333032323030313433322c57463047585847424247424d32363530332c2c332c302c464646462c57463047585847424247424d32363530332c312c31343930302c39383342383134302c3739392c33392c37392c372e332c2c302c302c302c2c302c33302c2c32303138313130343038303730342c3039394424
2018-11-04 09:07:06 INFO: [e85c9e4b: 37493 < 46.135.13.253] HEX: 2b524553503a47544f42442c3146303330312c3836323139333032323030313433322c57463047585847424247424d32363530332c2c302c464646462c57463047585847424247424d32363530332c312c31343834302c39383342383134302c3739392c33392c37392c372e332c2c302c302c302c2c302c33302c2c32303138313130343038303730352c3039394524
2018-11-04 09:07:08 INFO: [e85c9e4b: 37493 < 46.135.13.253] HEX: 2b524553503a47544652492c3146303330312c3836323139333032323030313433322c57463047585847424247424d32363530332c2c31343834302c34312c312c312c342e362c35342c3335362e312c31342e3132303133382c35302e3136373931382c32303138313130343038303730362c303233302c303030332c394231342c353839312c30302c37342e312c2c2c2c38332c3232303030302c3739392c372e332c2c3230313831313034303830
messages from CAN tracker Queclin gv300CAN
+RESP:GTCAN - CANBUS Device Information Report
the only one type which I have now, see the page 271 in documentation
2018-11-02 12:21:01 INFO: [45dc8eab: 37493 < 46.135.68.77] HEX: 2b524553503a475443414e2c3442303230312c3836373939353033303030313537352c2c31302c302c43303346464646462c2c302c48302c2c2c2c2c2c2c2c2c2c302e30302c302e30332c2c2c2c302c2c302c2c2c302c31302e302c3331302c3430342e332c31342e3039363734332c35302e3134333336332c32303138313130323131303533352c303233302c303030332c394231342c353036362c30302c32303138313130323131323130312c3033453024
2018-11-02 12:21:01 WARN: [45dc8eab] error - empty String - NumberFormatException (... < Gl200TextProtocolDecoder:595 < *:1102 < Gl200ProtocolDecoder:46 < ExtendedObjectDecoder:51 < ...)
+RESP:GTERI - If +RESP:GTERI is enabled, the device will send the message +RESP:GTERI to the backend server instead of +RESP:GTFRI.
2018-11-02 18:08:34 INFO: [12f6dec8: 37493 < 46.135.68.77] HEX: 2b524553503a47544552492c3442303230312c3836373939353033303030313537352c2c30303030303030342c2c31302c312c302c302e302c3331302c3339362e362c31342e3131373835352c35302e3134303239352c32303138313130323131323630342c303233302c303030332c394231342c363541352c30302c302e302c2c2c37372c3131303030302c302c302c43303346464646462c2c302c48302c2c2c2c2c2c2c2c2c2c302e30302c302e30332c2c2c2c302c2c302c2c2c32303138313130323137303833332c3036434424
messages from tracker Queclink gv65 with CanLogistic interface connected
+RESP:GTERI
2b524553503a47544552492c3331303730312c3836333238363032333731323835352c2c30303030303030362c32363134362c31302c312c312c302e352c35302c3337322e302c31342e3237363438352c35302e3131313632362c32303138313130363134323330362c303233302c303030332c393444342c333244332c30302c392e392c2c2c2c3131303030302c322c302c302c30303346464646462c2c322c4834363335322c31323239372e30302c3630312c302c36342c2c5035332e30302c2c302c2c302e30302c312e30302c2c2c2c35302c2c302c2c2c32303138313130363134323330372c3138364424
+RESP:GTCAN
2b524553503a475443414e2c3331303730312c3836333238363032333731323835352c2c31322c302c30303346464646462c2c322c4834363335322c31323239372e30302c3630312c302c36342c2c5035332e30302c2c302c2c302e30302c312e30302c2c2c2c35302c2c302c2c2c32303138313130363134323331362c3138373024
I am interested in this as well. Support for the GV500 would be a nice feature.
Dear: Could anyone advance the interpretation of the GV500 and GV300CAN reports?
No OBD data are decoded from gv500. Here are OBD messages filtered from log using