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

  • Visual Studio Integration

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.

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.

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!

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.

  • Visual Studio Integration
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 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

This may or may not be possible, but I'd like to be able to run my .NET program using real time.  If this isn't something that NI can do because it involves hardware that isn't supplied or supported by NI, it would be nice to have some information on how it can be done.  I recently saw some presentations by people that are able to use some real time kernel to get faster loop rates than I can get in Windows (9 Hz).  This is the one major deficiency for Measurement Studio.  LabVIEW supports FPGA and real time, and I can completely understand why FPGA may not be possible for .NET projects.

  • Visual Studio Integration