NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

DLL and Test Stand

Hi,

I hope I can explain myself clearly so here goes!!

 

I have two test stations both running XP.

 

Test Stand 2.01 on both with identical test sequences and external dll.

 

From within test stand a C++ dll is called which acts on a text file script.

 

When the dll is finished the execution it should return a TRUE or FALSE back to Test Stand.

 

I have identical code on both PC’s but one will not return any value leaving the local variable, in Test Stand, empty.

 

I believe I checked every thing in Test Stand and a few places on the PC.

 

Can I have suggestions as to what and where to check to get the second PC to work!!

 

Thanks for the help

 

Simon

Just been introduced to TestStand (3.1 and 2.0.1) on the 2ed June 2007.

 

0 Kudos
Message 1 of 3
(3,067 Views)

Hi there,

it sounds like if you have all the same settings, versions and service packs (XP might be a problem I would check that).  So really the fact that the code isn't returning the value could be a clue.  WHat kind of script does it run?  Is is accessing some kind of hardware?  is the hardware setup correctly?

Are both PC's the same speed, amount of memory etc?  How about different software installed ont eh PC's?

I can't really suggest too much else to look at at the moment.  Try looking at these differences, you might see something there?

 

AdamB

Applications Engineering Team Leader | National Instruments | UK & Ireland
0 Kudos
Message 2 of 3
(3,033 Views)
Have you debugged the DLL (assuming you have the ability to do so)?  If you have source to the DLL, Verify there is no way to skip the step that sets your variable name.  For example, if your routine falls out if an error occurs, perhaps the step which sets the TestStand variable is skipped, and either the DLL or TestStand is not handling whatever error has occurred.  You may even want to confirm the DLL is handling errors at all.  Perhaps the error is not being captured.

You may want to confirm that you are not missing support code the DLL may rely on, or that the support code is out of date.  Also check to make sure your Windows Path environment variable has all necessary paths in it.

Matthew
0 Kudos
Message 3 of 3
(3,022 Views)