Good morning.
I am trying to add a device to my Traccar service to conduct tests. I have added the device's IMEI, as well as configured the device itself (by SMS) to point itself to my computer's public IP address and appropiate port. The device's protocol is TK103, so I have configured it to listen to port 5002. Here is my tracker-server.log entry for my latest attempt (all IP addresses have been crossed out):
2020-02-04 11:44:23 INFO: [a797f3cc] connected
2020-02-04 11:44:23 INFO: [a797f3cc: osmand < xxxxxxx] HEX: 504f5354202f3f69643d3434373736312674696d657374616d703d31353830383237383035266c61743d31302e34383634313936266c6f6e3d2d36362e383232373435392673706565643d302e302662656172696e673d302e3026616c7469747564653d3833392e302661636375726163793d32362e32333830303038363937353039373726626174743d34392e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f696420352e312e313b20534d2d4735333146204275696c642f4c4d59343842290d0a486f73743a203139322e3136382e312e32343a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2020-02-04 11:44:23 INFO: [a797f3cc: osmand > xxxxxxx] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-02-04 11:44:23 INFO: [a797f3cc] id: 447761, time: 2020-02-04 10:50:05, lat: 10.48642, lon: -66.82275, course: 0.0, accuracy: 26.2
2020-02-04 11:44:23 INFO: [a797f3cc: osmand < xxxxxxx] HEX: 504f5354202f3f69643d3434373736312674696d657374616d703d31353830383238313036266c61743d31302e34383634353136266c6f6e3d2d36362e383232373137312673706565643d302e302662656172696e673d302e3026616c7469747564653d3835312e3139393935313137313837352661636375726163793d32382e373135303030313532353837383926626174743d34392e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f696420352e312e313b20534d2d4735333146204275696c642f4c4d59343842290d0a486f73743a203139322e3136382e312e32343a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
...
2020-02-04 11:44:24 INFO: [a797f3cc: osmand > xxxxxxx] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-02-04 11:44:24 INFO: [a797f3cc] id: 447761, time: 2020-02-04 11:40:17, lat: 10.48643, lon: -66.82271, course: 0.0, accuracy: 29.0
2020-02-04 11:44:45 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 3836383638333032383331333138313b
2020-02-04 11:44:45 WARN: [cd4b2b90] error - begin 13, end 17, length 16 - StringIndexOutOfBoundsException (... < Tk103ProtocolDecoder:354 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-02-04 11:44:51 INFO: user: 2, action: login
2020-02-04 11:45:45 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 3836383638333032383331333138313b
2020-02-04 11:45:45 WARN: [cd4b2b90] error - begin 13, end 17, length 16 - StringIndexOutOfBoundsException (... < Tk103ProtocolDecoder:354 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-02-04 11:46:01 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 696d65693a3836383638333032383331333138312c747261636b65722c3230303230343131343630302c2c4c2c2c2c313739382c2c333339632c2c2c3b
2020-02-04 11:46:45 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 3836383638333032383331333138313b
2020-02-04 11:46:45 WARN: [cd4b2b90] error - begin 13, end 17, length 16 - StringIndexOutOfBoundsException (... < Tk103ProtocolDecoder:354 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-02-04 11:47:45 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 3836383638333032383331333138313b
2020-02-04 11:47:45 WARN: [cd4b2b90] error - begin 13, end 17, length 16 - StringIndexOutOfBoundsException (... < Tk103ProtocolDecoder:354 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-02-04 11:48:31 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 696d65693a3836383638333032383331333138312c747261636b65722c3230303230343131343833302c2c4c2c2c2c313739382c2c333339632c2c2c3b
2020-02-04 11:48:45 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 3836383638333032383331333138313b
2020-02-04 11:48:45 WARN: [cd4b2b90] error - begin 13, end 17, length 16 - StringIndexOutOfBoundsException (... < Tk103ProtocolDecoder:354 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-02-04 11:49:45 INFO: [cd4b2b90: tk103 < xxxxxxx] HEX: 3836383638333032383331333138313b
2020-02-04 11:49:45 WARN: [cd4b2b90] error - begin 13, end 17, length 16 - StringIndexOutOfBoundsException (... < Tk103ProtocolDecoder:354 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-02-04 11:50:19 INFO: [a797f3cc] disconnected
All the instances of "osmand" are fine - it's my own phone -also used for tests-. But for the tk103, I keep getting this error:
WARN: [cd4b2b90] error - begin 13, end 17, length 16 - StringIndexOutOfBoundsException (... < Tk103ProtocolDecoder:354 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
The number in brackets seems to be different every time. At one point it was d231c798. Currently it's cd4b2b90.
What does this error mean? What should I do to correct it?
Thank you in advance.
Good morning.
I am trying to add a device to my Traccar service to conduct tests. I have added the device's IMEI, as well as configured the device itself (by SMS) to point itself to my computer's public IP address and appropiate port. The device's protocol is TK103, so I have configured it to listen to port 5002. Here is my tracker-server.log entry for my latest attempt (all IP addresses have been crossed out):
All the instances of "osmand" are fine - it's my own phone -also used for tests-. But for the tk103, I keep getting this error:
The number in brackets seems to be different every time. At one point it was d231c798. Currently it's cd4b2b90.
What does this error mean? What should I do to correct it?
Thank you in advance.