Advanced Search

Pretty interesting read. Looks like there's javascript code linked at github in the last post. Looks like 8-bit channel values.

I haven't done any looking at wifi quads myself.

The closest info I've found on this is the following reddit thread related to hacking the IP video and control protocol of the FQ777-954 which I believe uses the same or similar IP video board as the Cheerson CX-10W's.

www.reddit.com/r/HowToHack/comments/4512...camera_in_toy_drone/

(Unfortunately the code posted to tinyupload has disappeared.)

Cheerson's mini drones CX-10W, CX-10WD, and some other models can be controlled by WIFI as well as conventional 2.4GHz RC. Some of these models also use WIFI to receive steaming video from onboard cameras.

The conventional TX protocols are available as deviation modules. However, seems little is known about the protocol used to control via WIFI. What protocol is used to control via WIFI and receive video via WIFI? Has anyone cracked this yet? Sniffing WIFI communication may be necessary to do so; have never used a WIFI packet sniffer.

Would like to develop custom control software on iOS and/or Andoird for these Cheerson WIFI capable mini drones.

Please provide some SPI captures, it shouldn't be hard to implement as a CX-10 sub-format then.
www.deviationtx.com/forum/protocol-devel...95-spi-capture-guide

See capture here
Not sure if it is same as CX-10D.
I can also capture another CX-10WD if needed but not tonight. I have to solder on the MCU's pins which makes my eyes ache.

I got a CX-10WD, the variant with wifi fpv. The transmitter uses a XN297L. I can make captures if you think it helps.

I was wondering if anyone has come across a chip before which:
a) Repeats parts of the address and preamble in the messages sent on-air
b) Sends totally different payloads on-air to those which are clocked in via SPI

The packets I see being clocked in on SPI during bind are similar to the ones mentioned in this protocol post:
www.deviationtx.com/forum/protocol-devel...does-not-ack-packets

I'd really like to figure out if anything is happening inside the chip to modify the SPI payloads for transmission.

So do you think I could use it to bind a cheerson cx-10, I'm picking up a devo 7 today and would like to set it up for my daughters quad

SquirrelD did you get this sorted?

I have the Nrf module as well which works with me CX10 but I can't get it to work with my CX10c

Are there versions of the CX10c that do not use a NRF based protocol?

So I'm trying to get my cx-10 W to work with my 7e. The only module I put in is the nrf module and I know that's working because I control my Syma x5c-1 with it.

I've tried a couple of model files I've found but only one was for the 7e, either way, no joy. Can someone help me please? How should I proceed?

Thanks all, once I downloaded the right file all worked perfectly. Now I'm trying to get my cx-10 W working and not having much luck. But that's a post for a different thread I guess!

The FQ777-124 is a great little micro quad. It's really quick and agile, it's like a faster version of the Cheerson CX-10. It also has headless mode and return to home functions.

Attached is a Devo 10 model file for the FQ777-124 micro quad. It requires that you have an NRF24L01 module installed to use it. All known modes are implemented (flip, return to home, headless mode). The new protocol name is 'FQ777-124' and is in the nightly builds starting with the 2016-09-08 build.

I've also loaded this Devo 10 model file in a Devo 8S. It flew fine and all switches and modes worked correctly, but you will need to implement the toggle boxes if you want to display the switch positions.

Please note that the the 'powers to be' have recently changed the touch screen interface,on all current Nightly Builds and test builds, so, much of the touch screen GUI functionality and advantages are now gone. It now works more like a Devo 10 interface. These touch screen test builds are not broken, even though it seems that way, it was intentional (grrrr grumble rant).

I added the following comments to the top of the model.ini file:
; ==CHANNELS==
; ch 1 - Ail
; ch 2 - Ele
; ch 3 - Thr
; ch 4 - Rud
; ch 6 - Flip mode = +100
; ch 9 - Headless mode = +100
; ch 10 - Return to Home - reverse value to enable - use Ail or Ele stick to cancel
;
; ==SWITCH ASSIGNMENTS==
; FMod - Throttle Hold
; Aile D/R - Ail & Ele D/R, up = high rates
; MIX - Flip mode, Mix1 & Mix2 = enable
; Gear - Headless mode, down = enable
; ELEV D/R - Rud D/R, up = high rate
; RUDD D/R - Return to home, flip either way to enable, Ail or Ele stick to cancel

