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 gauge maintains a buffer of up to 400 events.  This buffer is written to file on the following bases:
On an append basis when - you exit the panel, when the On/Off click area is set to 'Off', or when the buffer is full.
On an overwrite basis when - the RST click area is clicked.

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

  10847  KEY_YAW_DAMPER_ON  0
  10847  KEY_ANTI_ICE_ON  0
  10847  KEY_MAGNETO1_LEFT  0
  10847  KEY_MAGNETO2_LEFT  0
  10847  KEY_PITOT_HEAT_OFF  0
  10847  KEY_YAW_DAMPER_ON  0
  10847  KEY_ANTI_ICE_ON  0
  10847  KEY_MAGNETO1_LEFT  0
  10847  KEY_MAGNETO2_LEFT  0
  10847  KEY_PITOT_HEAT_OFF  0
  10848  KEY_YAW_DAMPER_ON  0
  10848  KEY_ANTI_ICE_ON  0
  10848  KEY_MAGNETO1_LEFT  0
  10848  KEY_MAGNETO2_LEFT  0
  10848  KEY_PITOT_HEAT_OFF  0

The first number is the raw value from the Tick18 variable.  It will give you an idea of how frequently the events are being generated.  The second number, at the end of each line is the numeric parameter passed with the Key_Event.  This is usually zero, but can contain a useful number if the Key_Event takes a non-zero parameter (frequency set commands for the radios for instance).
The gauge will not log the axis_set events generated by game controllers such as yokes and joysticks. 

Additions to this second 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.

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.

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
Toronto, Canada
December 27, 2006
douglassdawson@netscape.net

