XK K110 (S-FHSS) build for Devo 7E and Devo 10

My new XK K110 BNF has arrived, to get it to bind using Deviation EMU Devo 10 v5.0.0 (e4a91dc) I changed the Freq-Fine=0 in the ini (I will attempt to find the min and max today)...

Is there any way to tell if 6G / 3D modes are being correctly selected by my TX or is how it flies the only way to tell?

Been playing with "Freq-Fine=" and found the following with my new XK K110...


From this then I set "Freq-Fine=51" and the controls seem ok, does that mean I don't need to bother with "Freq-Coarse"?

Yes, I think you can leave freq-coarse alone. I know people used freq-fine successfully, but no one reported usefulness of freq-coarse yet. Internally, they are just two different methods to shift the central frequency of a channel. Apparently, one works better than the other.

is it just a difference in the frequency adjustmemt amount between the 2 settings victzh? as in say freq-fine adjusts in 0.5 steps and freq-course adjusts in 5.0 steps or similar? if not what's the difference between the 2?

Use the Source, Luke!

CC2500_WriteReg(CC2500_0C_FSCTRL0, fine);
CC2500_WriteReg(CC2500_0F_FREQ0, FREQ0_VAL + coarse);

'Fine' modifies FSCTRL0 - frequency offset register which is intended for dynamic tuning the base frequency. If you can receive signal on TX - you have telemetry, then the offset can be found automatically and written into this register. If not - you can vary it until successful. The least significant bit is 1587Hz (26MHz/16384), and the range is around +-202KHz.

'Coarse' modifies the least significant byte of FREQ set of registers. These registers define the base frequency - center of the lowest channel. The value of the least significant bit is approximately 397Hz (26MHz/65536), so it allows theoretically to tune the frequency +-50KHz. Not so coarse it seems! Also, because the initial value of the least significant byte is set to some value (defined by protocol) the actual range of modification is skewed - it's not centered around the default value.

So, the conclusion is - 'fine' is actually more coarse than 'coarse' and has better range.

thanks for the detailed reply bud , unfortunately my coding knowledge is very minimal, so while i'd love to read the source and understand it's not possible for me yet

K123 BNF arrived this evening. That is my only scaled bird.

My devo10 using the little CC2500 module with reversed PA control has no problems in binding with K123 at 0 adjustments. I adjusted it anyway. The window is quite wide and centre is at the negative adjuestment side. Good job Victzh.

I assume K123 RX is very similar to K110. Do we have the channel map? Looks like 3D/6G mode is on CH5. Does it have a tail gyro gain somewhere? CH7 and 8 does not seem affecting the tail. How about gyro/ACC calibration? The manual also talks about hover debugging, Would they use any of the remaining channels?

Thanks.

