Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heartbeat message in the MAVLink Message Inspector doesn't display frequency #5

Closed
Susurrus opened this issue Jan 24, 2012 · 2 comments

Comments

@Susurrus
Copy link

this message always appears as having a 0Hz frequency, both with the demo MAVLink file as well as with my own code that is transmitting at 1Hz and being recognized by QGC.

@Susurrus
Copy link
Author

So looks like the problem is that messages aren't being updated properly in the MAVLink Inspector widget. If you add the line qDebug() << QString("%1:%2:%3").arg(messageInfo[msg->msgid].name).arg(messagesHz.value(msg->msgid, 0)).arg(i); to line 101 in QGCMAVLinkInspector.cc and recompile you'll see what's happening. The interface isn't properly tracking when new messages are received and so all messages map to 0 (which is the ID of the heartbeat message) when they haven't been received and so every message that hasn't been received updates the heartbeat message in this widget. This is also why even when no communications line is configured that the heartbeat message still shows up with a 0Hz frequency.

I'm uncertain of the right way to correct this issue given the existing code. Obviously there needs to be a way to only track which messages have actually be received and only update those ones. I would imagine putting received messages into a queue and pulling from that on every update would be the best way instead of polling over all message types.

@Susurrus
Copy link
Author

Susurrus commented Mar 1, 2012

Fixed in 2a42532

@Susurrus Susurrus closed this as completed Mar 1, 2012
MatejFranceskin pushed a commit to MatejFranceskin/qgroundcontrol that referenced this issue Nov 21, 2018
Skipping (not allowing) Beta, Dev or custom firmwares.
dogmaphobic pushed a commit that referenced this issue Oct 11, 2019
Davidsastresas pushed a commit to Davidsastresas/qgroundcontrol that referenced this issue Sep 20, 2023
Changes to better allow custom version of the standard Herelink QGC version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant