Configuring System Mappings for Channels and Aliases
- Updated2024-10-31
- 2 minute(s) read
Configuring System Mappings for Channels and Aliases
- In VeriStand, open your base system definition file in System Explorer and click System Configuration Mappings.
- Add mapping connections for those mappings in which both connections are included in the base system definition file.
- Save this file.
-
Create a new channel mappings text file. Add channel or alias source and destination
paths to this file in which each line is in the format of source path
[tab] destination path. For example, it might look like this:
Contoller/Alarms/Cycler Fault/Alarm Status [tab] Contoller/User Channels/Test Fixture Fault
Note To see an example channel mappings formatted file, open System Explorer in VeriStand, and click System Configuration Mappings to generate a system mappings file. - Move this channel mappings file into your test station package next to your test station XML configuration file.
-
In the test station XML configuration file, include the
ChannelMappings attribute with the system mappings file name (for
example, ChannelMappings="Mappings.txt"). Refer to Test Station
Package XML Conventions for more information.
Tip To simplify repeated use of socket-specific mappings, consider using %SOCKET%. Refer to Simplify the Application of VeriStand Entities Across Multiple DUTs for more information.Note BTS merges the mappings defined in the channel mappings file with the mappings that are defined in your base system definition file. If both the base system definition file and the channel mappings file include a mapping with the same destination path, the mapping defined in the channel mappings file is used.
Related Information
- Simplify the Application of VeriStand Entities Across Multiple DUTs
- Test Station Package XML Conventions
The test station XML configuration file (.teststation) defines the instrument channel mappings for a test station during a given test.