search

NotFastEnuf / NFE_QUICKSILVER

Quadcopter firmware for stm32f4
MIT License
12 stars 1 forks source link

IBUS - Unexpected behavior reported with matekf411 target #1

Open NotFastEnuf opened 3 years ago

NotFastEnuf commented 3 years ago

One report has rolled in so far regarding an IBUS receiver which was not detected by the universal serial protocol. Once hard set to IBUS in config.h and re-compiled - the receiver seemed to operate normally with one exception. The packet rate based rssi calculation was reported to show 29 when it probably should have been at 100%.

Problem reported on the following gear: Model: Fli14 Item Name: 2.4G 14CH Compatible Flysky AFHDS-2A Receiver Channel: 14CH Protocol: AFHDS-2A

sakitume commented 3 years ago

I have a Play F4 board with an IBUS (AFHDS2) receiver working with my SilverLite FC. I think it is hooked up to USART1.

I hope to try NFE_Quicksilver on this little micro and may be able to help test out the IBUS implementation. Just need to dig into Quicksilver to see what it takes to configure it to use USART1, probably the configurator I've heard about?

If I get around to testing this out I'll report back on what I find

sakitume commented 3 years ago

I was able to flash Quicksilver onto the Play F4 and configure it to use USART1. The FlySky RX (IBUS protocol) was auto-detected. There was one time that it didn't seem to be auto-detected but it might have been user error on my part as I wasn't able to repro it.

I've yet to actually fly this quad (only did a LOS test of a few seconds) so cannot confirm IBUS is working without issue, but all of the channels seemed to be working and auto-detect seems fine. I'll report back if I'm able to test more and encounter any issues.

bkleiner commented 2 years ago

@sakitume did you ever get around to doing some more testing? were you able to reproduce any issues?