From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Additional NI Software Idea Exchange

Post an idea

View All (4)

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).

MTO

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?

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.

View All (3)

Dear NI Community,

it would be a good feature, if it'll be possible to see directly in NI License Manager list of licenses, and expiration dates - all at once. If it'll be possilbe to export it, it would be really great, because then you can sort them, check what will expire first, and so on.

Because when sometimes we use trial keys for toolkits, activated at different time - it's a mess, because one needs somehow to track when trial license will expire, and when you need to ask for new one / to purchase final license, and so on...

Why don't to make it more easier for users then?

Thanks a lot,

Sincerely, kosist90.

View All (1)

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 !!!!

Best Regards

CFOE

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.

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!

View All (8)

Hello,

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.

View All (1)

Hello

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

Michael

Expanding the Remote Systems category in MAX or launching the NI Network Browser only shows devices in the same subnet that the used host PC is in. However networked devices (LabVIEW Real-Time systems or Ethernet CompactDAQ chassis) are often located on different subnets.

In order to keep the discovery time low, only one subnet should be selectable at any time.
The currently selected subnet (default: local subnet as today) should be indicated:
"Currently showing devices in the [local|[1...255]] subnet. Click here to change"
Some area or button allows users to pick a different subnet and once the user populates the field, MAX or the NI Network Browser refreshes.

View All (2)

Hello,

I recently had a service request where a customer was unsure why 30 day evaluation licenses were not made available when using unmanaged concurrent name based licenses. I explained that this was expected behavior.

Then I generated a license file, used a test machine as a server, and my work PC as a client.

Witihin NI License Manager on the client machine, the software package I checked out showed as 1 of 2 licenses checked out.

However, on the admin side, there was no notification of the number of checked out licenses. The total was displayed as well as the Total Seats Granted. However, the total seats granted is unmanaged, so this number stays at 0 even once a license is checked out to a client machine. I believe that another column should be added on the server copy of Volume License Manager to display the number of licenses currently checked out as is displayed on the client (1 of 2 licenses checked out).

Server View While License is Checked Out and Server is Running

Client License Manager Screen Shot While unmanaged name based license of LabVIEW 2011 is Checked Out

View All (7)

View All (1)

It makes sense to run the Volume License Manager on a server-based environment.

Typically these environments are managed by the IT departments with restricted access to users.

Managing licenses like it needs to be done with the Volume License Manager is sometimes the responsibility of key-users outside of the IT-department.

With the Volume License Manager have to be operated as an application on the server, this often makes it difficult to get the necessary access rights (remote desktop...) granted from the IT department.

It would be much easier to do the license management via a web based interface provided by the Volume License Management Service.

View All (3)

Title pretty much says it all. I can create them programmatically,why not with a configuration?

Workaround: create the channel programmatically and save it to the configuration.Very inconvenient.

<1% Use case? Perhaps.

I can display it in MAX and it shows the internal channel. It's not like it's hidden from anyone. Being able to select internal channels from a dropdown, just like a Channel Control in LabVIEW, would be entirely logical and consistent. Default behaviour could be external channels, with filter checkboxes just like the aforementioned control.

View All (3)

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:

Cam0

Cam1

Cam2

Cam3

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!

View All (3)

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

Additional NI Software Idea Exchange

Allow the Ability to Compare I/O Trace Files Side by Side

Automated creation of volume license installers when new software is released by NI

MAX: add an option to specify the proxy settings

NI License Manager: display list of licenses, with expiration dates; all at once

Measurement & Automation Explorer behaviour

MAX - Allow wildcards for batch renaming channels in tasks

MAX - Identify Functionality of Detected NI Hardware

Allow VLM Managed Concurrent Licenses in Groups to be Limited to the Number of Available Licenses

MAX should view an error if the NI low level services are not running ....

Improvement for rename channel dialog box in MAX

Allow the NI Network Browser (and/or MAX) to display the remote devices in a subnet different from the one where the host system is located

Display # of checked out and available licenses on Server using unmanaged user/computer licenses

Measurement & Automation Explorer on Touchscreen Interface

Add web-based configuration for Volume License Manager

MAX: Create Global Virtual Channels with Internal Physical channels

XNET Sessions in MAX

Improve the camera management in MAX

TWAIN Protocol Support

Software tools to implement audio and speech analysis standards

Project and Workspace Context in MAX