Play active model name on startup, or confirm?

[DHDSP]

Hi everyone,

I am one of those guys who always forgets to change models in the TX...
The checking of the switch position, and the safety switch for throttle have helped a lot, thanks (Bertrand) for those.

Now I want to play the name of the active model on switching on the TX, or even having to confirm the active model.
How do I accomplish this? (I can play sound files on normal swicthes)

TIA
Peter

PS: Alternatively I will just add a voicefile to the safety switch.

[mhotar]

Hi,
You can use mON event in function to play model name using custom sound.

[mhotar]

Hi,
You can use mON event in function to play model name using custom sound.

[mhotar]

Hi,
You can use mON event in function to play model name using custom sound.

[mhotar]

Hi,
You can use mON event in function to play model name using custom sound.

[Scott Page]

Hi,
You can use mON event in function to play model name using custom sound.

I've actually added a mSwitch to every switch position and mOn to the model name -- now when it starts up -- it welcomes me, gives me a rundown of all switches and announces which model is currently active. One problem -- I'm running out of Function switches. I'm hoping that can be expanded.

[bertrand35]

But there are 32 Custom Functions! It is not enough?
Bertrand.

[Scott Page]

But there are 32 Custom Functions! It is not enough?
Bertrand.

I'm a typical American -- I always want more.

I have each switch trigger sound in either direction. That takes 14 - just for sounds. Each model has unique announcement when it's chosen -- That's 12 (so far). Have volume knob (1) Welcome (1) and then there is the telemetry that I've only started to work with.

(embarrassed) but it's real amazingly cool. I can't wait until the weather warms enough that I can fly with my club members. They will soil their pants.

[Rob Thomson]

I believe it is 32 custom functions per model

[Scott Page]

Yes... you're right. I'll need to do closer inventory of where they are going. So I don't have all the model names in each one... correct.

[Scott Page]

I'm still building my "template" model that will be the basis for all others. I'm not out of slots yet, but I noticed when working late last night I can see the end of the tunnel. I'm pretty tired right now, I forgot that I have just one slot that speaks the model name. Wish I had the Tx with me so I could work on it now as I'm at work "monitoring".

[DHDSP]

OK, I will try the mOn - easy.

But to my second thought: would it be possible to have a screen on startup, asking for me to choose the active model every time on startup ?
Or would this be a bad idea in case of a reboot during flight ?

[bertrand35]

What about using the Phases/Mixes name field to play some files?

