This document contains the NI-DCPower known issues that were discovered before and since the release of NI-DCPower 2022 Q4. 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 |
|---|---|---|---|
| 1024555 |
No device names appear when initializing a session with NI-DCPower on NI Linux Real-Time TargetsWhen 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:
|
Reported Version: NI-DCPower 20.5 Resolved Version: N/A Added: Sep 7, 2020 |
|
| 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 8, 2021 |
|
No device names appear when initializing a session with NI-DCPower on Linux DesktopWhen 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: N/A Added: Apr 19, 2022 |
||
| 2047085 |
Using Hold Threshold Mode on Range Up Behavior causes device to enter complianceOn 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 |
Reported Version: NI-DCPower 2022 Q4 Resolved Version: N/A Added: Oct 6, 2022 |
|
| 2150834 |
PXIe-4147 devices may return error -1074118504 when Sequence Step Delta Time is enabledOn PXIe-4147 device, setting current range at the first step of a sequence with Sequence Step dt Enabled is true may return error -1074118504 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: N/A Added: Oct 6, 2022 |
|
| 2157486 |
Setting Source Delay to more than the Sequence Step Delta Time may return error -1074118503On 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: N/A Added: Oct 6, 2022 |
|
| 2146998 |
When using Independent Channels, Device Reset closes/opens session, and reopening can fail, invalidating the sessionAfter 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: N/A Added: Oct 6, 2022 |
|
| 2139994 |
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 6, 2022 |
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