Tag Archives: GF-RP48

XGoFlight 2.1 brings full customization for RP48 rotaries, array dataref support, and GA MCPPRO profile

Although it has been a mere two and a half weeks since the release of XGoFlight 2.0, I am pleased to announce the release of XGoFlight 2.1, which adds full customization for the RP48 rotaries, array dataref support, and a general aviation MCPPRO profile.

Customizing RP48 rotaries

When I started the XGoFlight project, my goal was to create the most flexible and customizable GoFlight plugin on the market.  In all versions prior to XGF 2.1, the rotaries could only be used with a limited number of preset actions.  After receiving some user feedback, I decided it was time to extend command and dataref-based customization to the RP48 rotaries.  An example JSON configuration for the rotaries is included below:

Let’s break it down…

  1. Uses preset action: spoiler
  2. Each turn to the right will increment the auto brake by one, whereas each turn to the left will decrement the auto brake by one.  The minimum auto brake level is zero, which usually signifies RTO.  The maximum auto brake level is 5, which usually signifies MAX.
  3. Each turn to the right will execute the command defined by “command_on,” whereas each turn to the left will execute the command defined by “command_off.”  In this case, turning the rotary left will turn the XPDR off, whereas turning the rotary right will turn the XPDR on.
  4. Uses preset action: engine_apu_switch

Using array datarefs

While most X-Plane datarefs contain only one integer or float value, some datarefs contain multiple integers or float values.  The datarefs that contain multiple values are called arrays.  In plugins/DataRefs.txt, those datarefs are indicated with brackets, as pictured below:

We will use the two “generator_on” datarefs for this example.  The first dataref (sim/cockpit2/electrical/generator_on) is an array of eight integers.  The following example can be used with the RP48, P8, or WP6 for any aircraft with two generators.

The number located within the brackets is called the offset.  Every array starts with a zero offset.  In this example, generator_on[0] is the first generator, and generator_on[1] is the second generator.  This pattern is relatively consistent across all X-Plane datarefs.

MCPPRO: General aviation profile

The default MCPPRO profile is geared toward jet aircraft with complex autopilot systems.  The default profile supports VNAV, autothrottle, and other functionality not seen in a common Cessna 172.  The general aviation profile provides a non-specific solution for users looking to more closely match that class of aircraft.  Below is a comparison between default and GA profiles (only differences are highlighted):

Default GA
A/T ARM NORMAL
SPEED NORMAL
LVL CHG NORMAL
VNAV NORMAL
ALT HLD ARM SYNC/HOLD
V/S NORMAL PITCH SYNC
V/S WHEEL NORMAL NOSE UP/DOWN
DISENGAGE NORMAL

To use the general aviation MCPPRO profile, add the following to your xgoflight.json configuration file.

 

Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS

XGoFlight 2.3.1 maintenance release available

Moments ago, I posted the XGoFlight 2.3.1 maintenance release.  This minor release includes two bug fixes and a new GF-46 feature.  In XGoFlight 2.3.1, barometric pressure is available for the GF-46 module using the barometer function.

The first bug fix corrects a change implemented in 2.3, which caused problems with the button toggle for float-based datarefs.  For example, when a simple float-based dataref was used on the RP48, P8, or WP6 modules, the associated button could be turned on but not off.  I found this out the hard way, after getting setup for a leg with FlyJSim’s 727.

Lastly, a few of you contacted me about problems with the EFIS map mode switch.  Over the past few weeks, it has become apparent that there may be slight differences between the various EFIS firmwares.  The 2.3.1 release includes a potential fix for the nonfunctional map mode knob.  If you are experiencing this issue, please see the Usage page for information on how to configure the version parameter.  Also, because I do not own any modules with the alternate firmware, I cannot test the provided solution.  As a result, any feedback (positive or negative) would be greatly appreciated.

Share and Enjoy

  • Facebook
  • Twitter
  • Delicious
  • LinkedIn
  • StumbleUpon
  • Add to favorites
  • Email
  • RSS