You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing mavlink_udp.c with QGC, I noticed an interesting behavior:
Case 1: If QGC is already connected to another existing UAV, then messages sent from mavlink_udp.c will be displayed properly at QGC (e.g., you can see them in Mavlink Inspector).
Case 2: If QGC is freshly started with no previous connection, mavlink_udp.c will connect to QGC, but the messages sent from mavlink_udp.c are NOT displayed at QGC. One can tell that they are indeed connected, because mavlink_udp.c pop up with all the received messages from QGC.
Could someone please explain what I did wrong, or why this behavior is indeed normal? Thanks!
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
When testing mavlink_udp.c with QGC, I noticed an interesting behavior:
Case 1: If QGC is already connected to another existing UAV, then messages sent from mavlink_udp.c will be displayed properly at QGC (e.g., you can see them in Mavlink Inspector).
Case 2: If QGC is freshly started with no previous connection, mavlink_udp.c will connect to QGC, but the messages sent from mavlink_udp.c are NOT displayed at QGC. One can tell that they are indeed connected, because mavlink_udp.c pop up with all the received messages from QGC.
Could someone please explain what I did wrong, or why this behavior is indeed normal? Thanks!
The text was updated successfully, but these errors were encountered: