Xexun protocol offline

Hello group I've been using a windows server for approximately 5 months with xexun and GT06 protocol trackers with zero problems until now. The GT06 protocol works fine, it's the xexun protocol. Only those are showing offline and report maybe once in a while sometimes even days or none at all like if the tracker is not sending any reports. But they are. When I text them they send links with correct location. I texted all the settings back to one of the trackers and it works again but only for a few minutes and then goes offline again. If anyone has had this problem before any help will be greatly appreciated. Thanks

Have you checked logs for errors?

2021-12-17 14:25:30  INFO: [68ed25c2: gt06 < 190.80.244.184] HEX: 78780a13460601000200975d840d0a
2021-12-17 14:25:30  INFO: [68ed25c2: gt06 > 190.80.244.184] HEX: 787805130097184e0d0a
2021-12-17 14:25:30  INFO: [68ed25c2] id: 355139082099638, time: 2021-12-17 14:24:56, lat: 18.67016, lon: -70.45335, speed: 4.3, course: 12.0
2021-12-17 14:25:31  INFO: [1fd2dda7: xexun < 190.80.245.112] HEX: 3231313231373133323533302c436c61726f2c4750524d432c3138323533302e3030302c412c313932352e373231302c4e2c30373033382e313330312c572c34372e35372c33392e38312c3137313232312c2c2c412a37312c462c2c20696d65693a3836323131373032313636343236322c30382c3230302e352c463a342e3238562c312c3133332c32363938392c3337302c30322c353635372c374635310a0d
2021-12-17 14:25:31  WARN: [1fd2dda7] error - readerIndex: -48, writerIndex: 208 (expected: 0 <= readerIndex <= writerIndex <= capacity(208)) - IndexOutOfBoundsException (... < BufferUtil:41 < XexunFrameDecoder:43 < BaseFrameDecoder:29 < ...)
2021-12-17 14:25:31  INFO: [1fd2dda7] disconnected
2021-12-17 14:25:31  WARN: [1fd2dda7] error - readerIndex: -48, writerIndex: 208 (expected: 0 <= readerIndex <= writerIndex <= capacity(208)) - IndexOutOfBoundsException (... < BufferUtil:41 < XexunFrameDecoder:43 < BaseFrameDecoder:29 < ...)

This is what I get in the logs. Copied both xexun and gt06 for comparison.

This probably means this format is not supported. If you need help with implementing it, you can contact support.

Thanks Anton for the quick reply. But I've been using this device for years with no problem first on the demo servers and now on my own server. It just recently started doing this.

There must have been some change in the format.

thanks Anton. Got it to work again all I did was stop and restart the server all is good again for now.