NI Measurement Studio Idea Exchange

Community Browser
About NI Measurement Studio Idea Exchange

Have a new Idea for MStudio?

  1. Browse by label or search in the Measurement Studio Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea to the Measurement Studio Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea
0 Kudos

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.

 

When the installer builder is called from the system shell (cmd.exe) using a command like the following:

InstallerBuilder "D:\NI Installer Builder\INSTALLERPROJECT.iip" -Build -Log "D:\NI Installer Builder\niib.log"

It spawns a background process and the application returns with a successful run BEFORE the installer is created. As the build is started in a background and a detached process; any build automation frameworks such as bamboo, jenkins, chef, etc. cannot monitor it's creation. This results in a failed operation a breaks continuous integration systems. 

As a work around I have built a light python solution that monitors for a que event; in this case a
file either being populated or updated. I am using this application to monitor the log file as a que.
The python file should be attached to this submission.

Basically:
1. InstallerBuilder is ran – begins running building process in the background
and returns successful process run before installer is constructed.

2. IndirectProcessMonitor.py is ran (max timeout and file set):
python IndirectProcessMonitor.py 300 “D:\NI_installerbuilder\niib.log”
NOTE: Probably could set it to your setup file as well

3. IndirectProcessMonitor.py returns when timeout is exceeded or que file is
created or updated.

If the NI installer builder is to be able to be dropped into any automation
frameworks this has to be fixed on NI’s end. If this bug/support is scheduled
for development I’d be interested to know as it will/should break our
workaround.

Let's go directly to the newest version.. Here is a preview:

https://www.visualstudio.com/de/vs/visual-studio-2017-rc/

 

VC2017 is propably released when we get Measurement Studio 2017.. (Hopefully 2017.. ;-))

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

0 Kudos

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.

0 Kudos

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.

0 Kudos

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.

If you generate multiple plots on a ScatterGraph in WindowsForms using the designer, they are automatically colored.  One of the colors is repeated.  

 

The list is as follows: 

 

1 . Lime
2 . Red
3 . Blue
4 . Cyan
5 . Yellow
6 . Fuchsia
7 . Gray
8 . DarkBlue
9 . Green
10 . Violet
11 . DarkGoldenrod
12 . DarkCyan
13 . DarkMagenta
14 . DarkOrange
15 . DeepPink
16 . DarkViolet
17 . DodgerBlue
18 . Chocolate
19 . MediumAquamarine
20 . SkyBlue
21 . IndianRed
22 . Plum
23 . Silver
24 . Gold
25 . Salmon
26 . Maroon
27 . YellowGreen
28 . IndianRed
29 . Tomato
30 . SteelBlue
31 . Bisque
32 . DarkKhaki

 

This selection has a length of 32 different colors before it begins repeating. It does a fairly good job of choosing colors which can be individually distinguished, except for our two techs who are colorblind...but that's another story, and I don't think there's a way to display 32 plots on one graph in a way that won't at least confuse even non-colorblind people.

 

However, on closer inspection, you'll note than plot 21 and plot 28 are both IndianRed.  These should be separate colors.  Perhaps 28 could be DimGray or LightGray?  There aren't many other options.

 

Here is an image for comparing the colors: 

 

Automatic Plot Color Comparison

 

Each line should be distinguishable. These are not: 

 

IndianRed repeated

 

And here is the code I used to generate it: 

 

int total_colors = 32;
scatterGraph1.Plots.Clear();
for (int i = 0; i <= total_colors - 1; i++) {
	scatterGraph1.Plots.Add(new NationalInstruments.UI.ScatterPlot { LineWidth = 6 });
	scatterGraph1.Plots[i].PlotXY(
        new double[]
        {
		    0,
		    5 + i * 2,
		    5 + total_colors + i * 2,
		    10 + 3 * total_colors
	    },
        new double[]
        {
		    total_colors - i,
		    total_colors - i,
		    -i,
		    -i
	    }
    );
}

 

In order to help debug and present measured data, it would be nice to have a plot tool that can display smitch chart plots. It could take in the data as an array or DataTable of imaginary numbers. Added bonus would be to provide methods to convert Impedance to Admittance and to also provide color scale based on a 3rd parameter (for example to plot impedance and gain in the same plot).

0 Kudos

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

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.

0 Kudos

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-plot...

 

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!

We need an equivalent to the AnalogMultiChannelReader.MemoryOptimizedReadWaveform, but for the digital channel readers (e.g. "DigitalSingleChannelReader.MemoryOptimizedReadMultiSamplePortByte"), in the .NET API for NI-DAQ.

 

Best regards,

Thomas

 

0 Kudos

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?

 

0 Kudos

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.

0 Kudos

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

Chuck Lippmeier

0 Kudos

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

0 Kudos

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.

We are limping along on the ancient components works 3D graph that does suface plots. Any plans to move it out of the 90s?