Hi,
I am currently trying to use pymavlink to send adsb data to ardupilot (SITL) using adsb_vehicle_send(0xABCDEF, 477900000, 89790000, 0, 500000, 0, 100, 0, b"TEST", 0, 0, 1, 0x1234).
however, I cannot see that test plane on missionplanner.
Is there a way to debug this with SITL? maybe some logging to see if the message arrived?
SITL produces *.bin files as on-board logging.
You can send it and people can take a look.
We should see ADSB on those logs.
I’ve only ever done this using sim_adsb_count SITL Parameters — Dev documentation
Not exactly what you’re lookin for but might help debug any other configs. Good luck!
00000010.BIN (978.8 KB)
thanks for the info, I have attached my logfile. How could I check that myself in the future?
in this session I just sent the testplane message a bunch of times.
EDIT: im connecting pymavlink to the same “serial port” as the gcs at the moment, using mavproxy. I know the connection works, as it responds to arm/disarm commands, but is there something that could prohibit adsb_vehicle messages from working in that scenario?
I just found the error. I just tried it by connecting directly to the sim with another serial port and my testplane showed up! thanks for the help 
1 Like