Home Cockpit Simulator
Control Interface Software

Read This First --> -> -> -> ->

HCSCI - How it works, Configuration

The main HCSCI tool is online Configurator which provides you with everything you need to configure a cockpit panel of any complexity.

Configurator table

The HCSCI Configurator is an interactive user interface consisting of layout image maps that represent aircraft systems, instruments and modules with correctly assigned HCSCI parameters. Using these layouts you can configure any cockpit panel that includes similar control elements, instruments and modules.

All you need is select an appropriate element in the loaded image map (or table if there is no map yet) and assign it to the switch, encoder, LED or display by clicking on the image-map area.

Then, you need to save the data.cfg file created in the Configurator, place it into the HCSCI plugin folder and start your flight. If you need to add or change some parameter, just upload it to the configuration tool, make needed changes, and save again. Then press the "Reload Configuration" button in the plugin status window.

The HCSCI data configuration (the list of parameters) is universal and can be used with any model of any author with the cockpit you have built. So, in this example the "Right_Gear_Pos" and "Left_Gear_Pos" flashing lignts will work in any aircraft you fly.

What does each HCSCI Parameter consist of

The main point is that having one configuration file (data.cfg) for Beechcraft Baron 58, you can use it with any free or payware B58, or any other similar aircraft, without changing your configuration file.

Each "parameter" defines a specific control or aircraft system/device and sets the conditions for its operation. A parameter NAME is an alias of a function and its options, represented in the form of a universal "keyword" that is aimed to designate the functionality of a real aircraft cockpit control element ( not a specific virtual plane's commands/datarefs !)

When an aircraft is loaded, the HCSCI plugin reads the data configuration file and converts a parameter into predefined HCSCI function that can use multiple datarefs and other parameters and conditions depended on the assigned device type, or transtates it to X-Plane commands or datarefs with a value range, output format and conditions.

Parameter structure variants:

Param_Name_1-- input - >X-Plane Commands -- + options --Conditions, systems state

Param_Name_2-- input - >X-Plane DataRef + Value + options +Internal Conditions

Param_Name_3-- output >X-Plane DataRef + Output Format + Options, mapping

Param_Name_4 <-- I/O -->HCSCI Function --- > X-Plane or HCSCI DataRefs/Commands

Param_Name_5 <-- I/O -->Custom Conversion Table --- > DataRef, Commands

HCSCI configurator database includes almost every named control element and device that can be found in an aircraft panel. Some functions (switches and other controls) that are not presented in the configurator yet for some reason will be added eventually.

  • Left_Toe_Brake - left rudder toe brake input (button switch or potentiometer) - direct X-Plane commands/datarefs usage.
  • Flaps_Unsafe - "flaps in transition" or "stuck" annunciator (Simple HCSCI function programmed in the plugin for output to LED or LCD)
  • DME_Display - it's a complex HCSCI plugin functions for multifunctional output to the DME display (it works depending on the DME type selected in the configurator).

This feature (universal parameter names) allows to have uniform configuration format, one configurator and the possibility to adapt them to other simulators using the same data file in future.

Default functionality

All aircraft models that are included in the X-Plane by default and all their mods ( including the "Laminar" planes), as well as freeware third-party aircraft using only X-Plane commands/datarefs for virtual panel controls, work with the HCSCI as-is.

Also, using HCSCI with some of the custom (paid) X-Plane aircraft models you don't need to worry about simulator commands, datarefs, scripts, and internal structure of each parameter. This means that you can simply assign all the necessary parameters in the Configurator and fly.

Data conversion for custom aicraft models

If some assigned HCSCI parameters do not work properly in your plane model that has its own "custom" datarefs/commands (some have just few custom commands, some have a lot of them), you may need to have an additional HCSCI "data conversion file" for this particular model (hcsci_xxx.dat) and place it in assotiated aicraft folder.

This data file includes only those HCSCI named parameters that had to be "remapped" by plugin to related custom commands (datarefs) provided with this specific model. You can download the related data convertion file for some planes on the HCSCI "Custom Conversion" table or create your own file that can be later added to the community download list.

How it works: When an aircraft is loading, the plugin looks for replacement data table and remaps all needed standard input/output parameters located in the HCSCI database into this plane model custom data.

NOTE: The conversion mapping for some freeware models, that use their own custom datarefs, can be already embedded in HCSCI database, like Aerobask Robin DR401 (you can use it as is). Also, if you have a plane that uses the REP (Reality Expansion Pack), the plugin should automatically remap all the needed parameters.

SimVimCockpit 2012 - 202X