Additional NI Software Idea Exchange

VeriStand natively includes several Action VIs that provide the critical ability to run code on the gateway when a certain action is performed. Most often, this is used for executing code that cannot be run on Real-Time but needs to coincide with an event within VeriStand. This can also be achieved with VeriStand services, but is more complicated. I think that additional Action VIs, specifically ActionVIOnDeploy and ActionVIOnUndeploy would be very useful. And I'm sure there are additional ActionVIs that others would find useful.

Benefit: Simplify the process and reduce errors when using FPGA personalities

Idea: Querry the user-generated FPGA diagram and automatically create the XML file. Additionally, have some kind of editor/viewer for the XML file that would present the information similar to how it is presented in the System Explorer but allow the user to edit certain values (or just make it editable in the system explorer). Some items would be read-only (items specific to the bitfile communication) and others would be editable (heirarchy, scaling, etc).

Ultimately, the process for using FPGA Personalities would be:

- create FPGA VI using NIVS interface/template

- select interface in "utility/view" or System Explorer (XML file automatically generated)

- edit default settings if desired

View All (5)

For security reasons, many customers using Volume License Manager to administer licenses to client machines do not authorize users to download and install anything from the web. Therefore, if a critical patch is released, the client machines are unable to download this unless it is distributed by the administrator. It would be useful for the VLM administrator to be able to configure the Update Service such that all Users can run the Update Service but the service has been configured to point to an internal network share rather than an internet location outside the firewall. This way, the administrator could make critical updates and patches available for the client machines and the clients can be notified and install them.

View All (1)

View All (7)

[Edited on 8/28/2014 by moderator Diego Carvajal (dcarvaja)] [Image included in original post as requested] To help debug medium and large real-time test sequences, it would be very useful if there was a sequence step that allowed the user to specify a console message.

Much like the Print Debug String VI helps debug issues when building custom devices, this step would allow the developer to insert specific console flags and see what part of his/her real-time sequence is executing.