Home Support Documentation Bugs

NI-DCPower 2024 Q1 Bug Fixes

Updated Feb 3, 2025

Overview

The following items are notable issues fixed between the release of NI-DCPower 2023 Q4 and NI-DCPower 2024 Q1, 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 NI-DCPower.

Bug Number

Legacy ID

Description

Details
1024555

No device names appear when initializing a session with NI-DCPower on NI Linux Real-Time Targets

When selecting a resource name with niDCPower Initialize With Channels.vi in LabVIEW with a LabVIEW version prior to 21.0 on an NI Linux Real-Time target, the drop-down menu for selecting resources appears empty and you cannot select a device that is in your system.


Workaround:

  1. Manually enter the resource name for the device you want to use. Use NI Measurement and Automation Explorer (NI MAX) or NI System Configuration software to retrieve the resource name for any devices in the system. Or
  2. Use LabVIEW version 21.0 or later.

Reported Version:

NI-DCPower 20.5

Resolved Version:

NI-DCPower 2023 Q4

Added:

Sep 7, 2020

No device names appear when initializing a session with NI-DCPower on Linux Desktop

When selecting a resource name with niDCPower Initialize With Channels.vi in LabVIEW on Linux Desktop, the drop-down menu for selecting resources appears empty and you cannot select a device that is in your system.


Workaround:

Manually enter the resource name for the device you want to use. Use the Hardware Configuration Utility or NI System Configuration software to retrieve the resource name for any devices in the system.

Reported Version:

NI-DCPower 20.1

Resolved Version:

NI-DCPower 2023 Q4

Added:

Apr 19, 2022
2047085

Using Hold Threshold Mode on Range Up Behavior causes device to enter compliance

On PXIe-4163 and PXIe-4163 (10 pA) devices, when performing sourcing with measurement autorange On, autorange behavior Range Up & threshold mode Hold, the device is not able to range up, and hits compliance with current measurement and current measurement range set to autorange minimum current range

Workaround:

1. Configure autorange behavior to Range Up and Down or Range Up to Limit then Down

OR

2. Configure threshold mode to Normal, Fast, High Hysteresis or Medium Hysteresis

Reported Version:

NI-DCPower 2022 Q4

Resolved Version:

NI-DCPower 2023 Q1

Added:

Oct 6, 2022
2150834

PXIe-4147 devices may return error -1074118504 when Sequence Step Delta Time is enabled

On PXIe-4147 device, setting current range at the first step of a sequence with Sequence Step dt Enabled is true may return error -1074118504


A range change in the first step of a sequence can cause the channel to exceed the Sequence Step Delta Time you specify for that step. 

Workaround:

To avoid exceeding your dt due to range changes in the first step, follow the guide "Avoiding Range Changes in the First Step" in https://www.ni.com/docs/en-US/bundle/ni-dcpower/page/ni_dc_power_supplies_help/sequencestepdeltatimetimingissues.html

Reported Version:

NI-DCPower 2022 Q4

Resolved Version:

NI-DCPower 2023 Q1

Added:

Oct 6, 2022
2157486

Setting Source Delay to more than the Sequence Step Delta Time may return error -1074118503

On PXIe-4147 device, setting Source Delay more than Sequence Step Delta Time at Advanced Sequence Commit Step may return error -1074118503.

Workaround:

Since the PXIe-4147 does not support Sequence Step Delta Time in Advanced Sequence, the Source Delay will be verified for all steps. Sequence Step Delta Time should not be enabled on Advance Sequence Commit Step, but only during the first step of the main sequence.

To avoid getting an error when setting Source Delay in the Advanced Sequence Commit Step, set the Sequence Step Delta Time to be greater than the Source Delay

Reported Version:

NI-DCPower 2022 Q4

Resolved Version:

NI-DCPower 2023 Q1

Added:

Oct 6, 2022
2146998

When using Independent Channels, Device Reset closes/opens session, and reopening can fail, invalidating the session

After a hardware error occurs, calling niDCPower_ResetDevice may leave the session in an unusable state if the hardware error has not been resolved.

Workaround:

Use NI-MAX or the System Configuration API to reset the device and then use the NI-DCPower API to create a new session.

Reported Version:

NI-DCPower 2022 Q4

Resolved Version:

NI-DCPower 2023 Q1

Added:

Oct 6, 2022
2197600, 2540838

Configuring Sequence Step Delta Time on the PXIe-4135 can cause error -1074118504

If the PXIe-4135 is configured to use the Sequence Step Delta Time property when Output Cutoff Enabled is set to true, NI-DCPower can throw error -1074118504. This occurs when the Output Cutoff property takes longer than the configured Sequence Step Delta Time value. When this happens the PXIe-4135 will stop the Sequence operation and set the output voltage to zero.



Workaround:

If using both the Sequence Step Delta Time and Output Cutoff Enabled properties in one session, explicitly configure your session using the NI-DCPower Commit VI.

Reported Version:

NI-DCPower 2023 Q1

Resolved Version:

NI-DCPower 2024 Q1

Added:

Feb 1, 2023
2100417, 2232430, 2292381

Ubuntu 22.04 hangs when running extended NI-DCPower generation tasks

NI-DCPower 2023 Q1 on Ubuntu 22.04 has been observed to hang execution after repeatedly initializing sessions for 4+ hours.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-DCPower 2022 Q3

Resolved Version:

NI-DCPower 2023 Q1

Added:

Jan 31, 2023
2546538

PXIe-4162/4163 intermittently returns error -1074118579 when sending a software trigger under high load

When a software start trigger is sent to most or all channels in parallel, the PXIe-4162/63 occasionally returns error -1074118579.

Example:
Error -1074118579 occurred at niDCPower Send Software Edge Trigger.vi

Possible reason(s):
The requested software trigger could not be sent because the device was not waiting for that trigger. Check the trigger configuration to ensure that the device is waiting for the trigger before sending the software trigger.

Workaround:

Send fewer software triggers simultaneously to the same instrument.

Reported Version:

NI-DCPower 2022 Q4

Resolved Version:

NI-DCPower 2024 Q1

Added:

Jan 31, 2024

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