LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Converting Labview Test Executive 5.1 to work with LV7.1.1

Jennifer/all,

I found the problem. The Testexec.ini file was empty. The same file found in the "DATABASE" folder is populated. When I moved this .ini file to the LVEXEC51 folder the callbacks are found. I think I can now build the exe version and see if it will work in the 7.1.1 environment on the target PC.

Howard 

0 Kudos
Message 21 of 27
(1,173 Views)

Jennifer/all,

I found the problem. The "testexec.ini" file was empty. When I moved the version found  in the DATABASE folder up to the LVEXEC51 folder, most of the callbacks are found. I will now try to build this version and deploy to the target.

Howard

0 Kudos
Message 22 of 27
(1,173 Views)
Thank you for posting your solution.
Eli S.
National Instruments
Applications Engineer
0 Kudos
Message 23 of 27
(1,162 Views)

Jenifer/Eli S,

 

I am having trouble with my 7.1.1 converted test executive 5.1.  When I try to run the test exec it cannot find the "Login Callback". Once I point it to the Callback.llb, it finds it and all other callbacks. I definitly have my testexec.ini file setup correctly, so it seems like the "Read System Callbacks.vi" is not working correctly. I found a reference to this problem in the knowledgbase (see link http://digital.ni.com/public.nsf/allkb/A0ADC2E9B088CE5886256682007578D4) and I did download and save the new "Read System Callbacks.vi" to the engine.llb library. This did not fix the problem. If I could just see the source for this vi, I'm sure I could fix the problem. Is there anyway that you could send me a copy of this vi with source not password protected?

 

I will include my testexec.ini file for you to check. I'm pretty sure it points to the right folders and the slashes are ok for windows...

 

Thanks,

Howard

0 Kudos
Message 24 of 27
(1,126 Views)

Hi Howard,

 

The .ini file seems to match the example in the KnowledgeBase you mentioned.  Have you made any changes to callback.llb or created any of your own callback VIs?

 

 I would mass compile callback.llb if you haven't already (Tools > Advanced > Mass Compile). 

 

The VIs are password-protected since making changes to the underlying code could affect Test Executive's performance or cause it to stop working entirely.  If mass compiling does not solve the problem, let me know and I will see if it is possible to provide unlocked VIs.

Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 25 of 27
(1,101 Views)

Jennifer,

 

The Callback.llb is straight from the Test executive install (not modified) and has been mass compiled. I do have my own custom callbacks, but they are in a separate library.

 

Having the password protection removed would allow me to troubleshoot these problems myself, and allow you to help people that are using the latest software like Test Stand.  If there was any money available for this project I would definitly be upgrading to the latest test exec to avoid using this obsolete code.

 

Thanks,

 

Howard 

0 Kudos
Message 26 of 27
(1,096 Views)

Howard,

 

I took a look at your ini file, and it looks like the last line (DefaultResourceFilePath) is missing quotes (").  I would guess that this is the source of your problem.  Because there is a space in the file name, it is probably being interpreted as two file paths by windows, which is causing it to fail loading your callbacks.

 

Let me know if this fixes your problem or not.

Josh W.
Certified TestStand Architect
Formerly blue
0 Kudos
Message 27 of 27
(1,060 Views)