Flysky AFHDS 2A, protocol as used i10, i6, iT4,

More
07 May 2017 15:18 #62103 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I'll tested this version and flight performance, betaflight + ibus inc new telemetry X6B it seems reliable.
Had a quick look at the LQI, it is 100% at few meter and a few hundred meters it is down to 60%, not sure where the thresholds for range warning to be set, but seems a quite stable readout getting down with range, probably logarithmic?

Please Log in or Create an account to join the conversation.

More
07 May 2017 15:27 #62104 by goebish
I'm not sure, but I think 100 = 100% of expected packets have been received (it's named "error rate" on actual AFHDS-2A transmitters), so unlike RSSI it's not logarithmic.

Please Log in or Create an account to join the conversation.

More
07 May 2017 18:52 #62112 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
latest firmware the external RX Volt, it is still C1, don't see a difference.

Please Log in or Create an account to join the conversation.

More
07 May 2017 19:24 #62114 by goebish
Have you checked AllCell ? It should be the sum of C1...C6

Please Log in or Create an account to join the conversation.

More
07 May 2017 21:18 #62117 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
hmm I get 0V at All cell, C1 is still displaying correct voltage as before.

Please Log in or Create an account to join the conversation.

More
07 May 2017 21:22 #62118 by goebish
Weird, I'll try to debug that.
Thanks for testing ;)

Please Log in or Create an account to join the conversation.

More
07 May 2017 21:36 - 07 May 2017 21:39 #62119 by goebish
Well, it should work, when I set AllCell in the code I can see it here:



Are you sure you're testing with the d1edbbc version ?
Last edit: 07 May 2017 21:39 by goebish.

Please Log in or Create an account to join the conversation.

More
07 May 2017 21:44 #62120 by goebish
Ah Ok, I think I found my mistake ... I'll build a new version :)

Please Log in or Create an account to join the conversation.

More
07 May 2017 21:50 - 07 May 2017 21:51 #62121 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
No I do not see that as you show, I double checed and confirm use your firmware ending "edbbc" that field is at 0V.
I still have the third field row 1, C1 displaying the ext Rx voltage.

I also select mainpage config AllCell and also, here displayed 0V.


******Edit forgot this post, waiting to test******
Last edit: 07 May 2017 21:51 by Fernandez.

Please Log in or Create an account to join the conversation.

More
07 May 2017 21:51 #62122 by goebish
Please check this one, I'm pretty confident it should work now:
www.dropbox.com/s/s06er6pg3gnr2mi/deviat...0.0-b6829cc.zip?dl=1

Please Log in or Create an account to join the conversation.

More
07 May 2017 21:59 - 07 May 2017 22:05 #62123 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Yes it works the AllCell Field and Cell1 field contain same value.
AllCell field can be used now to trigger battery lipo empty alert and it works.

I have no Flysky sensors to connect, so I can't do more testing from my side.
But I am wondering what happens if connecting a Flysky "lipo" sensor to the balance lead.

Maybe some others can help.
At least for me this is a very useable system now Pack Voltage and Range alerts !


Btw when connecting an Rx at the table, I connect the same volt to RX and to the Vbat port, I read: 5.07V Rx 5.01 V Cell1, to give idea about accuracy same voltage.
Last edit: 07 May 2017 22:05 by Fernandez.

Please Log in or Create an account to join the conversation.

More
07 May 2017 22:06 #62124 by goebish
All good, so it's ready to be merged now :)
... should appear soon in the nightly builds.

Please Log in or Create an account to join the conversation.

More
07 May 2017 22:08 - 07 May 2017 22:42 #62125 by goebish

Fernandez wrote: But I am wondering what happens if connecting a Flysky "lipo" sensor to the balance lead.

It should appear in TelemV2 (and TelemV3 if you daisy chain 2 of them), and not counted in AllCell.
Last edit: 07 May 2017 22:42 by goebish.

Please Log in or Create an account to join the conversation.

More
10 May 2017 15:15 #62209 by Quadman
I have the QX 95 which binds on the Flysky AFHDS 2A, protocol is this available for my devo 7e I have the 3 in one module connected and run all 4 chips?

Please Log in or Create an account to join the conversation.

More
10 May 2017 15:19 #62210 by goebish
Yes, the AFHDS-2A protocol should work, but I don't know if telemetry is available on your Rx, and even if it is, C1 and AllCell telemetry are not available on the 7e (no HAS_EXTENDED_TELEMETRY because of limited memory)

Please Log in or Create an account to join the conversation.

More
10 May 2017 15:37 #62211 by Quadman
Has it recently been added or is it the original flysky protocol, in the menu, I believe my devo is running version 5 and one of the nightly builds from 11/2016 ?

Please Log in or Create an account to join the conversation.

More
10 May 2017 15:38 #62212 by Quadman
Oh and telemetry does not matter as the QX 95 does not have.

Please Log in or Create an account to join the conversation.

More
10 May 2017 16:00 #62213 by goebish
If it is from 11/2016 then AFHDS-2A protocol should be available (not the same than FlySky, which is older AFHDS)

Please Log in or Create an account to join the conversation.

More
10 May 2017 16:30 #62215 by Quadman
The only Protacol for Flsky my 7e has is flysky, WLToys ext V9x9 V6x6 and V912, looks like I need to load a nightly build?

Please Log in or Create an account to join the conversation.

More
10 May 2017 20:11 - 10 May 2017 20:13 #62218 by goebish
Yes, flash the latest nightly, you'll also have to copy layout and media folders to the filesystem, they've been modified recently.
AFHDS-2A is a new protocol, not of sub-format of Flysky.
Last edit: 10 May 2017 20:13 by goebish.

Please Log in or Create an account to join the conversation.

Time to create page: 0.102 seconds
Powered by Kunena Forum