Additional NI Software Idea Exchange

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

First time poster here so please excuse my ignorance if I am posting incorrectly.

 

I know NI supports CentOS and SUSE GNU/Linux distributions, but Debian distros are the most popular according to distrowatch.  I would like NI to consider creating 488.2 driver support for Debian based distros.  Specifically Linux Mint and Ubuntu.  I have been using Ubuntu 14.04 LTS and recently switched to Linux Mint 18.3.  Mint 18.3 works so well, I abandoned Windows 7 on my personal computer and only use Windows 7 at work (because I must).  I can use NI USB devices on Mint (and Ubuntu) by installing the driver in a Windows 7 virtual machine and passing through the USB in VirtualBox.  However this does not work for PCI cards.  Drivers are a big roadblock to migrating our test equipment off Windows so I am hoping NI considers better GNU/Linux development in the future.  Thank you.

Hi

I would like to be able to simulate XNET devices in MAX (with minimal support). I would not expect these devices to simulate data on the bus. They could help us developers catch some bugs before we integrate with the actual HW.

 

It would be easier for a developer to be able to create configuration files, databases and test them out without connecting to the actual HW. In most cases, the HW is on a rig which is in use, or the HW is not yet delivered for the rig. We would not need any data on the bus in these cases.

 

I have been struggling over the past few months, to be able to define databases or use databases and test my configuration UI without the actual HW. And I have faced lot of error with creating multiple sessions, opening sessions after the HW is reserved etc.

 

I would hope that such errors could be tested and fixed using a simulated device, where the actual messages on the bus are not important.

 

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.

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.

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!

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. 

 

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.

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

 

VLMServer.jpg

 

 

 

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

 

LMClient.jpg

 

 

In a database (DBC or xml), signal could have a long name property. This property is not avaible in Xnet databse editor or in LabVIEW. That could be a probleme when several signal have the same first 32 character.

Always with Xnet, when reading signal value (or reading frame and convert frame to signals), the result is always a number. In database, some signal have a convertion table to string for a better understading

Download All

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? Smiley Wink

 

Thanks a lot,

Sincerely, kosist90.

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.

 

 

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!

Hi,

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

Regards,
Kira T

See Also

Simulated Devices in LabVIEW projects

Simulated Devices in TestStand Workspaces

 

Link to those ideas in next post.

 

For integration and station troubleshooting the Sessions, Aliases, Tasks et al would be organized by Project, Application or deployment in MAX and fault identification has all the "tools" any repair tech could want to isolate a failure.

 

Partial workaround: Copy VAS Sept 2011 (compatible with VS 2005 and 2008) Vision assemblies to VS 2010 project. I know no way of getting VAS Vision Help viewable in VS2010.

 

Note: ignore the MAX Idea Label on this post - I added this just to get the forum to accept the post.

Hello all,

 

In MAX, you can create a task or virtual channel for DIO

 

and the default setting is that MAX create one channel for one line

 

One of our customer ask if there is any method create a task of one channel for mutiple line

 

but in MAX, you can't set this

 

The only method for doing this is config it in LabVIEW code

 

It would be nice if this can be set in MAX

 

Thanks

 

I would like to suggest adding toolkit version information to the NI-MAX reports.  I would add this information to both the simple and technical reports.

Increase the size of the "handles" used to resize the display panes in MAX so that it can be done on a touchscreen interface. It is impossible to "grab" the border between two panes on the MAX window using touch to expand a pane. It would also be very nice if MAX remembered its window/panes positions between sessions.