Hey everyone.  
I've been searching the web for an answer to my problem and have yet to either find an answer or understand it for that matter.  
  
My question is: If i have an R9M Module tx which is labeled ACCESS  and an R9 rx which is labeled ACCST is there anyway to pair the two together?  
My controller is Jumper T16 Pro  
My Module is R9M ACCESS (Red EU version)  
My Reciever is R9 900mhz (868mhz EU) ACCST  
  
Can i flash the module to ACCST?  
Can i flash the R9 rx to ACCESS?  
Do i need to do anything at all with the Jumper T16?  
  
I was sent the wrong item today and the guy on the phone told me i can flash the module to ACCST but from what i can find on the web it's all starting to get confusing. Also would i just use the ACCST firmware update from the website or do i need something else?  
  
Thanks in advance
MrTrendizzle

Yes, you can install the ACCST firmware on the R9M 2019 module no problem. Just download version 190117 of the ACCST firmware it from the following web page and flash the R9M_FLEX.frk file to your R9M 2019 module. Make sure you also flash the FLEX firmware to your R9 receiver as well.

https://www.frsky-rc.com/r9m-2019

I also forgot to mention that you need to ensure that you flash OpenTX to your T16 with the "flexr9m" Build Option ticked in OpenTX Companion. If you don't do that then your transmitter won't be able to communicate with the FLEX firmware on your R9M module.

(03-Apr-2020, 10:27 PM)SnowLeopardFPV Wrote: Yes, you can install the ACCST firmware on the R9M 2019 module no problem. Just download version 190117 of the ACCST firmware it from the following web page and flash the R9M_FLEX.frk file to your R9M 2019 module. Make sure you also flash the FLEX firmware to your R9 receiver as well.

https://www.frsky-rc.com/r9m-2019

So it really is that simple.  
  
I just move the R9M_FLEX.frk file to an SD card, put it in the jumper controller and flash the external module correct?  
How would i do that with the receiver? Do i need any new cables etc... as to be honest this is an entire new area for me. The controller/module i'm pretty sure i understand and i'm comfortable but flashing the receiver i'm stumped.  
  
Thank you for the very simple and easy reply. That has really cleared my head from the 100's of pages i've read today trying to grasp all of this.

(03-Apr-2020, 10:33 PM)MrTrendizzle Wrote: So it really is that simple.  
  
I just move the R9M_FLEX.frk file to an SD card, put it in the jumper controller and flash the external module correct?  

Yes, correct

(03-Apr-2020, 10:33 PM)MrTrendizzle Wrote: How would i do that with the receiver? Do i need any new cables etc... as to be honest this is an entire new area for me. The controller/module i'm pretty sure i understand and i'm comfortable but flashing the receiver i'm stumped.  

Assuming your receiver is the original R9, download version 190201 of the ACCST firmware from the following link and then flash either the R9_FLEX.frk or R9_FLEX_Fport.frk file to the R9 receiver depending on whether you intend to use the SBUS/S.Port protol or the FPORT protocol and associated wiring on your quad.

To flash the R9 receiver you use the connector in the JR module bay on the back of the T16. The procedure for how to do that is detailed below in Oscar's blog article. That shows how to do it using an FrSky transmitters, but the procedure is exactly the same on the T16...

https://oscarliang.com/flash-frsky-rx-firmware

Afternatively you can watch the following video by a member on here showing how to do it with the T16. This is demonstrated using an R-XSR and Jumper R1 receivers but the same procedure applies to the R9 receivers as well. You just connect the SBUS, 5V and GND pins from the receiver to the connector in the back of the JR module bay and then select to flash the firmware file to the external module (which is the receiver connected via the wires).

(03-Apr-2020, 10:52 PM)SnowLeopardFPV Wrote: Yes, correct


Assuming your receiver is the original R9, download version 190201 of the ACCST firmware from the following link and then flash either the R9_FLEX.frk or R9_FLEX_Fport.frk file to the R9 receiver depending on whether you intend to use the SBUS/S.Port protol or the FPORT protocol and associated wiring on your quad.

