protocol for WL Heli V911-s

I just did some bench testing using the 8S. The servos seem to work smoother than the stock transmitter. But I did notice that when bound to the 8S the receiver LED is blinking so fast it's hard to tell it's blinking. The LED is on solid with the stock transmitter.

Ok, I read the post about the crystal accuracy.

FYI: My 8S is using the NRF24L01 module with PA and LNA, and it has an external antenna. The 4-in-1 on my Devo 10 is one of the first built, back when you had to have a Chinese broker buy it direct from the manufacturer and then ship it to you. It seems like there might have been a change to the 4-in-1 since then, but I'm not positive. Seems like maybe it has something to do with the routing of the traces to the antenna, but again, I'm not positive. It wouldn't be that odd for the manufacturer to have changed parts suppliers once he went into full production also.

Kiwi_Craig is going to start doing some testing with his Devo 10 with 4-in-1. We'll see if his 4-in-1 has any better luck at binding, but I think it might just be the bind time is too short on the Devo 10 version.

Confirmed. The bind display & timer now work for 3 seconds, there is no more power on autobind message. And unfortunately, as you said, it won't bind with the Devo 10. No change to the receiver LED at all, still 4 blinks - pause - 4 blinks..... as if the transmitter is off. Is there any way to tune the frequency by using something similar to the CC2500 freq-fine menu adjustment? If the problem was just drift I would think that it would bind occasionally.

I haven't tried the new code for the 8S, if it even exists. But yesterday's release always takes 2 tries to bind. The first one makes the receiver blink fast, but no bind. And the second attempt almost always binds, I have only had to try 3 times once. Once it's bound, it stays bound during power up/down cycles of both the TX and heli.

I'm using a Black Devo 10 with the permanent antenna, but I could open it up and try a temporary antenna just as a test.

Also, I added info to my previous post.

I'm going to sleep in a bit, then gone most of tomorrow.

I've got one more confirmation that it works on rcgroups.

Just a thought, you might want to try with the ID/freqs from the original TX just to eliminate this as the potential source of issue.

Pascal

The original id version doesn't bind either. I tried about 10 times.

I left the fixed id field blank, do I need to put the original ID in it?

Just a reminder, I've got a Devo F12E with 4-in-1 I can do testing with whenever you port the code.

The F12E wouldn't bind. The 4-in-1 in it is from the same July 2016 batch as the one in my Devo 10. I think the problem with the early 4-in-1 modules might have been with the LNA. I don't know if this protocol needs the LNA to listen to the receiver when binding or not. I'm not sure if mine have the new or old LNA. I think somebody with a newer 4-in-1 should give it a try.

The bind button timer looked fine. But I did get one power on autobind the first time I power cycled the TX after trying the new protocol. But it never did it again.

This protocol does not listen, it just sends...

Another successful report: www.rcgroups.com/forums/showpost.php?p=40462565&postcount=12902

It's strange that no one is reporting issues on the Multi module. They all use a 4in1 RF board from the same designer...

Pascal

I just tested my Devo 10 4-in-1 NRF24L01 module by binding to a HiSky HCP100S, it works fine (at a higher bit rate I assume).