FlexLogger 2020 R4 Known Issues

Overview

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

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:

N/A

Added:

Sep 10, 2020

1154827

Formula Output Incorrect When Operating on Two or More Channels

FlexLogger may map channels incorrectly and produce the wrong output from any formula that uses two or more channels. This can occur when configuring a formula, renaming any channels used in formulas, or migrating a project from a previous version of FlexLogger.

Workaround:

There is currently no known workaround for this issue. It will be resolved in an upcoming patch release, FlexLogger 2020 R4.1.

Reported Version:

FlexLogger 2020 R4

Resolved Version:

N/A

Added:

Oct 28, 2020

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

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:

N/A

Added:

Oct 28, 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).