sequence conversion

[heitke]

Hello:

I am trying to convert a LabWindows/CVI sequence file to TestStand but
I get warnings/errors when opening or running the sequence in TestStand.

After converting the file I do a File->Open in the TestStand Sequence
Editor and I get a "Open Sequence Warning" popup listing a bunch of items
it was unable to load due to undefined references.

When I attempt to run the sequence I get the following error:

Unable to get standard CVI step module address.
A CVI code module has unresolveable external references.
Error Code: -17709

The sequence file is pointing to an OBJ file. Do I have to rebuild the
object file prior to conversion or something?

We are attempting to migrate from CVI to TestStand and there will be a
lot of sequenc
e conversion taking place. I am doing the pilot and trying
to document the procedure.

The User Manual, page 4-31, says to refer to the online help under
"Converting From the Labwindows/CVI Test Executive to TestStand" but
I couldn't find anything in the windows help file or on the net.

Thanks for any help.

-Steve
--
________________________________________________________________________
Steve Heitke Tellabs Operations, Inc.
heitke@tellabs.com Advanced Test Methods
http://www.tellabs.com Bolingbrook, IL 60440
________________________________________________________________________

[Paul Mueller]

Steve,

Your object files probably depend on other object files or support libraries
that haven't been loaded. When you ran from the test executive, you included
them in the CVI project so they were preloaded.

TestStand is a little different because it isn't a CVI project that you build
into an application. Instead, you need to configure the CVI adapter to pre-load
your support libraries. Select Configure>>Adapters. Select the CVI Std
Prototype Adapter and click Configure. In the CVI Std Adapter Configuration
dialog, press the Configure Auto-Loading of Support Libraries Needed for
linking Objs and Libs. Add all your support libraries to this dialog. TestStand
will copy your files to the TEstStand\AdapterSupport\CVI\AutoLoadLIbs directory
where they can be preloaded.

It is often tricky to figure out which support libraries you need. For this
reason, NI and Microsoft encourage people to use DLLs instead. DLLs can
be loaded dynamically, and by default, the OS loads them for you. Usually,
you just leave DLLs in the same directory as the executable or the WIndows\System32
(\System for Win95/98).

Let us know if this doesn't work out.
Paul Mueller
National Instruments


Steve Heitke wrote:
>Hello:>>I am trying to convert a LabWindows/CVI sequence file to TestStand
but>I get warnings/errors when opening or running the sequence in TestStand.>>After
converting the file I do a File->Open in the TestStand Sequence>Editor and
I get a "Open Sequence Warning" popup listing a bunch of items>it was unable
to load due to undefined references.>>When I attempt to run the sequence
I get the following error:>> Unable to get standard CVI step module address.>
A CVI code module has unresolveable external references.> Error Code:
-17709>>The sequence file is pointing to an OBJ file. Do I have to rebuild
the>object file prior to conversion or something?>>We are attempting to migrate
from CVI to TestStand and there will be a>lot of sequence conversion taking
place. I am doing the pilot and trying>to document the procedure.>>The User
Manual, page 4-31, says to refer to the online help under>"Converting From
the Labwindows/CVI Test Executive to TestStand" but>I couldn't find anything
in the windows help file or on the net.>>Thanks for any help.>>-Steve>--
>________________________________________________________________________>
Steve Heitke Tellabs Operations, Inc.> heitke@tellabs.com
Advanced Test Methods> http://www.tellabs.com
Bolingbrook, IL 60440>________________________________________________________________________