Running Aerobits TR-1F ADS-B/Flarm transceiver. I cannot find anywhere to set callsign in MissionPlanner. By design?
When loading the correct ICAO (integer) and SQUAWK (7000) MissionPlanner will populate the callsign field with the number 7000 for ADSB TX, where other aircraft publish “LN-ABC” style callsign. Quite annoying if there is no place to change this in parameters. Transceiver operate as normal when not interfaced with MissionPlanner.
You have to set the callsign and probably a few other things using AT commands, remember to enable Mavlink mode while you are there.
I believe the idea is drone operators cant easily change the callsign, it’s basically hard-set in the device.
Thanks. The ADSB is in fact preconfigured using AT commands and working fine up untill the point where we allow MissionPlanner/Ardupilot/Mavlink to take control. I am aware that connected to MissionPlanner using Mavling the unit will default to RX only on boot and TX would need to manually be started. I can confirm this behavior is what I see as well. Disconnecting Mavlink to ADSB and power cycling brings the unit back online with the same settings as set using AT commands. MissionPlanner Ardupilot is actively pushing the ADSB_SQUAWK value to where Mavlink Dialect: uAvionix expect callsign (Vehicle identifier (8 characters, null terminated, valid characters are A-Z, 0-9, " " only)
What ADSB and serial parameters do you have?
I imagine ADSB_ICAO_ID,-1 might be suitable - in the doco it looks like they leave everything at defaults, except the baud rate, and mavlink treats it like a receiver only.