01-27-2023 08:51 AM - edited 01-27-2023 08:52 AM
Hi,
We have used Veristand together with Teststand as well as with the API for test sequencing.
For some long running tests we would like to get rid of the dependency of the host computer for sequencing.
We also have used the real-time sequences, but implementing a long and complex test sequence is a pain and there is no reporting.
Is there a possebility to communicated with the Veristand Engine without the Veristand Gateway on the host?
If there was an API, tests could be executed from a seperate program (pytest) running on the NI Real-Time Linux.
Has someone seen a test sequncer custom device?
01-27-2023 09:56 AM
I am not sure if this API can be used on Linux environment or without gateway.
Getting Started — niveristand-python 0.9.0 documentation
03-21-2023 04:39 PM - edited 03-21-2023 04:40 PM
I would also be interested in interacting with the Veristand engine directly from the Linux OS
Bala
03-22-2023 01:52 AM
Hi,
I guess you could implement a "command server" custom device using any interprocces or network protocol. But the ideal would have been a Linux Gateway implementation or at least its networking layer. I don't know if it's available or will be ever.
03-22-2023 03:18 AM
A different alternative for a real-time sequencer would be a sequencer+reporting custom-device.
The sequencer part of the custom device would load sequence file (maybe even a teststand .seq file) and execute the defined sequnces based on alias names.
A second part of the custom device would generate a result report also based on definitions in the sequence file. Maybe here a Asciidoc report (through the Antidoc library by Wovalabs) could be created or the results directly uploaded to Systemlink.
I think such a custom device is missing the versitile Veristand eco-system. Maybe a shared open-source project?