Hey folks,
this topic is not directly related to AQ, but maybe I may ask nevertheless
I'm implementing MavLink communication into the STorM32 gimbal controller, and face some issues with the AQ's stuff.
* I have done now the PARAM_REQUEST_LIST, PARAM_VALUE, PARAM_SET commands. With APM's Mission Planner things seem to work perfectly, however with AQ's QGroundControl the parameter reading get's stuck in the sense that the Onboard Parameter window displays "Requested param list ... waiting" and doesn't show the parameters. The Mavlink Message Inspector shows that the heartbeats are working, as well as that all parameters were read since the PARAM_VALUE entry shows the last parameter. It seems as if the QGC is waiting for or expecting some additional message to arrive to finally accept the parameters. What is needed to get AQ's QGC to read AND show the parameters?
* I tried to sniff the communication with the AQ M4, so I connected the M4 to a terminal expecting to see it's heartbeat ... however, the M4 just remained silent. What's the reason or how/when starts the M4 transmitting heartbeats? For what message from QGC is it waiting?
* a more general question, when QGC sends a message, and the receiver notices that but something goes wrong, e.g. that a timeout occurs because not sufficient bytes are coming in, or a crc error is detected, etc., what is the receiver supposed to do? Just nothing? Sending out an error message?
(I'm not asking about those commands where an ack is specified, such as e.g. COMMAND_LONG)
muchos gracias, Olli