GV55

jura5 years ago

Hello,

i'm trying to get GV55 to work, but no luck. I get messages to server, but device is offline all the time. I have tested with mobile app and it's working fine...

Does anyone have settings for GV55?

Thank you...

Anton Tananaev5 years ago

Logs?

jura5 years ago
2019-01-06 12:31:07  WARN: Unknown device - 862193020966644 (31.217.17.221)
2019-01-06 12:31:27  INFO: [ae8e7560: 5004 < 31.217.17.221] HEX: 2b41434b3a47545153532c3046383730312c3836323139333032303936363634342c414e32302c303133342c32303131303130313030303035332c3043343624
2019-01-06 12:31:27  WARN: Unknown device - 862193020966644 (31.217.17.221)
2019-01-06 12:31:29  INFO: user: 1, action: edit, object: device, id: 1
2019-01-06 12:31:47  INFO: [ae8e7560: 5004 < 31.217.17.221] HEX: 2b41434b3a47545153532c3046383730312c3836323139333032303936363634342c414e32302c303133342c32303131303130313030303035332c3043343624
2019-01-06 12:31:47  INFO: [ae8e7560] id: 862193020966644, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0, result: Command QSS accepted
2019-01-06 12:32:07  INFO: [ae8e7560: 5004 < 31.217.17.221] HEX: 2b41434b3a47545153532c3046383730312c3836323139333032303936363634342c414e32302c303133342c32303131303130313030303035332c3043343624
2019-01-06 12:32:07  INFO: [ae8e7560] id: 862193020966644, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0, result: Command QSS accepted
2019-01-06 12:32:27  INFO: [ae8e7560: 5004 < 31.217.17.221] HEX: 2b41434b3a47545153532c3046383730312c3836323139333032303936363634342c414e32302c303133342c32303131303130313030303035332c3043343624
2019-01-06 12:32:27  INFO: [ae8e7560] id: 862193020966644, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0, result: Command QSS accepted
2019-01-06 12:33:18  INFO: [ae8e7560: 5004 < 31.217.15.231] HEX: 243030303030383632313933303230393636363434303038393338353937303331383236323933323234663030303231393031393732333030333833320d0a
2019-01-06 12:33:39  INFO: [ae8e7560: 5004 < 31.217.15.231] HEX: 243030303030383632313933303230393636363434303038393338353937303331383236323933323234663030303231393031393732333030333833320d0a
2019-01-06 12:33:59  INFO: [ae8e7560: 5004 < 31.217.15.231] HEX: 243030303030383632313933303230393636363434303038393338353937303331383236323933323234663030303231393031393732333030333833320d0a
2019-01-06 12:34:19  INFO: [ae8e7560: 5004 < 31.217.15.231] HEX: 243030303030383632313933303230393636363434303038393338353937303331383236323933323234663030303231393031393732333030333833320d0a
2019-01-06 12:34:39  INFO: [ae8e7560: 5004 < 31.217.15.231] HEX: 243030303030383632313933303230393636363434303038393338353937303331383236323933323234663030303231393031393732333030333833320d0a
Anton Tananaev5 years ago

I suggest you carefully read log file yourself first. If you still don't see the problem, follow troubleshooting guide.

jura5 years ago

:) thank you Anton. So you want to say that it's normal that server decodes 0.0 coordinates in first few lines and then does not decode messages? So my device is working properly? This first few proper lines confused me..

btw i read the documentation before i opened this post...

Anton Tananaev5 years ago

Your device just doesn't send any GPS location. Also, last messages that are not decoded seem to be a malfunction of the device, unless there is something new in the protocol. Do you have protocol documentation for your device?

jura5 years ago