HI guys,
We are flying our aircraft (VTOL) with two datalinks in it.
A main datalink is Sprintlink 1.4G 5W and secondary is Skydroid H16 GCS controller.
We have been operating with this setting for a while and there was no problem until today.
When we test flied our new aircraft with freshly equipped those two datalinks, aircraft triggered GCS RTL when it flew beyond H16’s range.
We set thr_failsafe = 0 so it won’t trigger any RC failsafe but warning on the hud and they continue flying with main datalink without GCS failsafe all the time.
We have QGC installed on our H16 controller. What we tested and found was that if we don’t initiate QGC on the controller, it won’t trigger GCS failsafe when we turn off controller on the test, whereas GCS failsafe triggers when we open QGC on the controller before turning it off.
So, it seems QGC is regarded as GCS, which makes sense actaully, but it shouldn’t trigger GCS failsafe when there is another GCS communicating with aircraft. Should it? It hasn’t happened to other aircrafts with same datalink setup yet.
FS_GCS_ENABL is set 1, heartbeat. Is there any chance that our main datalink is not emiting heartbeat properly and that’s why failsafe is triggerred when H16 is disconnected? In the QGC mavlink setting of the H16 controller, emit heartbeat is enabled.