As the Idea : Controls for macros , it would be nice to add screen controls in order to handle with procedures !
For the moment, VeriStand RT procedures are only launched using alarms !
It could be usefull to be able to launch or stop procedures using screen objects. (Like the Model controller !)
VeriStand suppot 32 and 64-bit aligned fixed point data: http://zone.ni.com/reference/en-XX/help/372846G-01/veristandmerge/creating_custom_fpga_configuration_file/. Please add support for FXPU8, FXPI8, FXPU16, and FXPI16. This can potentially reduce the number of DMA reads/writes by 4.
HI That will be SUPER, if you can add extra option till pop-up menu "Create/duplicate Device as Simulated". And reversed option (to create Device from simulated one) when you will like to test software with real hardware. That will be also necessary to do check box to select, which you will like to use. For Tasks purpose, they have to also know which one they have to use.
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.
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.
Although user channels and alarms can be created under folders for better organization, I don't see a way to:
- move channels/alarms in folders out of folders (without first deleting them and recreating them outside of the folders)
- move channels/alarms out of folders
Being able to drag and drop in and out of folders would make organization easier. Thank you.
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.
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.
the company I work for designs automotive infotainment products, and we used products from NI extensively in product validation an testing, including TestStand, Labview, DIAdem, FPGA, RT. etc...
In order to simplify license management, we chose to used the NI Volume License Manager (VLM). This provides centralized managment of licenses, including easy addition and removal of licenses, as well as license recovery from PCs no longer in service (broken or decomissioned by IT).
Since I am the technical lead for test system development, it falls to me to perform license capacity planning, request disconnected licenses, manage license groups, and all the other administrative things that go with license management. I am not, however, in the IT department, and since the VLM runs on a Virtual Machine inside the VM park, I always have to request license changes from our IT specialists.
I would very much appreciate it if there were a tool to remotely administer the VLM. This would allow the IT department to give me access to just the VLM to perform administrative duties there, sort of like the MMC in Microsoft Windows Server lets users administer remote servers.
I was asked to post this here instead of in the VLM forum:
Every time there is a new update of LabVIEW we typically hunt down the installation disks from ni.com as soon as they are available, and start the process of making volume license installers...(Or, if the update seems less exciting, we wait patiently for the shipped DVDs).
I wish it the whole provcess could be made smoother. Based on the volume license installers we have, the VLM could simply subscribe to newer versions.
When 2014 comes out, the package would automatically go out to all the VLMs out there, and new volume license installers would pop up on our local VLM as soon as the software was ready...OR, alternatively, the VLM could be hosted by NI instead (possibly supported by a local VLM for offline use), so that the process of creating new installers were really done by NI (or automatically by NI hardware that is) based on whatever setup we as VLM admins had chosen...and the source material from NI.
(This idea came about as a side note to this related discussion about LabVIEW cloud services).
PS. Why do I have to assign this idea a label when the only available labels (I'm not allowed to create a new one) is unrelated to MAX, Veristand or the System Config API?
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.
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.
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.
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.
Dear NI community,
let me describe you one of my ideas.
It would be good to have a feature of "copy-paste" simulated devices in NI MAX. One creates a device, setups it, selects it, copy Ctrl+C and paste Ctrl+V - and device will appear below in the list of hardware.
For example, I was now adding four 1-slot cDAQ chassis, with measurement module. Chassis are the same, modules also - we have such setup (don't tell, if something, that we could use 4-slot chassis, b/c it was requirement to have 4 separate chassis). So, I had to do the same operations (create chassis, add device, rename) four times, and it took like 2 minutes approx. But in case of copy-paste feature, it would take 30 seconds, no more.
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.
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.
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,