Advanced Search

mwm wrote: New one arrived. It behaves exactly the same as the old one. Almost all stick movement is followed by a noticeable delay before the quad reacts. Anywhere from .5 to 1.5 seconds. Every once and a while, it'll react immediately, but that's the exception, not the rule.

I dug the first one out, and verified it does the same.

Bummer... sorry to hear that man..... this is so close to being the king of nanos, I wish we didn't have these problems.....

I do need to stress that my Proto X SLT with stock TX performs perfectly, way better then my two Cheerson CX-10s. I'd rather fly my SLT over the CX-10 any day. The TX is just so much better.... but when I pull out my Devo 7e our symptoms are just too similar to be coincidence... something is going on with this nano quad...

For me, with the Devo 7e it performs even better then stock tx, but there are these weird (rare) 0.5 - 1.0 second delays that cannot be explained.

I have to blame the TX - I have no other explanation.

Maybe I got lucky, but from where I stand, there is nothing wrong with the quad. The issue is with the TX.

side note: I went the opposite direction, I ordered a Proto X (old version, no SLT) to test my Devo 7e... I tried to go backwards... and although deviation flies it perfectly, the results were not impressive; it doesn't fly as well and the battery is noticeably less (2 min with prop guards). The SLT is better, and I want it to work dammit!

It would be extremely valuable if someone else here could confirm the SLT protocol works okay on Deviation...

....is ANYONE using SLT without issue?



 

According to the datasheet the IO pins are not 5V tolerant, I used a logic level converter for my first tests with a 5V Arduino.

I had another setback with XN297 - this time it does not work in my test setup, Arduino. I suspect it gets too much voltage, my Arduino works on USB power and does not have down regulator to 3.3v. Or I am doing something radically wrong - it just does not appear to be alive for me - no response, or one response only - then silence. I resoldered it back to check whether I ruined the module with 5v signals (I put 3.3v power, but Arduino uses 4.8v or so on signal lines) - no, the original TX works fine.

victzh wrote: I checked my config file - channel 5 is mapped to AUX4, which - you guess - happened to be positive. It leads to FLAG_FLIP to be constantly on and heli reacting to it, let's say, less predictably

And I checked behavior turning AUX4 back and forth - it is consistent.

Sorry for the confusion.

No worries. Thanks for testing. Wouldn't surprise me if some differences appear someday among the quads using the protocol.

Daryoon wrote: CX10 would be the holy grail for me as I have one of those. So surprise it still hasn't been deviated yet. LOL

Always appreciate you guys developing and continuing to push Deviation forward.

Note that you can make an external PPM to XN297 module to control the green and blue CX10s with your Devo:
www.rcgroups.com/forums/showthread.php?t...&page=3#post31068187

Join this thread if you want to make yours and need some help

I checked my config file - channel 5 is mapped to AUX4, which - you guess - happened to be positive. It leads to FLAG_FLIP to be constantly on and heli reacting to it, let's say, less predictably

And I checked behavior turning AUX4 back and forth - it is consistent.

Sorry for the confusion.

Flag data is completely separate from stick channels in the YD717 protocols. If your red board CX-10 is flipping when channel 5 is less than zero, then we need some SPI captures from the red board CX10 to see what the protocol difference is.

Does the red board CX10 stock tx have a flip control? The original yd717 does not. The protocol data showed flag bits being set when in high rates, and it turned out the flag byte controlled the flips separate from the rate control. Maybe the CX10 firmware is not exactly the same.

Actually, by chance I have red and green board. I like how green flies better, despite flying red with Devo. Also, sometimes red flips for no reason, may be an error in protocol implementation and some stick values leak into flags.

You guys never disappoint.

I didn't realized the green board used a different chip. That's lame. Especially since the red board was fine already. I thought only the blue board used a different chip. Thanks for the info and getting me up to speed.

Sorry to disappoint, but it uses 3 different protocols and 2 of them use a chip not totally compatible with nRF24L01+. If you're willing to add another radio chip to your Devo - it's available yesterday (actually, for quite some time). The red board works with already existing Deviation protocol and nRF chip.

CX10 would be the holy grail for me as I have one of those. So surprise it still hasn't been deviated yet. LOL

Always appreciate you guys developing and continuing to push Deviation forward.

Thanks for those informations, I'm totally new to that, I've never played with GNU radio or anything SDR related (yet )

