Device sometimes sends corrupted data. See following packet in HEX format with comments:
c902253d1c4401005202a581 // header
4957c8576bffc3db80400042014642eeb9d741141f1b1600acf99741f1000000946e4300d71000003b1000000000a401044f2f8139044d00000000000000000000000000000000000000 // length 74 (0x49 + 1) as expected
4987c8576bffc3db8040009101464260bad7411b1f18160077f71842f1000000b56e4300d7100d003b1000000000a401044f2f8139044d00000000000000000000000000000000000000
4917c9576bffc3db804000ba0246423fbcd7411c1f201800246a1743f1000000c66e4300d7100d003b1000000000a401044f2f4d38105000000000000000000000000000000000000000
4927c9576bffc3db804000e50246424dbcd7411d1f2b180041608541f1000000d66e4300d7100d003b1000000000a401044f2f4d38105000000000000000000000000000000000000000
4937c9576bffc3db8040001303464257bcd7411f1f25180063d78b41f1000000e76e4300d7100d003b1000000000a401044f2f4d38105000000000000000000000000000000000000000
4947c9576bffc3db8040003f03464278bcd741211f1e180097359241f1000000c66e4300c9100d003b1000000000a401044f2f4d38105000000000000000000000000000000000000000
4957c9576bffc3db80400066034642b1bcd741231f1517002a099741f1200000d66e4300d7100d003b1000000000a401044f2f4d38105000000000000000000000000000000000000000
49a7c9576bffc3db804000fa034642b2bdd7411c1f141400fb5a9c42f1200000c66e4300d7100d003b1000000000a401044f2f4d38105000000000000000000000000000000000000000
4c00a00049a758c16bffc3db8040008efb4542fa73d741261f6e0b0000000000f1000000396d4300d7100000651000000000a401044f2f9a2b023a00000000000000000000000000000000000000 // length should be 77 (0x4c + 1), but it is 78
b0 // checksum
Not only length of the last message in the block is incorrect, but coordinates and other info are wrong as well.
How does Wialon server handle this situation? Is there some workaround for this problem?