Hello ,does anybody know how to do or download the audio commands for a 24 channel.Thank you Nick

Nick,

I use http://http://www.fromtexttospeech.com/

Type in the command you want and select the voice. Download the mp3 and load it into the Audio/EN (or whatever language you use) folder on the transmitter.


Paul

Thank you Paul I will try and see how it goes

www.rc-thoughts.com has a text to speech translate which I use. Create the wave file you want to use and save it to the folder on the DC-24 with the others. But your radio should come with some basic voice commands already. Go to voice commands and adde a function you want annunciated and assign a wav file to it.
RP

https://www.espritmodel.com/elite-firmware-updates.aspx

Added a new parameter for configuration: Voltage Hysteresis
The hysteresis is taken into account in case of switching supply from one battery to the other and back. It is important to keep the hysteresis low to enable equal discharging of batteries. On the other hand, it must be high enough to prevent fast battery switching under load.

Thank you...

I use the XICOY telemetry adapter to get the motor status on my Jeti transmitter. The turbine status is just reported as a number. I found this list of codes from Gaspar:

Status 0 = "TempHigh"
Status 1 = "Trim Low"
Status 2 = "SetIdle!"
Status 3 = "Ready "
Status 4 = "Ignition"
Status 5 = "FuelRamp"
Status 6 = "GlowTest"
Status 7 = "Running "
Status 8 = "Stop "
Status 9 = "FlameOut"
Status 10 = "SpeedLow"
Status 11 = "Cooling "
Status 12 = "IgntrBad"
Status 13 = "StarterF"
Status 14 = "Weak Gas"
Status 15 = "Start On"
Status 16 = "User Off"
Status 17 = "Failsafe"
Status 18 = "Low RPM "
Status 19 = "Reset "
Status 20 = "RxPwFail"
Status 21 = "Pre Heat"
Status 22 = "Battery!"
Status 23 = "Time Out"
Status 24 = "Overload"
Status 25 = "Ign.Fail"
Status 26 = "BurnerOn"
Status 27 = "Starting"
Status 28 = "SwitchOv"
Status 29 = "Cal.Pump"
Status 30 = "PumpLimi"
Status 31 = "NoEngine"
Status 32 = "PwrBoost"
Status 33 = "Run-Idle"
Status 34 = "Run-Max "
Status 35 = "Restart "
Status 36 = "Error "

Is there a way to get an alarm when there is a flame out (code 9) without LUA scrip? Or has anyone made up the code to do this?
My X45 is quiet compared to the larger turbines and when it flamed-out I couldn't tell from sound. It would be nice to know quicker.
(the info was copied from the Digitech CTU thread and I posted similar in the X45 flame out thread)
Thx

Also posted on the X-45 thread.

A Flameout alarm can be set just using Telemetry Controls and Logical Switches.

Set TM Control MX1 for Pump Voltage < 0.01V, enabled by your engine kill switch in the run position
Set TM Control MX2 for EGT>300C, enabled by your engine kill switch in the run position
Set a Logical Switch for MX1 AND MX2

Use the Logical Switch to trigger a Flameout warning using 'Sounds on Event'.


Paul

You could also just use a Telemetry Control for Status = 9 to trigger the warning.

Health warning - I've not tried this method but I don't see why it wouldn't work

I use the first method I posted as most of my telemetry adaptors are older and do not output the Status message. According to Gaspar they can be updated, so I plan to send mine in.

Paul

Even if you can, I wouldn't do it based on the status code for flame out. There are other reasons such as Low RPM, that can result in the turbine shutting down in flight. Alarming based on something such as pump voltage and EGT, etc should cover them all where the flame out status code would seem to cover only one of the causes.

I also add a stick shaker (3 times) to the alarm. If it's so noisy you can't hear the engine, you might not hear the aural flameout warning either.

