3DR SiK Radio RSSI MAVLink Message SysId = 51, uh! ;-)

[Bill Bonney]

Hi,

I'd never really though about his before, but the 3DR Radio return MAVLINK_RADIO msgs for RSSI using the sysid of 51 and component id of 68. Why is that?

I'm trying to decide how best to handle this case since users of AP2 want to see the messages displayed, but they get filtered out since AP2 only registers systems based on receiving an HeartBeat message.

One solution is to fix up message for sysid51/compid68 to the currently active UAS (the one under control when you have multiple UAS connected) or somehow register this bogus system, as a real system (though with no HB message on the system, AP2 reports its not alive, joy ;) )

Anyway. How as other handled the 3DR Radio Mavlink Radio Message case?

Cheers

Bill

[Bill Bonney]

Also to follow up, is there a way assign Sysid to the radios ?

Bill

--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Oborne]

the IDs are from

https://github.com/Dronecode/SiK/blob/master/Firmware/radio/mavlink.c#L51

they are sysid "3" and compid "D" they are hard coded

because they dont send a HB, i treat all Radio_Status packets as a property of the link/connection.

Michael

On Friday, 18 September 2015 10:09:53 UTC+8, Bill Bonney wrote:

Also to follow up, is there a way assign Sysid to the radios ?

Bill

[Bill Bonney]

Hi,

So, if you have more than one radio connected, there is no way to differentiate them then, ouch. I’ll have to think about how to add that in, wihtout messing with the multiple UAV support. Maybe a SiK udpate with assignable IDs and a HB would be the way forward in future.

Thanks for the link

Bill

[Michael Oborne]

The radio_Status packet is only injected into the serial link, not the wireless link, so there is only ever one anyway.

To unsubscribe from this group and stop receiving emails from it, send an email to drones-discuss+unsubscribe@googlegroups.com.

[Tom Pittenger]

Is that only on the GCS side or both sides?

To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.

[Bill Bonney]

The radio_Status packet is only injected into the serial link, not the wireless link, so there is only ever one anyway.

That’s not the case is AP2. Links are all connect to the MAVLinkProtocol receivedPacket object and it targets the correct UAS based on sysid. It doesn’t have 1-to-1 mapping of the UAS to a link.

Bill

To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.

[Bill Bonney]

The Radio mavlink packet is ‘reflected’ back from the 3DR Radio, it does not get transmitted over the link.