flysky bug?

Start
Prev
1
Next
End

xxx
Topic Author
Offline

13 Sep 2015 07:41 #37707 by xxx

flysky bug? was created by xxx

I had to implement a (second) flysky rx today in order to test my A7105 module and code, and I noticed there were a couple of channels not receiving.

I found 2 of the channels in the hopping table are incorrect, at least for my transmitter. I use the turnigy i6 ( flysky FS-i6 rebranded).

The new hopping table looks like:

static const byte tx_channelsxx[16][16] = {
  {0x0a, 0x5a, 0x14, 0x64, 0x1e, 0x6e, 0x28, 0x78, 0x32, 0x82, 0x3c, 0x8c, 0x46, 0x96, 0x50, 0xa0},
  {0xa0, 0x50, 0x96, 0x46, 0x8c, 0x3c, 0x82, 0x32, 0x78, 0x28, 0x6e, 0x1e, 0x64, 0x14, 0x5a, 0x0a},
  {0x0a, 0x5a, 0x50, 0xa0, 0x14, 0x64, 0x46, 0x96, 0x1e, 0x6e, 0x3c, 0x8c, 0x28, 0x78, 0x32, 0x82},
  {0x82, 0x32, 0x78, 0x28, 0x8c, 0x3c, 0x6e, 0x1e, 0x96, 0x46, 0x64, 0x14, 0xa0, 0x50, 0x5a, 0x0a},
  {0x28, 0x78, 0x0a, 0x5a, 0x50, 0xa0, 0x14, 0x64, 0x1e, 0x6e, 0x3c, 0x8c, 0x32, 0x82, 0x46, 0x96},
  {0x96, 0x46, 0x82, 0x32, 0x8c, 0x3c, 0x6e, 0x1e, 0x64, 0x14, 0xa0, 0x50, 0x5a, 0x0a, 0x78, 0x28},
  {0x50, 0xa0, 0x28, 0x78, 0x0a, 0x5a, 0x1e, 0x6e, 0x3c, 0x8c, 0x32, 0x82, 0x46, 0x96, 0x14, 0x64},
  {0x64, 0x14, 0x96, 0x46, 0x82, 0x32, 0x8c, 0x3c, 0x6e, 0x1e, 0x5a, 0x0a, 0x78, 0x28, 0xa0, 0x50},
  {0x50, 0xa0, 0x46, 0x96, 0x3c, 0x8c, 0x28, 0x78, 0x0a, 0x5a, 0x32, 0x82, 0x1e, 0x6e, 0x14, 0x64},
  {0x64, 0x14, 0x6e, 0x1e, 0x82, 0x32, 0x5a, 0x0a, 0x78, 0x28, 0x8c, 0x3c, 0x96, 0x46, 0xa0, 0x50},
  {0x46, 0x96, 0x3c, 0x8c, 0x50, 0xa0, 0x28, 0x78, 0x0a, 0x5a, 0x1e, 0x6e, 0x32, 0x82, 0x14, 0x64},
  {0x64, 0x14, 0x82, 0x32, 0x6e, 0x1e, 0x5a, 0x0a, 0x78, 0x28, 0xa0, 0x50, 0x8c, 0x3c, 0x96, 0x46},
  {0x46, 0x96, 0x0a, 0x5a, 0x3c, 0x8c, 0x14, 0x64, 0x50, 0xa0, 0x28, 0x78, 0x1e, 0x6e, 0x32, 0x82},
  {0x82, 0x32, 0x6e, 0x1e, 0x78, 0x28, 0xa0, 0x50, 0x64, 0x14, 0x8c, 0x3c, 0x5a, 0x0a, 0x96, 0x46},
  {0x46, 0x96, 0x41, 0x5a, 0x50, 0x29, 0x3c, 0x8c, 0x28, 0x78, 0x1e, 0x6e, 0x32, 0x82, 0x14, 0x64},
  {0x64, 0x14, 0x82, 0x32, 0x6e, 0x1e, 0x78, 0x28, 0x8c, 0x3c, 0xa0, 0x50, 0x5a, 0x0a, 0x96, 0x46},
};

The changes are on the second to last row, index 2 and 5. With the new values the rx receives all packets, except for some random drops.

silverxxx

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

SeByDocKy
Offline

13 Sep 2015 07:49 #37708 by SeByDocKy

Replied by SeByDocKy on topic flysky bug?

Interesting ....

Are you working on the orignal FLySky protocol ? or the new one (2-way ...) ?

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

xxx
Topic Author
Offline

13 Sep 2015 10:34 - 13 Sep 2015 10:34 #37711 by xxx

Replied by xxx on topic flysky bug?

I haven't got the tools to do the new one sadly, this is the old one.

silverxxx

silverxxx

Last edit: 13 Sep 2015 10:34 by xxx.

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

skretchmer
Offline

13 Sep 2015 14:31 #37714 by skretchmer

Replied by skretchmer on topic flysky bug?

... Just wondering if this could be related to the jerky servo movement issue a few on here have seen with the v911 and A7105-D03?......

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

midelic
Offline

13 Sep 2015 17:05 - 13 Sep 2015 17:10 #37721 by midelic

Replied by midelic on topic flysky bug?

No,...very hard to believe this we;ll cause jerkiness.
The data on flysky is updated every ~1500us One or 2 frames missed it will not be noticed.I would say that this is not even relevant,
To see jerkiness, data should be skipped on more than 22000us(22ms).
For comparison
on Frsky data is updated every 9000us.
on DSM2 every 22000/11000us
and mostly on nrf chips every 4000/8000us.

I believe that jerky movementt with V911 most probably is caused by the RF power output settings. It may be set to maximum.Try reduce RF power and test again

Last edit: 13 Sep 2015 17:10 by midelic.

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

Start
Prev
1
Next
End

Time to create page: 0.033 seconds

Force desktop display