This document contains the NI-DCPower known issues that were discovered before and since the release of NI-DCPower 2025 Q1. 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; see Additional Resources.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
1173335 |
Simulated NI-DCPower devices may return error -2147220719 while running sessionsOccasionally simulated NI-DCPower devices running on an NI Linux Real-Time target will return error -2147220719 during a session. This error can cause some simulated NI-DCPower devices to stop responding. This is only an issue for simulated devices. Error -2147220719: The client process has been disconnected from the configuration server. If this problem persists, please note the steps you performed that led to this error and contact technical support at http://ni.com/support Workaround: Reboot the NI Linux Real-Time target.
|
Reported Version: NI-DCPower: 20.5 Resolved Version: N/A Added: Jan 9, 2021 |
|
2139994, 2139997 |
PXIe-4147/62/63 devices allow configured Voltage or Current levels to be larger than the Level Range when Autorange is enabled.
Workaround: Explicitly configure the Voltage Level Range or Current Level Range immediately after running a basic sequence. |
Reported Version: NI-DCPower: 2022 Q4 Resolved Version: N/A Added: Oct 7, 2022 |
|
2139572 |
Error -50400 rarely occurs with some instrument models on Linux DesktopOn Linux Desktop systems, certain instrument models rarely return error -50400 ("The transfer did not complete within the timeout period or within the specified number of retries.") while in the Running state. Impacted models include:
Workaround: Reset the device from the Hardware Configuration Utility or using System Configuration.
|
Reported Version: NI-DCPower: 2022 Q4 Resolved Version: N/A Added: Apr 3, 2024 |
|
2658185 |
The PXIe-4162 Guard pin does not behave correctly when Autorange is enabledWhen Current Limit Range is set to 60 mA / 100 mA and the Autorange property is set to 1 (Enabled), the Guard pin will output a much smaller voltage than expected, even when the hardware selects a current range where guarding is available.
Workaround: Turn off Autorange property when using 60 mA/100 mA current limit range alongside Guard pin functionality on PXIe-4162.
|
Reported Version: NI-DCPower: 2024 Q1 | NI-DCPower: 2024 Q2 | NI-DCPower: 2024 Q3 Resolved Version: N/A Added: Dec 16, 2024 |
|
2758044 |
Output Cutoff on PXIe-4135/6/7 may cause errors when used in conjunction with Measurement AutorangeWhen using Output Cutoff and Measurement Autorange on the NI PXIe-4135, PXIe-4136, or PXIe-4137, the instrument may return error -1074116059 ("Specified operation did not complete") or error -235140 ("Internal Hardware Error"). Workaround: Do not enable Output Cutoff at the same time as Measurement Autorange. |
Reported Version: NI-DCPower: 2024 Q2 | NI-DCPower: 2024 Q3 Resolved Version: N/A Added: Oct 24, 2024 |
|
2776070 |
Voltage glitch with several millisecond settling time can occur on PXIe-4162 at Commit when using Merged Channels and the current range is re-configuredWhile using Merged Channels on the PXIe-4162, if you re-configure Current Level Range or Current Limit Range, a several millisecond voltage glitch may be visible when calling Commit or Initiate. Using Remote Sense may prevent this glitch.
Workaround: There is currently no known workaround for this issue.
|
Reported Version: NI-DCPower: 2024 Q3 Resolved Version: N/A Added: Jun 29, 2024 |
|
2780312 |
The Voltage LED on the PXIe-4162 / 4163 does not always illuminate when the output is enabledThe Voltage LED on the PXIe-4162 / 4163 front panel may not illuminate even when one or more of the channels are sourcing voltage.
Workaround: Performing a device reset
may make the LED light up properly again, but performing a subsequent device reset while it is working properly may cause the issue to recur.
|
Reported Version: NI-DCPower: 2022 Q4 | NI-DCPower: 2023 Q1 Patch 2 | NI-DCPower: 2023 Q2 | NI-DCPower: 2023 Q3 | NI-DCPower: 2023 Q4 | NI-DCPower: 2023 Q4 Patch 1 | NI-DCPower: 2024 Q1 | NI-DCPower: 2024 Q2 | NI-DCPower: 2024 Q3 | NI-DCPower: 21.3.2 | NI-DCPower: 21.3.3 Resolved Version: N/A Added: Jul 3, 2024 |
|
2558394, 2807457 |
Calling niDCPower Wait for Event on multiple channels simultaneously will rarely return error -1074116981 on the PXIe-4162 and PXIe-4163When niDCPower Wait for Event is called using the Measure Complete Event on multiple channels on a PXIe-4162 or PXIe-4163 in parallel, a channel will occasionally return an internal hardware error, -1074116981. Once in this state, the error can only be cleared by performing a device reset. The error message looks similar to the following:
Workaround: Use a simple for loop instead of parallel for loop around the niDCPower Wait for Event (using Measure Complete Event) function call.
|
Reported Version: NI-DCPower: 2023 Q4 Resolved Version: N/A Added: Oct 24, 2024 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
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