This document contains the NI-DCPower known issues that were discovered before and since the release of NI-DCPower 20.6. 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.
|
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 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: 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.
|
Reported Version: NI-DCPower 20.5 Resolved Version: N/A Added: Sep 7, 2020 |
|
| 1056439 |
Test Panels in NI MAX do not work for NI-DCPower devices on Real-Time TargetsFor NI-DCPower devices on a NI Linux Real-Time or PharLap target system, the Test Panel button in NI Measurement and Automation Explorer (NI MAX) opens Instrument Studio instead of a test panel. Workaround: Use an example VI or a similar VI and deploy it to the target to exercise functionality instead of a test panel.
|
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 |
Issues found in this section will not be listed in future known issues documents for this product.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 847978 | 480527 |
Upgrading from Windows 8.0 to Windows 8.1 can result in lost configuration informationUpgrading the version of Windows on a system with NI-DCPower installed may result in the loss of device names, the loss of device configuration, and/or devices appearing disconnected. For more information on how to resolve this, visit ni.com/info and enter the Info Code 'excrxm'. Workaround: Reconfigure your devices in NI Measurement & Automation Explorer (NI MAX).
|
Reported Version: NI-DCPower 14.0 Resolved Version: N/A Added: Jun 30, 2014 |
| 668856 | 282622 |
SignalExpress 1.2 or earlier and the IVI Power Supply stepThe IVI Power Supply step does not support NI-DCPower in Signal Express 1.2 or earlier. Workaround: Use the native NI-DCPower Express step to access NI-DCPower from within SignalExpress 1.2 or earlier. In SignalExpress 2.0 or later, you can use either the IVI Power Supply step or the NI-DCPower Express step. |
Reported Version: NI-DCPower 1.6 Resolved Version: N/A Added: Jan 25, 2011 |
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