Man you make soldering look not so scary, like there is a good chance you could get it done without having to burn down a home, you know my greatest fear. thanks!
Thanks for confirming this was a JST-PH 2.0 connector. I'll be purchasing a 5-pin male/female pair so I can have a removable RX like the R-XSR. Have your thumbs up!
Just got my r9m in (with the same flight controller no less) and going to be connecting it up with a gps for rescue mode and gps speed looks like a fun build. Thanks for the walkthrough I love how many uarts this board has
I‘m new to the FrSky system ..i got a x-lite pro ..the R9m module and the R9MM receiver.. and i dont know why the binding does not work 😅 ... it was no problem with the r-xsr receiver on another drone. ^^
Haha yea this stuff can be a bit confusing and it almost always comes down to a fw incompatability contact me on discord so I can better assist you discord.gg/b2nUTux TH-cam chat is very difficult to troubleshoot.
There is no rssi pad. The rssi comes into betaflight as aux 12 if you flash the newer firmware. Either way rssi is always a telemetry sensor between the rx and your TX.
Havent you just switched the sport cable with the sbus cable? The girst cable you soldered you say was the sbus cable but it wss the sport cable isnt it?
@@TweetFPV i noticed yesterday that if i want to connect sbus and sport telemetry on my kissfc v2 i must solder the s-port/f-port pad to the kiss fc and not the inverted s-port.
thank you very much, this is useful for me, i'll try this and i will ask you if i have issue. i hope you don't mind. have a nice day and best wishes for you 🙏❤️
So if there is a S.Port (and the FPort) and an Inverted S.Port is the inverted S.Port also an inverted FPort? Trying to get around having to use a UART with an inverter
You can if you flash fport fw to the reciever. But there are issues with f4 flight controllers not taking a uninverted signal. The r9mm also has an inverted sport/fport pad which will work with a f4 fc that doesn't have a built in signal inverter.
You soldered it backwards or you just said it backwards in the beginning but sport is your blue wire according to you labeling it when you put em on. And when you weed it into the fc you out the green as s-port ;)
Possibly, but depending on which receiver you are using like the r9mm it has a inverted pad that can go to a uart tx pad that doesn't have a built in inverter (most f4 fcs) otherwise you are only going to be able to use sbus. Fortunately you will still get rssi with newer fw without using smart port telemetry.
@@TweetFPV yes R9MM ill probably end up skipping telemetry.. But twice now I have telemetry receiver and can't get telemetry to work lol.. i thought u can get an uninverted signal from r9mm.. Oscar Liang article said it.. idk.. ill try it while everything is apart. When stuff shows up. Maybe I'll put in a temporary frame to test
Yes you can get and uninverted signal from the r9mm. That can be used a ls f. Port for both rc and telemetry on a f4 fc. That wire needs to go to a uart tx pad.
Hey Tweet. Where on TH-cam is a good review of THE QUALITY OF THE RADIO LINK of the r9 system. Your videos, like every other video out there talks about how to hook it up. But is this a good, solid, failsafe free system? I don’t want to buy Crossfire because I hate TBS, but I’m not going to switch over to r9 until I know what kind of performance to expect. I ask you because it seems like you know the answer. Enlighten me!!!
I have a video where I test the distance of the two systems but not with it installed Ina Quad. I have had great results with both the crossfire and the r9 systems. Neither system is a silver bullet though. It isn't as forgiving to poor rf environments and poor installations of recievers antennas. There is a bit of work with both systems to get them to be reliable. Now with the region specific antennas released from frsky I think a lot of the poor rf conditions will be fixed.
TweetFPV - thanks for the quick reply. Interesting answer too. I guess maybe it’s not time yet for everyone to ditch 2.4 yet... huh? I would just hate to “upgrade” to 900 MHz , and then lose my quad because of a failsafe.
I originally started using a 900 system at distances that I would normally fly 2.4g just to never have to worry about failsafes and for that these systems are great. Now when you are trying to do long distance flight there is a lot of testing and tuning with any system. When I fly at normal distances and normal environments my rf signal is no longer a thing I even think about. My limiting factor is my 5.8g video signal.
TweetFPV - Oh ok. Well that sounds pretty good. Is the immortal T type antenna the best option in your opinion? That seems to be what most people like. Thanks for your help... subbed 🤓👍🏽
T style antenna on the Quad an a super 8, or tbs diamond antenna on the transmitter is the ideal setup. The stock antenna that comes with the r9m module isn't veery good and accounts for the majority of failsafes I've seen.
Could I use the "inverted" S.Bus signal with f.port to a UART without a serial inverter? Reason I ask is I've got an omnibus F4 that's never worked with frsky's inverted signal, so I had to do the uninversion hack to my XSR. If I could use the r9 mm it would make my day.
@@TweetFPV I have Omnibus F4 v5.1 with only 3 Uarts (one i use for esc telemetry, another for vtx, and only one free uart i use for R9m f.Port. so the only way to get f.Port working for me was to solder the f.Port Signal fbus (not sbus) to the sbus pad on my Omnibus FC. And so i dont Need to use sbus soldering. Furhermore i needed some CLI entries for Inversion and Duplex and half Duplex (every single CLI command was nessecary. for more Questions ask me!
@@mh7711 Max... I think you save me. Days trying to setup R9MM Fport on my Omnibus F4 V5. TX6/TX3/TX1. And now, connecting the fport wire to the SBUS pad... IS WORKINGGGGGGGGGGGGGGGGGG (on INAV)!!!! So, at the configuration tab, fport is selected. And I think that... as the UART6 is for the SBUS... and TX6 is UART6 too..... then... I'm HAPPY. Thank you very much. you have enlightened me :)
I have followed your tutorial and all mine does is binds with telematry info etc but no stick input. I have the mamba F405 MK2 F4 FC and R9M Lite module also the Frsky X Lite-S. All flashed with latest ACCESS firmware and Frsky firmware for the F.port, also tried to run without SBUS, still have telematry but no stick input.
If you can find the diagram for the helio fc just connect the r9 reciever the same way they show connecting the r-xsr reciever blog.seidel-philipp.de/wp-content/uploads/2018/03/HELIO_SPRING_Flight_Controller_Anschlussplan_Wiringplan.jpg I don't have first hand experience with the helio board but based on that diagram I think it will be a easy setup.
ok, the board has a sbus and a s port. it shows the r-xsr hooking up that way. my question is the inverted s port goes there or s port/fport goes there or does it go on a tx pad? here is the diagram fpv-flightclub.com/products/helio-spring-imu-f-v2/ thanks
thank you very much, confusing ha? because the second one down on r9m is s port/fport. in the setup menu in betaflight under ports do i need to setup the s port or just the serial rx
Hello sir thanks for great work. I have followed your video and for some reason I have no stick inputs in the betaflight receiver tab. My f4 has a inverted s bus . Any thoughts?? Really stumped on this one
@@TweetFPV hello sir thank you for your reply. I have found my issue which was a broken sbus wire. Literally the wire was split,while all the silicone cover was completely intact. The Only reason I caught it was because I was checking my solder connections and the wire stayed at 90 degrees. Again thank you for your reply. Your work is invaluable to the community and especially for us noobs cheers.
Hi all, Great video ! I'm trying to connect the R9MM to a MAMBA F405. Could I connect the SBUS and the S.port to the same number of RX and TX? (ex. RX1 and TX1) Inverted S.port? Could I use the F.port? Kind regards
Sbus and s.port can not go to the same uart. on this board sbus must go to uart rx1. That uart is the only one with a built in inverter. Here are your options with the mamba and the R9MM. 1) Sbus to RX1, "inverted S.port" to any unused uart TX pad with a Sbus firmware flashed to the R9MM 2) "Inverted S.port" pad to any unused uart TX pad with a F.port firmware flashed to the R9MM F.port signal will be sent out from the R9MM
@@TweetFPV Thanks for your quick reply. I need to connect the smart.audio from the VTX (TX) and the GPS (RX and TX), so I think I have only the option of F.port. In the second option you say (("Inverted S.port" pad to any unused uart TX)), why not use directly the S.port/F.port pad on the R9MM?
The regular sport/fport pad on the r9mm is not a inverted signal and the r4 processor does not have the ability to invert those signals internally like on a f3 or F7 chip. You need some external hardware inverter either on the fc or the rx. The mamba does not have any such inverter except on the rx1 pad for sbus. The protocol for fport requires it to be connected to a TX on a uart. The "inverted" pad on the r9mm does this signal inversion and allows the f4 processor to understand the signal.
You my friend are a god!!! it took me 5 Seconds to do what you said!! RSSI works perfect on the Merica!! Also once I turned off the analog OSD it let me switch to channel 16 in the CLI for RSSI the woman who sold it to me and built it couldn't tell me how to do any of it goggle face out of North Dakota Lexi d anyway I have a custom gep sparrow that I bought from her as well it has a hglrc F3 Evo I can't configure OSD on BF I'll have to get on a computer but do you know what OSD that is is it minim that's what betaflight tells me from the description that she told me the FCC doesn't have OSD but it's built into the VTX so maybe I can't get RSSI on my OSD Channel 12 is active for RSSI on betaflight and on the CLI Channel 16 is assigned for RSSI? Thank you again sir
Do you get all the sensors in the sensors tab in your radio. You will always get rssi and rx voltage. If you aren't getting all the sensors from bf then the luas won't work because you don't have telemetry working properly.
Thanks for the video! Why is it when I bind the r9mm channel with range 1-8 for better latency, I'm still getting rssi on channel 16? Is it not possible to bind in 1-8???
TweetFPV Thanks for the reply. The reason I’m asking is because this thing drops out of the air as though I disarmed it. This isn’t my first build but it’s my first go around with R9 setup. I’m trying to eliminate all other possibilities like power loss, poor ground, or maybe even a faulty R9mm or R9m. From what I gather, I may have a packet loss issue in Betaflight when binding in 1-16 channel range ( github.com/betaflight/betaflight/wiki/SBus-FPort-and-RC-Smoothing ). So I rebound in 1-8 range (which is all I need anyhow) and still see Rssi over channel 16 in Betaflight. Therefore my head is about to explode. The more I try to figure out what’s going on the further down a rabbit hole I go! So, since I bound in 1-8, that’s all I should be able to use, i.e. AETR plus Aux 1-4 and the R9mm just sends rssi down channel 16 anyway? Am I thinking this correctly? And my latency should be at 9ms thereby eliminating or rather minimizing any packet loss. I’m trying to make this thing work since I paid for it but geeze, I’m about to rip it out and put a trusty ole r-xsr in it! God, I hope that all made sense! Thanks. Oh, and it has the latest faa firmware. One was released just yesterday actually.
I see, there are a LOT, i mean a LOT of antenna issues with the r9 system. This LR stuff is great but it is very sensitive to poorly made and mounted antennas. As far as fw goes I have not tested the recent fw but I have had excellent results with the 2018-08-21 firmware. Be sure you update both the TX and rx. If you are using the stock antenna that came with the r9m I suggest looking at the super 8. How do you have your antennas orientated on the Quad and are you in the US? I assume you are because you said you are using the fcc fw.
TweetFPV Yup, I’m in Maryland. Both the R9m and R9mm are running the lates firmware and I’m using the super 8 antenna. I have the T-Dipole on the R9mm mounted horizontally out on a rear arm. Vertical would be better but finding a place to mount so it doesn’t get chopped is a challenge! I was also very careful when I removed the stock antenna and have the T-Dipole glued on with Kafuter. That’s the stuff they use at the factory. It’s odd though. It’s not like I see the rssi drop off and it failsafes. It just drops like I hit the disarm. It can happen 10’ away form me or 100’ away. No warnings in the OSD or barking from the radio. The Betaflight OSD just show the post flight info. One thing I haven’t tried is to turn the radio off on the bench to see if BF gives a fail safe message. I would think it would give some kind of message. I do know this setup is susceptible to antenna orientation and do see a drop off when the quad turns. Like from 99 rssi to 60-70 rssi. I want to use the R9 not so much for LR but for penetration and one place I fly seems to have a lot 2.4 interference. I think I may have to turn on the black box on and see if some clue turns up with that. I had crazy yaw spins on another build once. It had nothing to do with the build but just dumb luck it only happened when I was flying it. Turned out to be a faulty gimbal in the Taranis. I wouldn’t have caught it screwing up without the black box recording. I haven’t flown since I upgraded the firmware because the weather has been crap here. For all I know it might be fixed. The more I look into it the deeper down that hole I go! When I saw the latency issue on the BF wiki I searched around some more and came across your video. It seems very few people are using the R9mm and thought you might have some insight. If I end up fixing it I’ll repost here as others may have issues as well.
Thanks for this video 🙏🏻 But I have a problem, I have all the connections like you, but impossible to have the sticks that work. You changed the cli? I dt understand, it's been 5 days that I try
try serialrx_inverted = OFF and serialrx_halfduplex = ON in the CLI. also make sure you have serial RX selected for uart 6 and fport selected in the config tab in betaflight
Is there anyway you can do a video about the r9mm setup on a matek f722 fc? Im have a huge issue trying to get telemetry!! Im going crazy with this issue!! PLEASE PLEASE
I don't think I can make a video specific to the f722 but being that it's a F7 it should be the easiest fc to wire up. What is the issue you are having?
I just thought about what pins I have soldiered up and if I remember right I put the s port pin on the "f.port-s.port" pin out. Is that where I went wrong?
That should be the right pad. Are you trying to use f. Port or sbus/s. Port? Where do you have the s.port with soldered to on the fc and which fw do you have flashed to the r9m and r9mm? Do you have rc commands or is it just telemetry that is giving you problems? What kind of problems are you having.
Im using "sbus" with the sbus flex fw. It says to soldier it to any unused "tx" uart (which I did). The issue is, whenever I power up i have everything else but telemetry on my radio. (im using the Taranis x9d plus) Ive set up everything right in the config. Im not good with coding so i dont touch the CLI part of the config tab. I have countless Quads and Wings running Betaflight and Inav. but I prefer to use KISS on my Quads and Inav for my wings. so i have never had this issue before untill i started using the knew R9MM system.
Sbus wire to a unused uart rx. Your s.port wire to any unused uart tx pad. You just can't use the same uart for both. For example sbus to uart rx1 s.port to uart tx2. Have you flashed the r9m and r9mm with the same fw? And after you flashed did you rebind the pair?
Does your qx7 have a new version of opentx on it? When you are setting up your model under external device r9m should be an option. If it isn't then you will need to update the opentx on the qx7. Other than that is the basic binding procedure for any frsky recievers. Select bind under the r9m in the qx7 and hold the bind button on the rx while applying power. What color is the led on the r9mm when you try to bind and after you try to bind?
@@TweetFPV I have updated to opentx 2.2.3, and selected ExternalRF on R9m. I set it to bind and it starts beeping. On the R9mm when I hold the bind button and apply power both LEDs are on continuously. It does nothing beyond that.
I just went an bound a r9mm to my tx to see what the lights on the rx do. When in binding mode with the TX not set to bind the RX has two LEDs on one red and one green both solid. Once the TX is set to bind the red led begins flashing very quickly and the green remains solid. Stop the bind on the TX and unplug the power to the RX. When i re-apply power to the RX the red LED is out and the Green one is on steady. Does this match what is happening for you? If not what happens with the leds during this process? It is possible that during the firmware updating process you could have accidentally flashed the wrong firmware to either of the devices. Are you in the US or other parts of the world. These devices aren't smart enough to know that you are flashing the wrong firmware to them. flashing the wrong firmware should damage them but it very well might make them not work properly. Both the R9M and the R9MM have FCC and LBT versions of the firmware. Be sure to flash the same kind to each device, as LBT and FCC firmware do not communicate to each other. As far as openTX 2.2.3 goes, that is still a nightly build and is chock full of bugs and errors. I would stay away from anything in this hobby that is listed as nightly or beta builds. You never know what is going to fail and how.
@@TweetFPV thanks for your help. What you described is happening, but the R9mm lights never start blinking, they are just on solid. I flashed the r9_mini_fcc to the RX and r9m_fcc to the module. My QX7 is FCC as well, because I'm in the us. I'll try loading 2.2.2 on it
Any reason you opted away from using just F. Port? Tossing between using F. Port alone or doing it the old fashion way. I have an Airbot Omnibus F4 V6 nano, not that really matters which F4 FC it is, but with the MM having "inverted", I should be able to just use single wire to TX6 or TX3. I saw your video on F. Port setup, with the Mini, which didn't have inverted and you had to use soft serial, and then saw you setup this one with the SBUS and S. Port after that video, so figured I'd ask. Is it reliability issue?
@@TweetFPV Thanks for the quick reply. I'll keep thinking this over. I have a few more days till the rest of my parts come in to complete this build...
@Jdc 3D I have F. Port running on my 5" build, using R-XSR and Mamba Stack, and I also have F. Port working on my 3" build with R9MM and Omnibus F4, and I have no issues on either build with telemetry or TX latency. I used the inverted pad on both the R-XSR and the R9MM connected to FC and ran command to tell FC it was uninverted. Don't remember the exact command. Either case, both work excellent
Damn i want to upgrade to Frsky from Flysky and need to change my RX of the Tyro79. But i only have 2 uarts, 1 for RX and the other one i use for smartaudio. Do i really need the smartport wiring, if not what do i lose?
You don't really need smart port telemetry. In all honesty I don't usually connect smartport unless it is convenient to do so. The only things you will loose is the sensor data comming back to your taranis. Depending on which reciever you use you will still get rssi and rx voltage regardless of if you connect smart port. You won't be able to use Lua scripts for pid tuning or Vtx audio switching but you can still do those things through the betaflight osd menus anyways.
@@TweetFPV That's nice to hear, i can get my hands on brand new X-lite + R9 Lite + R9mm RX all-in-one package for 150,- that's pretty good right? I've read something about Fport a few minutes ago and that seems pretty cool and easy to setup. Either way i dont mind my transmitter NOT talking to me :) All i'm thinking about is just hooking up Sbus and bridge 2 pads and be done with it. The only thing i'm worried about is having to flash something but everything is EU based, but i hope it has the latest firmware because there was improved Rssi also in firmware but i dont know if i should take that with a grain of salt. There's also old firmware with telemetry issues so i'm starting to think damn the whole telemetry stuff..
That is a good deal. A word of warning if you are in the US buy a fcc version of the x9 lite or of your in the EU buy a lbt version. The internal module was not designed to switch regions.
@@TweetFPV Yes everything is bought local from national website i guess they dont sell other than EU, the package is described as EU region so i hope it's good. I just ordered it, along with some heatshrink tubing for the receiver. Pretty hyped already man, it should be plug and play right, apart from binding /setting up channels etc.?
Trying to find the R9 mm set to the r9m module in my qx7 won't bind hold the bind button down on RX I get steady red steady green no blink and no bind I can bind this outside the bird can't I? Just by applying power or does S Bus have to go to something?
You can bind the RX without it being connected to the quad. which FW did you flash to the RX and TX? what color are the leds after you try binding and then cycle power?
TweetFPV i see, sorry for that. F.port is what I meant yes, thanks for response. F port seems to have much better optimization so actual difference in latency vs SBUS is significantly better :)
Yea as of now i run all my quads on f.port and even on access fport. I can actually feel the difference between sbus and the new access f. Port on the r-xsr.
Im having problems Trying to bind R9m and and r9 mm receiver. both modules have been firmware updated, both are showing leds that are saying waiting to bind. nothing is happening, i power off and back on the receiver but still not binded... what am i missing here? edit: wired with fport on a spracing f3 to uart 3 using +,- and TX pad
TweetFPV, sorry for a noob question, but I'm just trying to install that MM receiver and I think I'm doing something wrong. Im using old omnibus f4 v3 pro which probably doesnt have built inverter however I'm not sure. I've soldered S.port pad (not the inverted s.port) to the tx3 on the fc. It doesnt give me the input while receiver is bound, what am I missing? Great video BTW, it helped me to start with R9 :)
So a few things here for clarification. S.port isn't your rx controls sbus is. That sbus wire needs to go to the sbus/ppm pad on your fc. In betaflight that is probably uart1 that needs to be selected as serial rx. Then sbus selected In the config page as your reciever type. Then your inverted sbus wire from the rx goes to your tx3.
The last sentence just confuses me. Inverted S.port pad from MM to tx3 on my FC yup? Why inverted one not the 'S.port' one? Thanks for so fast response mate!
So... This is going to get confusing so just hang in there. S.port is what it is by frsky's definition of how sport works. In our understanding of how sport works we say that it is an "inverted" protocol (in comparison to all the other protocols). So when frsky gives you an "inverted sport" pad they are saying that it is inverted from what it was originally designed as. So in basic terms the "inverted sport" pad is what we would normally call a hacked or uninverted sport signal. Unfortunately I'm in a tough spot on how to refer to it on the r9 mm rx because frsky calls it "inverted sport" but we would normally call that inverted sport...... So I'm sure I have lost everyone at this point. Short and simple solder the "inverted sport" pad from the rx to the f4 flight controller. I hope this clears up the "Pam, Pam" thing (stepbrothers reference)
I have problems getten my rssi correct on my osd. When i discover new sensors to rssi pops up and say its at 100% In the osd it say 212%rssi. The rssi in the mixer tab is set to aux 8 because thats a must in Flight1. The rssi is working because when in walk away the rssi is getting less. When i lower the offset in the input tab to -100 the rssi value is still 112% I have connected the sbus to a rx and the inverted s port to a tx. I have followed the correct instruction from mr bardwell get rssi on osd video. Using flex firmware 180926 beta do you know whats the problem?
Sorry, I dont have a synergy f4, and I'm not totally sure what box reciever thing you are talking about. Contact me on discord discord.gg/b2nUTux and post up some picture and I can help you out.
@@TweetFPV thx for your reply... ya got me flyin' Tweety... still confused... although fport is using a hardware inverted S port connection on Rx. Oscar, KnowItAll couple others have posts stating fport works on the un inverted UARTs and solves the inversion issue with F4 FCs. Sounds legit to me any program can be written to work through different types of serial connections. I'll give it a whirl on my next build.
Originally f.port was reported to solve the inversion issues but when it hit the streets in the small form rxs this was not the case. F.port does require a inverter on a uard with the exception of the r9mm and r9 slim+ rxs. Those have built in inverters to allow the fc to work with f.port/s.port when they don't have a second inverter on a uart. I hope that makes sense this inversion stuff is way too confusing. You have the r9mm rx so you can choose to use inverted or un inverted s.Port / f.port.
@@TweetFPV Makes sense to me... I'm on my 3rd build... 1. Tyro99 with R XSR lost :(... Had RSSI and Battery wich works without S Port on reciever and RSSI on OSD. 2. Tero Q215 XM+ RSSI 3. Tyro99 again with R9MM keeping things cheap til' I fly better. If or when I quit crashing I'll buy a better quad. I'm having lotta fun.
Straight up and down is the most ideal. Not in a V shape like older 2.4g diversity setups. Some people run them straight but horizontally which works but when you turn you run the risk of pointing the null directly at yourself and can failsafe. These long range systems are very unforgiving with poor antenna placement.
For optimal performance the antenna should be ran as straight as possible in a vertical orientation. Personally unless I'm trying to get the max range from it I make a compromise between rf performance and durability and I moun the antennas horizontally attached to one of the rear arms of my Quad. Recently I mounted one in the traditional "V" orientation on a race only Quad and have so far had no issues with it but have never had it out more than about 100 yards. I have a batch of antennas coming from frsky and will be trying those out.
Hey mate, which firmware did you flash on either the R9MM receiver and R9M module? The basic or the Fport one? I'm not able to obtain telemetry back from the quad... Thanks, cheers 👍🏻
I'm basically using all F. port with the R9MM receivers. The FW for the R9M module needs to be the same version as what you flash to the R9MM receiver. So basically any time you change you FW on either the TX or RX when you need to flash everything.
www.frsky-rc.com/r9-mm/ Go to accst then click the history download link at the bottom if you want Pre accst 2.x otherwise use V 19.02.01 there should be a fport fw file included.
Unless you are trying to use access. Then after you register and bind your reciever. Go into the receiver options and you select f.port through the software.
ok to clarify on the diagram from frisky they have Sbus out, Sbus in, separate Sport. Is your correction the blue wire the equivalent to the Sbus out or in or Sport ? Is the Green wire Sbus in or out? Thanks again. I am having issues with this. I cant get the Fport one wire to work despite CLI attempts etc
The SBUS in is for using receiver redundancy like if you wanted to run 2 receivers. Which FC are you trying to use f.port with? Depending on your FC using F.Port might not be possible with the R9MM RX. So based on the colors i used the connections should be as follows: blue UART TX for s.port green SUBS for RC signals red Power black Ground
@@TweetFPV Thank you. I am using a F7 Kakute, The fr Sky instruction sheet I have does not show inverted sport where you noted it. On my sheet from top to bottom with the channel holes on top Sbus_out, S.Port/Fport, GND, V_in, SBUS_in. I have finally got the radio and receiver to be seen by Beta, but I am only getting RSSI telemetry. I will sort that out next and I believe it has to do with my transmitter settings. I am bummed that the FPORT despite loading the new firmware and flashing and no issues with binding, the Beta does not see the fport. I did all permutations for CLI. Thanks again.
@@diveflyfish you need to flash the fport fw to the r9mm. Then connect the s.port wire to the "telm" port of your fc or to any unused uart tx pad. Contact me on my discord server. It's a lot easier to help you there. This is a easy fix but pictures help. discord.gg/R6DUpF
never mind the link, but from the color code you used to the receiver and then to the fc you reversed what you called them, you set up the fc as you called them in hookup to the fc but it shouldn't have worked when you powered the receiver?
I have two questions on the R9 mm RX do you use ground power and S bus? I did it that way and it won't bind with my receiver r9m module also frsky XM Plus RX I flashed mine an AUX 12 is active 4 RSSI but on betaflight CLI my Merica 5 inch it won't let me switch RSSI channel to 16 on my mobile device when I hit save and reboot they kicked me out and says USB is disconnected and when I try to change RSSI on the configuration tab to aux 12 and save it when I refresh or go off that tab and come back it's back to disabled what's up with this thing? The FC is a Aio running siskin 32 bit esc
For the RSSI issue i have seen this when you have "analog RSSI" enabled in the BF config tab. Disable that and see if you can change RSSI to AUX 12 in the RX tab. I usually connect my R9MM RX in this manner. From the RX I use S.bus, power, ground, "inverted" s.port (on a F4 without a inverter on a UART TX pad) If you are having issues with binding my first recommendation is to re-flash firmware to your R9M module and your R9MM RX. also every time you update FW always re-bind your setup even if it seams like i still have a bind. I hope this helps you out. if you have any more questions please let me know.
If that is the case and you have the mamba f405 then take the inverted s.port in from the r9mm (bottom pin) and connect it to uart 3tx you don't need soft serial. Just select smart port telemetry in betaflight ports tab on uart 3. Select telemetry in the config tab and hopefully that will work. If it does not you might need to do some work in the cli to change telemetry inversion.
Believe this or not but apparently the wire I was using for a signal wire was broken internally replace that wire and it updated now I need to know how to wire them in hopefully just using power ground S bus or do I use s port? I flashed them on the S Port wire
Any flight controller can use the r9 system because all flight controllers have the ability to use sbus. Sbus is just the control signals from your radio. The telemetry aspect is a seperat signal called smart port and is the communication from your flight controller back to your radio and requires a seperate uart. Telemetry is useful for pid tuning and Vtx adjustment but all these functions can be done through the betaflight osd without the need for telemetry. Typically f4 flight controllers especially 20x20 ones lack extra uarts to use sbus and smart port.
Hey there.. How do I connect this to a Helio AIO board? I am new to this Fport Sport concept. And I see that you said vertical orientation is the best for range, right? Didnt you have a 3D print where you could mount the antenna, similar to immortal T?
Which Helio board are you trying to use? There are a bunch of designs out there that work. Check out tinigiverse and find something that will work for your frame.
You could probably get away with using cut zip ties and heat shrink untill you get your antenna tubes. As far as your connections go you have a "sbus" pad and a "s.port" pad on your fc. Just solder the respective wires from your rx to those pads and you should be all set.
yeah i followed this one guy on setting up r9m and he does not know whats going on i did all this and now it just blink low number on my osd th-cam.com/video/hcTIBMDUyAU/w-d-xo.html
h, what I'm missing. I have no telemetry apart from RxBt and RSSI after Discover new sensors. I've installed an R9 MM with latest firm FLEX_20190201. and OpenTx 2.2.3 on my Taranis Qx7. The channels are working great. The problem is the lack of sensors in the telemetry
Did you flash the r9m and the r9mm with the same fw? If so did you re-bind the two after fw flashing? Do you have telemetry selected in bf config page? Do you have the correct uart selected for smart port telemetry in the bf ports tab? Which pin are you using for smart port on the r9mm? Which flight controller are you using?
Thank you for your fast answer. My FC is a HAKRC Flying F4 v3. I have telemetry selected in BF. I have flashed FLEX_20190201 on R9 MM and R9M_FLEX in the TX module. I'm going to check the rest and back to you later. Thank you
Re-bind again after fw flashing. I dont have uart selected because I'm using F.port. Is it necessary? I'm using the S.PORT/F.POT pin on R9 MM. The result is the same, i.e. only RxBt and RSSI after Discover new sensors.
Ok so your using f.port. Are you connected to a uart tx or rx? Also which pad are you connected to on the r9mm? You should be connected to the bottom pin (inverted s.port) and to a uart tx on the fc.
I don't know what's going on I tried to flash this piece of shit with a s port / fport wire and with sbus out and keep getting the same message " FW update error bottom pin no resp" now what do I do throw it all in the garbage? I know that asked for it works because I updated my XM plus receivers and they work I have a R9 Mini and a R9mm and have the same problem on both I updated them once but then the mini won't bind with my r9m module any help? Or off to the garbage can because this isn't fun anymore
His RSSI signal is showing up on AUX 12 which equates to CH 16 - in the receiver tab he needed to indicate RSSI is on channel 16 (AUX 12) and then in the other tab where you configure what you see in OSD have it reflect RSSI and it will show what is being output to channel 16.
Yes this works with the newer firmwares. It didn't when these recievers first came out. And I find that it take a couple of seconds after startup for the rssi to "come alive" in my osd.
Aux 12 (or ch16) is where the rx is giving betaflight rssi. You can choose to use that as your rssi value source for your osd but the scaling tends to be off, or you can choose to send the rssi from your transmitter back to bf on an aux channel for betaflight to use. I find that the one from the transmitter back to bf via an aux channel is a bit more accurate.
@@TweetFPV wow thank you for the quick response! i have one more question. im about to connect my last wire the "inverted s port" how do i know which tx to connect it to? im looking on my fc the cl racing f4 and i can only see a telemetry pad. Will clicking smart port in betaflight on the wrong uart brick my fc? i guess another question would be, How can i locate where my uarts are?
Wire the s. Port pad from the rx to the telemetry pad on the fc. The clf4 was designed with an inverter for smart port telemetry and should work with the normal s.port signal.
Hoping maybe you can help me, I have tried repeatedly to update a R9 mini and i keep getting a “Firmware update error module not responding” message from my Taranis X9D+. I have tried 2 different Mini 9’s same error message??? Can anybody help?
Sure. What pins do you have connected from your r9 mini to you Jr bay on your x9d? Also which fw are your tryinb to flash and what version of opentx do you have on your taranis? Does the r9 mini leds light up when you try and flash it?
TweetFPV i have the S. Port going to the bottom pin then ground then power. I have tried the newest firmware 190201 including the Flex. I have 2.2.4 open tx. Yes the lights do come on but even that took awhile.
I’ve got a crocodile 7 with the r9mm and I can’t figure out what the fuck is wrong... it came with only 3 wires connected to the r9mm and I think that might be the problem but idk... I’ve tried everything I can think of...
Okay trying to flash the R9 mm rx I use voltage in, ground,,, the last one do I use sbus or s port/f port? Both ways I tried keeps telling me that it's not reading the bottom pin I have a qx7 with the smart part on the front and when it goes into the firmware it says flash external module or flash s port so what's supposed to work I did it once before and it worked. I don't know why please help otherwise $1000 worth of birds goggles and transmitters are going to be smashed up with a hammer
Try power, ground and s.port. Connect to the smart port connector on the bottom of your x7 (next to the USB port) select flash external module. If that doesn't work try selecting flash s.port. If you have a older x7 some of them made you flash the rx through the pins in the Jr module bay like the x9d radios do. Do this with the r9m removed from the radio in either case.
Man you make soldering look not so scary, like there is a good chance you could get it done without having to burn down a home, you know my greatest fear. thanks!
Soldering isn't all that hard. Decent equipment makes the job a lot easier and practice helps too!
Thanks for confirming this was a JST-PH 2.0 connector. I'll be purchasing a 5-pin male/female pair so I can have a removable RX like the R-XSR. Have your thumbs up!
Just got my r9m in (with the same flight controller no less) and going to be connecting it up with a gps for rescue mode and gps speed looks like a fun build. Thanks for the walkthrough I love how many uarts this board has
Cheers buddy, followed steps and worked first time!! Excellent instructions and subbed... Nice work!!
Great to hear it. Thanks for the sub!
I‘m new to the FrSky system ..i got a x-lite pro ..the R9m module and the R9MM receiver.. and i dont know why the binding does not work 😅 ... it was no problem with the r-xsr receiver on another drone. ^^
Haha yea this stuff can be a bit confusing and it almost always comes down to a fw incompatability contact me on discord so I can better assist you discord.gg/b2nUTux TH-cam chat is very difficult to troubleshoot.
Very helpful, thanks... can you please send the link for the small vice that you used.
www.thingiverse.com/thing:2064269
Like your videos can’t wait till I make the switch to the r9
Awesome! thanks for the video, I kinda wish I hadn't bought 15 r9 mini's. Oh well.
F7 for life!
Can't wait to get mine
I pre ordered mine with the promotion
The FC is a omnibus f4 v6 not a lot of info on it ,thanks Rick..
Are you using the r9mm?
Great video, thank you, but I couldn’t get this to bind with t18 jumper.
most likely it is going to be a FW mismatch between your radio and your receiver.
@@TweetFPV yes I thought that but I’ve updated them all to the latest. Things are too complicated now
Fantastic work, dude. Really nice! 😊
Frsky 9 m mini.
I all so have a frsky 9 slim + I'm basically looking for telemetry connections.
Where is the RSSI pad on the 9MM? I have a RSSI pad on my FC and want to ensure I can use the RSSI. Thanks again,
Cheers
There is no rssi pad. The rssi comes into betaflight as aux 12 if you flash the newer firmware. Either way rssi is always a telemetry sensor between the rx and your TX.
Thank you!!
Thank you!!
Thanks 4 explaining all. Cheers.
Havent you just switched the sport cable with the sbus cable? The girst cable you soldered you say was the sbus cable but it wss the sport cable isnt it?
Sorry man i just see the discriptionafter i send this😉
You are correct, I noticed this error after uploading. There is a correction in the video description.
@@TweetFPV i noticed yesterday that if i want to connect sbus and sport telemetry on my kissfc v2 i must solder the s-port/f-port pad to the kiss fc and not the inverted s-port.
thank you very much, this is useful for me, i'll try this and i will ask you if i have issue. i hope you don't mind. have a nice day and best wishes for you 🙏❤️
So if there is a S.Port (and the FPort) and an Inverted S.Port is the inverted S.Port also an inverted FPort? Trying to get around having to use a UART with an inverter
The the inverted pad is and inverted smartport or fport depending on which firmware is flashed to your rx.
@@TweetFPV thanks, that is what I was assuming.
You wired the S Bus out to RC? Can you use the connection below that namely F/port SPort instead ? Thank you for the clarification. Have a great day.
You can if you flash fport fw to the reciever. But there are issues with f4 flight controllers not taking a uninverted signal. The r9mm also has an inverted sport/fport pad which will work with a f4 fc that doesn't have a built in signal inverter.
Awesome video exactly what I needed thank you so much!
Glad it helped!
You soldered it backwards or you just said it backwards in the beginning but sport is your blue wire according to you labeling it when you put em on. And when you weed it into the fc you out the green as s-port ;)
Yea. I cought that afterwards. But I left a note in the description
Aaah so i am not the only one that seen it😅
So if my FC doesnt have extra uart should I install using F.Port? Thats only one wire...
Betafpv whoop 20a fc going on 95x..
Possibly, but depending on which receiver you are using like the r9mm it has a inverted pad that can go to a uart tx pad that doesn't have a built in inverter (most f4 fcs) otherwise you are only going to be able to use sbus. Fortunately you will still get rssi with newer fw without using smart port telemetry.
@@TweetFPV yes R9MM ill probably end up skipping telemetry.. But twice now I have telemetry receiver and can't get telemetry to work lol.. i thought u can get an uninverted signal from r9mm.. Oscar Liang article said it.. idk.. ill try it while everything is apart. When stuff shows up. Maybe I'll put in a temporary frame to test
Yes you can get and uninverted signal from the r9mm. That can be used a ls f. Port for both rc and telemetry on a f4 fc. That wire needs to go to a uart tx pad.
@@TweetFPV ok cool.. thanks. I got to read more about f.port.. ill look if u have a video lol.. only have done sbus
Thank you for the video. Can you share STL files for this item at: 4:55 ?
www.thingiverse.com thing #2064269
Hey Tweet. Where on TH-cam is a good review of THE QUALITY OF THE RADIO LINK of the r9 system. Your videos, like every other video out there talks about how to hook it up. But is this a good, solid, failsafe free system?
I don’t want to buy Crossfire because I hate TBS, but I’m not going to switch over to r9 until I know what kind of performance to expect.
I ask you because it seems like you know the answer.
Enlighten me!!!
I have a video where I test the distance of the two systems but not with it installed Ina Quad. I have had great results with both the crossfire and the r9 systems. Neither system is a silver bullet though. It isn't as forgiving to poor rf environments and poor installations of recievers antennas. There is a bit of work with both systems to get them to be reliable. Now with the region specific antennas released from frsky I think a lot of the poor rf conditions will be fixed.
TweetFPV - thanks for the quick reply. Interesting answer too. I guess maybe it’s not time yet for everyone to ditch 2.4 yet... huh?
I would just hate to “upgrade” to 900 MHz , and then lose my quad because of a failsafe.
I originally started using a 900 system at distances that I would normally fly 2.4g just to never have to worry about failsafes and for that these systems are great. Now when you are trying to do long distance flight there is a lot of testing and tuning with any system. When I fly at normal distances and normal environments my rf signal is no longer a thing I even think about. My limiting factor is my 5.8g video signal.
TweetFPV - Oh ok. Well that sounds pretty good. Is the immortal T type antenna the best option in your opinion? That seems to be what most people like.
Thanks for your help... subbed 🤓👍🏽
T style antenna on the Quad an a super 8, or tbs diamond antenna on the transmitter is the ideal setup. The stock antenna that comes with the r9m module isn't veery good and accounts for the majority of failsafes I've seen.
Also with the R9 m m I don't know what to solder to on the FC can't I just use ground voltage and S Bus?
Could I use the "inverted" S.Bus signal with f.port to a UART without a serial inverter? Reason I ask is I've got an omnibus F4 that's never worked with frsky's inverted signal, so I had to do the uninversion hack to my XSR. If I could use the r9 mm it would make my day.
I can not confirm that fport on the "inverted" pad will work but it should. That's my next test of this rx.
@@TweetFPV I have Omnibus F4 v5.1 with only 3 Uarts (one i use for esc telemetry, another for vtx, and only one free uart i use for R9m f.Port. so the only way to get f.Port working for me was to solder the f.Port Signal fbus (not sbus) to the sbus pad on my Omnibus FC. And so i dont Need to use sbus soldering. Furhermore i needed some CLI entries for Inversion and Duplex and half Duplex (every single CLI command was nessecary. for more Questions ask me!
@@mh7711 Max... I think you save me. Days trying to setup R9MM Fport on my Omnibus F4 V5. TX6/TX3/TX1. And now, connecting the fport wire to the SBUS pad... IS WORKINGGGGGGGGGGGGGGGGGG (on INAV)!!!! So, at the configuration tab, fport is selected. And I think that... as the UART6 is for the SBUS... and TX6 is UART6 too..... then... I'm HAPPY. Thank you very much. you have enlightened me :)
@@ale-fpv Thank you for your feedback, nice u got it working yes it was frustrating for me at the beginning, too
I have followed your tutorial and all mine does is binds with telematry info etc but no stick input. I have the mamba F405 MK2 F4 FC and R9M Lite module also the Frsky X Lite-S. All flashed with latest ACCESS firmware and Frsky firmware for the F.port, also tried to run without SBUS, still have telematry but no stick input.
were you able to get it to worked? i have the exact same setup, but qx7s radio...
@@eduardosalasmx I used sbus in the end. Could never get telem. On it
hi , nice videos. i have the helios spring fc, which is a f3 and f4 board, is there a certain way to hook up this fc. thanks
If you can find the diagram for the helio fc just connect the r9 reciever the same way they show connecting the r-xsr reciever blog.seidel-philipp.de/wp-content/uploads/2018/03/HELIO_SPRING_Flight_Controller_Anschlussplan_Wiringplan.jpg I don't have first hand experience with the helio board but based on that diagram I think it will be a easy setup.
ok, the board has a sbus and a s port. it shows the r-xsr hooking up that way. my question is the inverted s port goes there or s port/fport goes there or does it go on a tx pad?
here is the diagram
fpv-flightclub.com/products/helio-spring-imu-f-v2/
thanks
Inverted sport from the r9mm goes to the sport pad on the fc. Then the sbus from the r9mm goes to the sbus pad.
thank you very much, confusing ha? because the second one down on r9m is s port/fport. in the setup menu in betaflight under ports do i need to setup the s port or just the serial rx
You will need to setup both is bf if you want telemetry
Hello sir thanks for great work. I have followed your video and for some reason I have no stick inputs in the betaflight receiver tab. My f4 has a inverted s bus . Any thoughts?? Really stumped on this one
which RX and FC are you using?
@@TweetFPV hello sir thank you for your reply. I have found my issue which was a broken sbus wire. Literally the wire was split,while all the silicone cover was completely intact. The Only reason I caught it was because I was checking my solder connections and the wire stayed at 90 degrees. Again thank you for your reply. Your work is invaluable to the community and especially for us noobs cheers.
It's great news that you found the problem! Thank you for the kind words. I'm always happy that I can help someone!
Thanks for the vid..do you have the stl’s for you vide?
Oh for the Floss antenna holder.i have them but havent posted them yet. I forgot to. I'll try and get them up and linked to this video.
The green *vice* I think he meant. Excellent video, btw, my dude. I'm just installing my R9 MM into a small 3" with Turtle v2 =)
Nice! If it's the green vise your looking for go to the usual place www.thingiverse.com and search for it.
Hi all,
Great video !
I'm trying to connect the R9MM to a MAMBA F405.
Could I connect the SBUS and the S.port to the same number of RX and TX? (ex. RX1 and TX1)
Inverted S.port?
Could I use the F.port?
Kind regards
Sbus and s.port can not go to the same uart. on this board sbus must go to uart rx1. That uart is the only one with a built in inverter. Here are your options with the mamba and the R9MM.
1) Sbus to RX1, "inverted S.port" to any unused uart TX pad with a Sbus firmware flashed to the R9MM
2) "Inverted S.port" pad to any unused uart TX pad with a F.port firmware flashed to the R9MM F.port signal will be sent out from the R9MM
@@TweetFPV Thanks for your quick reply.
I need to connect the smart.audio from the VTX (TX) and the GPS (RX and TX), so I think I have only the option of F.port.
In the second option you say (("Inverted S.port" pad to any unused uart TX)), why not use directly the S.port/F.port pad on the R9MM?
The regular sport/fport pad on the r9mm is not a inverted signal and the r4 processor does not have the ability to invert those signals internally like on a f3 or F7 chip. You need some external hardware inverter either on the fc or the rx. The mamba does not have any such inverter except on the rx1 pad for sbus. The protocol for fport requires it to be connected to a TX on a uart. The "inverted" pad on the r9mm does this signal inversion and allows the f4 processor to understand the signal.
You my friend are a god!!! it took me 5 Seconds to do what you said!! RSSI works perfect on the Merica!! Also once I turned off the analog OSD it let me switch to channel 16 in the CLI for RSSI the woman who sold it to me and built it couldn't tell me how to do any of it goggle face out of North Dakota Lexi d anyway I have a custom gep sparrow that I bought from her as well it has a hglrc F3 Evo I can't configure OSD on BF I'll have to get on a computer but do you know what OSD that is is it minim that's what betaflight tells me from the description that she told me the FCC doesn't have OSD but it's built into the VTX so maybe I can't get RSSI on my OSD Channel 12 is active for RSSI on betaflight and on the CLI Channel 16 is assigned for RSSI? Thank you again sir
I've set mine up and I get rssi back but I can't get luas to run. Any ideas?
Do you get all the sensors in the sensors tab in your radio. You will always get rssi and rx voltage. If you aren't getting all the sensors from bf then the luas won't work because you don't have telemetry working properly.
@@TweetFPV it's fine now I had telemetry set to frsky not smart port
Thanks for the video! Why is it when I bind the r9mm channel with range 1-8 for better latency, I'm still getting rssi on channel 16? Is it not possible to bind in 1-8???
With the r9mm the rssi comes across on ch16. It just part of the firmware.
TweetFPV Thanks for the reply. The reason I’m asking is because this thing drops out of the air as though I disarmed it. This isn’t my first build but it’s my first go around with R9 setup. I’m trying to eliminate all other possibilities like power loss, poor ground, or maybe even a faulty R9mm or R9m.
From what I gather, I may have a packet loss issue in Betaflight when binding in 1-16 channel range ( github.com/betaflight/betaflight/wiki/SBus-FPort-and-RC-Smoothing ).
So I rebound in 1-8 range (which is all I need anyhow) and still see Rssi over channel 16 in Betaflight. Therefore my head is about to explode. The more I try to figure out what’s going on the further down a rabbit hole I go!
So, since I bound in 1-8, that’s all I should be able to use, i.e. AETR plus Aux 1-4 and the R9mm just sends rssi down channel 16 anyway? Am I thinking this correctly? And my latency should be at 9ms thereby eliminating or rather minimizing any packet loss.
I’m trying to make this thing work since I paid for it but geeze, I’m about to rip it out and put a trusty ole r-xsr in it!
God, I hope that all made sense!
Thanks.
Oh, and it has the latest faa firmware. One was released just yesterday actually.
I see, there are a LOT, i mean a LOT of antenna issues with the r9 system. This LR stuff is great but it is very sensitive to poorly made and mounted antennas. As far as fw goes I have not tested the recent fw but I have had excellent results with the 2018-08-21 firmware. Be sure you update both the TX and rx. If you are using the stock antenna that came with the r9m I suggest looking at the super 8.
How do you have your antennas orientated on the Quad and are you in the US? I assume you are because you said you are using the fcc fw.
TweetFPV Yup, I’m in Maryland. Both the R9m and R9mm are running the lates firmware and I’m using the super 8 antenna. I have the T-Dipole on the R9mm mounted horizontally out on a rear arm. Vertical would be better but finding a place to mount so it doesn’t get chopped is a challenge!
I was also very careful when I removed the stock antenna and have the T-Dipole glued on with Kafuter. That’s the stuff they use at the factory.
It’s odd though. It’s not like I see the rssi drop off and it failsafes. It just drops like I hit the disarm. It can happen 10’ away form me or 100’ away. No warnings in the OSD or barking from the radio. The Betaflight OSD just show the post flight info. One thing I haven’t tried is to turn the radio off on the bench to see if BF gives a fail safe message. I would think it would give some kind of message.
I do know this setup is susceptible to antenna orientation and do see a drop off when the quad turns. Like from 99 rssi to 60-70 rssi.
I want to use the R9 not so much for LR but for penetration and one place I fly seems to have a lot 2.4 interference.
I think I may have to turn on the black box on and see if some clue turns up with that. I had crazy yaw spins on another build once. It had nothing to do with the build but just dumb luck it only happened when I was flying it.
Turned out to be a faulty gimbal in the Taranis. I wouldn’t have caught it screwing up without the black box recording.
I haven’t flown since I upgraded the firmware because the weather has been crap here. For all I know it might be fixed. The more I look into it the deeper down that hole I go! When I saw the latency issue on the BF wiki I searched around some more and came across your video. It seems very few people are using the R9mm and thought you might have some insight.
If I end up fixing it I’ll repost here as others may have issues as well.
are you running f.port or sbus/s.port?
Thanks for this video 🙏🏻 But I have a problem, I have all the connections like you, but impossible to have the sticks that work. You changed the cli? I dt understand, it's been 5 days that I try
Which fc, rx, and which firmware do you have flashed to both? Are you using fport or sbus?
TweetFPV fc = Omnibus F4 V3
RX = R9mm flash with r9mm flex fport
I use fport 🤷🏼♂️
Ok so fport. What pad do you have your signal wire soldered to on the rx and on the fc?
TweetFPV mmh, inverted sport to tx6, i understand a litte bit english
try serialrx_inverted = OFF and serialrx_halfduplex = ON in the CLI. also make sure you have serial RX selected for uart 6 and fport selected in the config tab in betaflight
Is there anyway you can do a video about the r9mm setup on a matek f722 fc? Im have a huge issue trying to get telemetry!! Im going crazy with this issue!! PLEASE PLEASE
I don't think I can make a video specific to the f722 but being that it's a F7 it should be the easiest fc to wire up. What is the issue you are having?
I just thought about what pins I have soldiered up and if I remember right I put the s port pin on the "f.port-s.port" pin out. Is that where I went wrong?
That should be the right pad. Are you trying to use f. Port or sbus/s. Port? Where do you have the s.port with soldered to on the fc and which fw do you have flashed to the r9m and r9mm? Do you have rc commands or is it just telemetry that is giving you problems? What kind of problems are you having.
Im using "sbus" with the sbus flex fw. It says to soldier it to any unused "tx" uart (which I did). The issue is, whenever I power up i have everything else but telemetry on my radio. (im using the Taranis x9d plus) Ive set up everything right in the config. Im not good with coding so i dont touch the CLI part of the config tab.
I have countless Quads and Wings running Betaflight and Inav. but I prefer to use KISS on my Quads and Inav for my wings. so i have never had this issue before untill i started using the knew R9MM system.
Sbus wire to a unused uart rx. Your s.port wire to any unused uart tx pad. You just can't use the same uart for both. For example sbus to uart rx1 s.port to uart tx2. Have you flashed the r9m and r9mm with the same fw? And after you flashed did you rebind the pair?
Hey man, can i ask the stl for your soldering jig🤔
www.thingiverse.com/thing:2064269
Hey, can you flash the MM firmware to the mini and see if it works?
Hi, I have an F7 FC and a Taranis X-lite, which 900 mhz receiver/transmitter should I buy? Thanks!
FrSky R9 MM-OTA m.banggood.com/beelink/ruzgGC
can i use this same wiring with my DYS F4 pro v2 FC ???? Please help me.
It won't be the same. Use sbus from r9 mm to rx1 on the fc and inverted smart port from the r9mm to tx3.
Just got this R9mm and the module for the QX7. I've updated the reciever and module, but I can't get it to bind with my transmitter. Any ideas?
Does your qx7 have a new version of opentx on it? When you are setting up your model under external device r9m should be an option. If it isn't then you will need to update the opentx on the qx7. Other than that is the basic binding procedure for any frsky recievers. Select bind under the r9m in the qx7 and hold the bind button on the rx while applying power.
What color is the led on the r9mm when you try to bind and after you try to bind?
@@TweetFPV I have updated to opentx 2.2.3, and selected ExternalRF on R9m. I set it to bind and it starts beeping. On the R9mm when I hold the bind button and apply power both LEDs are on continuously. It does nothing beyond that.
I just went an bound a r9mm to my tx to see what the lights on the rx do. When in binding mode with the TX not set to bind the RX has two LEDs on one red and one green both solid. Once the TX is set to bind the red led begins flashing very quickly and the green remains solid. Stop the bind on the TX and unplug the power to the RX. When i re-apply power to the RX the red LED is out and the Green one is on steady. Does this match what is happening for you? If not what happens with the leds during this process?
It is possible that during the firmware updating process you could have accidentally flashed the wrong firmware to either of the devices. Are you in the US or other parts of the world. These devices aren't smart enough to know that you are flashing the wrong firmware to them. flashing the wrong firmware should damage them but it very well might make them not work properly. Both the R9M and the R9MM have FCC and LBT versions of the firmware. Be sure to flash the same kind to each device, as LBT and FCC firmware do not communicate to each other.
As far as openTX 2.2.3 goes, that is still a nightly build and is chock full of bugs and errors. I would stay away from anything in this hobby that is listed as nightly or beta builds. You never know what is going to fail and how.
@@TweetFPV thanks for your help. What you described is happening, but the R9mm lights never start blinking, they are just on solid. I flashed the r9_mini_fcc to the RX and r9m_fcc to the module. My QX7 is FCC as well, because I'm in the us. I'll try loading 2.2.2 on it
Couldn't hurt to reflash the rx and rx just to be sure
Any reason you opted away from using just F. Port? Tossing between using F. Port alone or doing it the old fashion way. I have an Airbot Omnibus F4 V6 nano, not that really matters which F4 FC it is, but with the MM having "inverted", I should be able to just use single wire to TX6 or TX3. I saw your video on F. Port setup, with the Mini, which didn't have inverted and you had to use soft serial, and then saw you setup this one with the SBUS and S. Port after that video, so figured I'd ask. Is it reliability issue?
I haven't had any issues but I want to keep things as simple as possible. I just haven't gotten around to trying the f.port setup with the r9mm yet.
@@TweetFPV Thanks for the quick reply. I'll keep thinking this over. I have a few more days till the rest of my parts come in to complete this build...
Are you going with the r9mm or the r9 mini?
@@TweetFPV I bought the special combo R9M Lite pack, which came with the r9mm receiver
@Jdc 3D I have F. Port running on my 5" build, using R-XSR and Mamba Stack, and I also have F. Port working on my 3" build with R9MM and Omnibus F4, and I have no issues on either build with telemetry or TX latency. I used the inverted pad on both the R-XSR and the R9MM connected to FC and ran command to tell FC it was uninverted. Don't remember the exact command. Either case, both work excellent
Damn i want to upgrade to Frsky from Flysky and need to change my RX of the Tyro79.
But i only have 2 uarts, 1 for RX and the other one i use for smartaudio.
Do i really need the smartport wiring, if not what do i lose?
You don't really need smart port telemetry. In all honesty I don't usually connect smartport unless it is convenient to do so. The only things you will loose is the sensor data comming back to your taranis. Depending on which reciever you use you will still get rssi and rx voltage regardless of if you connect smart port. You won't be able to use Lua scripts for pid tuning or Vtx audio switching but you can still do those things through the betaflight osd menus anyways.
@@TweetFPV That's nice to hear, i can get my hands on brand new X-lite + R9 Lite + R9mm RX all-in-one package for 150,- that's pretty good right? I've read something about Fport a few minutes ago and that seems pretty cool and easy to setup. Either way i dont mind my transmitter NOT talking to me :) All i'm thinking about is just hooking up Sbus and bridge 2 pads and be done with it.
The only thing i'm worried about is having to flash something but everything is EU based, but i hope it has the latest firmware because there was improved Rssi also in firmware but i dont know if i should take that with a grain of salt. There's also old firmware with telemetry issues so i'm starting to think damn the whole telemetry stuff..
That is a good deal. A word of warning if you are in the US buy a fcc version of the x9 lite or of your in the EU buy a lbt version. The internal module was not designed to switch regions.
@@TweetFPV Yes everything is bought local from national website i guess they dont sell other than EU, the package is described as EU region so i hope it's good.
I just ordered it, along with some heatshrink tubing for the receiver. Pretty hyped already man, it should be plug and play right, apart from binding /setting up channels etc.?
Should be but there are some firmware updates for the x9 lite. You'll also need some 18650 batteries and a sd card.
Trying to find the R9 mm set to the r9m module in my qx7 won't bind hold the bind button down on RX I get steady red steady green no blink and no bind I can bind this outside the bird can't I? Just by applying power or does S Bus have to go to something?
You can bind the RX without it being connected to the quad. which FW did you flash to the RX and TX? what color are the leds after you try binding and then cycle power?
Hi, a little puzzled. F.bus needs only Power, GND, and uninvented SPort. Why did you connect also SBUS?
I think you mean f.port. I'm using sbus and smart port in this video because at the time of recording fport was unreliable.
TweetFPV i see, sorry for that. F.port is what I meant yes, thanks for response. F port seems to have much better optimization so actual difference in latency vs SBUS is significantly better :)
Yea as of now i run all my quads on f.port and even on access fport. I can actually feel the difference between sbus and the new access f. Port on the r-xsr.
@@TweetFPV awesome news :)
Im having problems
Trying to bind R9m and and r9 mm receiver. both modules have been firmware updated, both are showing leds that are saying waiting to bind. nothing is happening, i power off and back on the receiver but still not binded... what am i missing here?
edit: wired with fport on a spracing f3 to uart 3 using +,- and TX pad
What color are the leds on the rx?
TweetFPV, sorry for a noob question, but I'm just trying to install that MM receiver and I think I'm doing something wrong. Im using old omnibus f4 v3 pro which probably doesnt have built inverter however I'm not sure. I've soldered S.port pad (not the inverted s.port) to the tx3 on the fc. It doesnt give me the input while receiver is bound, what am I missing? Great video BTW, it helped me to start with R9 :)
So a few things here for clarification. S.port isn't your rx controls sbus is. That sbus wire needs to go to the sbus/ppm pad on your fc. In betaflight that is probably uart1 that needs to be selected as serial rx. Then sbus selected In the config page as your reciever type. Then your inverted sbus wire from the rx goes to your tx3.
The last sentence just confuses me. Inverted S.port pad from MM to tx3 on my FC yup? Why inverted one not the 'S.port' one? Thanks for so fast response mate!
So... This is going to get confusing so just hang in there. S.port is what it is by frsky's definition of how sport works. In our understanding of how sport works we say that it is an "inverted" protocol (in comparison to all the other protocols). So when frsky gives you an "inverted sport" pad they are saying that it is inverted from what it was originally designed as. So in basic terms the "inverted sport" pad is what we would normally call a hacked or uninverted sport signal. Unfortunately I'm in a tough spot on how to refer to it on the r9 mm rx because frsky calls it "inverted sport" but we would normally call that inverted sport...... So I'm sure I have lost everyone at this point. Short and simple solder the "inverted sport" pad from the rx to the f4 flight controller. I hope this clears up the "Pam, Pam" thing (stepbrothers reference)
I have problems getten my rssi correct on my osd.
When i discover new sensors to rssi pops up and say its at 100%
In the osd it say 212%rssi.
The rssi in the mixer tab is set to aux 8 because thats a must in Flight1.
The rssi is working because when in walk away the rssi is getting less.
When i lower the offset in the input tab to -100 the rssi value is still 112%
I have connected the sbus to a rx and the inverted s port to a tx.
I have followed the correct instruction from mr bardwell get rssi on osd video.
Using flex firmware 180926 beta do you know whats the problem?
Here is a link to a write up on how to setup rssi via the taranis. Give these steps a try. oscarliang.com/rssi-ppm-channel-taranis/
@@TweetFPV i have done that and no succes. I think it has something to do because of i connected it to a flight1 board
That would be my guess. I don't know anything about flight 1. Sorry I can't be more help that that.
@@TweetFPV its oke😉 i am trying for 3 days now and still no luck. But i dknt stop till i get it right
Good luck. Pleas post up here when you get it figured out. Hopefully it could help someone else out.
So I got the synergy f4 fc like you do too and the R9 receiver it's the huge box receiver thing how do I solder it to that fc that says receiver?
Sorry, I dont have a synergy f4, and I'm not totally sure what box reciever thing you are talking about. Contact me on discord discord.gg/b2nUTux and post up some picture and I can help you out.
Does the inverted s port support F port...? Just got one of these r9mm I haven't installed yet.
Yes it does.
@@TweetFPV thx for your reply... ya got me flyin' Tweety... still confused... although fport is using a hardware inverted S port connection on Rx. Oscar, KnowItAll couple others have posts stating fport works on the un inverted UARTs and solves the inversion issue with F4 FCs. Sounds legit to me any program can be written to work through different types of serial connections. I'll give it a whirl on my next build.
Originally f.port was reported to solve the inversion issues but when it hit the streets in the small form rxs this was not the case. F.port does require a inverter on a uard with the exception of the r9mm and r9 slim+ rxs. Those have built in inverters to allow the fc to work with f.port/s.port when they don't have a second inverter on a uart. I hope that makes sense this inversion stuff is way too confusing. You have the r9mm rx so you can choose to use inverted or un inverted s.Port / f.port.
@@TweetFPV Makes sense to me... I'm on my 3rd build... 1. Tyro99 with R XSR lost :(... Had RSSI and Battery wich works without S Port on reciever and RSSI on OSD. 2. Tero Q215 XM+ RSSI 3. Tyro99 again with R9MM keeping things cheap til' I fly better. If or when I quit crashing I'll buy a better quad. I'm having lotta fun.
That's what it's all about!
How should the antenna be mounted?
Straight up and down is the most ideal. Not in a V shape like older 2.4g diversity setups. Some people run them straight but horizontally which works but when you turn you run the risk of pointing the null directly at yourself and can failsafe. These long range systems are very unforgiving with poor antenna placement.
that's the one thing I pulled this video up for and it wasn't here. :-(
Antenna orientation is highly debated topic.
TweetFPV my former comment came out harsher than I intended. It was a great video I just would have liked to hear your opinion on antenna mounting.
For optimal performance the antenna should be ran as straight as possible in a vertical orientation. Personally unless I'm trying to get the max range from it I make a compromise between rf performance and durability and I moun the antennas horizontally attached to one of the rear arms of my Quad. Recently I mounted one in the traditional "V" orientation on a race only Quad and have so far had no issues with it but have never had it out more than about 100 yards. I have a batch of antennas coming from frsky and will be trying those out.
Hey mate, which firmware did you flash on either the R9MM receiver and R9M module? The basic or the Fport one?
I'm not able to obtain telemetry back from the quad...
Thanks, cheers 👍🏻
I'm basically using all F. port with the R9MM receivers. The FW for the R9M module needs to be the same version as what you flash to the R9MM receiver. So basically any time you change you FW on either the TX or RX when you need to flash everything.
@@TweetFPV Where did you get the firmware for the 9mm? I can't find the Fport Firmware anywhere..
www.frsky-rc.com/r9-mm/
Go to accst then click the history download link at the bottom if you want Pre accst 2.x otherwise use V 19.02.01 there should be a fport fw file included.
Unless you are trying to use access. Then after you register and bind your reciever. Go into the receiver options and you select f.port through the software.
Hey so we're do I connect the wire on the board and which wire is it on the receiver?
Thanks 🙏 Confused nooby..
C
Sorry, I need a bit more info to help you out here. What FC are you using and what receiver are you trying to connect it to?
Frsky 9m mini
Hello friend, I have a MAMBA F405 mini and I want to install r9mm, the s.port I take it out of tx3 ?
Tx3 to the inverted s. Port on your r9mm it should be the bottom pad on the r9mm.
ok to clarify on the diagram from frisky they have Sbus out, Sbus in, separate Sport. Is your correction the blue wire the equivalent to the Sbus out or in or Sport ? Is the Green wire Sbus in or out? Thanks again. I am having issues with this. I cant get the Fport one wire to work despite CLI attempts etc
The SBUS in is for using receiver redundancy like if you wanted to run 2 receivers. Which FC are you trying to use f.port with? Depending on your FC using F.Port might not be possible with the R9MM RX. So based on the colors i used the connections should be as follows:
blue UART TX for s.port
green SUBS for RC signals
red Power
black Ground
@@TweetFPV Thank you. I am using a F7 Kakute, The fr Sky instruction sheet I have does not show inverted sport where you noted it. On my sheet from top to bottom with the channel holes on top Sbus_out, S.Port/Fport, GND, V_in, SBUS_in. I have finally got the radio and receiver to be seen by Beta, but I am only getting RSSI telemetry. I will sort that out next and I believe it has to do with my transmitter settings. I am bummed that the FPORT despite loading the new firmware and flashing and no issues with binding, the Beta does not see the fport. I did all permutations for CLI.
Thanks again.
@@diveflyfish you need to flash the fport fw to the r9mm. Then connect the s.port wire to the "telm" port of your fc or to any unused uart tx pad. Contact me on my discord server. It's a lot easier to help you there. This is a easy fix but pictures help. discord.gg/R6DUpF
@@diveflyfish oh and which rx are you using r9mm or r9mini?
@@TweetFPV R9MM OTA
never mind the link, but from the color code you used to the receiver and then to the fc you reversed what you called them, you set up the fc as you called them in hookup to the fc but it shouldn't have worked when you powered the receiver?
he connected the sbus and inverted sport wires incorrectly, but at the end it looks like he re-soldered the blue and green wire
I have two questions on the R9 mm RX do you use ground power and S bus? I did it that way and it won't bind with my receiver r9m module also frsky XM Plus RX I flashed mine an AUX 12 is active 4 RSSI but on betaflight CLI my Merica 5 inch it won't let me switch RSSI channel to 16 on my mobile device when I hit save and reboot they kicked me out and says USB is disconnected and when I try to change RSSI on the configuration tab to aux 12 and save it when I refresh or go off that tab and come back it's back to disabled what's up with this thing? The FC is a Aio running siskin 32 bit esc
For the RSSI issue i have seen this when you have "analog RSSI" enabled in the BF config tab. Disable that and see if you can change RSSI to AUX 12 in the RX tab.
I usually connect my R9MM RX in this manner. From the RX I use S.bus, power, ground, "inverted" s.port (on a F4 without a inverter on a UART TX pad) If you are having issues with binding my first recommendation is to re-flash firmware to your R9M module and your R9MM RX. also every time you update FW always re-bind your setup even if it seams like i still have a bind.
I hope this helps you out. if you have any more questions please let me know.
I have a mamba FC. Connect the wire inverted s.port to an uart as you did? thank you
Can you provide some more info? What fc are you using and which reciever
@@TweetFPV mamba mkv705 and the r9mm
I think you ment the mamba f405 mk2?
If that is the case and you have the mamba f405 then take the inverted s.port in from the r9mm (bottom pin) and connect it to uart 3tx you don't need soft serial. Just select smart port telemetry in betaflight ports tab on uart 3. Select telemetry in the config tab and hopefully that will work. If it does not you might need to do some work in the cli to change telemetry inversion.
@@TweetFPV Thank you very much friend. very good
Please tell me where you got that small vise fir soldering thanks
I found the model on thingiverse.com search for vise and it's one of the top results.
@@TweetFPV Thanks found it. My son's going to print one for me.
inverted s port in sbus?
Is it possible to do Fport on this receiver by disregarding the Sbus pad and just hooking it up with only the "Inverted Sport" to a TX on F4 board?
Did you ever find out?
Yea that should work.
@@TweetFPV Thank you Sir.
Hi there, what firmware is the R9MM running in this video? Normal firmware or the fport/sport firmware? Thankyou
Yes normal sbus/s.port fw
@@TweetFPV you're a legend, thankyou for replying super quick!
Believe this or not but apparently the wire I was using for a signal wire was broken internally replace that wire and it updated now I need to know how to wire them in hopefully just using power ground S bus or do I use s port? I flashed them on the S Port wire
Power ground and sbus. If you want telemetry as well then you need to connect power ground sbus and s. Port.
What fc are your running?
@@TweetFPV on the Merica it is a F4 Aio running siskin 32 bit eSC
@@TweetFPV on my sparrow it is hglrc F3 evo
And dshot 1200
Can I put it on a LAL3-F411 Flight Controller? I am a littlebit confused because of the UART on this controller.
Yes it's possible but you may need to forgo having telemetry.
@@TweetFPV Thanks, so I dont have telemetry? I am a completly beginner and I am german so my English isn't that good.
Any flight controller can use the r9 system because all flight controllers have the ability to use sbus. Sbus is just the control signals from your radio. The telemetry aspect is a seperat signal called smart port and is the communication from your flight controller back to your radio and requires a seperate uart. Telemetry is useful for pid tuning and Vtx adjustment but all these functions can be done through the betaflight osd without the need for telemetry. Typically f4 flight controllers especially 20x20 ones lack extra uarts to use sbus and smart port.
@@TweetFPV Thanks, you helped me a lot.
Hey there.. How do I connect this to a Helio AIO board? I am new to this Fport Sport concept.
And I see that you said vertical orientation is the best for range, right? Didnt you have a 3D print where you could mount the antenna, similar to immortal T?
Which Helio board are you trying to use? There are a bunch of designs out there that work. Check out tinigiverse and find something that will work for your frame.
@@TweetFPV I am using Helio Spring AIO board. Also, I got the body 3d printed. WHat can I use for antenna tubes as I dont have them now?
You could probably get away with using cut zip ties and heat shrink untill you get your antenna tubes.
As far as your connections go you have a "sbus" pad and a "s.port" pad on your fc. Just solder the respective wires from your rx to those pads and you should be all set.
TweetFPV yes there is sbus and sport both available. So just simple wiring, right?
Yep. Btw what rx are you using?
i have the same set up but my rssi only read to 12 rssi no matter how far i fly just blinking 10 to 12
You most likely don't have rssi setup properly in your radio or betaflight.
yeah i followed this one guy on setting up r9m and he does not know whats going on
i did all this and now it just blink low number on my osd th-cam.com/video/hcTIBMDUyAU/w-d-xo.html
h, what I'm missing. I have no telemetry apart from RxBt and RSSI after Discover new sensors. I've installed an R9 MM with latest firm FLEX_20190201. and OpenTx 2.2.3 on my Taranis Qx7. The channels are working great. The problem is the lack of sensors in the telemetry
Did you flash the r9m and the r9mm with the same fw? If so did you re-bind the two after fw flashing? Do you have telemetry selected in bf config page? Do you have the correct uart selected for smart port telemetry in the bf ports tab? Which pin are you using for smart port on the r9mm? Which flight controller are you using?
Thank you for your fast answer. My FC is a HAKRC Flying F4 v3. I have telemetry selected in BF. I have flashed FLEX_20190201 on R9 MM and R9M_FLEX in the TX module. I'm going to check the rest and back to you later. Thank you
Re-bind again after fw flashing. I dont have uart selected because I'm using F.port. Is it necessary? I'm using the S.PORT/F.POT pin on R9 MM. The result is the same, i.e. only RxBt and RSSI after Discover new sensors.
Ok so your using f.port. Are you connected to a uart tx or rx? Also which pad are you connected to on the r9mm? You should be connected to the bottom pin (inverted s.port) and to a uart tx on the fc.
I was connected to S.port/F.Port. I changed to Inverted S.Port and re-bind (just in case…). Now I've lost the receiver channels. damm :(
I don't know what's going on I tried to flash this piece of shit with a s port / fport wire and with sbus out and keep getting the same message " FW update error bottom pin no resp" now what do I do throw it all in the garbage? I know that asked for it works because I updated my XM plus receivers and they work I have a R9 Mini and a R9mm and have the same problem on both I updated them once but then the mini won't bind with my r9m module any help? Or off to the garbage can because this isn't fun anymore
what AWG should I use?
Really any gauge would work. I typically use 28-26 AWG for low current things like this. amzn.to/3jpmzhP
How do I get Rossi in the osd with this reciever?
His RSSI signal is showing up on AUX 12 which equates to CH 16 - in the receiver tab he needed to indicate RSSI is on channel 16 (AUX 12) and then in the other tab where you configure what you see in OSD have it reflect RSSI and it will show what is being output to channel 16.
Thx for the reply
I will try that when I get mine
Thanks
Yes this works with the newer firmwares. It didn't when these recievers first came out. And I find that it take a couple of seconds after startup for the rssi to "come alive" in my osd.
Any reason aux 12 is full? mine is the same, is that an issue?
Aux 12 (or ch16) is where the rx is giving betaflight rssi. You can choose to use that as your rssi value source for your osd but the scaling tends to be off, or you can choose to send the rssi from your transmitter back to bf on an aux channel for betaflight to use. I find that the one from the transmitter back to bf via an aux channel is a bit more accurate.
@@TweetFPV wow thank you for the quick response! i have one more question. im about to connect my last wire the "inverted s port" how do i know which tx to connect it to? im looking on my fc the cl racing f4 and i can only see a telemetry pad. Will clicking smart port in betaflight on the wrong uart brick my fc? i guess another question would be, How can i locate where my uarts are?
Wire the s. Port pad from the rx to the telemetry pad on the fc. The clf4 was designed with an inverter for smart port telemetry and should work with the normal s.port signal.
Locate your uarts using the mfg pinout for your fc
Hoping maybe you can help me, I have tried repeatedly to update a R9 mini and i keep getting a “Firmware update error module not responding” message from my Taranis X9D+. I have tried 2 different Mini 9’s same error message??? Can anybody help?
Sure. What pins do you have connected from your r9 mini to you Jr bay on your x9d? Also which fw are your tryinb to flash and what version of opentx do you have on your taranis?
Does the r9 mini leds light up when you try and flash it?
TweetFPV i have the S. Port going to the bottom pin then ground then power. I have tried the newest firmware 190201 including the Flex. I have 2.2.4 open tx. Yes the lights do come on but even that took awhile.
When you select the fw in your taranis are you selecting flash s.port or flash external module?
TweetFPV external module. It doesn’t give the option to flash S port.
Just checking, are you soldered to the second from the top pad on the r9 mini? So the middle 3 pads?
I’ve got a crocodile 7 with the r9mm and I can’t figure out what the fuck is wrong... it came with only 3 wires connected to the r9mm and I think that might be the problem but idk... I’ve tried everything I can think of...
Okay trying to flash the R9 mm rx I use voltage in, ground,,, the last one do I use sbus or s port/f port? Both ways I tried keeps telling me that it's not reading the bottom pin I have a qx7 with the smart part on the front and when it goes into the firmware it says flash external module or flash s port so what's supposed to work I did it once before and it worked. I don't know why please help otherwise $1000 worth of birds goggles and transmitters are going to be smashed up with a hammer
Try power, ground and s.port. Connect to the smart port connector on the bottom of your x7 (next to the USB port) select flash external module. If that doesn't work try selecting flash s.port. If you have a older x7 some of them made you flash the rx through the pins in the Jr module bay like the x9d radios do. Do this with the r9m removed from the radio in either case.
I'll try it tomorrow if I keep doing it today I'm going to hit it with a hammer
Again thank you
Haha yea I've been there. Sometimes it's good to take a break before you break.
First!!
I think you are the first person to say first in any of my videos!
TweetFPV hah lol
Well there's a first to everything
+1👍
R9m mini
Check out this video. It should answer most of your questions. th-cam.com/video/dzZRv24u1mg/w-d-xo.html
you confusing Sbus and inverted S.port. Oh. now i read the description avobe. this is critical you should not keep this up.
This video has helped out a lot of people and it will stay up.
inverted s port in sbus?
My board has a rssi tab is that for telemetry?
No, the rssi pad is for a along rssi not for telemetry data transmission.