VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Veristand 2020 questions

Hello all,

 

My company is in the process of evaluating Veristand 2020 (running on Windows 10 x64) and have a few questions:

 

1) When developing screens using the nivsscr format the screen seems stuck in the main Veristand editor window, even after deploying and connecting to the target. Is there a way during runtime to "pop" the screen out of the main Veristand window so it runs as it's own window, similar to the Workspace screen?

 

2) The documentation states that multiple screens can be displayed at the same time when using the nivsscr format. So far I haven't been able to figure out how to do this; how do you display multiple screens at once?

 

3) Some basic UI functionality like being able to change colors programmatically or grey out controls/indicators based on channel values doesn't seem to be possible in Veristand. Is that correct? If so, is there a way to write a standard LabVIEW front panel that can be displayed within Veristand instead?

 

4) The real-time sequence / stimulus profile editor is a cool piece of tech. That said I don't see a way to call LabVIEW VIs during a real-time sequence step. We'd like to integrate one of our products as a custom device by wrapping our existing LabVIEW driver. This driver includes VI "functions" (start / stop / upload / download, etc) that cannot be wrapped into a channel variable because they require multiple inputs/outputs, so we'd like to find a way to trigger these VIs on demand from a real-time sequence. Is there a way to do this?

 

5) Related to question 4 - I see the default custom device template includes an event structure for responding to commands. This might let me achieve the functionality I was looking for in question 4. But I don't see a way to send a command to the custom device from a real-time sequence (for example, sending "COMMAND [ARGS]" to the custom device to execute some command). Is there any way to do this in a real-time sequence step?

 

Thanks!

0 Kudos
Message 1 of 2
(2,104 Views)

Hi shansen1,

 From my experience:

1) Since Veristand 2019 it's integrated - I'm not aware of any way of popping the window out. Only the old Workspace window can float...

 

2) Don't know, haven't tried.

 

3) There's no API for UI Manager. However, it's possible to write a standard LabVIEW VI that will interact with Veristand channels using Veristand API. Bonus thing is that it'll be floating and not connected to the Veristand window. You can even hide Veristand and operate entirely from the external VI.

 

4) If you wrap your driver into a Custom Device, you need to expose command channels and react to them - as far as I know, only way of having RT sequences interact with anything else is to write a channel.

 

5) See 4. You need command channels. See e.g. https://github.com/NIVeriStandAdd-Ons/Diagnostics-Custom-Device for an example of how this can be done.

Piotr F.
Hardware Engineer @ ZF
0 Kudos
Message 2 of 2
(2,000 Views)