Additional NI Software Idea Exchange

The VeriStand System Definition API allows you to edit a definition file. While it is mostly used as an offline API, it is also often used in custom devices code, notably thanks to the Item Reference to Pointer function that gives your access to the SystemStorage namespace, an internal representation of the SystemDefinitionAPI.

Unfortunately, there's a hiccup with that. If you want to edit existing nodes in your system definition, it works. If you want to add/remove nodes or sections (say, automatically add an alarm when you add a given custom device channel), the underlying API calls will work but you can't see the modifications in the System Definition tree: my alarm won't show up in the tree although it exists in memory. You'll have to manually save and reopen the *.nivssdf file for that. This can't be a decent workaround for end users.

Would NI R&D be nice enough to provide us with a public function that refreshes the tree (or parts of it if we feed the node reference)?

--Eric

Nb: I currently have a working solution, in case anyone urgently needs this feature.

I created a VI and wrote the description thinking I will retrieve it later in Veristand but it is not the case.

I have to copy and paste it into Veristand.

It would be nice to have teh direct copy.

Hello Folks,

As a developer, I use to have several screens for Test data display, Manual panel, Model execution control panel, etc. As per to the operator any screen other than Test data display is unnecessary.

It will be really good, if we could include the Screen selection in the "User Accounts Manager" with respect to the users like shown below

This option lets the administrator to select the specific screens whichever is necessary for the operator.

-SID

Now you can't drag&drop to move sequence files in Project Explorer. To workaround this, you have to add files under folders after creating folders. The way to workaround is time-consuming.

Thanks,

Saku

I was thinking for very large systems that use the same channel configuration for multiple channels on the system configuration can be very tedious. A work around for this is the API to build a system definition file but for those customer's with limited or no LabVIEW or .NET experience this isn't valid. 

Since we can test the IO channels in MAX by creating tasks for all of our hardware I would like to add the ability to pull the configuration information from a task we've created in MAX and apply them to our channels in VeriStand. So in stead of setting MIN, MAX, input configuration, shunt resistor location and value for 100 channels I can configure it in one location (MAX) and apply the settings to all my Current Channels. 

The other issue is if the channel doesn't support all the configurations from each page then we need to contact NI support to add functionality. Recently I worked with a LVDT sensor for a SCXI chassis. This allows customers to have an instant workaround rather than having for NI to allocate resources to update the page.

By adding MAX task to act as the template for our channels we can edit the parameters for all channels of the same setup from one location (MAX) vs each individual page. This also allows you to test individual channels instantly in MAX to make sure the configuration is valid without resolving other errors across the whole system definition.

Again this is more for deployments where they have 100s of channel similarly configured where configurating each channel is tedious but they are not unique.

Hello,

It would be nice to be able to control the stimulis from a workspace screen.

It would be nice to had a control like this ...

The stimulus list could be filled according to the content of a Project directory. (Project Root / Stimulis )

Thanks.

Manu.net

Whenever I delete a signal (whether it's a custom device, user channel, calculated channel, etc.), VeriStand goes through to delete that signal from anything referencing it. This is often nice but at times undesirable because I may plan to add it back again at a later time with a new custom device with the same signal names, for example. The auto deletion of all references means that I'd need to go back to relink all of the broken references even if the missing signal gets restored later anyway. Some of my channels are used in 20+ places.

I'd like to see VeriStand prompt me or give me an option as to whether I want to delete all references. If I choose not to delete the reference, I understand that an error will show up later if I try to deploy or run. Thanks.