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

More
19 May 2016 16:03 - 19 May 2016 16:06 #48720 by hexfet
No, you're right it's broken. After pulling the latest master from deviationtx I also see the failure.
Last edit: 19 May 2016 16:06 by hexfet.

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

More
19 May 2016 17:18 #48727 by goebish
Thanks for testing, looks like it's broken since this commit:

merge scrollable code from at9 branch
github.com/DeviationTX/deviation/commit/...ab936765175e7355c497

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

More
19 May 2016 19:35 #48734 by goebish
dc59, I had a quick look at the captures you made some time ago, the IA6B doesn't report RSSI (in dB), only an error rate, I'll add it in a future update.
Regarding the issue with the 7e, I'll make another build that uses DSM telemetry type instead of FrSky, looks like there's no issue with this one. Be aware that there's an issue with the current nightly build tho, I added a comment on the faulty commit.

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

More
19 May 2016 21:50 #48740 by dc59
Thanks Goebish and Hexfet :lol:

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

More
20 May 2016 06:00 - 20 May 2016 06:25 #48839 by john
good job
Last edit: 20 May 2016 06:25 by john.

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

More
21 May 2016 04:39 #48926 by hexfet

goebish wrote: Thanks for testing, looks like it's broken since this commit:

merge scrollable code from at9 branch
github.com/DeviationTX/deviation/commit/...ab936765175e7355c497

Latest PR includes a fix for this. The old scrollable code tolerated empty rows. Screen looks better cleaned up :)

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

More
21 May 2016 08:20 - 21 May 2016 08:21 #48939 by goebish
Thanks :)
I thought about adding a telemetry type, but maybe that's not worth it if an existing one already has all the required fields ...
Last edit: 21 May 2016 08:21 by goebish.

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

More
21 May 2016 08:33 - 21 May 2016 08:40 #48940 by goebish
Does anyone here has an AFHDS2 RX (not 2A), I'd like to implement the protocol while I've an i10 but I can't find an iR4 RX for a reasonable price, they're sold out everywhere I've looked at, or selling for ~ 35€ in Germany :(
Last edit: 21 May 2016 08:40 by goebish.

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

More
21 May 2016 12:04 #48945 by Alexandro
Replied by Alexandro on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Hello,
Can you make a 8s Testbuild ?
Then i can help to Debug it
Greetings Alex

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

More
21 May 2016 12:08 - 21 May 2016 12:23 #48946 by goebish
Here it is, it's the same than the previous version for 7e/10, I'll wait for hexfet PR to be merged into master before releasing a new one (with failsafe and more telemetry):
www.dropbox.com/s/ry607lmv3m9czwk/deviat...0.0-179cd46.zip?dl=0
Last edit: 21 May 2016 12:23 by goebish.

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

More
23 May 2016 12:24 #49070 by Evil Pusher
Replied by Evil Pusher on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
@ Goebish, why not using this one: ( www.hobbyking.com/hobbyking/store/__3337...2_EU_warehouse_.html ) - it´s in stock.
It´s also uses AFHDS protocol. Shipping times depend on the shipping you choose. (NL -> DE).

I used some with the TGY-i10, and TGY-i6 TX - it was working well.
Sorry, I would send you some, but I sold them all at ebay.

D.I.Y. or die

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

More
24 May 2016 07:46 - 24 May 2016 07:54 #49110 by goebish
This RX is using the AFHDS protocol, this protocol has already been reversed so I don't need it, I already have something similar ;)

I accept your PM offer to send me your iR4 (AFHDS2), but only if it binds with the TGY i10, if it only binds with the Carson iT4 it will be useless to me, at least for now.
Last edit: 24 May 2016 07:54 by goebish.

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

More
25 May 2016 13:26 #49198 by goebish
Here's a new test build for 7e, no changes except that it shouldn't crash anymore when entering telemetry monitor page ;)
www.dropbox.com/s/9vxgh9z28oesgqt/deviat...0.0-b020095.zip?dl=0

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

More
26 May 2016 00:25 #49235 by dc59
Hi Goebish,

