Jt600 protocol problem

I have some Jointech JT701 brand devices, these are reporting to port 5014 (protocol jt600). The reports are correct, however the devices report the same information repeatedly. Analyzing the log, I cannot find responses from the server towards the device informed that it received the message. and I think this is the reason why the information is repeated.

2020-11-09 00:12:56  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 28373539313131353533342c404a5429
2020-11-09 00:13:06  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 2475911155341713003410102006123104318978074189935b2372000032a30b000000002020463afe07211b00020f0f0f0f0f0f0f0f0f0f000002dc7b0f2475911155341713003410102006063104320619074168471b21ac0000329d0b0000000020204628ca07450f00020f0f0f0f0f0f0f0f0f0f000002dc7b0d2475911155341713003410102006153204317484074204808b277f000032a60c000000002020462a8c07211000020f0f0f0f0f0f0f0f0f0f000002dc7b102475911155341712003410102006163404314819074211237b277c000032a70c00000000203046470f07211a00020f0f0f0f0f0f0f0f0f0f000002dc7b302475911155341712003410102006263504261977074230797b2768000032b40c00000000203046296907211500020f0f0f0f0f0f0f0f0f0f000002dc7b312475911155341712003410102006363504227598074232281b1d6f000032bd0b00000000203046297107211600020f0f0f0f0f0f0f0f0f0f000002dc7b322475911155341712003410102006463504199274074251915b1367000032c70c00000000203046471007210e00020f0f0f0f0f0f0f0f0f0f000002dc7b332475911155341712003410102006483304192665074253981b197b000032c80c000000002120462956214a0d00020f0f0f0f0f0f0f0f0f0f000002dc7b342475911155341712003410102006563804163369074295063b2381000032d20c00000000203046650707211a00020f0f0f0f0f0f0f0f0f0f000002dc7b352475911155341712003410102007063804155124074325533b26a7000032db0c000000002030463d9107210b00020f0f0f0f0f0f0f0f0f0f000002dc7b36
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:12:31, lat: 4.53163, lon: -74.31656, speed: 23.0, course: 228.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:06:31, lat: 4.53437, lon: -74.28079, speed: 21.0, course: 344.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:15:32, lat: 4.52914, lon: -74.34135, speed: 27.0, course: 254.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:16:34, lat: 4.52470, lon: -74.35206, speed: 27.0, course: 248.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:26:35, lat: 4.43663, lon: -74.38466, speed: 27.0, course: 208.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:36:35, lat: 4.37933, lon: -74.38714, speed: 23.0, course: 222.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:46:35, lat: 4.33212, lon: -74.41986, speed: 13.0, course: 206.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:48:33, lat: 4.32111, lon: -74.42330, speed: 19.0, course: 246.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 01:56:38, lat: 4.27228, lon: -74.49177, speed: 23.0, course: 258.0
2020-11-09 00:13:06  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:06:38, lat: 4.25854, lon: -74.54256, speed: 26.0, course: 334.0
2020-11-09 00:14:06  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 28373539313131353533342c404a5429
2020-11-09 00:14:16  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 2475911155341712003410102007164004152257074365871b2774000032e40b000000002030462e9307211500020f0f0f0f0f0f0f0f0f0f000002dc7b372475911155341712003410102007264004128027074404373b327b000032f00c000000002030462e5507211700020f0f0f0f0f0f0f0f0f0f000002dc7b382475911155341713003410102007333204149169074435112b2da2000032f80c000000002020461b2807211000020f0f0f0f0f0f0f0f0f0f000002dc7b2a2475911155341712003410102007364004150359074452665b2e80000032fc0b0000000020304636bb07210e00020f0f0f0f0f0f0f0f0f0f000002dc7b392475911155341713003410102007423104153125074495266b2684000033040c000000002020462bf607210b00020f0f0f0f0f0f0f0f0f0f000002dc7b2d2475911155341713003410102007453204151739074517070b3083000033080c00000000202046178522761500020f0f0f0f0f0f0f0f0f0f000002dc7b2e2475911155341712003410102007464204148846074525859b3177000033090c00000000203046178522761700020f0f0f0f0f0f0f0f0f0f000002dc7b3a2475911155341712003410102007483304147185074528708b00000000330a0c00000000212046178522760e00020f0f0f0f0f0f0f0f0f0f000002dc7b3b2475911155341713003410102008183204147191074528726b00000000330a0b00000000202046178522760a00020f0f0f0f0f0f0f0f0f0f000002dc7b392475911155341713003410102008213204147181074528721b00000000330a0b00000000202046178622760e00020f0f0f0f0f0f0f0f0f0f000002dc7b3a
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:16:40, lat: 4.25376, lon: -74.60979, speed: 27.0, course: 232.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:26:40, lat: 4.21338, lon: -74.67396, speed: 32.0, course: 246.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:33:32, lat: 4.24862, lon: -74.72519, speed: 33.0, course: 324.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:36:40, lat: 4.25060, lon: -74.75444, speed: 34.0, course: 256.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:42:31, lat: 4.25521, lon: -74.82544, speed: 26.0, course: 264.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:45:32, lat: 4.25290, lon: -74.86178, speed: 30.0, course: 262.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:46:42, lat: 4.24808, lon: -74.87643, speed: 31.0, course: 238.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 02:48:33, lat: 4.24531, lon: -74.88118, course: 0.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:18:32, lat: 4.24532, lon: -74.88121, course: 0.0
2020-11-09 00:14:16  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:21:32, lat: 4.24530, lon: -74.88120, course: 0.0
2020-11-09 00:15:15  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 28373539313131353533342c404a5429
2020-11-09 00:15:25  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 2475911155341712003410102008250004147123074528747b0d780000330a0c00000000203046178622761300020f0f0f0f0f0f0f0f0f0f000002dc7b3c2475911155341712003410102008350204138776074586392b25a9000033170c000000002030463217070a1600020f0f0f0f0f0f0f0f0f0f000002dc7b3d2475911155341712003410102008450404181517075031171b259f000033220c000000002030462a6f070a1700020f0f0f0f0f0f0f0f0f0f000002dc7b3e2475911155341713003410102008423304174607075020550b2b90000033200c000000002020463217070a0300020f0f0f0f0f0f0f0f0f0f000002dc7b412475911155341713003410102008453304183949075033393b2a98000033230c000000002020462a6f070a1800020f0f0f0f0f0f0f0f0f0f000002dc7b422475911155341712003410102008483404193407075048200b3188000033270c00000000212046499a070a1000020f0f0f0f0f0f0f0f0f0f000002dc7b3f2475911155341713003410102008543204220771075082426b31920000332f0c000000002020462cbd070a0c00020f0f0f0f0f0f0f0f0f0f000002dc7b452475911155341712003410102008550504222729075086391b329f000033300c000000002030462cbd070a0d00020f0f0f0f0f0f0f0f0f0f000002dc7b402475911155341713003410102008513204207759075062572b33a70000332b0c0000000020204619fb20460f00020f0f0f0f0f0f0f0f0f0f000002dc7b442475911155341713003410102008573304233893075095909b2c99000033330c0000000020204647f507091600020f0f0f0f0f0f0f0f0f0f000002dc7b46
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:25:00, lat: 4.24521, lon: -74.88125, speed: 13.0, course: 240.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:35:02, lat: 4.23129, lon: -74.97732, speed: 25.0, course: 338.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:45:04, lat: 4.30253, lon: -75.05195, speed: 25.0, course: 318.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:42:33, lat: 4.29101, lon: -75.03425, speed: 31.0, course: 288.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:45:33, lat: 4.30658, lon: -75.05566, speed: 30.0, course: 304.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:48:34, lat: 4.32235, lon: -75.08033, speed: 31.0, course: 272.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:54:32, lat: 4.36795, lon: -75.13738, speed: 31.0, course: 292.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:55:05, lat: 4.37122, lon: -75.14399, speed: 32.0, course: 318.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:51:32, lat: 4.34627, lon: -75.10429, speed: 33.0, course: 334.0
2020-11-09 00:15:25  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 03:57:33, lat: 4.38982, lon: -75.15985, speed: 32.0, course: 306.0
2020-11-09 00:16:24  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 28373539313131353533342c404a5429
2020-11-09 00:16:34  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 2475911155341713003410102009003204242905075108454b1591000033360c0000000020204647f507091100020f0f0f0f0f0f0f0f0f0f000002dc7b472475911155341712003410102009050604253943075120640b22830000333908000000002030462cef07091800020f0f0f0f0f0f0f0f0f0f000002dc7b412475911155341713003410102009183204247271075159597b000000003341070000000020204655e807091100020f0f0f0f0f0f0f0f0f0f000002dc7b4d2475911155341713003410102009153204247287075159616b0000000033410a0000000020204655e807091200020f0f0f0f0f0f0f0f0f0f000002dc7b4c2475911155341713003410102009213204247351075159619b000000003341090000000020204655e807090e00020f0f0f0f0f0f0f0f0f0f000002dc7b4e2475911155341713003410102009273304247289075159585b000000003341080000000020204655e807091000020f0f0f0f0f0f0f0f0f0f000002dc7b502475911155341713003410102009303204247299075159599b000000003341090000000020204655e807091000020f0f0f0f0f0f0f0f0f0f000002dc7b512475911155341712003410102009343804247195075159777b157200003341070000000020304633c4070a1300020f0f0f0f0f0f0f0f0f0f000002dc7b4224759111553417130034101020093332
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:00:32, lat: 4.40484, lon: -75.18076, speed: 15.0, course: 290.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:05:06, lat: 4.42324, lon: -75.20107, speed: 22.0, course: 262.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:18:32, lat: 4.41212, lon: -75.26600, course: 0.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:15:32, lat: 4.41215, lon: -75.26603, course: 0.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:21:32, lat: 4.41225, lon: -75.26603, course: 0.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:27:33, lat: 4.41215, lon: -75.26598, course: 0.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:30:32, lat: 4.41217, lon: -75.26600, course: 0.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:34:38, lat: 4.41199, lon: -75.26630, speed: 15.0, course: 228.0
2020-11-09 00:16:34  INFO: [4a4c224b: jt600 < 186.102.26.91] HEX: 04247326075159630b000000003341080000000020204633c4070a1300020f0f0f0f0f0f0f0f0f0f000002dc7b522475911155341713003410102009363204246351075162126b109600003342070000000020204631f820141300020f0f0f0f0f0f0f0f0f0f000002dc7b53
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:33:32, lat: 4.41221, lon: -75.26605, course: 0.0
2020-11-09 00:16:34  INFO: [4a4c224b] id: 7591115534, time: 2020-10-10 04:36:32, lat: 4.41059, lon: -75.27021, speed: 10.0, course: 300.0

