beautypg.com

Ieee-488 parallel interface, Protocol, Ieee-488 parallel interface -2 – INFICON MDC-360 Thin Film Deposition Controller User Manual

Page 130: Protocol -2

background image

MDC-360 DEPOSITION CONTROLLER

11-2

COMPUTER INTERFACE

lists pin signal assignments, including a definition

whether t

l is

-360 o

inpu

the MDC 60.

d on th

ont p

and labe

RS-232 c

us

485 por

auto

cally set

to operat

fol

ud, 8 Bit data, N

arity

top bit

-488

PARALLEL

INTERFACE

-488 inter

e pro

s the MDC-360 with the ability to

computer

nd oth

evices ov a standard

488

he IEEE-488

terfac

lso know

s GPIB or

prov

chronous interface between up to 15 individual devices

mean

at on

mputer e

pped with

-48

munic

with

to 14 MD

360 contro

othe

Figure 8-5

a

-3

, inclu

g a d

ition of whether the signal is an output

an inp

to the

C-360.

rial po

can s

e used w

IEEE-488 installed.

terfaces use the same input and output

uff

,

at th

ame t

This wi

esult in c

tio

All communication

e

c

er

d the MDC-3

are in the for of

dress - The controller address byte defines the controller

that sho

nge from 0 to 32 (set via Edit System Setup,

). A controller address of zero will be

uction code byte, message length byte and the

of

he signa

an

output from the MDC

r an

t to

-3

The DJ11 jack locate

e fr

anel

led

an not be

ed if

RS-485 is installed.

The MDC-360’s RS-

s:

t is

mati

up

e with the

lowing

specification

9600 Ba

o P

, 1 S

11.4 IEEE

The optional IEEE

fac

vide

communicate with

s a

er d

er

IEEE-

interface bus. T
an eight bit parallel asyn

in

e, a

n a

HPIB,

ides

on the same bus. This

s th

e co

qui

an IEEE

8

interface card can com

ate

up

C-

llers or

r

devices.

The pin layout of the IEEE-488 port is shown in

nd Table 8 lists

pin signal assignments

din

efin

from the MDC-360 or

ut

MD

Both of the RS-232 se

rts

till b

ith

However, since both in

ed

message b

ers

they should not be us
errors.

e s

ime.

ll r

ommunica

n

11.5 PROTOCOL

s betw en the omput

an

60

m

message character strings with the format:

* Two byte header - FFh,FEh i.e. Chr$(255),Chr$(254)

*One byte controller ad

uld receive the message, or should respond to the message by transmitting

data. The controller address will ra
Edit Utility Setup, Interface Address
received by all controllers except in the case of the IEEE-488 interface. With this
interface, only the addressed device will receive the message.

*One byte instruction code.
*One byte message length.

* 0-249 byte message.

* One byte checksum, for the instr

0-249 byte message.