NI-DCPower 20.5 Known Issues

Overview

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

847978 480527

Upgrading from Windows 8.0 to Windows 8.1 can result in lost configuration information

Upgrading 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 Measurement & Automation Explorer.

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 step

The 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

1024555

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

When 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 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 MAX do not work for NI-DCPower devices on RTOS target systems

For NI-DCPower devices on a NI Linux Real-Time or PharLap target system, the Test Panel button in 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

1113818

Errors reported in English instead of Japanese on LinuxRT for NI-DCPower driver

On a Linux Real-Time target with the language set to Japanese, the NI-DCPower driver returns errors in English instead of Japanese.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-DCPower 20.5

Resolved Version:

N/A

Added:

Sep 7, 2020

1125517

NI-DCPower error -1074097807 on LinuxRT when used with SystemLink

If self-calibration or self-test runs from SystemLink before executing commands with the driver through MAX or LabVIEW, then driver operations including self-test and self-calibration in MAX or LabVIEW result in error -1074097807 "File was not found at specified path."

If the driver executes commands in MAX or LabVIEW before running a self-test or self-calibration in SystemLink, then SystemLink throws error -1074097807.

Workaround:

Option 1:
  1. Reformat that target and reinstall all the relevant drivers and software.
  2. Do not use self-test or self-calibration from SystemLink.

Option 2:
  1. Run niDCPower Initialize with Channels.vi in LabVIEW. Disregard any error that may appear.
  2. SSH into the LinuxRT controller and execute this command as admin:
    chmod -R 0777 /var/lib/ni-dcpower/sessions
  3. Reboot the LinuxRT controller.

Option 3:
  1. Run niDCPower Initialize with Channels.vi in LabVIEW. Disregard any error that may appear.
  2. Use the SystemLink state editor to create and install the following state to the LinuxRT controller:
/var/lib/ni-dcpower/sessions/:  
  file.directory:    
   - source: /var/lib/ni-dcpower/sessions/    
   - user: admin
   - dir_mode: 777
   - file_mode: 777
   - recurse:
      - user
      - mode

system.reboot:
    module.run

Reported Version:

NI-DCPower 20.5

Resolved Version:

N/A

Added:

Sep 7, 2020

1125517

NI-DCPower error -1074118653 or -1074097807 on LinuxRT when used with Python

nidcpower.errors.DriverError: -1074118653: Cannot open a session to the instrument.
  • If self-calibration or self-test runs from MAX before executing commands with the driver through Python, then Python use of the driver produces this error.
  • any driver commands execute in LabVIEW before executing commands with the driver through Python, then Python use of the driver produces this error.
-1074097807: File was not found at specified path.
If Python executes driver commands before MAX or LabVIEW, then driver operations in MAX or LabVIEW produce this error.

Workaround:

  1. Run niDCPower Initialize with Channels in Python or LabVIEW. Disregard any error that may appear.
  2. SSH into the LinuxRT controller and execute this command as admin: 
    chmod -R 0777 /var/lib/ni-dcpower/sessions
  3. Reboot the LinuxRT controller.

Reported Version:

NI-DCPower 20.5

Resolved Version:

N/A

Added:

Sep 7, 2020

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