Changes

<br />

<br />

=Setup with StudioX= <!--T:3-->

=Setup with StudioX= <!--T:4-->

 

=Setup with StudioXm= <!--T:4-->

Please note that editing parameters is only possible when the device has initialized completely. So as long as the system is not in operation mode the button to open the "Parameters" section is greyed out. If it does not pass initialization sequence check the device status shown in the middle of the screen. If the system does not finish "Receiver init" check the receiver settings and radio setup. If the system does not finish "Sensor init" make sure that it is perfectly standing still and that power supply is stable.<br />

Please note that editing parameters is only possible when the device has initialized completely. So as long as the system is not in operation mode the button to open the "Parameters" section is greyed out. If it does not pass initialization sequence check the device status shown in the middle of the screen. If the system does not finish "Receiver init" check the receiver settings and radio setup. If the system does not finish "Sensor init" make sure that it is perfectly standing still and that power supply is stable.<br />

<br />

<br />

<br />

<br />

==Stick deadzone (E)==

==Stick deadzone (E)== <!--T:9-->

The deadzone defines the range around the very center of the stick in which MICROBEAST PLUS will not react to stick inputs. Unfortunately, some on the market available transmitters have the problem that when the sticks are brought back to the center position after a stick input, they aren’t exactly at the same center position as before. This generates a continuous deviation on the corresponding function, although the stick seems to be at mid position. This deviation is interpreted as a small input by MICROBEAST PLUS which leads to an unwanted drift on one or more axis. Especially you can see and feel this in hovering flight when the helicopter is turning slightly to one or another direction all the time. This makes it difficult to have precise hovering as it is hard to find a stick position at which no input is sent to MICROBEAST PLUS. This can be very dangerous as it may cause the helicopter to tip over when trying to take off or it can cause the pilot to loose control over the helicopter at all! So increase the stick deadband stepwise just until you don‘t see such effects. Note that as a result of large stick deadband there will be a wide range around mid stick position in that MICROBEAST PLUS will not react to stick inputs. This will make the control more inprecise. So if using “large“ or “very large“ deadband is necessary, we recommend to let your transmitter get checked by its manufacturer for damaged or worn out stick potentiometers.<br />

The deadzone defines the range around the very center of the stick in which MICROBEAST PLUS will not react to stick inputs. Unfortunately, some on the market available transmitters have the problem that when the sticks are brought back to the center position after a stick input, they aren’t exactly at the same center position as before. This generates a continuous deviation on the corresponding function, although the stick seems to be at mid position. This deviation is interpreted as a small input by MICROBEAST PLUS which leads to an unwanted drift on one or more axis. Especially you can see and feel this in hovering flight when the helicopter is turning slightly to one or another direction all the time. This makes it difficult to have precise hovering as it is hard to find a stick position at which no input is sent to MICROBEAST PLUS. This can be very dangerous as it may cause the helicopter to tip over when trying to take off or it can cause the pilot to loose control over the helicopter at all! So increase the stick deadband stepwise just until you don‘t see such effects. Note that as a result of large stick deadband there will be a wide range around mid stick position in that MICROBEAST PLUS will not react to stick inputs. This will make the control more inprecise. So if using “large“ or “very large“ deadband is necessary, we recommend to let your transmitter get checked by its manufacturer for damaged or worn out stick potentiometers.<br />

<br />

<br />

<br />

<br />

==Torque precompensation/RevoMix (F)==

==Torque precompensation/RevoMix (F)== <!--T:10-->

The advantage of always knowing the collective and cyclic inputs allows MICROBEAST PLUS to help the tail gyro holding the tail in position. It can precompensate for the torque variations on the tail rotor, just before any noticeable deviation occurs. This method of torque precompensation (RevoMix) relieves the tail control loop and improves the tail performance, especially when using MICROBEAST PLUS on helicopters with insufficient tail authority and/or extreme motor torque (e.g. overpowered electric helicopters) where the tail does blow out for a short moment when applying a sudden collective or cyclic input.<br />

The advantage of always knowing the collective and cyclic inputs allows MICROBEAST PLUS to help the tail gyro holding the tail in position. It can precompensate for the torque variations on the tail rotor, just before any noticeable deviation occurs. This method of torque precompensation (RevoMix) relieves the tail control loop and improves the tail performance, especially when using MICROBEAST PLUS on helicopters with insufficient tail authority and/or extreme motor torque (e.g. overpowered electric helicopters) where the tail does blow out for a short moment when applying a sudden collective or cyclic input.<br />

