Home Support Documentation Bugs

Battery Test System Software 2023 Q2 Known Issues

Created Jun 22, 2023

Overview

This document contains the Battery Test System Software known issues that were discovered before and since the release of Battery Test System Software 2023 Q2. 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
1596248

Test Monitor does not attach large test reports to SystemLink

TestStand report files over 80 MB are not uploaded to SystemLink and attached to the corresponding test result.

Workaround:

Ensure your report files are smaller than 80 MB or transfer them manually.
Complete the following steps to ensure the report is unique to each DUT if you are using the batch process model:

  1. Navigate to Configure > Results Processing...
  2. Select the Options... icon in the Report row.
  3. Select the Report File Pathname tab.
  4. Configure the report to be created per DUT.

Reported Version:

Battery Test System Software Toolkit 2.0

Resolved Version:

N/A

Added:

Sep 1, 2021
1985043

The NI Battery Test System Web Server does not start properly in slow computers

The NI Battery Test System Web Server windows service does not start properly and displays a timeout error in slow computers.

Workaround:

Increase the Windows service timeout value following the instructions here: A slow service does not start due to time-out error in Windows

Reported Version:

Battery Test System Software Toolkit 2022 Q2

Resolved Version:

N/A

Added:

Jun 27, 2022
2351968

The NI-VCOM custom device doesn't use latest arxml/dbc and rbsconfig files for new configurations

Deploying a new configuration with the VeriStand NI-VCOM custom device fails to upload the new arxml/dbc file or rbsconfig_linx to the target.

Workaround:

  1. Import a configuration in the system explorer to the VeriStand NI-VCOM custom device.
  2. Click on the Set RBS Configuration button and then close the Configurator dialog. No action is necessary in this dialog.
  3. Save the system definition file to add the Dependency properties.
  4. Deploy the system definition.

Reported Version:

Battery Test System Software Toolkit 2022 Q4

Resolved Version:

N/A

Added:

May 30, 2023

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