Gauge: fsx_event_logger.gau

This gauge is designed to detect repeating FS Key_Events which interfere with normal panel operation.  Symptoms of repeating Key_Events include an inability to select a second exit or second engine, as well as accelerated selection on autopilot controls (Course and Heading controls increment by 10 instead of 1, Altitude Select increments by 1000 instead of 100.)  
This gauge will not tell you which gauge is sending the repeated Key_Events, but by identifying the events themselves, it should make the task of identifying the offending gauge somewhat easier.

INSTALLATION:
The gauge file can be placed in your gauges folder or in the panel folder.  Syntax is:
gauge20=fsx_event_logger!event_logger,  315,544,120,73

The log file is called 'Key_Events_Sent.log' and is located in the main FS folder.  This is a sample of the output:

 Time= 0.000060 Aircraft Loaded Title= Boeing 777-300 Type= BOEING Model= B773
 Time= 0.000072 Gauge Loaded= D:\fsx\GAUGES\fsx_event_logger.GAU
 Time= 2.339155 Logging Started
 Time= 3.203019 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 250
 Time= 3.846376 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 250
 Time= 4.449432 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 225
 Time= 5.001878 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 225
 Time= 5.756971 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 10035
 Time= 6.260553 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 10035
 Time= 7.139572 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 77
 Time= 7.510679 id= 970 event= KEY_PANEL_ID_TOGGLE evdata= 77
 Time= 8.436040 id= 804 event= KEY_TOGGLE_ELECT_FUEL_PUMP1 evdata= 0
 Time= 8.892325 id= 805 event= KEY_TOGGLE_ELECT_FUEL_PUMP2 evdata= 0
 Time= 9.375627 id= 958 event= KEY_TOGGLE_FUEL_VALVE_ENG1 evdata= 0
 Time= 9.959176 id= 959 event= KEY_TOGGLE_FUEL_VALVE_ENG2 evdata= 0
 Time= 11.197402 Logging Stopped
 Time= 41.139337 Log File Closed

The first number is the time, in seconds (system time, not sim time.)  It will give you an idea of how frequently the events are being generated.
The next item, "id" is the numeric description of the event being logged, with the "event" item being the text description.
"evdata" is the parameter being passed with the event.  In the example above,  "KEY_PANEL_ID_TOGGLE" requires the number of the panel ID being toggled. 

Additions to this version include the count of Key_Events issued.  If this number is increasing rapidly, then you likely have a repeating event, which the log file will reveal when you activate the logging function.  Also, when the mouse is held over the event counter, the tooltip will display the most recently issued Key_Event.  It is hoped that these two features will reduce the amount of actual logging to file that needs to be done.
The displayed event counter will be reset to zero when the RST click area is clicked.

By default, the gauge will ignore control surface and throttle axis commands.  Typically, these events are generated by game controllers.  Any game controller that is not very, very new will generate enough noise so as to be quite annoying when you are trying to log events.
If you need/want to log control surface and throttle axis events, add a fifth parameter to the panel.cfg entry.  Any value will do - for example:
gauge20=fsx_event_logger!event_logger,  315,544,120,73, X

That's about it.  Typically, you don't have to leave the gauge 'On' for very long - a couple of seconds will usually be enough to give you an idea if there are any Key_Events that are being generated repetitively.

Although not tested, this gauge should work in FS9 - there is nothing that should prevent it from doing so.
Also, if you are prepared, this gauge could prove useful as well... ;-)

The gauge is code signed for use in FSX.  When you start up the sim, you will receive a Security Warning, asking if you want to run "FS Event Logging Gauge," published by Douglas S. Dawson.  You can click "Run" or "Don't Run" as you wish :-)
If you click on the "More Options" button on the left, you will be given the choice of always trusting software that I have published.  If you do so, you will never get this security warning again for any of the gauges which I have code signed. 

Doug Dawson
douglassdawson@netscape.net
Ottawa, Canada
April 14, 2012