GP485A TDK Corporation, GP485A Datasheet - Page 17

• Manufacturer Part Number: GP485A
• Description: GPIB CONTROLLER
• Manufacturer: TDK Corporation
• Series: ZUPr

Specifications of GP485A

• Accessory Type: Controller
• For Use With/related Products: ZUP Series
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: Q4846340

4.6
You can program the GP485 by sending it programming messages, which are ASCII strings, via it’s
GPIB port. Each programming message is terminated with a carriage return (<CR>), a linefeed (<LF>),
or a carriage return followed by a linefeed (<CR><LF>). This is denoted by <CR> in the syntax portions
of the function descriptions and by CHR$(13) in the BASIC examples.
Programming messages can be entered in any combination of uppercase and lowercase letters.
4.6.1 Programming message example
4.6.2 How messages are processed
4.7
4.7.1 Abbreviations for arguments
4.8
4.8.1 Address of the GP485
The following lines of code are an example of a programming message in BASIC:
The programming message WRT$ contains
arguments, and CHR$ is the terminating carriage return. This programming message tells the GP485
to assert the
example is a NI-488.2 function call that allows a personal computer to control the GPIB from Microsoft
BASIC. This function outputs the string in WRT$ to the GP485.
The GP485 processes each programming message on a line-by-line basis. When the GP485 receives
a message, it buffers the message, interprets the function name and arguments, then executes the
message.
When typing in a function, separate the first argument from the function name with at least one space.
Separate each additional argument with at least one space or a comma. In the syntax portions of the
function descriptions in Table 5-5, the square brackets ([ ]) that enclosed some arguments indicate that
those arguments are optional. Do not enter the brackets as part of the argument.
The term bool is an abbreviation used for an argument in the functions description.
The values for bool are:
The GP485 uses dual addressing to determine what type of GPIB data is being processed. With dual
addressing, the GP485 recognizes two different GPIB addresses. The first address is the GP485
address. When the GP485 receives it’s own address, the data received is referred to as programming
messages; the data it sends is referred to as status information. The second address is the serial port
address. When the GP485 receives the serial port address, the data it sends and receives is referred to
as serial data.
The address of the GP485 is the primary address set with the DIP switch on the top panel. Par. 4.2.3,
with the secondary addressing disabled.
WRT$ =”eos x,10”+CHR$(13)
CALL IBWRT(GP485% , WRT$)
1 = true, on or enable
0 = false, off or disable
PROGRAMMING MESSAGE FORMAT
FUNCTION ARGUMENTS
ADDRESSING THE GP485 AND SERIAL PORT
EOI
* line when it sends the end-of-string character linefeed. The second line of the
eos
, which is the function name, x and 10 are the