Bayangtoys x16 new version (altitude hold)

Hi I have an new bayangtoys x16, but I'm not able to bind it with my Devo7e (v5.0.0). The copter is the new upgraded version with alttidute hold.
I've tried several protocols (bayang, H8-3D,...) but the copter will not bind.

Maybe one of the experts has an answer or ideas?
In case I could get support from the experts, i would order an logic analyzer and capture the necessary informations out of the TX.

Thanks Seb.

First you need to find out which RF chip is used. This usually means screwing open your RTF transmitter and taking pictures of the biggest chips on the pcb. Or read their markings. Post your findings and we'll do the next steps from there.

Hi Moeder,

i've checked the RF PCB for the chip, its the XN297LBW. Picture is attached.

OK, then we need spi captures from the transmitter as the next step. Check this thread for details. You'll need a logic analyzer which can be bought for very little money for example on ebay. Look for salae compatible model, probably the easiest to get started with.

I have already ordered an salae compatible analyzer. Also soldered some wires to the RF chip.
Will reply in the next days with the SPI captures.

update from today: i have connected the xn297 to the logic analyzer (ch0-CSN; ch1-DATA; ch2-SCK) and captured the binding sequence.
The captured session is about 10sec, TX on after ~1.5sec, initiate binding after ~5sec (binding will be initiated with throttle stick to 100% and 0%). In the altidute hold version the throttle sticks is centerd by default.

I've uploaded the binding session:
www.dropbox.com/s/v223vcbc0dxmo45/bayang...nding.logicdata?dl=0

Also captured stick-movement & buttons:
www.dropbox.com/s/dptbqqwviao5mws/bayang...ticks.logicdata?dl=0
timestamp [sec] stick/button position
5 all center
10 throttle max
15 throttle min
20 yaw right
25 yaw left
30 pitch forward
35 pitch backward
40 roll right
45 roll left
50 rate high
55 rate low
60 take off/landing
65 photo
70 headless
75 camera

Good captures. The protocol is very similar to the baying protocol. I'll try to make first test version for you and will post it later in this thread for you to try out.

Ok, this is a first try. In Bayang protocol options select Format "X16-AH". Channel 11 is Take-Off/Landing, the rest is the same mapping as "regular" bayang protocol.

As with any new protocol, please take off props or tie down your quad before testing!

Hi Moeder,

thanks for this promt test build. On the desk the devo binds immediately to the copter. Also the reactions to the sticks apperas to be correct.
I will test it under real flight conditions.

Is there any table for the bayang protocol where i can find the channel mapping?

Freut mich das es klappt

So, are you successful?

Sorry, not until now. Maybe on the weekend.

Sorry for the delay, have tried to fly on weekend.
Unfortunately the copter has some problems to fly. Copter is not able to take off, drifts immediately to the side. Not controlable by TX. Issue is the same with original TX. Checked already the calibration, the props, motors, wiring...
I'm in touch with the seller, a new FCB is shipped. Will replace the FCB as soon as possible.

I haven't checked the flight behavior before. Only done some fundamental cheks (binding, arming...)

Hi,
received the new FCB today. Soldered it and the copter lifts off and stays stable. Hooray!
All simple functions are available with your protocol on my Devo7e.
Will try to add extended functions to the extra switches on weekend (camera, lift off, landing and so on)
Due to evening darkness im not able to test more today.

Moeder wrote: Ok, this is a first try. In Bayang protocol options select Format "X16-AH". Channel 11 is Take-Off/Landing, the rest is the same mapping as "regular" bayang protocol.

As with any new protocol, please take off props or tie down your quad before testing!

Hello,

Do you have a version for the DEVO 10?

Thank you for your reply.

Have a good day,

I will post the devo 10 build tonight

Here's the test build for devo 10. Please give feedback if you are successful. I'm still taking suggestions for the name of the protocol format option

I have problem about binding Bayang X16 to Multi module(iRangeX IRX4).

You made bin file about DEVO7, Is it suitable for Multi module(I have)?

If it is not suitable, how can I modify the Multi Module's firmware?

Thank you

@goebish: would you mind making a mm testbuild from my changes ? Users of this new protocol seem to be rare, so maybe together we can finish it faster