protocol for WL Heli V911-s

I've noticed that the LED on the heli flickers and is not steady as with the original remote. Strangely it does not appear random which is what I would expect from random packet loss. When paying attention to rapid servo movements, I can see that it is not as smooth as it should be. But even if I send exactly the same ID/Freqs as the original it does the same... (I've also double checked all timings)
Anyway and at least for me the heli is perfectly flyable as it is, you don't notice the behavior while flying.
I've pushed the code on my github.
Pascal

Great news!! Thanks for all your efforts.

If you need a tester once you've got it ported to Deviation I've got aV911S and 4-in-1s in a Devo 10 and Devo F12E, and all modules except the CC2500 in a Devo 8S.

I don't suppose you can tell if there are any possible undocumented channel features, such as channel 5 for use as a 3G/6G mode switch? I hate the 6G only with the stock transmitter and was hoping the receiver might might have 3G capabilities like all other 6 axis helis.

BirdBarber wrote: I don't suppose you can tell if there are any possible undocumented channel features, such as channel 5 for use as a 3G/6G mode switch? I hate the 6G only with the stock transmitter and was hoping the receiver might might have 3G capabilities like all other 6 axis helis.

There are 2 bytes in the payload packet[1] and packet[2] with only 1 bit in each used as flags. You can always test all the others 14 bits to see if there is a hidden feature...
But like goebish said I'm not sure it's worse the time as such a feature would have been marketed.
Pascal

planger wrote: There are 2 bytes in the payload packet[1] and packet[2] with only 1 bit in each used as flags. You can always test all the others 14 bits to see if there is a hidden feature...
But like goebish said I'm not sure it's worse the time as such a feature would have been marketed.
Pascal

I know others beside myself are interested in testing for 3G capability. The V911S is so beginner specific that we wonder if 3G is not available from the transmitter so a beginner can't accidentally put it in 3G mode and get in over their head.

Will those unused flag bits be available to a Deviation user to experiment with by mapping them to unused channels or by some other method? Either 14 on/off virtual channels or maybe 2 virtual channels where TX values from 0 to 127 (or -100 to +27) are mapped to the 7 unused bits of the 2 packets?

Great! Thanks.

And thanks again guys for all of your great work on this and previous protocols.

I got the test build from Dropbox and installed it on a Devo 10 with 4-in-1. I already had a 2 month old nightly build file system installed (deviation-devo10-v5.0.0-362ffd0) so I only installed the DFU (deviation-devo10-v5.0.0-c02102f.dfu). I got the 'V911S' protocol to show up, but can't get it to bind.

I tried both 4 and 5 channels, with and without fixed ID. The Deviation bind timeout is extremely short and on the receiver I get the 4 blinks... pause... 4 blinks... as if the transmitter was still off. I also tried the TX 'power on' binding with both heli powered first and then with TX powered first. Nothing worked. I then tested the heli again with the stock TX and it bound after 2 or 3 seconds, and the Deviation bind timeout is much less than that (under a second). It's getting late here so I will check back tomorrow.

Edit: Also note that I pre-ordered my V911 very early and it is one of the first built and may have even been the first one in the US. I'm just mentioning it in case WL made a change after mine was built.

Yes, most of the tests were done with the Bind button on the Model Menu (4ch Fixed id, 4ch no id, 5ch fixed id, 5ch no id). It times out almost instantly both when I press the bind button or when I power up the Devo 10 and get the instant "Binding WL V911S... Press ENT to stop, 0 seconds left" message.

I have a confirmation on rcgroups that the protocol works for someone else.
Pascal

Can you post a link to your code? I'll check if I can pinpoint something...
Pascal

I've done more testing with a Devo 10 and 8S.

With the Devo 10 with 4-in-1 it still doesn't bind. The bind switch timeout is now longer, but still only about 1/2 second and it wouldn't bind. The power up autobind is still the same, only a slight fraction of a second.

So I tried on an 8S that has a separate NRF24L01 module instead of a 4-in-1. I installed the file system and DFU. It did bind using the bind button, but it took 3 tries and finally bound after about 2 seconds. After that, it would re-bind in under a second. The power on autobind also showed a bind message but would not bind. The timer on it is set for 2970 seconds, a bit long, lol. The bind button timeout is at about 3 seconds, but it doesn't show the binding message the first time I press it, but it does beep after 3 seconds. Pressing bind again and I do get the binding message which runs from 2970 seconds until timeout at 2967 seconds.

I thought you had transmitter power on autobind turned off for the V911S protocol. But I get an autobind message immediately upon powering up the Devo 10 and Devo 8S.

I'll be in and out the rest of the day, so It may take me a couple of hours to respond to messages.

Edit: I did more tests with the 8S. The first time I press the bind button the receiver responds with a fast blink but doesn't bind, and the TX doesn't show the binding message, but it does beep then quit after 3 seconds. If I press the bind button again I do get the binding message, the receiver doesn't switch to fast blink but it does bind after 2 seconds. I'm clearing the bind information off of the receiver by binding it with the stock TX between Deviation tests.

I went to take off and the lights in my room went out the instant it took off. I thought 'now that's a bug' lol. Then I heard a crash in the dark a second later. The channel layout is the same as the V911 but you need to not reverse the ELE channel. With the lights repaired and ELE un-reversed it flew fine. I was using a discharged battery so it was a short flight from very close range.

All of my recent testing on both transmitters was done at 30mw, 5 channels, no fixed ID.