VeriStand suppot 32 and 64-bit aligned fixed point data: http://zone.ni.com/reference/en-XX/help/372846G-01
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.
It would be nice to add a tool like RAD (NI Replication And Deployement utility) directly into MAX.
But a RAD compatible with all Targets LabVIEW Runtimes.
... a kind ok target cloner, saver , restorer ...
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).
Send the VLA log automatically as notification to the VLM administrator.
The VLM log can send the logfile automatically to NI, however this is not an option when the server is not connected to the internet. In this case, emails can be send to the administrator. It would be great if the VLA log will be attached to the email, so that the administrator can forward this to NI.
When running a stimulus profile in NI Veristand, there is currently no direct way of enabling/disabling Alarms in real time sequences. It would be great to have this capability for use in real time sequence when you are transitioning a channel value with an initial set of abort limits to a new set of abort limits. With the current set up while transitioning depending on the rate of change of the channel value we may hit the upper or lower limits to an abort condition and trigger a procedure even though we actually meant to change the channel to different value with new channel limits.
It is always a pain finding new hardware in NI MAX. You never know the IP Address. It would be great if MAX had the capability to find hardware and configure network settings via ethernet Data-link layer 2. You should be able to identify all NI hardware with your common vendor MAC prefix and communicate network settings. I have seen other companies use this to find and configure their hardware on the network regardless of the ethernet adapter configuration.
It would be great if we could disconnect per user not every software attached to the user but only some of them. For example, if I only need NI Diadem offline, I only disconnect NI Diadem and not the other software, the other software could be available for other people.
Another thing, the start date of the disconnected license should be proposed as a choice when creating a disconnected license file.
Have à good day, bye.
With VLM 3.1, a number of default reports are available (License Activity, Client Activity, ...).
Some of the default reports (License Activity, Seat utilization and Seat Utilization (Concurrent)) have a License field that the user need to complete.
The issue I have is that we are using different licenses (Dev Suite, Dev Suite with Data Management, Dev Suite with FPGA, ...) and that I cannot generate a report that includes all licenses together.
My request is to have the possibility to select "All licenses" in the License field.
I am more than willing to validate this feature in an alpha/beta release.
Ideas for NI Multisim software:
1. Schematic: To make an option to lock REFDES during copying circuit to the new sheet.
2. Schematic: To add power bias annotation for a components.
3. Schematic: To add active probe (see CircuitMaker 2000 solution).
4. Schematic: To add operating state annotation for transistors (active, cutt-off, saturated).
5. Schematic: To set some min and max limits for a voltage, current or power (they shall be visible in Grapher when you generate the plot).
6. Simulation: To add circuit optimizer with various algorithms: Hooke and Jeeves, Levenberg-Marquardt etc.
For example: I would like to find a resitors values according to voltage limits.
7. Simulation: Current Worst Case simulation can not find right solution for a non monothonic functions, so please consider to add Hooke-Jeeves algorithm to find real min and max.
8. Simulation: To add Root Sum Squared (RSS) method.
9. Simulation: To add assymetrical tolerances option for a components (resistors, capacitors, voltage and current sources etc.)
10. Simulation: To add additional drift tolerance (aging, humidity etc.) option for a components (resistors and capacitors). Please create an option to turn ON and turn OFF additional drifts globally for a whole circuit design and for specific component.
11. Simulation: To add component stress analysis but more advanced. The goal is to check maximum dissipated power according to derating power characteristics for resistors according to current operating temperature (TEMP parameter for circuit simulation) and maximum voltage for a components (resistors, capacitors).
12. Grapher: To add histogram plots for a Monte Carlo simulation incl. table with data: MEAN, SIGMA, UCL, LCL:
13. Grapher: To add option to generate one report for Worst Case EVA, RSS and Monte Carlo.
14. Grapher: To add 3D plots (see circuit optimizer).
15. Interface: Batched analysis is fine, but it would be a good to see TEMP parameter visible in main window.
16. Interface: Fast BOM import for Excel and txt file (incl. some component parameters included value, TC1, max operating voltage and so on). For a quick changes on schematic.
17. Simulation: To add Worst Case option to Monte Carlo analysis to check ONLY endpoints values.
18. Model: To add a module that can build a component model from characteristics from datasheet (eg. to track output voltage characteristics of voltage regulator and to build behavioral model).
19. Model: To improve custom component drawing editor (make it handy and efficient like drawing schematic in Multisim). Current solution takes too much time.
The goal of these changes is to focus your product more in professional market where engineers must to find voltage/current limits according to operating temperature limits and component tolerance variation. Your product is good but it might be more oriented to perform these tasks much faster.
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.
It would be nice for real time sequences to be able to provide customizable feedback/dialog info to the user in the workspace. If this is not feasible due to its running on the real time side, printing to the console would be helpful too. This could act as a debugger and user prompt.
The Update Service supposedly already checked in the background and found I needed updates.
Yet when I say “view updates” it makes me wait on a progress bar while it checks for updates.
And then when I click “Upgrades and Service Packs” it has to check AGAIN with another, extra-slow progress bar.
It should just do all the checking in the background, retrieve the full list of updates, and stop interrupting our work to wait on progress bars.
I had to manually enter the properties of 25 frames and their signals (at an average of ~5 signals per frame). That's not fun, especially since many of them were similar.
The process would be a lot faster if I can clone the frames/signals and just edit the fields that differ.
The size of the NI-488.2 driver files is quite large. I have an inquiry from a customer about the possibility of having a driver that just contains the driver to be recognised by the computer, without all the compatibility files for programs such as C++, Visual Basic etc.
For certain customers, there is alot of overhead associated with downloading a file the size of the current NI-488.2 driver, when the compatibility for different environments is not always necessary.
Here at the University I work at we use a large number of license management software (mainly flexlm). This past semester I installed a new license management service that would be used to serve licenses to multiple labs in multiple buildings across campus. Unfortunately after installing it and deploying it to a large number of machines I realized that my Labview license manager had stopped working because both processes were trying to use the default port of 27000. At this point in time my only option was to change the port on the Labview license manager to a new port (in this case 27006). Unfortunately due to the current nature of Labview I now have to visit 100+ machines in my building and elsewhere and point them to <SERVER_NAME>:27006.
A peer here had a similar issue with the Autodesk software Autocad, which runs on a similar license manager. However, Autocad checks a range of ports automatically if their license server isn’t available on the default port. It would be nice if Labview would do the same. That is, check port 27000 for a license server, if not found, check 27001…up to 27009 then store the port in the software. Because of this, we do not have to tell Autocad which port the license server is on and if it changes, nothing needs to be done.
What I am suggesting is that users not be required to point to a given port if the default is not used. Instead, the Labview client look at 27000 on a given server, if not found, it looks to 27001, this continues up to a maximum of say 27009.
Another potential fix for such issues would be to have a registry key that can be updated through group policy. This existed in Windows XP but in Windows 7 this key was removed an instead an .ini files used.