GPS103

emmerossi4 years ago

Hi, I'm using a tracker that should be a TK103 similar to another one configured as protocol 5001 receiving this :

2021-04-06 17:27:53  INFO: [e2eae59a] connected
2021-04-06 17:27:54  INFO: [e2eae59a: gps103 < 5.35.166.181] HEX: 2a48512c3836353230353033383931313130322c563023
2021-04-06 17:27:54  WARN: [e2eae59a] error - begin 21, end 24, length 1 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-04-06 17:27:54  INFO: [e2eae59a] disconnected
2021-04-06 17:27:55  INFO: [f3284308] connected
2021-04-06 17:27:55  INFO: [f3284308: gps103 < 5.35.166.181] HEX: 2a48512c3836353230353033383931313130322c563023
2021-04-06 17:27:55  WARN: [f3284308] error - begin 21, end 24, length 1 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-04-06 17:27:55  INFO: [f3284308] disconnected

Any idea about the error ? looks like a problem in the tracker, thanks

Anton Tananaev4 years ago

Wrong port. Try 5013. Next time please read documentation before asking on the forum.

emmerossi4 years ago

I try to use protocol 5002 with this result :

2021-04-06 17:35:48  INFO: [50caf156] connected
2021-04-06 17:35:48  INFO: [50caf156: gps103 < 5.35.166.181] HEX: 2a48512c3836353230353033383931313130322c563023
2021-04-06 17:35:48  WARN: [50caf156] error - begin 21, end 24, length 1 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
emmerossi4 years ago

I'll try immediately

emmerossi4 years ago

Thank you, much better. In the documentation anyway the protocol 5013 is not referenced to GPS103 or TK103, Am I wrong ?
Using 5013 this is the log :

2021-04-06 17:48:23  INFO: [9ae0be10] connected
2021-04-06 17:48:23  INFO: [9ae0be10: tk103 < 5.35.166.181] HEX: 2a48512c3836353230353033383931313130322c563023
2021-04-06 17:48:29  INFO: [9ae0be10: tk103 < 5.35.166.181] HEX: 2a48512c3836353230353033383931313130322c56312c3135343832382c412c343532362e333931322c4e2c30303930392e393534352c452c3030302e30302c3330302c3036303432312c454645374642464623
2021-04-06 17:48:49  INFO: [9ae0be10: tk103 < 5.35.166.181] HEX: 2a48512c3836353230353033383931313130322c56312c3135343834382c412c343532362e333931322c4e2c30303930392e393534352c452c3030302e30302c3332342c3036303432312c454645374642464623

But there still someting wrong, since i cannot show on the app.

Anton Tananaev4 years ago

Wrong port or wrong port mapping. It should be H02.

ihalili2 years ago

Hi there i have this issue,

using the port 5001

2022-12-27 18:56:45  INFO: [Td4f8d05a: gps103 > 46.99.116.153] 4f4e
2022-12-27 18:56:45  INFO: [Td4f8d05a: gps103 > 46.99.116.153] 4f4e
2022-12-27 18:56:45  INFO: [Td4f8d05a] disconnected
2022-12-27 18:56:50  INFO: [T900e447d] connected
2022-12-27 18:56:50  INFO: [T900e447d: gps103 < 46.99.116.153] 5b33472a393730353033323130342a303030392a4c4b2c302c302c32305d
2022-12-27 18:56:50  INFO: [T900e447d] error - begin 21, end 24, length 4 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)

and how can add register the device

ihalili2 years ago

Solved i used diffrent port number