Data Logging Options When Using ASAM XIL Steps for NI TestStand

ASAM XIL is an API standard for the communication between test automation tools and test benches. The standard supports test benches at all stages of the development and testing process. 

The ASAM XIL Steps for NI TestStand are sets of custom steps that allow you to reuse test sequences developed for other hardware-in-the-loop (HIL) systems that use the ASAM XIL API. 

ASAM XIL standard defines two major components:

• the framework, which provides data measuring and mapping functionality independent from the used test bench hardware and software.
• the test bench, which provides port-based communication means to the simulation model, the ECU, the electrical subsystem and the ECU network.

Each component has its own data logging standard, named Framework Acquisition and Testbench MAPort Capturing. As of ASAM XIL TestStand Steps 1.4, data logging is not supported in ASAM XIL TestStand steps. This articles explains how you can do data logging for NI VeriStand when using ASAM XIL Steps for NI TestStand.

NI VeriStand offers various Data Logging Options. You can decide which option to use depending on the requirement.
 

Log File Saved at Target

Embedded Data Logger and NI-XNET Raw Frame Data Logging provide Log Trigger channel which you can control from TestStand using Framework Get Variable Values or Target Script Set Parameter Values step.



Logging waveform acquisition from a DAQ device provides limited start and stop trigger functionality. You cannot control the when to start and stop the logging for waveform acquisition.

You can then retrieve the file from Real-Time targets. Please refer to Using WebDAV to Transfer Files to Real-Time Target or Tools Available for File Transfer/Access on NI Linux Real-Time Targets.
 

Log File Saved at Host 

NI VeriStand Steps for TestStand provides TDMS logging functionality based on VeriStand .NET Client API. The relevant LabVIEW VIs have been attached to this article. Note that Start Logging.vi uses forward slash "/" for the Channel paths input, as opposed to the backslash "\" used in the ASAM XIL TestStand steps.

If you are familiar with C# programming, the C# shipping example for MAPort Capturing is available at C:\Users\Public\Documents\National Instruments\NI VeriStand 20xx\Examples\DotNet4.6.2\ASAM XIL
You can create your own .NET assemblies and call it from TestStand using .NET Adapter.

ASAM XIL API does not work with Stimulus Profile Editor. NI does not recommend using Stimulus Profile Editor for new project. VeriStand Editor logging specification file and Data Logging workspace control do not have automation API and cannot be controlled programmatically from TestStand.