Eachine CG023 protocols - what are they?

Ok, flashing the new version, and I will test with a few different power output values.

Ok, last version appears to work good, for sure better than previous versions.
But need to check more to be sure. Change the power output doesn't appear to change anything.

What's the Datarate for this protocol?

Ok, Thanks! I was asking to calculate the power output versus distance.

Last version appears to work good. Not any delayed command with several resets/binds. For me appears to be Ok.
But I think is better more people test your code because the strange issue.
I will return tomorrow after a few more batteries.

Here is my model file and icon file in case anybody want to test the code.


Thank you very much Goebish for such great job!

Hi Goebish, more updates about this protocol...

The Camera channels, are exchanged. According some people with camera version, when the camera is recording video the quacopter's leds blink continuous. At this moment with channel 7 at 100 value, the quadcopter's leds blink continuous.
With channel 8 at 100 value, the quadcopter's leds blink for a second (as with stock TX taking a picture).
So channel 7 and 8 needs to be exchanged.

About the delayed commands, I tested 2600 and 4100 versions and for sure the 2600 version works better, but not good...
You can feel the delay even at throttle channel. With 2600 version you can fly the Quad, but you feel the delay almost continuous.
With 4100 version is not flyable at all

Something weird is going...

I also start testing. The first one - Devo10 on 4100µs. Everything ok - three rates switching, headless and flips. No visible delays. As for camera - I do not have one to test. No unexplained blinking. DynTrim - ok.

Second test - Devo7e on 4100µs. The same as above but with one great problem - high visible delay on all the controls. Especially bad on throttle. Changed output power from 150 to 30 - the same or even worse.

Third test - Devo7e on 2600µs. Much better than 4100µs, but delay is lower and still there. Especially good point of viewing it - low throttle situation on the surface with throttle then fully down - smth like 100-200 ms delay visible.

Then I changed fixed id from none to some value - nothing changed. So this time my battery gave LVC and I decided to write the report while it is charging.

By the way... I see one visual difference between 10 and 7e firmwares. If you go to "Channel monitor" there are 10 channels in output as it should be - on Devo10. But on Devo7e there are 11 channels (the additional - Ch11). I do not know if it related to delay-bug... But just for your information...

I agree with Vasily. The throttle delay is very visible even at the floor.
@ Vasily. I tested even with 4 channels, and the delay remains.

Flashing 2050 version....

goebish wrote: Also, can you build from sources yourself ?
That would make testing small changes easier

www.deviationtx.com/articles/18-developm...velopment-on-windows

As for me - I can. I even do not need all those on windows development as I have only linux at home. The only one thing I need to be helped with - I need correct commands to checkin and update my local copy of the repository with your branch code. And the command to build 7e with its protocol directory - as I am not completely sure...

As for 2050 version. Now it is really flyable on 7e. But... delay is still there. It is visible with low throttle test. It is much less than on 4100 version. But on Devo10 and 4100 version - there is no delay at all.

Ok, tested with 2050 version.
Now is totally flyable, but can feel something is not completly right There is a very very small delay.
Camera channels are now corrected, and works as the original TX. When you engage video recording, the Quadcopter reduce rates, even in high rates.
I don't see channel 11 at my model file, is working as expected with 10 channels.

@Goebish. I promise you install the environment to compile my own builds will be my next task

I attach my model file with latest changes for camera controls in case anyone wants to test.
Valid for Devo 7e with 3x2 Switch Mod.
FMod1. Engage Flip Mode.
Hold1. Throttle Cut.
SWB switch. to select rates.
Throttle Trim +. Take pictures.
Throttle Trim - . Start/stop video.
Yaw trim (Left). Enable/Disable Headless mode.

goebish wrote:

vasiliy_gr wrote: need correct commands to checkin and update my local copy of the repository with your branch code.

I'm not a mercurial expert (I don't know how to add remotes from command line, I'm using SourceTree), so just create a clone of this branch in another folder:

hg clone https://bitbucket.org/goebish/deviationtx -r YD-829

And the command to build 7e with its protocol directory - as I am not completely sure...

cd src
make TARGET=devo7e zip

Something goes wrong on linking stage:May be I am using wrong tools version?.. Meanwhile previous version of deviation (smth about 1-2 months of age) can be built flawlessly.

The 7e build from default also overflows for me.
arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150303 (release) [ARM/embedded-4_9-branch revision 221220]

goebish wrote: ouch !
region `rom' overflowed by 52 bytes
Maybe this has something to do with newer arm gcc, I haven't updated mine (and I won't as all my arm projects build fine ).

edit: I'm using GNU Tools ARM Embedded 4.8 2014q1

YES! Switched to 4.8 2014q1 - and compiled 7e build flawlessly!

But... What is the default compiler version for big deviationTX?..