Trying to attach the events/logs but the forum post editor says "No more attachments are allowed today" so....
Had a few flights on a ikon2 mini in the Fireball Havok today, about 4 minutes in flipped to IU2 and was running for about 20 seconds and the heli just fell out of the sky. When I got to it it was on and I couldn't find anything mechanically wrong (beyond what happened from it hitting the ground). Checked the event logs when I got home and see there is
Event Code 151: Hot Restart/WarmBoot
What could cause the unit to reboot in the air? The pack still had plenty of juice left, was 3.85v post crash.
Also is there any manual for what the ikon event codes are, it's kind of frustrating trying to find answers when most of it is outdated on forums. An official guide to the telemetry and event codes would be awesome.
Good morning,
It is not always possible, but in order to "attempt" to make a diagnosis remotely, without holding the transmitter and being in front of the model to be able to do some testing and verification, we need more information.
So we need: the Flight Control Unit (FCU) configuration file (downloadable from the flight control unit using the "Save config. to file ..." command found in the "File" menu at the top left of the configuration software, saved while holding the controls sticks as indicated in the appropriate message), the Events file (downloadable using the "Save to File" button at the bottom of the Events tab in the DIAGNOSTIC section), and a Flight Log possibly just the one from the model crash.
If you cannot send these to us via forum, you can send them to us by attaching them to an e-mail to "customercare@msh-electronics.com"
Regardless of the files, what makes you believe that the FCU reboot did not occur when the model crashed on the ground but occurred in flight?
In flight with the FCU still running regularly, the ESC may have shut down the motor due to multiple factors (overcurrent protection, overtemperature protection, undervoltage protection), or false contacts of the ESC input or output connectors, or the pinion gear may have started slipping on the motor shaft, or the unidirectional bearing may have started slipping on the main shaft. These are all things that can happen when increasing the motor RPM by going from IdleUp1 to IdleUp2.
Did the ESC emit error warning beeps? With what frequency of repetition?
No mechanical failure was found after the crash?
It is useful to remember here that if during the emergency autorotation maneuver the rotor RPMs drop too much, the model control also slows down giving the feeling that even the sticks controls no longer work.
This is also why we need the three files.
If, on the other hand, you are absolutely certain that the reboot of the ESC occurred in flight, the problem may have been caused by a power supply voltage drop.
Can you tell us what size your model is and how many continuous amps the BEC you are using generates (or at least tell us what the model of the BEC is),
Have you verified that by moving all the controls to maximum (both minimum and maximum pitch, The servos never go to the stop generating very high draws?
Have you tried moving the cables from the battery to the ESC and the cables from the ESC to the flight controller?
Have you checked that the cables do not touch against the chassis edges, the insulators are not scratched and cannot short against the conductive carbon chassis?
Have you secured the connectors connected to the control unit by hot glue so that the model's vibrations cannot cause false contacts?
Have you tried holding the model on the bench to move all the controls for a few minutes to see if the FCU reset is repeated?
Regarding Events, a self-explanatory description of what that event number means is shown for each event code.
BR
SAB Fireball Havok, 280mm blades, 60A SAB (Hobbywing) ESC set to 7.4v BEC output, direct drive motor so no pinion/drivetrain. 6s 1250mah Battery. Flight 17 is during the flight, 18 is after the reboot on the ground.
The model was in level flight and I lost complete control, no response. When I got to it on the ground it was powered on and responsive again, only because of event log did I realize there was a hot reboot in flight. I've flown this model maybe 50 times without issues, nothing changed about the setup. There is no binding on any servos, the cables are all glued into the FBL and were all firmly plugged in post crash.
Thanks for the files.
Why there is no Transmitter brand, no Cyclic Control Servo Model, no Tail Control Servo Model, no Transmitter Mode selected on page 1 of the Wizard?
All products used are not listed? Which ones are used by you? Can you also tell us which receiver model you use?
From the events we note that in the majority of your flights (11, 12, 14, 16) you use only Speed 1.
When you used Speed 2 the problem occurred.
Since from the Flight Log graphs related to RPM we do not notice significant drops in rotational speed, it means that the assumptions made regarding the motor being shut down by the ESC that may have gone into protection have not occurred.
This leaves as the only possible hypothesis a false contact on the power supply that disconnected for a brief moment (otherwise if the disconnection had lasted longer a total restart of the unit would have occurred) or a short circuit of short duration.
From Flight Log 17 we see that the vibrations remain contained within limits even with Speed 2 but the frequency of vibrations obviously increases and this may have been the cause of the false contact on the connectors or the short circuit on the chassis edges.
Repeat the question: When you went to pick up the model after the crash, did the ESC emit error beeps? With what frequency of repetition?
From the original HobbyWing ESC manual (rebranded by SAB) we read:
1. Input voltage is abnormal: The ESC will measure the input voltage the moment when it's powered on. The motor will keep beeping "BB, BB, BB" (the interval between two BBs is 1 second) when the input voltage is beyond the normal range. The warning tone will not stop until the voltage turns normal.
2. Throttle signal loss protection is activated: The motor will beep "B-, B-, B-" (the interval between two B-s is 2 seconds) when the ESC doesn't detect any throttle signal.
3. Throttle stick is not at the bottom position: The motor will beep "B-B-B-B-" when the throttle stick is not moved to the bottom position.
4. Throttle range is too narrow: The motor will beep "B-B-B-B-" when the throttle range you set is too narrow (when designing this ESC, it requires that the entire throttle range you set cannot be less than 50% of the whole throttle range available on the transmitter). The warning tone indicates the throttle range you set is void and you need to set it again.
The type of warning tone (or led blink) emitted by the ESC after a fall it is ever important. Might help to know whether the power supply voltage to the ESC from the battery side was missing or the output voltage from the BEC to the flight controller was missing, whether the Throttle signal sent from the flight controller to the ESC was missing, and whether when the power came back the Throttle was zero or greater than zero or absent.
We then recommend that you do everything we have already told you in the previous post:
Try moving the cables that go from the battery to the ESC and those that go from the ESC to the flight controller and also the servo cables to highlight possible false contacts or possible short circuits.
Check that the cables are not touching against any edges of the chassis, the insulating sheaths of the cables are not scratched and stripped, and cannot short against the conductive carbon chassis (which is electrically connected to the motor ground).
Secure the connectors connected to the flight controller by hot glue between connectors and the top of the flight controller case so that vibrations of the model cannot cause false contacts (we recommend hot glue because it is easily removed if necessary).
Above all, try keeping the model running on the bench for several minutes with the engine running (Obviously, to be safe, without main blades and tail blades) constantly moving all the transmitter controls and cables to then see if the flight controller reset is repeated in the Events. Obviously without the wright of main blades and tail blades the model vibrations will be much smaller, but it is still worth doing this check.
Why there is no Transmitter brand, no Cyclic Control Servo Model, no Tail Control Servo Model, no Transmitter Mode selected on page 1 of the Wizard?
All products used are not listed? Which ones are used by you? Can you also tell us which receiver model you use?
They either weren't listed when I set up the model (~2 years ago) or they were added in more recent firmware upgrades, generally don't bother selecting new wizard options after the model is already setup and flying well.
I run TX16S mode 2 with a R-XSR receiver, the servos are the SAB micro servos that come with the kit. DS12-C x3 and DS12-T on tail.
Repeat the question: When you went to pick up the model after the crash, did the ESC emit error beeps? With what frequency of repetition?
There were no error tones, the model was powered on and seemingly normal on the ground, except for the damage that occurred from falling (broken blades, tail bent, ect). It arms normally still.
It sounds like the most likely cause is some temporary short/power disconnect, the main outcome here I think is that a capacitor backup bank would have probably saved me here, I'm not going to rebuild this model since it's already discontinued, but the electronics will go into something else, I'll just run opto-gaurds on it.
Thanks for the help, I know there's a tone of variables here just wanted to understand what the most likely cause would be.
