Unknown tag is the reason. Do you have protocol documentation?
Anton,
I act as an end user, unfortunately I do not have documentation on the protocol.
found only this guide http://base.galileosky.com/articles/#!docs-publication/galileosky-7x-user-manual
correctly I understand that the current protocol is not supported by the traccar server?
The protocol is supported, but some new parameters are not.
http://base.galileosky.com/articles/#!docs-publication/galileosky-protocol
0xFE Tag showing the presence of extended tags
Extended tags are sent as tag data 0xFE
Unfortunately the link doesn't provide any details on how to decode it or how to determine the length.
Good afternoon, the support engineer recommends that you apply for information on the protocol at the following address:
http://base.galileosky.com/articles/#!docs-publication/galileosky-protocol
where the protocol and its specification are described
Have you done that?
I'm not sure if there is enough information on the given page for the manufacturer's protocol to work and
your protocol for processing. as I understand it, this information is not enough for you to adapt to your implementation and support of equipment with this protocol?
Correct, as I said previously it doesn't have enough details about the extended tag.
the manufacturer is ready to get involved in solving this problem in the new year. I hope they are interested in their devices being distributed in alternative software products.
Dear
I contact the GalileoSKy 7x manufacture regarding to 0xFE and they mentioned to this link -> Packet protocol tags
BR
It still doesn't explain how to determine the length for the whole field. How do we know when it ends?
Anton, maybe the following protocol description will help to solve the problem with the tag length
Packet length is calculated from the head tag to checksum beginning. Tags are in ascending order. The data and the checksum are transferred in little-endian format (lower bytes are the first). The checksum is calculated for the whole packet including the header, length field and indicator of unsent data. The checksum is calculated by CRC-16 Modbus algorithm.
https://base.galileosky.com/articles/#!en-documentation/galileosky-protocol/a/h3_292074199
0xFE | Extended tags | Length is determined by the content of the tag
September 17, 2020 Description of extended tags is added
This link leads to a description of the extended tags:
https://base.galileosky.com/articles/#!en-documentation/galileosky-protocol/a/h3_1772820241
Hello!
Terminal: GalileoSKy 7x
incoming protocol & port: GalileoSky galileo 5034
when connecting the terminal, we get the following error:
Please, tell me what is the reason?