The difference is minimal - One is a production version, with components moved around, RF cage is designed in (not populated), RF cleaned up a bit, no 900MHz antenna on board (which you needed to isolate by desoldering a bridge anyways), plastic case, reset button, LEDs in a convenient place, extension pinout.

Jawbreaker is the last beta - fully functional, but less convenient. It lives in an antistatic bag and I get it out of it and put on antenna and USB every time I need to use it. On the other hand, I've got it for free as a part of the beta program - who am I to complain

I was not very lucky with XN297 so far - I soldered to CX-10 green TX and tried to isolate the MCU so that I can use it with my own code but keep an ability to switch back to the native code to keep the baseline for comparison. This approach fails - the other elements on the TX board feed MCU enough to interfere with my code.

I ordered another CX-10 - and got a red version! So, I'm waiting for Eachine H7 which is guaranteed to have XN297 in it in a detachable form.

Next I plan to first make my code work with CX-10 green and Eachine's XN297 and make a comparison RF traces of biding sequence with XN297, Beken, and Nordic. CX-10 binding is luckily uses one RF channel so it's easy to catch. I can publish these traces for analysis - just set up GNU radio and you can read it from file. You don't need HackRF or any other SDR for this.

I'd really like to go into that someday... I had a look at the HackRFs, what's the difference between the One and the JawBreaker ?
Is the Jawbreaker, the "beta" version of the one, I'm confused ?

Meanwhile, I reversed yet another XN297 protocol, for the Eachine 3D X4:
gist.github.com/goebish/6095bb2d95037297641d

Hi,

I ported deviation protocols to Arduino mini for controlling drones with Android Smartphone.
Interface between Arduino and Smartphone is bluetooth.
I named the module as UniConTX and the schematic and codes are open.
Click here for more details





Here is a screen shot for controller UI


UniConTX Firmware can be updated through bluetooth from smartphone.
All models from deviation are not supported due to arduino mini memory limitation.
Only below models are supported. (Actually every model is not tested yet...)
If you want specific models, you need not install all modules. just install the module what you want.

Manufacturer	Model	Type	Module
Ares	Ethos QX75	Quad	NRF24L01
Attop	YD717	Quad	NRF24L01
Attop	YD928	Quad	NRF24L01
Aviator	YK016	Quad	NRF24L01
Cheerson	CX-10	Quad	NRF24L01
Cheerson	CX-11	Quad	NRF24L01
Cheerson	CX-205/SH6057	Quad	NRF24L01
Cheerson	CX-30	Quad	NRF24L01
Flytecs	X-Drone Nano	Quad	NRF24L01
Hisky	FF120	Quad	NRF24L01
Hisky	HMX120	Quad	NRF24L01
HobbyKing	Q-Bot Micro	Quad	NRF24L01
Huan	QI 881	Quad	NRF24L01
Hubsan	X4	Quad	A7105
Hubsan	H107C	Quad	A7105
Hubsan	H107L	Quad	A7105
Hubsan	H107D	Quad	A7105
Hubsan	H111	Quad	A7105
Huaxiang Toys	Sky Walker 8983	Quad	NRF24L01
JD	JXD 385	Quad	NRF24L01
JD	JXD 388	Quad	NRF24L01
JD	JXD 389	Quad	NRF24L01
JD	JXD 390	Quad	NRF24L01
JD	JXD 391	Quad	NRF24L01
JD	JXD 392	Quad	NRF24L01
JD	JXD 393	Quad	NRF24L01
JIAYUAN	S-2	Quad	NRF24L01
JJR/C	1000A	Quad	NRF24L01
JJR/C	F180	Quad	NRF24L01
JJR/C	F182	Quad	NRF24L01
JJR/C	H8C	Quad	NRF24L01
Landbow	X-Dart Next	Quad	NRF24L01
Ni Hui	U207	Quad	NRF24L01
Nincoair	Quadrone	Quad	NRF24L01
Sanlianhuan	SH 6043 Ladybug	Quad	NRF24L01
Sanlianhuan	SH 6044	Quad	NRF24L01
Sanlianhuan	SH 6046 Puffer	Quad	NRF24L01
Sanlianhuan	SH 6048 F22	Quad	NRF24L01
Sky Walker	HM-1306	Quad	NRF24L01
Skybotz	Mini UFO	Quad	NRF24L01
Skyline	YD717	Quad	NRF24L01
Syma	X1	Quad	A7105
Syma	X2	Quad	NRF24L01
Syma	X3	Quad	NRF24L01
Syma	X4	Quad	NRF24L01
Syma	X5C	Quad	NRF24L01
Syma	X5C-1	Quad	NRF24L01
Syma	X6	Quad	NRF24L01
Syma	X7	Quad	NRF24L01
Syma	X8C	Quad	NRF24L01
Syma	X11	Quad	NRF24L01
Syma	X12	Quad	NRF24L01
Toybase	L6036	Quad	NRF24L01
Toybase	L6038	Quad	NRF24L01
Walkera	QR Ladybird	Quad	CYRF6936
Walkera	QR InfraX	Quad	CYRF6936
Walkera	QR X350	Quad	CYRF6936
WL TOYS	v929	Quad	A7105
WL TOYS	v939	Quad	A7105
WL TOYS	v949	Quad	A7105
WL TOYS	v959	Quad	A7105
WL TOYS	v202	Quad	NRF24L01
WL TOYS	v212	Quad	NRF24L01
WL TOYS	v222	Quad	NRF24L01
WL TOYS	v252	Quad	NRF24L01
WL TOYS	v252 Pro	Quad	NRF24L01
WL TOYS	v262	Quad	NRF24L01
WL TOYS	v272	Quad	NRF24L01
WL TOYS	v323	Hex	NRF24L01
WL TOYS	v333	Quad	NRF24L01
WL TOYS	v343	Quad	NRF24L01
WL TOYS	v353	Quad	NRF24L01
WL TOYS	v393	Quad	NRF24L01
WL TOYS	v626	Quad	NRF24L01
WL TOYS	v636	Quad	NRF24L01
WL TOYS	v646	Quad	A7105
WL TOYS	v666	Quad	NRF24L01
WL TOYS	v676	Quad	A7105
XINXUN	X28	Quad	NRF24L01
XINXUN	X30	Quad	NRF24L01
XINXUN	X33	Quad	NRF24L01
XINXUN	X39	Quad	NRF24L01
XINXUN	X40	Quad	NRF24L01
YI ZHAN	X4	Quad	NRF24L01
YI ZHAN	X6	Quad	NRF24L01

