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
08 Aug 2016 13:22 #52583 by anthony7288
Replied by anthony7288 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

goebish wrote:

anthony7288 wrote: ok , i will try , Uhm maybe STM32F030R8T6 LQFP64


That's a LQFP48, not 64.

joloebig wrote: sound good to me, maybe it other 1.0.8 than my, i read somewhere that tgy was not consist in their versions.


Downloaded from hobbyking.


thank , i confuse .
i wonder : why pin Boot0 connect Gnd still can load program with stlink ? i remember devo 7e have to set Boot0 to 1 to load program ?

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

More
09 Aug 2016 14:59 - 09 Aug 2016 15:00 #52616 by anthony7288
Replied by anthony7288 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
it fail :P


22:01:49 : Device family :STM32F051x4/F051x6/F051x8/F030x8
22:01:49 : Failed to read memory @08000050!
22:02:04 : Flash memory erased.
22:02:13 : [iA6B_1.6.bin] opened successfully.
22:02:13 : [iA6B_1.6.bin] checksum : 0x00431566
22:02:40 : Memory programmed in 9s and 703ms.
22:02:40 : Verification...OK
22:02:40 : Programmed memory Checksum: 0x00431566
22:02:40 : Failed to read memory @0800004C!
22:02:53 : Disconnected from device.
Last edit: 09 Aug 2016 15:00 by anthony7288.

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

More
09 Aug 2016 16:05 #52619 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I don't know, maybe there's a short somewhere else on the board, I'd check the regulators ... but if you replace half of the parts on the board just to find the RF part is also toast in the end, that's really not worth it.

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

More
09 Aug 2016 16:16 #52620 by anthony7288
Replied by anthony7288 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
i guess stm32f030c8t6 not enough memory for code . . i can load program but it has a problem with memory .

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

More
09 Aug 2016 16:19 #52621 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
No, it should be fine, it has 64kB of flash while 32kB are enough.

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

More
09 Aug 2016 19:47 #52633 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Thanks Goebish!

The U7E + Extra Switches Pull request, it runs ! Switches still work and the AFHDS 2a it binds. (no flights yet but all seems fine)

Now I need to flash my Ia6b to get the RSSI, if I update using your instruction, do I get also the SBus? Is 1.6 still the latest version?
www.rcgroups.com/forums/showthread.php?t=2677694


btw, for people who want to read the pack voltage, easy mod here:
www.rcgroups.com/forums/showpost.php?p=33432940&postcount=23

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

More
09 Aug 2016 19:48 #52634 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Yes, it's the latest version and has SBUS support :)

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

More
09 Aug 2016 20:51 #52636 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I flashed using your procedure with 1.6firmware.

One comment to your instruction you can easily edit the ID in the STM-32 ST link utility itself, no need to go to hex editor.
So open the file, scroll to field 0x1C00, than change the 8 digits here into any hex nr except FFFFFFFF
Then must press save first.
Then this file can be flashed.

I have no idea about what the RSSI value means and where to set the threshold for alarm to warn for dropouts or problematic control. When at the table close to my Rx I get value -60d in my Ultimate devo 7e telemetry monitor.

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

More
10 Aug 2016 12:24 - 10 Aug 2016 12:26 #52650 by anthony7288
Replied by anthony7288 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
So result is chip stm32f030c8t6 48pin can not replace for stm031c6t6 orginal
You can see led blink very strange :lol:


Last edit: 10 Aug 2016 12:26 by anthony7288.

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

More
12 Aug 2016 08:27 #52694 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
At least it seems the MCU is executing some code, I suppose the led flashing 5 times is an error code, maybe because the A7105 is toast as well and doesn't reply to the RF calibration sequence ?

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

More
12 Aug 2016 09:15 #52696 by anthony7288
Replied by anthony7288 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
a7105 not died . I'm sure . because i try it with project Multiprotocol , bind with rx v911 , it work .
i looking for datasheet between Stmf030c8t6 and stm32f031c6t6 . Not diffirence much for two this chip.

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

More
12 Aug 2016 09:33 #52697 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I'm talking of the A7105 (well, A7106 actually) that's inside the iA6B, under the RF shield, not the A7105 in your Devo ;)

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

More
14 Aug 2016 12:44 - 14 Aug 2016 13:12 #52741 by anthony7288
Replied by anthony7288 on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
i think i find a problem . IC I2C on rx maybe died .Chip Stm32 can not reply :lol:
Attachments:
Last edit: 14 Aug 2016 13:12 by anthony7288.

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

More
18 Aug 2016 12:42 #52869 by djdazzy
Replied by djdazzy on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Can someone please confirm if the AFHDS 2A protocol is in the nightly build now for the 7e?

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

More
18 Aug 2016 12:48 #52870 by goebish
Replied by goebish on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
No, it's not in the nightly, just download the test build above.

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

More
19 Aug 2016 13:04 #52899 by djdazzy
Replied by djdazzy on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Thanks Goebish

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

More
21 Aug 2016 09:34 #52965 by Arise
Replied by Arise on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,

goebish wrote: Yes, it's the latest version and has SBUS support :)


What is SBUS used for in Flysky/Turnigy Remote? Or is sBUS only for the receivers so they can be paired with sBUS remotes?

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

More
21 Aug 2016 09:53 #52969 by Fernandez
Replied by Fernandez on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
The nice thing is that these cheap RX, can output ppm channels, cppm sum, ibus and sbus.
The tx is used to setup the mode of the Rx.
Fantastic isn't it ? much better than keeping buttons on RX pushed forfew seconds etc etc.......

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

More
27 Aug 2016 20:44 #53157 by joloebig
Replied by joloebig on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
anyone tested the telemety with a 3in1 modul?
reg
jo

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

More
10 Sep 2016 18:01 #53756 by ketsa
Replied by ketsa on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
I'm building a new quad with an FS-IA6B, I have it bound to my Devo7E with AFHDS2A build and A7105, no problem.

But I cannot get any signal in cleanflight receiver page. I tried with PPM and with PWM connected to a SP Racing F3.... no results.
What am I missing ? is my IA6B DOA ?

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

  1. Forum
  3. Development
  5. Protocol Development
  7. Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Time to create page: 0.104 seconds
Powered by Kunena Forum
Force desktop display