Teststand project transfered to different machine (same specs) and the Initiate fails

[Nivs]

Hi all, 

I am working on a bench setup with different intruments controlled by GPIB (HP E3631 power supply, Keithley 2400 etc). We are using teststand, which calls the dll generated from Labwindows/CVI environment. Our project is recently transferred to a different machine and now the communication (initiate command) fails with the HP E3631 and rest everything is working fine. I also tried running NI spy and I see nothing when I execute the instructions seperately for HP E3631.

Can someone please help me to narrow down where the possible problem can be ( everything remains the same from the old machine to new machine). ?

Regards,

Nivesh

[mkossmann]

Which instrument driver is used for the E3631 and ( if it is installed from a windows installer) did you ensure that you really use the same version on both machines ?

What means " I see nothing when I execute the instructions seperately for HP E3631.". ? Did you run NI-Spy on both machines and you don't see any difference in the logs until the failure ? What is the exact error number for the failure ? Would it be possible that you show us the spy logs from both machines ?

[Nivs]

The driver that is used on both the machines is exactly the same copy. As i told earlier a Labwindows/CVI generated dll is called from the Teststand program. The only difference is that the machine_1 (working with E3631) have the Labwindows/CVI version 5.5 installed and the other machine has version 5.0. I am also attaching the generated Spy logs for both the machines:

1) Machine 1 has instructions for both the Kiethley and E3631 in the spy file.

2) Machine 2 has instructions only for the Keithley and it fails when it reaches the initiate instruction for E3631.

    Error code > (-1074135040 : User defined)

Thanks in advance.

[mkossmann]

That could be the same probem as  here

[Nivs]

I have installed the IVI compliance package 2.5 now, but still the same problem 😞

[Nivs]

I am also able to communicate with the device using NI MAX , but still no communication with the Teststand program.

I have Labwindows/CVI version 5.0 and I have installed IVI compliance package 2.5, can it be a problem ? I saw nothing strange, while installing the package. So I guess that should be fine.

[Hossein128]

hi,

I hope that you solved your problem. But I found somelinks which are very usefull to check.

Using IVI Drivers to Simulate Your Instrumentation Hardware in LabVIEW and LabWindows/CVI

http://www.ni.com/white-paper/4560/en

KnowledgeBase 20DC4B0Z: Timeout When Running the "tkds30xx" Getting Started VI
http://digital.ni.com/public.nsf/allkb/15B9C29DA282DDD88625693B0063ACA8?OpenDocument

Developer Zone Tutorial: How to Use an Instrument Driver in LabWindows/CVI Tutorial
http://zone.ni.com/devzone/cda/tut/p/id/4317

Developer Zone Tutorial: Getting Started Using National Instruments IVI with LabVIEW or LabWindows/CVI
http://zone.ni.com/devzone/cda/tut/p/id/3377

Good luck,

Hossein