All communications are inbound "<" but none outbound ">". In addition, the device is reporting information that is already in the database and is information that is more than a month old.
Thank you in advance for your help

My guess is that some response is missing.

Thanks for the quick reply
The log is much longer, but all the responses are of the same type until there is a timeout, I have configured the timeout to short and long times but it is always the same behavior, only for "<" and not for ">".

Server responses are marked with ">", so it means you don't have any response. Do you have protocol documentation with info on what is expected in the response?

The truth of all the documentation that I have, I cannot find the format of the response that must be delivered to the device. The question arises because I am also testing with gt06 protocol devices and even the osmand and their communication if it is biodirectional "<" and ">". Is it normal that there are devices that do not need confirmation that the message was delivered? And if so, then the device must be configured so that it does not continue to send more historical information?

Is it normal that there are devices that do not need confirmation that the message was delivered?

Some devices don't require confirmation and some do.

And if so, then the device must be configured so that it does not continue to send more historical information?

Again, there is no single answer. Some device can be configured to require acknowledgement, some other not.

I found the following documentation:

Gps data (realtime/re-uploading/alarm data) No.17 device status:  byte1.bit5=1 upload  then  Server center: ACK this data by (P35)

Device status Instructions: 
  Example:

   After analysised the data and get the devcie status:　 20 E1
   pleaes don't convert device status to Decimal system.
    convert HEX  0x20E1  to binary system:
     byte2            byte1
