User manual

Computer Gateway User Manual 2-10 5/96
2.4
Certain data access-request messages do not require an ACIDP name and will be honored
regardless of ACP/ACIDP connection status. See Tables 2-1 and 2-2 for summaries of
restrictions enforced by the CG depending upon ACIDP installation mode.
2.4 CG/HOST STARTUP STEPS
Startup of the CG and of the host processor requires a series of steps that begins with
configuration and loading of the CG, goes through establishment of communication
between host processor and CG, and ends with modification of the CG database by the
host processor.
2.4.1 Preparing the CG
The first step in configuring the CG—from a TDC 3000
X
Universal Station—to modify
the system NCF to include the CG node. Refer to Network Data Entry as a starting point if
this procedure is unfamiliar. As part of LCN Nodes Configuration, you will assign one or
more Process Units to the CG (see Network Form Instructions and Appendix A of this
manual for additional information).
Additional CG configuration entries are made through the CG Configuration display. To
reach this display, call up the Engineering Main Menu at a Universal Station on the same
LCN as the CG, then select the "Computing Module" target. This brings up the Computer
Gateway Build and Configuration menu from which you select the "CG Configuration"
target.
Your selection of CG configuration type is controlled by the hardware used to interface
your host to the LCN. Select either "CLI-HDLC" or "CLI-BISYNC" depending on the
data link protocol used. Additional CG configuration choices you will have to make
depend on this first selection and include the link baud rate and a floating-point number
conversion type. See Section 4 of the CG Parameter Reference Dictionary for information
on these CG configuration entries.
NOTE
On completion of CG/PLNM configuration (or configuration change), you must demand a CG
checkpoint save, then shutdown and restore the node from the saved checkpoint to enable
the changes to take effect.
Point building (of ACIDPs and CRDPs) can be deferred for the moment, but must precede
any connection to, or use by, an ACP. Information on the building of these points and
their associated Custom Data Segments is found in Appendix E of this document.