Eachine CG023 protocols - what are they?

Hi all, I hope I am writing this in the right section. I just ordered an Eachine CG023 (Blade nano QX clone) from BG, just wondering what protocol it uses and if Deviation will work with it. I have a Devo 10 in transit to me with both additional modules, but won't be here for a while. Just planning ahead. Thanks.

For those who are curious,
www.banggood.com/Eachine-CG023-Mini-2_4G...er-RTF-p-956820.html

Cheap as hell, $22.99USD RTF, even cheaper if you use "bestbg" as a discount code.

Thanks.

Hi,

I'm pretty sure you will find a LT8910 RF chip inside the quadcopter and the transmitter, as that's what is inside Eachine CG022 and H1, see www.deviationtx.com/forum/protocol-devel...-h1-a-k-a-mini-ninja for H1 protocol details.

This means: This one is currently not supported by Deviation and needs some work to go.

One and only way to harvest a (short range) LT8910 module I know is to get hands on the transmitter of a tiny quadcopter which is labeled as "CX033" nano 6-axis quadcopter (V272 clone, NOT the cheerson mini-phantom). This one:

But still you would need to attach that small RF module to your Devo and have an implementation of the proper protocol in DeviationTX.

That requires attaching a logic analyzer to sniff SPI traffic to RF chip on transmitter side (as protocol is 99.9% not the same as on CG022).
Plus someone willing to spend (and actually have) time to implement, test and finalize code for Deviation.

Even that I have SPI captures, two CX033 and a CG022 to test LT8910 integration and am able to do the coding, testing and finalization - I don't have spare time yet.
Family fun (three small kids) plus way too much unfinished projects waiting for me

Thanks for the reply. Once I get the CG023 I'll take pics of everything and see what's inside. Hopefully in the near future a solution will be found.

I too have three young kids running around, so I know what it is like!

Thanks again!

I just got one Yesterday.. It's got an XN297 in the quad (Impossible to photograph with my phone..)

Here's the TX module:

copy.com/thumbs_public/8S4sYjeA22UJaaTb/IMAG0372.jpg?size=1024

I googled it (XN297) quickly. It is apparently made by Panchip mainly for a wireless mouse!

Here is the spec page....
www.panchip.com/en/products_show.aspx?cid=63&id=333

I have extremely bad luck with Eachine 3D X4 - the props are so brittle that I managed to break left forward one twice! I'm out of props, nothing else fits this heli (the props should be flat), slow boat from banggood is coming in in a month or two!

I'll check your code with a black prop instead of nice white one!

avroarrow4ever wrote: I googled it (XN297) quickly. It is apparently made by Panchip mainly for a wireless mouse!

Here is the spec page....
www.panchip.com/en/products_show.aspx?cid=63&id=333

CYRF6936 was intended for wireless mice originally as well And nRF24L01+ is used by Microsoft and Logitech in their wireless mice and keyboards.

XN297 is hacked, so some of XN297-based helis is not too hard to cover. Some are still a problem.

I have my batteries on the chargers now, and I hope to get to trying it out later tonight. My CG023 I think has a bad motor (haven't used it in a while), but I should be able to report on basic stuff. I'll keep everyone posted. Thanks again!

goebish: Thanks for the file, seems to work ok. I'll go into more details below.

TX: Devo 10
Quad: CG023 with the Right Rear motor failing. Also using a 300mah battery.

-TX flashing OK, no problems.
-Made a new file from within the TX, found the Eachine protocol, binded OK, no problems.

Did not fly well, it was all over and hard to predict.

Copied and modified a working V911 file, or I should say I copied the control bits of the V911 file into the CG023 one. Had to remove all reverse codes. It seems to fly the same now as the stock TX, but with the motor failing it drifts back and to the right.

I am not 100% familiar with the model building codes, so I still need to program in the led lights and such. On the next nice day outside I'll take it to the park and see what I can figure out. It is a bit cranky to fly inside.

In the mean time, I've attached my model.ini file for all to see and mod.

Thanks again for making the flash upgrade!

I decided to try also 7e build (I already reported yesterday on rcg my results with devo10). But there is a problem - I have "Bad/missing protocol modules!" message on restart with EachineX4 protocol selected. All other protocols seems to work correctly. Protocol executable is stored on 7e's FS:I tried reloading dfu and rewriting protocol directory - nothing helped.

goebish wrote: Cool, first reports from here and rcg seems to indicate it's working fine, for both machines.

Say thanks to victzh, he's the wizard who made this possible

Thanks to victzh and you both. Been wanting to try a 3d quad

goebish wrote: - rate is fixed to 100%, using dual rate is not a good option because controls have a low resolution (only 7 bits per channels for roll / pitch / yaw).
- trims are not implemented (they are on the RX side, I'm not sure where to put them in deviation, protocol options dialog ?)

Probably biased but recommend the approach in the yd717 and symax protocols:
- Quad always set to highest rate. Use Deviation scale in mixes to adjust stick response.
- Use the trim channels to extend control range by driving the trim with appropriately scaled channel value. Deviation trims handle any real trim adjustments.

goebish wrote: Files updated, same url, new protocol name: EAchine4:
www.deviationtx.com/downloads-new/catego...-cg023-nrf24l01-test

Thanks very much for testing and reporting, gotta love this community

Привет!
I checked the updated 7e build. Now everything is ok. Cg023 is flying greately. Previously I reported some strange behaviour with light channel - now it's gone. So it was simply LVC warning with old battery in my case.

And again - many thanks for you and all those who make it possible.

And if it's upside down throttle up moves it up, not down as in the real 3D heli.

I am not a big fan of using protocol trims as extension for the range. It can be implemented differently for different models - different multiplier or even different sign of multiplier. So for one model it would extend the range, and for another - contract.