Devo 8s orange rx recievers

Hi All.
Anybody knows if the orange rx recievers range should work correctly with deviation release 3.0,0

Sometimes i am able to bind but most of the times it wont.
and if it does its highly unstable and responds badly to the tx

i currently have a orange rx 710 series

see below

www.hobbyking.com/hobbyking/store/__2068...iver_w_Failsafe.html

All my walkera r801 recievers work fine but ofcourse those are not dsm2

I use some R610 rx but more regularly I use the Lemonrx versions in a few foamies. I haven't tested range but I have found them very reliable on Devo8s on v3 and newer nightlies. I haven't tried further but I know they are good for about 600m my sight range.

humz strange cant imagen there are big diferences between the r610 and r710 series except for one extra channel

are you using any special settings ?

Not doing anything special, have 1 R610 in a wing, 3 Lemonrx in wings, and 1 Lemonrx on a 450 quad. I personally prefer the Lemonrx though no technical grounds why just gut feel better. When binding, make sure you bind long enough, the led goes solid initially, then off, then wait till it comes on solid again. If it doesn't come solid again rebind until you get it right then I normally set a fixed id.

humz strange how do you bind yours ?

i just use the bind button in the model settings.
but in my case the led never goes to solid Always remains blinking or goes in a sort of randomly blinking mode

Hi,

I mostly used Orange RX with my planes (2x R410 and 1 R415) and my Devo8S. I have a R600 somewhere, I can try it too if you need.

Never had problem at all with DeviationTx, which I use since version 2.1.1.

Here is the binding process I follow:
- plug the bind plug into the RX
- switch on the TX
- switch on the RX (it must blink rapidly but at a constant rate) Be careful that the RX is not to close to the TX. 1 or 2 meters is ok.
- click on the Bind button on the TX
- the LED should go solid on the RX
- remove the bind plug
- switch off the RX
- switch off the TX

Then:
- switch on the TX
- switch on the RX
=> must beep a little bit then after 2-5 seconds, the LED on the TX should switch on.

It you follow this process, and you never get a solid bind, your RX is maybe faulty. You should try to bind on another Orange or Spektrum RX to see if the problem comes from your RX or your TX...

Good luck !

thanks Bitone


seems like im doing it the right way
maybe im sitting to close to the rx ?

ledfreak3d wrote: thanks Bitone


seems like im doing it the right way
maybe im sitting to close to the rx ?

Could be that or you've got a faulty unit.

One more possibility: you could be in very noisy environment from a 2.4Ghz point. For example, if you're trying to bind close to a Wifi access point, it could bring some problem I suppose. So try to switch it off or get far from it. Or you have a microwave that is running each time you try to bind

But my advise would be to get a new R615 Orange RX from HobbyKing or a LemonRX 6 channels from lemon-rx.com and try it again with your Devo 8S. It would cost you less than 10$ and if you're lucky you could get an Orange one with fast shipping from a local warehouse.

And you will directly get your answer if the fault is on the Devo side (unlikely, as it works with Walkera RX) or on your current Orange RX.

Yea thats sounds like a good plan
ill try some more this evening when im home
and else ill just order a other rx when there back in stock
dont realy need it but always handy to have a spare specialy at those prices

Tested again Orangerx r710 does not seem to work or is detective
need to find a other dsm2 rx to test with

Wel good news the rx710 was faulty i orderd a new 610 and that one binds and works fine.

But

its seems the channels still get mixed up
i fly my devo 8 in mode 2
so my left stick is throttle but when binding to the orange rx
it thinks my right stick is throttle

even complains during power on that my stick is not in a safe position witch it issent because its in the middle
im prety sure im overlooking something

assign the channels in the following order:
1 throttle
2 Aileron
3 Elevator
4 rudder

or set the protocol to dsm first and load a template in the second step then the channels are automativ in the right order to the protocol

Hi,

For me is ok with :

www.hobbyking.com/hobbyking/store/__1882...2_4Ghz_Receiver.html

and

www.hobbyking.com/hobbyking/store/__2855...2_4Ghz_Receiver.html

links dont seem to work anymore

Thanks wil try that one

no issues with the devo recievers

Channels work fine now
just some minor issues to solve my throtle % display it no linked to pitch