a little warning i think

[Ross Northcott]

Just thought i would let people know i had a issue with my beastx over the last couple of weeks on the set up (my fault).
On the test flight on the 3rd tank the beastx re-trimed in flight so as what the beastx thought was the swash plate level was in fact 6 degrees to the right aileron and caused a minor crash as was only 4ft of the ground, anyway repaired the heli went through the settings on beastx 3 times and re-tested, on the 2nd tank same happened again, but managed to save heli this time.
After 5 long hours of re-checking everthing i found the problem was i had set my tx as per normal with expo at 30% (on aileron,rudder & elevation)
for the maiden not relising the beastx perameter settings was on control behaviour !extreme! so i think it confused the beastx some how.
Once i removed the expo and choose the pro option all has been fine , although i may use the option where i can use my tx to set the expo.
Seemed a easy mistake to make with devostating consequences if i was not in just a hover.
This may not be the same on all beastx units but it seems to be my problem.

[Jamin_00]

I nearly had a heart attack reading that title lol

Glad you got it sorted though, phew

[waveydavey]

Nicely spotted. I think I set mine the same albeit with only 10%. Thanks for that. Setup to be redone before flying again methinks.

I have switched the control behaviour to the Tx as I found on extreme the flip rate was too quick and the roll rate too slow, the Tx way allows you to customise this.

[Ross Northcott]

Nicely spotted. I think I set mine the same albeit with only 10%. Thanks for that. Setup to be redone before flying again methinks.

I have switched the control behaviour to the Tx as I found on extreme the flip rate was too quick and the roll rate too slow, the Tx way allows you to customise this.

As i said in the post i think this is what the issue was, but i have since spoken to beastx admin and they say this is not possible, but some how it happened to mine, surely if the beastx is assuming it should have no expo but the radio is telling it there should be expo it can get confused.

[Ross Northcott]

Here is the latest from beastx admin,


Ok, than it will be very interesting what softwareversion you have on your System.

Early software version where very sensitive against vibrations and so during no motion (very static flying, hovering) it tried to compensate for this as the system thought the motion introduced due to the vibrations is a wrong trimmed system.

Softwareversion can be found out by using the Updater Software for the Microbeast (you need the USB Interface), by looking at the Microbeast Box sticker (only on newer devices), or by a special LED menu.

Special LED Menu showing Microbeast Version:

-in normal operational mode when microbeast has initialized and is ready for flying (not in setup and not in paramter menu)

-press and hold the button (on the microbeast) until "menu A LED" start flashing, still holding wait until "menu A LED" it steady further holding until "status LED" starts "blue flashing", now the "Menu LED's" shows the hardware version bitwise with 2 bitrows each 7 bits, where bit0 is "menu LED H" and "menu LED A" and bit6 is "menu LED N" and "menu LED G".

On all microbeasts until now only "menu LED H" and "menu LED A" should light up (on "blue flashing" = Hardware Version) which means Hardware Version 1.1 (the only Hardwareversion until yet, 06.sept.2010)

-press the button short, "status LED" will switch to "red flashing" showing you the Softwareversion Major (row "menu LED H" to "menu LED N") and Minor ("menu LED A" to "menu LED G")
here note down the "Menu LED" e.g. at a sheet of paper

-press the button short again and the "status LED" will start "flashing purple" showing the Software PatchVersion this is 14 bit long with bit0 on "menu LED A" and bit13 on "menu LED N"
note down the "Menu LED"s again

-press the button short again the "status LED" will go off and the "menu LED" will show you the Dataversion, there are again two rows "bit0" on "menu LED H" to bit6 on "menu LED N" giving the Dataversion and the second row is "bit0" on "menu LED A" to bit6 on "menu LED" giving the PatchdataVersion.

-press again and you are back in nromal operational mode

Now please give me the "menu LEDs" shown at Softwareversion Major, Softwareversion Minor and Software Patchversion display.

[Ross Northcott]

Ok here are results from above does anyone else have any?

the first step H & A light up, then push button again and red flashing light and letter H light up , push button again and purple light flashes and letters A,B,D, light up, push button again and the letter I lights up.

[ChrisB]

Expo cant cause that,could be vibes.

The Knight 3d i setup at the weekend was fine then the owner changed the tailblades and the model wanted to pull left quite a lot and trim would not stop it trying to do so,everyone at DMHC witnessed this.If you did not hold correction it would be on its side in about 3 seconds.

Cure,,,,,refit original tailblades the ones he fitted were causing vibes.FWIW i am using a bit of expo on my TX with unit set to extreme its fine.

V Bar can act similar to vibes although i never experienced it as extremely as the Beast wanted to pull over.

[Ross Northcott]

Expo cant cause that,could be vibes.

The Knight 3d i setup at the weekend was fine then the owner changed the tailblades and the model wanted to pull left quite a lot and trim would not stop it trying to do so,everyone at DMHC witnessed this.If you did not hold correction it would be on its side in about 3 seconds.

Cure,,,,,refit original tailblades the ones he fitted were causing vibes.FWIW i am using a bit of expo on my TX with unit set to extreme its fine.

V Bar can act similar to vibes although i never experienced it as extremely as the Beast wanted to pull over.

Defo not vibes the tail fin is as steady as a rock and the engine was set up by Eckman so no vibes apart from bedding in new engine.
Its just strange how when i removed the expo the heli trimmed itself and flew hands off for 4-5 seconds and then didnt move much.

[GravityKills]

I'm not convinced with the explanation. I'm afraid it's something else.

I witnessed a BeastX crash on Saturday, when a 500 went into a rainbow as soon as it left the ground. We suspect it didn't initialize properly, no gyro gain LED was lit up.

[ChrisB]

Defo not vibes the tail fin is as steady as a rock and the engine was set up by Eckman so no vibes apart from bedding in new engine.
Its just strange how when i removed the expo the heli trimmed itself and flew hands off for 4-5 seconds and then didnt move much.

The Knight showed no signs of vibes either but when the blades were swapped as a last resort the problem went away.......................or did it?

He has not flown it since.

[Eckchaz]

Glad you got it sorted mate... At least you wasnt a stupid as me.. I was trying to calm down my major tail wag on maiden through the Gyro gain menu system!!.. Only 30mins later did I realise I had to do it on my Tx.. DOH!!

[Mslater]

I've looked deeply into the workings of these systems including Vbar, 3G, Helicommand and a couple of others for a special project.

I can tell you that Expo would not be the problem, there's something else a mis.

The TX will send a position command to the servos (or in this case the beastx) Expo does not alter the command sent just the value of it at a certain stick position.

EG stick at 20% with Expo may send a 15% signal
(Same as stick at 15% with no expo)

You're not putting positive expo on by any chance ? Eg stick at 15% sends 20% signal ??

Are you lifting off with no cyclic control input ?

[G-Bru]

If you are running a belt driven tail it could be static?

G


Sent from my iPhone using Tapatalk

[Jamin_00]

Are you lifting off with no cyclic control input ?

What does it do if you do??

[tourerjim]

Not read all the posts so may have already been mentioned!
I fitted my Beastx Friday night & was flight testing Saterday morning with couple issues, thoughout the day I just could not resolve them so in the end I defaulted my TX & done a reset on the Beastx then I done a complete setup again" back to the field for another test flight & perfect but she was very relaxed so then whilst at the field 'in parameters' set cyclic & pitch to 'extreme' now she is awesome with no gain inputs other than tail 'gain' in TX.