SYMA X5C-1, X11, X12

The pitch and roll trims, I'm not sure they are working because the slow rates.

you guys rock.. I wish I could help out heck ill buy a spi reader and tear some tx's apart lol.. I want the green/blue cx-10s to fly with my devo7e . anyway, good work here guys I will be flashing the posted nightly this evening and giving the x11 a go with my 7e and a big smile! thanks again
Neil

Durete wrote: The button assignment is perfect, all channels are working now as you wrote before, and without reverse.
The yaw rate is a little bit slower also, but not scandalous as pitch and roll.

About the name for the protocol in YD717 maybe the Syma X4 is more widespread, but I'm not sure. What do you think Seby?

@Hexfet, do you need any other capture? I have the cables soldered to the module, so very easy for me.

Please try the attached build and let me know how the rates are.

Despite the name, the trim channels to the receiver are unrelated to the Deviation trim. You don't need to test trim settings on the Devo.

No other traces needed unless there are buttons we haven't covered.

I changed the YD717 protocol option to "SymaX4". Don't think there's any way to find out how many deviation users are really flying these models.

Yeaaahhhh! Working 1000% perfect!



Now the rates are perfect, same as with original transmitter.
All settings working perfect, flip, rates, all....

Thank you Hexfet!

I include my Model file for Devo 7e for everyone needs to use.

Throttle trim down, start/stop video capture.
Throttle trim up, take picture.
Fmod1. High rates.
Hold1. Flip mode On.

Great! Nice video

I'll make a pull request to the deviationtx repo so it'll get in those nightlies soon.

Next will be to try randomizing the tx address in the X11 protocol and see if that works. Then add the camera controls when we get the data and should be done. Til Syma makes the next variation...

Neilyboy et al, feel free to help test. Always good to verify it's not just one quad that's working.

A new info a little bit off topic...
I read some minutes ago at RcGroups, the latest Syma X4 are using the new SymaX protocol, so we continue to have all Syma protocols covered

Neilyboy wrote: you guys rock.. I wish I could help out heck ill buy a spi reader and tear some tx's apart lol.. I want the green/blue cx-10s to fly with my devo7e . anyway, good work here guys I will be flashing the posted nightly this evening and giving the x11 a go with my 7e and a big smile! thanks again
Neil

I wish my CX-10 "green" and JXD 395 could fly some day with my Devo Tx, but according the info on his Development thread is not very clear the XN297 transceiver could be 100% nRF24L01 compatible

@Hexfet, I saw at your build a "CX-10" protocol. What is supposed to control this protocol?

The CX10 protocol is an implementation of the protocol captured in this thread . It doesn't work with an nRF24L01. Don't think anyone's tried it with an XN297 module.

The protocol writes to three registers in the XN297 that do not exist (or at least are not documented) in the nRF device, so perhaps that's why it's not working. Or it could be a coding mistake.

I couldn't find XN297-based modules on ebay or amazon, so not much reason to pursue it. If someone wants to put an XN297 module in their devo, the cx10 protocol may work. It would also be interesting to see if other nRF protocols would work.

OK ok, understood.
So the challenge is to install an XN297 based module, and test into an Arduino implementation or Devo TX a XN297 based protocol, and a nRF24L01 based protocol for compability test.

Durete wrote:

Neilyboy wrote: you guys rock.. I wish I could help out heck ill buy a spi reader and tear some tx's apart lol.. I want the green/blue cx-10s to fly with my devo7e . anyway, good work here guys I will be flashing the posted nightly this evening and giving the x11 a go with my 7e and a big smile! thanks again
Neil

I wish my CX-10 "green" and JXD 395 could fly some day with my Devo Tx, but according the info on his Development thread is not very clear the XN297 transceiver could be 100% nRF24L01 compatible

@Hexfet, I saw at your build a "CX-10" protocol. What is supposed to control this protocol?

Ah so its different hardware all together.. That makes sense I saw that it started off well then just kind of died.. I figured there was something behind the lack of interest.. It honestly would not be worth it if longer range hardware was not available (not that your going to fly a cx-10 farther than 50 yards away). If there were a decent medium/long range xn297 chip out there I would deff buy another 7e just to give it a go lol. Back to the x11! Excellent work!
Neil

@HexFet, are last changes available in your repo ?

SeByDocKy wrote: @HexFet, are last changes available in your repo ?

Yes. The symax_x11 branch has the changes branched from the current PB repo, while default also has a few other recent fixes.

I'm using a build from the deviationtx repo because it has other additional fixes/features. The symax_x11 branch in that repo is also up-to-date and will be merged to default soon.

Gents, please test the attached with x11, x12, and/or x5c-1. This build randomizes the tx address to reduce interference between multiple transmitters.

Thanks!

Sorry, don't work



When start the controller, the led stop blink for a moment, but one second later start to blink.

If you need it, I can try to capture bind process from my X11 TX, or wait for the X11-C capture, to have the bind sequence from another transmitter.

yes, it looks like we'll need captures from some additional transmitters. This likely indicates that the transmitter ID is involved in the checksum calculations or the selection of channel hopping frequencies.

Either way is fine. May need captures from more than one additional transmitter to figure it out.

Ok, I will capture SPI traces from my X11's transmitter ASAP, and later from my X11-C when receive.

Please give this a try. I'd missed changing the checksum on the bind packets. Based on the behavior in the video I don't think it will make a difference, but maybe...

I'm sorry, don't work
Now, the leds at the X11 never stop blinking, don't make the tentative to bind, so worse situation.

Today, I had time to fly for about 3 batteries my X11 in good conditions. I'm impressed about the range for this protocol at 250Kbps.
I flew with my Devo 7e configured to 10mw to about 70/80 meters without the minor signal of lose bind. Really impressed.

Later, I will capture SPI bus at my X11's transmitter.

Durete wrote: Today, I had time to fly for about 3 batteries my X11 in good conditions. I'm impressed about the range for this protocol at 250Kbps.
I flew with my Devo 7e configured to 10mw to about 70/80 meters without the minor signal of lose bind. Really impressed.

Later, I will capture SPI bus at my X11's transmitter.

This is why I choose the X11 as microFPV plateform

SeByDocKy wrote:
This is why I choose the X11 as microFPV plateform

Probably, now the problem is the 5.8Ghz signal