×

Notice

The forum is in read only mode.
  1. Forum
  3. Development
  5. Protocol Development
  7. Flysky AFHDS 2A, protocol as used i10, i6, iT4,

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

More
15 Mar 2017 18:59 #60223 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Sorry but I've no idea, the safest way would be to update with an actual i6/i10 transmitter ... then you could extract and share it ;)
More
15 Mar 2017 19:41 #60224 by povlhp
Replied by povlhp on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Not sure if there is a transmittable upgrade.
But I will give it a try read out old. Use your iA6B 1.6 and see if it works.
One reseller says they have fixed x6b. Brand new from BG has issues.
More
15 Mar 2017 21:59 #60227 by povlhp
Replied by povlhp on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Could not read firmware from x6b.
But I read from iA6C.
Tested the X6B with both iA6B and iA6C firmware. IA6C has auto-bind.
Both binds. It runs. But external voltage sensor maps to internal voltage sensor, and the 4.95V was read as 4.1V. External voltage sensor was constant at 8.6V.
Rssi/error/snr were all fine.
Tested PPM with simulator. Worked. With working failsafe.
So not an optimal solution as telemetry is no good. But at least I get a failsafe.
IBus not tested yet.
More
16 Mar 2017 12:59 #60247 by Peaceliker
Replied by Peaceliker on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Maybe important. I have devo 7e,. With Fs ia6 receiver its works great...
More
19 Mar 2017 12:26 #60361 by anthony7288
Replied by anthony7288 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

povlhp wrote: Could not read firmware from x6b.
But I read from iA6C.
Tested the X6B with both iA6B and iA6C firmware. IA6C has auto-bind.
Both binds. It runs. But external voltage sensor maps to internal voltage sensor, and the 4.95V was read as 4.1V. External voltage sensor was constant at 8.6V.
Rssi/error/snr were all fine.
Tested PPM with simulator. Worked. With working failsafe.
So not an optimal solution as telemetry is no good. But at least I get a failsafe.
IBus not tested yet.


can you post firmware IA6C here ?
More
19 Mar 2017 20:37 - 19 Mar 2017 20:38 #60381 by povlhp
Replied by povlhp on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
i will create a github repository with iA6B, iA6C and X6B firmware. and instructions.
Had some good X6B, so now all mine works. For all firmwares 0x1C00 seems to hold the ID.
The X6B seemed to have pins in a different order, but they are easy to locate.

For now the iA6C firmware is in .hex, will have to save as .bin
Last edit: 19 Mar 2017 20:38 by povlhp.
More
20 Mar 2017 08:44 #60402 by povlhp
Replied by povlhp on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I created a GitHub repository with the firmwares and instructions. Need a few more images. But if you just want to grab a firmware, they are here:

github.com/povlhp/FlySkyRxFirmware
More
30 Mar 2017 01:50 #60929 by ALi
Replied by ALi on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Can I use the Flysky X6B with deviation, namely the 4 in 1 MultiModule.? I just ordered the x6b and multimodule from banggood before checking even if it would work. I see you got it working somewhat with a firmware update. Is it important to update the firmware on the x6b?
More
13 Apr 2017 11:21 #61423 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Just to confirm, the Flysky X6B, pcb receiver works well.
I confirm Failsave works with Ibus, but it has to be set in tx per channel.

RSSI is 60d at the desk, what would be good threshold for range warning, to be still in control, but warn you from flying further?
Than I still have small issue sbus range compared to ibus, the values do not match. (checked Betaflight) ibus seems to be correct as spot on 1000-1500-2000
More
13 Apr 2017 11:29 - 13 Apr 2017 15:17 #61424 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
One way to check for low RSSI warning is to set TX power to minimum value, get away from the Rx, then check at which value the communication is lost, needs 2 persons, one has to stay near the Rx to check when com is lost (blinking led, or connect a servo to check when it starts to stutter or stops moving).

What are the values in betaflight with defaults mixer settings in sbus mode ?
I think this is normal as originally sbus center is 1520 (futaba), but I can add an offset when sbus mode is enabled if this is annoying ...
Last edit: 13 Apr 2017 15:17 by goebish.
More
13 Apr 2017 12:09 #61426 by plaisthos
Replied by plaisthos on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I have a Flysky FS-A8S receiver that does not with the multi module, no idea if it works with deviation. Anyway if one you developers wants it to try, I can send it to you. (I don't want anything in return and also don't want it back)
More
13 Apr 2017 12:12 #61427 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
According to this post, FS-A8S is working fine with Deviation:
www.deviationtx.com/forum/protocol-devel...-it4?start=400#57538

Maybe yours is defective ?
More
13 Apr 2017 13:12 - 13 Apr 2017 14:04 #61428 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
ibus 1000-1500-2000, seems ok all default.
then change to sbus tx and in betaflight:
sbus 1030-1515-2000

Maybe someone with original flysky transmitter and a betafliight drone can check if it show same difference in range between ibus and sbus.

(edited)
Last edit: 13 Apr 2017 14:04 by Fernandez.
More
13 Apr 2017 13:44 #61429 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Are you sure ?
It should be low=1000, center=1500, high=2000, well, that's what deviation (and the FS i10) sends with default mixer settings.
More
13 Apr 2017 14:07 #61431 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Think you are right I made mistake cant verify now.
But I am certain from what I saw, low value is 30 higher than ibus, mid value 15 higher than , the high value ibus sbus is same value.
More
13 Apr 2017 14:14 - 13 Apr 2017 14:21 #61433 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Ok, I think this is expected with sbus, instead of making a dirty patch in deviation, that would be better to set mid_rc to 1515 in betaflight + use subtrims (or edit scaling) on the transmitter:
github.com/cleanflight/cleanflight/blob/master/docs/Cli.md (check mid_rc)
... but as betaflight supports ibus, better use it ;)
Last edit: 13 Apr 2017 14:21 by goebish.
More
13 Apr 2017 14:26 #61435 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
... Still, I'll check later what's the behavior with an actual flysky transmitter.
More
13 Apr 2017 19:03 #61439 by AirPatoine
Replied by AirPatoine on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I''ve been watching this post with interest. I want to make sure I understand where you guys are at in making this work. I have a flysky iA6B receiver with a voltage monitor - CVT01. To get voltage info on my Devo 10 do I just need to update the firmware on the receiver? Haven't seen anyone refer to the voltage monitor. Is it working with Deviation?

What Devo firmware do I need. Now I'm running 5.5.0 - v 4447ec3

Thanks for all your work on this.
Attachments:
More
13 Apr 2017 19:04 #61440 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
External voltage sensor is still not implemented, it's on my todo list ...
More
13 Apr 2017 21:09 #61442 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I get RSSI and Rx Voltage, so the the external Vbat ADC port not yet implemented? As I do not seem to get the data.

Or are you speaking about external ibus, sensors add on.
  1. Forum
  3. Development
  5. Protocol Development
  7. Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Time to create page: 0.062 seconds
Powered by Kunena Forum
Re-enable mobile display