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

More
21 Dec 2017 15:22 #66558 by HTo1980
V5.0.0-ed27f5f

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

More
21 Dec 2017 17:45 #66559 by goebish
AFHDS 2A protocol has been merged more than 1 year ago, I suppose you're using a pretty old firmware ;)
Flashing a nightly build should fix your issue.
www.deviationtx.com/downloads-new/category/13-nightly-builds

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

More
21 Dec 2017 18:46 - 21 Dec 2017 18:50 #66561 by HTo1980
Thanks for your feedback. I used this one
However, this doesn't change a bit.

To the left of FlySky = J6Pro, to the right = Hubsan4, the list still lacks AFHDS 2A (pics attached).
I formatted the drive via windows to get rid of the old data and copied the content of the zip to the root of it.
Maybe it's something with the TX?
(And is it usual that one doesn't get any firmware version shown when going to "About Deviation"?)
Attachments:
Last edit: 21 Dec 2017 18:50 by HTo1980.

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

More
21 Dec 2017 18:50 #66562 by goebish
Have you flashed the .dfu to your Tx via Devention Upgrade Tools ?
Copying files to the filesystem doesn't update the firmware.

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

More
21 Dec 2017 19:01 #66563 by HTo1980
:whistle:
Couldn't be more precise. Thank you a lot. Have a good one!!!

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

More
10 Jan 2018 21:56 #66824 by Fer
Hi guys,

I have installed FS-iA6B receiver in one of my planes, and the servos (Corona DS939MG) move in a spasmodic - twichy way. Not terrible problem, but defenately i am not flying the plane with a problem like that. I replaced the receiver with a DSM2 one (unfortunatelly it's only a parkflyer) and the servos now move smoothly. Is this just a broken receiver i have, or is it maybe some other problem with the protocol? Am i doing something wrong, or maybe is there an option or a selection i can make to fix the problem? Thank you.

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

More
10 Jan 2018 22:08 - 10 Jan 2018 22:10 #66825 by goebish
Perhaps your A7105 module has an inaccurate crystal oscillator.
This can be fixed with recent versions of deviation (nightly), go to the protocol options settings (highlight AFHDS 2A then press ENT) then try different values for "Freq Tune" until the issue is fixed.
This is done in realtime, no need to rebind / reboot.
Last edit: 10 Jan 2018 22:10 by goebish.

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

More
10 Jan 2018 23:35 #66830 by Fer

goebish wrote: Perhaps your A7105 module has an inaccurate crystal oscillator.
This can be fixed with recent versions of deviation (nightly), go to the protocol options settings (highlight AFHDS 2A then press ENT) then try different values for "Freq Tune" until the issue is fixed.
This is done in realtime, no need to rebind / reboot.


I have 4in1 module installed. My firmware is 82d3345 and i don't see any option for "Freq Tune", only an option to change the servo hertz. I tryed that, it didn't help. I will install a new firmware tommorow and see if i can change anything to the better.

But, does this mean that i have a problem with every protocol using the 7105 module? I am worried that if it is a chip problem it affects all other aircrafts i have, although all other aircrafts controlled by 7105 are not planes, and i have not noticed any strange behaviour. What do you think? Thank you.

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

More
10 Jan 2018 23:39 - 10 Jan 2018 23:40 #66831 by goebish
Install a nightly build.
This is not a problem with the a7105 chip, just that the clock (crystal) of your a7105 doesn't oscillate at the same frequency than the one in your iA6B, this is a very common issue with CC2500 RXs (FrSky ...), not so with a7105 but it can happen, that's why I've added this option a few months ago.
Last edit: 10 Jan 2018 23:40 by goebish.

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

More
10 Jan 2018 23:42 #66832 by goebish
You can take a look at this thread to better understand the issue:
www.deviationtx.com/forum/6-general-disc...flysky-afhds-latency

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

More
11 Jan 2018 15:54 #66860 by Fer

goebish wrote: You can take a look at this thread to better understand the issue:
www.deviationtx.com/forum/6-general-disc...flysky-afhds-latency


Thank you goebish, i was able to fix the problem following your instructions. I installed a fresh version of nightly so i was able to experiment with frequency. A value of -170 seems to be optimum for smooth servo movement for my case, but many other values around -170 seem to work too.

Again thank you so much.

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

More
11 Jan 2018 15:58 - 11 Jan 2018 16:38 #66861 by goebish
You're welcome.
You can try to get it spot on (but it doesn't need to be, the Rx will still receive the packets fine even with a few dozen kHz off):
Find at which values it starts twitching (eg: -230 & -110) and use the value that's just in the middle (eg: -170).
Last edit: 11 Jan 2018 16:38 by goebish.

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

More
06 Feb 2018 11:46 #67415 by qba667
@goebish I have question related to original dump of protocol, and your implementation.
Settings registers 0x0B and 0x0C to values 0x33 and 0x31 seems to be related to hardware specific platform (XL7105?).
In case of FlySky module it seems that we are able to use WTR on line GPIO1. Both are configured just once.
But TX_SW and RX_SW must be controlled manually.

Also selecting of antenna (RF0, RF1) - but this is dependent from TX/RX SW.

How I should handle this?

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

More
06 Feb 2018 11:53 #67416 by goebish
No idea, in deviation we're using GPIO0 & GPIO1 to switch between PA and LNA (check a7105.c), if memory serves (that was 2 years ago...) they're used as interrupts in the i10 to tell the firmware a telemetry packet has been received.

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

More
06 Feb 2018 13:40 #67419 by qba667
@goebish thank you very much!
I believe same is done in I6 and I6X. Now, I have to check documentation how WTR is triggered and then handle it.
Antenna switching is trivial as well - few small extensions to your implementation and we should be able to run Deviation on I6X.

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

More
05 Mar 2018 10:43 - 05 Mar 2018 10:44 #67909 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Anyone who has been connecting the ibus and sensor line, with 10k resistor and 1n4148 to a Tx uart of Betaflight?
Will deviation display telemetry send from flight controller such as V battery, amps etc? will it work and what will we get in deviation?

github.com/betaflight/betaflight/wiki/Ibus-telemetry
Last edit: 05 Mar 2018 10:44 by Fernandez.

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

More
05 Mar 2018 10:47 - 05 Mar 2018 10:49 #67910 by goebish
From the github:

Due to the limited telemetry data types possible with ibus, we simply send everything which can be represented. Currently this is voltage and temperature and throttle value.

Voltage & temperature are supported by deviation, not throttle telemetry, but who cares ?
Unfortunately ibus doesn't support current sensors (yet ?).
Last edit: 05 Mar 2018 10:49 by goebish.

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

More
05 Mar 2018 12:52 - 05 Mar 2018 12:59 #67911 by qba667
@Fernandez
Even better - after changing 2 bytes in firmware of IA6B you can get channels data and sensor data on same serial.
So far patched variants of IA6B:
github.com/qba667/MAVLinkToIbus/tree/master/IA6B
@goebish
My Cleanflight build ( github.com/qba667/Cleanflight ) supports:
Temperature
RPM
External Voltage
Avg Cell Voltage
Battery current
Remaining batt.
Throttle
Heading
Climb rate
CoG
GPS status
ACC X
ACC Y
ACC Z
Roll
Pitch
Yaw
Vertical speed
Ground speed
GPS distance
Armed
Flight mode

DeviationTX must support AC frames to get:
Pressure
Latitude
Longitude
Altitude
GPS Altitude
Max Altitude

The Betaflight since PR 4978 supports IBUS sensors as well:
github.com/betaflight/betaflight/pull/4978
Last edit: 05 Mar 2018 12:59 by qba667.

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

More
05 Mar 2018 14:53 #67915 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Interesting, I have to say Flysky for me has an excellent link never an issue.

I have now one of these receivers, I expect it can be easily flashed, probably it has original Ia6b firmware on it...
Pads are accessible for STlink, but I have just waterproofed the whole thing.....
www.rcgroups.com/forums/showthread.php?3...er-for-FS-I6X-FS-i6S

It is small, smaller than standard XSR of Frsky, I would say if it works as expected, than it is a very nice small Rx.

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

More
07 Mar 2018 07:50 #67945 by qba667
@Fernandez changes in receivers are not required - it Flip10 supports 4 bytes telemetry there is nothing to be done.
If you have cleanflight compatible FC you can try send telemetry data using my custom build github.com/qba667/cleanflight/releases
You need to configure sensors send from FC using command:
set ibus_sensor = 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
where 0 must be replaced by sensor ID:
INTV (0) // Internal Voltage
TEM (1) // Temperature
MOT (2) // RPM
EXTV (3) // External Voltage
CELL (4) // Avg Cell voltage
BAT_CURR (5) // battery current A * 100
FUEL (6) // remaining battery percentage / mah drawn otherwise or fuel level no unit!
RPM (7) // throttle value / battery capacity
CMP_HEAD (8) //Heading 0..360 deg, 0=north
CLIMB_RATE (9) m/s *100
COG (10) //Course over ground(NOT heading, but direction of movement) in degrees * 100, 0.0..359.99 degrees. unknown max uint
GPS_STATUS (11)
ACC_X (12) // m/s *100
ACC_Y (13) //m/s *100
ACC_Z (14) //m/s *100
ROLL (15) //deg *100
PITCH (16) // deg *100
YAW (17) // deg *100
VERTICAL_SPEED (18) // m/s *100
GROUND_SPEED (19) // m/s *100 different unit than build-in sensor
GPS_DIST (20) // dist from home m
ARMED (21)
FLIGHT_MODE (22) // simple index listed below


PRES (65) // Pressure
ODO1 (124) // Odometer1
ODO2 (125) // Odometer2
SPE (126) // Speed km/h
TX_V (127) // TX Voltage


//4 byte sensors
GPS_LAT (128) // WGS84 in degrees * 1E7
GPS_LON (129) //WGS84 in degrees * 1E7
GPS_ALT (130) // GPS alt m*100
ALT (131) // Alt m*100
ALT_MAX (132) //MaxAlt m*100
S85 (133)
S86 (134)
S87 (135)
S88 (136)
S89 (137)
S8a (138)


ALT_FLYSKY (249) // Altitude in m
SNR (250) // SNR
NOISE (251) // Noise
RSSI (252) // RSSI
ERR (254) // Error rate
UNKNOWN (255)

Needs RX firmware mod update

GPS_FULL (253)
VOLT_FULL (240)
ACC_FULL (239) 
The configuration array is checked until first occurrence of 0.
Because of limitations of flash on F3 target - GPS telemetry (and GPS itself) is not included.

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

Time to create page: 0.100 seconds
Powered by Kunena Forum