Hi All, just wanted to check on any updates? Looking to update to 6.36 for my AR wing pro. Is that a good version to prevent the unbinding issue? Thank you
I havenāt had issues with 6.36 and updating to the latest AP firmware.
Iām still having the issue with the channel 5 and the pwm channel change as previous.
What I made is configuring mode 1 and 2 as FBWA.
Hi, Iām using a CRSF nano Rx in a sailboat. I have a Matek H743 Slim V3/Ardupilot rover and Radiomaster Tx16s with a CRSF module. I have used the Tx with several different nano rx in BF drones with no issue (well 1, but I fixed it with an rx reset). In the sailboat though, the Rx loses bind after one or two minutes on the water. I have to yank all the electronics out to get at the bind button and rebind, only to have the same thing happen next time out. From reading this thread, it seems the issue is likely related to running telemetry/yaapu script, and I need to update firmware to 6.36 (or should I use 6.42, the latest current beta?). Iām currently running 6.19 - the current public release. I guess this means Iāll have to update all my other TBS rx as wellā¦
Yes 6.19 has this issue, you should update. 6.42 seems like a good bet - I have updated all my CRSF TX/RX to this
I have to admit defeat.
Back in the summer I was convinced all was good with the system after update to 6.3 something but then started having intermittent disconnects again on 2 separate nano RX machines, but not loss of bind this time. It was kind of the last straw and I have changed everything to MLRS. Its just ideal having a toughbook running mission planner on a bluetooth link and all at a really good price.
Thanks! I did the update, it seems solid on the bench. Looks like I will have to wait until next Thursday for a breath of wind to test it on the water, here in the PNW!
yep. also had same issue but when update reciver and not to reset it. Also had some test modules, 6.42 had also this bug with unbind. So i stay at 6.35.
today i try, also the same problem, link lost, link recover in every two seconds. arduplane 4.5.7 and tbs 6.42 link 50Hz fixed
This is a different problem to the loss of bind problem, which was permanent without a firmware reset
Can you try the latest alpha to see if thatās any better?
6.40 Ardualpha tbs firmware or 4.6 ardupilot?
6.46 or whatever the latest TBS alpha is
i can see only 6.40 in tbs agent. maybe need test AGENT_ID
if you use the ARDU agent id above it will give you access to later releases
matek f405-se
tbs crsf nanoRx (pic32 previosly work fine on 6.19) fw 6.40 ardualpha 150hz fix link, CRSF Uart1 (DMA), MAVLink2 UART4. Region Open 868, 500mw max power.
after 7min stop working and red light on rx (like unbind)
after power OFF/ON FC with reciver, it automatic bind.
ardupilot 4.5.7
added.
install arduplane 4.1.2. I remember exactly that I had no problems with it, although it was a long time ago, I think in the winter of 21-22. Soā¦ more then 10min. with active mavlink, sometimes move sticks and sometimes changing params on phoneā¦ all good.
added. It redlight and lost bind ))) I change 150hz to 50 and it lost link. After power off and on reciver, link recovered. I try to repeat and next time i made redlight only at 4th change 150 to 50 and back to 150.
@andyp1per The 6.42 public version for tbs nano has been released, there seems to be a problem with ardupilot 4.6. I just switched to the tbs crsf system and I havenāt tested it with previous ardupilot versions. When I plug the battery directly, the fc doesnāt see the receiver. But the remote connects to the receiver. If I reboot the ardupilot from the missionplanner compass section without removing the battery, it sees the receiver. There is no such problem with the tbs 6.48 beta version, but I donāt know how reliable the beta is. I also experienced bind lost problems with the 6.19 version, and now Iām afraid to fly. I want to go back to the old frsky r9 system.
Can you start a thread in the 4.6 forum? I am flying 6.42 on 4.6 without issue at the moment. There is a momentary loss of receiver at boot but I think that is unrelated.