My thanks to all that developed this protocol and all the others making Deviation great.

Hello all, i'm new to this forum and first of all i want to thank you for your job and the incredible ability to make our favorite drone to fly with devo radio!
I have this drone and devo 7e, i have tryed to test the last goebish build but i have a problem with the nrf module, i have installed it on my radio and work perfect with other drone like cx-10, h8 mini ect..
If nrf is enabled in hardware.ini (i have it in port no. 13) and selecting fq777 protocol the radio crashes into reboot looping, if i disable nrf module the model with fq777 work fine.
I don't understand nothing of programming, but hope my experience can help you!

sorry for my bad english

Fer wrote: CX-Blue A doesn't seem to be affected as my CX-33S flys equally well with both DEVOs (one with 3in1 and the other with NRF+A7105). CX-10 is ok too, and i tryed my V222 and it flyes well without lag. I don't know if range is affected, but at the usual ranges i fly there isn't any problem yet.

All the CX-30 boards i have lag and deleting the fixed id only partially seems to improove the situation, if at all. I don't see any special option to dissable something in the protocol settings of my tx.

All others i tryed (CX-10A, E010, JJRC1000, H20 and a couple more), fly ok.

Lets hope that in a new nightly build there will be an option to at least solve the lag problem.

According to the code, cx10 protocol does not use AA. However it does use receive mode on binding. Hence if your 3 in 1 does not have the correct LNA control for nRF24L01, you may have a hard time.

CX-Blue A doesn't seem to be affected as my CX-33S flys equally well with both DEVOs (one with 3in1 and the other with NRF+A7105). CX-10 is ok too, and i tryed my V222 and it flyes well without lag. I don't know if range is affected, but at the usual ranges i fly there isn't any problem yet.

All the CX-30 boards i have lag and deleting the fixed id only partially seems to improove the situation, if at all. I don't see any special option to dissable something in the protocol settings of my tx.

All others i tryed (CX-10A, E010, JJRC1000, H20 and a couple more), fly ok.

Lets hope that in a new nightly build there will be an option to at least solve the lag problem.

BirdBarber wrote:

robpur wrote: ...One possible remaining issue could be the long antenna trace...

...
Does anybody know if the long trace may effect higher power differently than lower power?

It turns out that the length of RF feedline or transmission line is irrelevant. What is important is its width which should be chosen such that it has the impedance of 50ohm at 2.4Ghz. Hopefully the daughter board was done with the right RF PCB design tools which has taken care of the issue.

I have completed my Devo 10 mod. It was super easy and clean. So far I have tested it briefly with X5C-1, X8G, CX-10, CX Stars and Proto-X Nano without issue.

I still have several latest version 4-in-1 modules with Devo 10 daughter boards for someone in US who want to get it quickly or don't want to deal with Chinese website. Just PM me if interested.

Update: All 4-in-1 modules are gone.

Is there a ready made .ini file for the Cheerson CX-33S? I have read in another thread that it uses the cx-10 blue protocol. I should be relativly easy to programm the basic channels, but i don't know about the other channels like the autotake off and land, or the photo/video thing. I don't think it has any other abilities like 3D, RTH and Headless and such, so autotake off/land and photo/video could be all needed. And rates of course.

This is in the manuals in the left hand nav column. The '*' at the start of the name in the contents & section header means it needs an additional module. Similarly, if it shows up on your Tx with a '*', you need to add a module (or maybe you need to get the one you have properly connected).

The section for each protocol tells you which module you need for that protocol, and provides a link to installation instructions.

Yep, you need the nRF24L01 module installed.

so i see with this new build that there is a cx-10 protocol. i have the cx-10 and cx-10a do i still need a separate module? i cant get my devo 7e to bind...