|
|
Thread OP
|
Question
RXSR-FC firmware update problem
My RXSR-FC has been flying well on firmware v.1.x, but I now wish to update to firmware v.2.1.0. In Betaflight configurator I've set UART2 to SPort and used the serialpassthrough 2 57600 command at the CLI. The FrSky updater tool automatically selects the correct COM port when I connect my RXSR-FC to the USB, but when I select the new firmware that I've already downloaded, it doesn't find my receiver.
On the top of the RXSR-FC board (opposite side to the RXSR receiver box) there's a solder pad for SPort. Can I use this and the 5v and GND pads to connect an SPort socket so I can use my STK device to update the firmware? For me this will be much easier than trying to use the USB socket. |
|
Last edited by abenn; May 23, 2020 at 05:22 AM.
Reason: Command syntax corrected
|
|
|
|
Thread OP
|
I'm still struggling with this one. I've tried time and again to use the serialpassthrough command and the FrSky updater, but it still can't find the device.
Today I looked at my board more closely, and realised that the two pads that are labelled 'SBUS' and 'S.Port' on this schematic are in fact 'SBUS' and 'TX1' on my actual board, so it seems like my idea of connecting to S. Bus from the top of the board is not possible. I've pulled the board out of my quad now and, on inspecting the RXSR receiver side of it, I can't see any kind of S.Port connection. Is there one accessible if I remove the RXSR from its casing? So, any ideas how to easlily connect via S.Port to this receiver, or how to get the frsky_update_sport-rev20 utility to work through USB with the serialpassthrough CLI command? The update utility is working fine with the STK device through the S.Port connections on my other receivers, such as X8R, where I can easily access the S.Port. |
|
|
|
|
Thread OP
|
The box says RXSR-FC (OMNIBUS F4 V6), and the enclosed 'instructions' leaflet says it's for RXSR-FC (OMNIBUS F4 Fireworks V2/OMNIBUS F4 V6/OMNINXT F7). The diagrams in the leaflet for F4V6 and F7 both show S.Port and SBUS pads at the top right of the top side of the board, though in reversed order. My actual board clearly shows 'SBUS' and 'TX1' at those positions. The leaflet diagram for the F4V6 shows a 'S/A(TX1)' pad on the underside of the board next to 'CAM_C', but on my actual board that pad is just labelled 'S/A'
So, is it safe for me to assume that the pad on my board that's labelled 'TX1' is in fact the S.Port pad? That would match the F4V6 diagram in the leaflet. And, if it's not the S.Port pad, will I do any permanent damage by making that assumption and connecting it to my FrSky STK device? |
|
|
|
|
Thread OP
|
I don't find anything on the FrSky download page that explains the discrepancy -- only copies of the instruction leaflet that came with my board. They do show that there's S.Bus pads (~, +, -) on the RXSR module, but they seem to only be accessible if I remove the module from the FC board, which I was reluctant to do. Looks like I'm going to have to do that now because I've just connected my STK to the TX1 tab on top of the board (S.Port on the diagram in the instruction leaflet) along with the 5v and GND tabs, and the FrSky updater still can't find the device.
|
|
|
|
|
Thread OP
|
Thanks Allerhopp, I had read about the importance of getting the sequence right. What I've been doing is (1) plug in the STK device and hear the 'ding dong' sound that tells me it's recognised, (2) open up the FrSky updater app and see that it's showing a COM port, (3) in the updater app select the firmware file that I've already downloaded and it then says 'Finding device' (or something similar), (4) then plug in the S.Port connection cable from the receiver. With my other receivers it then quickly shows the file name and allows me to click on the button to start the update. With my RXSR-FC it doesn't go beyond the 'Finding device' stage, even if I wait several minutes.
You've got me thinking though: On the RXSR-FC board there's two 5v pads near the S.Port (Tx1) pad. One is labelled '5V_DC', but when I used that one the RXSR receiver didn't power up even though the FC board did. So I then used the other one labelled '5V_BEC' and the RXSR and the FC both lit up when I plugged into the STK. Does it matter that everything was powered? If so, is there a simple way to power just the RXSR? |
|
|
|
|
Thread OP
|
Yes, that's what I was beginning to think. Hopefully the ribbon cable just unplugs from the FC after I've opened the little box that houses the R-XSR?
|
|
|
|
|
|
Frsky offers it as spare part. So there is a way to unplug it. If you are unsure about the locking mechanism better write an e-mail to the tech-support.
|
|
|
|
|
Thread OP
|
Success
The hardest part was taking the enclosure apart, for one of the four retaining screws had been loctited! I soldered three ultra-fine (0.5mm outer diameter) multi-strand wires onto the ~+- pads on the RXSR and put a plug on them to connect to my STK. I didn't disconnect the ribbon cable from the FC because I was scared of breaking something, but the firmware download went exactly as it should. When re-assembling the device I fed the three new wires out beneath one side of the enclosure, so I've now got a permanent S.Bus socket mounted on this quad for future updates. A quick test hover proved that things are working as they should. I hope to get some proper flights this weekend. I'm glad I've got this one sorted, for it's about the only model I've got that I don't mind crashing while I gain confidence in the v2.1 firmware |
|
|
Thread Tools | |
Similar Threads | |||||
Category | Thread | Thread Starter | Forum | Replies | Last Post |
Help! | RXSR-FC (Omnibus F4 Nano v7) Betaflight Receiver Problem | sgtmeowmerrs | FrSky | 2 | Dec 02, 2019 08:52 AM |
Discussion | Graupner mz-12 firmware update problem | JB_Jacobo | Radios | 3 | Sep 01, 2016 05:10 PM |
Discussion | SP3 EVO firmware update problem | Milkco72 | Multirotor Drone Talk | 1 | May 11, 2016 07:51 PM |