Additional NI Software Idea Exchange

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)

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

The current Device Driver Installer dialog is not obvious to use. First of all you have to figure out which drivers that you need for your products and then you would probably prefer to remove other unnecessary drivers. However, this is a tedious process with a lot of dependencies.

I have seen many people just installing everything (with its drawbacks) to be safe, eventhough they only needed the NI RIO driver.

I'd like to see a more user friendly dialog where drivers are automatically selected.

My suggestion is that the user instead filters out the drivers on a product level like this:

Let say you choose Modular Instruments. Then next page could let you filter on what type of instrument you have; Scopes, FlexRIO, DMMs, RF, Switching etc...

One of the buttons in the bottom would be something like "Add more products?" so you could iterate this process and finally all needed drivers would be filtered out.

What do you think?

/Pelle - NI Sweden

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.

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 NI.com (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.

http://digital.ni.com/public.nsf/allkb/3114EE73A39F1300862578BE0059A895

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)

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!

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.

View All (1)

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.

Shane.

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.

View All (1)

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

http://forums.ni.com/t5/NI-Applications-Engineers/DIAdem-is-double-checked-out-from-VLA-when-several-versions-are/td-p/2139600

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!

Cheers!

Shawn S.

View All (12)

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)

View All (4)

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)

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

Run Time Driver- 488.2

Is this where to discuss problems connecting a PXI-1033 using NI-MAX?

MAX: Create Global Virtual Channels with Internal Physical channels

Measurement & Automation Explorer behaviour

Simplified Device Drivers Installer

MAX - Allow wildcards for batch renaming channels in tasks

Download Option for Measurement and Automation Explorer

MAX - Identify Functionality of Detected NI Hardware

CDaq Digitial IO documentation needs information on correlated devices

MAX: add an option to specify the proxy settings

Improve the camera management in MAX

VLM and Flex Support: TIMEOUTALL Option

Driver versioning and multiple parallel driver installations

MAX Print Task, Configuration

VLM and Update Service: Allow Administrators to control what patches are installed by clients via Update Service

VLM: Set Software Check Out Presidence to Avoid Checking Out Multiple Concurrent Licenses

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

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

MAX

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