The principle of inpit/output configuration in SimVimvCockpit is that you select all Inputs/outputs which are needed to be used in your cockpit using convenient configurator where you can find a parameter that is the most appropriate for the selected control, display or annunciator in your panel, assign it to the direct input pin, multiplexer input or output, and then place saved data config file in the SimVim plugin folder.
Before this, you need to decide how it is better for you to connect every toggle switch or button, how many LED drivers (or registers), LCDs or 7-segment displays you need, reading all related pages on SimVim website.
In general, when building a cockpit with SimVim, users don't need to concern themselves with the specifics of using "commands", "datarefs" (even for some custom planes), scripts or various options, and can fully focus their attention on the building process.*
It doesn't matter if your plane is a standard or customized X-Plane model, or some of the paid models - for any of them you need to create controls and assign outputs using SimVim Configurator that includes almost all controls, instruments and annunciators that can be found in any plane.*
All parameters are defined in SimVim database as abbreviated names that are meant to represent the real functionality in an actual aircraft cockpit, not limited to a specific virtual model's commands/datarefs set.
The idea is that a cockpit builder assigns these parameters to inputs/outputs based on what they should do in a real aircraft cockpit, not how they would interact with a particular virtual model in X-Plane. For example, these two parameter names represent the LED indicator for Left Gear Unsafe (in transition) and rotary switch for DC meter/display source selector:
Behind every of such SimVim parameter name stands a "macro", defined in the plugin database as a pre-assigned set of standard commands, or datarefs with all needed values, data format, conditions or a specific SimVim function.
This macro can also include a set of custom commands/datarefs, for example the parameters listed above consist of these sets of commands, dataref, values and options included in the plugin database (examples for standard and custom data):
standard: sim/flightmodel2/gear/deploy_ratio i=2 r=0.01,0.99
custom b737: laminar/B738/annunciator/left_gear_transit
custom b737: laminar/B738/knob/dc_power_up,laminar/B738/knob/dc_power_dn q=laminar/B738/knob/dc_power:6
Notice that for the latter Laminar B737 example a pair of linked up/dn commands is used in conjunction with a reference dataref as a "macro" function.
(!) Users are not allowed to create their own parameter names. We cannot allow this, because it can lead to the same "custom dataref" chaos that we see in X-Plane. If you think we don't have some parameter in the database (you can't find it), you can ask us to add it.
As we eventually plan to make SimVim compatible with other simulators, this feature (universal parameter names) it guarantees uniform configuration format, one configurator and possibility to fly on any simulator using the same data file.
Usually you don't need to know about simulator commands, datarefs and internal structure of each parameter to work with SimVimCockpit, just select an appropriate data name from the configurator table to assign input or output. It doesn't matter if your plane is a standard, custom, paid, you should make only one main data configuration file with all needed parameters from the table and test every input and output in you aircraft model.
If you have an aircraft model for which some of the selected and assigned parameters don't work, and there is no data conversion available yet for this plane model in SimVim, you need to find out yourself what parameter macros need to be used as custom ones and replace them in the plugin menu.
Using custom commands/datarefs set the plugin creates the "data conversion" table for specific aircraft model. These data conversion tables are references for the plugin that "reassigns" all needed data for your custom plane when it's loading.
Note: For some planes that have custom commands and datarefs this convesion Table is already included in SimVim database and you don't need to create it. You can see the list of planes for which non-standard (custom) functions are supported here, for example there are some new X-Plane 11 Laminar aircrafts that have several new datarefs/commands, and B737 Zibo mod version.
The custom data conversion tool is included in the plugin (since v 0.9.28). The "conversion" menu displays all your configured parameters, and provide the means to replace their default functions with custom commands or datarefs.
You have to know what you're doing when assigning conversion options! You will need to find specific info on your aircraft model to know which custom datarefs/commands and values to use.
There is no need to edit all the listed parameters. Only edit the parameters that don't work as-is in your custom aircraft. Test all assigned switches, buttons, outputs before (you can do this while the conversion menu window is opened).
Don't add/change parameters using standard datarefs/commands. ALL standard drefs/coms are already present in the SimVim database. Use only custom ones.
Don't do this for ZiboMod. It's correction data table (>600 parameters) is already added to the main database (as well as a few other custom planes). A few remaining parameters will be added soon. But you can test some parameter if you think we don't have it in the database, you can ask us to add it. Before that you can test it with your custom commands, assigning one "Test_Param_Input" or "Test_Param_Output" parameter in the data file and then mapping it to custom data.