FlexLogger 2020 R2 Known Issues

Überblick

This document contains the FlexLogger 2020 known issues that were discovered before and since the release of FlexLogger 2020 R2. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details

1043153

Scan for TEDS on unconnected channel can pull stale TEDS data from NI MAX

Scan for TEDS on unconnected channels can reference stale TEDS data from NI MAX.

Workaround:

Remove TEDS info from NI MAX. Then, re-scan in FlexLogger.

Reported Version:

FlexLogger 2020 R2

Resolved Version:

FlexLogger 2020 R3

Added:

N/A

1125138

Formula Output Incorrect When Operating on Both Digital and Analog Channels

FlexLogger may map channels incorrectly and produce the wrong output from any formula that includes both digital (any channel that has a boolean value) and analog channels (any channel that has a numeric value). If the name of a digital channel comes alphabetically before the name of any analog channels in the formula, then the channels will get mapped to the wrong position in the formula. For example, the formula "b_digital ? a_analog : c_analog" would be mapped incorrectly because the name "b_digital" comes before "c_analog" alphabetically.

Workaround:

Rename channels so that, alphabetically, all analog channels are before any digital channels. This issue will be resolved in an upcoming patch release, FlexLogger 2020 R4.1.

Reported Version:

FlexLogger 2020 R2

Resolved Version:

N/A

Added:

Oct 28, 2020

1116657

Adding DAQ Channels in a Non-sequential Order Corrupts Anything Referencing a Channel

When new DAQ channels are configured in non-sequential order within a device (PXI, cDAQ, FieldDAQ, USB, etc.), any existing or future calculated channels, plugins, logging triggers, and events reference the wrong channel. This means that calculated channels and plugins will be operating on the wrong data and events and triggers may not fire when expected. To obtain more information, click the link below.

Workaround:

Save and re-open your project after you have finished all new channel configurations and before you validate the project.

Reported Version:

FlexLogger 2020 R1

Resolved Version:

FlexLogger 2020 R4

Added:

Sep 10, 2020

957223

Numeric Indicator increases digits of precision at random times in FlexLogger

Numeric indicators configured with 'Digits of Precision' can display more digits of precision than specified for values near zero.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

FlexLogger 2019 R4.1

Resolved Version:

FlexLogger 2020 R4

Added:

Sep 10, 2020

1035075

Decimal Value Can Cause Errors in Plugins on Systems with Certain Regional and Language Settings

On systems with regional/language settings that use "," as the decimal, entering values with "," for plugin channels with result in an error.


Workaround:

Use a language/regional setting that uses "." as the decimal.

Reported Version:

FlexLogger Plugin Development Kit 1.2 | FlexLogger 2020 R2

Resolved Version:

FlexLogger 2020 R3

Added:

N/A

1065421

Disabled Plugin Channel Can Lead to Misorder of Channels

Disabling plugin channels can lead to plugin channels being out of order. Logging and calculated channels could refer to the incorrect channels.

Workaround:

Avoid disabling plugin channels before starting a test.

Reported Version:

FlexLogger Plugin Development Kit 1.2 | FlexLogger 2020 R2

Resolved Version:

FlexLogger 2020 R3

Added:

N/A

1065682

Update Channel Units VI does not function for consumer channels

For plugins, Update Channel Units VI does not work for set point (consumer) channels.

Workaround:

Re-create the consumer channels with the new units.

Reported Version:

FlexLogger Plugin Development Kit 1.2 | FlexLogger 2020 R2

Resolved Version:

FlexLogger 2020 R4

Added:

Sep 10, 2020

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

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