You can get Android application (BTCon4Drone) at play.google.com/store/apps/details?id=com.pinggusoft.btcon

All of it does not matter

I finally demodulated the binding packets using an excellent HackRF Jawbreaker and Gnu Radio. I used www.inguardians.com/pubs/GRC_signal_analysis_InGuardians_v1.pdf as a guide.

The results are the following: if I use my own code and both nRF24L01 and Beken 2421 I can successfully demodulate the signal and can see preamble (0xAA), the address (five 0xCC bytes), and following packet bytes.

If I try to demodulate XN297 I can see some demodulated signal which coincides with the radio signal but have no such well defined structure - I can't see the preamble and address - just some bytes arbitrarily appearing.

I will look at it more - I have an impression that it is passed through some scrambler. It is untypical to do so - usually only the contents of the packet is scrambled and preamble and address are as is.

pmc wrote: I have the New blue version.
I have the devo 7e versie 4.0.1
It har noen options for the protocol, just yd717.It binds without any problems. I just need a good ini to try. If you have One please post it.

So you are trying to fly a Blue PCB CX-10 with your Devo?
Sorry, It's not possible . The only version works with Devo TX it's the Original First Red version, using YD717/Sky Walker protocol.

Here is my CX-10 model file and Icon.
FMODE1 to high rates.
HOLD1 to activate flip mode.

victzh wrote: Durete, are we talking about controlling Cheerson CX-10 with Devo and nRF24L01+ module? What protocol code do you use? I was not so lucky and there is a thread discussing it with very little luck: www.deviationtx.com/forum/protocol-devel...nt/3368-jd-395-cx-10

How did you manage to do this?

Hi Victzh.

There are 3 CX-10 versions. The first original version (Red PCB version) uses YD717/Skywalker protocol using nRF module.
The thread you linked me, is about the second "Green PCB version", with XN297 module.
After these version, the sellers start to sell a new "Blue PCB version" with XN297 module but different protocol than "Green PCB version".
It's a shame, because the original version could be controlled with Devo TX but the better flyer it's probably the Green PCB version.

Durete, are we talking about controlling Cheerson CX-10 with Devo and nRF24L01+ module? What protocol code do you use? I was not so lucky and there is a thread discussing it with very little luck: www.deviationtx.com/forum/protocol-devel...nt/3368-jd-395-cx-10

How did you manage to do this?