Thanks for update 7E fixed FW, but I can't do any test until next week , my 7E is just heading to a " brain operation "(256k) :lol:
It will come back to me next week, if I can successfully installed boot loader and don't kill my 7E , I will test this build immediately. :cheer:

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

More
26 May 2016 07:24 #49266 by goebish
No problem, I'll try to add failsafe and missing telemetry sensors during the week-end.

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

More
26 May 2016 07:57 - 26 May 2016 08:23 #49268 by goebish
As you may know, there are multiple brands manufacturing those TXs / RXs (Turnigy, FlySky, Carson) and it seems they're not compatible between each others.

Evil Pusher sent me some captures of his Carson iT4 (thanks mate !) and I may have found the differences between it and the Turnigy.

Turnigy enables FEC encoding , A710x Code Register 1 (address 0x1f) bit 4 is set (=0x1f), while it is not on the Carson (=0x0f), no wonder why a Turnigy i10 can't bind to a Carson / FlySky RX ! This should be fixed with a simple protocol option :)

Also stick data packets start with 0x55 on Carson instead of 0x58 on TGY, but maybe that's only because the captures I have are for AFHDS2 (not 2A) protocol.
... or maybe that's something else, I've my idea but I'd need someone that has NOT updated the firmware of his TX/RX to send me some captures.

Does anyone here have an AFHDS2A RX that doesn't work with a TGY TX so we can make some tests ?
Last edit: 26 May 2016 08:23 by goebish.

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

More
26 May 2016 15:05 - 26 May 2016 15:07 #49290 by Alexandro
Replied by Alexandro on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Hello,
Test Ver.b02 on Devo 7e

PWM 1-6 on the 6 Channel RX ok
PWM 1-10 on the 10 Channel RX ok

Volt1 on 6 and 10 Channel ok
RSSI on 6 Channel shows only 0d
RSSI on 10 Channel Shows -60db , looks ok to me

on the A2 RX:
-> all versions of the Carson,Flysky,Turnigy does Bind with each other of the 10i Transmitter
if you downgrade the TX to a previous Firmware all works, but the Channel order is sometimes Mixed ( tested with the Carson Version, maybe the new Firmware is a Original Flysky with a Patch to accept the Carson TX -> Carson send it tom as Beta Version ).
You can always upgrade all 3 Versions of the RX with all 3 Version of the TX, but the highest Number of the Firmware on the RX counts.
Maybe there is some difference for Int. Versions to Eu Versions.
-> the 10 Channel RX has no Servo Bus, the 6 Channel has a Servo Bus
-> if you Bind a new RX it prompts automatic the Message to Update your RX,if the Version Number of the RX is lower. The RX Firmware is integrated into the TX Firmware.

greetings Alex
Last edit: 26 May 2016 15:07 by Alexandro.

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

More
26 May 2016 15:16 #49292 by goebish
Thank you for those clarifications.

When using the iA6B with the i10, does it show RSSI in dB, or only error rate ?

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

More
26 May 2016 16:50 - 26 May 2016 16:52 #49294 by Alexandro
Replied by Alexandro on topic Flysky AFHDS 2A, protocol as used i10, i6, iT4,
Hello,
i tested it with my Carson i10

you can chose booth at the Telemetry Display on the i10
RSSI is -60db
Signal Strength 10

RX Firmware was 1.3 (Flysky Factory Version) and updated it to 1.6.

on Devo 7e:
--> Fs-ia6b on version 1.6 ( updated with my Carson i10) shows now the RSSI -60 db !
--> on v 1.3 it does not show the RSSI, it is always 0

Bug Version from Factory ? :(



greetings Alex
Last edit: 26 May 2016 16:52 by Alexandro.

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

More
26 May 2016 16:52 - 26 May 2016 16:53 #49295 by goebish
Probably not a bug, just that it was not present in FW 1.3 ...
There's nothing I can do about it, we won't update the RX firmware from Deviation ;)

Hopefully, as time goes, they should be shipped with newer firmwares ...
Last edit: 26 May 2016 16:53 by goebish.

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

Time to create page: 0.115 seconds
Powered by Kunena Forum