This document contains the PAtools known issues that were discovered before and since the release of PAtools 2024 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 |
|---|---|---|---|
| 2880704 |
Updated of SystemLink result is not workingThe PAscript function to update a SystemLink result is not working correctly.
Workaround: There is currently no known workaround for this issue. |
Reported Version: PAtools Runtime System 2024 Q4 Resolved Version: N/A Added: Oct 29, 2024 |
|
| 2881568 |
TestAnalyzer displays the wrong Runtime System numberWhen the TestAnalyzer is started from the Application Center for a specific Runtime System, in the title of the TestAnalyzer window the wrong Runtime System number is displayed.
Workaround: There is currently no known workaround for this issue.
|
Reported Version: PAtools PAconfigurator 2024 Q4 Resolved Version: N/A Added: Oct 29, 2024 |
|
| 2881816 |
Runtime runs out of pab memory because of PAscript SystemLink commandsThe call of PAscript functions like “createResult” and “createStep” consume pab memory. If there are too many of these calls during one test, the runtime system can run out of pab memory leading to an error message.
Workaround: Reduce the number of “createStep” calls or unload and reload the test.
|
Reported Version: PAtools Runtime System 2024 Q4 Resolved Version: N/A Added: Oct 29, 2024 |
|
| 2897017 |
Generation error when importing/scanning data with EtherCAT HotConfig editor in new PAconfiguratorWith the 2024Q4 release the EtherCAT HotConfig group editor is available in the new PAconfigurator. However, when the network is scanned through this new group editor an error shows up upon generating at test stating that “2. Parameter (INT) unknown”.
Workaround: Use the classic PAconfigurator to scan data with the EtherCAT HotConfig editor.
|
Reported Version: PAtools PAconfigurator 2024 Q4 Resolved Version: N/A Added: Oct 29, 2024 |
|
| 2904503 |
Profibus driver restartsThe integration of the Profibus driver is not complete, which can result under specific conditions that the Profibus driver reboots itself when in operation and, thus, is not usable. Workaround: There is currently no known workaround for this issue.
|
Reported Version: PAtools Runtime System 2024 Q4 Resolved Version: N/A Added: Oct 29, 2024 |
|
| 2906299 |
Error when Sequence Table is closedIf the second level of a sequence table is opened and eventually closed again, an error message appears stating that multiple properties cannot be set simultaneously
Workaround: After closing the error, the sequence table can be closed normally.
|
Reported Version: PAtools PAconfigurator 2024 Q4 Resolved Version: N/A Added: Oct 29, 2024 |
|
| 2911298 |
XML import of a library failsThe import of a PAscript XML library fails if only the library is imported. Workaround: The library can be imported via a module import or the content of the library can be copied manually into a newly created library.
|
Reported Version: PAtools PAconfigurator 2024 Q4 Resolved Version: N/A Added: Oct 29, 2024 |
|
| 2921610 |
Recovery file overwrites setpoints when starting a sequenceWhen recovering a sequence in the Battery Cell Application, the setpoints from a recovery file (sav-file) overwrite the actual setpoints that are defined in the user box. Workaround: Navigate to the sav-folder on the PXI and replace the setpoints of “CCSub_Temperature.SP” and “CCsub_Humidity.SP” in the file “abt.sav” with the new values.
|
Reported Version: PAtools Battery Application 2024 Q4 Resolved Version: N/A Added: Aug 11, 2024 |
|
| 2924893 |
Profinet connection interrupts on a PXI-8862Using a CPU with the split_lock_detect feature and a Linux-Kernel-Version >= 5.6, the Profinet connection faces interrupts frequently. Workaround: Determine whether the used CPU is affected by executing this command in a command line tool (e.g., Putty) on the PXI: grep 'flags' /proc/cpuinfo | head -n 1 | tr ' ' '\n' | grep split_lock_detect Two options to fix this issue: 1.For a temporary solution: Executing this command in a command line tool on the PXI: sysctl -w kernel.split_lock_mitigate=0 2.For a persistent solution follow the following steps: a. create the /boot/runmode/split_lock_detect.cfg file by executing this command in a command line tool on the PXI: echo 'set otherbootargs="${otherbootargs} split_lock_detect=off"' > /boot/runmode/split_lock_detect.cfg b. add this line to /boot/runmode/bootimage.cfg file: if [ -f "/runmode/split_lock_detect.cfg" ]; then source "/runmode/split_lock_detect.cfg" fi c. after the restart of the PXI you can validate your changes: cat /proc/cmdline
|
Reported Version: PAtools Runtime System 2024 Q4 Resolved Version: N/A Added: Aug 11, 2024 |
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