Kramer Electronics WP-501 - Manual (Page 31)

26 K-Config - The Driver Manager – Getting Started
For example, when selecting PWR_ON:
Figure 35: An Empty Command Line
Note that when adding a command name to one of the Shared sub categories, this command name will be
added to the Serial, Serial Replies and IR sections in your command name tree and will appear as empty in
all the drivers you will open for editing or as new from now on.
Each of the above categories also includes a Non-Shared sub-group. The Non-shared sub-group is used for device
specific command actions which are not used for other devices. Command names added to this section will not
appear as empty command names in other drivers you will later open, since they are specific for this driver.
When importing or opening an existing driver, the command names included in this driver are compared to the shared
command names. Whenever a match between command names is found, the syntax associated with this command
name will appear under the relevant shared command name. If a command name is not found in the Shared sections,
it will appear in the Non-Shared section of this driver.
5.1.1 Updating Commands Names to the current version of K-Config
If you were using a previous version of K-Config, we recommend that you update the command names that are used
in your command tree. This can be done easily by opening the command syntax, and changing the command name
to the relevant Shared command name (see Section 5.4 ).
For example, in a certain driver the Power On function was previously tagged with the command name
"POWER_ON". In the Driver Manager this command will be listed in the Non-Shared category as a non-shared
command. Select this command for editing, and change the command name to “PWR_ON”. The command name
changes and will move to the Shared section of this driver.
It is important that you carefully change the command names in this manner. If these commands are already
used in an existing project that you may want to upload in the future to control devices, you will need to
update the command names in the project itself where they are used.
This framework was structured to let you standardize the command names so that all the same command types will
share the same command name although the specific command content is unique for each specific device.
i
i