DualTurbine

You have a plane with two turbines? You need a easy monitoring for following rpm’s on both turbines at the same time? Here is one possibility for it! Made from a request from France, so here you are, s’il vouz plait!

Introducing DualTurbine

Featured functions

  • One telemetry screen with all info
  • Shows both rpm’s in the same screen
  • Shows bar graph with relative rpm’s
  • Alarm activated from any switch user chooses
  • Alarm when rpm’s differ with user selectable amount
  • Voice-announcement separately for left or right turbine for too low rpm

Available for DC/DS-24, requires firmware 4.22 or higher. App does not run with older firmware.

Installation

In short: Copy the .lc (or .lua, the .lc is memory-optimized) file from github here to your transmitters Apps-folder, if there is a translation file copy the .jsn file to Apps/Lang-folder on your transmitter. Head on to “Applications” -> “User applications” and add the app. Guide on installation of Lua-apps available here if you need some more in-depth guide.

Setting up and usage of  DualTurbine

After installation open the app and you are presented with easy setup with few options:

Let’s go through settings.

Turbine Settings

Rpm-sensors are self explanatory, just select the telemetry-sensor giving you their rpm. Sensor multiplicator is a setting for adding compatibility. Let’s say we have a turbine with rpm up to 230 000 rpm. Now the telemetry gives out values from 0 to 230 instead of 0 to 230 000, if this is the case select multiplicator of 1000. If your ECU-telemetry gives out correct value leave multiplicator to 1. Possible values are 1 and 1000.

Next up is idle and max rpm-settings. These are among other things for the bar graph on telemetry screen in your main screen. Let’s say your turbine has a maximum rpm of 250 000 and idle at 30 000. Settings these values in setup means the bar graph shows you the range between 30 to 250 000.

Alarm Settings

Next up is the alarm-settings. Alarm is made if one turbine rpm is lower than the other.

First is the choice of switch. Alarms will function if this switch is activated. Advantage is that you can set the switch as the same for example as flight-mode, gear or anything that is active only when you are actually in the air. This way you will not generate any unnecessary alarms when starting or shutting down etc.

Allowed rpm difference is the maximum allowed difference in two turbines rpm’s before alarm is generated. If you need to keep them within 1000 rpm set this to 10. Note the multiplicator of x100 here.

Voice-files are self-explanatory. For example for left you could make your own file like “Left turbine low rpm”.

Telemetry Display

Go to “Main Menu” -> “Timers/Sensors” -> “Displayed Telemetry” and add “RCT DualTurbine” to your main screen.

DualTurbine In Use

Here’s a example of settings:

I have set up idle rpm to 30 000, max rpm to 275 000 and allowed difference to 5000 rpm. Lest see how it would look on your main screen.

 

First picture above shows the screen when there is no signal from telemetry ie. plane is powered down. Second screen shows rpm’s as 0 since power is on but turbines are not running.

 

First picture above shows a little high idle of 35 000 rpm on both turbines. The bar graph is just started since our idle rpm setting is on 30 000. Second picture has us in flight with 235 000 rpm on the left turbine and 233 000 rpm on right turbine. Since the difference is not over our max difference setting everything is green and normal.

Here is a screen of what happens if one turbine’s rpm goes down. The lower turbines rpm-display and bar graph goes red, there’s also visual red arrow pointing to the turbine with lower rpm.  This is also the moment where voice-warning is played, in this case for the right turbine.

Alarm is generated once. For the alarm to be possible to trigger again rpm’s need come back to rpm’s inside the max allowed difference-setting.

That’s it. Quite simple but very informative!

Version history

  • 1.0 Release version

Disclaimer

Some rules do of course apply!

  • Never use Lua to control a function that would take the model down if misbehaving!
  • Always, always test the function thoroughly before flying!
  • If you do not know, then don’t!
  • RC-Thoughts or myself is NOT responsible for anything this application does
  • Applications are free to use (MIT-license) and linking to this page is encouraged!