FlexLogger 2020 R4 Bug Fixes
Overview
The following items are notable issues fixed between the release of FlexLogger 2020 R3 and FlexLogger 2020 R4, 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 2020.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1125138 |
Formula Output Incorrect When Operating on Both Digital and Analog ChannelsFlexLogger 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 |
|
| 1154827 |
Formula Output Incorrect When Operating on Two or More ChannelsFlexLogger 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. You can use the attached tool, FlexLogger2020FormulaDiagnosticUtility, to determine if any of your projects may be affected by this issue. |
Reported Version: FlexLogger: 2020 R4 Resolved Version: FlexLogger: 2020 R4.1 Added: Oct 28, 2020 |
|
| 1116657 |
Adding DAQ Channels in a Non-sequential Order Corrupts Anything Referencing a ChannelWhen 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 FlexLoggerNumeric 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 channelsFor 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 |
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).