Frsky XM+ pulling my hair out

CurryKitten · November 19, 2017, 10:59:51 AM

It would certainly be useful to try binding it on another TX (as you mentioned) which will pin is down. You could try updating the firmware on your internal XJT module (although you shouldn't need to). Out of interest, what version of OpenTX are you running (again, shouldn't make a difference) but as I've just got 2 more XM+'s from Banggood, which I haven't tried binding to yet, it might be useful to see how we match up

Loopdreams · November 19, 2017, 05:02:06 PM

They bound straight away with my brother's Q X7. I'm using the latest Open TX as I updated it as part of my quest to get these things working. I did also update my internal module firmware but I think I'm going to try an earlier (but later than was on it originally) version.

Loopdreams · November 19, 2017, 05:13:52 PM

Success!

The latest version of the firmware on the Frsky site, whilst it still seemed to be broadly compatible with my internal module did not fix this particular issue but after some google sleuthing I came across some recommendations to try XJT_build161214.frk which doesn't seem to be on the Frsky site but which someone had attached to a post on RC Groups. Flashed that to my internal module and bingo!

English Turbines · November 19, 2017, 05:25:55 PM

Cool....So you have loaded (an older) version of Firmware on your TX Module which is NOT the latest but which works your XM plus RX which DO have the latest Firmware..?

I think that's what you said...?

:vulture:

Loopdreams · November 19, 2017, 05:59:50 PM

Yeah, that's about the size of it. I think there must have been an update to my particular module (EU but pre LBT) which isn't rolled into subsequent firmware versions.

English Turbines · November 19, 2017, 06:12:43 PM

Quote from: Loopdreams on November 19, 2017, 05:59:50 PM
Yeah, that's about the size of it. I think there must have been an update to my particular module (EU but pre LBT) which isn't rolled into subsequent firmware versions.

Yeah, that exactly what I was thinking....The meddling EU who need a special version of LBT Firmware to satisfy just them, while the rest of the entire Planet does not....

They have to justify their existence somehow I suppose.

Oh....and do the rest of your receivers still work ok now.....??????

:vulture:

AdamG · November 20, 2017, 09:36:23 PM

I don't understand why firmware designed for the specific rx in some cases simply won't flash, you get an error on the X9D. Iv'e had issues with FrSky rx firmware and find you have to just try loads of different firmware until 1 works. Not a great UX

English Turbines · November 21, 2017, 12:52:26 AM

Just watched a clip of a Z84 5kms out using an XM Plus....unbelievable, and it wasn't even that high up either using a standard Taranis antenna setup...

:vulture:

Schalonsus · November 21, 2017, 11:31:57 AM

XM+ has a lot of range, flown mine in the Viper Mini also to 5.5km and had 70% RSSI left. Just had to turn around because the picture of the 200mW 5G8 transmitter got worse
https://youtu.be/TtX9HzQ68IE

English Turbines · November 21, 2017, 01:37:50 PM

Quote from: Schalonsus on November 21, 2017, 11:31:57 AM
XM+ has a lot of range, flown mine in the Viper Mini also to 5.5km and had 70% RSSI left. Just had to turn around because the picture of the 200mW 5G8 transmitter got worse
https://youtu.be/TtX9HzQ68IE

Nice work (Karma given) using only 200mw...Not sure if you are using iNAV or not, but I thought there were basically two different systems for receivers regarding RSSI....3.30V and 5.00V..?
Inside iNAV it doesn't ask the question, so not sure how well their code works regarding RSSI....or how accurate it is as there appears to be no calibration routine either...but it appears to work ok.
In any event, clearly this tiny receiver has no problems with range whatsoever, which is why I want to try one.

Like the L9R it has no telemetry and I wonder if this is playing a part in its exceptional performance...?
Bit of a bargain really, even using T9 they are only about £12 each, with a compulsory next day Royal Mail delivery, which is a bit bonkers as it costs about £3.00..with no cheaper alternative.
The receiver is so thin and tiny, that burying it out on a wingtip should be easy on a small model.

:vulture:

Schalonsus · November 21, 2017, 02:17:34 PM

Thanks. I'm using iNav. I inject RSSI over SBUS channel 16 into iNav. Since i use microMinimOSD with MWOSD there is calibration function for RSSI. You start with TX close to RX and then turn off TX to get lowest value.
But it think now in iNav 1.8 there is also a calibration option.

English Turbines · November 21, 2017, 09:49:07 PM

Quote from: Schalonsus on November 21, 2017, 02:17:34 PM
Thanks. I'm using iNav. I inject RSSI over SBUS channel 16 into iNav. Since i use microMinimOSD with MWOSD there is calibration function for RSSI. You start with TX close to RX and then turn off TX to get lowest value.
But it think now in iNav 1.8 there is also a calibration option.

Oh, cool...yes, Im using iNAV too...Im a bit confused unless it's the FC your using that's different..?
I use the Omnibus F4 with its onboard OSD, are you using something different then..?

Yes, I also have loaded the channel 16 RSSI feed firmware to the XM Plus...I must try iNAV 1.8 now....lol.

iNAV is slowly improving, although its perfectly usable as it is TBH.

:vulture: