Additional NI Software Idea Exchange

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

right now, if I invoke nivlm.exe /exportClientPermissions C:\foo\bar.txt, I don't get any information about disconnected licenses.

It would be great if it had a column for disconnected license expiration date associated with each item (that would be empty/null if no disconnected license was assigned). 

Would also be helpful if there was also information about home use licenses grated against a user.

 

 

  • MAX

Hi,

 

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.  

  • MAX

Hi

 

attached is a MAX view from a typical process control application: There are dozens of cDAQ-modules there and hundreds of Global Channels.

 

The question is for instance: which cDAQ-modules have any free inputs? There is currently no easy answer to this without physically accessing the cabinet 😞

 

Would it not be very easy to provide a tab in the right-hand part of my MAX-view where I can sort my Global channels based on the physical channel that they refer to ?

 

Thanks HU

  • MAX
0 Kudos

Dear NI R&D folks.

 

It is wrong the time zone for Caracas at the Time Settings configuration (MAX 14.0) . Since december 30, 2007 has been changed to -4.5 UTC. I will appreciate if you correct this bug in future LabVIEW versions.

Best regards.

 

Jesús Hidalgo.

 

 

  • MAX

This is a bit of a feature request for the service request manager and/or as a stand-alone (my NI web) tool!  

 

It is needed because the NI webpage makes it terribly hard to search for CAR#'s and a CAR# is only listed when solved, and only listed for the one version where it was resolved, making it nigh-on impossible to check lists of (new) CAR#s and get notified when they are resolved.

For example, I know this CAR exists, but I'm not sure if it has been resolved and the NI search just didn't find it, or if does not exist (user input error for example) or anything..

no car in search.png

 

  1. The tool should reside on "my NI" but it should be possible to export/share the list of monitored CAR's (so colleageus/companies can maintain one master list of company relevant CAR's).
  2. The tool should connect/check against NI (ideally directly to a back-end database) and return any "public" information related to a CAR, such as "in progress", "known work-around", "details" etc. along with driver/software version where it was resolved (if any).
  3. The tool should present a clear list (ideally with green checkmarks / red cross icons) showing the status of each CAR and maybe a synopsis/one-liner from the description to indicate what problem the number is for.
  4. wish-list added feature:  allow (on a per user basis) the user to add personal notes to a CAR (e.g. this affects projects x, y and z, once resolved, refactor those projects to remove performance intensive work-arounds!) or similar.
  5. e-mail notification (optional/configurable) when the status changes on any of the tracked CAR's.

 

 

As far as how it relates to the service request manager, I would prefer a separate tool but that it also can link to the service request manager as outlined below:

 

A small but significant number of tickets either relate to, or create one or more CAR#'s (or at least mine seem to create a large amount of CAR's).

When a support tech adds / associates a ticket# with a CAR#, ideally this CAR# would be automatically added to the user's CAR Tracking list..

 

In addition it would be great if the back-end database tracked CAR#'s and offered up a list of these numbers in the webpage overview, for example next to the "status" column. Taking it a step further, it would be very nice if NI could make it simpler to check if a CAR has been resolved and if so, what version of LabVIEW it was resolved in/with. This information could be displayed in the same web page table, or a new page to itself. The "Status" column could then also be expanded with a green check-mark if (all) associated CAR#'s have been resolved..

 

Tracking CAR's and manually trying to search and check them off lists locally is labor intensive, especially since the web-page "search" does not do even a passable job when you enter CAR numbers.

  • MAX
0 Kudos

Hello,

 

I got a cDAQ 9184 connected to a PC running Vision Builder. The IO-Channels on the 9184 are connected via global virtual DAQmx channels. These channels are available on Vision Builder.

 

When power is cycled on the 9184, Vision Builder does not reconnect to it. You have to close and restart Vision Builder to get it running again.

 

My Wish is that Vision Builder is able to reconnect automatically.

 

Best regards,

 

Klaus

 

  • MAX

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. Task configuration.PNG

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.

 

Current VeriStand.PNG

 

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.

MAX Task for VeriStand.PNG

 

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.

Hello,

 

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 ... Smiley Happy

 

Rad.png 

 

Manu.

  • MAX

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?

  • MAX
0 Kudos

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.  

  • MAX

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.

  • MAX
0 Kudos

I have no idea about how to trigger "Bad Status Alarm" of SV without binding any IO.I have no idea about how to set the quality of IO Servers Output item, too.

So I think it is good if SV has "Update Timeout Alarm".

 

  • MAX
0 Kudos

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. 

  • MAX
0 Kudos

Using NI-MAX to find a PXI-1033 with a single NI PXI 4462 in slot2, I get the following problems,

  • MAX

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.

 

 

  • MAX

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

 

  • MAX

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.

Picture2.png

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:

Picture1.png

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

  • MAX

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.

  • MAX

In simple, to have a way of downloading different versions of MAX from ni.com 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.

  • MAX

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.

  • MAX