X20S HD Ethos 1.3.0 f bus TD MX 1.0.8 RF 2.2.2.
I Updated the brain and set up last friday, 18/12/22
receiver entered failsafe in flight at less than 100metres. Heli flew for a good 30 seconds enough time for it to do a big loop, but control never came back, recovery was held in during that 30 seconds!! failsafe was set to 'no pulses' on throttle and hold everything else, in hindsight this should off been set to recovery. I was unaware that F_BUS had problems with the brain and its cost me severely. (I too have used F port without issues.)
reverting to version 3.4.059 is a fix for now, Hopefully MSH will sort this quickly for those that have a machine to fly.
So i hope this saves someone else some heartache.
failsafe was set to 'no pulses' on throttle and hold everything else, in hindsight this should off been set to recovery.
If by "recovery" you mean "Rescue" or "Autolevel" you won't be able to set it to go off as a Failsafe. MSH team blocked this possibility claiming that it's not safe.
I'd love to hear about the workaround if someone knows to make it work though (except using classic PWM inputs)
I had the same issue and 2 helis failed in flight. FPORT was stable but I'm not sure about FBUS.
EQUIPMENT
Frsky Tandem 20S w/ Ethos
Firmware: Firmware Version: 1.4.2
ISRM (transmitter module): 2.2.2
Bootloader Version: 1.4.2
Flash: (8.0MB): System Bitmaps 1.4.0
Frsky Archer RS Firmware: 2.1.10
MSH Ikon V2 BT Firmware: 3.4.086
PROTOCOLS
ACCESS 2.4 (radio to receiver) FBUS (receiver to flight controller)
SUMMARY
For the last 1-2 years I've been using FPORT with no issues on my Tandem (and before my Horus). After I switched to FBUS is when I had issues.
Heli is flying fine, then the iKON logs an Rx Failure. The iKON goes into Failsafe and down comes the heli. Ouch.
The first time this happened, I presumed a bad receiver so continued using the radio and flew another heli. Then the exact same thing happened to a second heli a number of flights later.
EVENT LOGS
SPECTER V2
7;;1;PowerOn
7;;2;Coldstart
7;;3;Autotests passed
7;;52;Setup 2 activated
7;;4;Receiver Signal Ok
7;9;6;Logs Recording Started
154;9;57;Speed 2 selected
164;9;54;Governor was engaged
173;9;108;Elevator output limit reached
203;9;5;Good health (for 30 seconds)
216;9;158;Receiver Signal Off
216;9;157;Throttle gone in Fail Safe
216;9;55;Governor was disengaged
Crash
TRON 7.0 EVENT LOGS FROM CRASH
5;;1;PowerOn
5;;2;Coldstart
5;;3;Autotests passed
5;;52;Setup 2 activated
5;;4;Receiver Signal Ok
5;7;6;Logs Recording Started
11;7;57;Speed 2 selected
22;7;54;Governor was engaged
40;7;158;Receiver Signal Off
40;7;157;Throttle gone in Fail Safe
27;7;55;Governor was disengaged
Crash
Since, I've moved back to FPORT. I loose integration though. The weather went to crap so not many flights since.
Oh and forgot to mention... This only seems to happen once every dozen flights or so. Hard to reproduce on the bench!
Yes, seems there is quite an issue with FBUS at this present moment.
New X20S and TDMX (both latest fw) in FBUS mode on firmware 3.4.059 (since earlier in this thread Rik said to use that version).
This is really bad. Do we know if it's FBUS protocol itself, the receivers, or the Brain firmware?
The Archer RS I also tried in FBUS did not work with FBUS at all, but I think that is because I have the signal soldered to the inv. s.port pin as that receiver was one I soldered up back when Brain only supported inv. (technically uninv.) and not regular (technically inv.) F.port.
I also just tried with 3.4.086 (after video) and the odd twitches went away and no more logs telling setup change, but this is the firmware that according to the OP and some others is failsafing. And indeed, I already see one RX signal lost/failsafe on the bench.
Here is my config file 3.4.086
"I have the signal soldered to the inv. s.port pin as..."
Ya. You have to use the first 3 pins. GND, VIN, S.PORT. Inverted was from the early days. The first three pins work for FPORT and FBUS and you set the ikon accordingly.
It's normal to get those Receiver Signal Off and Ok in the events when it's on the bench and plugged into the ikon configurator app. I have been using FPORT with Archer RS for over a year and it's rock solid. You just get these events when plugged in. You don't get them when flying. So don't worry about that.
I'm talking about FBUS here. The mention of my Archer RS, F.Port, and the pins I used was just an aside as to why I didn't use the RS in this test case. It's pretty clear so far that the issue is with FBUS usage and not F.Port, as I also have been using F.Port for a long time. It's only recently when I got the X20S that I tried FBUS.
Going to solder up a new RS right now and try it on the same heli as all of my RS are currently in use or installed somewhere. Will report back.
As an side, why does the Ethos integration only work with FBUS and not F.Port or S.Bus/S.Port? So many people still have receivers that do not support F.Bus at all, and having to buy all new receivers just for integration to work is far from ideal. Especially since right now while we're seeing apparent issues with FBUS and Brain2. Is it an Ethos limitation, a Brain2 limitation, or simply that FBUS is the only one that has been made to work yet? I have so many receivers, three transmitters (one OpenTX and two Ethos) and lots of time, so if further testing is required I'm all about it.
Small update. ESC telemetry seems to cause problems when using FBUS. With latest RS firmware, .086 Brain firmware, and YGE xVT telemetry, I randomly get sensors lost from Brain and Integration stops working. Restarting the electronics by power cycling fixes it temporarily but it happens again a short time later. This seems to collaborate with reports from other users in other threads in this forum. Since you also reported that it doesn't usually happen on the bench, I think I got lucky last night when testing and saw a failsafe. Hasn't happened on the bench since with the TDMX or RS. I can't say I agree that RX loss/recovery on the bench is normal, as in 6+ years of using Brain2 I can't say I've ever seen that happen except when something was wrong.
Hello, I was able to reproduce this issue on the bench as well.
Brain2 went into failsafe when testing with FrSky X20
Using FrSky RS receiver on v2.1.10
X20s is on the latest firmware
Hobbywing Platinum v4 120a
Prior to the event I noticed a "sensor lost" audio alert and "Fuel" telemetry was lost.
About 30 seconds later Brain2 reported "Throttle Gone failsafe" and then reported "Receiver Signal Off"
When this occurred the FrSky radio also lost all ESC telemetry but receiver telemetry remained.
Can't seem to access my original MSH account and can't upload files on my new account so here is a google drive link to my config, logs and telemetry screenshot during the event.
drive(dot)google(dot)com/file/d/1cQD08MxBle44bP-3dmH2uq-EuMYrAFw1/view?usp=sharing
Happy to provide anything else if needed.
It looks like new ikon firmware just came out that might address all of this. Anyone want to go back to testing FBUS?
@cbarron I still have the same issue on 3.4.99.
Had a crash with 3.4.86 with a Arccher RS and changed the receiver thinking it was the problem cause. Also updated to 3.4.99 when connected to the pc to see the logs.
Almost had my second crash last week after updated to 3.4.99. With a new heli I was doing the first flight, when it was already on the ground the receiver entered in failsafe. Same issue.
We are sorry for your problems.@cbarron I still have the same issue on 3.4.99.
Had a crash with 3.4.86 with a Arccher RS and changed the receiver thinking it was the problem cause. Also updated to 3.4.99 when connected to the pc to see the logs.
Almost had my second crash last week after updated to 3.4.99. With a new heli I was doing the first flight, when it was already on the ground the receiver entered in failsafe. Same issue.
But the last and actual firmware is 3.4.103 released many day ago.
Although it is very difficult for us to make a diagnosis related to old firmware can you still send us the configuration and diagnostic files?
Thanks.
Drat. That was 3-4 months ago I was dealing with that and I don't have the log anymore. Sorry. I since went back to FPORT and off of FBUS. I do also stay current on firmware. I do plan to go back to testing FBUS again though in the future. FPORT has been rock solid.
