Battery Test System Software Toolkit 2.0 Known Issues
Overview
This document contains the Battery Test System Software Toolkit known issues that were discovered before and since the release of Battery Test System Software Toolkit 2.0. 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 |
|---|---|---|---|
| 1341233 |
Battery Test System Toolkit examples do not initialize models in an OS that does not use period decimal separatorsVeriStand triggers an alarm due to an improper model initialization when the operating system language configuration is set to use a non-period decimal separator. This error occurs when running the SAE J1798 Battery Test Stand example project and when creating a demo project from the VeriStand home screen. This error occurs because the model initialization file uses "." as a decimal separator instead of the "," used in other languages, and VeriStand uses the operating system language setting to parse to double floating points.
Workaround: Replace the period decimal separators with commas in the model initialization file, located in Models\Model Initialization\Model Initialization.txt under the VeriStand project folder.
|
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: Mar 26, 2021 |
|
| 1374772 |
The Battery Test System Software Suite may fail when installing NI-XNETThe Battery Test System Software Suite may fail when installing NI-XNET in computers with restricted IT settings.
Workaround: Work with your IT department to ensure NI-XNET can install and start its services on the computer.
|
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: Mar 26, 2021 |
|
| 1376914 |
XNET & DAQ modules in same chassis can cause XNET devices to fail if an incorrect DAQ channel path is usedIf a cDAQ-9189 chassis in the system contains a mix of XNET (CAN/LIN) and DAQ modules, and an incorrect channel path is entered into the Network DAQ custom device configuration, then the Network DAQ custom device returns an error. If the custom device has the option to "Try Reconnecting in Error?" enabled, then the XNET devices installed in the chassis will stop working.
Workaround: To recover from the error condition, reset the chassis from NI MAX and reserve the chassis To prevent the condition, uncheck the "Try Reconnecting in Error?" setting in the Network DAQ custom device.
|
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: Mar 26, 2021 |
|
| 1375902 |
User Manual provides incorrect information for UPS state in Standby modeDescription: The Uninterruptible Power Supply (UPS) is Off when
the Battery Test System is in Standby mode, contrary to what is shown in Table 8 of the Battery Test System User Manual.
Workaround: Use the information provided in the Description column of Table 9 in the Battery Test System User Manual. The table in the Downloads section of this page contains the correct information. |
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: Mar 26, 2021 |
|
| 1351796 |
Error occurs during sequence execution when connection with the SystemLink server is interruptedRunning a test sequence without the "Enable Store and Forward when Disconnecting from Server" option enabled causes an error to be thrown if the connection between the computer executing TestStand and the SystemLink server is interrupted. The Battery Test System User Manual does not explain how to prevent this error.
Workaround: Enable the "Enable Store and Forward when Disconnected from Server" setting in the result processing settings of the NI SystemLink Test Monitor Client. Learn more here: Storing and Forwarding Offline Test Data
|
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: Apr 5, 2021 |
|
| 1421195 |
TestStand's memory usage increases when using the Battery Test System Software ToolkitTestStand's memory usage may increase over time as tests execute when
using the Battery Test System Software Toolkit.
Workaround: Use the next settings in TestStand to slow down the memory growth:
|
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: May 26, 2021 |
|
| 1596248 |
Test Monitor does not attach large test reports to SystemLinkTestStand 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:
|
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: Sep 1, 2021 |
|
| 1554849 |
TestStand reports a missing SystemLink file when using the Test Monitor with SystemLink Client R4.2 or higherTestStand returns error -2147024894 (System.IO.FileNotFoundException: Could not load file or assembly 'NationalInstruments.TestMonitorClient2020) if SystemLink R4.2 or later is installed.
Workaround: Contact NI Technical Support for assistance.
|
Reported Version: Battery Test System Software Toolkit 2.0 Resolved Version: N/A Added: Sep 1, 2021 |
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
Downloads
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).