FW 3.2.010, Esc DropOut / Tail Twitch Issue

[toadiscoil]

Originally Posted by Thickfog

Hey Toad, on Tapatalk just touch the check mark in the upper right.

Thanks!


Sent from my iPhone using Tapatalk

[msallua]

Originally Posted by Pygmaeus

Subscribed!


What i did notice on your 700 flight is that your throttle input signal dropped at the same time which would cause you to loose power. Is this the same problem that was reported before?

I think yes..

Originally Posted by Crashalotjoe

Maybe it is related to the ESC telemetry.

Maybe

Now I disable the ESC telemetry in the G420.. but can't test the change until the next weekend

[msallua]

BrainDev,

If you check my signature you will notice that I have 2x Goblin 420 ... In my house I took the second G420 and the same thing happens to me in the workbench

You may notice the "ESC Power Output" dropout approx. in the seconds:

1) 163,10
2) 203.22
3) 229.50
4) 288.22

These 3 helicopters worked perfect with version 3.1.027 and Telemetry ON

Attachment CSV and Attachment MTR, of the second G420

I have already prepared the first G420 and the G700 without telemetry to test the next weekend .. For work reasons it is impossible to try them before.

[nflanagin]

Are all the CC's updated? When you look at the actual Throttle out, there's no drop.

[msallua]

yes, it's a telemetry problem

[yrjou]

I had no issue on FW 3.2 but met ESC Dropout issue 7~8 times after update to 3.2.101 and caused 4 times crash.
Logs capture attached.
Any idea about this issue on FW 3.2.101, it should be fixed....tight?

I am using Hobbywing Gov. Spektrum Satellite, No telemitry.

thanks

[BrainDev]

Originally Posted by yrjou

I had no issue on FW 3.2 but met ESC Dropout issue 7~8 times after update to 3.2.101 and caused 4 times crash.
Logs capture attached.
Any idea about this issue on FW 3.2.101, it should be fixed....tight?

I am using Hobbywing Gov. Spektrum Satellite, No telemitry.

thanks

This is a real fail safe.
And corresponds to a shot in which the frame rate rises indicating the loss of one or more signal frames.
Please check the wires of your satellite and eventually substitute it with a new cable.
You can try on bench to move the sat wire and check.
How many sat do you have? One or two?
Can you send your event file?

[yrjou]

Originally Posted by BrainDev

This is a real fail safe.
And corresponds to a shot in which the frame rate rises indicating the loss of one or more signal frames.
Please check the wires of your satellite and eventually substitute it with a new cable.
You can try on bench to move the sat wire and check.
How many sat do you have? One or two?
Can you send your event file?

Hi Brain,

Thanks for your quick replied.
Here is the log attached.

[OnTheSnap]

Originally Posted by yrjou

Hi Brain,

Thanks for your quick replied.
Here is the log attached.

As BrainDev noted you have failsafe and receiver failures all over the event log. Looks like a bad receiver or connection.

[yrjou]

Originally Posted by OnTheSnap

As BrainDev noted you have failsafe and receiver failures all over the event log. Looks like a bad receiver or connection.

Thanks all,
I will check my sat wire connection.

BTW, any concern if I only use one sat on my mini Brain2?

thanks

[OnTheSnap]

Originally Posted by yrjou

Thanks all,
I will check my sat wire connection.

BTW, any concern if I only use one sat on my mini Brain2?

thanks

Personally I would fly with 2 sats to minimize any rf shadowing and provide redundancy.

[eliasnjr]

I had this problem of cutting the ESC using a Brain1 on a Trex450 with two spektrum dsm2 satellites without telemetry. This is unfortunate and could not occur after a firmware/softwarr upgrade of a reputable brand.

Enviado de meu SM-J500M usando o Tapatalk

[msallua]

Updated manually to 3.2.010... , in the bench it's all OK now.

Going to the field in this moment to test IRL.

I give you my feedback later

fingers crossed!!

[Krager]

Originally Posted by msallua

Updated manually to 3.2.010...

Confusing statement.

Updates are always automatic. New feature allows update to be cancelled, but still automatic when it occurs.

If you updated ~to~ 3.2.010 then you're coming from the previous version which was known to have the throttle bug.

Not trying to give you a hard time, just seeking clarification.

[msallua]

@BrainDev


Following your recommendation, update the 3.2.010 firmware manually.

1)Goblin 420

First the good news of the Goblin 420, no dropout, no tailtwitch, no engine cutoff

I flew the G420 3 times and got 3 solid flights without problems, perfect.

Align 700e (two flights)

In the first flight .Good news.
No Esc dropout, no tailtwitch, no motor cutoff. It was a sports flight.

Now the BAD NEWS

In the second flight hard 3D flight, I did not have ESC Dropout, no tailtwitch.

BUT!. I had an motor cut-off .. land without problems because I master the autorotation (this issue was reported by other pilots)

I attached the Castle log, the flight number 5 of the castle was without problems, the flight 6 of the castle was in which I had the motor cut-off

I attached the Brain log. that was perfect and I attached the Brain log where I had the motor cut-off

I also attach the .MTR, EVENTS

Hope it helps to solve the problem

Thanks in advance

[Crashalotjoe]

Originally Posted by msallua

@BrainDev

Now the BAD NEWS

In the second flight hard 3D flight, I did not have ESC Dropout, no tailtwitch.

BUT!. I had an motor cut-off .. land without problems because I master the autorotation (this issue was reported by other pilots)

I attached the Castle log, the flight number 5 of the castle was without problems, the flight 6 of the castle was in which I had the motor cut-off

I attached the Brain log. that was perfect and I attached the Brain log where I had the motor cut-off

I also attach the .MTR, EVENTS

Hope it helps to solve the problem

Thanks in advance

If I'm reading this correctly, the Castle log is showing a throttle cut and is responding correctly but the Brain log is showing the throttle out increasing while it is trying to maintain head speed. It would seem that both devices are working correctly but there is a disconnect between the Brain and the ESC.

[Helihabit]

Today, several flights after last crash due to FW bug, the same thing happened again! The heli being again relatively close to me (sat antennas in clear sight), at ~3mtr/9feet hight the motor shut down. Again I just half flipped it backwards! I’m not sure if the motor signal was the only signal that got lost.
Frustrating!!!

Brain1v2/HWplatinum v4/SpektrumDX8 & 2x dsmx sat/FW 3.2.010

[Helihabit]

I opened up my TX and saw the connector of the antenna hanging loose. And then remembering the antenna got hit last time



I am 'glad' it hasn't got anything to do with the Brain

besides the one in my head

[BrainDev]

Originally Posted by Helihabit

Today, several flights after last crash due to FW bug, the same thing happened again! The heli being again relatively close to me (sat antennas in clear sight), at ~3mtr/9feet hight the motor shut down. Again I just half flipped it backwards! I’m not sure if the motor signal was the only signal that got lost.
Frustrating!!!

Brain1v2/HWplatinum v4/SpektrumDX8 & 2x dsmx sat/FW 3.2.010

This theread is only related to the Futaba S.Bus protocol and only when used with ESC Castle Creation that have the Live Link protocol active.

From the signature it does not seem to me that the radio used is Futaba but Spektrum.
As far as I know and as reported by all users the problems of all other protocols with all types of ESC have been definitively solved with firmware 3.2.010

[BrainDev]

Originally Posted by Helihabit

I opened up my TX and saw the connector of the antenna hanging loose. And then remembering the antenna got hit last time



I am 'glad' it hasn't got anything to do with the Brain

besides the one in my head

Okay, I read only now. Happy that you have found the real cause of the problem. In any case, I recommend you to manually reloading the latest firmware.