The built in CAN information channels for timestamp and time difference are useful. However, to detect a dead CAN network, I'd really like to know the time since a message was last received. The time difference doesn't work because it waits for a next frame before computing the time difference. If I have a 10 Hz frame that is not coming in, it will just display 0.10 s even if no new frames come in. I'd like to have a time since the last message so I can detect if the message is no longer coming in. I was thinking of doing a difference between system time and the most recent receive time, but system time is relative to the start of VeriStand while the CAN receive time seems to refer to real world time. I hear that real world time will be available in VeriStand 2012, so we can more easily do this checking in a calculated channel, but it'd be great to have this feature as a CAN information channel. Thank you.
Make the Measurement & Automation Explorer ( MAX ) Import Assistant Window resizable, because now not all informations are visible to the user:
I'd like a way to select/deselect dependencies that get sent to the target upon deployment. I understand that all dependencies are necessary for a project to run. However, I deploy one system definition to many targets, and often there are very minor changes that don't need a transfer of all the dependencies which takes time. Also, the fact that the default is to transfer all dependencies means I need to keep every computer updated and sync'd or else a deployment could fail. I'd like the ability to manage which dependencies to transfer and potentially overwrite. Thank you.
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
I'd like to see the Calculated Channels in System Explorer displayed in something other than the evaluation order. I'd like to sort by name due to the large number of calculated channels that I have.
Editing the NI VeriStand Workspace is a very time-consuming job. Especially after arranging a huge number of controls and indicators it is a pain to drag and drop each object in order to move the whole arrangement to another place.
Improvement: If the user could mark multiple objects at one time he could move them all together. The selection could be done by holding the Shift or Ctrl key or just by framing them with a selection box.
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.
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 )
Is there any development in improving the pallet of Calculated Channels? The new stimulus profile editor has a very large list of mathematical and logical functions while the Calculated Channels pallet is very limited. Thanks.
Also, it'd be great if the conditional could be a bit more flexible (e.g., allow multiple conditions) or be changed to a switch/case type function.
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.
The Project Explorer is inoperable when the System Definition File is open.
I frequently want to open the Workspace or Stimulus Profile Editor while working on the System Definition File.
This should be possible because it is already possible to let the Workspace open before you start the System Definition File.
Currently, In VeriStand, you can refresh Models if you made a change or added/removed channels. I would like to be able to refresh custom devices so I do not have to completely remove it and add it again when I add or remove a channel.
You can not choose multiple Workspace objects to move in VS 2011, so it is time-consuming to organize the Workspace. I hope that 1. you can choose and move multiple objects at the same time 2. you can align object by alignment tool like below images.
In most places around VeriStand, channels can be searched and filtered. However, in the channel logging pane of the simulus profile editor, one must manually dig down through the nodes and select channels independently which requires users to know exactly where the channels are in the structure. This is a pain for large systems (we have 4000 channels including CAN and 2000 channels excluding CAN). Thank you.
Why don't we integrate PuTTY or some version of it into MAX? "Console out" is powerful troubleshooting tool for all NI RT targets and more because it tranfers vital information such as errors and IP address information regardless of whether you can find the device in MAX. It's especially useful for devices that don't have hardware dipswitches. It's a great tool, but is useless without a program like PuTTY. Hence, my suggestion remain to integrate PuTTY or some form of it into MAX.
To raise the visibility of the increasing number of NI VeriStand add-ons available on the website, I suggest we put a button on the Getting Started Window of NI VeriStand that takes the user to www.ni.com/veristand/addons.htm
This doesn't have to be a button on the window, it could be in the menu.. under file, tools or help.
In System Explorer, you can not change the order of items by drag & drop. It is better for users to change the order of items like Calculated Channel.
However, I guess better mapping usablitity will resolve this problems. If the mapping is like below image and the order can be changed, it is better for users to map all things.
When configuring a system definition file in VeriStand, you can spend a lot of time expanding all of the tree items even if there's only one other item under it. I think it would be nice if the tree auto expanded down to the first set of user-added branches. For example, say I have a simple System Definition as shown below:
If I want to get down to the CAN port I've added, I need to expand Controller, Hardware, Chassis, NI-XNET, and CAN. It would be nice if, assuming the only hardware I've added is the CAN Port, that when I expand Hardware it automatically expands all the way down to CAN 1 since it's the first node I've added. Obviously if I'd also added a DAQ card I'd be ok with it only expanding down to under chassis. Alternatively, or in addition, a button that completely expands the currently highlighted section would be nice.
Versioning is often a fairly important matter when it comes to long/large projects. When a new FPGA bitfile is generated in LabVIEW, there's a possibility to change its version (in the build specification). As a result, a parse of the .lvbitx file as text file can be used to decypher the aforementioned version (it's following the <BuildSpecVersion> tag).
Though, there's no simple way (aside of making a Custom Device or modifying the accepted tags in the xsd file)) to get this information in Veristand after importing a new FPGA personality. The version may be important, but more information about the bitfile might need to be made public in this window :
In fact, there are a bunch of information that are readable in VeriStand about the model imported (name, version...). Once more, the FPGA needs the same feature ;-)
Have a great day,