To flash the R9 receiver you use the connector in the JR module bay on the back of the T16. The procedure for how to do that is detailed below in Oscar's blog article. That shows how to do it using an FrSky transmitters, but the procedure is exactly the same on the T16...

https://oscarliang.com/flash-frsky-rx-firmware

Afternatively you can watch the following video by a member on here showing how to do it with the T16. This is demonstrated using an R-XSR and Jumper R1 receivers but the same procedure applies to the R9 receivers as well. You just connect the SBUS, 5V and GND pins from the receiver to the connector in the back of the JR module bay and then select to flash the firmware file to the external module (which is the receiver connected via the wires).

You have honestly been the single best person on the internet today for myself.

100's of pages just confusing me further and further and you managed to get straight to the point with clear precise instructions. I honestly can't thank you enough. I've had my drone partially built for the last year and only just gathered the final few pieces to get this in the air along with getting my operator licence etc... last night.  
  
As soon as my radio turns up next week i'm going to be one happy guy finally escaping the confines of my house through my drone.  
I think i've just found that video on Youtube showing exactly how to flash the receiver. So simple.  
  
One last question tho?  
S-Bus, F-Port? What is the difference? I wired my receiver to the flight controller using A-E-T-R-U rather than a single S-Bus cable.  

Again, Thank you so much for all the answers to my issues.

No problem Oscar has taught us all well

It's better to use a serial communication protocol if you have the option. It has lower latency, carries more channels, and can handle telemetry data back to the transmitter.

1. SBUS/S.Port uses two wires for communication - SBUS for the RC Commands data from the receiver to the flight controller, and S.Port for telemetry data back from the flight controller to the receiver.
   
   
2. FPORT uses a single bi-directional communication wire that carries both RC Commands data and telemetry data between the receiver and flight controller.
   

What flight controller do you have? Maybe post a link to it and/or post some photos of your current wiring between the R9 receiver and the FC.

(03-Apr-2020, 11:28 PM)SnowLeopardFPV Wrote: No problem Oscar has taught us all well

It's better to use a serial communication protocol if you have the option. It has lower latency, carries more channels, and can handle telemetry data back to the transmitter.

1. SBUS/S.Port uses two wires for communication - SBUS for the RC Commands data from the receiver to the flight controller, and S.Port for telemetry data back from the flight controller to the receiver.
   
   
2. FPORT uses a single bi-directional communication wire that carries both RC Commands data and telemetry data between the receiver and flight controller.
   

What flight controller do you have? Maybe post a link to it and/or post some photos of your current wiring between the R9 receiver and the FC.

Ahh ok. I did have my rx wired up 1-2-3-4-5 to A-E-T-R-U but have no switched it to S-Bus out to X2 on the FC.  
  
I'm using the Naza m V2 which i believe dosn't allow telemetry because DJI and it's software or whatever. I did find out about Zagometry but it's end of life and the only person that ever sold it has said they have no more and won't make any more. I've had a look at trying to build it myself but can't find any plans online.  

This is my setup right now. I do need to plug the antenna back in but will leave that until i've flashed the rx.

Oh, wow. A DJI NAZA V2  I hadn't even heard of drones and FPV when that was released to market 

You might struggle to get any support for the NAZA on here if you run into problems because most (if not all) of us use flight controllers that run the Betaflight and iNav open source firmwares.

As long as the NAZA handles the standard SBUS protocol which I believe it does then it should just work, but I have no idea what configuration options exist for the NAZA. You will need to flash the R9_FLEX.frk SBUS/S.Port firmware file to the R9 receiver.

(03-Apr-2020, 11:54 PM)SnowLeopardFPV Wrote: Oh, wow. A DJI NAZA V2  I hadn't even heard of drones and FPV when that was released to market 

