disable filters for some devices only

Lukas Z. 7 years ago
2018-10-30 09:19:21  INFO: [a7dfbd25: 37493 < 46.135.10.184] HEX: 2b524553503a475449474c2c3331303730312c3836333238363032333731323835352c2c2c30312c312c312c302e302c302c3337362e382c31342e3131383338332c35302e3134303833392c32303138313033303038313932302c303233302c303030332c394231342c363541352c30302c302e302c32303138313033303038313932312c3036443224

expected YES, see NO

Anton Tananaev 7 years ago

In your example Report ID/Report Type value is 01, so Report Type is 1. According to the documentation that I have:

In the message of ignition on and ignition off message +RESP:GTIGL
0: the engine is ignition on.
1: the engine is ignition off.

Which means that device reported ignition as OFF. Is your documentation different?

Lukas Z. 7 years ago

Yes, in the GV65 Track Interface document V2.0 I have sent You by email is 0=off,1=on. See the page 93 please

Lukas Z. 7 years ago

Also see the page 96 how is ignition status reported in GTFRI messages

Anton Tananaev 7 years ago

I'm not sure what to do then. Different devices seem to report opposite values.

Lukas Z. 7 years ago

Maybe there could be only error in the documentation you have. Or you can create different protocol (gv65?). I have several different Queclink devices and I am ready to test them.

Anton Tananaev 7 years ago

It would be nice if you can ask device vendor if it's a mistake. Creating a new protocol just because of one value is definitely not an option though.

Lukas Z. 7 years ago

Sure I can ask. But I have tested gv65,gv65L,gv65N,gv300,gv600. Any of them works with 1=on,0=off (it seems to be logical I mean)

Anton Tananaev 7 years ago

Documentation that I quoted is for GV300:

GSM/GPRS/GPS Tracker GV300
@Track Air Interface Protocol
Application Notes: TRACGV300AN004
Revision: 8.00

Lukas Z. 7 years ago

Confirmed - in GV300 @Track Air Interface Protocol TRACGV300AN001 Revision: 14.05 is 0=off,1=on. Page 162. I am sending it to You by email.