Section 13: LPT library function reference
Model 4200A-SCS Parameter Analyzer Reference Manual
13-22
4200A-901-01 Rev. C / February 2017
kibdefclr
This command defines the device-dependent command sent to an instrument connected to the GPIB interface.
Usage
int kibdefclr(int
pri_addr
, int
sec_addr
, unsigned int
timeout
, double
delay
,
unsigned int
snd_size
, char *
sndbuffer
);
pri_addr
The primary address of the instrument (0 to 30; the controller uses address 31)
sec_addr
The secondary address of the instrument (1 to 30; if the instrument device does not
support secondary addressing, this parameter must be -1)
timeout
The GPIB timeout for the transfer in 100 ms units (for example,
timeout = 40 = 4.0 s)
delay
The time to wait after the device-dependent string is sent to the device, in seconds
snd_size
The number of bytes to send over the GPIB interface
sndbuffer
The physical byte buffer containing the data to send over the bus (the physical
CLEAR string); a maximum of 1024 bytes is allowed
Details
This string is sent during any normal tester-based
devclr
command. It ensures that if the tester is
calling the
devclr
command internally, any external GPIB device is cleared with the given string.
Each call to
kibdefclr
copies parameters into a data structure within the tester memory. These
data structures are allocated dynamically. After the execution of the command buffer using
execut
,
these tables are cleared. Any strings previously defined must be redefined.
The tester system allows you to define a maximum of 20 clear and 20 initialization strings. Each string
may contain up to a maximum of 1024 bytes. Once defined, these strings remain in effect until the
execut
statement is processed.
Strings are sent over the GPIB interface in a first-in, first-out queue. This means that the first call to
the
kibdefclr
or
kibdefint
command is the first string sent over the GPIB. The
devclr
(
kibdefclr
) strings are always sent before initialization.
The KIBLIB
devclr
strings are sent before the
devclr
and
devint
commands execute. This may
be a problem when communicating with any Keithley-supported GPIB instruments. This may also
have an effect on the
bsweep
X
command, because the
bsweep
X
command sends a call to the
devclr
command to clear active sources. It is not recommended to use GPIB instruments when
performing tests with the
bsweep
X
command.
Also see
(on page 13-65)
(on page 13-67)
(on page 13-13)
(on page 13-16)
(on page 13-24)
