Heartbeat Packet Format about livox-sdk HOT 4 CLOSED

Hi,Ryan:
you are right, there is an error in section 2.1 , the size of CRC_32 should be 4 bytes!
thanks a lot!
and we will test your command!

from livox-sdk.

We tested your heartbeat command and sent it without recurring your problem according to the process specified in the sdk communication protocol. Suspected that the destination port of the heartbeat command you sent is incorrect, you can do the following verification:

1. Use the Wireshark tool to capture the communication network package between the Python3 driver and the Mid-40 sensor.
2. Confirm whether the destination port of the heartbeat command sent by the Python3 driver is the cmd_port in the handshake command.

• Wireshark Download Address:

• The normal Wireshark package is as follows:

from livox-sdk.

Thank you very much for the quick and helpful reply. My heartbeat commands were being sent to the correct destination port (65000) on the Mid-40. However, my error was that I was not sending the commands using my local/host port as was defined in the connection request command. I mistakenly thought that the connection request command only informed the Mid-40 as to which port to use when it transmits command acknowledgements back to the host. I didn't understand that it was also defining which port to be listening on for my transmitted commands (which of course makes sense now). I don't have a lot of experience with UDP but with your help here, it's starting to become clear! Thanks again.

from livox-sdk.

Hi,Ryan:
You can also try to develop the python interface based on our SDK core. We will soon provide the installation on Mac in the wiki.
Please inform us anytime if there is a question and you can share your progress with us!

from livox-sdk.