protocol for WL Heli V911-s

goebish wrote: Ok, nightly build is still using nrf24, not the cc2500 (still experimental).

You mean the test build works with default ID 123456 now ? I though it didn't work

Just reading in diagonal .... Are you able now to reproduce any 256kbit/s nRF24L01 based with a CC250 ?

goebish wrote: XN297L@250kbps, yes

iirc you have an YZ i6S, that's one of the protocols using this mode, would you like that I add it to the test build ? Not a very popular model, you might be the only one able to test it

Outch..... the question; where is this one.... I moved a lot under my house .... yes under ... in the small saninatary void .
but maybe not this one coz it's a small model.... I will have too look a bit in next days

Good news for the CC2500 workaround

goebish wrote: dozens of models scattered everywhere around the house, I know what you mean

For me it's around 400

Yes, 123456 works now with Frq-Fine set to 25, I will try another IDs and will report results if I get good news!

Good morning, goebish.

Test build deviation-t8sg_v2_plus-v5.0.0-ee7176e

We will notify you of the bind test results.

XK K100. JJRC H8-MINI.H8S-3D.H98, X400, X600, X800, SYMA X5C-1 worked without any problem.

Nice to meet you all,

My t8sg v2 plus can't bind V911S at ee7176e
Tried Freq-Fine -127 to 127 in 5 intervals at ID 123456.
Does V911S have different IDs depending on individuals?

Kio wrote: Nice to meet you all,

My t8sg v2 plus can't bind V911S at ee7176e
Tried Freq-Fine -127 to 127 in 5 intervals at ID 123456.
Does V911S have different IDs depending on individuals?

my v911s worked with ID : 123456 / 888888 / 999999 , Freq-Fine=25.

Thank you dc59,
Thank you goebish,

I tried trying ID: 123456/888888/999999, Freq-Fine = 25. My V911S did not respond.

It seems that you need to try various combinations.

Also, I will try it next time.

HAd time to play = Flaky !
Tx just turns off for no reason , and all settings are lost ...

No bind yet !
I will try and change the ID , but a CRASHING OS means I cant use the firmware for flying .. ( Which is OK , I have a T12 )

I purchased/received an XK A120-A380 plane, a guy on Youtube found that it would work with the V911-S protocol.
I first tried to bind it to my Devo 6S tx (nightly build, 4-in-1 module), no dice.
I then found it would bind to my 7E (with standalone nrf24l01 module) and also my Devo 10 (same brand 4-in-1 module as the 6S).
I installed goebish's test build linked to earlier in this thread on my 6S tx and still no dice, I varied the freq. fine tune the whole range in steps of 20, varied the Fixed ID, but still no luck.
Any suggestions?

yes I can bind my XK A120-A380 plane with my 7e on V911-S protocol, ID = 123456 too

will try with my friend's Jumper T8SG in these two days

cmPang

Hi, I am always thankful to the developers.
I tried goebish's test-build / CC2500 (ee7176e) with several transmitters I own.

tx	id	FreqFine	Power	Result
Devo6 w/ 4in1	123456	-50~+50	1mAh	Failure
	123456	-127	1mAh	Failure
	123456	-127	10mAh	Success
	123456	-127	30mAh	Success
	123456	-127	100mAh	Failure
	123456	-127	150mAh	Failure
Devo7e w/ 4in1	123456	-50~+50	1mAh	Failure
	123456	-127	1~150mAh	Failure
Devo7e w/ 3in1	123456	-50~+50	1mAh	Failure
	123456	-127	1~150mAh	Failure
Devo10 w/ 4in1	123456	-50~+50	1mAh	Failure
	123456	-127	1~150mAh	Failure
IR8M	123456	-50~+50	1mAh	Failure
	123456	-127	1~150mAh	Failure
T8SG (1st Gen)	123456	-50~+50	1mAh	Failure
T8SG V2 Plus (1)	123456	-50~+50	1mAh	Failure
	123456	-127	1mAh	Success
	123456	-127	10mAh	Success
	111111	-127	1mAh	Failure
	888888	-127	1mAh	Failure
	999999	-127	1mAh	Failure
	123455	-127	1mAh	Failure
	123457	-127	1mAh	Failure
T8SG V2 Plus (2)	123456	-127	1mAh	Failure
	123456	-127	3mAh	Failure
	123456	-127	10mAh	Failure
	123456	-127	30mAh	Failure
	123456	-127	100mAh	Failure
	123456	-127	150mAh	Failure

I can not understand. It should be the same but success or failure.
If I keep making mistakes, I wonder if I can not bind at all even if I set the same transmitters until then.
The transmitter I own is equipped with almost all 4in1 modules.
Devo6, Devo7e and Devo10 are Retail version 4in1 modules purchased at the same time.
The IR8M is an initial version, but the 4in1 module has been replaced with the Retail version.
There are two T8 SGV2 + s. It is what I purchased recently with 1st lot.
As for the value of Freq-Fine, since the value set for the first successful Devo 6 was -127, it is set and tested on other transmitters as a successful example.
The ID succeeded only 123456.
It fails or succeeds due to transmission output. Even if the output is small, it is useless, too large, it seems like useless, is there a sweet spot? I do not understand.

p.s. I can only speak Japanese. This sentence is in English with GoogleTransrate. I am afraid that I have not transmitted it correctly. Thank you sorry.

Hi Goebish,

It has been a while since I last flew my micro's, It took me a while to figure out which protocol to use over the weekend as I was sharing ini files for some of them.

Somehow I had to rebind my V977 with XK Rx and K100. Not sure if they can loose binding in staying powered down for too long.

According to my counting, I have more than 10 sub120 working micros but I still want to add a V911S.

Is this working yet?

Would it be it an issue with crystal? Is it cc250 or nrf24l01 based?

Regards

I haven't bought it yet. Probably would have one in July or August.

Thanks.

+++++++

Is the protocol working?

If I buy a V911S BNF, my devo 10 has to be able to control it.

goebish wrote: Yes
www.deviationtx.com/forum/protocol-devel...911-s?start=40#71667

Devo10-v911s
i have successfully connected with devo10 (fw deviation-devo10-v5.0.0-7fb7de1) . thanks Goebish