error 18005

[simjianyou123]

I'm new to TestStand. I encountered an error below,

Error - 18005 occurred at Parameter 'hsdio out':

Failed to convert a TestStand type to a LabVIEW type or vice versa.

What does this mean?

Is there anyway I can overcome this?

Thanks in advance.

[simjianyou123]

by the way, I am trying to run a test sequence using TestStand 4.1 and LabVIEW8.2.

the hsdio out parameter is a container with the following outputs,

1D array (ASCII Strings)

Number (DBL)

Number (I32)

Number (U16)

ASCII String

1D Array (LabVIEW IO Control)

I did not encounter errors when directly loading the sequence using TestStand.

However when I use LabVIEW to call the sequence the error 18005 occured.

[Manooch_H]

Simjianyou -

Could you please post a simple example sequence file and VI that reproduces this behavior? Also, am I correct in assuming from your comments that when you attempt to run the sequence file from the TestStand Sequence Editor, it runs fine, but when you attempt to run the sequence file from a LabVIEW User Interface you receive the error? Are you calling the VI using the LabVIEW development environment or the LabVIEW Run-Time Engine?

[muks]

Have you seen this discussion?

[Manooch_H]

Simjianyou -

Could you please let us know if the suggestions made in the discussion forum that Muks linked to fixes the error you are encountering?

Thanks.

[AmitKaria2k]

Manooch,

I was facing the same issue & was able to fix it. The error never shows up in development environment system. It appears only in deployment system.

Basically I had created a VISA container in TestStand to hold the Device name & Session reference. In initialization step I assigned Session number to "-1" just for the sake of indication that the device is not initialized.

Now while Initializing PXI-4110 I used to pass the TestStand container to LabVIEW VI. However, this was throwing error 18005 and when I opened FP of LV I saw that the Device Reference variable was not populated in LabVIEW (It was blank) which mean it was not passed from TestStand to LabVIEW.

Now, instead of initializing session to "-1" if I changed it to "0" the error disappeared and the TS was able to pass the container to LV.

I'm not sure why it works in Development system and not in Deployment. May be you investigate at NI R&D. See attached image for additional details.

This solution worked with TestStand 2010 deployment license and LabVIEW 2010 SP1 run-time engine

- Amit Karia

[Al.B]

Hi Amit,

We'd definitely like to take a look at this behavior.  Can you send a simple example that reproduces the issue so I can be sure I am testing the correct case?  Also please let me know what versions of VISA, TestStand, and LabVIEW you are currently using.

Thanks!