Home Support Documentation Bugs

FlexLogger 2020 R3 Known Issues

Updated May 14, 2024

Overview

This document contains the FlexLogger R3 known issues that were discovered before and since the release of FlexLogger 2020 R3. 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
1379207

FlexLogger Crashes While Opening Projects That Have at Least One Plugin Configured

FlexLogger may crash while opening a project that meets the following conditions:
  • The project was saved in FlexLogger 2020 R1 or earlier
  • The project has at least one plugin which consumes data from a FlexLogger channel
  • The project is being opened in FlexLogger 2020 R2, 2020 R3, 2020 R4, or 2021 R1

Workaround:

  1. Open the project on a computer using the same version of FlexLogger with which you created and saved the project.
  2. Delete all plugins from the project and save a copy of the project.
  3. Move the copied project to a computer with the desired version of FlexLogger installed and open it.
  4. Add the plugins back to the project and re-apply their configuration.

Reported Version:

FlexLogger 2020 R2

Resolved Version:

FlexLogger 2021 R2

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. You can use the attached tool, FlexLogger2020FormulaDiagnosticUtility, to determine if any of your projects may be affected by this issue.

Reported Version:

FlexLogger 2020 R2

Resolved Version:

FlexLogger 2020 R4.1

Added:

Oct 28, 2020
1102692

FlexLogger Temporarily Hangs When a TSN-Enabled Ethernet cDAQ with an XNET Module is Present

FlexLogger temporarily hangs and becomes unresponsive for tens of seconds when a TSN-Enabled Ethernet cDAQ containing an XNET module is present at project load or added later.

Workaround:

Wait for the application to become responsive.

Reported Version:

FlexLogger 2020 R3

Resolved Version:

FlexLogger 2021 R1

Added:

Sep 10, 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
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).