Advanced Search

can you please upload the model file you use with it?

Hi,

I have red PCB with integrated antenna and it's working with Blue-A too.

goophoba wrote: I just got a FX-10, CX-10 Blue-A protocol works. My CX-10 is a red PCB but works on the blue protocol.

Does your CX-10 have no wire antenna?

Xradeon wrote: Confirmed. Red PCB without antenna cable is working for me on my Devo 7E using Blue-A format.

Did you have to create a particular fixed ID or config to bind?
I have a red pcb without antenna and it won't bind to cx-10 green, blue-a, dm007 or skywalkr

Hi, I tried this protocol on a 3015-2 quadcopter fcb it works great, even if I can set a maximum of 30 mw or does not transmit. Only thing I can not do somersaults with channel 6 and channel 5 will change the speed rate. I had to also invert the channels.

Reset the cx-10 gyro first... just google it on youtube. works like magic

goebish wrote: I might have a go at implementing it sometime next week, looks like the newer CX-10 H8 mini "3D" is using the same protocol (well, that's what I've been told )

It is.. I received my H8 Mini 3D yesterday, and it uses the exact same TX as the H20. You can fly the H8 3D with the H20 TX, tested that. And without any modding, it has almost the same poor range as the H20, resulting in multiply fly-aways, and having to retrieve the quad by walking over to it.

I might have a go at implementing it sometime next week, looks like the newer CX-10 H8 mini "3D" is using the same protocol (well, that's what I've been told )

vasiliy_gr wrote:

T.N. wrote:

vasiliy_gr wrote: Tested. Ch7 now ok. So all the extra functions of DM007 are working now.

Can you please post your dm007 ini file?

Here is my ini for dm007 on 7e with two extra 3x switches. It may have some defects as I am really got mixed up with testing on two devo's four new quads with test builds... But I checked it right now - it is flyable.

SWB for speed rate (low-medium-high), FMODE for flips (you need it ON - flip - OFF - ON again - flip again), HOLD for headless, UP and DN for photo/video (or vice versa - do not remember exactly).

Hi

I made my own variation of this .ini you made, hope you don't mind. Your one I found to be a great starting point and I just made some adjustments to my own personal preferences. The main difference I made was moving the camera control to SWA, where SWA0 is video, SWA1 is off, and SWA2 is camera. I found this better personally on this model as if you don't turn the camera off before turning the quad off, it doesn't save the file, and this way I know it's turned off, and also it's easier to just "flick" it into a mode whilst keeping your fingers on both the sticks. You have to keep it in SWA0 to record, and the moment you move it back to SWA1 it stops recording, and with the camera, just a quick "pulse" to SWA2 and back to SWA1 takes the photo... if you keep it in SWA2 it will take a series of photos until you turn it off.

I also made a couple of changes in the main screen presentation, simplifying it a littl by removing unneeded bars and making the second timer a countdown one from 7 minutes, as I made a big battery mod (internal 500mAh battry with a switch to turn off and charging via the balance plug under the hatch) and I get 8 minutes of flight time now, so I wanted a countdown with a margin for safety.

Anyway, I thought I'd share my version of your .ini on here... thank you ever so much for making the first .ini, it helped out a LOT!!

Did you ever get to the bottom of this? I currently have a CX-10, an H8 and an X900 and the CX-10 yaws slowly to the left with the Devo but not with the original controller, the H8 yaws slowly to right and the X900 doesn't move at all, I would have assumed it was a weak motor or dodgy prop causing the drift except that the CX10 doesn't yaw with the original controller (mind you the nano controller has other trim issues so maybe not proof of anything).. Flying outside I don't really notice it but it's obvious when hovering in-place inside, like you I've found rudder trim really has no effect either.

I've just rebuilt my old red-PCB CX10 using a motor and the battery from a bad CX-10A, I've tested it with the original controller and now I'm trying to find a simple baseline config for it on my Devo 7E, the ini files I've found so far are quite complicated and don't seem to work very well for me (weird yaw problems and general instability).

