LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Keithley 2700 Initialize Error

I am using a Keithley 2700 DMM with two 40 Channel I/O cards (7702).  When the I/O cards are not installed, the DMM initializes fine. When we install one or both of the I/O boards, the Initialize function returns the following error:

Error -1074110464 occurred at KE2700 Initialize.vi.

Possible reasons:

Driver Status:  (Hex 0xBFFA6000) Repeated Capability lists cannot be modified after attributes have been added to them.

I have a second DMM with an older firmware revision, and it has the same problem.  An NI Forums search found one reference to "Repeated Capability lists" that indicated this is IVI related. I am using the Keithley LabVIEW drivers that impliment the DLL (2.0.2.702), but I am NOT using the LabVIEW IVI functions.






Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.

"You are what you don't automate"
Inplaceness is synonymous with insidiousness

0 Kudos
Message 1 of 10
(5,712 Views)
Hi Phillip,

I wanted to have a few clarifications here.
1)  what are you using to communicate with the device(GPIB, Serial, VXI)?
2) where did you get these drivers? were they downloaded from Keithley's site, or from our site?
3) are they plug and play drivers, or are they IVI drivers?

Can you attach a spy capture to your next post too?

Thanks,
Matt S.
National Instruments

LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.
0 Kudos
Message 2 of 10
(5,689 Views)

We are using GPIB, with a DLL based driver from 2002. This is supposed to be IVI compliant, but we never used the IVI functions. We only used the KE2700 wrapper functions for the DLL.

We punted these older drivers, and have switched to the newer Plug and Play drivers from the NI web site. There are a few issues in switching from the DLL based drivers to the Plug and Play, but we're working through them. At least with the Plug and Play drivers, I can step through and see what's going on. DLL drivers are a black-box, and should be called Plug and Pray.


Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.

"You are what you don't automate"
Inplaceness is synonymous with insidiousness

0 Kudos
Message 3 of 10
(5,670 Views)

hi there

after struggling with IVI layers from Keithley and NI we developed our own driver - layer with pure VISA. needs some string formatting at the start but its worth a try. from then on we never had any problems anymore.

best regards

chris

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
0 Kudos
Message 4 of 10
(5,650 Views)
I encounter the same problem, I call the KE2700_InitWithOptions in LabWindows/CVI 7.1, I got a error said:
"Primary Error: (Hex 0xbffa6000), Repeated capability lists cannot be modified after attributes have been added to them."
after the 7701 switch module had been plugged in.
 
According the header file, the .lib version is 2.0, and it was last revised on 5/07/02 by Xiuwen,
 
Here is the messages recorded in the NI Spy
1.  viOpenDefaultRM (0x001FB9A8)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.317       Call Duration: 00:00:00.172
Status: 0 (VI_SUCCESS)
2.  viOpen (0x001FB9A8, "GPIB0::16::INSTR", 4, 0, 0x001FBE68)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.489       Call Duration: 00:00:00.078
Status: 0x3FFF0077 (VI_WARN_CONFIG_NLOADED)
3.  viSetBuf (0x001FBE68, 3, 5000)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
4.  viSetAttribute (0x001FBE68, 0x3FFF002D, 1)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
5.  viSetAttribute (0x001FBE68, 0x3FFF002A, 1)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
6.  viGetAttribute (0x001FBE68, 0x3FFF0171, 1)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
7.  viGetAttribute (0x001FBE68, 0x3FFF001A, 3000)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
8.  viSetAttribute (0x001FBE68, 0x3FFF001A, 10000)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
9.  viPrintf (0x001FBE68, "*OPT?
")
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
10.  Formatted viWrite (0x001FBE68, "*OPT?.", 6, 6)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.567       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
11.  viScanf (0x001FBE68, "%s")
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.582       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
12.  Formatted viRead (0x001FBE68, "7701,NONE.", 5000, 10)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.582       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
13.  viClose (0x001FBE68)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.582       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
14.  viClose (0x001FB9A8)
Process ID: 0x00000398         Thread ID: 0x00000EF4
Start Time: 15:44:13.582       Call Duration: 00:00:00.000
Status: 0 (VI_SUCCESS)
Is there anybody can help me out? thanks.
0 Kudos
Message 5 of 10
(5,291 Views)

The IVI driver we have on our website is a link to the Keithley IVI driver.

What are the problems you are seeing with the Plug and Play drivers?  

0 Kudos
Message 6 of 10
(5,282 Views)
Maybe this follow-up CVI qustion should have been posted in another forum...

Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.

"You are what you don't automate"
Inplaceness is synonymous with insidiousness

0 Kudos
Message 7 of 10
(5,280 Views)
Hello wilcn,
      Since the IVI Driver for the 2700 is not NI certified or NI supported, I highly recommend that you contact Keithley directly for support on this issue.  Another route would be to try the LabVIEW Plug and Play driver for the 2700, which is NI Certified and Supported.  Let us know and which route(s) you choose and how it goes.

Cheers,

NathanT

0 Kudos
Message 8 of 10
(5,246 Views)

Phillip,

 

I realize this is an old thread but how did you solve this problem?  With TestStand, I'm using simulation mode trying to use the KE2700_InstallPseudoCard function.   I'm just trying to set up a simple read of 4 inputs on a 7708 using the driver docs. I don't have hardware.

 

IVI Foundation\IVI\Drivers\KE2700\Keithley.IVI.NET.KE2700.dll error:

An exception occurred inside the call to .NET member 'InstallPseudoCard':
System.Runtime.InteropServices.ExternalException (0xBFFA6000)\r
at Keithley.IVI.NET.KE2700.PInvoke.ThrowError(IntPtr handle, Int32 code)\r
at Keithley.IVI.NET.KE2700.InstallPseudoCard(String Slot, String Model)[Error Code: -1074110464]

 

IVI Foundation\IVI\Bin\KE2700_32.dll driver error:

Repeated Capability lists cannot be modified after attributes have been added to them.

 

Same error just sometimes helps to see other details.

 

Thanks,

Pat

0 Kudos
Message 9 of 10
(4,398 Views)
This really is an old and unrelated thread. IVI.NET drivers are not from NI and TestStand has its own board. I've only ever ever used IVI-C drivers so I have no idea what is required to use the one you have, sorry.
0 Kudos
Message 10 of 10
(4,393 Views)