If your device sends it, you will see it in the state panel, as everything else. To associate, yes, use driver menu.
hi anton and thanks for the reply
i'm a bit confused about what to write in the identification tab of the driver's menu.
I write the teltonika IMEI and then in the attributes I write the code on the name tab and for value i write ibutton?
thanks
Identification is obviously driver identifier, not your device IMEI.
Hi Anton and thanks, I can't understand where to look in the log file to see if and when the key registration comes...
Below is a recursive log piece:
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:38 WARN: Geocoding failed - javax.ws.rs.ClientErrorException: HTTP 429 Too Many Requests - ResponseProcessingException (...)
2019-03-25 11:17:43 INFO: [25a61e22] connected
2019-03-25 11:17:43 INFO: [25a61e22: 5027 < 5.170.223.209] HEX: 000f383631313037303331363835303238
2019-03-25 11:17:43 INFO: [25a61e22: 5027 > 5.170.223.209] HEX: 01
2019-03-25 11:17:43 INFO: [25a61e22: 5027 < 5.170.223.209] HEX: 000000000000016b080c00000169b45a32e000049c8b3c1acf633000ed004b08000000000000000000000169b45a466800049c8b3c1acf632e00ed004b08000000000000000000000169b45a59f000049c8b3c1acf632b00ed004b08000000000000000000000169b45a6d7800049c8b3b1acf632a00ed004b08000000000000000000000169b45a810000049c8b3b1acf632900ed004b08000000000000000000000169b45a948800049c8b3b1acf632800ed004b08000000000000000000000169b45aa81000049c8b3a1acf632800ed004b08000000000000000000000169b45abb9800049c8b3a1acf632700ed004b08000000000000000000000169b45acf2000049c8b3a1acf632700ed004b08000000000000000000000169b45ae2a800049c8b3a1acf632600ed004b08000000000000000000000169b45af63000049c8b3b1acf632500ed004b08000000000000000000000169b45b09b800049c8b3b1acf632500ed004b0800000000000000000c0000e434
2019-03-25 11:17:43 INFO: [25a61e22: 5027 > 5.170.223.209] HEX: 0000000c
I don't understand if the gps sends something about the ibotton.
Any help is welcome.
Thanks
what I have reported are the logs that I see continuously, confirm that in the last 4 lines there is nothing that concerns the ibotton tag?
No ibotton information, as far as I can tell.
Hi Anton and hi everyone, I wanted to know how to view the ibotton codes sent by the GPS and how to associate them with the name on the server.
Driver Section?
I have already configured the GPS to send the position to the server, I discovered from another post that I had to set DIN1 to ignition status, but I'm trying to figure out how to view the green status on the server only when the car is turned on with the botton tag, and i think is it a configuration on Teltonika data sending.
Thanks all for reply