Hi Starting to evaluate using NI Veristand(2018) via ASAM-XIL (MAPort) and did some initial performance tests reading and writing values to aliases in the Engine demo using Python. My current setup is running python using the ASAM-XIL API on one computer and Veristand on another, connected via Wifi. Read averages on 1-2ms, sometimes slower ~6ms, something that seems rather ok. Write is in the range 30-60ms which to me seems very slow given that the network added latency part of it should be less than 1ms. Is this what one can expect? Is there a obvious reason on why(update loops in Veristand?)? Other experiences or ways to improve? Best regards! Kristofer

VeriStand

NI Veristand via ASAM XIL - MAPort: Expected latency on write?

Author

We did test against RT target but with about the same results.

We did however also test using NI's own Veristand client API, giving much faster writes, ~1ms. (not sure about the details of exactly what was verified except that the synchronous call only took the specified time)

https://buildmedia.readthedocs.org/media/pdf/niveristand-python/latest/niveristand-python.pdf

from niveristand.clientapi import ChannelReference

alias_ref = ChannelReference(variable)
print(alias_ref.value)  # Read
alias_ref.value = new_value  # Write