Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (02-Sep-2020, 10:31 AM)SnowLeopardFPV Wrote: The firmware you've used should work (assuming that you also flashed the latest 190117 version of the ACCST firmware to your R9M module).
You definitely ticked the "flexr9m" option in OpenTX before you flashed it to your transmitter didn't you? Yes, I did tick the flexr9m option. I can try to re-do everything and make sure I get the correct firmware, but I'm pretty sure I already have the correct one. I mean Slim+ is bound successfully to the radio. It seems to me that the problem is with reading the info from the S. PORT. Also, beside your instructions I followed instructions in when setting this up. I can try with ACCESS firmware too but I'm having trouble bounding the reciever and the radio. ![[-]](https://intofpv.com/images/collapse.png) • Posts: 21,315 Threads: 589 Likes Received: 8,997 in 6,660 posts Likes Given: 1,426 Joined: Jun 2018 Reputation: 790 What you've got wired and configured should work. I guess you don't have a spare receiver you can try on that FC, or a spare FC you can try that receiver on? • Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (03-Sep-2020, 06:21 PM)SnowLeopardFPV Wrote: What you've got wired and configured should work. I guess you don't have a spare receiver you can try on that FC, or a spare FC you can try that receiver on? I don't have an extra Slim+ or FC sadly. I re-did everything, made sure my radio firmware (and bootloader) is updated, R9M flashed to 190117 version of ACCST firmware, flashed the R9 Slim+ to ACCST FLEX F-port firmware, bound it again (got a green light on the receiver and radio says it is connected as well), then I open Betaflight, open the receiver tab, click refresh, and move my sticks around and there is no response. Also, the components for this setup are brand new (R9M, R9 Slim + and the radio X9D+ 2019 SE). My quad worked well on my previous setup which was through FSIA6B receiver (I-BUS). It's really frustrating to not have it work like this. Other people might experience same problems when trying to go for long range with FrSky's module. Does anyone else have any ideas? • Posts: 21,315 Threads: 589 Likes Received: 8,997 in 6,660 posts Likes Given: 1,426 Joined: Jun 2018 Reputation: 790 With no spare FC to try, the only other options I can think of is to either try UART1 instead, or revert to trying an SBUS connection on a UART RX pad (you would need to flash SBUS/S.Port formware to the R9 Slim+ for that). • Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (06-Sep-2020, 01:06 PM)SnowLeopardFPV Wrote: With no spare FC to try, the only other options I can think of is to either try UART1 instead, or revert to trying an SBUS connection on a UART RX pad (you would need to flash SBUS/S.Port formware to the R9 Slim+ for that). I decided to try that by also redoing the whole process. However, this time, when flashing the FC firmware I encountered an error: STM32 - timed out, programming: FAILED ![[Image: YrTeUJt.png]](https://imgur.com/YrTeUJt.png) • Posts: 11 Threads: 1 Likes Received: 0 in 0 posts Likes Given: 2 Joined: Apr 2020 Reputation: 0 (06-Sep-2020, 03:16 PM)flyer555 Wrote: I decided to try that by also redoing the whole process.
However, this time, when flashing the FC firmware I encountered an error: STM32 - timed out, programming: FAILED
It worked on the fifth try. Onto installing firmware for R9M and R9 Slim plus now. I'll post here once I'm done. • Posts: 21,315 Threads: 589 Likes Received: 8,997 in 6,660 posts Likes Given: 1,426 Joined: Jun 2018 Reputation: 790 (06-Sep-2020, 03:16 PM)flyer555 Wrote: However, this time, when flashing the FC firmware I encountered an error: STM32 - timed out, programming: FAILED That's strange. I've not encountered that issue before. Out of interest, was this on a Windows machine or a Mac? • |
