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

magic_marty
Offline

21 Jul 2017 20:23 #63549 by magic_marty

Replied by magic_marty on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

goebish wrote: That's because your Tx doesn't receive telemetry data for a few seconds, check your antenna.
Also, if you've one of the firsts x-in-1, the LNA is not working for the nrf24l01 and the a7105, this is a known issue, this has been fixed in the last revisions.

Weird thing to add, i got a second X6B rx for another build and it never drops the telemetry link..Not sure if it's a newer firmware version or maybe my first one is just buggy...Both are labeled with the same version# on them..

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

magic_marty
Offline

22 Jul 2017 06:43 - 22 Jul 2017 07:39 #63552 by magic_marty

Replied by magic_marty on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

So i thought i would try updating the firmware on the rx i have to see it it stops the telemetry drop outs and thanks to these instructions which i followed exactly my rx is completely dead and will not power on and the stlink will no longer connect to it at all...
So anybody wanting to update there firmware i advise against it...
github.com/povlhp/FlySkyRxFirmware

EDIT: Figured it out the ground wire came loose on the STM stick...Got it flashed and still get the momentary drop outs on the telemetry..Don't understand whats the difference between the 2 x6b's i have but the last one i got does not drop the telemetry link at all..Perhaps i will order another one to see if it does or not just out of curiosity ...

Last edit: 22 Jul 2017 07:39 by magic_marty. Reason: problem solved

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

Fernandez
Topic Author
Offline

17 Sep 2017 09:46 #64452 by Fernandez

Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

I think I have mentioned it before just checking with you. I have an issue with the ranges offset in betaflight.

ibus - betaflight, just setting a 3 pole switch deviation 100% scale.
I read in betaflight 1000 - 1497 - 1994.
It should be 1000 - 1500 - 2000

My main question, anyone who can test with original flysky transmitter ?
Is it the same behaviour?

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

goebish
Offline
I Void Warranties

18 Sep 2017 08:34 #64474 by goebish

Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Perhaps that's a rounding error, I'll check that when I get back home in 2 weeks.

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

MiSKLaCH
Offline

19 Sep 2017 08:30 - 19 Sep 2017 08:30 #64503 by MiSKLaCH

Replied by MiSKLaCH on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Fernandez wrote: I think I have mentioned it before just checking with you. I have an issue with the ranges offset in betaflight.

ibus - betaflight, just setting a 3 pole switch deviation 100% scale.
I read in betaflight 1000 - 1497 - 1994.
It should be 1000 - 1500 - 2000

A quick workaround could be, if possible, adjusting subtrims and/or using rxrange commands in BF CLI.

Last edit: 19 Sep 2017 08:30 by MiSKLaCH.

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

aMax
Offline

19 Sep 2017 09:45 - 19 Sep 2017 09:48 #64505 by aMax

Replied by aMax on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

I really can´t imagine why this is so important for the aux channels. Please tell me...
I think, this is only useful for the stick channels, the aux channels can be properly setup with the sliders in the mode section.
As far as I remember, I even restricted the weight for all switches in prior years using PPM. >>(signal frame size)

Devo7e, TaranisQ X7, R9M , 4in1 MM, Futaba FC18plusV3.2 & DFT/FLD-02

Last edit: 19 Sep 2017 09:48 by aMax.

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

Fernandez
Topic Author
Offline

19 Sep 2017 18:25 #64520 by Fernandez

Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Yes I just used switch channels 100% to prove /confirm the issue, I see same indeed also on sticks, but that could be affected by calibration worn out sticks etc.....

Indeed you can trim fly etc, but just wondering if it is deviation, betaflight.......

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

vlad_vy
Offline

19 Sep 2017 18:39 #64522 by vlad_vy

Replied by vlad_vy on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Fernandez wrote: I think I have mentioned it before just checking with you. I have an issue with the ranges offset in betaflight.

ibus - betaflight, just setting a 3 pole switch deviation 100% scale.
I read in betaflight 1000 - 1497 - 1994.
It should be 1000 - 1500 - 2000

My main question, anyone who can test with original flysky transmitter ?
Is it the same behaviour?

AFHDS2A protocol data packet

s32 value = (s32)Channels[ch] * 0x1f1 / CHAN_MAX_VALUE + 0x5d9;

0x5d9 = 1497

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

Fernandez
Topic Author
Offline

20 Sep 2017 08:49 #64538 by Fernandez

Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

So it confirms then it is not Betaflight....
So is the same scale when using an original Flysky Tx and IBUS ??

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

goebish
Offline
I Void Warranties

20 Sep 2017 08:51 #64539 by goebish

Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

I took the formula from the AFHDS (flysky) protocol, I'll fix it when I get back home.

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

Fernandez
Topic Author
Offline

20 Sep 2017 10:57 #64543 by Fernandez

Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Hmm maybe need to double check to be sure to find the real situation.....
Now from what I can remember that S-Bus and I-Bus ranges did not line up, so when switching between those ranges are different S-bus sbus 1030-1515-2000......

