Advanced Search

So i got the green cx-10 board but why is it not binding , selected yd171 protocol but no luck . What does it mean by select sky walkr protocol option ?

PhracturedBlue wrote: you could go to the amazon warehouse with screwdriver in hand

Dont overlook this option, of course Amazon isnt going to let you but I've headed down to my local hobby shop numerous times (BuddyRC) with tools to take something apart BEFORE I BUY IT to verify it was exactly what I wanted, again dont even bother asking amazon but your LHS should understand the issues and work with you.

In fact, Buddy sells CX-10's (or maybe CX-11's, I actually dont know the difference between them) but if it's that important to you, and you want to call Garry and set it up, I'll go there and check for you (hell Garry might even check him self), it's literally an 8 minute drive from my house (how lucky is that!).

you could go to the amazon warehouse with screwdriver in hand

There is no way, they'll send you an arbitrary choice of 3 models - red, green, or blue. And this is not necessarily a color of the copter board, it's the color of controller board. Red and green are now supported, blue is not.

I have an opposite problem - I need blue to test it, but there is no guaranteed way to get it

Guys, where can i buy a deviation compatible CX-10 ? i was reading somewhere here that the green board will work but how can i tell by just looking at the model?

Thanks,

submitted a pull request:
bitbucket.org/deviationtx/deviation/pull...-3d-x4-attop-yd/diff

@goebish, I added a pull request with my XN297 emulation code (still one directional, didn't have time to tackle reading yet) and CX-10 green board code. After it is accepted, feel free to modify CX-10 to add arbitrary TX id.

As PB suggested, I moved XN297 emulation code to nRF24L01 module, so it should be available for any other XN297 based protocol.

I'll try to approach reading next week, time permitting.

my module is working, I can bind with my Syma X5, X11, JJRC H8C and the CX-10 , so I will review the settings on the ini file, maybe I'm doing something wrong

I just coded it for Taranis XN297 module, for my green CX10, and it seems like it works. I constrained TXID[1] to be less than < 0x30 as you suggested.

I should verify the values are getting generated as expected, and then I'll update the code on my blog on rcgroups.

(edit - DONE!)

Just modified the code for PPM/xn297 module for the blue pcb CX10 to use a random tx id and matching rf channels, it works, don't even need to limit packet[2] actually, it works even with 0xFF.
gist.github.com/goebish/f8982353c34f2b71ffe8

edit: well, it works but maybe the rx drops 1/4 of the packets... I'll constrain packet[2] to 0x2F just to be safe ...

Yes, but it has to be confirmed, I haven't tried against an actual RX yet
Not sure if packet[2] should be limited to 0x1F or 0x2F

goebish,
Very impressed that you figured this out.

Other than the limitation you mentioned for packet[2], are you assuming the data packet sequence is just randomly generated?

goebish wrote: Yes, cx10 blue pcb & cx10-A are using the same protocol.
Looks like there are 2 kinds of "blue" pcb CX10, some fly as good as green ones, some other are just slow and not fun (as the one I have, seems to be the case for the CX10-A too ...)

Damn, I think I got the crappy blue PCB one too. Although I'm not 100% sure. It might be just the TX.

Yes, cx10 blue pcb & cx10-A are using the same protocol.
Looks like there are 2 kinds of "blue" pcb CX10, some fly as good as green ones, some other are just slow and not fun (as the one I have, seems to be the case for the CX10-A too ...)

I have cx-10a. And I really hate it. The worst pico-quad I have.
Anyway - I can participate in testing. Is it equivalent to "blue board" of cx-10 without "a"?

goebish wrote: Yes, they are probably both "blue protocol", which doesn't work with deviation for now.

Thanks for the info goebish need to find another quad to test!

Yes, they are probably both "blue protocol", which doesn't work with deviation for now.

hi guys
Just purchased a cx10 and cx11 and found out the 10 has a blue board and the cx11 also won't bind but both the cx 10 and 11 remotes work on each other and the 11 is now a green board does this mean there are on the same protocol (blue PCb)

(I only got them to test my newly fitted modules but must say there great fun)
Any help appreciated

I think I got it:

so, packet[1~4] seems to be the TX ID, but only [1~2] has something to do with frequencies:

rf channel 1 = (packet[1] & 0x0F) + 0x03
rf channel 2 = ((u8)packet[1] >> 4) + 0x16
rf channel 3 = (packet[2] & 0x0F) + 0x2D
rf channel 4 = ((u8)packet[2] >> 4) + 0x40

Seems to work with the 6 captures I have.

Victzh could you try to implement that in your code ? (or I can add it to my test firmwares later)
Also I think packet [2] must be clamped to some low values... (0x00~0x2F ?) this has to be checked against an actual RX but in the stock TXs captures the maximum value I've seen is 0x10 (so rf channel 4 = 0x41), and when I was experimenting with the eachine 3d x4 I noticed weird results when rf channel is greater than 0x42, it still binds, but only works a few inches away before losing connection. Looks like this is a xn297 limitation because I've seen captures of a few different models and it seems none is using any rf channel greater than 0x42 ever (2466 MHz ?) despite the datasheet states 频率范围2400~2483MHz.

Yeahhh!!!