<br />

<br />

<br />

<br />

==Cyclic response (G)==

==Cyclic response (G)== <!--T:11-->

With point G can be set how aggressive the MICROBEAST PLUS responds to cyclic control commands (roll and pitch). This can reduce the usual uniform and linear control feeling of flybarless systems and approach it to the feeling of a flybared helicopter.<br />

With point G can be set how aggressive the MICROBEAST PLUS responds to cyclic control commands (roll and pitch). This can reduce the usual uniform and linear control feeling of flybarless systems and approach it to the feeling of a flybared helicopter.<br />

<br />

<br />

<br />

<br />

==Pitch boost (H)==

==Pitch boost (H)== <!--T:12-->

PARAMETER MENU point H allows you to setup the collective pitch boost function. This function causes that the faster you move the thrust stick, the more additional collective pitch will be exposed. This can be especially useful in 3D aerobatics when very rapid collective pitch changes are necessary for certain flight maneuvers, as hereby dynamically the required control stick deflection will be reduced. However, the maximum pitch value will not be exceeded.<br />

PARAMETER MENU point H allows you to setup the collective pitch boost function. This function causes that the faster you move the thrust stick, the more additional collective pitch will be exposed. This can be especially useful in 3D aerobatics when very rapid collective pitch changes are necessary for certain flight maneuvers, as hereby dynamically the required control stick deflection will be reduced. However, the maximum pitch value will not be exceeded.<br />

<br />

<br />

<br />

<br />

==Throttle response (I)==

==Throttle response (I)== <!--T:13-->

Use PARAMETER MENU point I to change the response of the internal Governor control. This determines how fast and how far the system will open the throttle when the rotor speed changes. Ideally the response is set as high as possible. If it is too low, the main rotor will speed up in unloaded conditions as the system reduces throttle not quick enough. Also the internal Governor will increase throttle very cautious when the rotor is loaded, so that the head speed will drop. If on the other hand the response is set too high, the throttle may stutter audible and the throttle will kick in very hard. So the motor speed will overshoot when the rotor head is loaded. This will make the headspeed even more inconsistent than with a lower setting. The height of throttle response highly depends on factors such as heli size (blade size), motor power and performance and/or the throttle reponse behavior of the speed controller (when flying an electric heli). If you need to adjust the throttle response, we recommend to start with the lowest value and increase stepwise just until you get the most consistent rotor head speed. Having a heli with good motor power and a fast responding speed controller (on electric helis) typically allows to have high throttle response values (up to "very aggressive" setting) which will give very consistent head speed. Helis with not so much power (small nitros, gasser, scale helis) prefer low throttle response settings for a softer throttle management.<br />

Use PARAMETER MENU point I to change the response of the internal Governor control. This determines how fast and how far the system will open the throttle when the rotor speed changes. Ideally the response is set as high as possible. If it is too low, the main rotor will speed up in unloaded conditions as the system reduces throttle not quick enough. Also the internal Governor will increase throttle very cautious when the rotor is loaded, so that the head speed will drop. If on the other hand the response is set too high, the throttle may stutter audible and the throttle will kick in very hard. So the motor speed will overshoot when the rotor head is loaded. This will make the headspeed even more inconsistent than with a lower setting. The height of throttle response highly depends on factors such as heli size (blade size), motor power and performance and/or the throttle reponse behavior of the speed controller (when flying an electric heli). If you need to adjust the throttle response, we recommend to start with the lowest value and increase stepwise just until you get the most consistent rotor head speed. Having a heli with good motor power and a fast responding speed controller (on electric helis) typically allows to have high throttle response values (up to "very aggressive" setting) which will give very consistent head speed. Helis with not so much power (small nitros, gasser, scale helis) prefer low throttle response settings for a softer throttle management.<br />

<br />

<br />

{{TABLEV5|Throttle response

{{TABLEV5|Throttle response

|normal

|normal

|slightly increased

|slightly increased

|aggressive

|aggressive

|very aggressive

|very aggressive

}}<br />

}}<br />

<br />

<br />

==Slow rampup speed (J)==

==Slow rampup speed (J)== <!--T:14-->

