Error 18002 when using TestStandSimpleLVGUIRTS as Labview-adapter

[_Aleksi]

Hi!

I have the NI Developer Suite. I have created a test using Teststand 2.0 and Labview 7.0 . I have created the test using LabView as the LabView-adapter. When I tried to use the TestStandLVRTS and TestStandLVGUIRTS I got the 18002 error everytime I run the test.

I contacted the finnish NI technical support, but they didn't have an answer. They told me to write TestStandSimpleLVGUIRTS as the adapter, because that is the interface I'm using. My version of Labview 7.0 doesn't include the Application Builder. I thought myself, that the problem would be with the version of the runtime-server (5.1.1)

Could someone help me with this? I'm developing these tests at my own computer and they're supposed to wor
k at the production facility as production testers.

Thanks in advance,
Aleksi Sandqvist

[RayFarmer]

Hi,

You need to re-build either the Operator Interface (which is activeX server TestStandLVGUIRTS) or the Labview runtime server (which is TestStandLVRTS.exe) with the LabVIEW application builder. As you dont have this it going to be a problem. NI do not have an updated TestStandLVRTS for TS2.0 using LV7.0 on their website yet so you need to get back to them and see if they will generate it for you.

In the short term you will have to use the LabVIEW developement software as the ActiveX server.

Regards
Ray Farmer

[_Aleksi]

Hi Ray

I got the files from the finnish NI, but it didn't really help. Now I'm getting this error message:

Error loading step 'XXXXX' of sequence 'MainSquence' in file 'xxxx.seq'
Unable to launch the 'TestStandLVRTS.Application' ActiveX automation server
Error Code: - 18001, An error occurred accessing the LabView ActiveX automation server.
Source: 'TSAPI'

I looked up the error on the forums and the solution vas to register with TestStandLVRTS /RegServer. Unfortunately this didn't help...

So what next?

[RayFarmer]

Hi Aleksi,

One thing you will need to do is mass compile the TestStand directory to bring all the associated VI's upto Ver 7.0. These will still be ver5.1.1

The Runtime server is best placed in \Components\User\RuntimeServers\LabVIEW.

If you have a TestStand.llb placed in your LabVIEW\vi.lib\AddOns then this will need mass compiling as well.

Have you used the 'Assemble Test VI's for Run-time Distribution'?

Regards
Ray Farmer

[_Aleksi]

I got the 7.0 runtime-servers and the Simple interface from National. The problem was that I had to have the RTS running when I executed the test. TestStand didn't start it, as I thought...

I'm now having problems when I try to Assemble Test VI's for... I Get an error (18002) about the VI packager.seq. Basicly I can make the necessary files with labview (application distribution) so I'm going to try that on the target machines. Do you have any answers to VI packager.seq? I looked it up on the forums, but didn't find anything that worked with this case

Best regards,
Aleksi Sandqvust

[RayFarmer]

Hi,

Looks like your RTS hasn't been registered properly. Have you tried launching the RTS manually before running your sequencefile? Is any RTS being launched when you execute a sequencefile?

For the Assemble Test Vi's... to work you need to restore the LabVIEW adapter back to using the LabVIEW development system and not one of the runtime servers by selecting the Configure | Adapters...

regards
Ray Farmer

[Elaine_R.]

One quick comment to add to Ray's suggestions, you may want to double check that you have mass compiled your VIs recently so that they are all of the same version. I would do this after switching TestStand's LabVIEW Adapter back to LabVIEW and making the other changes, so that LabVIEW is the LabVIEW ActiveX server.

The only other thing I am not sure of from your replies is, when they rebuilt your new testexec.exe, did they create you an installer for it? If you're just copying files around on your harddrive your TestStandLVGUIRTS will probably not be auto-registered.

Regards,

Elaine R.
National Instruments
http://www.ni.com/support

[_Aleksi]

Hi

I actually got my tests running at the target computer. I must stay, that in my case, the instructions and the reality were a bit apart from each other. Here's how I got mine to work.

- I installed the TestStand Engine and LabView Runtime 7.0 to the target computer
- Assembled the Test VI's for distribution.
- Copied the Simple Operator Interface and TestStandLVRTS to the target computer. Both of these prgrams I got from the finnish NI. However I didn't get an installer for the TestStandLVRTS. But doesn't it register itself when ran for the first time.
- The main trick to get all these working, was that I had to have the TestStandLVRTS running (meaning that I started it manually) for everything to
work.

I actually suspect that there maybe quite a few other developers that had this problems. After all, The Developer Suite does sell big amounts, right?

Best regards,
Aleksi Sandqvist

[Elaine_R.]

Hello Aleksi -


It it strange that you have to manually launch the LVRTS exe before your Operator Interface can call VIs. Usually the TestStand Engine can automatically launch the exe when it loads the first VI, and the exe remains running until the interface is shut down.

This may have something to do with how you've installed or copied your operator interface, but that is not a behavior commonly seen by other customers, or certainly we would have written more documentation for it...

What sort of operating system are you installing the run time engine on?

--Regards

Elaine R.
National Instruments
http://www.ni.com/support

[_Aleksi]

Hi Elaine,

I have Windows 2000 on both computers (the development and the actual tester). I have to start the LVRTS manually on both systems.

If I don't start the LVRTS ,TestStand and the RTS start the LVRTS and immediately close it, then give the error messages. If I open it manually, it works OK.

Main thing is that everything is working now, but I must say I don't fully understand why NI ships the development suite with LabView7.0 and TestStandLVRTS 5.11 (with TestStand). From what I've read this should cause problems, and if so why isn't there update/fix in the downloads?

Best regards,
Aleksi Sandqvist