This was EXCELLENT. About to do this on my Jumper T-Lite. Bought that and an Iflight BNF with FrSKy R-XSR and didn't know about the caveat that the Jumper is compatible with FrSky receivers but only with old firmware. Not happy about that, but you've given exactly the info I needed. Perhaps update your tags on this video with Jumper T-Lite to help future T-Lite purchasers. I found this in a very roundabout way through a forum. Thank you sir!
Thanks Jonathan! Just remember if you plan on updating a Jumper R1 receiver, as I stated in my pinned comment " I mistakenly updated the R1 receiver with R-XSR firmware in this video. The "Writing" and "Flashing" of the R-XSR firmware showed as "Flash Successful." I incorrectly took this to mean the Jumper R1 receiver had been successfully updated with the R-XSR firmware. It had not. It simply ignored the attempted update, even though the transmitter showed "Flash Successful." The receiver simply left the old version firmware on it. If you want to update your Jumper R1 receiver with FRSky firmware, you'll need to use XSR firmware."
Thank you man, you make my day ! I have done exactly the same before watching your video, but with the last ACCST firmware v2.0.1. With the version you use, it work like a charme. I juste have see the note on frsky site : "Note: Please update the firmware of all your radios, RF modules and receivers accordingly." It means the binding method has certainly changed ...
Your'e quite welcome! I truly appreciate you taking the time to provide your feedback! The new FrSky ACCST firmware release dated Jan 16th is as of this date not compatible with the multiprotocol module (MPM) firmware in the Jumper T16. MPM Dev's are working on a fix for this and will implement in future MPM firmware update. Video will be posted today (Jan 24th) on how to do MPM firmware updates.👍
Another great way to use the Jumper T16! 🤩I thought it was pretty cool you can update the Jumper R1 with the FrSky firmware. Although it makes sense, it just took me by (a pleasant) surprise! I did, however, make a mistake in this video. I mistakenly updated the R1 receiver with R-XSR firmware in this video. The "Writing" and "Flashing" of the R-XSR firmware showed as "Flash Successful." I incorrectly took this to mean the Jumper R1 receiver had been successfully updated with the R-XSR firmware. It had not. It simply ignored the attempted update, even though the transmitter showed "Flash Successful." The receiver simply left the old version firmware on it. If you want to update your Jumper R1 receiver with FrSky firmware, you'll need to use XSR firmware, not R-XSR firmware.
Agreed. That is good news indeed. Any chance you could confirm if the F.Port firmware will work as well. I have been using F.Port exclusively since is came out and would like to maybe try it with this receiver. I did notice that there is actually a Jumper R1F F.Port receiver now available as well. If the Jumper R1+ can be flashed to F.Port, then I don't much see the point of an additional receiver. I'm guessing there may be some issues with inversion on the R1+ using F.Port. IDK?
@@Dieselshroom You can update the FrSky R-XSR with F_Port firmware file using the T16 (which tells me you should be able to update teh Jumper R1F (F_Port receiver) the same way). Looking at the diagrams on Grayson Hobby, it appears you would not be able to update the Jumper R1+ with F_Port firmware as there is no F_Port connection for it). Thanks for your comment! I was unaware there is a new R1F! You taught me something today👍😀
Awesome video TMac! What do we gain by updating reciever? Will it help the range? I will have to update quite a few rxsr's if I start this process. Thanks again!
Hey Lawrence! If you look at the #:00 time hack mark on the FrSky site under Notes for the firmware update versions, you'll see a couple reasons: "Update Time Version Notes 1.Fixed the problem of abnormal high frame loss rate. 2. F.Port version included. 2019-03-13 190311 1. Fix the bug that sometimes can not bind to radios. 2. F.Port version included." Periodically, firmware updates fix "bugs" in previous versions, add new features, etc. Also, you may find you get a receiver which doesn't bind. It could be because it has the FCC version on it when you need the EU LBT or vice versa. You'll then need to update the firmware with the correct version. Its always a good idea when you get a new receiver to update its firmware with the latest version (see notes on FrSky versions above) or you may end up having a version on it which has "bugs" which have been fixed in newer versions. I hope this answers your question.
Hi Tmac, I am having some issues with the jumper r1 receiver. I followed your instructions to set it up and I managed to bind it using the frsky protocol but every now and then it just says sensor lost. I tried to flash the frsky firmware (2.1 r-xrs) and like you I thought it was successful but after reading some of the comments I realized that it wasn't. I am using a mamba mini and I double checked the connections and they are fine.I am using the ppm port as a softserial for the smart port and assigned a channel for telemetry on my t16 as you suggest in your check list. I don't know whether the r1 is faulty or I am doing something wrong. The quad flies ok but I don't dare go too far just in case I lose control of if... What could be the reason of this constant sensor lost? Thanks Tmac for this video 👍
Hey Luis, so what firmware do you have on it now? RXSR or XSR? V2.1 or pre-v2? What "FrSky protocol" are you using to bind with your multimodule? FrSky D16 or FrSkyX2 D16? If you "tried" to flash RXSR, as you said, it will have looked like it worked but id did not. So, if you haven't done anything else with it, it should still be on ACCST D16 protocol (pre v2). So, you should be using FrSky D16 protocol instead of FrSky X2 D16. If you're using the Mamba Mini Mk2, did you enable SoftSerial for the PPM pad as I did ion the video on Jumper R1 telemetry? Have you "Discovered New Sensors" on the Telemetry Page of your transmitter? These are all things you can check out
@@TMacFPV I guess it's the original firmware that came with the jumper r1 since I failed to flash the rxsr and until now I did not know that i had to use the xrs. I amusing the Frsky D16 protocol to bind the receiver to my T16. Yes, i followed your instructions in the video but I don't know what I am missing... The quad is flying in front of me at a few metres and my T16 says sensor lost several times. It seems to recover connection and then again gives you the warning sensor lost. You can see that the battery voltage desappear from the screen and then comes back. RSSI seems to be more stable and there is no warning 🤔
If the transmitter and receiver are too close, this will happen. Also make sure your antenna on both transmitter and receiver are oriented properly for good transmission/reception. This can also happen if the quads antenae ends are pointed directly at the transmitter. These are called "null points." The transmission from the antennae actually comes out the "sides" of the antennae
@@TMacFPV I think I found the culprit! I checked for continuity and one the antennas was damaged. I replaced it, repositioned them as you suggested and I did a fine tune. It seems to have done the trick. I am wondering if it will be worth updating to the xrs firmware or just leave it like this... What you think? Thanks for your help Tmac👍
@@luismanchego6856 Outstanding!🤩 Great work!💪Leave the firmware the way it is. Here's my philosophy on firmware updates (ANY firmware updates to include Betaflight, OpenTX, receivers, Multi-protocol Modules, etc.). 1. Is the firmware update you're thinking of doing a "fix" for a problem with your current firmware or a "feature enhancement?" In other words, research what the firmware update provides other than a new number designation. 2. If it's a feature enhancement only, how bad do you want this feature? Is it a lot better than what you have? Is it worth your time and effort to update? If you decide to update any firmware for any reason, do your best to save a backup copy of your current firmware in case something goes wrong. Now, having said all of that. What would be the added benefit of you updating your receiver firmware? Stuff to think about🤔
Has anyone been able to get un-inverted f-port (to use with an F4) out of a Jumper R1 like the xsr/r-xsr, or do you have to bite the bullet and get an R1F?
Hello from across the pond TMac I have purchased a Jumper T16 pro with the following Rx's ..... the only way i can bind to them is selecting FHSS on the Tx can i receive any telemetry from any of the Rx's below ( i would really like to have at least the Rx battery voltage for my glow engine aircraft & would like the lipo battery pack voltage for my electric helicopters etc plus the Rx's signal strength would be good to know ).... do i need to flash them to a FRSKY protocol if yes how do i do it or do i need to set my Tx jumper t16 pro to a different protocol setting..... please forgive me TMac as i am coming back into the hobby after a 15 year gap and things have changed a lot since my old futaba 35Mhz long wire setup but i am learning all the time due to people like you TMac thank you so much plus they say the SF810 is 8 channel but one of the slots is taken up by the battery connection what is the best method to share the battery slot / channel ? ...... all the best from Ian in England Jumper SF810 8CH Full Range S-FHSS Jumper SF610 6CH Full Range S-FHSS Jumper SF410 4CH Full Range S-FHSS Jumper SF410 Mini 4CH Futaba FHSS
Hey Ian! No worries friend, I'll do my best for oyu. Here we go: Just looking at the description of these S-FHSS and receivers on the GetFPV site, I do not see any mention of them being "telemetry-capable." I do not have any experience with this type of receiver, however, S-FHSS is the protocol that they use and that is the protocol you need to use on your Jumper T16 transmitter to bind them. Protocols used by the Jumper T16 multi-protocol module can be found here: www.multi-module.org/using-the-module/protocol-options and by going to this site and clicking on the S-FHSS protocol and reading the protocol description it states that protocol is NOT telemetry capable - see: www.multi-module.org/using-the-module/protocol-details/sfhss . The Jumper R8 IS telemetry-capable and should be bound using FrSky D16 protocol. See bind procedures and description at Grayson Hobby site here: graysonhobby.com/jumper-r8-16-channel-receiver.html . This info should get you headed in the right direction👍😀
@@TMacFPV oops.... i know what thought did now "Followed a muck cart, and thought it was a wedding" I guess i will now purchase some Jumper R8 receivers thank you for the links and your help TMac
I'm guessing this works with the hobbymate/hobbycool d16 rx. But can you confirm is it R-XSR or XSR firmware to use? On the unmannedtech website it says XSR.... Thanks for the video keep up the work
Wait, at 1:39 are you saying that one can use not only the XSR but also the R-XSR firmware? This is important to me, as there is pre-2.0 ACCST F-port firmware for the R-XSR, but not for the XSR.
In both the description of this video and my pinned comment I state "I mistakenly updated the R1 receiver with R-XSR firmware in this video. The "Writing" and "Flashing" of the R-XSR firmware showed as "Flash Successful." I incorrectly took this to mean the Jumper R1 receiver had been successfully updated with the R-XSR firmware. It had not. It simply ignored the attempted update, even though the transmitter showed "Flash Successful." The receiver simply left the old version firmware on it. If you want to update your Jumper R1 receiver with FRSky firmware, you'll need to use XSR firmware." Regardless, F Port firmware will not work on non-F Port receivers. Jumper R1 is non-F Port. As you mentioned the other day, that's why they came out with Jumper R1F (F Port).
@@TMacFPV I see, thanks for the clarification. Sorry I didn't catch that. The whole situation gets confusing lol. Just got my first rig on ELRS and I think i'm going to continue migrating as I need more rxs.
Just wondering, I have the new Radiomaster TX16s, is the process the same for that radio or are the external module pins different than the old Jumper T16 used in the video?
First of all congrats!👍🤩Should be EXACTLY the same since the module bay on each is compatible with the same modules (standard module bay), therefore the pins must be the same
Great Video like always. I have the Problem of loosing Telemetry after 30 Meters, with Always good range and full RSSI with Jumper R1. Dies it help to flash the Firmware ?
No. Jumper does not have its own firmware and the latest FrSky ACCST firmware is not currently supported by the T16 multi-module (FrSky made it so). This may change in the near future. What "telemetry" are you losing if "RSSI" is full? Here are some possibilities: Do you have telemetry setup correctly per ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-dJI4E36fXbg.html ? Also, you shouldn't have to do this (since its not a genuine FrSky receiver), but you may try frequency tuning it using procedure here studio.ru-vid.comPMckTYrLdvM/edit with additional info here www.multi-module.org/using-the-module/frequency-tuning . And the last one I can think of is do you have the latest firmware on your multi-module? ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-EJx9mz-DI_g.html
Thanx, i will try all of it. So latest Firmware ist 2.1. I think from March. You say this is not working on Jumper R1. Which Version ist the latest working FW. Thanx for your time and stay healthy.
@@bjorndestree8496 I said the latest FrSky ACCST firmware is not working on the jumper T16 multimodule. The latest ACCST firmware that works with (currently) the multimodule on the Jumper T16 (and Jumper T12) is any of the FrSky R-XSR firwmare versions lower than 2.0. The R1 should have come with the correct version of the ACCST D16 firmware. If you updated it with FrSky ACCST firmware version 2.0 or later (newer), as of now, it will not work with the Jumper T16 or t12 multimodule. It may work soon however with upcoming multimodule firmware release. I do not know when the multimodule firmware released will happen. if you require the older version of teh ACCST R-XSR firmwar eto re-flash your R1 receiver (because you previously "updated" it with the newer FrSky firmware version 2.0 or later) than I have made it available to you through the following link on Google Drive. Threre are 4 files in this folder. 2 are the "regular" ACCST D16 for both FCC and LBT and the other two are FCC and LBT for F-Port. You're welcome to download any/all of these as I do not believe they are available any more on FrSky site. Download and use at your own risk. I am not responsible for the upkeep of this firmware nor its use by anyone. drive.google.com/drive/folders/1RqBmbefbnZ6u7tiVGMMg7HmR5dNivm_u?usp=sharing
@@TMacFPV Hi, thank you for your excellent contents. I did downgrade to older version that you said, but it did not bind with JumperT16 internal Multi-Module. What can I do? thank you.
Hi Mac, Great video. I sent you a PM letting you know that when I tried to flash the receiver the receiver did nit respond and therefore the update failed. Tried this several times and no luck. In my PM to you I included a photo of the wiring system that I used. Thanks, Sam
Sam, I got your latest email with photos. Your make-shift wiring connector appears to be wired correctly. I have no idea why it is not working for you. I've provided you with all the information I have (including checklists) regarding the setup of your receiver over the past several weeks. Perhaps the Beta 85X FB group you're involved with can help more. Good luck Sam, and happy flying!
TMac it’s frustrating say the least. By the way, I’ve tried the link to the check list five times now and I’ve still not received an email with the download link. Thanks again for all your help.
@@samavella8831 Check your other email folders such as "Promotions" folder or "Social" folder (or even Spam folder). Sometimes it gets routed to one of these. I just tried sending it to myself and it went to my "Promotions" folder. If you find it in another folder, drag and drop it to your Inbox. Then future emails from me will go to your Inbox.
TMac, a new friend of mine in Europe updated his internal module firmware T16 (ran into some error messages) we got the errors to stop but he cant bind. Is there a particular T16 Internal Module Firmware Update just for Europe. If so where is it and what's it called ? He does have a newer transmitter that came with the bootloader. Thanks TMac Z
Hey Prozay! I don't own any DJI products, however, if you're talking about "off-the-shelf DJI drones", I believe you would need to replace the stock receiver on the DJI with one that uses a protocol within the T16 multi-protocol module and then that may have an impact on your video feed. please verify this information with someone who has more DJI experience than I do
No. the R1 receivers actually use the XSR NOT the R-XSR firmware. Additionally, you would need the F-port firmware that uses a version PRIOR to v2.xx. IF you can find the pre-v2.xx FPort firmware for the XSR, you can TRY to flash that to the R1F to see if that works. The X9D+ I believe has the similar pins in the back to flash receivers (not entirely certain of this though)
Will the jumper r1 f port version do Lua? I cannot get it to work. It binds and fly's fine super easy but have tried everything I can think of to get Lua to work and get nothing. Another question when using the rxsr shouldnt I be able to adjust vtx settings in my jumper? I can do pids and everything but the vtx control. It shows me the channel etc but I cannot change anything. It's a tramp protocol vtx.
Hey Tony. I've not used R1F myself, so I'm not able to personally confirm this or not for you. Regarding RXSR, what firmware version do you have on multi-module, what OpenTX version do you have (with LUA) and when did you get your RXSR and have you updated it's firmware (if so,with what version)?
@@TMacFPV regarding the rxsr following your videos of course, I updated the multi with 13053 and but for the rxsr I used the fport update latest version 191128 NOT accst the one right under it. As I recall I did have to do an uninverted hack on the rxsr and then set serial half duplex on. To make it work. And it all works with the acception of vtx. But I'm running bf 3.5.7 not sure if that makes a difference. At this point it's just one of those things I want to know if I did something wrong in my setup. Thanks much for always responding.
@@RubyS.1 Tony, not sure if you 've seen it or not but here's a video on BF Lua Script which explains you need to have BF Lua 1.4.o or greater for Jumper T16 (don't know what version you have): ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-z9l0fqFrILA.html Your RX firmware and Multimodule firmware are good. So, next step is OpenTX firmware version update? BF LUa Script version update? Betaflight update? I held off on updating from 3.5.7 for a long time myself (I fly micros mostly and was hesitnat to go with 4.0 or higher). I am currently running 4.1.1 (latest version for that FC) on my most recent micro build (Rattler) and 4.1.2 (latest version for that FC) on the build prior. I'm using default PIDS on both! They fly great! I used to have to adjust PIDs and filters with 3.5.7. Don't even need to do that anymore with my 3 inch builds running 13-15xx motors. Hope one of these things helps you out.
I would not recommend updating your receiver firmware as this is most likely NOT the issue. However, if you do update it for some reason, do not use R-XSR firmware as this receiver is more if an XSR clone (not R-XSR). Check to make sure you're using the correct protocol for your internal module (protocol FrSky, subprotocol D16). Try using the User Manual instructions for the RadioMaster R161 receiver (same type of receiver as Jumper R1) that you can download from "Download" section here www.radiomasterrc.com/
Hi, I updated the firmware three times, now it does not work anymore and I'm blocked on the FCC version without Fport. When I try to flash the two leds flash for a while then I got a short beep and the message: device not responding. Any ideas ? Thanks.
Hi there . I was just wondering . I do all the steps as in the video . Only one difference is that my t16 does not offer to flash when i go into the firmware I only have options to copy ,delete, Rename . is there a step that I am missing? Also it could be that I am trying to flash the flsky R9 MX though in theory the steps should be the same. can anyone help me please ?
You mean FrSky R9 MX, not FlySky, correct? FrSky R9 MX is an ACCESS protocol receiver. I believe T16 does not work with ACCESS protocol. This could be the reason you are not able to update the FrSky R9 MX receiver firmware through the T16 transmitter. For the protocols that T16 multimodule supports, please see www.multi-module.org/basics/supported-protocols
@@zatbr1 I am not familiar with this receiver, however, Per the FrSky site www.frsky-rc.com/r9-mx/ the R9 MX uses ACCESS protocol firmware only, which once again, goes back to my previous reply
@@TMacFPV thanks. Though on the frsky website one can download 3 firmwares for it. Flex access and the one already on it. Just thought I was doing flashing wrong. I shall keep looking. Thanx for your input.
If you look at the #:00 time hack mark on the FrSky site under Notes for the firmware update versions, you'll see a couple reasons: "Update Time Version Notes 1.Fixed the problem of abnormal high frame loss rate. 2. F.Port version included. 2019-03-13 190311 1. Fix the bug that sometimes can not bind to radios. 2. F.Port version included." Periodically, firmware updates fix "bugs" in previous versions, add new features, etc. Also, you may find you get a receiver which doesn't bind. It could be because it has the FCC version on it when you need the EU LBT or vice versa. You'll then need to update the firmware with the correct version. Its always a good idea when you get a new receiver to update its firmware with the latest version (see notes on FrSky versions above) or you may end up having a version on it which has "bugs" which have been fixed in newer versions. I hope this answers your question.
Any FrSky ACCST D16 firmware version PRIOR to FrSky 2020-01-16 ACCST D16 v2.0.1 will work with Jumper T16 multimodule. Its just this last Version 2.0.1 (and later when that happens) which will not work with Jumper T16 as of now (dev's are working to see if they can come up with a fix for it). You can download a previous version of the FrSky ACCST D16 firmware for the R-XSR at: www.frsky-rc.com/r-xsr/ Of course, FrSky ACCESS protocol will not work with Jumper T16 either.
@@TMacFPV You miss understand my question. Can we replace the firmware on an FrSky receiver with the firmware from a Jumper receiver ? We could do away with ACCST V2 if that is so...
@@SomeTechGuy666 To my knowledge Jumper doesn't even make its own receiver firmware, its being relying on FrSky ACCST D16. To do away with ACCST V2 on an FrSky receiver, just upload the previous version of the ACCST firmware. Someone I spoke with just yesterday did that and said it worked great
@@SomeTechGuy666 ok, R1 & R8 too (I believe) use ACCST D16 firmware which has been "open" for quite some time. FrSky has decided to make it's newer firmware more closed and incompatible with non-FrSky transmitters. If you find Jumper-unique firmware please share your information with all of us
Sorry to hear you're having issues after flashing your R1 receiver. If you flashed it with the latest FrSky ACCST D16 v2.1 firmware, you'll need to bind it to your transmitter's multimodule (assuming you have a transmitter with a multimodule) using FrSky X2 protocol (one of the options in the binding menu).
Not sure what you mean by V2 of the T16 Pro, however, yes, the pins in the module bay are the same (its the same standard module bay). You do not "need" to update your receiver firmware unless you have a specific reason to do so. This video is showing you HOW you CAN do it if you need/want to for some reason. Also, if you're talking about updating firmware for an R1 receiver, in this video I show using R-XSR firmware to do so. That was a mistake. It looks like it updated, but it actually did not. It indicated it did but it really just ignored the R-XSR firmware update and left the old firmware on. To update the R1, you need XSR (NOT R-XSR) firmware.
i got the R-XSR about a year and just decided to use it in the Diatone R 349 just thought it would be easier before i put it in to do it rather than finding out i had to later...
put Jumper R1 firmware on R-XSR? There is no Jumper R1 firmware. It uses FrSky ACCST D16 protocol firmware version less than 2.0. 2.0 version didn't work with T16 Multi-protocol Module. Just recently with newest Multi-protocol Module firmware, version 2.1 ACCST D16 firmware works with Multi-protocol Module (see multi-module.org)