When using the internal Governor function this will not apply full throttle immediately when switching into idle up but will increase the motor speed slowly until the desired head speed is reached. At menu point J you can determine how fast this soft start occurs when the Governor is activated initially. The speed is given in number of revolutions by how much the rotor speed is increased per second. The higher the speed the faster your preset head speed will be reached. Please note that the given rates only are indicative. Depending on the response of the speed controller and the inertia of the rotor system it can actually take longer or shorter until the desired speed is reached.<br />

When using the internal Governor function this will not apply full throttle immediately when switching into idle up but will increase the motor speed slowly until the desired head speed is reached. At menu point J you can determine how fast this soft start occurs when the Governor is activated initially. The speed is given in number of revolutions by how much the rotor speed is increased per second. The higher the speed the faster your preset head speed will be reached. Please note that the given rates only are indicative. Depending on the response of the speed controller and the inertia of the rotor system it can actually take longer or shorter until the desired speed is reached.<br />

<br />

<br />

}}<br />

}}<br />

<br />

<br />

With the StudioX software/StudioXm App you have the option to disable the softstart feature, which will set the spool up rate to "0". This is necessary when using a speed controler with built-in softstart feature (but without headspeed governing!). In this case the system will add half throttle immediately and wait until the speed controler has finished the spool up. Then it will activate the governing.<br />

With the StudioX software/StudioXm App you have the option to disable the softstart feature, which will set the spool up rate to "0". This is necessary when using a speed controler with built-in soft start feature (but without headspeed governing!). In this case the system will add half throttle immediately and wait until the speed controler has finished the spool up. Then it will activate the governing.<br />

{{WARNING_QUOTE|Please note that you can't set a speed lower than 50 rps with StudioX because of the fact noted above. Setting the speed below 50 will be the same as setting it to 0, so it will disable the soft start!}}<br />

<br />

<br />

==Fast rampup speed (K)==

==Fast rampup speed (K)== <!--T:15-->

When using the internal governor function and you change the head speed in the transmitter in flight (i.e. by switching to a different flight mode), there will not be an abrupt change but the system will increase the rotor rpm with a given rate that can be adjusted here. This rate also determines how fast the rotor head speed will increase when reactivating the Governor after an autorotation maneuver (Autorotation bailout). In this case, when the heli is still in the air, the normal soft start (which is set at point J) would take way too much time for the rotor to speed up again, so we use this faster spool up rate instead.<br />

When using the internal governor function and you change the head speed in the transmitter in flight (i.e. by switching to a different flight mode), there will not be an abrupt change but the system will increase the rotor rpm with a given rate that can be adjusted here. This rate also determines how fast the rotor head speed will increase when reactivating the Governor after an autorotation maneuver (Autorotation bailout). In this case, when the heli is still in the air, the normal soft start (which is set at point J) would take way too much time for the rotor to speed up again, so we use this faster spool up rate instead.<br />

<br />

<br />

}}<br />

}}<br />

<br />

<br />

{{WARNING_QUOTE|When using a very fast rampup speed the throttle will be opened very quick. Especially when recovering from an autorotation maneuver this can cause the rotor blades to fold in or can damage the main gear in (especially electric models), so only increase the value stepwise and with care. With nitro helicopters in general using low values is recommended (even the setting "same as slow rampup speed (J)" can be sufficient) as here an abrupt throttle change from idle position can cause the engine to quit! Additionaly nitro motors react quite slow to throttle changes and it takes some time to speed up the rotor. So when the change rate does not fit to the mechanical speed up, it can happen that the motor is driven to full throttle during spool up by accident as the motor does not speed up immediately. For technical reason it may happen that the systems stays at full throttle in that case!}}<br />

{{WARNING_QUOTE|When using a very fast rampup speed in consequence the throttle will be opened very quick. Especially when recovering from an autorotation maneuver this can cause the rotor blades to fold in or will damage the main gear. So only increase the value stepwise and with care. With nitro helicopters using quite low values is recommended (even the setting "same as slow rampup speed (J)" may be sufficient) as here an abrupt throttle change from idle position can cause the engine to quit! Also nitro motors react quite slow to throttle changes and it takes some time to speed up the rotor. When the change rate does not fit to the physical speed up, it can happen that the motor is driven to full throttle during spool up by accident as the motor does not come to speed. In this case for technical reason it may happen that the systems stays at full throttle then!}}<br />

<br />

<br />

</translate>

</translate>