Deviation 3.0.0 with OrangeRX R620 problem

Hi,

I'm new to this forum, and could not find answer to my problem yet, so if by any change there already is a topic please direct me.

I just installed Deviation to my Devo8S radio to be able to connect a OrangeRX DSM2 RX.
Never used Deviation or any DSM2 RX before, but have used other radios.

After installing nightbuilds from 24.Jun.2013, I could configure walkera RX, and after that could bind de Orange RX too.
I believe I have understand de menus, as I configures my V200D03 model (6ch heli flybarless).

Yet, whne I try to configure another model for the DSM2 protocol for fixed wing plane, I always get ch3 output equal to what I set on ch2 , even with ch3 not assign stil get ch2 signal.

I am not being able to isolate if this is a receiver default or a protocol bug. as this is the only TX and RX I have for the moment.

Have any one experienced this before ?

PS: just load nightbuild dated 2013.Ago.08 and the problems persists.

Thanks Vlad_vy,

but I've see that post already and I believe to be a diferente problem.
You can have a pick in this video

Pedro,
would you share your config file?
Have you looked at the channel monitor when experimenting with the different settings? Have you seen your changes correctly transmitted to the receiver?

Thanks for your comment rbe2012,

I've used a 4ch plane template, after I have selected dSM2.

but attached are 2 files I believe may be enough to simulate.
Channel monitor show good outputs, but my dought is about the output after modulation.
I believe there must be some code after computing the output value, in order to send to the transmiter.
Is there any chance to have some bug for DSM2 protocol ?
If nobody has complained then the most probable is that my OrangeRX unit is damaged.

A bug in DSM protocol is unlikely - a bug of this dimension would have been discovered a long time ago.
I am flying helis and flying discs with orange receivers and never mentioned problems like yous.
Your ini looks ok (besides a mix of ch2 and 3, but this is not important for the malfunction).

Have you tried to select other channels like 5 and 6 instead of 2 and 3? Just put the servos in the right place and change the config. I am quite sure that you will not have issues and your rx is broken (maybe a shortcut on the board? Even small metal particles can achieve this).

Thanks, RBE2012

in fact I have done tests in all channel, and no problem except that, no matter what in I send to channel 2 is comming out from ch2 and ch3.
So I also believe that this problem may be comming from the receiver itself.
A hardware problem, is for me unlikely (cut strip or shunt), as with a cut there should be nothing comming from ch3, and with shunt there sould be a "fight" between ch2 and 3 and the output should me messy willy operating both channels, which is not the case. Nothing directed to ch3 on radio is afecting ch3 output in the RX (or any other ch ).

My beste guess is that there must be a Bug in the RX software (now a day's everything has software ).

I found the problem!!!


rbe2012, you where absolutly right.
There was a welding blur between R11 and R12 (output resistores for ch2 and ch3).

Yet it was in a special way that allowed to have this behavier and not the one I would expect from a short.
As I dont have a photo, let me try to discribe...
Say pin2 of resistor is connected to servo lead, and pin1 is connected to internal IC.
the short was between pin1 of R11 (ch2) to pin2 of R12 (ch3), so the output from ch2 was always dominating.


Problem solved!

thanks for all your comments.
Pedro

Well done.