Additional NI Software Idea Exchange

Community Browser
Showing results for 
Search instead for 
Did you mean: 
Post an idea

NI-DAQmx Tasks can frequently have dozens of channels, sometimes hundreds.  Renaming each channel can prove tedious when the format needs to be more complex than rootname_#, indexed from zero.


This change will allow developers to batch rename channels in a more flexible format, saving task setup time.


This idea includes:

1. Using rootname as it is now, allowing for all channels to have a common base name

2. Creating wildcards for naming channels.  Each channel would then have the base name, a changeable separator character if specified, and an incremented number or character(s) specified by the wildcard.  Examples include:

a. Current_[001] = Current_001, Current_002, Current_003...

b. Temp [AA] = Temp AA, Temp AB, Temp AC, ..., Temp BA, etc.

c. [05]_Reactor = 05_Reactor, 06_Reactor, 07_Reactor, etc.

In simple, to have a way of downloading different versions of MAX from without having to download drivers.

This would be useful if problems with MAX arise whereby it needs repairing or even if a specific version of MAX is required.

A piece of feedback received from a regional seminar:

It would be great if MAX could tell you what different modules are used for (e.g. NI 9235 - strain gage module or NI 9213 - thermocouple module) or include information such as what is on the product page for the module. Of course, you could rename the modules as soon as they are detected to make it easier to identify but you would still need to go one by one matching up a number to the measurement type.

The various Compact DAQ digital IO modules available can be either correlated or not.


However, there is no information regarding this in the various device specifications.


The information is required because a correlated device is required to access the chassis counters.


A comparison table for correlated devices does exist on (see link below) but the user has to search for it.  It would be far more useful if it were included in the device documentation and specifications along with a supporting information.

I wrote this idea after having spent a lot of time trying to understand a strange connection problem between MAX and NI-cDAQ 9188 ethernet chassis.

As a matter of fact I discovered that MAX uses the proxy settings made inside Internet Explorer (in Tools >> Internet options >> Connections >> LAN settings). If you set a proxy inside IE, MAX uses this proxy trying to connect to a NI cDAQ ethernet chassis.

If you set the same proxy inside Firefox (for example), MAX doesn't use this proxy settings.

For this reason you must tell the customer how to configure the proxy inside IE in order to be sure that MAx is able to connect to the NI cDAQ ethernet chassis. And if the customer has already set the IE proxy as requested for network connection, it could happen that he must change this settings, and this could be a problem.


I suggest that MAX (and other NI software) should have its own proxy settings (has Firefox has) so that it would be possible connecting to cDAQ ethernet chassis even with "strange" settings of IE proxy.

If you add a NI camera to the computer, Max will recognize that.

The camera is added as Cam0.

In the back a file gets created which includes the Type, Name, Serial number,… of the camera.

If the camera gets broken and you put in a new one it gets added as Cam1. ?!?

If you only have one Camera it will be easy to scan pragmatically and

use the one that you find. But if you have several cameras you get a problem.


For Example:







You want to change camera 1 and put it out. Now you put the new one in.

Max creates Cam4 because Cam1 is reserved for the other one.

It is not possible to delete Cam1. Only if you go to the specific folder and

Delete the special .iid file the port is no longer reserved.


Please implement the management of this directly in Max!

Currently, our NILM license daemon doesn't support the TIMEOUTALL function when used with a FlexNet server. The purpose of the timeout is to cause an application to release its license if idle, which is useful in the case that a user doesn't realize LabVIEW or another NI program is still open on the client machine. The TIMEOUTALL command is a standard FlexNet option.


It would be useful if we provided this function, or provided a similar function in the Volume License Manager server product.

Before I start, I want to make clear that I am fully aware that my suggestion is probably linked to some crazy amount of work....  That being out of the way:


I often have to switch between LV Versions and have on more than one occasion run into the rpoblem that different versions of LV work with MUTUALLY EXCLUSIVE sets of drivers.  This means that I cannot (_for example) have LabVIEW 7.1 and 2011 on the same machine if I need to be coding GPIB functionality over VISA because there is no single VISA version which supports both 7.1 and 2011 (image below).



Of course these days we just fire up a VM with the appropriate drivers but for much hardware (Like PCI or Serial or GPIB) this doesn't work out too well.


Why can't we have some version selection ability for hardware drivers.  Why can't I have VISA 4.0 and 5.1.1 installed in parallel and then make a selection of which version to use in my project definition?  I know that ehse drivers probably share some files on the OS level so it clearly won't work for existing driver packages but for future developmend it would be utterly magnificent to be able to define which version of a hardware driver (Or even LV Toolkit like Vision) should be used ina  project.



Wouldn't it be simpler to wire your DAQ systems if there was a way to print the tasks? This is exactly what I'm proposing - a 'Print' function from the menu to print the channel order for a specific task that would also contain the system configuration. See below:




Would create a file that looks similar to this:




I'm not saying that this is the end-all-be-all, but some way to print the channels contained in a task would simplify my life.

For security reasons, many customers using Volume License Manager to administer licenses to client machines do not authorize users to download and install anything from the web. Therefore, if a critical patch is released, the client machines are unable to download this unless it is distributed by the administrator. It would be useful for the VLM administrator to be able to configure the Update Service such that all Users can run the Update Service but the service has been configured to point to an internal network share rather than an internet location outside the firewall. This way, the administrator could make critical updates and patches available for the client machines and the clients can be notified and install them.

