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

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.. ;-))

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
	    }
    );
}

 

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.

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 3D Chart control needs to be updated to the .Net platform.  In addition it would be nice to have the waterfall functionality included in Labview.

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

Log charts such as the ones pictured in the screenshot I attached are common in the oil industry. Many oils companies use NI equipment and write LabView and Measurement studio based software. The collected data is often plotted in log charts. It would be nice if NI would consider offering a vertical graph control in both Measurement Studio and the LabView products.

Hello, I would like to have the NI-CAN, NI-XNETsupport integrated into the next version of NI Measurement Studio.

Why this kind of devices only have an old style C Library? Could be more useful to have classes on C++ and .NET

 

Best regards

Roberto Guerzoni

Distributing applications via ClickOnce is a fast and easy way to deploy applications to clients all over.  However, a "bootstrapper" (http://digital.ni.com/public.nsf/allkb/148A815DF9379F8786257560005DB06A) is needed to install the required MStudio files into the GAC.  Please provide a working example for VisualStudio 2012/2013 of a bootstrapper that does this, so we can just deploy the application and updates via ClickOnce.

I would like to see the following methods from LabWindows/CVI and Labview added to the Measurement Studio TDMS. The "Create Linear Scaling Info" would be the most useful to me when converting from other data formats to TDMS. I really like being able to keep unscaled data with the scale factors and having the data automatically scaled when reading with TDMS libraries/dlls.

 

Methods from LabWindows/CVI API

Advanced Data Scaling  
Create Linear Scaling Info TDMS_CreateLinearScalingInfo
Create Polynomial Scaling Info TDMS_CreatePolynomialScalingInfo
Create Thermocouple Scaling Info TDMS_CreateThermocoupleScalingInfo
Create RTD Scaling Info TDMS_CreateRTDScalingInfo
Create Table Scaling Info TDMS_CreateTableScalingInfo
Create Strain Scaling Info TDMS_CreateStrainGageScalingInfo
Create Thermistor Scaling Info TDMS_CreateThermistorScalingInfo
Create Reciprocal Scaling Info TDMS_CreateReciprocalScalingInfo

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

Can I suggest it's time NI add some utility to work out which merge modules are needed. I can often spend a lot of time trying to deploy NI projects.

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

 

The title says it all.

I have a project file using .Net 4 (VS2010, properly update) which I opened in VS2013, upon opening with no warning all NI license.licx lines were removed with no warning whatsover.

 

This should never happen, if something is going to be changed the user should be informed what is happening, especially if it's going to break a build.

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.

Hello, I would like to have the NI Network Streams support integrated into the next version of NI Measurement Studio.

 

Best regards

Christian

Hi, NI team.
I was adviced to share my idea here ( actually it was something I needed, not idea Smiley Happy ).
I have Waveform graph control in my application. There are two axes: vertical and horizontal. The plots I show on the graph have different units by vertical axis, so I decided to show those units as a caption of vertical axis. However I wasn't able to give this caption appropriate view and was forced to use label control. The problem with the caption of vertical axis is that it is oriented vertically and you can only change text direction between top-to-down and down-to-top. What I was looking for is a normal orientation from-left-to-right.

 

May be someone else will use this feature in future Smiley Happy
Regards

Hello, I would like to have the NI PID support integrated into the next version of NI Measurement Studio.

 

Best regards

Roberto Guerzoni

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!