Home Support Documentation Bugs

FlexLogger 2021 R1 Known Issues

Updated May 14, 2024

Overview

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

Cannot Configure Events Based on Alarms or to Reset Output Channels

When specifying Select channel in the Configure Events dialog, the available channels are visible but cannot be selected. This happens when configuring events that meet one of the following conditions:

  • The If condition is specified as Critical alarm on channel(s) or Warning alarm on channel(s).
  • The Then condition is specified as Reset output channels.

Workaround:

Specify the If condition as Channel value change and the Then condition as Set analog output or Set digital output instead to achieve the desired events.

Reported Version:

FlexLogger 2021 R1

Resolved Version:

FlexLogger 2021 R1 f1

Added:

Apr 29, 2021
1234319

FlexLogger Crashes When Starting a Test on a Localized System

FlexLogger may crash when starting a test if all of the following conditions are met:
  • You are using a non-English version of FlexLogger.
  • The Navigation pane that contains the Project Files and Data tabs is collapsed.

Workaround:

Confirm that the Navigation pane is expanded before starting a test.

Reported Version:

FlexLogger 2021 R1

Resolved Version:

FlexLogger 2021 R1 f1

Added:

Apr 29, 2021
1224828

RMS and Mean Channels May Lose Synchronization With Their Data Source Channels

RMS and Mean channels may lose synchronization with their data source channels when the sample rate of the data source channels is modified. Both the start time (t0) and time step (dt) of the RMS and Mean channels may still be based off the old sample rate. This is noticeable in graphs on the screen and in any log files.

Workaround:

Save, close, and re-open the project.

Reported Version:

FlexLogger 2021 R1

Resolved Version:

FlexLogger 2021 R2

Added:

Feb 1, 2021
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
1398209

Logfiles Are Missing Data When All Channels Sample at Less Than 1 Hz

Some data points may not get saved to the log file when all channels in a project are configured to sample at less than 1 Hz.

Workaround:

Ensure all channels are configured to sample at greater than or equal to 1 Hz. Alternatively, ensure at least one channel is configured to sample at greater than or equal to 5 Hz.

Reported Version:

FlexLogger 2021 R1 f1

Resolved Version:

FlexLogger 2021 R2

Added:

N/A

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