For example suppose you have a Mix named "Flaps". The Tx would play:
- "flapsON.wav" when activated (one time)
- "flapsOF.wav" when de-activated (one time as well).
- "flapsBM.wav" (background during the whole time the Mix is enabled

The same could apply for the phases :
- "landON.wav"
- "landOF.wav"
- "landBM.wav"

Just a proposal, nothing is done

Bertrand.

[Kilrah]

But then you'd have the same phase sounds for all models, no?

Let's complete that idea then...
When a model is loaded, the radio looks for a subfolder of the 9XSOUNDS folder with the same name as the model (case sensitive). If found, it then uses the sounds in there for all switch / phase events when present:
- THRon.wav, THRoff.wav, ID0.wav, ID1.wav, ID2.wav, ... same for all switches
- FP0.wav, FP1.wav, etc (no need for OFF sounds as a phase OFF necessarily means another phase ON, BM is a good idea though)
- Timer1.wav, Timer2.wav for when they expired
- modelname.wav
- ...?

This would allow for the vast majority of events to be handled directly, leaving custom functions only for "special" complex things, and would not unnecessarily clutter the menus.

Or maybe a sound setup screen where those sounds can be chosen for each model instead of the subfolder thing? Might be more clear and not require as many file operations / name guessing for lost users...

[bertrand35]

Mais oui mais bien sûr !!!

The idea of "fixed" filenames saves a lot of RAM and EEPROM - and work
With the Massstorage, I think it will be really easy to configure those sounds and replicate them for each model if needed!

Bertrand.

[DHDSP]

I think it's a great idea too. From a dumb user point of view, it would be great to have "standard" sounds which can be copied for each model - without having to assign them manually in menus.

Another idea would be having a directory containing fixed-filename-sounds which are used regardless of the model in use. That way you wouldn't have duplicate files on the storage. Then another directory called "model1", which would only contain files that are different , like "modelname.wav".

[Kilrah]

Yup why not. Radio looks for thron.wav in the model's folder first (if it exists), if not found it looks for it directly in 9xsounds, and plays that if found.

[Flaps 30]

I have each switch trigger sound in either direction. That takes 14 - just for sounds. Each model has unique announcement when it's chosen -- That's 12 (so far). Have volume knob (1) Welcome (1) and then there is the telemetry that I've only started to work with.

This is where Er9x wins out regarding voice file use. Each switch can have two (one for on, one for off) voice files that are activited by the 'Both' command in safety switches. That would save you half the number of slots that you use with Open9x. The voice safety switches also offer something that I really miss, and that is being able to repeat a voice file every 15/30/60 seconds (selectable) while a switch is activated. As for model name voice. In Er9x that is in another setup page, so that is another safety switch saving.

[bertrand35]

This delay / repeat function is also in open9x!
Bertrand.

[jhsa]

open9x and er9x start going in different ways, and while I agree with you about the switches, I would like to have for example, audio for the throttle and switch check at startup in er9x.. I think that is already available in open9x..

João

[Scott Page]

What about using the Phases/Mixes name field to play some files?

For example suppose you have a Mix named "Flaps". The Tx would play:
- "flapsON.wav" when activated (one time)
- "flapsOF.wav" when de-activated (one time as well).
- "flapsBM.wav" (background during the whole time the Mix is enabled

The same could apply for the phases :
- "landON.wav"
- "landOF.wav"
- "landBM.wav"

Just a proposal, nothing is done

Bertrand.

My brain is thick(er) today. I need to think about this. basically I want it to tell me when I switch from high to low rate each time or the opposite -- so I know where I am and hit the correct switch. Not just for safety - but also for bling at the field. I'm going to have to take a day off work to think about this.

[Flaps 30]

This delay / repeat function is also in open9x! Bertrand.

I have yet to discover that function. Someone a while back mentioned using the timer combined with whatever other functions, it all sounded rather complex. I couldn't get it working.

open9x and er9x start going in different ways, and while I agree with you about the switches, I would like to have for example, audio for the throttle and switch check at startup in er9x.. I think that is already available in open9x..

I left Er9x in October to gain the vario 'beep' dunction that Open9x has. So I would have to dig back to see what the differences are as of now on the voice front.

[jhsa]

In er9x, still the same as before.. but I meant to say that the audio in open9x works a bit different as far as I understand

[bertrand35]

But then you'd have the same phase sounds for all models, no?

Let's complete that idea then...
When a model is loaded, the radio looks for a subfolder of the 9XSOUNDS folder with the same name as the model (case sensitive). If found, it then uses the sounds in there for all switch / phase events when present:
- THRon.wav, THRoff.wav, ID0.wav, ID1.wav, ID2.wav, ... same for all switches
- FP0.wav, FP1.wav, etc (no need for OFF sounds as a phase OFF necessarily means another phase ON, BM is a good idea though)
- Timer1.wav, Timer2.wav for when they expired
- modelname.wav
- ...?

This would allow for the vast majority of events to be handled directly, leaving custom functions only for "special" complex things, and would not unnecessarily clutter the menus.

Or maybe a sound setup screen where those sounds can be chosen for each model instead of the subfolder thing? Might be more clear and not require as many file operations / name guessing for lost users...

The first part of this feature is implemented in the current revision: when starting a flight phase, the file /9XSOUNDS/[model name]/[flight phase name]-ON.wav is played. The same for the [...]-OFF.wav file.

Bertrand.

[Kilrah]

But:

- FP0.wav, FP1.wav, etc (no need for OFF sounds as a phase OFF necessarily means another phase ON)

[bertrand35]

Less flexible! When you enter in a phase, you don't know which one you are leaving...
Bertrand.

[Rob Thomson]

Sometimes you may use flight phases as a on off switch.

Having and off file does not mean you have to use it?

But guess you would in the code have to play one after the other... Can that be done?

[bertrand35]

Of course, and the OFF of the previous phase is played before the ON of the current, of course!
Bertrand.

[Kilrah]

I thought it made no sense to have an OFF sound, because the ON sound for the newly selected phase will play anyway, and that's what counts (when you flip the switch and hear the sound for the "landing" phase, its pretty obvious that the previous phase isn't selected anymore )

But well, I guess making it possible is OK for those who might want it as it's easy to just not put files for the OFF events.