DH Instruments PPC4, Operation And Maintenance Manual

Page: 54 / 228

PPC4™ OPERATION AND MAINTENANCE MANUAL
© 2009 DH Instruments, a Fluke Company Page 42
3.2.23 Drivers

PURPOSE
To control the output signals of PPC4’s 8 channel, 12 V external drivers.

PRINCIPLE
PPC4 external drivers are available to drive peripheral equipment in a PPC4 system, for
example, solenoid valves or the optional Self Purging Liquid Trap (SPLT). The driver
electrical connections are available from a rear panel connector

Caution
The PPC4 PURGE function makes use of the valve driver option. Valve
driver number 8 is used to actuate the SPLT exhaust valve. The SPLT
exhaust valve Is actuated when performing the Purge function and in the
background every time the PPC4 VENT function is used. When making use
of valve drivers, note that when the Purge function is enabled, valve driver
number 8 will be actuated independently of user initiated valve driver
commands (see Section 3.2.17).

OPERATION
For Basic Interface, see Section 4.4.6.
For Advanced Interface, see Section 5.7.4.
3.2.24 Remote

PURPOSE
To configure the PPC4 COM1, COM2, IEEE-488 (GPIB), or Ethernet communication ports.
To test COM1 and COM2 communications. To select remote programming communications
format. (COM1 and COM2 ports are standard on all PPC4 controllers. IEEE-488 (GPIB) and
LAN ports are installed only if the appropriate communication option is purchased.)

PRINCIPLE
The PPC4 has two RS232 communications ports referred to as COM1 and COM2 as well as
a front panel USB port. Optionally, the PPC4 may be configured with either an IEEE-488
(GPIB) port or Ethernet port. COM1, IEEE-488, and Ethernet are for communicating with a
host computer (see Section 6.2). COM2 is reserved for communicating with an external
device (i.e. RPM4, multimeter, etc.). Port settings can be viewed and changed using front
panel commands. The USB port(s) allow connection with a PC using PPC4 Cockpit software
(see Section 6.2).
The PPC4 has 3 different syntax formats available for remote program commands. Classic
format is compatible with previous PPC products and is the default format. Enhanced format
follows the syntax, format, and status reporting features of IEEE Std 488.2. Alternatively, a
custom command format defined by the Command Interpreter Editor is selectable. The
details of each are covered in Section 6.4 and the command interpreter documentation,
included with the PPC4 API documentation when PPC4 Cockpit is installed (see Section
6.2.2). Select and view the active command format.

OPERATION
For Basic Interface see Section 4.5.2.
For Advanced Interface see Section 5.7.9.