I’ve been using TBS Tracer via SBUS successfully for some time, but decided to try it via CRSF to be able to use Yaapu and other telemetry. Everything seems to work (RC calibration page works, gimbal moves as it should, I can see telemetry info on my RC controller) but it rapidly connects and disconnects over and over again. From the Mission Planner messages it looks like the telemetry rate is changing? The Tracer TX and RX firmware are up to date.
With some more testing - it looks like it works better if I turn on the radio before the aircraft. It then does CRSFv3. But the problem returns if I power cycle the radio to simulate a failsafe, so I’m concerned about failsafe behavior, that it won’t clear.
Also, if I reset the aircraft from MP (preflight reboot shutdown) the FC loses all connection with the receiver. The radio and receiver are still connected - there’s a green light on the RX - but the aircraft acts as if the radio were turned off.
Screenshot from a start where the connect/disconnect stops once CSRFv3 is recognized:
I have seen this also on latest beta using crossfire on 6.19. Its a must to turn on radio first had a quad arm and go skipping merrily across the driveway doing that same exact radio failsafe behavior you have
there. This was using pixracer and was on 4.4.0 beta1
It looks like it’s working now. I tried factory resetting the RX and TX. I tried going back to 6.17, but that didn’t fix the issue (except for soft reboots). After reloading 6.19 it is working even if I power the transmitter after the receiver. Failsafe clears OK if I turn off and then repower the transmitter. All only tested on the bench so far.
I noticed in the 6.13 release notes that it said one may have to load the firmware twice because of updated protocols. It’s possible I went straight from 5.x to 6.19 on this setup and loading the firmware a few more times helped.
