Teststand 4.0 IVI-DMM Step error

[Havarti]

I have Teststand 3.5 and 4.0 installed on a computer and a NI-4060 in a PXI chassis.  When I try running a sequence that has an IVI-DMM step in it in 3.5 everything runs fine.  When I try the same sequence opened in 4.0 it gives me the following attached error (both attachments are the same error one is just scrolled down so you can see the whole thing.)  I have tried adding a simple IVI step from scratch in teststand 4.0 and I get the same error.

Any ideas?

Brian

[AllenP]

That error code is defined by NI-DMM as:

"The number of concurrent sessions opened to this device has been exceeded. Only one session can be opened per device."  It sounds like you have an open session to the device already.

Allen P.
NI

[Havarti]

Thanks, I couldn't find that error when I searched the NI site.  

There are no open DMM sessions.  I tried running it after resetting the DMM using the IVI Soft Front Panel and right after a reboot with the same results.

Brian

[AllenP]

Brian,

Can you get a Spy capture of what happens when you run your sequence?  You can do this by launching NI-Spy (Start >> Programs >> National Instruments >> NI-Spy).  Under the Spy >> Options menu item, you can choose to log the capture to disk.  Can you run this in both 3.5 and 4.0 in your computer and post the files so we can see what is different between the two?

Allen P.
NI

[Havarti]

Ok, I used the version selector, went back to 3.5, and ran the sequence and it ran fine like I expected.  When I switch back to 4.0 and ran it it worked (first time in a dozen tries.)  So I switched back to 3.5 ran it and then ran it 4.0 again and it failed.  I attached a spy capture from 3.5, 4.0 worked, and 4.0 didnt work.

Brian

[Havarti]

I still haven't been able to get an IVI-DMM call to work in teststand 4.0 since the one time it did work.   Any help?

Brian

[Josh_W]

Brian,

I have been able to get IVI-DMM steps to work with TestStand 4.0 before, so we're probably looking at a problem either with your IVI configuration or with how we're using that configuration from TestStand.

To try to address the first of these two issues, could you follow the instructions in this KB: http://digital.ni.com/public.nsf/allkb/8425DA9C78C0712A86256F0300810986?OpenDocument

and attach your IVI configuration from the computer that is having trouble?

Could you attach a short sequence file that reproduces this behavior?  Are you using the same sequence file in TestStand 3.5 and 4.0?

I'm also looking into this on my side to see if I can reproduce it, but with this information I'll have a better chance.

Thanks!