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.MemoryOptimizedReadWavefo
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/148A815DF93
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.
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|
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
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.
Hi, NI team.
I was adviced to share my idea here ( actually it was something I needed, not idea ).
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
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.
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.
I'd like to take advantage of Windows Presentation Foundation as the user interface for our data acquisition software. I'd like to see WPF graphs, switches, gauges, etc. with the ability to add the controls to XAML, databind, etc.
(Also wondering what happened to the beta version of Visual Studio 2012??)
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.