Additional NI Software Idea Exchange

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

I/O Trace is extremely useful when debugging system-level text-based applications. Error handling for systems involving multiple drivers + software packages (RF toolkits, for example) is very difficult. After recognizing there was an error, we still have to determine which device threw the error and then query the appropriate driver/toolkit with the correct handle to determine what the error was. NI I/O Trace is a great way to quickly determine which device threw an error and at which function call. Unfortunately, the error reporting returned by I/OTrace is pretty limited. For example, consider the I/O Trace shown below of an application synchronizing two waveform generators. A property is not configured correctly for one of the generators. I/O Trace clearly indicates there is an error, however the exact cause of the error is difficult to discern from the message: 

 

Capture.PNG

 

The actual error message is: “The Sample Rate property can not be configured if OSP Enabled is VI_TRUE. “. It would be great if I/O trace could provide the entire error description. Compare this to the LabVIEW error handler:

Capture.PNG

In LabVIEW, we have a lot of options for saving our projects as seen below:

 

LabVIEW.jpg

 

 

In VeriStand, currently, you only have the option for a normal save (as shown below). I think it would be nice to have a "Save As" for saving a copy of the project and, if possible, a "Save for Previous Version".

 

 

VeriStand.jpg

 

When I talk with customers who wants to create stimulus test pattern signals, many customers say "I want to create test pattern signals by similar meathods to Signal Builder in Simulink. In "Signal Builder", user can change value by mouse action, and user seems to like that way. (I think Signal Builder in Simulink is not so intuitive and flexible) And user wants to create multiple signals in stacking graph because it is easy to compare each signal timing.

 

image.png

Although many examples exist for VeriStand. They are not easy to find for new users unless they are shown where they are. If they have been using other NI Software , they would likely go to the Help>Find Examples option in the splash/development menu options. In LabVIEW,

 

lvyesfindexamples.png

 

This menu option does not exist in VeriStand.

 

nofindexamples.PNG

 

Giving access to these Examples from the load screen would be helpful for new customers who are getting started and existing customers looking to do a quick test. Navigating for a specific example can be a bit tedious at times because they don't all exist in the same level. Like Sinewave Delay and Engine Demo for instance.

 

<Public VeriStand>\Projects\Example\Sinewave Delay.nivsproj

<Public VeriStand>\Examples\Stimulus Profile\Engine Demo\Engine Demo.nivsproj

 

Currently, Switch Executive virtual devices can only be imported and exported through Switch Executive itself.  It would be really nice if instead Switch Executive virtual devices were handled through the MAX configuration import and export wizards.  This would simplify test system deployment, particularly since the MAX configuration import wizard can be easily automated through deployment installers.  Importing of Switch Executive devices can currently be automated, but you have to create an executable using the Switch Executive Configuration API and then call that executable using a batch file called by your deployment installer.  It would be so much simpler and more consistent if the MAX configuration wizards supported Switch Executive in addition to other products such as DAQmx and VISA.

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.

Hello,

 

Sometimes, customer want to change current model file with another model file. Once the model file is deleted on system definition, mapping infomation related to deleted model also disappear. To workaround this, we have to export map info, then delete mdl file and add new model, and then import map info...but this process sucks.

 

To save our time, I want to suggest "replace" function as below. When replace the model files, map info for the same inport/outport are kept.

 

Img.png

 

Saku

 

The error messages and the texts in MAX are displayed in the current user language. This is based on the selected user keyboard language. This is very anoying for me because I'm working in Switzerland. 

 

We use the English version of LabVIEW to develop our software and, depending on the users, we get messages in german, in french or in english.

 

I would appreciate to be able to really choose the language I will use.

Hello

 

I have encountered problems while converting the Embedded Data Logger Receive Time information from VeriStand in double format into a Excel time stamp.

 

When I am introducing my logging data in .tdsm format I was not able to convert it into a "normal" time stamp with date and time information using the excel cell categories concerning time and data options. My solution to that was a exectuable which the NI support has generated for me. Otherwise it was not possible to me to make this conversion.

 

Either NI should publish the algorithm how to convert this double value into a "normal" time stamp or there should be a possibility to log the data in a easiliy understandble way for Excel to convert it.

 

Best greetings

Lukas Nowak

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.

Way back when VeriStand was first introduced recorded files could automatically be broken apart when they reached a set size.  This feature went away and I would like it back.  I am running test that will last days at 10Hz or faster, so large files are generated.  This really bogs down DIAdem when the data is analysed.  I would like to be able to set the logging file size max  (i.e. 50 Meg) and when the file hits that size a new file with an incremented name (i.e. TestFile_1) is created and data is now logged to it untill it reaches the set size limit.  This not only creates smaller files that can analysed, it lets the data be looked at sooner in the test cycle.

Currently, In VeriStand, you can refresh Models if you made a change or added/removed channels.  I would like to be able to refresh custom devices so I do not have to completely remove it and add it again when I add or remove a channel. 

If the License Manager is used to deactivate software, it will leave the prior serial key in the registry. On subsequent activations, the Activation Wizard will automatically populate the serial number field. I assume the same kind of thing will happen with .lic/.lc licenses.

I can see a valid use case for this, but in my scenario, I need to remove development licenses from productions and disallow users to reactivate the software without getting permission (the serial key) from me. Since these keys can be found in the registry, I can write a script to do this; however, it seems like a feature that License Manager should include.

 

PS: I know, I used the wrong idea label. We need more label flexibility to cover other smaller NI software!

I would really like it if VeriStand channels supported other data types like Strings, or arrays. The channels can even be Variants that would allow me to use any datatype I want.

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:

 

MAX_PrintTask.png

 

Would create a file that looks similar to this:

 

MaxTaskConfig.PNG

 

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.

In Veristand you can add a alarm with one low and one high limit. Often it is helpfully not only have alarm limits but also warning limits. In some automation systems (e.g. Morphe from D2T) we can define three limits.

 

For example:

Warning: The oil pressure of a engine fall below the warning limit we could log that, show a dialog and stop smoothly the engine.

Alarm: But if we fall below the alarm limit its very important to stop as fast as possible.

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

 

Concurrent.png

 

 

 

Sort Keyword Within a Server's License File

 

ServerLicense.png

 

 

 

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.

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!

I have a system definition of over a thousand signals. I see that VeriStand 2011 has some search functionality built in. Is there a way to search not just ni the channel names but for the use of particular variables within calculated channels? For example, if I have UserVar1, I'd like to be able to find all occurrences of where UserVar1 is used. It could be an argument in a Calculated Channel, a mapping destination, an alias, etc. Is there a search tool that can accomplish this? Thanks.