So I Bought A Horus

Fair point but I'm not sure it would have changed my attitude at the time.

I like the neat and tidy menu driven approach which Futaba and the look-a-like FrsOs gives. I really want FrOs to work but it does seem to lack some of the functionality of OpenTX. Only having access to the first 100 items of the Amber voice pack is an example. Poor or no implementation of LUA scripts is also an issue.

I take your point about having more granular programmability, especialy if more use is to be made of telemetry data.

The desperate truth is that various Frsky bugs around the S6R are going to force me into using OpenTX. I may have more questions!

AlanF wrote: I like the neat and tidy menu driven approach

You will hate OpenTX

AlanF wrote: Only having access to the first 100 items of the Amber voice pack is an example.

Does FrOS allow you to create your own sounds? I realised a long time ago that the sound packs that are available for OTX only include a few sounds that I want to use and that some of those I do not like. So I now create my own custom sounds. My 'sound pack' probably has about 10 files because that's all I use.

AlanF wrote: Poor or no implementation of LUA scripts is also an issue.

Are you sure you need LUA scripts? I've seen some nice work with LUA but never felt the need to learn how to implement it - too much hassle for not a lot of advantage.

AlanF wrote: Frsky bugs around the S6R are going to force me into using OpenTX.

You could look at this two ways:

1. Stop messing around with stabilisers. You don't need them.
2. Stop procrastinating and change to OTX. You will have a steep learning curve and initially regret it, but once you get your head around it all of your niggles about FrOS will be forgotten.

MikeSeale wrote:

AlanF wrote: I like the neat and tidy menu driven approach

You will hate OpenTX

That's my fear- once I've satisfied myself that I can readily revert back to FrOs I'll switch over.
There are some aspects of OpenTX that I like in terms of its use with Companion. Archiving and transfer of model setups for example, allowing use of a keyboard for naming items.

AlanF wrote: Only having access to the first 100 items of the Amber voice pack is an example.

Does FrOS allow you to create your own sounds? I realised a long time ago that the sound packs that are available for OTX only include a few sounds that I want to use and that some of those I do not like. So I now create my own custom sounds. My 'sound pack' probably has about 10 files because that's all I use.

The directory and file structure is the same for both I believe. FrOs will treat wave files in the same way as OpenTX it's just that the implementation of the FroS selection menu is limited to 100 items whereas OpenTX gives to access to everying thing on the SD card - I think!

AlanF wrote: Poor or no implementation of LUA scripts is also an issue.

Are you sure you need LUA scripts? I've seen some nice work with LUA but never felt the need to learn how to implement it - too much hassle for not a lot of advantage.

The LUA scripts are required to setup and calibrate the S6R and are required for FrOs and OpenTX. Its just been hard coded into FrOs - and doesn't work!

If I don't use the stabilisation I can run the S6R as a normal Rx and everything is ok which is probably the sensible way forward at the moment.

AlanF wrote: Frsky bugs around the S6R are going to force me into using OpenTX.

You could look at this two ways:

1. Stop messing around with stabilisers. You don't need them.
2. Stop procrastinating and change to OTX. You will have a steep learning curve and initially regret it, but once you get your head around it all of your niggles about FrOS will be forgotten.

Well I have plenty of time now. Once I've satisfied myself that I can easily revert back I'll dive in.

AlanF wrote: Well I have plenty of time now. Once I've satisfied myself that I can easily revert back I'll dive in.

Another big advantage to OTX is that there is support online (RCGroups for example) as well as within the club. You will not find the same level of support for FrOS because virtually no one uses it - or if they do they are not posting on the forums. I regularly see discussions such as:

Question - "I'm try to do [insert problem here] with my X10S"

Answer - "That's easy. Do [insert answer here]"

Question - "Thanks for your reply but I'm using FrOS not OTX"

Answer - "OK, sorry, I can't help you then"


So if/when you do move over to OpenTX make sure you give it time for the logic to sink in. Don't be too quick to say "this would have been much easier with FrOS" and then revert to the original software.

The ability to program what You want, the end user rather than what the engineers think you want appealed to me. Here is an example: An EDF came with a door/gear sequencer circuit board. But it played up (as many RC forums mention often), gear moving before door, etc. With some spare channels I programmed the TX to control the main gear, nose gear and gear doors in the order and timing I wanted.

You have made a good move I think Alan but it comes with a learning curve (you have got loads of time at present ) but once understood the possibilities are endless. I spent maybe three weeks with the Taranis X9D just playing with settings using a RX and some servos plugged in on the bench to see what effect I had created. With both my TXs I back up their settings on to my PC using the OTX Companion so if I mess up at home or at the field I just reload the TX from the back up file.

Shame we cannot get together but you can alternatively contact me re:PM

MikeSeale wrote: So if/when you do move over to OpenTX make sure you give it time for the logic to sink in. Don't be too quick to say "this would have been much easier with FrOS" and then revert to the original software.

Footnote: I am going to use OTX on my race buggy too