Changes

Jump to navigation Jump to search
2,169 bytes added ,  7 years ago
no edit summary
Line 21: Line 21:  
===Can MICROBEAST PLUS be used with gasser helis, especially with RPM Governor and AttitudeControl?=== <!--T:64-->
 
===Can MICROBEAST PLUS be used with gasser helis, especially with RPM Governor and AttitudeControl?=== <!--T:64-->
 
We did do several tests with gas powered helis and we do not see any restriction on this. Gas motors produce very low frequent vibrations which normally can be filtered by the gyro sensors very well. So you should be able to fly with MICROBEAST PLUS and use AttitudeControl without issues on gasser helis. Also the RPM Governor function can be used with gas motors. Only restriction is that a rpm sensor with digital sensor output (PWM) must be used for proper function. Analog sensors like the Futaba GV1 magnet sensor or StatorGator which are often installed on gasser helis can't be used.<br />
 
We did do several tests with gas powered helis and we do not see any restriction on this. Gas motors produce very low frequent vibrations which normally can be filtered by the gyro sensors very well. So you should be able to fly with MICROBEAST PLUS and use AttitudeControl without issues on gasser helis. Also the RPM Governor function can be used with gas motors. Only restriction is that a rpm sensor with digital sensor output (PWM) must be used for proper function. Analog sensors like the Futaba GV1 magnet sensor or StatorGator which are often installed on gasser helis can't be used.<br />
{|style="text-align: center; margin-left: 10px; font-size: 90%; line-height: 100%; border-width: 1px; border-style: solid;"
+
<br />
 +
{|style="text-align: center; margin-left: 10px; font-size:small;"
 
|[[File:Gsr260_2.jpg|border|none|x150px]]
 
|[[File:Gsr260_2.jpg|border|none|x150px]]
 
|-
 
|-
Line 105: Line 106:  
{{QUOTE|'''Note:''' This firmware does not allow to use any other type of receiver, so [[Manuals:MB_Plus:Receiver_setup_menu_A/en|Receiver setup menu point '''A''']] will be skipped automatically when you enter Receiver setup menu! Otherwise this modified firmware does not differ from the default firmware.}}<br />
 
{{QUOTE|'''Note:''' This firmware does not allow to use any other type of receiver, so [[Manuals:MB_Plus:Receiver_setup_menu_A/en|Receiver setup menu point '''A''']] will be skipped automatically when you enter Receiver setup menu! Otherwise this modified firmware does not differ from the default firmware.}}<br />
 
<br />
 
<br />
 +
 +
===I get a red Status LED signal at Receiver menu point B===
 +
Red Status LED at menu point B shows that the system is not receiving valid channel data or no data at all. This can have several reasons:
 +
* Check that you've selected the correct receiver type / transmission protocol at Receiver menu point A.
 +
* Make sure the receiver's output is connected properly to CH5/DI1 input of MICROBEAST / MICROBEAST PLUS.
 +
* Make sure the transmitter is bound to the receiver and the receiver is receiving control signals from the transmitter. Keep some distance between receiver and transmitter.
 +
* Some Spektrum SRXL receivers require a special firmware (MICROBEAST PLUS only) which can decode the signals of these receivers. These receivers use a very unique coding which is not conform to the SRXL standards.<br />
 +
<br />
 +
When using a SRXL receiver we offer a free software to download that allows to connect your receiver to the computer with the USB2SYS interface adapter. With this SRXLViewer software you can make the output of your receiver visible and analyze the data output (if there is any), so you can find out why MICROBEAST does not accept the incoming signal. At the moment this software is only available for Microsoft Windows, you can get it [http://studiox.beastx.com/download/misc/SRXL_Viewer.zip here (click)].<br />
 +
<br />
 +
Just unzip the folder to somewhere on the Harddisk and start the .exe file (or it even should run from winrar, winzip, whatever, when opening it there).<br />
 +
<br />
 +
{|
 +
|align="center" | [[File:SRXL_Viewer1.jpg|border|none|x150px]]
 +
|align="center" | [[File:SRXL_Viewer2.PNG|border|none|x150px]]
 +
|-
 +
| style="width: 300px; font-size:small; padding-left: 10px; padding-right: 10px;" | Connect the receiver's SRXL port directly to the USB2SYS interface. The receiver needs some receiver battery or similar power source.
 +
| style="width: 300px; font-size:small;" | In the software select the COM port of the interface and click connect. Then you should see data output like this.
 +
|}
 +
<br />
 +
When the CRC is not correct or the data output is delayed or interrupted probably there is something not correct with the signal coming from your receiver. When there is no data output please contact the manufacturer of your radio system.<br />
 +
<br />
    
===MICROBEAST / MICROBEAST PLUS with single SPEKTRUM remote satellite on large helis=== <!--T:60-->
 
===MICROBEAST / MICROBEAST PLUS with single SPEKTRUM remote satellite on large helis=== <!--T:60-->
''Why is using a single SPEKTRUM remote satellite directly connected to MICROBEAST / MICROBEAST PLUS only recommended for helis equal or smaller than 450 size?''<br />
+
''Why is using a single SPEKTRUM remote satellite only recommended for helis equal or smaller than 450 size?''<br />
 
<br />
 
<br />
 
We say it is not safe to use a single remote satellite on anything bigger than TRex 450 size as the chassis on larger helis may hide the satellite in different flight situations. So you will loose direct sight between TX and RX more easily on larger helis. Additionally with large helis you fly further away than with small helis, so this doubles the risk of loosing the RF link when the satelite antenna is hidden. Using an EU Version of the SPEKTRUM TX even more it is very likely the RF link may get disturbed in such situations as these radios do not have so much RF power output. If using an US version of the SPEKTRUM radio with 300mW output power this can be different though. But also here we can't give a general rule, as the quality of RF link depends on many other factors like such mentioned above (Where is the satellite placed? Is direct sight to the TX in any flight condition guaranteed? How far do you fly away? Are there obstacles in your flying field like tress or houses? ...). So it's hard to give a definitive limit and we only recommend to use this setup on small helis as this can be considered as safe application.<br />
 
We say it is not safe to use a single remote satellite on anything bigger than TRex 450 size as the chassis on larger helis may hide the satellite in different flight situations. So you will loose direct sight between TX and RX more easily on larger helis. Additionally with large helis you fly further away than with small helis, so this doubles the risk of loosing the RF link when the satelite antenna is hidden. Using an EU Version of the SPEKTRUM TX even more it is very likely the RF link may get disturbed in such situations as these radios do not have so much RF power output. If using an US version of the SPEKTRUM radio with 300mW output power this can be different though. But also here we can't give a general rule, as the quality of RF link depends on many other factors like such mentioned above (Where is the satellite placed? Is direct sight to the TX in any flight condition guaranteed? How far do you fly away? Are there obstacles in your flying field like tress or houses? ...). So it's hard to give a definitive limit and we only recommend to use this setup on small helis as this can be considered as safe application.<br />
Bureaucrats, Administrators, translate-proofr
15,511

edits

Navigation menu