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 XILYou 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.