Nova Quanum (eventually Cheerson CX-20)

Here is a model config pour the quad "NOVA Quanum".
It might work for the Cheerson CX-20

My Devo 7E is settled with 2 additional switches
Left Side (SWA) is a 2-position
Right side (SWB) is a 3-position
My firmware is a nightly build : devo7e-v4.01-3b6213a8
I have a RX701 in the quad

Notice the hardware.ini is set with "extra-switches = 3x2" as there is no option for a 3x+2x but I just had to use SWA1 and SWA2

For the flight modes, I set them to the exact same switches combinations as the stock TX of the RTF version (notice the SWA-SWB permutation that has no effect)

I have the 6th Flight Mode with both FMODE & ALT HOLD switches (this configuration is prioritary to any SWA-SWB combination). I made it "Land Mode" in order to have an idiot-proof configuration :
all 4 switches high => Stabilize mode (= manual fly)
all 4 switches down => Land mode

I use the right trims to drive the gimbals (replacement of the knobs on the stock TX)
I also set a proportional countdown timer linked to THROTTLE (value has to be set according to your battery)

I don't use the CH6 in the FC






Enjoy your flights !
Yann

not binding to my opensource cx-20 . any ideas ?

The RX 701 receiver is not the standard RX for the CX-20. According to this thread (my CX-20 is still in transit) you should be able to use Flysky protocol. So you should be able to just change the line in the Model2.ini that says "protocol=Devo" to "protocol=Flysky".

Let us know what you get. I hope to have mine later this week...

wish it was that easy .. i tried switching to every protocol .

No sync . i have cx-20 with solid white flight controller
and white receiver . flight controller has APM 2.52 on circuit board .

wish i could get it to work .

gurusonwheels wrote: wish it was that easy .. i tried switching to every protocol .

www.rcgroups.com/forums/showpost.php?p=28848146&postcount=3246

Hmm... that link seems to be just another question about which protocol.

After checking both Google and Bing, the only specific reference seems to be from Tesla1856, reporting second-hand. I don't see other confirmation in any search, but maybe i'm not searching for the right thing. In any case I'll have one to test in a few days (or maybe weeks...)

www.rcgroups.com/forums/showpost.php?p=30829980&postcount=16317

If take a look inside the CX20 tx, you will notice, that the module looks quite alike the shielded module you will find into the Flysky and the Turnigy tx module.

raw.githubusercontent.com/jlnaudin/x-VTO.../cx20transmitter.jpg

www.rctech.net/forum/attachments/radio-e...ter-dsc01211-mod.jpg

I'm getting my cheerson cx-20 tomorrow and just wanted to confirm -- so the cheerson cx-20 does not work with the default hardware on the 7E? i will need to install the A7105 or the cheerson chip?
Also, is the Devo 7E superior to the stock tx in every way? Any feature you think the stock tx is better than the 7E?

I have the Big Fly Shark (BFS) version of the Nova (Cheerson CX-20). They have 3 different FC's available but the tx's all work the same as far as selecting flight modes go.
I have a Devo 8s and 802 rx and would LOVE to use them on the CX-20.
One of the biggest problems with BFS version of the CX-20 is the failsafe mode. Rather than dropping ch.3 to a low level, it actually activates the RTL function in ch5. causing the FC to bring the quad home......most times.
Will this firmware work on the BFS version?

PS: I'm THRILLED that the right trim is being used for ch6 (gimbal)....I have been scratching my head looking at the stock programming for that.

I am still waiting to see if Gearbest ever even shipped my CX-20, but in the meantime I'm getting ready. If we can bind with devo, for the 7e you'll need an A7105 module, and given this application you want the PA version. I have found no one who can confirm that the Deviation protocols can bind with the CX-20 stock.

I have seen a number of people using DEVO with a non-stock RX. So once mine arrives I'll see if I can capture the TX and RX data. Once we know the data stream I hope some of our wizards can figure out the tricks.

With the 7e I've used the trim and other buttons to do stepped things, we just have to get the INI file right one we get a bind!

Deal57 wrote: I am still waiting to see if Gearbest ever even shipped my CX-20, but in the meantime I'm getting ready. If we can bind with devo, for the 7e you'll need an A7105 module, and given this application you want the PA version. I have found no one who can confirm that the Deviation protocols can bind with the CX-20 stock.

I have seen a number of people using DEVO with a non-stock RX. So once mine arrives I'll see if I can capture the TX and RX data. Once we know the data stream I hope some of our wizards can figure out the tricks.

With the 7e I've used the trim and other buttons to do stepped things, we just have to get the INI file right one we get a bind!

I dont think there's a seperate A7105+PA module is there? I only saw one kind. It's incredible that no one with devo and the cx20 can simply confirm their setup.

This is the one: A7105-D03-PA .

I agree, but since many of the owners have the Quanum Nova version (which comes without a receiver), it seems that the general approach has been to use alternative RX. With a Walkera or spektrum RX you can easily bind to Deviation without the need for an additional module.

I've hooked up my Salea to the CX-20 stock TX and checked the lines connected to the transmitter module. There are 6 lines from the TX board to the module, and line 1 is definitely ground. The remaining five lines are less obvious. I cannot see any activity on line 6, so i've concentrated on lines 2-5. When I get the capture, here's the pattern I've seen. The first photo is the initialization of the board when it is turned on. The second photo shows the pattern that happens 10 seconds later, presumably bound to the receiver.







I don't think this is exactly what i should be getting. Can anyone look at this and tell me if anything is missing? I don't think this is exactly what i should be getting. If you need to see the entire capture it is at dl.dropboxusercontent.com/u/31578062/CX2...%20%5B8%5D.logicdata .

Thank you!

Looks like maybe you're on the right pins but the sample rate is too low. Start with a high sample rate to get an idea of the spi clock frequency.

I hadn't tried that yet! Thank you.

I think this should be in Protocol Development, right? I'll start a thread there unless you think otherwise.