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

I got the 3in1 installed in my devo 10,the FHSS protocol gives me the reinit option not bind,when I press enter it does absolutely nothing.I have 5.0 installed.Is this the norm? and is there any resolve?All fb is greatly appreciated.

there's an issue (found by either victzh or hexfet, i can't find the post and i can't fully remember) that's occuring with the cc2500 modules recently where the accuracy of the crystal used isn't as good as it needs to be (or the wrong value is used), but in the protocol options there are settings to adjust the frequency to correct for this, see cmPang's post here for the method >>
www.deviationtx.com/forum/7-development/...dule?start=580#50467

and yeah some protocols say bind, some say reinit, that's perfectly normal

HappyHarry wrote: and yeah some protocols say bind, some say reinit, that's perfectly normal

It's also meaningful - for at least some protocols. If it says "Reinit", then all it does is try to reinitialize the protocol, as if you'd loaded the model. If it says "bind", then it may re-initialize the model, but it will try and bind (as in the sense of establishing a permanent connection with that model). Some protocols don't support binding at all but will connect to any model looking for a connection, and some don't support connecting without first binding (aka "auto-binding"), and some do both.

Ok,so it's perfectly normal with the skyartech with the bind option to not attempt enabling unless it has something to bind to,correct?Your feedback is very much appreciated.

I'm having a strange problem with this protocol and my xk x100, I can get the quad to bind from freq-fine +22 up to freq-fine +97, if i pull the quads battery and reconnect it the quad binds again, but if i power cycle or press re-init on the tx it wont re-bind again unless I go into the options and move freq-fine up or down 1 digit. incidentally my frsky 'diy' rx's both bind and rebind no problem and without any changes in freq-fine/course. pb thinks the issue sounds like an initialization problem where the frequency is not properly reinitilaiized on reboot/reinit. let me know if there is anything I can do to help debug

It's highly probable. Can you file a bug and assign it to me, when I have stable internet I'll check it.

will do, thanks in advance for looking at it

C0ckpitvue 777 wrote: Ok,so it's perfectly normal with the skyartech with the bind option to not attempt enabling unless it has something to bind to,correct?Your feedback is very much appreciated.

Not sure what you meant? The button shows up as Re-init on the emu. If you have the CC2500 RF module installed correctly you should NOT have a "*" before Skyartec. Remember to short press the bind button on the RX to bind with devo the first time.

Thanks for the response wasp09,the star is not there so I know the modules are installed properly,I don't see a bind button on the Xk x251 that's the only model that I have now that's affiliated with the FHSS module.

C0ckpitvue 777 wrote: Thanks for the response wasp09,the star is not there so I know the modules are installed properly,I don't see a bind button on the Xk x251 that's the only model that I have now that's affiliated with the FHSS module.

please read Seby's post on RCGroup, there is a picture about bind button location.
www.rcgroups.com/forums/showthread.php?t=2630741

Thanks Dc59,physically looked inside the hole and stuck a toothpick down there and didn't feel the bind button.Ingot the Xk k110 on the way and will try this operation with that.Thanks for the link and the fb it is graciously appreciated.

@HappyHarry, can you check this build for the freq options bug. It is built from trunk, so don't pay attention to possible other bugs. If successful I'll submit a pull request against 5.0 version also.

db.tt/ePDeotux

is this in your own repo? if so which branch? if not can you post the changes or a diff?, as my 7e is an utimate7e so i'll need to pull and build it for that

I built you devo7e-256, it is here: db.tt/ciYdolGq
And just in case, I pushed it to my repository, master branch. It's in github.com/victzh/deviation

many thanks, I'll get it tested later today and get back to you

this change has fixed the issue with the xk x100, many thanks victzh

wasp09 wrote:

Nitro_123 wrote: @wasp09,
Sure send me the file. I'll solder the new module in and have a look

The code has been checked in. Hence it is available in nightly build from now on.
To activate reversal on cc2500 GDO0 and GDO2, add "config-cc2500 = 0x01" to modules section of hardware.ini.

wasp09 wrote:

wasp09 wrote:

Nitro_123 wrote: @wasp09,
Sure send me the file. I'll solder the new module in and have a look

The code has been checked in. Hence it is available in nightly build from now on.
To activate reversal on cc2500 GDO0 and GDO2, add "config-cc2500 = 0x01" to modules section of hardware.ini.

wasp09 wrote:

Nitro_123 wrote: @wasp09,

I tested the devo 10 version in the reverse way. With "swap_control_cc2500 = 1", the range dropped down to a few feet using my now "normal" CC2500 module. Without "swap_control_cc2500 = 1" or with "swap_control_cc2500 = 0", range returns to normal.


Thanks.

which is rigrt ? wasp09

"swap_control_cc2500 = 1"

or

"config-cc2500 = 0x01"


and insert hẻre ?
; enable-cyrf6936 = B12
has_pa-cyrf6936 = 0
; enable-a7105 = A13
; has_pa-a7105 = 1
; enable-cc2500 = A14
; has_pa-cc2500 = 1
"swap_control_cc2500 = 1"
; enable-nrf24l01 = A14
; has_pa-nrf24l01 = 1
; enable-multimod = A13

"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.

BTW, I have ordered an XK K123 BNF. It's on its way.

I guess that uses the S-FHSS protocol. I'll need the latest greatest nightly build which seems stuck at June 21. Or would it be the May 12 test build?