Advanced Search

I can't test because I do not have a green CX-10 board, but I used your NRF24L01 to XN297 emulation layer to implement the EAchine 3D X4 protocol and it's working fine, you made a really impressive work !



I won't commit any code until victzh has completed his cleanup, but I can make test builds on demand. Note that it should work with the CG023 too as they both use the same stock TX.

edit: Devo7e & Devo10 test builds uploaded to www.deviationtx.com/downloads-new/catego...-cg023-nrf24l01-test

@Durete - it's as safe as any nightly build, your judgement here is as good as mine.

@magic_marty - it will, I just built it for the one I have (10) and another one that is critical with resources (7E) to check it compiles and works well with the module system. The module itself is not production quality yes, one thing is the protocol is not reversed fully yet and we can't support many CX-10 flying simultaneously. Another, I would like to implement "blue board" as well. It will take some time but it's gonna be soon.

Will this work with the Devo 8 and Devo 12?

Also is it now in the deviation nightly builds?
Thanks for all your hard work..

Hi victzh, I have a question...
Can I use safely your experimental build to fly other protocols?
Your build appears to be compiled with latest merges from DeviationTX repository, but I would prefer to ask you because tomorrow morning I plain to use my Devo TX.

I think you could just put it in nrf24l01.c The build system should do the right thing.

PhracturedBlue wrote: victzh,
can you use the uploader script instead in the future?
I'm trying to get developers to use the upload area because it allow me to not have hundreds of old builds sitting in the archives for years taking up space. All developers have access to it, and it works on all platforms.

I will. I forgot about this script when uploading the build. May be it makes sense to pin the message with the script in Builds subforum as a reminder?

And FYI, this is amazing work. Good job.

Thanks! Still many things remain to be solved, in particular the reception path. Do you think it makes sense to put the emulation code in the separate file in src/protocol/spi directory? The alternative is to make it an include (I would call it xn297emu.inc - it's not a header) to not burden Devo 7E at the cost of multiple instances in all other Devos.

BTW, answering your question about scrambling sequence - it's fixed, it covers both address, no matter the size (from 3 to 5 bytes) and then the message. The code in the emulation layer (as you probably figured by now) handles all of this for you. You just need to call some functions instead of calling native nRF24 ones. Also, note that the main body of message is bit-reversed - it gave me extra headache decoding it

No problem, I just wanted to test, I'll wait that you finish before committing anything

Nice! Mind you, the code can change - I may be put it in a separate file (may be .inc for textual inclusion - it's needed only by modules and I don't want to burden Devo 7E already tight space).

Also, the situation with checksums is not very clear. It seems to be working, but some packets can mismatch it - I never explored it in depth. I've seen radio traces that does not match this checksum algorithm - they may be artifacts of decoding, or may be real.

Victzh, you're a god !
I just used your xn297 emulation layer to write some code to bind the EAchine X4 3D and it works !!!

Thanks! It was a nice journey - I started it April 22 as can be seen by first file dates.

I am trying to document it, may be a list of my mistakes can be useful for somebody

Amazing ....

Very nice work! I second the request for a blog post

camousse wrote: Hi,
I doesn't work on mine. But may be i make something bad:
- i boot up cx10. led flash, and after a little amount of time, blue light flash fast, and red light stay solid.
- i boot up devo. nothing change on the cx 10
- i go full throttle, and min throttle (i remember i had to do that with the original radio)
nothing change on cx10...
i will try with the original radio

Are you sure your CX-10 is a green pcb edition?
What nRF24L01 module do you have installed at your Devo TX? I lost your comment about blue PCB.
The armin procedure from stock TX (throttle Up, Throttle down) is not necessary using your Devo TX.

@Victzh, tested 3 more charges under my CX-10 and JXD-395 flying outside. Not any single packet drop flying at 1mw power output to about 50 meters.
My nRF24L01 module was bought at Banggood, it's the typical under other sellers with PA + LNA, maybe people using modules extracted from stock TXs could have problems, I don't know...

victzh,
can you use the uploader script instead in the future?
I'm trying to get developers to use the upload area because it allow me to not have hundreds of old builds sitting in the archives for years taking up space. All developers have access to it, and it works on all platforms.

And FYI, this is amazing work. Good job.

I have a blue board. Didn't remember this little detail...

Hi,
I doesn't work on mine. But may be i make something bad:
- i boot up cx10. led flash, and after a little amount of time, blue light flash fast, and red light stay solid.
- i boot up devo. nothing change on the cx 10
- i go full throttle, and min throttle (i remember i had to do that with the original radio)
nothing change on cx10...
i will try with the original radio

Before I start working on the Eachine X4 3D I've a question for victzh Do you think the "scrambling table" (xn297_scramble[]) is fixed or depends of the values thrown into the debug registers at startup on the xn297 ?
Same question for polynomial, initial and xorout.

edit: forget this post, I tried and it works

Unreal thanks buddy great work
Neil

You sir are amazing.I'll try today!
Excellent work !
Neil