Have you read troubleshooting guide? It should answer your first question.
As for second question, unfortunately it's not clear what the problem is.
Thanks Anton's reply,
As for the first question, I convert the hex code to ASCII with the hex decoder, and use the socket tool to send it again, it can display ID info normally. but the ASCII was sent by the real device won't display. It's very strange.
Please provide logs fragment for full connection session (see id in the square brackets), and explain on that example what's wrong.
#real device
2018-10-24 21:22:35 INFO: [4545d192] connected
2018-10-24 21:22:35 INFO: [4545d192: 5093 < 117.136.40.201] HEX: 5b53472a3838303938303030303030303031362a303038302a414c2c3234313031382c3231313730302c562c302e30302c4e2c302e30302c452c302e30302c302c302c302c38332c38332c302c302c30303030303030302c342c312c3436302c302c393337362c333638332c2d37312c393337362c333638312c2d35312c393337362c343435312c2d35312c393337362c333636312c2d35315d0d0a
2018-10-24 21:22:35 INFO: [4545d192: 5093 > 117.136.40.201] HEX: 5b53472a3838303938303030303030303031362a303031642a414c2c20323031382d31302d32342032313a32323a33352c204d5347305d
2018-10-24 21:22:36 INFO: [4545d192] disconnected
#Simulate
2018-10-24 21:31:56 INFO: [a5f0ec45] connected
2018-10-24 21:32:00 INFO: [a5f0ec45: 5093 < 183.14.134.174] HEX: 5b53472a3838303938303030303030303031362a303038302a414c2c3234313031382c3231313730302c562c302e30302c4e2c302e30302c452c302e30302c302c302c302c38332c38332c302c302c30303030303030302c342c312c3436302c302c393337362c333638332c2d37312c393337362c333638312c2d35312c393337362c343435312c2d35312c393337362c333636312c2d35315d
2018-10-24 21:32:00 INFO: [a5f0ec45: 5093 > 183.14.134.174] HEX: 5b53472a3838303938303030303030303031362a303031642a414c2c20323031382d31302d32342032313a33323a30302c204d5347305d
2018-10-24 21:32:01 INFO: [a5f0ec45] id: 880980000000016, time: 2018-10-24 21:32:00, lat: 22.66829, lon: 114.19814, course: 0.0
2018-10-24 21:32:05 INFO: [a5f0ec45] disconnected
the 2 part is simulated.
Can you see the difference between two?
Thanks Anton,
I compare and check the difference is 0d0a at the end.
But I find some hexcode contained 0x0d0a also can display ID info normally...
It's all about message length.
Hi, Anton Tananaev,
Nice to meet you. I update to version4.1 and find some log problem, can you confirm it :
sometime can diaplay ID like
INFO: [476ec2f3] id: 880980000000016, time: 2018-10-24
after the info like5093 > 117.136.40.213] HEX: 5b0a5b2a....
,but most can't display ID, why?some string Header will be mess by other characters, the expected is
5b53472a38383039383030....
but is replaced by5b0a5b2a472a383830......