EasyManua.ls Logo

HP 3336A - Page 42

HP 3336A
147 pages
Save Page as PDF
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Model
3336A/B/C
Operation
3-123.
Step
One.
Choose
one
of
the
Bus
Messages
for
conversion.
Begin
with
the
System
@
Management
Messages
since
they
are
usually
easier
to
convert
to
controller
statements
than
the
Trigger
or
Data
Messages.
Locate
the
description
of
the
Bus
Message
in
this
manual.
The
description
of
each
message
contains
the
following
information
as
applicable:
—the
response
of
the
-hp-
3336
to
the
message.
—~the
device
dependent
information
required
for
the
controller
statement.
—any
prerequisite
operations.
—suggestions
for
optimizing
the
use
of
the
message.
The
device
dependent
information
required
for
the
controller
statement
is
always
found
-under
the
heading
Implementation.
NOTE
1.
The
Require
Service
Message
originates
at
the
instrument
rather
than
at
the
controller.
Consequently,
there
is
no
controller
message
that
implements
this
message.
This
does
not
diminish
the
importance
of
this
message
to
the
operator.
Study
it
carefully
in
turn.
2.
The
Status
Bit,
Pass
Control,
Abort,
and
Trigger
Messages
can
not
be
implemented
because
the
-hp-
3336
does
not
have
the
capacity
or
the
need
to
respond
to
them.
3-124.
Step
Two.
Find
the
description
of
the
selected
Bus
Message
in
the
controller
documentation.
This
description
usually
consists
of
the
following
information:
©
—one
or
more
controller
statements
that
implement
the
message.
—mnemonics
for
the
controller
statements.
—syntax
of
the
controller
statements.
—suggestions
for
optimizing
the
implementation
of
the
message.
3-125.
Step
Three.
Integrate
the
device
dependent
information,
found
in
Step
One,
with
the
controller
dependent
information
found
in
Step
Two.
The
syntax
of
the
controller
statement
explains
how
this
should
be
done.
3-126.
Step
Four.
Record
the
statements
that
implement
each
Bus
Message
in
Table
3-1
as
they
are
found.
The
operator
needs
to
translate
the
Bus
Messages
only
once.
Table
3-1
can
be
used
as
a
quick
reference
when
writing
programs
in
the
future
and
should
be
included
in
your
system
documentation.
3-127.
When
searching
for
a
message
in
the
controller
documentation,
it
is
usually
best
to
start
with
the
Table
of
Contents.
If
the
message
is
not
referenced
there,
look
in
the
Index.
In
order
to
use
the
twelve
bus
messages,
the
controller
documentation
must
organize
the
In-
put/Output
Operation
programming
statements
according
to
the
definitions
of
the
twelve
messages.
It
would
be
unusual
for
any
manufacturer
of
controllers
to
do
otherwise.
The
ex-
act
nomenclature,
however,
used
to
describe
the
Bus
Messages
may
vary
from
one
manufac-
turer
to
another.
-
NOTE
&
If
your
controller
documentation
does
not
contain
a
program-
mable
statement
for
a
particular
Bus
Message,
the
controller
may
not
be
capable
of
implementing
the
message.
3-21

Related product manuals