I am trying to create a swarm network with a couple of solos and monitoring their data on qgroundcontrol. However it looks like all solos have the same system id leading to a conflict on qgroundcontrol. I changed the sysid_thismav parameter on the solo using mission planner but now it looks like the artoo controller is unable to detect the solo and is hung up on waiting for solo
Can anyone please help me out? Thanks
Andre-K
January 6, 2019, 10:38pm
2
did you find a solution ?
1 Like
Tim_D
April 28, 2019, 4:06pm
3
The sysid is hard coded in artoo.
#include "hostprotocol.h"
class Mavlink
{
public:
Mavlink(); // do no implement
static const uint8_t ArtooSysID = 0xff; // default sysid pixhawk looks for
static const uint8_t ArtooComponentID = MAV_TYPE_GCS;
static const uint8_t SoloSysID = 0x01;
static const uint8_t SoloComponentID = 0x01; // default
static const uint8_t GimbalSysID = 1;
static const uint8_t GimbalComponentID = 154;
static const uint8_t RssiSenderSysID = 10;
static const uint8_t RssiSenderComponentID = 0;
static void onMavlinkData(const uint8_t *bytes, unsigned len);
static void packetizeMsg(HostProtocol::Packet &p, const mavlink_message_t *msg);
YM-98
August 29, 2022, 7:47am
4
Maybe you can write “param set SYSID_THISMAV 2” on a single terminal, and then roboot it. This can change sysid. Hope this can help you.
A.Larribau
March 28, 2023, 9:42am
5
Did you find a solution ?
A.Larribau
March 28, 2023, 9:42am
6
This didn’t work for me
