NI Measurement Studio Idea Exchange

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

A project template and nice controls for creating real-time web based test&measurement applications based on ASP.NET MVC, SignalR,..

 

https://www.asp.net/signalr

The information provided with exceptions has not been useful in determining the problem cause.  For example, the latest bug I've been dealing with in my code involves 2 tasks trying to access the same resource.  The exception gives the name of the task that throws the exception.  Great.  It's really easy to tell which task throws the exception because, well, it's throwing the exception.  What the exception message doesn't tell me are the other task(s) that have that resource.  The really useful information is consistently lacking in exception messages.

When I install Measurement Studio 2013 on a development computer, activate my Standard Development serial number and license that PC over the Internet, and build some software in Visual Studio, the Enterprise Development trial is automatically selected in the build process. After 30 days, the license expires, and the software behaves as if it is unlicensed - that is, it crashes. A Clean and Rebuild must be run to select the Standard Development license and make the software work again.  I believe that this default behavior is incorrect.  This 30 day window is often shortly after delivering the machine to a customer, so it fails on their floor right after we leave! This is not good for our reputation or for NI's reputation.

 

One or more of the following options would be the preferred behavior:

 

(1) Do not automatically enable the "Enterprise Development" trial. This trial should be deactivated by default when a Standard or Professional license is activated, and a user should be able to open NI License Manager and Activate it as required.

 

(2) Show a warning on start-up whenever a trial license is used. This is what LabVIEW does: upon launch of LabVIEW the user would see something like "Evaluation License - 5 days remaining".  Measurement Studio users do not see this upon launch of Visual Studio, upon building the project in Visual Studio, or upon starting the resulting software.  It would be nice if you could provide a link that would instruct users on how to deactivate the Enterprise Development license in this warning.

 

