Table Of Contents

Implementation Differences and Limitations with the ASAM XIL Interface

Last Modified: June 10, 2021

VeriStand's ASAM XIL implementation deviates from the ASAM XIL standard in areas such as signal generation and capturing.

Implementation Differences

The following table displays implementation differences.

Process Implementation differences
Signal Generation
  • ConditionWatcher definitions cannot be saved in the STI format when a SignalDescriptionSet contains ConditionWatchers as StopTriggers.
  • Signal generation operations cannot write to model parameters.
  • Signal generation processes create temporary real-time sequence files in the temporary directory.
Capturing
  • When Capture.DurationUnit is set to eSAMPLES, VeriStand ASAM XIL assumes the data capture rate was set during capture creation.
  • Capture.Stop() may take longer than expected to complete execution. The function only returns a value after flushing log data into files and finishing post-processing.
  • Capture.Fetch() might not return the latest samples because of buffering.
  • VeriStand logs data to TDMS despite what capture result writer you choose. The data is later processed by either an MDF or in-memory capture result writer.
Miscellaneous
  • Condition Watchers conditions support the syntax, operators, and expression functions that VeriStand real-time sequences support.
  • Signal generation and capturing are not supported when the gateway is running on a machine other than localhost.

Limitations

The following table displays known limitations.

Process Limitation
Capturing

Capture sessions ignore data logging errors. ASAM XIL API users will not receive an error notification. Instead, the capture will immediately enter the eFINISHED state and cease logging data. Untriggered captures also cause this state change. Capture results and .mdf files contain logging data until when the error occurred.


Recently Viewed Topics