The main HCSCI tool is online Configurator which is an user interface consisting of layout image maps that represent all aircraft systems with all correct HCSCI parameters. You can quickly configure any cockpit panel that includes similar control elements, instruments or modules.
Usage: Select an appropriate element in the loaded image map and assign it to the switch, encoder, LED or display by clicking on the image-map area. When the configuration is ready (or in any moment) click the SAVE button to download the data.cfg file created in the Configurator.
Place this file into the HCSCI plugin folder and start your flight. If you need to add or change some parameter, just upload it to the configurator, 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. The main point is that having one configuration file (data.cfg) for Baron 58, you can use it with any free or payware B58, or any other similar aircraft, without changing your configuration file. For example, the assigned "Right_Gear_Pos" and "Left_Gear_Pos" parameters for flashing lignts will work in any aircraft you fly.
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 depenfing of 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.
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.Examples:
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.
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.
If you have assigned some hardware switch but see that the same switch on your virtual panel doesn't flip, it doesn't mean that the system in X-Plane is not affected. It can work as needed and you just have no "visual" representation on the screen (that you don't need when you have a "real" panel..). In most cases it is just animation of the on-screen switch for which the developer included additional commands/datarefs.
1. If some HCSCI control parameter assigned in the configurator is really not working with your aircraft model, that means the loaded plane script overrides the X-Plane commands/datarefs associated with this parameter, requiring its own "custom" datarefs/commands to be used (some models have just few custom commands and datarefs, some have a lot of them ).
In most cases, when plane developer creates custom datarefs/commands, this is useless in terms of the plane functionality because all these custom commands are used just for virtual 3D cockpit animations and writing the standard X-Plane datarefs.See more in [Custom Data Notes]
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. Download the data convertion file for some planes on the here "Custom Conversion" page.
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.