Ultimately what I want is a simple config with med/high rates on one of the switches (I'm not interested in auto-flip)

I'm running the latest hexfet test build, I've calibrated the sticks and my H8 and X900 both work really well so I'm confident that the tx is fine.

Can anyone help me out?

Thanks!
Bruce

And the CX033 Nano from 'CX Model' (which I got for 10 bucks from a german ebay seller).
The (CX-10-alike) transmitter contains a small RF PCB with the LT8910 which could be easily hooked up to a devo.
I already have plans to re-use the CYRF connection on the multi-module for that, but I have no spare time at the moment.

Same probably applies to the DHD Drone D1, as I can fly the recent version of the CX-10 with the controller that came with the Drone D1. From what I understand, the Floureon and Drone D1 are from Cheerson, I remember seeing a picture of a spare receiver board, having CX printed on it.

goophoba wrote: Just a heads up for anyone searching for this. The Floureon FX-10 works on the latest release using the CX-10 protocol and the Blue-A sub-option.

Thanks for the info

Just a heads up for anyone searching for this. The Floureon FX-10 works on the latest release using the CX-10 protocol and the Blue-A sub-option.

Epitaph wrote: Hi everyone!!

Just a couple of question, I have a DM007 on its way as well as an FX-10. The FX-10 is made by Cheerson it seems, but does anyone know if it is deviation compatible? I mean, Cheerson have this lovely habit of changing protocols even within a particular model so it seems, and was wondering if this model might have a protocol which is the same as one of the CX-10's for example...

I just got a FX-10, CX-10 Blue-A protocol works. My CX-10 is a red PCB but works on the blue protocol.

Tried all my available transmitters, no binding for any of these:

- JJRC JJ1000
- Bayangtoys X9 (same protocol as H8 Mini)
- Cheerson CX-10 older version
- Cheerson CX-10 newer version
- DHD Drone D1
- JJRC H20

I've had a devo 7e for 5 or 6 weeks now. Right away I added a Nrf24l01+pa+lna module, as all my quads work off it, and the latest nightly build. A few weeks later I switched to the MJXq test build to fly my MJX quads also. Everything was great for a while after I put the nRF module in but over the past week or two I've been having trouble with the symax protocol. The other quads I have with me that are not on the symax protocol work just like they do with a stock tx (or better). I am on vacation and we have 4 symas, a cx-10, and a jj-1000 with us.

With Symax I get inconsistent binding requiring either one or two things; restarts of the binding on the 7e by shutoff or re-bind button until it works (usually within three or four tries), or if that is not going well I restart the quad and try again. Every so often when I flip the tx off or hit re-bind the lights go solid for about a full second then keep flashing.

I always manage to get a bind but it's not easy. Even if I get a bind I lose the connection at random it seems. I thought I killed my nRF module somehow, but the other quads work great, the jj-1000 even at a large distance manual flips and all, so I guess the module is ok.

With syma quads when I do connect it is either has lots of intermittent cutouts small enough to look like lag but not cause flashing, or/and it losses connection long enough to start flashing. It always rebinds within a moment but its enough to screw up manual flips or precision flying. This is regardless of distance, could be one foot or two hundred.

I've been testing syma binding this morning. My x11 quads (two of them) both bind and lose bind at the same time (I bound them concurrently). Both of our x5 quads also show the binding issue (but I did not test the x5 quads at the exact same time). The x11 quads are sitting next to me, with the 7e, bound as I wrote this and they have had momentary loss of bind flashing a number of times.

The other quads bind first time, every time.

Any ideas? I was thinking about going back to the nightly build and see what happens but I wanted to see what you guys thought first.

Hi everyone!!

Just a couple of question, I have a DM007 on its way as well as an FX-10. The FX-10 is made by Cheerson it seems, but does anyone know if it is deviation compatible? I mean, Cheerson have this lovely habit of changing protocols even within a particular model so it seems, and was wondering if this model might have a protocol which is the same as one of the CX-10's for example...

I've been looking through the thread and it seems to be getting a little confusing about what's been done and what not, and especially pertaining to the protocol in itself. Now I have downloaded the .ini file that has been shared for the DM007 (thank you for your work, BTW), but in reading it I noticed it uses a protocol called CX-10. At the moment I have my Devo 7E with build 4.0.1-42611fe, and I don't remember seeing that protocol on there... was it added in a later nightly build or is it in this one only I just haven't seen it? (I'm hoping it is on my build, because the last time I updated it messed up my models a bit, changing the way they reacted to input and such so I had to retune everything )

Also, has anyone made an icon for the DM007?

Thank you!!

Thanks for sharing !

Cool, thanks for reporting !