Devo 12s 3in1 / 4in1 RF module neat installation.

@dat, can you try freq coarse = 0, freq fine = +20..40?

The point is, freq coarse appears to be MORE fine than freq fine, so it does not add much value, only confusion.

All my CC2500 based birds I have tried (i.e. Skyartec WNCPX,V3 with X303V RX, XK K100, K123 and V977 with K123 RX so far) bind with my devo 10. They centre around -5 to -20, closed to centre enough that they actually came up without tuning.

I am using the little CC2500 module with reversed PA control. It covers the entire house at 1mW power.

If nothing works, it probably is something wrong with the RF module.

wasp09 wrote: All my CC2500 based birds I have tried (i.e. Skyartec WNCPX,V3 with X303V RX, XK K100, K123 and V977 with K123 RX so far) bind with my devo 10. They centre around -5 to -20, closed to centre enough that they actually came up without tuning.

I am using the little CC2500 module with reversed PA control. It covers the entire house at 1mW power.

If nothing works, it probably is something wrong with the RF module.

Can you please elaborate on the method you use to find the right freq for the very first bind? Thank you.

@blackmoon,
it does not require soldering if you use it in Devo with Devo 10 compatible socket (Devo 10, 6, 8, 12S, F4, F7, F12, F12E, 12E).
It does not require soldering to MCU pin for Devo 7E or Ultimate (with MCU upgrade).
Soldering to Devo 7E is straightforward and equips it with Devo 10 socket in which the module plugs in.
It does not require configuration change - if it is detected the code assumes you use the 4-in-1 module with fixed module assignment and PA on all RF chips.
It has an SPI flash on it, mainly for Radiolink AT9, but can be used in Devo F series to provide a normal size FAT filesystem.

Right now I'm struggling with F4 - my code makes it hang

@vmsda, can you paste the contents of your hardware.ini file here?

Vmsda ,

As I mentioned, they all came up with no tuning at all. Just don't forget to the press the bind button on the RX before activating the TX.

With the bird bound, alter the tuning setting until it loses bind, try the other direction until it loses bind again. Then I set the tuning at the middle in between the 2 values where binding is lost. So far the centre is on the negative side, not far from 0.

It is the way I used, but putting it in the middle may not be politically correct as victzh mentioned the setting is somewhat non-linear.

victzh wrote: @blackmoon,
it does not require soldering if you use it in Devo with Devo 10 compatible socket (Devo 10, 6, 8, 12S, F4, F7, F12, F12E, 12E).
It does not require soldering to MCU pin for Devo 7E or Ultimate (with MCU upgrade).
Soldering to Devo 7E is straightforward and equips it with Devo 10 socket in which the module plugs in.
It does not require configuration change - if it is detected the code assumes you use the 4-in-1 module with fixed module assignment and PA on all RF chips.
It has an SPI flash on it, mainly for Radiolink AT9, but can be used in Devo F series to provide a normal size FAT filesystem.

Mmmm.....Sounds very very good...
Waiting more info...

Actually, S-FHSS passes bind packets all the time, so for the XK K-110 I have it's unimportant when you press the bind button. As soon as it senses the transmission it binds to it.

For Skyartec, we definitely have to press the bind button on the RX to get the RX into bind mode if it was bound to another TX before. I have a stock Skyartec TX before I added devo 10.

You are probably right for XK, I did not watch carefully enough. Wonder why we need a bind button on the RX after all.

Devo 10 is my only XK capable TX. I cannot retest if I really need to press the button unless I get a new XK.

On RX - yes, you need to press the bind button. But the order of turning on TX first or RX first is not important.

On the stock Skyartec TX, it can only bind within about 1 minute of powering on and not later.... Not sure if the deviation Skyartec protocol does the same.

victzh wrote: ,,,
It has an SPI flash on it, mainly for Radiolink AT9, but can be used in Devo F series to provide a normal size FAT filesystem,,,

That's a very nice PLUS! Good for my F4.
Looking forward to the photos.

Judging by the code, Deviation Skyartec can bind in the first 6 minutes If you can try it and verify that would be nice. We can reduce this to a more reasonable 1 minute or so.