I've often wondered what's the fastest possible telemetry response to a flameout .. you could look directly at exhaust temperature, or the RPM or the pump voltage. I've always presumed that temperature would be the best, since the RPM response would be slowed by mechanical inertia, and the pump voltage (and the ECU code for flameout) only occurs after the ECU figures out what has happened and starts to take its own action.

But I've never done any actual tests .. and perhaps the time difference is only fractions of a second and would not really matter anyway.

I do like the idea of a stick shaker.

Dave

Dave,
The setup Paul described, which I use, works very well. The EGT > 300 to arm keeps the alarm from activating until after the engine is running. I think most ECU's shut down the fuel pump almost immediately if the EGT drops, so the pump voltage is a good trigger. Also, it activates every time you shut down the turbine, verifying it's set up correctly.

I suppose there are other reasons an ECU might shut down a turbine, such as overspeed or overtemp, but again, I think the ECU is going to kill the pump to do so.

Craig

PS: On my A-10, I have it set up to shake the left stick if the left engine fails and shake the right stick for the right engine. Unlike the rest of the programming, I thought of that myself.

Craig,

By having the MX1 and MX2 TM Controls enabled by the engine run/ kill switch, this avoids the flameout warning every time you shut the engine down.

I do get the occasional flameout warning during engine start - this appears to be due to a momentary 0V command to the fuel pump during the initial switchover & fuel ramp phase of the start sequence. I just ignore these.

Paul

RCU was deleting about half of my post. Trying again.


Based on Craig's comment about setting up a stick shaker, I've modified my logic a little.


Set TM Control MX1 for Pump Voltage < 0.01V, enabled by your engine kill switch in the run position

Set TM Control MX2 for EGT>300C, enabled by your engine kill switch in the run position

Set a Logical Switch for MX1 AND MX2

Set an Alarm based on Pump Voltage <=0.01V, activated by the above Logical Switch


Using Alarms allows access to the stick shaker, along with an audio announcement, unlike my previous Sound on Event.


Paul

I give up, hopefully this part posts to complete the logic.


Set an Alarm based on Pump Voltage <=0.01V, activated by the above Logical Switch


Using Alarms allows access to the stick shaker, along with an audio announcement, unlike my previous Sound on Event.

I was trying to complete my post, but RCU for some reason is cutting off some of my text.


Set an alarm based on Pump Voltage less than
0.01V, activated by the above Logical Switch.

Using Alarms allows access to the stick shaker, unlike Sounds on Event.


Paul

It was the less than or equal to symbol that was messing up my posts. Duh!

Paul,
Reading a little closer, I realize my setup is not exactly as you described since I don't link the alarm to the Run switch. This is my setup:
· Alarm pump voltage (X< 0.2) switched by MX1 in Telemetry
· MX1 (in Telemetry) EGT (X>200)
· “Flameout” 3 times and left stick 3 short vibrations
It's the same trigger as yours and don't mind it going off on shutdown because it confirms it's working. In fact, with my setup at least, there is no way to test it without starting up and then shutting down, one way or the other.

FWIW, I've never had mine activate during a start.

Lots of different methods and options with Jeti.

Craig

This is really cool. I'm gonna have to try it out.
Thanks,
Gary

Hi,
I set my Throttle trim up so that one push is full down trim. I watched Harry's video on how to do this.
So, one push up enables the turbine and one push down will shut it off.
Is it necessary to have a dedicated 'kill switch'? It seems redundant.

Instead of using the trim button I used a locking switch for the throttle trim....no kill switch....but does the same.

I use the throttle trim but with two clicks instead of one. Easy enough to shut down quickly but not so easy that an accidental bump shuts it down by accident. A locking switch like Dansy uses is also a good method but I already use the one I have for the wireless ON/OFF switch.

I have second one for the wireless as well

I love locking switches. I use 3. RC on/off, turbine start ready/cut off (in lieu of trim switch) and gear up/down. I've seen too many jets do the "squat" over the years due to accidental gear switch activation. It's easy to activate after you practice and eliminates the accidental "squat".
Gary