You might struggle to get any support for the NAZA on here if you run into problems because most (if not all) of us use flight controllers that run the Betaflight and iNav open source firmwares.

As long as the NAZA handles the standard SBUS protocol which I believe it does then it should just work, but I have no idea what configuration options exist for the NAZA. You will need to flash the R9_FLEX.frk SBUS/S.Port firmware file to the R9 receiver.

I've built this over the last year sucking up parts from all over the web super cheap.  
For example: My frame which is a diatone 550? I think... Cost £5. It's a little heavy but it's a good starter. I've messed around with some of those syma drone's and decided to build my own and ended up getting a few parts before figuring out the bigger i go the more expensive it became lol.  
  
Naza support is next to none besides what's already out there. I think i've come to the understanding unless i dive in to Tweensy? i'm not going to get telemetry or OSD working very well if at all.  
If this thing flies and does what it's supposed to do i'm thinking of building a much smaller 5" drone. I think the only reason i went for the NAZA was the baro/gps hold rather than having to feather the throttle all the time to keep it in the air without having to add a bunch of different modules together hoping i understand the software behind everything and using hopes and dreams to make things work together.  
  
Total drone weight is 2096g and if my math is correct i should have a 15 minute flight time using 80% battery capacity give or take depending on the load. I think i worked it out as full throttle for 15 minutes. I could be wrong tho and open for correction.  
  
My drone's full specs are,  

Diatone 550 frame  
Naza M V2 FC  
R9 receiver  
8000mah 120C 4S lipo  
Racestar 2210 1000kv motors  
1045 props  
Turnigy 30a ESC  
1 metric ton of LED's 

Jumper T16 Pro
R9M external Module

I think that's everything. I would like to upgrade the motors a little and get some wider flatter motors more for aesthetics than anything else.  
My next drone i'm thinking will be a smaller 5" zippy FPV drone. I do like the idea of crashing small bits of plastic in to the side of my house as i try and climb the wall only to fail and watch as my wife throws a tantrum because i'm spending more money on drone parts lol.

OK, so now I understand. This is going to be a mega beast of a copter with autonomous flight capabilities  I was originally thinking this was some kind of 5" but at over 2Kg it's clearly not one of those LOL.

Is that Diatone 500 the hexacopter frame or the reptile quad frame?

(04-Apr-2020, 12:25 AM)SnowLeopardFPV Wrote: OK, so now I understand. This is going to be a mega beast of a copter with autonomous flight capabilities  I was originally thinking this was some kind of 5" but at over 2Kg it's clearly not one of those LOL.

Is that Diatone 500 the hexacopter frame or the reptile quad frame?

It's a hexcopter. It's absolutely huge. I'm still debating if i should invest in a VTX and decent 4k camera. I've Frankensteined old Syma internals and the really terrible camera which connects to my phone via an app to get a video feed from the battery that came with the syma drone. It works. Not the best but atleast i'll be able to explore the countryside opposite my house while in lockdown.  

As you can see this is a rather large drone. Should hold up to the elements. I need to bolt the top piece back on but i need access to the rx.
From the tip of the prop to prop it measures 31 inches across. Not bad for my first ever build tho.
  

What a monster. I could use the top plate as a landing pad. WOW.

(12-Apr-2020, 05:47 PM)iFly4rotors Wrote: What a monster. I could use the top plate as a landing pad. WOW.

Hey if we ever see each other i'll gladly move the GPS out the way and hoover for some air to air docking. lol. It's so heavy and turns heads every time i've taken it out so far. My neighbors have had a tiny little thing buzzing up and down the road. I pulled mine out today to get a bit of practice and he was gob smacked that it even flew because of how much it weighs.

Very interesting...air to air landing   
Yeah, but a good landing for me means that nothing got broken when it hit the ground    (ha, ha).  

Even though your craft is heavy, it looks pretty powerful. So, how much payload do you think it will lift? 

I would be interested in seeing some FPV flight footage.