Home Support Documentation Bugs

NI-DCPower 2024 Q3 Known Issues

Updated Feb 3, 2025

Overview

This document contains the NI-DCPower known issues that were discovered before and since the release of NI-DCPower 2024 Q3. 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 sessions

Occasionally 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 8, 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.

On the PXIe-4147/62/63, after using a basic sequence with Voltage Level Autorange or Current Level Autorange enabled, the Voltage or Current Level Range is not restored to the configured range. This can cause the configured Voltage or Current Level to be larger than the Level Range.

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 6, 2022
2139572

Error -50400 rarely occurs with some instrument models on Linux Desktop

On 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:
  • PXIe-4137/38/39
  • PXIe-4140/1/2/3/4/5
  • PXIe-4147

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 2, 2024
2758054

On the PXIe-4135/6/7 when Output Cutoff is triggered, it cannot be disabled without calling resetting the device

When Output Cutoff is enabled on the NI PXIe-4135, PXIe-4136, PXIe-4137, if a condition is reached which activates the cutoff on a channel, calling Reset with Channels will not clear the output cutoff condition. In this situation, the channel will continue to output a near-zero voltage and current.

Workaround:

Call Reset Device to remove the Output Cutoff condition.

Reported Version:

NI-DCPower 2024 Q2

Resolved Version:

N/A

Added:

Jun 28, 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-configured

While 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 28, 2024
2780312

The Voltage LED on the PXIe-4162 / 4163 does not always illuminate when the output is enabled

The 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 2, 2024
2758044

Output Cutoff on PXIe-4135/6/7 may cause errors when used in conjunction with Measurement Autorange

When 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:

N/A
2558394, 2807457

Calling niDCPower Wait for Event on multiple channels simultaneously will rarely return error -1074116981 on the PXIe-4162 and PXIe-4163

When 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:
Error -1074116981 occurred at niDCPower Wait For Event.vi

Possible reason(s):
Internal Hardware Error. Contact NI support.
Additional Error Info: Applicable Iso Captured: [RegPortDcBusTxOverflow]


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:

N/A

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