Currently licenses use the sort key word within a server's license file to specify the priorotized check out of similar software products ( a preference to check out DIAdem professional over DIAdem Advanced for example when a user has permissions for both).  With concurrent licenses, right clicking on a software product from a client's License Manager application and selecting the Do not Allow License Request from the context menu as shown below will also bring about this functionality.


Without a set preference, sometimes two licenses are checked out, and this is a known issue:


DIAdem is double-checked out from VLA when several versions are licensed


Do Not Allow License Request for Concurrent License






Sort Keyword Within a Server's License File






My suggestion is that we create a way within VLM to modify the server's *.lic file (by changing sort key word's value) to reflect software check out priority.  Currently this change can be made by manually modifying the sort value in the server's *.lic file.  This works since the server's license doesn't need to be resigned after said modification.  However, it would be nice if this change could be made through the VLM user interface and the *.lic file would be modified behind the scenes.



Feel free to comment or Kudo!




Shawn S.

As I understand it now, with VLM, groups were introduced.


I could create a group of Developers that has two members and I could create a group of New Hires with 8 members.  Then I could issue permissions to the ten licenses of LabVIEW that I purchased to each group. 


When I add the LabVIEW licenses to the Developers Group I notice that only 2 of the 10 licenses are used for the members of the Developer group.  Then I add the remaining licenses to the New Hires group.


The problem that I see with groups now is connected to what happens when more people are hired at the company.


If two more people are hired at the company, and all of the new hires are using LabVIEW licenses, then the Developers will see a message that all of the LabVIEW Licenses are checked out.


Could R&D make a way to lock the number of concurrent licenses in a group? For example, if we could lock the 2 concurrent licenses issued to the Developer group, then in the previous scenario when all ten of the new hires attempted to open and use LabVIEW, two of the licenses would be reserved for the Developers and the last two New Hire members to attempt to open LabVIEW would get a message that all licenses had been checked out.


I think this could be a very useful addition to the current functionality of VLM and that it could benefit many companies who utilize it!  Feel free to post, comment, or kudo.  Thanks!



Many times, I find myself wanting to compare different I/O traces side-by-side, but I can only have one instance of I/O Trace in memory and hense can only view one capture at a time.  Would it be possible to view two different captures within one instance of I/O Trace?  I believe a lot of people would appreciate either a split screen option or the ability to open another instance of the I/O Trace application in memory.




Shawn S.

How about a separate Discussions Forum for MAX?



I had recently a problem with Max : I got an error when viewing my NI hardware.

MAX was running very slowly ... like when its database is corrupted.

All board autotests were failed !


With the NI FRANCE support, we fixed the problem ! In fact one of the NI low level services was not running !

( NI device loader was not running )

We fixed the problem by changing the restart option of the windows service !


The problem was, that MAX wasn't working properly ... and was showing to me hardware errors !

But it fact there were no hardware problem, only a software issue !


It would be nice if MAX could check the working status of all its required components ( services ... ) !

A message at MAX startup saying "The NI device loader is not running !!! Max will not work properly" would have save us a lot of time !


I think that showing the problem at the launching of MAX is more user friendly that to let MAX hang and show a bad hardware configuration.



Thank you for your help. 


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.

Posted this in Data Acquisition Ideas as well, but it seems like it would be implemented with something like MAX, so...


When dealing with various remotely deployed cRIO hardware configurations, it may be impossible to keep a sample configuration of every type of system we ever sell.  Unfortunately, if upgrades or revisions are made to the base code in our system, remotely deploying to our customers becomes impossible unless we have their exact configuration on-hand for the programmers to compile.  Remote connection to the hardware for this type of operation is also not typically possible.


To be able to simulate or emulate a full cRIO system (processor & hardware modules), then compile the RT code for deployment on that system as if it is physically connected to our development system would be ideal.  This would allow images to be created, which can be sent to customers for local deployment at their facility.  Dramatic decrease in "hardware library" requirements on the development end, reduction in "on-site upgrade" service trip costs to the customers.  Plus, easier for OEMs like me to justify the move away from PLC types of hardware and towards cRIO, once you take away some of the potentially nightmarish continued support and update issues involved with basing systems on cRIO platforms.


I suggest including TWAIN protocol support in the IMAQ Vision drivers.  

Kira T


This is a very small issue, albeit an annoying one:

When using <F2> to call a rename dialog in MAX, it would be very intuitive to have the focus on the name field, since this is ultimately the field of interest for the user.


Currently, the dialog has no focussed field and pressing <TAB> does not even move focus except to the <Abort> field.


So now, I do not only have to change from keyboard to mouse, but also, I have to mark the entire name in the field to change the name. As I tend to give meaningful names to my channels, this makes for a good many time-consuming "mouse/keyboard/move/click and back" journeys


If the <TAB> key would at least move focus, this would be equally helpful.

 Thank you



When using the Read/Write Variables to INI File step in VBAI and not selecting the Ethernet option the code that is generated still includes this step and therefore requires the Ethernet IP toolkit to run the code.  I suggest that when the box is uncheck then the generated code not require this toolkit becuase the VIs are going unused.