I did not test stock S-FHSS TX - I did not have the original when I was implementing it. There is no word in the documentation about it.

victzh wrote: Actually, S-FHSS passes bind packets all the time, so for the XK K-110 I have it's unimportant when you press the bind button. As soon as it senses the transmission it binds to it.

Spent a goodly part of the afternoon trying a bind on my XK-K110. No luck whatsoever. Gonna try one or two more of your suggestions, but seem to be running out of realistic options.

@Arnold, F4 is exactly what refuses to work with it right now

@vmsda,
your module is probably misconfigured or defective. To exclude the former you need to give us some info to decide upon.

Publish your hardware.ini file's contents here, and take a look at how the module installed - take photos of its soldering to the board.

No point in "trying" right now, nothing changed since your first try.

Hi victzh
yes , i have try fine math -127 to +127 with coarse 0 from The fist i begin setup,
i add +5 math up untill +127 , and -5 down to -127 step by btep , many many cycle rounds
just like in forum many people post ,
but it all failed.
when i fell tired that way , ~suddenlly~ , a thought float in my brain ,
try coarse , give it a chance , And ~~ bingo done. ^^
take 2 short video post on youtube
and some pic in here


<iframe width="560" height="315" src="" frameborder="0" allowfullscreen></iframe>

<iframe width="560" height="315" src="" frameborder="0" allowfullscreen></iframe>

Hi all,

I have a 3-in-1 module. I have wired the module, but I have not soldered it into the Devo 10. Want to use it mostly for indoor models.

What is the recommendation ? Should I just for forward ? Or should I buy the 4-in-1- model ? I do have plenty of 3117 3.3V modules and plans to use one to power it directly from the battery pack.

I have moved to use primarily the FlySky i6 due to smaller size/weight, good range, and low cost Rx. And the fact that we have iBus support in BetaFlight, and my iBus2PPM project will give me 10 channels PPM if I need it for APM/PixHawk.

Would it be relatively trivial for me to re-use the 3-in-1 module with a Rx and an Arduino for iBus -> module bridge - Talking the differnet protocols (E010 is my primary goal).

victzh wrote: @vmsda,
your module is probably misconfigured or defective. To exclude the former you need to give us some info to decide upon.

Publish your hardware.ini file's contents here, and take a look at how the module installed - take photos of its soldering to the board.

No point in "trying" right now, nothing changed since your first try.

First, the hardware.ini file (only lines which are not commented out):

extra-switches=3x2
enable-cyrf6936 = B12
has_pa-cyrf6936 = 1
enable-a7105 = A13
has_pa-a7105 = 1
enable-cc2500 = A14
has_pa-cc2500 = 1
enable-nrf24l01 = A15
has_pa-nrf24l01 = 1

img.rcgroups.com/http://i925.photobucket...64pQ4ZUDJEjEhUmQFPpA
The image is taken from the Classified section of RCGroups. The soldering you asked for is hardly visible, even with my own naked eyes. The wire leading to the MCU is soldered to the second pin from the bottom on the vertical righthand side of the MCU pin structure. When this saga started, the seller asked me to swap A13 and A14 in the hardware.ini; on power-up, the 7E complained that cc2500 was missing, so we changed it back to the way it is shown above.
Hope this helps. Many thks once again for your unstinting support.

victzh wrote: Judging by the code, Deviation Skyartec can bind in the first 6 minutes If you can try it and verify that would be nice. We can reduce this to a more reasonable 1 minute or so.

I did not test stock S-FHSS TX - I did not have the original when I was implementing it. There is no word in the documentation about it.

It definitely says 1 minute on the Skyartec user manual. That number is about right as the stock TX gives us a beep around 1 minute after power up.

6 minutes implemented in Deviation is error on the good side. It is fine for me. If it is too short it won't give enough time for old men like me.

You know, the Hisky RX times out so quickly, sometimes before I can put the bird flat on ground to calibrate correctly after plugging in the battery. I hate that.

Chances of picking up unwanted binds isn't too high as we have to press the button on the RX to bind.

I'll check the 6 minute thing back at home if I remember.

I don't have any other S-FHSS capable TX. If the binding packets do not overload anything, it is OK to leave the S-FHSS implementation as is.