(3) Use the lowest possible development system. If Enterprise-only features are used and a Standard license and Enterprise trial are available, then the trial is necessary (though a warning as in #2 above would be nice), but otherwise use the Standard or Professional license. This issue has caused us some embarrassment several times. Please fix it!

 

The workaround, according to Michael Keane from NI (in Service Request #7454045, if anyone from NI is reading this), is as follows:

 

I assume that in License Manager during those 30 days you would see a green box next to Standard edition and a half white / half yellow box next to Enterprise. The workaround for what you are describing would be to go into ProgramData (hidden folder, will have to type it into Windows Explorer) >> National Instruments >> License Manager >> Licenses and move the Enterprise .lc file outside the Licenses folder. It probably has "TmpEthernet" in the name. This way, License Manager would not be able to find an evaluation version license and I would expect the checkbox next to Enterprise to appear white after refresh. Then, the software would have to look toward the full license and no builds would be expiring.

 

This works, but is still leaves the possibility for the step to be forgotten and the software to fail shortly after delivery, which is obviously no good at all!  Please fix this!

Plotting a big array of sample uses quite some time in the current version. I think this comes from Measurement Studio drawing a line explicitly between each two samples. However, in case of millions of samples, many of those lines will cover only one single pixel.

 

Instead of drawing all lines, it would be possible to sample the data at a rate where each sample matches just one pixel in the input axis. In order to not loose peaks, the sampling needs to do a min/max calculation and draw two lines for the minima and maxima. A shade could be used between the two curves. When zooming, the sampling needs to be repeated.

 

This feature would not only save much performance for big data (I think), it can also help to improve clarity of the graph, p.e. in case of noisy signals.

 

While it's great that Measurement Studio offers all capabilities for us to implement this functionality ourselves, such a feature could be of interest for many users.

 

Of course, this idea is not my intellectual property. It's a feature already implemented in other products.

Hi,

 

I'd like to see some of the functionality contained in NI-VISA without having to install VISA on my system, but just set a reference to the library in my project. I'd just like to access devices/instrumentation through the serial port or usb without needing admin rights on every machine the runs the application.

Microsofts serial class has limited functionality. I like the reliability that comes with Visa.

 

Curt

Dear NI team,

 

NI is competing to a level in the automotive domain to some extent.  But if there is some value addition it could be easy to get markets.

 

Already NI website have cRIO and PXI advisor.

 

We need the following also items to make it nice to catch the market

 

  HIL advisor - which integrates all the tool kits (such as UDS etc) NI hardware specifically related to Automotive

 

I am sure i was and wont be the only one who wants to create a plot with timing data where it starts at zero and counts up in seconds or something else.  It would have helped me a lot if something like this would be in the original librarys and documentated as such. Seems like a really marginal feature which is easy to implement.

 

Greetings

rizardus

Please add NI DataPlugin Capabilities to Measurement Studio. Of specific use to me would be the equivalent functionality of the following 2 VIs:

1. Convert to TDM or TDMS.vi

2. List DataPlugins.vi

 

I have been looking for an easy way to resample data with either Measurement Studio or LabWindows/CVI and came across the Rational Resample VI for LabVIEW users. It would be great to have this functionality in Measurement Studio.

 

At the very least it would be good to have an Upsample method to insert zeros into a waveform/signal. Then an FIR interpolation filter can be used on the upsampled signal to interpolate the signal.

 

Hi,

 

OPC UA TSN integration directly into Measurement Studio; the both server and client sides.

 

NI is supporting the standard:
http://www.abb.com/cawp/seitp202/288CCF9454F992B9C1258074002D93EC.aspx

 

2016-11-23-Press-Release-OPC+UA+TSN-e.jpg

Thanx.

Currently, it seems that the only versions of Measurement Studio are 32-bit.  Since applications developed with 32-bit have certain limitations (particularly with memory usage), it would be great to be able to use NI analysis and filtering on larger files. Currently, this is a limitation that causes problems with processing some data files, and will only become a larger problem as the trend to store (and analyze) more and more information continues.  Perhaps I'm missing something and there's already a 64 bit version somewhere, but I did contact support and they were unaware of anything.

It appears that the installer that Installer Builder produces does not check 
that the system has the required components. For example, my app uses .NET 
4.6.1, but the app installed with no warning on a machine that had an earlier 
version of .NET and the app failed with mysterious errors that gave no indication that 
this was the issue. Microsoft's installers could check for prerequisites, 
and Installer Builder has to, too.

hOW TO USE NI DAQ 9471 to get my data from analog sensors by using C++ language.help me with resources to start please

It would be extremely useful to break up the Intensity Graph data into cells to easily see "coordinates".  At the moment you have to follow coordinates with your finger or a pen.

I was given this solution but it is surely an overkill for what should be a simple setting.

 

http://forums.ni.com/t5/Measurement-Studio-for-NET/WPF-Intensity-Graph-gridlines-not-visible-on-plotted-data/td-p/3168193

 

The MS grid control and all of the 3rd party vendors grid (WPF) controls data bind to an object that has a property for each column of data for example firstname, last name, age, phone number etc.

 

Well in Data acq say I had 250 channels I would need to create an object that has 250 properties on it. Doable I guess but what if the customer then decides to just show 200 channels I would need a different object for that.

 

I would want the Measurment Studio grid to be easy to add arrays of data (V, I, R etc). Then if the customer enables Power I could easily add a 4th column or if they stopped the acquisition have the option to append the new arrays of dat to the end of the existing data.

 

Show me a WPF grid that can do this with performace of course?

 

It would be great to incorporate the STM protocol into Measurement Studio, this would all an STM connection by just dropping the tool into Visual Studio, adding the IP and the Port, then collect data.  The idea would be to incorporate Flattening and Unflattening of the data after connection to the STM server in the Labview Realtime.  This can make everyones life much easier.

I'd like to make an ASP.NET web page that uses server-side controls to access NIDAQ.

Chuck Lippmeier

The ability to make 3d views of control would be very impressive. 

I am often adding the glue code to make it work like LabVIEW. I guess I should make my own custom control but it would be better if there was something I could use off the shelf.

The IntensityGraph is a great control - but unfortunately its usefulness is hampered in the extreme due to performance issues. Basically the IntensityGraph.OnPaint() takes way too many CPU cycles. For a 500x150 intensity plot updating at ~10 Hz, this takes upwards of 30-40% of my PC's total CPU. Anything higher than that and my application becomes unusable due to latency problems. I really need to be able to show 2 or 3 times that much data.

 

Another user has separately reported an inability to display two 500x256 intensity graphs updating at 5 Hz.

 

We really need NI to address the severe performance limitations of this important control.