This is a long one, but I need to describe the process.
My brother and I are both using the same rig for the most part, he’s using low KV motors and longer props. I’ve got about everything you can hook up to one of these…hooked up.
Trying to put as much info out as I can here:
RCT800 Hex Frames
His 320KV 15" Prop / Mine 380kv 13" both Tarot motors.
Both using Xrotor 40A ESC, although mine are a newer revision.
6S setup with Mauch Power Modules, His using Mauch BEC and mine using Mauch switching supply.
I have tried other power modules as well, however.
Both using Pixhawk - I have 3 different board revisions 3dr original, holybro 2.4.X, and a ?? 2.4.8.
Taranis 9+ using X8Rs
Both using the Craft & Theory Telemetry modules BUT THIS IS HAPPENING ON THE OFFICIAL FW. as well
as the C&T.
Mine using Lightware SF11 Lidar, PX4Flow, minimosd
Both Have FrSky FLVSS lipo monitor & FAS-150 current monitor.
Both using that little Naza LED controller, setup on RC passthrough
Both using Tarot Gimbal setup on RC passthrough.
I’ve made a gopro controller, which is using AUX 5 & AUX 6 relay functions.
Both have video xmitter.
Both have sik radios.
I obviously like to tinker.
Anyway…I’ve now reproduced this on all 3 separate FC’s.
Using both RC versions I eventually lose motor 2 on my hex setup. I say eventually because I didn’t specifically check this after the flash, as I didn’t expect it to be happening. I’m going to test this in a bit and start reflashing from RC2 up to RC5 because I don’t recall this issue below RC4.
Power is fine (I’m using high end Fluke meters). Both are using the Mauch for board power, and a Castle 5V bec for servo rail power. Both are steady at around 5.1V
I power up, let it run through it boot process.
Press the safety switch and all ESC’s beep, then go quiet like they usually do, except for motor 2 which continues beeping with that “haven’t got a throttle signal” beep.
This first happened to me last week & being a bonehead, I tested my FC over and over for hardware issues (resistors, caps, power, etc.) and actually replaced my FC thinking it went bad. Not even thinking about the fact I’m loading test software.
While I waited on it to arrive, I tried every possible thing to get it working. It does this with nothing but power and gps, safety switch, speaker. I even tried without the speaker and gps. Tried multiple different power sources. Reverted all accessory setting to default / not there states.
So I got my new FC Weds. I went through the full mission planner setup wizard and put 3.3.3 on hooked everything up, redid all my params (fresh set, from scratch, did not load backup) and everything is fine. Flew fine.
Loaded RC5. Put it aside and started on my brothers, since the 2nd relay function doesn’t work on 3.3.3, I loaded RC5.
Then I notice when I hit the safety for arming, I hear his motor 2 beeping…
Then I boot mine up, and it’s doing the same thing.
Then I notice that my 6 position mode switch isn’t responding properly. Its reading the wrong pwm values, and modes aren’t switching.
His is doing the same, and he’s lost control of the led module (simple hi/low pwm switching on RC passthru)
We can’t get gimbals to respond.
I’m freaking out thinking I burnt up his stuff, but then I know I’m good, I’m super excessively thorough, double checking etc.
So I reload 3.3.3 on mine, and the issue is gone. Radio pwm and signal anomalies are gone. All motors arm and spin.
Any ideas? Any other things for me to try? Edit: What specifically would you like me to post log-wise?
Edit: I also wanted to add that some settings are reverting after writing changes in MP. Specifically the camera related settings, servo/relay setting. I"m also getting some random locks in the connection, where it appears to just quit responding. I’ve only noticed this when the siks are being used.