Hi @blutonomy,
Apologies for the confusion here - while the latest version of ping-protocol has a specification for auto-transmit functionality for the ping360 message set, there is not yet a released Ping360 device firmware that supports it.
The existing test code has been set up to help us evaluate an upcoming firmware (and to serve as an example in future, and for any current users with custom devices/drivers that support ping-protocol’s ping360 message set) although it really aught to be checking the connected device’s reported protocol version before deciding whether to use auto-transmit
control messages, or fall back to only manually looping through angles with the lower level transducer
control messages.
Those lines wait for and receive a data message into the message_device_data
variable, then perform some basic checks to make sure the message was actually received and is the intended one, then move on to the next iteration (discarding the data from the previous one in the process).
For non-test applications you’ll likely want to write some code to process and/or persistently store the received data as well