MultiWii

Thank you

E_T

Everything works fine in my opinion. I usually fly in the angle-mode. Just before I fly a looping I switch by remote control in the arm mode. After full throttle and roll stick to the right the looping starts. After the looping is finished I switch back to the angle-mode. When the remotestick (nick ...

Ok I testet the signals with an oscilloscope.

The receiver stops the signal after signal loss.
This explain why it works.
Now I just have to figure out why it did not go with 2.1 multiwii.

E_T

Ok I testet the signals with an oscilloscope.

The receiver stops any signal after signal loss.
This explain why it works.
Now I just have to figure out why it did not go with 2.1 multiwii.

E_T

Calibtrate ACC!

E_T

Look at the values the controller generates.

You can change thresholds here:

Multiwii.ino

(Because my controller generates cannel-values ​​in the range from 1055 to 1886)

// ******************
// rc functions
// ******************
#define MINCHECK 1100
#define MAXCHECK 1800


E_T

Look at the values the controller generates.

You can change thresholds here:

Multiwii.ino

(Because my controller generates cannel-values ​​in the range from 1055 to 1886)

// ******************
// rc functions
// ******************
#define MINCHECK 1100
#define MAXCHECK 1800


E_T

Look at the values the controller generates.

You can change thresholds here:

Multiwii.ino

(Because my controller generates cannel-values ​​in the range from 1055 to 1886)

// ******************
// rc functions
// ******************
#define MINCHECK 1100
#define MAXCHECK 1800


E_T

Back to the topic. E_TE_T i think the turnigy rx must send some grainy pwm signals to the mwii on signal loss. So the readout has some timeouts and increases the errorcounter to engage failsave. The gui is probably too slow or too filtered to show that. Cheers Kraut Rob Once I have time, I look at ...

The RX does not keep all levels the same, it stops the signal completely(*) . I have checked almost all the channels with a servo. All servos keep the last value. (The receivers from different manufacturers behave differently here) In my view, therefore, the software can not notice any loss of rece...

ardufriki wrote:Hi, finally I confirm your experiment. I dont know yet why it didnt work, but now does well. So I will remove my failsafe system at A6 pin.

It works with MW2.2 and w/o modifications on the rx. Good.

Next is to check if we can get a RSSI from this cheap rx.

Nice to read

E_T

In the video you can see that the receiver stores the last values, when signal is lost. After one second the failsafe-funktion are activated.

Here is the video that show it: http://www.youtube.com/watch?v=C9DrIlzB ... e=youtu.be

I can not explain now why the faisafe function starts?

E_T

Why does failsafe works? In the video you can see that the receiver stores the last values, when signal is lost. After one second the failsafe-funktion are activated. I have the Turnigy 9x wit the turinigy 8Ch receiver 2.4 Ghz. (original firmware) 5 Channels are connected to the board. The board is ...

In Multiwii 2.2 you can choose: (config.h) HK_MultiWii_SE_V2

E_T

I have this board: m The first 5 channels from the receiver are connected to the board. In the Multiwii-software i changed this: Config.h #define QUADX #define FAILSAFE #define FAILSAFE_OFF_DELAY 50 #define HK_MultiWii_SE_V2 GPS (Not connected) #define I2C_GPS #define MAG_DECLINIATION 1.18f Multiwii...

I have the Turinigy 9x V2 (original firmware) and the turnigy 8ch receiver v2.
http://www.hobbyking.com/hobbyking/stor ... ware_.html
No hardware were changed.



E_T

Multiwii 2.2 + Turnigy 9x (original firmeware) V2 + 8Ch receiver V2 failsave worked. I set in the controller Setting->Fail Saf -> All Channel are now F/S 000%. (I can not say for sure whether it is necessary) Then I started the motors and turned off the remote control. In my case, after one second t...