On one of my helis using an IKON2 and HobbyWing ESC v3 the events list is showing all entries as Events Code "111" and Events Type as "Deceleration >= 16g". No one I have communicated with knows what this means. I don't want to have a problem out at the field with the IKON while in flight.
Thanks in Advance
Greg Newman PH:513-535-5614 Email gregnewman0922@sbcglobal.net
Hi Greg, what firmware version are you running on the FBL unit? Any crash or very hard landing recently, or has the unit been sitting un-used for a long period of time perhaps? I suspect that unless you are using auto-level or rescue, this shouldn't be an issue. However, let's see what Braindev comes back with. If it's a stuck accelerometer perhaps, then a few hard taps on the top of the case with your finger may well fix it.
Good morning
Thanks for the speedy reply ?
Answers to your question as follows.
The firmware version I am currently using is 3.3.039
Yes I did have a hard crash recently
I am not using auto-level or rescue at this time
A stuck accelerometer does make sense (PS...I tried rapping on the IKON and did not see any change)
I will try the rap on the IKON suggestion. Please let me know if Braindev comes up with. Thanks…Greg
so here is my last question. If the event log entries are filling up continuously as they appear to be, is the Ikon going go fall behind which may cause unexpected flight performance? in other words should I throw the Ikon away and buy a new one? or can it be fixed?
@andyoleary...so here is my last question. If the event log entries are filling up continuously as they appear to be, is the Ikon going go fall behind which may cause unexpected flight performance? in other words should I throw the Ikon away and buy a new one? or can it be fixed?
@andyoleary...so here is my last question. If the event log entries are filling up continuously as they appear to be, is the Ikon going go fall behind which may cause unexpected flight performance? in other words should I throw the Ikon away and buy a new one? or can it be fixed?
Hi Greg. The Events log is just a memory loop, once it is full, it starts at the beginning again, overwriting the oldest data. Filling the event log is annoying but will not impact on the behaviour of the FBL. However, the root cause may need further investigation, I would recommend you email your config (MTR) file and a flight log to customercare@msh-electronics.com and describe the situation and/or reference this thread. The DEV team normally see these posts too but it would probably be best to officially create a service ticket via email.