I was handling this problem as well, and just when I was ready to commit the changes back to master I saw a few days ago it was solved:
not sure if it is in the stable release yet though. Tested with adrupilot and SITL and works great for me.
1 Like
The ADSB fix is in 4.0.1
1 Like
Similar issue on my endā¦ I think setting the system ID of the source and target has something to do with it, that is, in the Dronekit script thatās producing the fake ADSB messages. Iām still learning Mavlink routing so I may be wrongā¦
Iām producing ADSB messages with a python script using the pymavlink module. Theyāre being sent with the source system ID as 0 into one of the SITLās default UDP ports (14551). The SITLās mavproxy instance is logging the ADSB messages in its tlog, but MP/QGC are not displaying or logging in theirs.