The system also requires information about the exact vertical axis rotation for the exact orienting of position - for instance after a vertical axis rotation - as well as for fast tilt adjustment (pirouette stabilization). Therefore the rotor gyro is also used for controlling the main rotor control.
The control signals given by the auto pilot naturally require the same composites as the control signals given by the pilots depending on swashplate linkage. Therefore a board mixer is necessary.
Any active mixer in the transmitter must be deactivated at the same time.
A pleasant side effect results for the installed gyroscope due to the availability of the pitch channel, which the conventional tail rotor gyro does not offer: A revo mix is also possible in the heading hold mode (pitch tailpiece rotor admixture). The revo mix equalizes torque changes during pitch changes already in the making and thus offers additional support for the gyroscopes holding force. This combination is optimal because the combination of heading hold and revo mix already reacts before yaw rotations occur, are measured and can be regulated again.
If the desired steering movements are not appearing at the head, for instance if they are going in the wrong direction or are completely unable to function, the most common cause is a false connection to the receiver (cable connection or channel definition), or hidden mixers are still operating in the transmitter.
These are empirical values from various tests for different models and linkage types.
Changes for individual models are necessary and belong to the basic set-up for this.
The connection cables supplied are designed for 10A steady load and 12A short-term peak current. There is no reason for concern.
Please look at instructions for connection variants.
In the case of an unstable tailpiece or if the tailpiece in only sluggishly steerable in one direction a number of causes are conceivable and most notably a gyroscope sensitivity which is possibly too low.
Yes, this is possible. Since every helicopter is different, to begin with no general value can be specified. And comparisons with possible previously used rotor gyros (for instance when it was still a flybar helicopter) are particularly useless. The conditions were entirely different before.
Furthermore the tailpiece sensitivity is very heavily dependant on the rotational speed. The higher the rotational speed the lower the required tailpiece sensitivity.
Modern MEMS gyroscopes operate in the devices. As all gyroscopes these are also subject to a temperature drift . A company-developed temperature compensation is lodged in the system to protect against these drifts as best possible.
The installed artificial horizon reacts to angle changes and to absolute neutral values. For a normal "heading hold" tailpiece the smallest neutral deviations would continuously add up and a remaining tilt would result. Furthermore, control signals would also add up and a one-time controlled tilt would be maintained. However, a fundamentally different algorithm is installed in the bavarianDEMON for this purpose.
The difference from a normal 3-axis gyroscope is explained as follows: Since a normal tailpiece continuously adds up control signals as well as its rotation measurement it gets stuck in every controlled position. It would not cancel a tilt. Two different functions operate in the bavarianDEMON horizon mode, namely the artificial horizon at one time and the control at one time which uses the horizon data and carries out an actual value/desired value comparison. This is again reversed during an inverse flight attitude so that the control automatically operates in the correct direction in the supine position and thus produces a stable equilibrium.
The fact that temperature drifts do not add up is due to the installed compensating control. If minor deviations occur due to temperature drifts, only temporary and minor angle differences arise. They can be conveniently balanced by simple control deflections in the horizontal mode, exactly like all external influences. Small control deflections are occasionally necessary anyhow in the horizon mode since a helicopter itself does not have any geographic fixed point even in the most precise horizontal position and always drifts somewhere.
In the horizontal mode it is important that after release of the control stick the horizontal position is constantly re-established. However, this is only applicable provided that instructions are followed.
There are two possible reasons here:
Supported are all current digital and analogue servos with default mid-pulse range (1.5 ms).
The heli systems since the X-series also support narrow pulse servos on the tail (not valid for 3A, 3D, RIGID, RIGID V.2).
A slight operation is recognizable or audible primarily for fast digital servos by the bavarianDEMON, even when the model is standing still. This is completely unproblematic and is due to either the output rate or due to small measurement fluctuations as they could appear with rotor gyros on the tailpiece servo.
The fact that 4 servos are now affected by this can of course boost power consumption of a receiver's rechargeable battery . However, in practice this primarily occurs during the flight. Then all "controlled" servos namely operate nearly continuously, i.e. more often than they would for "manual operation" of an average pilot for sure. This additional work is incidentally reasonably independent of whether fluctuations are already registered on the ground or not - only you just don't hear them in flight. The servo activity depends much more on whether control in flight works properly and if it is adjusted rather agile or rather quietly. If the servos also work easily on the ground, this is hence insignificant.
This is different if a "rough" servo vibration should occur. Reception disturbances are possibly at fault.
Yes, but only to a very reasonable extent.
An angle displacement occurs between the roll and nick axis in many rigid heads.
bavarianDEMON has a built-in virtual SP torsion for this purpose and thus the possibility of an electronic compensation.
In addition, RIGID stabilization automatically corrects a percentage of deviations. The original angle displacement should, however, constitute approx. 8-10° at most.
Alternatively the mechanical balance is formed by rotation on the swashplate driver, however, this is not always possible. You should also take care that the push rods are not standing too diagonal otherwise increased rotary loads would affect the driver.
Unfortunately - .NET Framework is the current and future basis for software development under WINDOWS. It is correct that the installation of .NET Framework takes a few minutes; however, this only takes place on the computer once and is then a fixed component of the operating system. All following application programs which use this (no matter small or large) are then installed quickly since basically only the executable program files must be copied. This also applies, for example, to new versions of the bavarianDEMON. .NET Framework is not an integral component of WINDOWS. However it is already partly preinstalled on new computers.
Upgrades: all currently offered upgrade options are only performed directly at Captron. This is due to the fact that the source code is handled or is reinstalled on the device. Understandably enough, this cannot be contracted out.
Updates: are made on-line for 3X and 3SX provided that at least firmware V.113 is installed on the device. The Rigid V.2 must be sent in.
In general this is not a system error but rather one of the following errors:
Yes, the FBL-electronics must simply be turned off via PC software for this purpose. All other functions remain preserved.
On the one hand the tilting of the swashplate for the gyroscope/direction test is severely dependent on the tailpiece sensitivity. The smaller, the smaller the deflections. Furthermore, mostly only very small deflections are necessary for a helicopter in order to maintain very agile behaviour. In other words the swashplate only requires very mild deflections for regulation operations.
With cable harness: Master BEC, if coupled with ESC, to the receiver and slave to the bavarianDEMON. If BEC is separate, then connect all connections to the bavarianDEMON.
Always connect all connections to the bavarianDEMON: this applies to all other variants. There is a gas outlet especially for ESC which also carries out tension
The reason for this is not the bavarianDEMON this itself but rather the shortest path to the servos. These are the main current consumers.
Yes, this works with modern transmitters with program mixers. Hence it is made possible to, for instance, place the rescue mode on a well accessible moment switch and at the same time to turn the pure horizon mode on and off via another switch and to even program various sensitivities where required, for instance on a 3-level switch.