A self-help group for anyone having problems or indeed anybody that can help with FrSKY products.
Hi,
I've tried searching but cannot see an answer to the problem I'm experienceing with a secondhand Horus X10S TX that a friend has just purchased, but does not appear to be working correctly.
In brief summary - its a Horus X10S with standard IXJT RF module. Seller apparently upgraded the OS to OTX 2.3.15 prior to the sale.
On Model setup page the RF selection only has OFF or ISRM options - no IXJT ??
On the SYS info screen the Internal RF Module shows --- so it seems to not recognise the IXJT RF module ?
I've tried re-flashing the RF with IXJT_2.1.6. Flash works normally and states its successful but no difference.
I've tried reloading the complete OTX 2.3.15 - no difference.
I have read that some upgrade RF modules are ISRM but were labelled as IXJT 2.0 so I tried to flash it as an ISRM but the flash is unsuccessful so I'm reasonably confident that it is an original IXJT - also the aerial connections look to be undisturbed, etc.
I'm minded to recomend he goes with an ISRM upgrade as I did, but would be happier if we could at least see the radio working first before he spends more money on it. He has a Taranis X9D+/ACSST setup at the moment so this was supposed to be a first step, then ISRM/ACCESS upgrade in due course.
I hope someone can point me in the right direction as I'm stumped as what to try next.
Thanks
David
Hi,
Just a quick update of progress this morning as it has been annoying me, and this might help someone else.
I rolled back the OTX to the one on the FRSky downloads page for the X10S which is OTX 2.3.9 and it now all magically works, sees the IXJT module and I've successfully bound and tested an RX so all is working....a very big relief!!
I'm wondering if the latest OTX versions will only work with ISRM modules? Would be good to know at which version (between 2.3.9 to 2.3.15) this happened or if there is some other issue at work here.
Has anyone else run the latest OTX on legacy IXJT Horus X10S?
Rolling OTX back to 2.3.9 resolved it in this instance so I'm not minded to probe any further.
David
