The details on the success/errors for the MAVLink protocols are now shown for each link as tooltips that are updated every 5s. Values are currently wrong and unsure why as of yet.
@ -230,6 +238,9 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
@@ -230,6 +238,9 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
emitprotocolStatusMessage("MAVLink Version or Baud Rate Mismatch","Your MAVLink device seems to use the deprecated version 0.9, while QGroundControl only supports version 1.0+. Please upgrade the MAVLink version of your autopilot. If your autopilot is using version 1.0, check if the baud rates of QGroundControl and your autopilot are the same.");
@ -391,8 +402,8 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
@@ -391,8 +402,8 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
{
// Increase receive counter
totalReceiveCounter++;
currReceiveCounter++;
totalReceiveCounter[linkId]++;
currReceiveCounter[linkId]++;
// Update last message sequence ID
uint8_texpectedIndex;
@ -412,7 +423,7 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
@@ -412,7 +423,7 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
if(message.seq!=expectedIndex)
{
// Determine how many messages were skipped accounting for 0-wraparound
int16_tlostMessages=message.seq-expectedIndex;
int16_tlostMessages=message.seq-expectedIndex;
if(lostMessages<0)
{
// Usually, this happens in the case of an out-of order packet
@ -423,22 +434,22 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
@@ -423,22 +434,22 @@ void MAVLinkProtocol::receiveBytes(LinkInterface* link, QByteArray b)
// Console generates excessive load at high loss rates, needs better GUI visualization
//qDebug() << QString("Lost %1 messages for comp %4: expected sequence ID %2 but received %3.").arg(lostMessages).arg(expectedIndex).arg(message.seq).arg(message.compid);