‭    0010 0000          1110 0001‬
   from high bit to low bit , so bit7 at left, bit0 at right.
    so       byte1's bit0=1   indicates  located by LBS  .
               byte1's bit5 =1   
indicates this data need to be acknowledged by server side with (P35) command, otherwise, keeps uploading the same gps data.
              byte1's bit 6=1  strings inserted
              byte1's bit 7=1   motor lock.
           …
           Byte2.bit5=1  indicates back cap open

U02- Unvarnished transmission data
 When the device  uploads the temperature data to server center. Server center need to send (A20) command to acknowledge this data. 
e.g.
RAW data in HEX:
28373537303130313939382C5530322C332C312C33362C562C3233313131363136313531342C452C31303832322E303935382C4E2C323234392E393739382C36302CBEBE3502484EF3387308161123161504201657381F0E061611231533570B0265500C027434090203160A061611231533570D01D1014A000003A6EBEB29

I have a document in word with this information called "JT701T Device Integration Manual v1.1"

Please provide the full document.

I just uploaded the documentation to one of my development servers, it will be available for some time

Documentacion

Looks like the logic is pretty complicated. Different message types require different acknowledgement. If you need help with implementing it and happy to sponsor the work you can contact us via support email.

Yes of course, if you tell me what to do, tomorrow I will start working on this! What email do I communicate with?

Check support page.