Assistance with protocol identification

joluasa year ago

Hello everyone,

I am having issues identifying the protocol that the device that I have is using. I was able to extract some logs and I performed some research on my end in order to try to figure it out on my own but I am not getting anywhere.

Here are some details of my findings:

  • The device says it is a 303F/G and it looks similar to Coban Tk303f
  • Most likely, this is a chinese clone
  • This doesn't appear to be a text-based protocol as the decoder always gives me the error Binary Hex can't be converted to Text
  • Each message coming from the device to the server is 486 characters long

I tested with the following protocols and bellow them is the message and error that I got for each test:

  • gps103
    Error message:
    INFO: [T1b6a50d3] error - begin 21, end 24, length 14 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
    Message from the device to the server:

    16030100ee010000ea0303f4ffe0098ecc216f79c428f88534609706c681ad02cdfc5ff0202df35a9273b22002d1a68e252c977cb9d5f1d4a0da62babe91fc4334e4b6e79794449d6df249750026cca9cca8c02bc02fc02cc030c009c013c00ac014009c009d002f0035c012000a1303130113020100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff010001000017000000120000002b00050403040303003300260024001d00205678cfdf57d8ee283a3a01ce9fccd4eb5c166416de9ac266a34c0d7b0ab70c57

  • tk103
    Error message:
    No error message, it went from connected to disconnected directly
    Message from the device to the server:

    16030100ee010000ea0303362ea55bc0afa03d690481e0ccbf89c10f304097b8353ab3ac410e2a8408149a2038fd27051aee4adb6b68c0329a53a5475fdc11ea2951774298d02efebe1f36580026cca9cca8c02bc02fc02cc030c009c013c00ac014009c009d002f0035c012000a1303130113020100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff010001000017000000120000002b00050403040303003300260024001d002051cd61fd6c4982de95488847f4db352d651db4aa0f840cffcceb50b2111b5755

  • gl100
    Error message:
    No error message, it went from connected to disconnected directly
    Message from the device to the server:

    16030100ee010000ea0303f2177e6a9da936515e28a5405d81f8111457ee3b476bc02afdaeaf3279f4eed120715d99295bf92daaaa3d4c73a346bf8c559323ef2415f506f5a3541f16384c8a0026cca9cca8c02bc02fc02cc030c009c013c00ac014009c009d002f0035c012000a1303130113020100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff010001000017000000120000002b00050403040303003300260024001d0020ba4f744a522c84d54a7c6d30d26fc5077e6bf2bd567abffc9b482c370268556a

  • gl200
    Error message:
    No error message, it went from connected to disconnected directly
    Message from the device to the server:

    16030100ee010000ea0303ca47b1e495fbfac092f2d6a6827dcaef8c094c484d7dfc0945f358e371070bd6208e6285b0e7a02756b02c66aa37a3a3db363ff2d262088bbd3a5ff2ac3758aad30026cca9cca8c02bc02fc02cc030c009c013c00ac014009c009d002f0035c012000a1303130113020100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff010001000017000000120000002b00050403040303003300260024001d00203bf2c7404ec54e12ac985bd2e924dd4538bdefd5956c7f600fa102ad16fc3629

  • t55
    Error message:
    WARN: Unknown device     +  3
    Message from the device to the server:

    16030100ee010000ea0303df5d298938d54e701aabac74a55178ae1398786f377371b93445212b51db784520d92ff97439c604260ef1a9e933762c9d4abb5ba42cee66432502bd110dba354b0026cca9cca8c02bc02fc02cc030c009c013c00ac014009c009d002f0035c012000a1303130113020100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff010001000017000000120000002b00050403040303003300260024001d0020d3129a3017bc816ff07f241293ede472836ac90a51cc469e0a6fefd5eebb3d40

  • h02
    Error message:
    WARN: Unknown device - 001d0020fd
    Message from the device to the server:

    16030100ee010000ea03032330c7508347c8391dd3fedfca71f727af56157fd86a1ee10f9cbe5a611a781420de2919ff1f546ed1ecaef19fb5b2f027f88a2bd54af5fc01ba3eff94c6eaabce0026cca9cca8c02bc02fc02cc030c009c013c00ac014009c009d002f0035c012000a1303130113020100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff010001000017000000120000002b00050403040303003300260024001d0020fd98daaa545e3c82991d6e99d151c73c46f1b81696de6981b73eb96e94fe572a

  • gt06
    Error message:
    No error message, it went from connected to disconnected directly
    Message from the device to the server:

    16030100ee010000ea0303d18ef320cf064cc66ef1b6cb4514e4a2322e5b6caa07989223cfb2a498da5c09209c8de1c5e7cf45fc542abc62130a58fe19810ad7c57c77d2c4dd2cc1c85a564b0026cca9cca8c02bc02fc02cc030c009c013c00ac014009c009d002f0035c012000a1303130113020100007b000500050100000000000a000a0008001d001700180019000b00020100000d001a0018080404030807080508060401050106010503060302010203ff010001000017000000120000002b00050403040303003300260024001d00206d8ee885dbd2f973476c5592534609ac758d4942705533a5f640001b39825360

I appreciate any assistance identifying the protocol. Thanks for any comment.

Anton Tananaeva year ago

It doesn't look like any common protocol I know. Do you have the protocol documentation?

joluasa year ago

Hello Anton,

Sadly I do not have the documentation for the device as it did not had anything in the box. I appreciate your quick reply.

Anton Tananaeva year ago

You should ask your vendor for the documentation.