LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

keithley 2636 error message 5038

I'm using LabVIEW to control a Keithley 2636A SourceMeter.  I connect to the Keithley through ethernet and I'm using VISA commands to communicate with the Keithley.  I'm seeing the error code 5038: Index Exceeds Maximum Reading.  I'd guess it has to do with reading the buffer: either the buffer overruns or I'm trying to read too many bytes from the buffer? Does anyone know what causes this error and how to avoid it?

 

Thanks very much,
Tim

0 Kudos
Message 1 of 7
(6,207 Views)
What is the buffer size you have defined? Can you post a screen shot of your vi?
0 Kudos
Message 2 of 7
(6,178 Views)

Hi, Tim.

 

The error 5038 is not a defined error code. If you could post a screenshot of this error message and possibly attach your code, this would be very helpful in solving this issue.

Regards,

Sara Lewandroski
Applications Engineer | National Instruments
Message 3 of 7
(6,169 Views)

This is a screenshot of most of the VI I use for reading the buffer.  The buffer reading happens in the lower right corner.  The input parameters to printbuffer() are the Start Index (I use the default, 1ms) Timeout (I use the larger of 2s and the number of points x 42 bytes in my measurement) the End Index (I use the number of points in my measurement) and the Byte Count (I use the larger of 1024ms and the number of points x 42 bytes).

ReadBuffer.JPG 

0 Kudos
Message 4 of 7
(5,984 Views)

Hey Tim,

 

Thanks for the screenshot of the code.  I see that you are running the KE24XX example.  Have you made any modifications to this example? 

 

Could you send me a spy capture of this event?  To do this:

  1. Open NI-Spy.  (Start»Programs»National Instruments»NI-Spy)
  2. Click the green start arrow to start a capture.
  3. Run the program and generate the error that you were receiving.
  4. Click the red stop button to stop the capture.
  5. Save the capture as a .spy file.  (File»Save As)

If you could provide the following information:

  1. Operation System version and bitness
  2. ADE version, type, and bitness
  3. Instrument Driver name, version, and bitness
  4. Exact instrument model, revision, and firmware version
  5. Was the instrument driver working well before? If yes, what has changed since then?
  6. Does the problem reproduce on other computers?
  7. Does the problem reproduce with other identical instruments?
  8. Instrument control bus being used (USB, GPIB, Serial, etc.)
    1. Does the problem occur in all buses?
Let me know the answers to these questions, and we'll get you up and running as soon as possible.
Regards,

Sara Lewandroski
Applications Engineer | National Instruments
Message 5 of 7
(5,965 Views)

 

Here is a capture.  

 

1. I am running  Windows XP, SP3, 32 bits

2. I'm sorry but I don't know what ADE is

3. The instrument driver info is:

Instrument Driver Technology: LabVIEW Plug and Play (project-style)

Manufacturer: Keithley Instruments, Inc.

Supported Language(s): LabVIEW

Supported Model(s): ..., 2636A

Model(s) Tested:  ... 2636A

Interface(s): GPIB, Serial, Ethernet

Firmware Revision(s) Tested: 1.4.1, 2.0.0

Certified: No

Source Code Available: Yes

Driver Revision: 2.1.2

Original Release Date: 09/01/2005

Current Revision Date: 12/03/2008

 

4. The instrument is a Keithley 2636A 

5. The instrument has always had this problem 

6& 7 I don't have the capability to test on other instruments and computers, I'm sorry

8.  connected by GPIB, but it has had the problem with LAN/ethernet connection as well

 

Thanks very much for your help. 

 

 

0 Kudos
Message 6 of 7
(5,956 Views)

Hello,

 

I got the same error and found out that I had written nbuffer ("v" was missing after "n") instead of nvbuffer at one script line.  Altough I was using a script the principal should be the same, so it might be good idea to check all the buffer names.

 

Regards,

Boga

0 Kudos
Message 7 of 7
(5,658 Views)