No Telemetry Values Showing? SOLVED! (Kinda?) YES!!!

[Old Swashplate]

Hey Guys,
I haven’t flown my helis this year, mostly my quads. So I noticed my telemetry wasn’t working on one of the helis. I was running OpenTX 2.3 with a X9E, X6R and a FLVSS. Also have two MLVSS. The radio will “discover” all three sensors but now doesn’t show any values. I’ve updated to OpenTX 3.2.1 and still no joy. I’m noticing an occasional, brief flash where the sensor value should appear (three dashes) like it’s trying to display something but it also did that before I updated to 3.2.1. I have a second heli that also has a X6R but with the FrSky FrESC32 and the telemetry still works with that setup as before. I’ve tried every possible combination (both of my X6R’s with all three sensors and the ESC) and I get nada from the FLVSS/MLVSS sensors. I did update my X9E internal module to V2.1.0 and the X6R’s last spring and everything seemed to be working then. Also I don’t have any problems with telemetry on my two quads w/iNav. I didn’t reverse the polarity on the MLVSS sensors and the FLVSS is polarity protected. I’d be surprised if all three sensors were defective or dead.....how bizarre. Any ideas?
Thanks, JW

 

[Old Swashplate]

FWIW I remembered I have a SPort Airlink S so I updated the FW on all three sensors this morning. Same thing, nada....

 

[Kilrah]

Maybe bound the receiver with "no telemetry"?

 

[Old Swashplate]

Maybe bound the receiver with "no telemetry"?

I had to rebind my RX’s when I updated them but I just went through binding them again to check. I tried both ways, 1-8 telemetry on and 9-16 telemetry on and still nothing. I also tried binding one of my extra R-XSR receivers for my quads both ways, same thing.

 

[Wayne]

Please make sure the sensors are plugged into the smart port, not the sbus port.

 

[Old Swashplate]

Please make sure the sensors are plugged into the smart port, not the sbus port.

Thanks Wayne,
I’m only using one MLVSS and I do have it connected to the smart port on my X6R. I’ve also posted this on the FrSky Facebook page and probably will also post this on RCGroups FrSky vendor section.

 

[Old Swashplate]

Since I have one of my quads “in for service “ after an unscheduled landing I tried the sensors with a R9 Mini and BINGO! They work! So apparently when I updated my 2.4 internal module and RX’s something didn’t load correctly. I did upload both the module and receivers to the latest FW but evidently the module and RX’s/sensors aren’t playing nice together now. Still it’s very odd the telemetry displays from the ESC. I honestly don’t remember trying the telemetry when I updated, probably just checked for proper servo movement. So now I get to try reloading the FW and see if that resolves the issue. If not I’ll scrap the 2.4 stuff and install R9 receivers on my helis.

 

[Konrad]

What version of FW did you try to put on your internal RF module. I hope you are aware that FrSky had a heck of a time getting the new ACCST v2 to work. (Many of these issues were around the telemetry) There are a plethora of revision that never should have made out into the public. Please make sure that the ACCST v2 is the latest ( I think this is now 2.1.0). Also you will need to update all RX that you want to use on ACCST v2. The FW on TX and RX need to match. ( I think you did this. But for a long time there were revision numbers that looked real close like 2.0.1. I see that FrSky has cleaned up their offering of the failed earlier 2.x.x FW)

 

[Old Swashplate]

Konrad I believe it was 2.1.0 but I’ll verify that later when I get home. This all started last spring when I installed my R9 module and was trying to install the FW for it...the enter/scroll button rolled up to “flash internal module” as I tried to push enter and I accidentally flashed my internal module with the R9 FW. ?? So I went ahead and flashed the “newest“ XJT FW for the X9E and was able to get it installed/working....or so I thought. I now see the history 170317 version but if I’m correct I can’t go back to that after upgrading to 2.1.0?

 

[Konrad]

My understanding is that you can always go back. To be clear FrSky finally has a working and stable FW with 2.1.0. If going to the effort of upgrading I'd stay with ACCST v2.

Not sure what you may have done. If you think you have a file misplaced, I don't think I'd be comfortable even on 900mHz until I knew what was going on.

I think Aloft can set you up with a clean sheet to work from. Heck, they might even start you off with ACCST v2.

(The only way I know to brick a FrSky radio is to burn up the voltage regulator in the Horus brand. And then the fix is just a few dollars, new mother board)

 

[Old Swashplate]

Hey Konrad,
I was able to load the ver170317 FW on my radio BUT....the only other FW for the X6R on the FrSky website is the “history“ ver180322 FW and those two together won’t bind. So I decided to start over, again. I went back and erased the 2.1.0 FW file on my radio and computer, re-downloaded 2.1.0, copied that to my radio a reflashed it, flashed a new copy of 2.1.0 on my X6R and it binds fine as before but still no telemetry values will display. I even tried one of my RXSR receivers this morning again but it’s the same thing, the RXSR FW is either 2.1.0 or the “history“ ver19112 and it only binds on 2.1.0 but no telemetry values will display. If I understand correctly the FW numbers/version are supposed to match (makes sense) and I’m not finding any FW with matching numbers except 2.1.0. So at this point apparently my XJT internal module is the problem since I get telemetry displayed correctly with my R9 module. ??‍

 

[Konrad]

And my last suggestion, are the switches #1, & #2 both down (off).
Yep, it is starting to look to me like an XJT problem. Check for broken pin solder joints on the mother board to the XJT module. ( These where a known issue with the JR radio, maybe not as the R9 works)

As the X9E doesn't accept the XJT module in its stock form, can we get a photo of how you installed it? With details on how the antenna is installed.

https://www.frsky-rc.com/wp-content/uploads/2017/07/Manual/XJT.pdf

P.S.
Are you aware that not all S-Port have the same pin call outs.

The G-RX8 receiver is NOT ready for the mass market

Maybe I'll just get one anyway despite the mixed reviews. :rolleyes:

forum.alofthobbies.com

 

[Konrad]

Here is how my XJT bay looks.

Now the external module bay was a very poorly thought out option by FrSky on the X9E. Aloft has a very nice practical retro fit.

X9E Module Bay Kit

Plug in a module without taking the back cover off!

alofthobbies.com

 

[Old Swashplate]

SUCCESS!! I tried going back to the previous OTX 2.2.4 I was using and that didn’t work either. So as I’m thinking about it I decided to just do a factory reset and sure enough, it did the trick! I didn’t even care about trying to save any of my settings/models as I’m only using two helicopters and two quads for now. No clue what was causing the problem but it’s fixed and that’s what counts. I’ve always said, I may loose a battle or two but I always win the war!

 

[Old Swashplate]

Konrad it looks like we both used the same beaver to mod the case....? And don’t ask about the blue tape on the main display ribbon cable....sometimes ya do what ya gotta do.

Here is how my XJT bay looks.

Now the external module bay was a very poorly thought out option by FrSky on the X9E. Aloft has a very nice practical retro fit.

X9E Module Bay Kit

Plug in a module without taking the back cover off!

alofthobbies.com

View attachment 5120
View attachment 5121

 

[Konrad]

Wow, it looks like you fully populated the switch board!

 

[Old Swashplate]

Yes sir. I run the Spirit/GeoLink units on my helis so between that and the quads with iNav/GPS I pretty much can use all I have. I use a few for goofy stuff like timer resets, backlight and volume control. Damn radio has become a “hobby within a hobby“ and I swore i wouldn’t go down that rabbit hole....but here I am, killin it.