Programmatic Signal Mapping with the API

Alias variables in the NI VeriStand environment are used to create an abstraction layer which:


  • allows for update/change of lower-level project components (e.g. plant models, restbus, HW interfaces) without impacting on project integrity (signal mappings etc.)
  • provides unified naming convention across model framework, restbus simulation and ECU HW IO

As an example, the figure below shows the naming convention switch (model to network naming) happening when mirroring model network interface signals into their correspondent alias signals.

In the alias layer, restbus and model network interface signals share the same naming conventions enabling the automation of signal mapping. diagram of signal mapping programmatically

Alias variables for model network interface are stored into a text file suitable for further import into NI VeriStand.