Naze32 Fun Fly - First Impressions

[Hands0n]

Who binds an RX with the throttle up?

Using RX failsafe - if you want your Naze32 (or whatever) to descend rather than fall like a stone you need some throttle below hover to do so. 

To rely upon the FC';s failsafe you need to be able to set the right conditions to trigger it

[Biffa]

One thing I learned when moving over to 2.4GHz from 35MHz was to bind anything with the throttle off, perhaps now with how things are quickly moving on people don';t take the time to stop and research a little beforehand.

I suppose that';s the iPod generation for you

[teslahed]

To rely upon the FC';s failsafe you need to be able to set the right conditions to trigger it

This is true. My openLRSng radio receiver has the option to stop PPM on signal lose (and restart on signal gain) and the naze32 detects the total lack of PPM signal and failsafes accordingly.

It works very well as long as your receiver can be configured to stop on signal loss in this way.

If your receiver continues to spam last known signals on signal loss then you';ll need to setup and use the radio receivers failsafe instead. It';s your only other option anyway i think.

[Hands0n]

Yes Chris, that seems to be the problem faced with the Orange R620 and other likely candidates.  They will failsafe to either throttle low (still sending a PWM) or a programmable present of each channel sticks and switches (again, still sending a PWM). 

So far I can find no means of setting the R620 to PWM off on RF signal loss.  If I could do that then the Naze32 failsafe could be used. 

Now, if I were using a Turnigy 9x with their FlySky receivers that do fail to PWM off on RF loss then I could use the Naze32';s software failsafe ...

I suspect this is where people are going wrong with their Orange RX - nothing wrong with the RX itself, but confusion as to what to set up and how.

[kilby]

I bound my 450 with throttle down around 920 (from memory) and it works fine with apm

I had been messing about to prove that a satellite could be used (only tested in the house) but when I put the full rx back on I didn';t rebind with a preset value.

Which brings in the added issue of if people decide to use satellites can they fail to preset values (I doubt it)

[teslahed]

You would probably have to use the naze32';s failsafe. Assuming the satellites can stop PPM on signal loss that would work fine. You could then use the Naze32 chrome config app to set the failsafe throttle levels that way.

If the satellites have no built in failsafe and can';t be set to stop sending signals to the flight controller on signal loss with the control transmitter - then they are best avoided because you wont have a failsafe of either type.

[kilby]

I would assume that they can';t, the only reason I played with it was as an experiment.

Once I get another Naze I will do a minimal setup doc so others can avoid some losses.

I guess I can do the spektrum and orange 2.4GHz bits

[Hands0n]

And I think GroundEngineer can add info also - I think it was him - about setting up the various Aux modes.  IIRC he had set up the two GPS functions on a single switch position. That was never going to go well. But who';d know who was unfamiliar with MultiWii?

[kilby]

I did notice that one and although I would have caught the issue it';s only because I have spent over 30 years working with microprocessors and usually spot ambiguous states.

Tbh it would probably be a good idea to cover the gotchas of the more common flight controllers.

Would save a lot of heartbreak and possibly some pain

[kilby]

Interesting posting on the MultiWii Forums regarding a flyaway by ummagwad http://www.multiwii.com/forum/viewtopic.php?f=22&t=2387&start=2200

Though I suspect damage to the Naze after his flyaway

[gzw]

I just had my naze32 fly away with the exact same conditions. Orange TX+RX, was hovering and handling just fine only 20 feet above me, and then stopped responding - I guess the last command it received was fly left and up - and so it did, forever.

Worst part? It was only my second flight with it, after ages of research and build time.

The even more worse part? I have a HawkEye UHF tx+rx, and was just doing a v basic flight test with this temporary Orange combo.

Never going to touch Orange again.

Here';s my tearfully produced "Missing" poster:

http://i.imgur.com/SvssOc6.jpg

[Hands0n]

@gzw - Sorry to read of your fly away. Its ghastly when that happens!  I hope you get it back.  Fingers crossed 

Which Orange RX was you using?  Did you have a failsafe set on it?

[gzw]

Thanks for the sympathy. I had the OrangeRx R620, and thought I';d setup failsafe, but maybe not.

[kilby]

Oh crap sorry to hear that (I now have a Tesla H as my small quad)

Mine was one of the Orange 8 channel dsm2 things.

What firmware version did you have installed as there was a change somewhere around the 10th July, that addressed some issues.

On my H I have a Spektrum 6210 with a satellite rx, they';re mounted at opposite ends and at 90° to each other (I got paranoid) it';s also the smallest spectrum rx that had failsafe capabilities (mine is currently set to behave like a rock as I';m only indulging in low level flights over grass till I get my confidence back)

[sevet]

This is true. My openLRSng radio receiver has the option to stop PPM on signal lose (and restart on signal gain) and the naze32 detects the total lack of PPM signal and failsafes accordingly.

It works very well as long as your receiver can be configured to stop on signal loss in this way.

If your receiver continues to spam last known signals on signal loss then you';ll need to setup and use the radio receivers failsafe instead. It';s your only other option anyway i think.

Why donfigure the RX to stop the PPM on signal lose with OpenLRSng?
Then you relay on the FC for the FS,
With OpenLRSng you can configure the FS with a click of a button to the current input state.

So on test flights I set it to kill switch, later i set it to land, and when confident with the multi I set it to RTL, all without touching any confs.

Also, didn';t follow the whole thread but setting the FS to have some lower than hover throttle is tricky.
Sure, when you loose signal on high altitude it will save you more than harm you.
But if you loose the signal not too high the risk of a motor jam (grass, upside down on the pavement....) making you loose all ESC if you can';t stop it in time is not worth it, even if it doesn';t jam, you might loose your battery.

Its a balance you have to make.

[kilby]

For those of you who own a Naze32 and especially those with one installed in the middle deck of a 250 H quad you have probably discovered that the usb connector is in the second most awkward place imaginable.

Well eBay delivered my solution today slightly irritating as the right hand one can';t be used because I have 90° pins installed for a buzzer and voltage monitoring.

http://pages.ebay.com/link/?nav=item.view&id=321431142277&alt=web

Would recommend that stockist of Naze boards offer these as an upgrade

[MultirotorParts]

you can just rotate the whole board 90 degrees and type in a cmd in CLI to reflect this, cant remember it off the top of my head

edit i think its

set align_board_yaw = 90

[kilby]

Yeah I know but then the ESC connectors stick out at the sides

Considering the minor cost I think I will buy another couple of pairs of these