Search results

  1. C

    Suggestion for another EMS gauge

    Personally I think acceleration would be almost useless as well as misleading because the speed required to fly varies based on your total weight (passengers, cargo, and fuel) as well as density altitude. A more useful metric, that does not make assumptions, would be to indicate runway distance...
  2. C

    I need rotor RPM added to my display

    In any case your latest file worked and changing the engine type to Other, as you suggested, allowed me to configure the gauges as needed. Thanks for your help. I still maintain it would be nice if I could retain the existing Rotax behavior for just one of the RPM sensors but don't expect this...
  3. C

    I need rotor RPM added to my display

    But if I do that then I lose out on the variable engine range, right? The way it works right now, out of the box, is when oil temperature is < 120 degrees then engine green range only goes up to about 2400 rpm, and when oil temp is >= 120 it changes to about 5500 rpm. With a nonspecific engine...
  4. C

    I need rotor RPM added to my display

    Your suggestion does not work. I even deleted both RPM inputs, reloaded the file, exited setup, went back in, added them to sensor input mapping, but as always only one appears in Sensor Setup or the Screen Layout Editor which is grayed out and says "ROTAX - FIXED". But even if it had worked...
  5. C

    I need rotor RPM added to my display

    I did answer you already; I loaded that file but it does not make a difference. I clicked "Load Files", selected it, and loaded it, and it said the load was successful. I had used a modified version of the file that only had rpm_policy=single and not ff_policy since that guy had multiple fuel...
  6. C

    I need rotor RPM added to my display

    By the way I was thinking about solutions. I think the existing sensor value of "RPM" should be renamed "ENGINE RPM" and otherwise remain exactly as-is in behavior, but in addition there should be a new sensor type of "OTHER RPM" which functions as a fully-configurable RPM sensor, not locked...
  7. C

    I need rotor RPM added to my display

    And here are photos. You can see in Sensor Input Mapping I have two RPM sensors defined, named "ENGINE" and "ROTOR". But in Sensor Setup the system arbitarily selects the last one entered (which happens to be Rotor), does not list the engine rpm, and the rotor rpm cannot be selected; it's grayed...
  8. C

    I need rotor RPM added to my display

    I'll post screenshots tomorrow after I've gone to the hangar again, but it is an experimental aircraft, not LSA. I did load the dfg file from the other thread but it has nothing to do with the number of RPM inputs, only how RPM is calculated. The engine is a Rotax 912ULS. The engine RPM gauge...
  9. C

    I need rotor RPM added to my display

    Unfortunately that doesn't work; I have the sensor input mappings correct but the sensor list only shows one RPM input which is grayed out and says "Rotax - Fixed". It will not let me add a second RPM, at least not in the UI. I'm going to need some kind of DFG file to allow me to add a second...
  10. C

    I need rotor RPM added to my display

    I need two RPM widgets: one for the engine and one for the rotor. They are entirely independent of each other, and the rotor one should be labelled as such.
  11. C

    I need rotor RPM added to my display

    I have the HDX suite in a gyroplane and I need a rotor RPM gauge added to the EMS screen. The rotor RPM is already wired up on pin 35 of the EMS if I remember correctly, and configured in the EMS setup already (i.e. 10 pulses per rev). I just don't know how to add it to the UI.
  12. C

    Zoom buttons

    I concur. The knob is the obvious choice for zooming.
  13. C

    Bug with bugs, and feature requests

    Again, you guys are acting like I suggested removing the omnidirectional nearest function, but I did not. There should always be omnidirectional nearest by default but with a directional nearest applied with a simple button push. That is much more useful the 99.9% of the time that you are not in...
  14. C

    Bug with bugs, and feature requests

    Well height above ground is not height above obstructions. You can click any point on the map and it tells you the terrain elevation and how that compares to the aircraft's current altitude but again that is not obstruction height, just terrain height.
  15. C

    COM Radio Suggestion

    When viewing the info page for any airport, you can push the display button that says "APT->COM" to program the radio. Then you push the physical TWR/GND/etc. buttons on the radio to dial in the corresponding frequency for that airport. You can also manually tune a frequency on the radio and...
  16. C

    Bug with bugs, and feature requests

    We've been flying 100 years without GPS ground speed yet we have it now because it's nice to know. Same with AGL. Yeah, once or twice out of a thousand flights you will need an omnidirectional nearest option which is why the directional mode should be toggled with a simple button push. But for...
  17. C

    Bug with bugs, and feature requests

    I've had a week so far to fly my new aircraft with a Dynon HDX and it's awesome, but I found a very minor bug with bugs and I had some feature requests too. The bug bug is that if you disable a bug, the digital indicator remains onscreen. For example with the airspeed bug disabled, I still get...
  18. C

    Backup battery test impossible after the first yea

    Nominal voltage of the battery is only 11.1V and I think mine went to 10.6V after 45+ minutes if I remember right. I do agree you need to swap batteries to verify the problwm is with the battery and not the display.
  19. C

    Keeping backup battery charged while building

    The backup batteries are lithium ion which does NOT self-discharge, and it is best NOT to keep the battery fully charged when not in use. That is why lithium ion batteries are never sold fully charged.
  20. C

    Backup battery test impossible after the first yea

    Your alternator might be weak. Verify by keeping your other screen off and only using the screen with the low battery. See if it charges the battery more quickly that way.
Top