wasp09, could you do me a favour and try out my Model.ini I found (Can't remember if it was posted on this thread!) and edited slightly to better suite my requirements?

It is for the K110 but as you think the K123 is very similar it might work ok.

To calibrate 6G mode, once bound (Have channel 5 at -100%) I hold down both sticks for 3 seconds which gets the blue LED flashing then hover for a few seconds. Then land and hold both sticks down again until the blue LED stops flashing.
To calibrate 3D mode, (Channel 5 at 100%) this time hold both sticks down and out until the blue LED flashes fast and keep them there until it stops flashing (No hover required).

still cant bind my xk x100 with my moded devo 7e with the 3 in 1 module. Have tried almost everything. Any help guys??

D_an_W,

I figured out the calibations by sticks, believe it or not, from reading the manual included in the box. Thanks for confirming.

However I still don't know if tail gyro gain is adjustable and how. The "manual' seems implying CH5 does both mode switch and gyro gain. I put CH5 on a knob (AUX 4) but I don't think it affects the tail, It does change mode though.

Sure I would test your ini when I have a chance to test fly it.

Regards.
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Update;

I would say your ini mostly works.

+20 adjustment won't work for my devo 10 and K123. The centre of window is at the negative side. No adjustment is fine. Change it if it does not work for you.
I don't need 150mW transmission power. 10mW on my devo 10 would cover the little K123 to as far as I can see it. I have a small TX LiPo, have to save on energy.
Pitch scaled at 60 is too high for the K123. Manual suggests 40. The K123 has a very wide collective travel. It won't jam even if pitch curve is not scaled at all. However the motors won't be too happy and collective would be too sensitive if it is 50% more than we need.

+++++ update +++++++++++++++++++++++++++++++++++++++++++++++
Tried putting the K123 RX on my V977 today. 60% ptich actually turned out to be the right amount for the V977 head.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Many gauges/indicators on the GUI. Some of them show ?. Normaily I'll be too busy to look at the screen when flying my CP. I don't really care what ??? means.
Ini uses K110 icon which isn't included in the zip.
Throttle hold is activated when key is up on this ini. That is unacceptable (to me) as throttle hold on all my TXs is always key down to activate.

No luck at all binding to my XK DHC-2 A600 (plane) with devo 7e + 3in1. The controller light just blinks like there's no transmitter. I've tried all sorts of values for Fine/Corse. Wish there was a fix even if it involved replacing a crystal on the board?

@aleonp13, @koss can you make sure your CC2500 works with some other protocol? FrSky and Skyartec are the only other options.
Also, have you configured it correctly? No star '*' before protocol name in model page?
Leave coarse alone, just use fine to tune frequency. I'm thinking of removing coarse altogether or recoding it to be really coarse tuning.
Also you can try to change the TX id on the model page.

victzh wrote: @aleonp13, @koss can you make sure your CC2500 works with some other protocol? FrSky and Skyartec are the only other options.
Also, have you configured it correctly? No star '*' before protocol name in model page?
Leave coarse alone, just use fine to tune frequency. I'm thinking of removing coarse altogether or recoding it to be really coarse tuning.
Also you can try to change the TX id on the model page.

Nope no star on S-FHSS. I'm using 7-13-16 nightly and re-tested FrSky and it's still working. Just went up and down the range by 10 and the FC just blinks like nothing is there. I also tried other values people on this thread seemed to have luck with.

victzh wrote: @aleonp13, @koss can you make sure your CC2500 works with some other protocol? FrSky and Skyartec are the only other options.
Also, have you configured it correctly? No star '*' before protocol name in model page?
Leave coarse alone, just use fine to tune frequency. I'm thinking of removing coarse altogether or recoding it to be really coarse tuning.
Also you can try to change the TX id on the model page.

No star before protocol name, and don´t have any other models in this protocols, just know my V2x2 are working with the NRF... any sugestions on the id?? Do I have to reset the transmitter everytime I change the freq tunning or just re-init the S-FHSS?

Would be great to control it with my devo 7e cause the RTF transmitter really sucks...

i reset my transmitter every time when i went up/down by 10 "just in case" didn't help. i did try a few other random IDs also no help

wasp09 wrote: "swap_control_cc2500 = 1" was for the zips I posted before. When the code was checked in, the chief developer wanted it changed as other modules wouldn't have the swap_control issue but may make use of an option to distinguish between different makes. Hence from now on, we use "config-cc2500 = 0x01" for zips from new nightly builds (e.g. June 21).

We actually have "config-cyrf6936 = 0x01" and "config-cyrf6936 = 0x02" right after.

Today , i try thís modul Cc2500 with Devo 7e , install for devo 7e OK , but i can not bind any protocol , FRSKY ,SFHSS .. it do not work although i move rx near TX .

Just a quick note on the Devo 10 with a CC2500 module - with mine my SkyArtec helis will not bind if the tx is too close. I need to bind with the tx at least a metre away from the helicopter.

Don't know if this applies to other protocols but maybe worth a try.

"config-cc2500 = 0x01" is only for CC2500 RF modules with reversed PA/LNA controls. Don't use that if it works without.

For CC2500 based RX, don't forget to press the bind button on the RX unless you have bound it to the same TX/ID before. If your RF module is functioning correctly, don't put it too close to the RX especially when power is set to high. Theoretically that may damage the LNA on the RX. My CC2500 is set to 1mW for indoors, even 100uW covers the entire house.

Hi, I got the CC2500 SI4432cc2500 module for Devo 8s. How can I connect it to the transmitter? Thanks for the help

Try this thread:

www.deviationtx.com/forum/6-general-disc...ith-3-new-tx-modules