Hi,
Last flight with my Protos 700 I had a "warning" in flight, fortunately with no crash. I was flying normally and then suddenly governor was disengaged and engaged four times, and I don't know why. You can see this in the attached events log. And if you see the graph, TxThrottle remains constant while governor and Throttle out varies. How can this be possible?
Unit is Brain 2 HD BT with 3.2.018 firmware, Futaba 14SG Transmitter and Futaba R7008SB receiver. It has been flying flawlessly for several flights with same setup and I haven't had any crash in this heli, so I don't know what can happened.
Any help is greatly appreciated.
First of all, we would like to point out that it is flying with an old version of the firmware that, despite having been used without any particular problems reported for several months, has long since been superseded by new versions. We therefore suggest that you update both the firmware and the software to the latest versions.
For a complete evaluation we would need other information (ESC, BEC, Etc) which should be present along with numerous other information in the configuration file which however did not send us.
In the Events file sent, however, we see that a reset to factory default has been made to the unit so we imagine that the previous configuration file with which the unit flew was not saved and is no longer available and recoverable.
We also see that there is no correspondence in the event file with the flight log where the governor hooks to the second 39 and is switched off at the second 271. In the events we see nothing of all this. We also noted that the number of events in the file you send us is only 50 instead of 200 (typical).
But we see that the vibrations when the governor releases (127sec) are the highest.
From the vibration graph it would also seem that the blades are out of tracking.
We suggest you to register the QOS parameters of the radio signal (Fades, Frame Losses, Holds, Frame Rate, etc) and possibly ESC data such as temperature, instantaneous current and battery voltage (but we do not know which ESC uses and has activated its telemetry). The governor can be deactivated if there is a total loss of the radio signal exceeding 500 milliseconds. However, the ESCs also switch off and self-protect if the temperature exceeds certain maximum values or the instantaneous peak current exceeds certain values, or if the battery voltage drops over a certain value. It would therefore be useful to know how he configured the protection parameters of his ESC (which we do not know what brand and model it is).
We also suggest that you increase the frequency of flight logs recordings to 50Hz to have a greater resolution and detail of what may be the cause of the problem.
BR
Hi BrainDev,
First of all, thank you very much for your time, patience and efforts with my problem and Brain 2 community. I have been reading you for a long time at helifreak.com and your posts have always been very valuable and helpful.
I have updated my Brain 2 software and firmware to 3.2.054 as you suggested. I have changed my datalogging setup as you suggested, and I added the X-Y-Z acceleration if it's helpful. I have attached my new configuration, please tell me if it's OK or I have to change something.
I suspect that I attached a wrong events file, because I haven´t done a factory reset to the unit in a long time. So I have attached the events file again, with aprox 200 entries, so I hope is the right file now. I have attached the graph again and my ESC (Castle 160HV) configuration (both in Castle Creations and PDF format). Unfortunately, I don't have the ESC Flight log because the memory of the ESC is cleaned when it's full, sorry. But I don't think is a temperature problem, I fly 3D but not aggresive, and my ESC temps at the end of the flight are always low (I can keep my finger touching the ESC indefinitely after the flight). I don't use BEC, instead I use a direct 2S 1800mah lipo to power my RX and servos.
My setup is:
Futaba 14SG and genuine Futaba R7008SB receiver
KST BLS915HV cyclic servos and BLS905X tail servo
Align 800MX 440KV
Rotortech 710mm and SAB 115mm tail blades
Castle Edge 160HV ESC
Direct 2S 1800mah to RX
Brain 2 HD BT
Please tell me if I can do something more for you.
Regards and thanks in advance.
Note: Rename extension of Castle 160HV settings files, I have to do this because the forum doesn't allow to upload .pdf and .dat files.
Great. Thanks for the files.
From the events it results that there were two consecutive "Governor was disengaged" to the second 128 and 129 immediately followed both by "Governor was engaged".
From the flight log in those moments (128-129sec) you can see that Throttle Out brings the value of Throttle In (60%).
It's always difficult to make a remote diagnosis but it would seem that Brain2 in those moments stopped receiving the RPM signal from the ESC and then went into a condition of "Not Governed" by sending to the ESC the same input signal.
As I have already said, unfortunately at 20Hz the resolution is too low to see more.
Rather than logging the accelerometer values, which are useless for this problem, I would log the unfiltered 0-3000 RPM signal as it arrives on the GOV connector (parameter 11 shows instead the RPM signal filtered by the Governor).
Please check that the RPM connector is fully inserted into the GOV connector of the Brain2. To improve the tightness of this connector I suggest you to insert in the other two empty and free holes, two wireless contacts so that the mechanical seal of the connector triples and / or to lock the connector in the Brain2 by using hot glue placed between the connector and the case of the Brain2 (the hot glue can then be removed easily). Also check that the cable that goes from the ESC to the GOV connector of the Brain2 does not touch the edges of the carbon frame with the risk of short-circuiting temporarily (the carbon is conductive!). Your High vibrations at 127,2 Sec can be the cause of false contacts. Did you correct the tracking of your main blades?
It's a shame that you can't see the ESC log too to understand what the ESC "saw".
From the ESC configuration file, I see that it has not activated Live Link to read the ESC telemetry data. Consequently, you do not need to connect the Brain2 to the receiver's S.Bus2 telemetry connector, but simply connect to the receiver's standard S.Bus output. Can you confirm that you use the S.Bus output of the receiver and not the S.Bus2 output?
Thank you for reporting the attachments ".DAT" problem. Strange about the ".PDF" extension as we have often posted our PDF documents without any problems. For example, this is your file without extension modification:
Thank you very much again for your detailed response.
I have followed your advise and I have changed:
- I have hot glued ESC, Brain2 and Futaba RX connectors.
- I have isolated ESC cables from carbon fiber frames.
- I have changed datalogging to what you said.
- The tracking of the main blades is correct. But I have seen that one main blade was tighter (the main blade bolt) than the other blade, maybe that's the reason of the high vibrations. Now the 2 blades are very tight.
- I have changed from S.Bus2 to S.Bus. I thought that I could safely continue using S.Bus2 port without telemetry.
I hope everything is OK now 🙂