Array with Uninstantiated Object Causes Error -17502 in TestStand

Updated Jul 8, 2020

Reported In

Software

  • TestStand

Issue Details

In my TestStand sequence, I am using an action step that uses a LabVIEW code module. In this code module, I am writing to an uninitialized array that holds an uninstantiated object. When the TestStand adapter is set to the LabVIEW Development Environment the sequence runs fine. However, if I switch the adapter to using the LabVIEW Run Time Engine, I receive error -17502. 

Solution

This issue is caused due to how LabVIEW allocates memory. When the development environment is chosen, LabVIEW is able to successfully allocate the memory needed and handle this exception. However, when the Run Time Engine is being used, LabVIEW does not have the same ability.

To resolve this issue, use the Development Environment as the adapter, or make changes in the LabVIEW code modules to avoid creating an uninitialized array with an uninstantiated object.

Related Links

How to Change the LabVIEW Version TestStand Uses

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement may be required, and support options vary by country.