NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Error -18002 on LabVIEW with RunTime Engine

Good morning everyone, I have a TestStand 2020 sequence in which, within a loop, I call two VIs: one in which I write via I2C using an FPGA, and a second one in which I send the ‘Write&Read’ command.

When I run the two VIs from LabVIEW 2021 or TestStand with ‘LabVIEW Development’ selected as the adapter, everything works correctly.

However, when I run the sequence with the LabVIEW Runtime Engine as the adapter, it only works on the first iteration; on the second, it freezes, giving me error -18002: ‘VI was aborted’.

The two VIs are very, very similar (only the command sent to the FPGA changes), so I don’t understand why the error occurs.

If it helps, I open and close the FPGA reference each time using ‘Open FPGA VI Reference’ via the bitfile and ‘Close FPGA’. How can I resolve this? It’s not an insurmountable problem, but it would be better to be able to use the sequence with the Runtime Engine for stability reasons.

 

0 Kudos
Message 1 of 3
(363 Views)

Check the path of the bitfile you use for open ref, I bet the file can't be found since the Runtime Path differs from the one in the dev environment 

0 Kudos
Message 2 of 3
(360 Views)

Thanks for your reply, but I don’t think that’s the issue: I’m passing the full path, so it shouldn’t depend on whether it’s running with the runtime or not, should it? Besides, if that were the case, all the VIs where I use the bitfile should have the same problem, but they all work correctly (even that one, albeit only on the first iteration of the loop)... which is why I don’t understand

0 Kudos
Message 3 of 3
(301 Views)