Advanced Search

SeByDocKy wrote: Do you need also some informations from the RX part ?

More info is almost always a good thing. A couple SPI traces from the receiver would be interesting too - see if it's receiving anything at all from the Devo and what a successful bind looks like. But can't offer any hope it will help with binding to an nRF chip...

hexfet wrote: Here's the better translation of the XN297 manual

Do you need also some informations from the RX part ?

Here's the better translation of the XN297 manual

A little update on the issue:

The little hack mentioned above works, but has its quirks. I've never been able to go into "flip mode" and sometimes, especially after a crash, the quad goes crazy. Shooting off in any direction, random flips, stuff like that. So I can fly the quad but it's not really a lot of fun.

Then I acquired a Devo8s (which I absolutely love, btw) and that's when stuff got really weird. I put in another nRF24 module and it behaved exactly like the one in my module.
It binds the quad successfully but doesn't know it, and even the hack I did on my module works exactly the same (including the quirks).

Right now I can't come to any conclusion other than that both of my nRF24 modules are faulty or at least somewhat different to what everybody else is using. Which isn't total nonsense as I bought them as a pair quite a while ago. Or I made the same wiring error twice, and I really don't want to believe that.

PB mentioned somewhere that the nRF modules can be very sensitive to 5V, and come to think of it, both of my modules may well have been exposed to 5V a few times in the past.

I've ordered a whole set of new modules plus a bunch of multimodule boards, so I'll see how that goes.

SeByDocKy wrote: The specific green edition

Might get one when they have them in stock.

Turns out google translates pdf files - amazing. Here's the link to the XN297 manual . Strangely the translation seems to be breaking halfway through now. I got a better translation earlier today and hopefully it will still be on the screen when back to work Monday.

The non-nRF registers are named demodulator calibration, RF calibration, and baseband calibration. The values written by the init code are different from the default values in the manual. Don't know to what effect.

The manual mentions "universal communication mode" in several places which seems to imply they intended compatibility with other chips. Don't know if the changes to the calibration registers are what's causing the bind to fail with nRF devices.

Interestingly, if you installed an XN297 in your Devo it would not support nRF protocols that enable dynamic payload length or auto-acknowledge. The XN297 supports 64-byte data packets and uses a slightly different packet format in "enhanced communication mode". The CX10 uses the universal mode so it seems it could be compatible.

It would be interesting to see if the calibration register addresses can be read on nRF/Bekin chips and what the default values are. Since the protocol option to write those registers didn't work for Daryoon or SeByDocKy it doesn't seem they do the same thing as on the XN297.

hexfet wrote: Anyone able to translate the XN297 datasheet posted earlier in the thread? Might shed some light, though it didn't seem to document the registers.

If I order a CX10 from Banggood will it have the green board?

The specific green edition

www.banggood.com/Cheerson-CX-10-CX10-2_4...en-PCB-p-945097.html

Anyone able to translate the XN297 datasheet posted earlier in the thread? Might shed some light, though it didn't seem to document the registers.

If I order a CX10 from Banggood will it have the green board?

Not working too with my Devo10 (both options)

Yeah, didn't work on the Devo 7e. Even with the option turned on.

Here are new builds for Devo 10 and 7e. I've also pushed everything to my bitbucket repo if anyone wants to fiddle with the source.

I added a protocol option to set the undocumented registers. Set the option On and re-init to try it. Have no idea if it will have any effect on non-XN297 chips. I tried it on my Devo10 with the Bekin chip and nothing blew up so it should be safe, though probably safest to power down after trying it before using another nRF protocol.

I did find one register I missed initialising. Didn't seem like it would make a difference, but maybe...

That should be the one. CX10 protocol for the green one.

I just wanted to double-check.

I think it has to be something simple. Hopefully PracturedBlue or victzh can take a look?

I've selected "CX10", that was the good one ?
Also tried YD717 just in case, but nothing more ...

Did you select the correct protocol?

I've tested the Devo10 firmware in the previous page on my Devo10 but unfortunately it doesn't bind with my "green" board CX10.
I don't know if this is important but I've noticed the following behaviour with original remote which is quite different from usual :
1) When I switch on the CX10, the blue leds are blinking very fast
2) Then I switch on the original remote, and the blue leds are blinking only medium fast
3) Then I do the "full throttle" (hear BIP) "0 throttle" (hear BIP) => leds become fixed ON

=> at step 2), right after switching remote on, the quad seems to be partially binded and waiting for initialization sequence.
I didn't manage to get this fast to medium blinking leds when using the CX10 protocol, so I guess doing the initialisation sequence (full to 0 throttle) could'nt do anything.

Hope to hear from you

Yes, many of us are hoping to use the the CX-10 green pcb with the Devo7e.

So a Devo 7e build would be good for me to test and give feedback too.

Thank you.

I don't think it will work because it didn't for SeByDocKy, but you're welcome to try. It's not in the nightly. There's a build for Devo10 posted earlier in the thread. If you have a different radio I can make a zip for you. It's a new 'CX10' protocol.

I'm going to test if you think it may work !
So I should flash the latest nightly and use of the following protocol :
"YD717", "Sky Wlr" or "XinXun" ?
It's the same setting for red board / green board or is there anything to set up to try ?

ben1977 wrote: A few posts above, the investigation of "green board" protocol seemed very close to be functional, could you please tell us about your work ?
Thanks !

I've tested in the emulator and believe the code is sending the same init and bind sequence as in the capture, but SeByDocKy's quad wouldn't bind. Perhaps there's a error in the code.

Or there could be some incompatibility with the XN297 chip. It would be nice to know what is set by the two writes to registers that aren't in the nRF documentation.

Or something else. Open to suggestions

Wene001 wrote: Hi

Can you pleas tell me the binding Prozess with Skvwklr Protocol and a Cheerson CX-10

i've planted a BK2421 tx Modul without PA in my Devo6s
The problem is that i don`t know if its working.

I,ve tried different Vd717 Variants and skywlkr binds one time with (not reproduceable) but doesnt work properly.

Seems So please tell me how the binding should work.

Ive opended the Cx-10 ....red board

Greetz from Austria

Personnaly, I installed a real nRF24L01+PA+LNA chip. Can't tell if it's worling also with a Beken2421.... Probably ...

Hi

Can you pleas tell me the binding Prozess with Skvwklr Protocol and a Cheerson CX-10

i've planted a BK2421 tx Modul without PA in my Devo6s
The problem is that i don`t know if its working.

I,ve tried different Vd717 Variants and skywlkr binds one time with (not reproduceable) but doesnt work properly.

Seems So please tell me how the binding should work.

Ive opended the Cx-10 ....red board

Greetz from Austria