Mapping in VeriStand 2011 consists of only text, but user could grasp the whole mapping if the number of connections is increasing. So, visualized mapping tool like dSPACE ConfigurationDesk as below image must be good user interface for users.
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.
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 )
If you want to exchange a model you have to reconfigure many things. You could use Aliases to reduce the effort for the Workspace and Workspace Tools.
But in the System Explorer you can only use Aliases for Calculated Channels.
Please make it possible to use Aliases also for Mappings, Alarms and Procedures.
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.
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.
Make the Measurement & Automation Explorer ( MAX ) Import Assistant Window resizable, because now not all informations are visible to the user:
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.
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
Hello NI guys,
I want to know when NI will develop a better software than MAX, each new release is more unstable than the previous one.
With the release 5.1.0f0, each MAX execution starts or stops by a crash. It's totaly unusable.
I want to change the name, it hangs !
I want to see the boards on the target, it hangs !
I don't know why it hangs, I can use a computer with only NI Products and nothing else, it will hang on each time.
I'M NOT ALONE IN THIS CASE !
Please hurry up and develop a new software to setup the target !!!!
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.
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.
Say I have profileA which calls sequenceB which calls sequenceC. sequenceC needs to access UserChannelX defined in the system definition. Currently, the only way to do so, I believe, is to pass UserChannelX into sequenceC as a parameter which means it needs to be defined as a parameter in sequenceB as well, even if it's not used in sequenceB. This greatly increases the number of arguments of a sequence which may never be used but is necessary in order to give the lowest sequence access to system definition channels. It seems like we should make sytem definition channels directly available at any subsequence level (sort of like how global variables can be referenced anywhere). Thank you.
It would be nice to add some controls in VeriStand workspace screen objects in order to handle macros.
The two controls could be linked to a combobox which could list the content of a "Macros" directory, located under the project root.
These controls could be helpfull when you want to build a simple screen, for users without big knoledges about VeriStand.
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.
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.
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.
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 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.
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.