TK-419 - Protocol Eelink (5064)
The line that you picked from the logs doesn't give any context.
Hey mate,
Hope this is more information.
2020-02-19 08:55:59 INFO: [a01cbaa8] connected
2020-02-19 08:55:59 INFO: [a01cbaa8: eelink < 192.168.1.1] HEX: 474554202f20485454502f312e310d0a557365722d4167656e743a204d6f7a696c6c612f352e3020285831313b205562756e74753b204c696e757820693638363b2072763a32342e3029204765636b6f2f32303130303130312046697265666f782f32342e300d0a4163636570743a206170706c69636174696f6e2f786d6c2c6170706c69636174696f6e2f7868746d6c2b786d6c2c746578742f68746d6c3b713d302e392c746578742f706c61696e3b713d302e382c696d6167652f706e672c2a2f2a3b713d302e350d0a4163636570742d4c616e67756167653a20656e0d0a4163636570742d456e636f64696e673a206964656e746974790d0a486f73743a20736d6567736f6e2e686f70746f2e6f72673a353036340d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a0d0a
2020-02-19 08:55:59 WARN: [a01cbaa8] error - Adjusted frame length exceeds 1024: 8244 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-02-19 08:55:59 INFO: [a01cbaa8] disconnected
2020-02-19 08:55:59 INFO: [9a79741e] connected
2020-02-19 08:55:59 INFO: [9a79741e: eelink < 192.168.1.1] HEX: 474554202f20485454502f312e310d0a557365722d4167656e743a204d6f7a696c6c612f352e3020285831313b205562756e74753b204c696e757820693638363b2072763a32342e3029204765636b6f2f32303130303130312046697265666f782f32342e300d0a4163636570743a206170706c69636174696f6e2f786d6c2c6170706c69636174696f6e2f7868746d6c2b786d6c2c746578742f68746d6c3b713d302e392c746578742f706c61696e3b713d302e382c696d6167652f706e672c2a2f2a3b713d302e350d0a4163636570742d4c616e67756167653a20656e0d0a4163636570742d456e636f64696e673a206964656e746974790d0a486f73743a20736d6567736f6e2e686f70746f2e6f72673a353036340d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a0d0a
2020-02-19 08:55:59 WARN: [9a79741e] error - Adjusted frame length exceeds 1024: 8244 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-02-19 08:55:59 INFO: [9a79741e] disconnectedHave you tried decoding those messages? I only see two attempts from a Firefox browser to connect to this port. No messages from any GPS devices.
I'v sent URL# requests and pressed SOS.
What are the WARN messages there though?
Have you read my comment? Those logs are NOT FROM YOUR DEVICE. They are from a browser. Obviously a browser request doesn't comply with the eelink protocol, so you get errors.
hello，Sam，if you need help and dont know how to make device work well at traccar platform。you can contact the device seller.
If you dont know how to set up the configuration commands for your devices， you can check this manual device command or the eelink 2.0 protocols
Hey David, thanks for your kind advise, something i would of expected from the admin/moderators of this site.
I have had GT06e's running off this platform for quite some time and got them working with ease. I don't have experience with coding/log writing etc. which i'm trying to learn.
I have since fixed this issue which was a incorrect command sent to the GPS, which was different to what the device manual provided.
Thank you.
Sam
is TK419 is working??
is there any update on this? really is a good gps, but bad settings or decoder from server (traccar) anyway i can do it manually?
Original issue discussed in this thread has nothing to do with the server. Device simply doesn't report anything to the server, which probably indicates a device or device configuration issue.
Great conversation.
i found that pdf, so this divice will not work with traccar? :/
This protocol is supported. What makes you think it's not?
Hello,
i have a Eelink TK-419, i have set to Port 5064 but it doesn't seem to work
Any help please.