Measurement Studio 2019 Bug Fixes

Visão geral

The following items are notable issues fixed between the release of Measurement Studio 2015 and Measurement Studio 2019, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of Measurement Studio 2019.

Contents

Contacting NI

Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. 

Bug Fixes

Bug Number

Legacy ID

Description

Details

892713 366974

The arrow label to an annotation on a WPF Graph control can shrink and disappear depending on the size of the label and its alignment.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Measurement Studio 2013

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

892584 191580

Uninstalling NI products may also remove installed .NET applications that use NI libraries.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Measurement Studio 2010

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

893112 671668

Application hangs at run time when you pan a WPF graph with y-axis set to logarithmic scale.

When using a WPF graph with a logarithmic Y-axis, attempting to pan with ctrl+click causes the application to hang.

Workaround:

Convert data to logarithmic representation and the y-axis to linear scale.

Reported Version:

Measurement Studio 2015

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

893233 604388

Using multiple WPF graphs in different threads can cause your application to crash.

When rendering WPF graphs, a point-renderer generates a static bitmap. When multiple WPF graphs are rendering in different threads, the first graph to render will write to the bitmap, but the subsequent threads will fail to access the bitmap. This can cause a crash.

Workaround:

Follow the workaround as described in this community post.

Reported Version:

Measurement Studio 2013

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

287880 668896

NationalInstruments.NI4882.dll throws a type initializer exception on FIPS-enabled Windows.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Measurement Studio 2013

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

287869 607424

The SignalProcessing.Convolve2d method produces incorrect output when convolving matrices of different sizes.

The Convolve2d method can sometimes produce incorrect values when matrices A and B are different sizes. The incorrect values are very large or small, e.g., 3E+216 or 2E-314.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Measurement Studio 2015

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

287888 529919

Measurement Studio libraries are not selected in the Add/Remove .NET Class Libraries dialog after adding a reference to Web Forms to the project in Visual Studio 2013.

In the Add/Remove .NET Class Libraries dialog, if you select the Web Forms library and close the dialog, the reference is added and the .licx file is updated. When you reopen the Add/Remove .NET Class Libraries dialog, the Web Forms library is not selected.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Measurement Studio 2015

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

287893 586755

Writing DateTime to a TDMS file slightly offsets the time.

Writing a DateTime value to a TDMS file using the Measurement Studio API writes a slightly offset value for the DateTime to the TDMS file. The value written is 76 ticks later than expected.

Workaround:

Convert the DateTime to a PrecisionDateTime. Example: file.AddProperty("_ts0", TdmsPropertyDataType.DateTime, PrecisionDateTime.FromDateTime(writeDate));

Reported Version:

Measurement Studio 2015

Resolved Version:

Measurement Studio 2019

Added:

Jul 21, 2020

1001407

Error When Compiling Measurement Studio Project Using NI-Digital

When you use Measurement Studio to compile a .NET project that includes references to NI-Digital, an error occurs because NationalInstruments.ModularInstruments.Common 19.0 cannot be found. This is caused by Measurement Studio adding references to assemblies with different .NET Fx versions, which creates a conflict.

Workaround:

Update all project references to include only Fx40 or Fx45 versions of NI assemblies.

Reported Version:

Measurement Studio 2019

Resolved Version:

Measurement Studio 2019 f4

Added:

Jul 21, 2020

194375

Loss of precision occurs when using the PrecisionTimeSpan structure in certain mathematical operations

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Measurement Studio 2019

Resolved Version:

Measurement Studio 2019 f4

Added:

Jul 21, 2020

220170

The Visual Studio Performance Manager window appears the first time Visual Studio 2019 is opened

The following text is displayed the first time Visual Studio 2019 is launched after installing Measurement Studio 2019: "NI Measurement Studio Support for Visual Studio: The extension uses deprecated APIs and will not be compatible with a future Visual Studio update.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

Measurement Studio 2019

Resolved Version:

Measurement Studio 2019 f4

Added:

Jul 21, 2020

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).