to be confirmed....

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

goebish
Offline
I Void Warranties

20 Sep 2017 12:33 #64545 by goebish

Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Sbus is weird, that's expected

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

thesacredmoocow
Offline

24 Sep 2017 22:18 #64634 by thesacredmoocow

Replied by thesacredmoocow on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

I'm sorry if this has already been mentioned in the thread somewhere, but from what I understand, the protocol has been cracked, right? Is there any version of the code for an arduino, to make a module similar to the multipro one?

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

quad450
Offline

26 Sep 2017 21:35 - 28 Sep 2017 15:57 #64680 by quad450

Replied by quad450 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Hi everyone,

first of all, thanks for all the work on this project.

Regarding the protocol, I just noticed a strange behaviour of RSSI with X6B receiver (I have a Devo7e with standalone nrf24l01 and A7105 modules):
Connecting the quadcopter to my laptop via USB I get real time variation of RSSI on my transmitter; on the contrary, if I use the battery to power on the aircraft, RSSI value changes with a big delay like if it is losing signal.

Any ideas?

EDIT: I have also found this www.deviationtx.com/forum/6-general-disc...power-afhds-2a#64720
It seems that TX power is set only in afhds2a_init(). So, if TX power is changed after powering on the transmitter, it is not set correctly.

Last edit: 28 Sep 2017 15:57 by quad450.

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

daniel.snowsurf
Offline

06 Oct 2017 15:28 - 06 Oct 2017 15:47 #64877 by daniel.snowsurf

Replied by daniel.snowsurf on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

I got a new X6B RX, binds to Devo 7E standard, not ultimate, FW is nightly build deviation-devo7e-v5.0.0-ef04024 (June 2017).
I've telemetry RSSI, LQI, RX V. But no external voltage sensor data

. Is it only available on devo7e-256?
How can I get battery voltage? Could I get it from FC SP Racing F3 (Wizard X220) through the iBus port?
Thanks

Edit: No OSD, so telemetry is what I need

Last edit: 06 Oct 2017 15:47 by daniel.snowsurf.

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

goebish
Offline
I Void Warranties

06 Oct 2017 15:30 #64878 by goebish

Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

It's not available on 7e (no EXTENDED_TELEMETRY), it's available in ultimate (devo7-256).

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

daniel.snowsurf
Offline

06 Oct 2017 15:51 #64879 by daniel.snowsurf

Replied by daniel.snowsurf on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Thanks Goebish.
Do you think it's worth trying to do a custom build (no experience building deviation).

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

goebish
Offline
I Void Warranties

21 Oct 2017 10:45 - 21 Oct 2017 15:13 #65156 by goebish

Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

@daniel.snowsurf I've hacked a 7e firmware with extended telemetry support for FrSky D & AFHDS 2A protocols at the expense of a few disabled stuffs (VIBRATINGMOTOR, MULTIMOD_SUPPORT, 4IN1FLASH). Also, I had to use size optimization flag for armgcc, I'm not sure this doesn't have any side effects, but everything seems to be fine, this firmware has been used by a few people since June already.
build: www.dropbox.com/sh/v1ckkohd8nmlc5a/AAA_n..._wCGMl8qbdtOgRa?dl=0
source: github.com/goebish/deviation/tree/7e_extended_telem

I'll probably not maintain it, that will be up to you to merge this branch with current master in order to update your build (if even possible, this build is already using most of the available flash space: 114.61kB out of 116kB).

ps: special thanks to my old armgcc toolchain (4.8.3) that produces smaller binaries than the current versions

Last edit: 21 Oct 2017 15:13 by goebish.

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

goebish
Offline
I Void Warranties

21 Oct 2017 12:30 #65157 by goebish

Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

Fernandez wrote: ibus - betaflight, just setting a 3 pole switch deviation 100% scale.
I read in betaflight 1000 - 1497 - 1994.
It should be 1000 - 1500 - 2000

github.com/DeviationTX/deviation/pull/306

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

goebish
Offline
I Void Warranties

21 Oct 2017 13:15 - 21 Oct 2017 13:48 #65158 by goebish

Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

thesacredmoocow wrote: I'm sorry if this has already been mentioned in the thread somewhere, but from what I understand, the protocol has been cracked, right? Is there any version of the code for an arduino, to make a module similar to the multipro one?

Yes, you could make an AVR version of the Multi Module with only an Arduino + A7105, it has the AFHDS 2A protocol:
github.com/pascallanger/DIY-Multiprotocol-TX-Module

I was using an simple arduino+a7105 module similar to the nrf24 multipro when I started hacking this protocol but I think I never completed the implementation ...
www.deviationtx.com/forum/protocol-devel...6-it4?start=60#47046

Last edit: 21 Oct 2017 13:48 by goebish.

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

Time to create page: 0.108 seconds

Re-enable mobile display