Home Support Documentation Bugs

FlexLogger 2021 R1 Bug Fixes

Created Jun 20, 2023

Overview

The following items are notable issues fixed between the release of FlexLogger 2020 R4 and FlexLogger 2021 R1, 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 FlexLogger.

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
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
1153539

Incorrect Timestamps for Data Coming From cDAQ Onboard Counters

FlexLogger 2020 R4 added a preview feature which, when enabled, allows the use of onboard counters on cDAQ devices. However the timestamps of all but the first sample from these counters are incorrect. The samples are scaled incorrectly in time because the data is recorded as a waveform and the dt (delta in time) between samples is set to the default sample rate of the counter rather than the actual sample rate. The error is evident when graphing the data on a FlexLogger screen and when analyzing the data from any log files.

    Workaround:

    Logged data can be corrected by re-calculating the timestamps. Use the first sample timestamp and calculate the remaining timestamps using the correct dt, where the correct dt is 1 divided by the actual sample rate reported in FlexLogger. In DIAdem, you can set the Waveform x-step width of each counter channel to correct all the timestamps quickly.

    Reported Version:

    FlexLogger: 2020 R4

    Resolved Version:

    FlexLogger 2021 R1

    Added:

    Oct 28, 2020
    1198557

    FlexLogger May Crash When Using Plugins with Numeric Channel Properties

    FlexLogger crashes when the following two conditions are met:
    • a plugin is loaded in which one or more channels from that plugin have numeric configuration properties
    • the OS is localized to a language in which a comma (,) is the decimal separator
    Numeric configuration properties at the top level of the plugin do not cause this issue. Producing or consuming numeric data with a plugin does not cause this issue.

    Workaround:

    Change the language settings of your OS to a language that uses a period (.) as the decimal separator, such as Chinese, English, Japanese, or Korean.

    Reported Version:

    FlexLogger: 2020 R4.1

    Resolved Version:

    FlexLogger 2021 R1

    Added:

    Dec 9, 2020

    Additional Patch Information

    Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

    These patches currently do not have any special instructions.

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