09-15-2006 06:10 AM
09-15-2006 06:17 AM
09-17-2006 04:58 AM
09-18-2006 03:27 AM
09-18-2006 03:35 AM
I encountered with such problem too.
I suppose that the possible issues are interconnection between LabVIEW and TestStand or the usage of a wrong adapter at RUN TIME.
I still did not get the solution from NI, but when i will get i will publish!
09-18-2006 04:49 AM
Hi Ray,
Thank you for the reply.
To check for problems similar to your suggestion, I added a Labview Action step to the sequence,
so that it was the first to be executed.
This new step performed as required, but then the next step (the original first step) caused a -18002 error.
regards,
Gary.
09-19-2006 04:34 AM
Hi Guys,
Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
Best wishes,
Mark
Applications Engineer
National Instruments
10-16-2006 04:32 AM
Looks like I may not have Mass Compiled all the files involved - will have to be more careful in future.
regards,
Gary.
10-19-2006 12:41 AM
After a lot of efforts the solution - MASS COMPILING all of files.
It helped!