L Computer Gateway User Manual CG11-510
L Implementation Computer Gateway Computer Gateway User Manual CG11-510 Release 500 5/96
Copyright, Trademarks, and Notices © Copyright 1995 by Honeywell Inc. Revision 04 - May 1, 1996 While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any indirect, special or consequential damages.
About This Publication NOTE The contents of this manual are needed by only those who intend to develop their own interface between a computer and TDC 3000X. If your TDC 3000X System includes the CM50S or CM50N, that interface is already provided and you should not need this manual. This publication provides information that will aid you in the development of the software necessary to provide the bridge between your host processor and the TDC 3000X process control system through the Computer Gateway.
Computer Gateway User Manual 5/96
Table of Contents ABOUT THIS PUBLICATION 1 INTRODUCTION 1.1 1.2 1.3 1.4 1.5 1.6 2 FUNCTIONAL OVERVIEW 2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.4 2.4.1 2.4.2 2.4.3 2.4.
Table of Contents 4 DATA LINK MESSAGES 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.2 4.2.1 4.2.2 4.2.3 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.3.6 4.3.7 4.3.8 4.4 4.4.1 4.4.2 4.4.3 4.4.4 4.4.5 4.4.6 4.4.7 4.4.8 4.5 4.5.1 4.5.2 4.5.3 4.5.4 4.5.5 4.6 4.6.1 4.6.2 4.6.3 4.6.4 4.6.5 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5 4.7.6 4.7.7 4.7.8 4.7.9 4.7.
Table of Contents 4.7.11 4.7.12 4.8 4.8.1 4.8.2 4.9 4.9.1 4.9.2 4.9.3 4.9.4 4.9.5 4.10 4.10.1 4.10.2 4.10.3 4.10.4 4.10.5 4.10.6 4.10.7 4.10.8 4.10.9 4.10.10 4.10.11 4.10.12 4.10.13 4.10.14 4.10.15 4.10.16 4.10.17 4.11 4.11.1 4.11.2 4.11.3 4.11.
Table of Contents 6 CG DATABASE CONTENT 6.1 6.2 6.2.1 6.2.2 6.3 6.3.1 6.3.2 6.4 6.5 APPENDIX A A.1 A.2 A.2.1 A.2.2 A.2.3 A.2.4 A.3 A.3.1 APPENDIX B B.1 B.1.1 B.1.2 B.1.3 B.2 B.2.1 B.2.2 B.2.3 B.2.4 B.2.5 B.2.6 B.2.7 B.2.8 B.2.9 B.2.10 B.2.11 APPENDIX C C.1 C.2 C.
1 INTRODUCTION Section 1 This section discusses the CG role in a TDC 3000X System; reviews the most significant hardware and software components of the CG; and lists the other publications you need to consult during implementation and operation of a host computer-to-CG data link. 1.1 COMPUTER GATEWAY ROLE IN TDC 3000X SYSTEMS Figure 1-1 shows an overview of the TDC 3000X System architecture.
1.
1.5 ACP INTERFACE ROUTINES HOST PROCESSOR HOST PROCESSOR SOFTWARE ENVIRONMENT* DISPATCHER PROGRAM COMMUNICATION HANDLER BISYNCH OR HDLC DATA LINK COMMUNICATION HANDLER SCHEDULER PROGRAM CG SOFTWARE ENVIRONMENT* CG COMMUNICATION HANDLER (LCN) LOCAL CONTROL NETWORK * Software environments include all databases, data access mechanisms, and other essential software.
1.6 1.6 REFERENCES The following TDC 3000X publications contain additional information related to functions of the CG. Title Publication No.
2 FUNCTIONAL OVERVIEW Section 2 This section shows how the CG works with the host processor to enable your application programs to interact with the various modules on the TDC 3000X Local Control Network (LCN). 2.1 WHAT THE HOST PROCESSOR CAN DO The following paragraphs introduce you to the types of work the host computer can do by working through the CG to access data from, and send data to, devices on the TDC 3000X Local Control Network.
2.1.2 2.1.2 Get and Store Current Process Values Application programs in the host processor can request the input of values from named data point parameters from anywhere on the LCN. These requests can be either for single points or for groups of points specified in prebuilt tables. The host processor can also request the output of values to named data point parameters anywhere on the LCN or on attached Data Hiways.
2.2 2.17 Role of Data Definition Tables The most efficient method of data exchange between the host processor and the LCN is by the use of table-driven multipoint value transfers. This is the only method provided for retrieval of history data (current LCN data can be read or written one point at a time as well as by multipoint transfers). As many as four DDTs may get or store data at the same time.
2.2.1 2.2.1.1 Scheduled Program Activation Periodic programs first run at a specified daily start time (STIME) and thereafter run at a specified time interval (RTPERIOD). Example 1: RTPERIOD = 24:00:00 STIME = 17:00:00 This periodic program will run each day at 17:00:00 hours. Example 2: RTPERIOD = 08:00:00 STIME = 07:00:00 This periodic program will run each day at the following hours: 07:00:00, 15:00:00 and 23:00:00.
2.2.2 2.2.2 Process Data Exchanges The CG receives data-exchange requests (get or store) from the host processor, performs any necessary reformatting and external-to-internal identification translation, transmits the request over the LCN, then returns the data and/or status information to the host processor. Two types of data requests are supported, single-point and table-driven.
2.3 2.3 SPECIAL SITUATIONS The following paragraphs contain some additional material about CG characteristics that may be useful, depending upon the specific way in which you wish to implement your host-processor software. 2.3.1 Host Processor Scheduling of ACPs The CG is designed to have the primary responsibility for scheduling of ACPs in the host processor. The host processor itself can schedule operation of its ACPs, but restrictions exist.
2.3.
2.3.2 2.3.2 Use of 16-Character Point Names This release of the CG is compatible with previous TDC releases (R230 and the R300 series of releases) that use 8-character point names. It also supports the use of long point names (up to 16 characters). Support for long point names is provided through new versions of those message transactions between the Host Processor and the CG that use point names.
2.3.3 The CG assumes that it is communicating with a pre-R400 system until it receives a "CG Database List" message (transaction code 47 or 147) from the host processor that requests "CG Node List" information (list type 5). This causes the CG to do two things. • The CG responds with information about the CG including the point-name length (8 or 16 characters) used on the local LCN. • The CG changes the transaction codes used for the only "unsolicited" messages that it sends to the host processor.
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.
2.4.2 2.4.2 Starting of CG-Host Processor Communications Responsibility for establishing communication between the host processor and CG is left to the CG. Whenever the CG is freshly loaded it attempts to make a Cold Restart. If communications with the host processor are interrupted following a successful Cold Restart, the CG then attempts a Warm Restart. If communication is broken at any time, the failure should be recorded at the host-processor operator terminal.
Computer Gateway User Manual 2-12 5/96
3 HOST COMPUTER SOFTWARE COMPONENTS Section 3 This section discusses the types of support programs and communication program interfaces that can be used as the base for development of host processor-resident application programs. This section deals with the ways in which applications interfaces to CG functions can be constructed with the host-to-CG data link messages as a foundation. It is only a guide; the exact requirements/specifications can vary from user to user.
3.1.1 3.1.1 Advanced Control Programs (ACPs) The preparation and installation of an ACP is a multi-step operation initiated at a host processor terminal. In summary, those steps are • • • • Prepare ACP source file(s) Compile and link the program(s) Build any required Data Definition Tables Use the ACP Installer to install the ACP in the host processor and to make the ACIDP connection, if CG scheduling is desired.
3.2 3.2 HOST PROCESSOR COMPONENTS The following paragraphs deal with the components that provide the host-processor services already noted. Figure 3.1 depicts the general structure of the software and tables as implemented in the host processor portion of the sample system.
3.2.1 3.2.1 ACP Interface Routines The application programmer is provided with a number of interface routines that allow him to give and get LCN data and to perform necessary housekeeping work.
3.2.1 3.2.1.4 Store Data This routine sends data to points in the CG, or elsewhere on the LCN. The specification of what points are to receive data, and the location of data within the calling-program's data arrays, is contained in the Data Definition Table referenced by the call. Errors encountered during execution of the routine, as well as individual point-data errors, are returned to the calling program. 3.2.1.
3.2.1 3.2.1.10 Get ACP Status This routine fetches a set of parameters that enables the requesting program to determine why the system has turned it on, and what special processing may be required at this time. 3.2.1.11 Program Delay This routine suspends execution of the calling ACP for a specified number of seconds. Program execution resumes at the statement following the delay call. 3.2.1.12 Program Termination This routine terminates the execution of the calling ACP.
3.2.2 3.2.
3.2.4 When its installation mode is Test, the data values returned to an ACP by a table-driven data-access request are replaced by test values contained in the referenced Data Definition Table. During the time that an ACIDP is Inhibited by Operator action at a Universal Station, the ACP will not be activated by the CG either by schedule or by PPS. 3.2.4 Data Definition Table Builder The DDTs are prepared and stored separately from ACPs. The ACP specifies a DDT in the data access fetch/store request.
3.2.7 3.2.7 Dispatcher The Dispatcher activates ACPs when requested by the Communications Handler or by the ACP Installer. 3.2.8 Communications Handler The Communications Handler is responsible for "blocking" and "unblocking" messages between the CG and the host processor. Additionally, it is responsible for message routing over the two links (if a second link is present).
Computer Gateway User Manual 3-10 5/96
4 DATA LINK MESSAGES Section 4 This section covers the various data transfer and support messages that pass between the CG and host processor. 4.1 MESSAGE STRUCTURE AND FORMATS In this section, emphasis is placed on the messages as they may be presented by you to the applications program.
4.1.1 Table 4-2 shows the set of startup messages, while Figure 4-1 illustrates a simple startup-message sequence including components at the communications level. Details of the initialization messages are found at paragraph 4.3. • Normal Operation-message sequences are initiated by the host processor, each with a required CG response message.
4.1.
4.1.1 CG CODE Host CODE 31 31 Time Synch message from CG; echo back by Host* 43 30 CG Restore message from CG; confirmation by Host -- 47 30 -- 48 30 -- 44 30 ** DB List Request from Host; confirmation by CG DB List Response from CG; confirmation by Host Restore complete from Host; Figure 4-1 * Time Synch message and ehco can occur during the following sequence. ** At this point normal-operation applications level messages can commence.
4.1.2 4.1.2 Data Link Messages Format Messages passed between the CG and host processor are formed of a fixed-length message header followed by message data that varies in length by message type and by content. 4.1.2.1 Message Header Format The header for each message contains eight words. Header words 3, 4, 7, and 8 are used only at the link-operation level. The remaining words are used for internal routing and processing. Significance of each header word is explained below.
4.1.2 Header word 6 Host Task Identifier (2 ASCII characters)—This field has fixed values for three CG-initiated messages and one host-initiated message. – – – – Turn on ACP (Transaction Code 2/102)—"DI" Time Synch (Transaction Code 31)—"UN" CG Restore (Transaction Code 43)—"RS" Restore Complete (Transaction Code 44)—"RS" For all other message types, the codes are defined by the host processor and are echoed in the CG responses.
4.1.2 Table 4-4 — CG Sources and Destinations of Data Link Messages CG SCHEDULER (Identifier parameter=1) TRANSACTION CODE 1/101 2/102 31 43 44 MESSAGE NAME Operator Message Confirmation/Timeout Turn On ACP Time Synchronization CG Restore Restore Complete WHERE DESCRIBED 4.9.5 4.4.5 4.2.1 4.3.1 4.3.
4.1.
4.1.3 4.1.3 Data Representations NOTE In any data-exchange message (except for History) you are required to specify the data type for each data-point parameter being transferred. You also will need to know the set of value assignments (both ordinal and character string) for any enumerations accessed. REALS—Real values consist of 32 bits.
4.1.4 The CG handles necessary conversions to/from the DPS6 or IBM format from/to the format used by devices on the LCN (IEEE 754). INTEGER—Each integer value occupies one 16-bit word with a value range of -32767 to 32767. History messages also include 32-bit integer values for sample counts. ASCII—Each ASCII value consists of a 24- or 40-byte ASCII string. A string of question marks is used to specify a "doubtful" ASCII value.
4.1.5 PARAMETER INDEX—Applies only to certain parameter types (see Computer Gateway Parameter Reference Dictionary and Hiway Gateway Parameter Reference Dictionary); when not applicable must equal zero. INTERNAL DDT TABLE NAME—The Internal DDT Table name must be from one-to-nine printing ASCII characters long and contain no leading or embedded blanks. ACP NAME—The ACP name as stored in the ACIDP parameter ACPROG when the ACP is attached.
4.2 4.2 COMMUNICATIONS HANDLER MESSAGES The messages in this group are designed for use at the communication-handler level and are not intended to be visible at the applications level. 4.2.1 Time Synchronization Message This unsolicited message from the CG sends current time and date to the host processor and is used by the CG during periods of host-processor inactivity to confirm that the data link and host processor are ready to restart or continue to function properly.
4.2.2 4.2.2 Message Confirmation This message is used to confirm that all blocks of a message have been properly received. Each message except Time Synchronization or Link Failure (and the Message Confirmation message itself) must be confirmed by the receiver (either host processor or CG) before the next message can be sent by the originator. A negative confirmation requires the originator to retransmit all blocks of the original message.
4.2.3 4.2.3 Link Failure Message This message is sent by either CG or host processor to indicate failure of one of the links in a dual-Bisynch pair. It is used as a trigger for switch-over to single-link communication. Header information: Word 1—Transaction Code = 32 Word 2—Number of Words = 1 Word 5—CG Identifier = 5 Message format: Word 1—not used Use information: On detection of a failure of its input link, the CG or the host sends this message on its output link, immediately followed by EOT.
4.3 4.3 DATA LINK INITIALIZATION MESSAGES The CG will not start the scheduling of ACPs or perform any of the normal LCN data exchanges until it has exchanged a set of initialization messages with the host processor. The CG begins by sending a time-synchronization message (see paragraph 4.2.1). When the time-synchronization message is echoed back from the host processor, the CG sends a message that informs the host processor of the type of restart.
4.3.2 4.3.2 Restore Complete This message is returned by the host processor in response to the CG Restore message, but only after completion of its initialization/synchronization process. Message content must be identical to that in the original restore message.
4.3.3 4.3.3 CG Database List Request This message is originated by the host processor to determine content of the CG database. Each request specifies one of five list types: an ACIDP list, an enhanced ACIDP list, a CRDP list, a Internal DDT list, or a CG node list.
4.3.4 4.3.4 ACIDP List Return This message is returned by the CG if the host processor has requested the ACIDP list. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 48 Word 2—Number of Words = 2 plus 12 times the number of ACIDPs Word 5—CG Identifier = 3 Message format: Word 1—Return status (integer) 0=normal status 1=invalid type Word 2—Number of ACIDPs (integer) Word 3—start of ACIDP list ACIDP list format Words 1..4—ACIDP name (8 ASCII characters) Words 5..
4.3.4 ACIDP list format Words 1..8—ACIDP name (16 ASCII characters) Words 9..14—associated ACP name (12 ASCII characters) Word 15—program status (integer) 0=NOT INST 1=TEST 2=RESTRICT 3=NORMAL Word 16—execution state (integer) 0=ABORT 1=ACCESS 2=DELAY 3=OFF 4=RUN 5=WAIT 6=FAIL Use information: There can be a maximum of 250 ACIDPs in a CG.
4.3.5 4.3.5 CRDP List Return This message is returned by the CG if the host processor has requested the CRDP list. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 48 Word 2—Number of Words = 2 plus 4 times the number of CRDPs Word 5—CG Identifier = 3 Message format Word 1—Return status (integer) 0=normal status 1=invalid type Word 2—Number of CRDPs (integer) Words 3..6—Name of CRDP number 1 (8 ASCII characters) Words 7..10—Name of CRDP number 2 (8 ASCII characters) Words nn..
4.3.6 4.3.6 DDT List Return This message is returned by the CG if the host processor has requested the DDT list. Eight-Character Tagname Form Header information: Word 1—Transaction-Code = 48 Word 2—Number of Words = 2 plus 5 times the number of Internal DDT tables in-CG Word 5—CG Identifier = 3 Message format: Word 1—Return status (integer) Use information: There can be a maximum of 40 Internal DDTs per-CG. 0=normal status 1=invalid type Word 2—Number of Internal DDTs (integer) Words 3..
4.3.7 4.3.7 Enhanced ACIDP List Return This message is returned by the CG if the host processor has requested the enhanced ACIDP list. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 48 Word 2—Number of Words = 2 plus 20 times the number of ACIDPs Word 5—CG Identifier = 3 Message format: Word 1—Return status (integer) ACIDP list format Words 1..4—ACIDP name (8 ASCII characters) Words 5..
4.3.7 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 148 Word 2—Number of Words = 2 plus 24 times the number of ACIDPs Word 5—CG Identifier = 3 Message format: Word 1—Return status (integer) ACIDP list format Words 1..8—ACIDP name (16 ASCII characters) Words 9..14—associated ACP name (12 ASCII characters) Word 15—program status (integer) 0=NOT INST 1=TEST 2=RESTRICT 3=NORMAL Word 16—execution state (integer) 0=ABORT 1=ACCESS 2=DELAY 3=OFF 4=RUN 5=WAIT 6=FAIL Words 17..
4.3.8 4.3.8 CG Node List Return This message is returned by the CG if the host processor has requested the CG node list. The information returned includes the configured values of a number of CG parameters.
4.4 4.4 PROGRAM SCHEDULING AND STATUS MESSAGES 4.4.1 ACIDP Program Mode Change Request This message originated by the host processor, requests connection of an ACP to an ACIDP, and/or to change the PROGSTAT value. The allowed modes are: NOT INST, TEST, RESTRICT, and NORMAL. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 22 Word 2—Number of Words = 11 Word 5—CG Identifier = 3 Message format: Words 1..4—ACIDP name (8 ASCII characters) Words 5..
4.4.2 4.4.2 ACIDP Mode Change Return This message originated by the CG signals success or failure of a requested program mode change. Header information: Word 1—Transaction Code = 23 Word 2—Number of Words = 1 Word 5—CG Identifier = 3 Message format: Word 1—return status (integer) 0=normal return 1=ACP ACIDP mismatch 4=EXECSTAT incorrect 6=valid ACIDP not found Use information: PROGSTAT changes can only be made while the ACIDP's EXECSTAT value is set to OFF, DELAY, or ABORT. 4.4.
4.4.4 4.4.4 Get ACIDP Status Return This message from the CG returns all the parameter values for an ACIDP. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 25 Word 2—Number of Words = 1 (plus 67 if ACIDP found) Word 5—CG Identifier = 3 Message format: Word 1—return status (integer) 0=normal return 6=valid ACIDP not found Words 2..5—ACIDP name (8 ASCII characters) Words 6..17—PTDESC (24 ASCII characters) Word 18—UNIT (2 ASCII characters) Words 19..
4.4.4 Words 55..58—RTPERIOD (8 ASCII characters) Words 59..62—STIME (8 ASCII characters) Word 63—RUN_INIT (integer) 0=OFF, 1=ON Word 64—OPER_DMD (integer) 0=OFF, 1=ON Word 65—PPS (integer) 0=OFF, 1=ON Word 66—not used Word 67—CONF_RQD (integer) 0=OFF, 1=ON Word 68—TAKE_IP (integer) 0=OFF, 1=ON Use information: See the Computer Gateway Parameter Reference Dictionary for descriptions of these parameters, including the mechanisms for their setup and change.
4.4.4 Word 49—PROGSTAT (integer) 0=NOT INST 1=TEST 2=RESTRICT 3=NORMAL Words 50..51—ABORTCOD (4 ASCII characters) Word 52—MSG_INDX Word 53—CONF_IND Word 54—CONFWAIT (integer) Word 55—not used Words 56..64—NEXT_RTM (18 ASCII characters) Words 65..68—RTPERIOD (8 ASCI characters) Words 69..
4.4.5 4.4.5 Turn On ACP This is the only unsolicited application-level message from the CG during normal operation and is used to signal the need for a specified ACP to begin execution. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 2 Word 2—Number of Words = 9 Word 5—CG Identifier = 1 Word 6—Host Task Identifier = DI Message format: Words 1..
4.4.5 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 102 Word 2—Number of Words = 18 Word 5—CG Identifier = 1 Word 6—Host Task Identifier = DI Message format: Words 1..8—ACIDP name (16 ASCII characters) Words 9..
4.4.6 4.4.6 ACIDP Execution State Change Request This message, originated by the host processor, informs the CG of a change of an ACP's execution state. It does this by requesting a change of the ACP execution state as recorded in the parameter EXECSTAT of its associated ACIDP. The allowable operations are to change to RUN state or from RUN to ABORT or to OFF/DELAY.
4.4.6 Use information: The abort codes are visible at the Universal Station and can have any value assignments you wish. Presumably they will be coded to indicate the apparent reason for aborting the ACP/ACIDP. Abort code of 0000 (ASCII zeros) indicates a normal termination. The change to RUN state message is required after receipt by the host processor of a turn-on message. This confirms to the CG that the ACP has been activated.
4.4.7 4.4.7 Internal DDT Connect or Disconnect Request The host processor sends this request to initiate the connect or disconnect of a CG-resident Internal DDT (input values only) to a specified ACIDP that already has a connected ACP. It also is used to change "trigger" values for a previously connected DDT.
4.4.7 Use information: Precollection occurs only for the ON trigger or triggers. In order for the request to be accepted, there must be a correlation between the message data and what already exists in the CG database. The following table summarizes these relationships as they affect the request type.
4.4.8 4.4.8 Internal DDT Connect or Disconnect Return This message originated by the CG signals success or failure of a requested DDT connect, disconnect, or trigger values change. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 46 Word 2—Number of Words = 20 Word 5—CG Identifier = 3 Message format: Word 1—return status (integer) Use information: The values returned are those to be found in the CG database after the command is serviced.
4.4.8 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 146 Word 2—Number of Words = 29 Word 5—CG Identifier = 3 Message format: Word 1—return status (integer) Use information: The values returned are those to be found in the CG database after the command is serviced. Even if the request is invalid, the CG returns whatever data exists for that ACIDP.
4.5 4.5 INTERNAL DDT PREPARATION MESSAGES The messages in this section are a necessary precursor of any table-driven get and store requests. They are concerned with the establishment and saving of point-identifier tables required by the table-driven request messages. 4.5.1 Build Internal DDT Request The host processor sends this request to initiate the external-to-internal identifier conversions for a specified table of point.parameters.
4.5.1 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 106 Word 2—Number of Words = 9 + total for external name/parameter sets (21 words each) Word 5—CG Identifier = 2 Message format: Word 1—start of external data table Data table format: Word 1—table purpose (integer) 1=input table 2=output table 5=history query table Words 2..
4.5.1 Use information: "Point name index" must = 0 "Parameter name index" is used to identify a specific parameter array element. When used with nonarray parameters, this field must = 0. The order and number of points for each data type is significant (to the CG for processing of Store Data messages and to the ACP for the processing of Get Data Return messages) because the number of data words for each point varies with data type.
4.5.2 4.5.2 Build Internal DDT Return The CG sends this response, which includes data corresponding to the build Internal DDT request.
4.5.2 Name/parameter set format–point error Word 1—255 (integer) Words 2..3—not used Word 4—error code (integer) 1=Point name error (entity name error) 2=Duplicate point name (duplicate entity error) 3=Incomplete search 4=Subscript out of range 5=Point does not have subscript 6=Parameter name error 7=Invalid parameter for point name type 8=Enumeration fetch error 9=Point is not Boolean or Enumeration Words 5..
4.5.3 4.5.3 Store Internal DDT in CG Request This message from the host processor sends a copy of a Internal DDT for the CG to use in Data Table-driven Get Data requests. Header information: Word 1—Transaction Code = 10 Word 2—Number of Words = 5 plus size of data table Word 5—CG Identifier = 3 Message format: Words 1..5—table identifier (9 ASCII characters) Word 6—start of data table, see paragraph 4.5.2 for format Use information: CG-resident Internal DDTs cannot be used by Store Data or Get History.
4.6 4.6 POINT-DATA TRANSFERS USING DATA TABLES The following group of data-transfer messages require the use of previously built and converted Internal Data Tables (Internal DDT). See paragraph 4.5 for descriptions of the messages used in Internal DDT preparation, and for table format and content. 4.6.1 Get Data Request (Internal DDT in CG) This message from the host processor is used when a copy of the Internal DDT is kept by the CG (see paragraph 4.5.3).
4.6.2 4.6.2 Get Data Request (Internal DDT in Host Processor) This message from the host processor is used when no copy of the Internal DDT is kept by the CG, and the Internal DDT becomes part of the request message. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 4 Word 2—Number of Words = 5 plus size of the Internal DDT Word 5—CG Identifier = 2 Message format: Words 1..
4.6.3 4.6.3 Get Data Return This message from the CG is in response to either type of Get Data request (message types 3 and 4). The data returned includes both values and value status. The number of words returned for each point varies by data type (3 for Reals, 2 for Integers, 13 for ASCII strings, and 5 for Enumerations). Eight-Character Tagname Form Header information: Word 1—Transaction Code = 7 Word 2—Number of Words = 5 plus size of data Word 5—CG Identifier = 2 Message format: Words 1..
4.6.3 Internal Entity ID Words 1..4—value (internal format) Word 5—value status (integer) External Entity ID Words 1..8—name (up to 16 ASCII char.) Word 9—LCN id (2 characters; blank=local) Word 10—value status (integer) LCN Internal Time Words 1..2—seconds since 1 January 1979 (32-bit integer) Word 3—tenths of ms in current second (integer) Word 4—value status (integer) ASCII String (40 characters) Use information: Words 1..
4.6.3 Parameter value formats: Real Words 1 and 2—value (real) Word 3—value status (integer) Integer Word 1—value (integer) Word 2—value status (integer) ASCII String (24 characters) Words 1..12—value (ASCII characters) Word 13—value status (integer) Enumeration Words 1..4—value (ASCII characters) Word 5—value status (integer) Ordinal Value of Enumeration Word 1—value (integer) Word 2—value status (integer) Internal Entity ID Words 1..
4.6.4 4.6.4 Store Data Request This message from the host processor is used to store values to locations in the CG and other LCN devices. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 5 Word 2—Number of Words = 5 plus size of data Word 5—CG Identifier = 2 Message format: Words 1..4—ACIDP name (8 ASCII characters) Word 5—data access priority (integer) l=control 2=noncontrol Word 6—start of Internal DDT table (see paragraph 4.
4.6.4 Use information: The number of point/parameters is limited to a total of 300 or less. See heading 4.1.5. The Internal DDT used by this request must be previously created (messages 6 and 9) with no errors reported. Because of the possibility for errors in point and parameter definition, caution in use of this message type is advised. One suggested technique is to read and check the data values before attempting to change them. The store status controls what—if any—value is to be stored.
4.6.4 ASCII Words 1..12—value (ASCII characters) Word 13—store status (integer) Enumeration Words 1..4—value (enumeration) Word 5—store status (integer) Ordinal Value of Enumeration Word 1—value (integer) Word 2—store status (integer) Internal Entity ID Words 1..4—value (internal format) Word 5—value status (integer) LCN Internal Time Words 1..
4.6.5 4.6.5 Store Data Return This message from the CG is in response to a store data request. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 8 Word 2—Number of Words = 5 plus size of tables Word 5—CG Identifier = 2 Message format: Words 1..
4.6.5 Eight-Character Tagname Form Header information: Word 1—Transaction Code = 108 Word 2—Number of Words = 14 plus size of tables Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name (16 ASCII characters) Words 9..
4.7 4.7 SINGLE-POINT DATA TRANSFERS Single-point data transfers are used to get or store a value for a single parameter, for a selected parameter within a parameter array, or for all elements of a parameter array. (Parameter arrays are used with Custom Data Segments.) Two methods are provided for single parameter gets and stores.
4.7.2 4.7.2 Get Single Point Request (External Identifier) This request from the host processor is used to fetch a single value (or an array of values) for a point and parameter specified in the ACP's calling sequence, using the external identifier. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 28 Word 2—Number of Words = 16 Word 5—CG Identifier = 2 Message format: Words 1..
4.7.3 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 128 Word 2—Number of Words = 31 Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name or blank (16 ASCII characters) Word 9—data access priority (integer) 1=control 2=noncontrol Word 10—data type (integer) 1=real 2=integer 3=ASCII (24 character string) 4=enumeration/boolean 5=enumeration ordinal value 6=LCN external time (see 4.7.
4.7.4 4.7.4 Get Single Point Return (External Identifier) This message from the CG is the response to a Get Single Point request (external identifier). The data returned includes both value and value status. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 29 Word 2—Number of Words = 6 plus size of data record Word 5—CG Identifier = 2 Message format: Words 1..
4.7.4 Word 6—data type (integer) 1=real 2=integer 3=ASCII (24-character string) 4=enumeration/Boolean 5=enumeration ordinal value 6=LCN external time (see 4.7.3) 7=real array 8=integer array 9=enumeration array 10=enum ordinal values array 13=internal entity id 14=internal entity id array 15=external entity id (ASCII name) 16=external entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII (40-char.
4.7.4 Ordinal Array Word 1—array value status (integer) Word 2—array element 1 (integer) Word 3—array element 2 (integer) etc. Internal Entity ID Words 1..4—value (internal format) Word 5—value status (integer) Internal Entity ID Array Word 1—value status (integer) Words 2..5—array element 1 Words 6..9—array element 2 etc. External Entity ID Words 1..
4.7.4 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 129 Word 2—Number of Words = 15 plus size of data record Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name or blank (16 ASCII characters) Word 9..
4.7.4 Word 15—data type (integer) 1=real 2=integer 3=ASCII (24-character string) 4=enumeration/Boolean 5=enumeration ordinal value 6=LCN external time (see 4.7.3) 7=real array 8=integer array 9=enumeration array 10=enum ordinal values array 13=internal entity id 14=internal entity id array 15=external entity id (ASCII name) 16=external entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII (40-char.
4.7.4 Ordinal Array Word 1—array value status (integer) Word 2—array element 1 (integer) Word 3—array element 2 (integer) etc. Internal Entity ID Words 1..4—value (internal format) Word 5—value status (integer) Internal Entity ID Array Word 1—value status (integer) Words 2..5—array element 1 Words 6..9—array element 2 etc. External Entity ID Words 1..
4.7.5 4.7.5 Store Single Point Request (External Identifier) This request from the host processor stores single value (or an array of values) for a point and parameter specified in the ACP's calling sequence, using the external identifier. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 35 Word 2—Number of Words = 16 plus data record size Word 5—CG Identifier = 2 Message format: Words 1..
4.7.5 Real Array Word 1—array store status (integer) Words 2..3—array element 1 (real) Words 4..5—array element 2 (real) etc. Integer Array Word 1—0 (integer) Word 2—array element 1 (integer) Word 3—array element 2 (integer) etc. Enum Array Word 1—0 (integer) Words 2..5—array element 1 (ASCII characters) Words 6..9—array element 2 (ASCII characters) etc. Ordinal Array Word 1—0 (integer) Word 2—array element 1 (integer) Word 3—array element 2 (integer) etc. Internal Entity ID Words 1..
4.7.5 Use information: Store status (applies only to reals and ASCII) 0=store the data value(s) provided 1=store the bad value representation instead When data type is an array, the store status applies to the whole array. The bad value representations are NaN for real values and question mark strings for ASCII. Content of the field "parameter array pointer/size" depends on data-type specification. See paragraph 4.7.1 for an explanation of this field's use with single parameters and with parameter arrays.
4.7.5 Data Record formats: Real Words 1 and 2—value (real) Word 3—store status (integer) Integer Word 1—value (integer) Word 2—0 (integer) ASCII String (24 characters) Words 1..12—value (ASCII characters) Word 13—store status (integer) Enumeration Words 1..4—value (ASCII characters) Word 5—0 (integer) Ordinal Word 1—ordinal value of enumeration (integer) Word 2—0 (integer) Real Array Word 1—array store status (integer) Words 2..3—array element 1 (real) Words 4..5—array element 2 (real) etc.
4.7.5 LCN Internal Time Word 1—value status (integer) Array Words 2..4—array element 1 Words 5..7—array element 2 etc. Use information: ASCII String (40 characters) Words 1..20—value (ASCII characters) Word 21—value status (integer) ASCII String (40 characters) Array Word 1—value status (integer) Words 2..21—array element 1 Words 22..41—array element 2 etc.
4.7.6 4.7.6 Store Single Point Return (External Identifier) This message from the CG is the response to a Store Single Point request (external identifier). The data returned is value status only. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 36 Word 2—Number of Words = 7 Word 5—CG Identifier = 2 Message format: Words 1..
4.7.6 Word 6—data type (integer) 1=real 2=integer 3=ASCII (24-character string) 4=enumeration/Boolean 5=enumeration ordinal value 7=real array 8=integer array 9=enumeration array 10=enum ordinal values array 13=internal entity id 14=internal entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII array (40-char. string) Word 7—value status (integer), see “Data Access Status Codes” in the Messages Directory.
4.7.6 NOTE Return Status code 11 indicates a warning. Useful information (correct data type code) has been returned. Return Status code 5 indicates that the value status contains a non-normal data access status code.
4.7.7 4.7.7 Convert Identifier Request This message from the host processor requests the conversion of a point/parameter name from external form (ASCII characters) to internal form. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 41 Word 2—Number of Words = 16 Word 5—CG Identifier = 2 Message format: Words 1..
4.7.7 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 141 Word 2—Number of Words = 31 Word 5—CG Identifier = 2 Message format: Words 1..
4.7.8 4.7.8 Convert Identifier Return This message from the CG is the response to a Convert Identifier request. The information returned is obtained by a search of LCN nodes. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 42 Word 2—Number of Words = 13 Word 5—CG Identifier = 2 Message format: Words 1..
4.7.8 Word 6—data type (integer) 1=real 2=integer 3=ASCII (24-character string) 4=enumeration/Boolean 5=enumeration ordinal value 7=real array 8=integer array 9=enumeration array 10=ordinal values array 13=internal entity id 14=internal entity id array 15=external entity id (ASCII name) 16=external entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII (40-char. string) array Words 7..
4.7.8 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 142 Word 2—Number of Words = 22 Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name or blank (16 ASCII characters) Words 9..
4.7.8 Word 15—data type (integer) 1=real 2=integer 3=ASCII (24-character string) 4=enumeration/Boolean 5=enumeration ordinal value 7=real array 8=integer array 9=enumeration array 10=ordinal values array 13=internal entity id 14=internal entity id array 15=external entity id (ASCII name) 16=external entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII (40-char. string) array Words 16..
4.7.9 4.7.9 Get Single Point Request (Internal Address) This request from the host processor is used to fetch a single value (or an array of values) for a point and parameter specified in the ACP's calling sequence, using the internal address. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 39 Word 2—Number of Words = 13 Word 5—CG Identifier = 2 Message format: Words 1..
4.7.9 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 139 Word 2—Number of Words = 22 Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name or blank (16 ASCII characters) Words 9..
4.7.10 4.7.10 Get Single Point Return (Internal Address) This message from the CG is the response to a Get Single Point request (internal address). The data returned includes both value and value status. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 40 Word 2—Number of Words = 6 plus size of data record Word 5—CG Identifier = 2 Message format: Words 1..
4.7.10 13=internal entity id 14=internal entity id array 15=external entity id (ASCII name) 16=external entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII array (40-char string) Word 7—start of data record Data record formats: Real Words 1 and 2—value (real) Word 3—value status (integer) Integer Word 1—value (integer) Word 2—value status (integer) ASCII String Words 1..
4.7.10 External Entity ID Words 1..8—name (up to 16 ASCII char) Word 9—LCN id (2 characters; blank=local) Word 10—value status (integer) External Entity ID Array Word 1—value status (integer) Words 2..10—array element 1 Words 11..19—array element 2 etc. LCN Internal Time Words 1..2—seconds since 1 January 1979 (32-bit integer) Word 3—tenths of ms in current second (integer) Word 4—value status (integer) LCN Internal Time Word 1—value status (integer) Array Words 2..4—array element 1 Words 5..
4.7.10 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 140 Word 2—Number of Words = 15 plus size of data record Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name or blank (16 ASCII characters) Words 9..
4.7.10 16=external entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII array (40-char. string) Word 16—start of data record Data record formats: Real Words 1 and 2—value (real) Word 3—value status (integer) Integer Word 1—value (integer) Word 2—value status (integer) ASCII String Words 1..12—value (ASCII characters) (24 characters) Word 13—value status (integer) Enumeration Words 1..
4.7.10 External Entity ID Array Word 1—value status (integer) Words 2..10—array element 1 Words 11..19—array element 2 etc. LCN Internal Time Words 1..2—seconds since 1 January 1979 (32-bit integer) Word 3—tenths of ms in current second (integer) Word 4—value status (integer) LCN Internal Time Word 1—value status (integer) Array Words 2..4—array element 1 Words 5..7—array element 2 etc. Use information: ASCII String (40 characters) Words 1..
4.7.11 4.7.11 Store Single Point Request (Internal Address) This request from the host processor stores a single value (or an array of values) for a specified point and parameter using its internal identification (address). Eight-Character Tagname Form Header information: Word 1—Transaction Code = 37 Word 2—Number of Words = 13 plus size of data record Word 5—CG Identifier = 2 Message format: Words 1..
4.7.11 Ordinal Word 1—ordinal value of enumeration (integer) Word 2—0 (integer) Real Array Word 1—array store status (integer) Words 2..3—array element 1 (real) Words 4..5—array element 2 (real) etc. Integer Array Word 1—0 (integer) Word 2—array element 1 (integer) Word 3—array element 2 (integer) etc. Enum Array Word 1—0 (integer) Words 2..5—array element 1 (ASCII characters) Words 6..9—array element 2 (ASCII characters) etc.
4.7.11 Use information: Store status (applies only to reals and ASCII) 0=store the data value(s) provided 1=store the bad value representation instead When data type is an array, the store status applies to the whole array. The bad value representations are NaN for real values and question mark strings for ASCII. This message can be used by one ACP to turn on another ACP by setting the other's PPS parameter to ON.
4.7.11 Data record formats: Real Words 1 and 2—value (real) Word 3—store status (integer) Integer Word 1—value (integer) Word 2—0 (integer) ASCII String (24 characters) Words 1..12—value (ASCII characters) Word 13—store status (integer) Enumeration Words 1..4—value (ASCII characters) Word 5—0 (integer) Ordinal Word 1—ordinal value of enumeration (integer) Word 2—0 (integer) Real Array Word 1—array store status (integer) Words 2..3—array element 1 (real) Words 4..5—array element 2 (real) etc.
4.7.11 LCN Internal Time Word 1—value status (integer) Array Words 2..4—array element 1 Words 5..7—array element 2 etc. Use information: ASCII String (40 characters) Words 1..20—value (ASCII characters) Word 21—value status (integer) ASCII String (40 characters) Array Word 1—value status (integer) Words 2..21—array element 1 Words 22..41—array element 2 etc.
4.7.12 4.7.12 Store Single Point Return (Internal Address) This message from the CG is the response to a Store Single Point request (internal address). The data returned is value status only. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 38 Word 2—Number of Words = 7 Word 5—CG Identifier = 2 Message format: Words 1..
4.7.12 13=internal entity id 14=internal entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII (40-char. string) array Word 7—value status (integer), see “Data Access Status Codes” in the Messages Directory. Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 138 Word 2—Number of Words = 16 Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name (16 ASCII characters) Words 9..
4.7.12 Word 15—data type (integer) 1=real 2=integer 3=ASCII (24-character string) 4=enumeration/Boolean 5=enumeration ordinal value 7=real array 8=integer array 9=enumeration array 10=ordinal values array 13=internal entity id 14=internal entity id array 17=LCN internal time 18=LCN internal time array 19=ASCII (40-character string) 20=ASCII (40-char. string) array Word 16—value status (integer), see “Data Access Status Codes” in the Messages Directory.
4.8 4.8 HISTORY DATA TRANSFERS History data requests are limited to the data types that can be historized. These are primarily analog points with parameters that are expressed as real values; however, history snapshots can include digital points that are expressed as integer (ordinal) values. Up-to-four concurrent History requests (from separate ACPs) can be accepted by the CG. A fifth request will be rejected with a queue-full return status. 4.8.
4.8.1 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 150 Word 2—Number of Words = 39 plus size of the Internal DDT table Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name or blank (16 ASCII characters) Words 9..
4.8.1 Relative requests—Beginning and ending offset times apply to only relative history requests. They are stated in the units of the specified history type and are used to establish start time, search direction, and the number of samples to be collected from the HM.
4.8.1 The following table summarizes results of some possible combinations of starting and ending offsets with numbers of samples returned and reasons for zero-sample returns.
4.8.2 4.8.2 Get History Return This message is sent by the CG in response to a request for transmission of history data stored at the HM. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 51 Word 2—Number of Words = 5 plus size of the data table Word 5—CG Identifier = 2 Message format: Words 1..
4.8.2 Sixteen-Character Tagname Form Header information: Word 1—Transaction Code = 151 Word 2—Number of Words = 14 plus size of the data table Word 5—CG Identifier = 2 Message format: Words 1..8—ACIDP name or blank (16 ASCII characters) Words 9..
4.8.2 Form 2 Word 1 Word 2 Word 3 Words 4..5 =2 (integer)—digital process data value ordinal value of a self-defined enumeration (integer) not used (real, initialized to IEEE NaN) timestamp (unsigned 32-bit integer) Form 3 Word 1 Words 2..3 Words 4..
4.8.2 For Fast Interval Monthly Averages (history type = 7) derived from 5-, 10-, or 20-second snapshots, each subrecord is 11 words long. Form 1 Word 1 =0 (integer)—normal data, or =1 (integer)—nonstandard, or =5 (integer)—time change, or =13 (integer)—time change nonstandard Words 2..3 process value (real) Words 4..5 timestamp (unsigned 32-bit integer) Words 6..7 maximum process value* in period (real) Words 8..9 minimum process value* in period (real) Word 10..
4.8.2 When snapshot data (history type 0, 9, 10, or 11) is requested, all the data returned is controlled by the time interval specified in the request (60-, 5-, 10, or 20-second intervals, respectively).
4.8.2 4.8.2.2 Value-Type Meanings for Averages Averages are of analog data and are the total of the summed good averages for the period divided by the number of good samples. 0 1 2 = Normal: 90% or more good samples = Nonstandard: Less than 90% good samples = Digital Value: not applicable (if an average is requested for a parameter of type digital, the value type returned is "data not in history").
4.8.2 As shown by Figure 4-1, the remainder of the history record for the minute when the time change occurred is filled with "no data" indicators in order for the four different collection rates to stay in alignment. Note that the slower collection intervals fill with "fast collect not configured" indicators on each 5-second interval when they are not collecting data. (In the illustration, "dnc " represents a "data not collected" record, and "fcnc" indicates a "fast collection not configured" record.
4.9 4.9 TEXT MESSAGE TRANSFERS 4.9.1 Get Message Request This message is used by the host processor to request the fetching of a message placed in an ACIDP by a CL/MC sequence program in a Multifunction Controller or by a CL/PM sequence program in a Process Manager Module. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 13 Word 2—Number of Words = 4 Word 5—CG Identifier = 3 Message format: Words 1..
4.9.3 4.9.3 Send Message Request This message is used by the host processor to request the sending of a message to the operator personality in all Universal Stations monitoring the Area containing the Unit to which the ACIDP is assigned by point configuration. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 15 Word 2—Number of Words = 7 plus message size Word 5—CG Identifier = 3 Message format: Words 1..
4.9.4 Message-length maximums are dependent on destination: 60 characters for CRT messages, 72 characters for printing, and HM journaling (all messages to the operator are journaled if the History Module is so configured). Oversize messages are truncated. Two types of Event Initiated reports can be invoked by specially formatted messages from an ACP to the Area Universal Station.
4.9.5 4.9.5 Message Confirmation or Timeout This message is sent by the CG as the final response to a send message requiring operator response. It indicates either operator action or timeout. Eight-Character Tagname Form Header information: Word 1—Transaction Code = 1 Word 2—Number of Words = 10 Word 5—CG Identifier = 1 Message format: Words 1..
4.10 4.10 FILE TRANSFERS 4.10.1 Introduction to File Transfers The following paragraphs explain the format and content of the file transfer requests that a host processor can make to an HM on the local LCN. Some of these file requests also can be made across the Network Gateway to an HM on a remote LCN. The host initiates all file transfer operations and can also request abort of any operation. For each file transfer request from the host there is a paired response from the CG.
4.10.1 4.10.1.3 Status Codes Returned by File Transactions The message block of each File Transfer response contains two words of status data. • Word 11 of the message block contains the code specifying the overall return status (0 = normal). See heading 4.10.17.1 for details. • Word 12 of the message block contains a substatus code that is significant only when word one contains the value 1 (see heading 4.10.17.2) or the value 14 (see heading 4.10.17.3).
4.10.1 4.10.1.5 Use of EP Utilities Options Several of the File Transfer transactions make use of one or more command options associated with the Engineering Personality Utilities. These options are invoked by adding "-" followed by the option name to the filename. More than one option can be included and each is separated by a space. For example a filename showing three of the available EP options would have this form: NET>vdir>*.
4.10.2 4.10.2 Read LCN File This request/response pair reads a single file and its attributes from a volume on an HM to the host. Contiguous or linked files can be transferred. Record size is affected by file type. • Contiguous files have a fixed record size of 256 bytes. • Linked files can have either a fixed or a variable record size. - The record size common to all records of a fixed-length linked file is returned in word 34 of the response message.
4.10.2 Word 29—Ending record requested (Words 28 and 29 are not used when Word 27 = 0) Words 30—User supplied time-out in seconds. The valid values are 1 to 1800. A value outside this range sets a default of 60. Words 31..40—Reserved for response data 4.10.2.2 Read LCN File Response Header information: Word 1—Transaction Code = 63 Word 2—Number of Words = 40 + data size Word 5—CG Identifier = 2 Message format: Words 1..
4.10.3 A temporary file with a unique name is created to receive the data on the requested volume. After the transmission is complete, the temporary file is Safe Renamed to the requested LCN pathname. If the contents of an existing file are over written or data are appended to the file, the resulting file attributes of the file are those specified in the message block of the request. 4.10.3.
4.10.4 Word 39—File Revision* Word 40—Write access code* (0 = unprotected) Data information: Words 1..32—File descriptor* (ASCII characters) Words 33..5792—File data 4.10.3.2 Write LCN File Response Header information: Word 1—Transaction Code = 63 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..10—Request echo Word 11—Return status 0 = normal Word 12—Return substatus 0 = normal Words 13..32—Request echo Word 33—Request transmission counter +1 Word 34..40—Request echo 4.
4.10.5 Message format: Words 1..10—Request echo Word 11—Return status (0 = normal) Word 12—Return substatus (0 = normal) Words 13..26—Request echo Word 27—Write access code (0 = unprotected) Word 28—File Type (0 = contiguous, 1 = linked) Word 29—File record size for fixed length linked files only (otherwise = 0) Words 30..31—EOF Number of blocks Word 32—File block size for linked files only (otherwise = 0) Words 33..34—Directory time stamp (seconds since 1/01/79 00:00) Word 35—File configuration (0..
4.10.5 4.10.5.1 List Catalog into a File Request Header information: Word 1—Transaction Code = 62 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..8—Reserved for future use Word 9—Command type = 4 Word 10—Not used Word 11..12—Reserved for response data Words 13..90—LCN pathname for the device/volume/file and command options to catalog (ASCII characters) (PN:nn>vdir>*.* -rec -fd or NET>vdir>*.
4.10.5 Option Description –BF* Display limited attribute information. –D* List detailed information about a volume and its directories. –A List all files and directories in the volume. –FD* List file descriptor with files. –REC* Used with –FD. List record information and file descriptor. When –FD option is used without –REC, the file descriptor is displayed instead of the record information. The –REC option causes this information to be displayed when –FD is used.
4.10.6 4.10.6 Retrieve Volumes/Directories for a Device This request/response pair is used to fetch the volume names, directory names, and sector usage associated with the volumes of a specified HM. No wild card characters or options are applicable with this command. 4.10.6.1 Retrieve Volumes/Directories for a Device Request Header information: Word 1—Transaction Code = 62 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..
4.10.7 Data information: Word 1—Total number of directories in volume 1 Words 2..3—Total number of sectors (32-bit integer) Words 4..5—Sectors in use (32-bit integer) Words 6..7—Reserved for future use Words 8..9—Volume Id for volume 1 (4 ASCII characters) Words 10..11—Directory Id 1 for volume 1 (4 ASCII characters) Words 12..135—Directory Ids 2..63 for Volume 1 Words 136..4050—Volume and Directory Ids for Volumes 2..30 4.10.
4.10.8 4.10.8 Copy File This request/response pair is used to copy an HM file and place the copy in a destination file on an HM. Wild card characters are permitted. The destination suffix must always be the same as the source suffix. The -D option outputs to the Data Out file if specified in the destination path. 4.10.8.1 Copy File Request Header information: Word 1—Transaction Code = 62 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..
4.10.10 Message format: Words 1..8—Reserved for future use Word 9—Command type = 8 Word 10—Not used Word 11—Reserved for response data Word 12—Reserved for response data Words 13..26—LCN pathname for the HM source file (NET>dir1>filename.xx) Words 27..40—LCN pathname for the HM destination directory (dir2 -D) 4.10.9.2 Move File Response Header information: Word 1—Transaction Code = 63 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..
4.10.11 Message format: Words 1..10—Request echo Word 11—Return status (0 = normal) Word 12—Return substatus (0 = normal) Words 13..40—Request echo 4.10.11 Create Directory This request/response pair is used to create a directory under a user-defined volume on the HM (user volume names must begin with a character other than ! or &). Each directory can have one or more files assigned to it. A volume can have up to 63 directories. No wild card characters or options are applicable with this request. 4.10.11.
4.10.12 4.10.12 Delete Directory This request/response pair is used to delete a directory from a user-defined volume on the HM (user volume names must begin with a character other than ! or &). A directory that still contains files cannot be deleted. No wild card characters or options are applicable. 4.10.12.1 Delete Directory Request Header information: Word 1—Transaction Code = 62 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..
4.10.13 4.10.13 Delete Files This request/response pair is used to delete one or more files from a user-defined volume on the HM (user volume names must begin with a character other than ! or &). A deleted file cannot be recovered. Wild card characters can be used to allow selective and multiple file deletions. The -D option lists the files deleted in the Data Out file if specified. 4.10.13.
4.10.14 4.10.14.2 Break Response Header information: Word 1—Transaction Code = 63 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..10—Request echo Word 11—Return status (0 = normal) Word 12—Return substatus (0 = normal) Words 13..40—Request echo 4.10.15 Data Out Request This request/response pair is used to turn on (assign) or turn off (de-assign) the Data Out file function or to request its on/off status.
4.10.15 4.10.15.2 Data Out Response Header information: Word 1—Transaction Code = 63 Word 2—Number of Words = 40 Word 5—CG Identifier = 2 Message format: Words 1..10—Request echo Word 11—Return status (0 = normal) Word 12—Return substatus (0 = Data Out OFF, 1 = Data Out ON) Words 13..26—Request echo Words 27..40—Data Out file's pathname (NET>vdir>filename.yy) returned when the subcommand value = 1 or 2 4.10.
4.10.16 4.10.16.2 Retrieve File Names and Extensions Response Header information: Word 1—Transaction Code = 63 Word 2—Number of Words = 40 + 5900 Word 5—CG Identifier = 2 Message format: Words 1..10—Request echo Word 11—Return status (0 = normal) Word 12—Return substatus (0 = normal, 1 = 1180 names limit has been reached and not all names could be returned) Words 13..26—Request echo Word 27—Number of file names returned Words 28..40—Not used Data information: Words 1..
4.10.17 4.10.17 File Transfer Response Status Codes The following information defines the various major and sub-status response status codes that can be returned by the CG to the various file requests in words 11 and 12 of the response message. 4.10.17.
4.10.
4.10.
4.10.
4.11 4.11 CM JOURNAL ACCESS 4.11.1 Introduction to CM Journal Access The Purpose of the CM Journal Access is to allow a request from a CM50 function to pass and convert LCN Real-Time HM journals into ASCII files for a host processor. The journal requests are passed to the CG/PLNM through a unique transaction code of 64. Only one journal access request per CG/PLNM is allowed. Concurrent requests will not be queued.
4.11 4.11.3.1 CM Journal Access Request Message Record Header information: Word 1—Transaction Code = 64 (CM50 request) Word 2—Number of words in message = 340 Words 3..4—reserved Word 5—CG/PLNM Identifier = 2 Word 6—host task identifier (specified by CM 50) Words 7..8—reserved Message format: Words 1..
4.11 Event Request Rec: Word 274—Type of journal (integer) 0 = Process alarms 1 = Operator messages 2 = Process changes 3 = SOE events 4 = System status 5 = System maintenance 6 = System errors 7 = Status notification Word 275—Number of key values (integer) 1..8 = Number of modules, points, nodes, or boxes on which the search is to be performed Zero = Search all events (allow only system journal types 4,5,6,7) Word 276—Journal Key type (integer) 0 = Module 1 = Point 2 = Node 3 = Box Word 277..
4.11 4.11.4.1 CM Journal Access Return Message Record Header information: Word 1—Transaction Code = 65 (CM50 request) Word 2—Number of words in message = 5445 Words 3..4—reserved Word 5—CG/PLNM Identifier = 2 Word 6..13—reserved Message format: Words 1..8—ACIDP name - echoed back (16 ASCII characters) Word 9—Local LCN PIN node ID - echoed back (2 ASCII characters) Word 10—Unit ID - echoed back (2 ASCII characters) Word 11..15—Reserved for future use (fill with integer zeroes) Word 16..
4.
5 DATA LINK CHARACTERISTICS Section 5 This section summarizes the data link hardware, transaction management, and supported protocols (Bisynch and HDLC). See Appendix B for cabling and connector information. 5.1 INTRODUCTION Communication between the host processor and the CG is over a serial link, using either Binary Synchronous (Bisynch) or HDLC protocol. When Bisynch is used, either one or two half-duplex links can be used (one is recommended). When HDLC is used, one fullduplex link is supported.
5.3 The following message formats are supported: • • • • • • • • • Line Bid Sequence Single Block Text Transfer Multiple Block Text Transfer Wait Before Transmitting Positive Acknowledge Start Transparent Text (DLE STX) End Transparent Text (DLE ETX) End Transparent Text Block (DLE ETB) Synch/Fill (DLE SYN) Ignore DLE Pattern (DLE DLE) CAUTION Be sure that your CG is configured to correspond with the host data-link type (single/dual).
5.3.1 5.3.1 Single-Link Bisynch Sequences Most CG applications are expected to use single-link communications. Each single-link transaction starts with the line-bid sequence and ends with release of the line. The CG conflict timeout has been set to 0.75 second to reduce delays. If possible, the host computer timeout should be set similarly (for CM60 applications, the DPS6 timeout is set at one second). The CG is assigned primary priority for contention resolution.
5.3.2 5.3.2 Dual-Link Bisynch Sequences Although a single-link connection to the host computer is recommended, there is an option for a dual Bisynch-link connection. The advantage of dual links is improved throughput rates. The disadvantage is the need for more complex host-computer software necessary to react to the CG on startup and in failure recovery conditions and the maintenance of send and receive maintenance counters. In a dual-link configuration, the CG checks the Message Counter of each message.
5.4 5.4 HDLC LINK PROTOCOL Operation of the HDLC link follows the Link Access Procedure, Balanced (LAPB), according to C.C.I.T.T. document AP VIII-58-E June 1984 (Recommendation X.25) and complies with FIPS 100 certification. To provide a compatible HDLC interface with the CG, host processor software must meet the following requirements: • Link protocol is HDLC LAPB. • Station identifier is configurable as either 1 or 3; default is 1. • Maximum message size is 1024 bytes.
5.6 5.6 HOST PROCESSOR STATE DIAGRAM The types of messages that should be expected from, or are accepted by, the CG vary as processing states of the host-processor change. Figure 5-1 summarizes the expected reaction to various CG messages depending upon host-processor processing state. Those processing states are defined as follows: INIT Hardware-level communication has been established; waiting for Restore Message from CG. Will also receive Time Synch messages in this and all other states.
Figure 5-1 — Host Processor Processing States Computer Gateway User Manual 5-7 Not Not appropriate appropriate (NOTE 4) (Note 4) Send next data Not appropriate message (Note 5b) (NOTE 5a) goto RESTORE 1 Negative Confirm (30) Received Data messages to CIU stacked at Host Processor Link Fail (32) Message Received (Note 6) goto INIT 0 Not Not appropriate appropriate (NOTE 3) (Note 3) Positive Confirm (30) Received goto INIT 0 Send CNFPOS OR Send CNFNEG Send CNFPOS OR Send CNFNEG Not appropriate (NOTE
5.6.1 5.6.1 Explanatory Notes to Figure 5-1 Note 1 RESTORE message is expected only while host processor is in INIT state. Receipt of this message, at any other time, indicates violation of the 3-minute time limit between dispatch of a RESTORE and receipt of a RESTORE COMPLETE, by the CG. Note 2 Data messages occur only in response to requests from the host processor and cannot occur in this state.
5.6.2 5.6.2 Analysis of Data Link Messages Figure 5-2 is a re-creation of a series of single-link messages between a CG and a host processor recorded by a data analyzer at the beginning of a startup sequence. The transmissions are shown in the order they occurred, with the host-processor transmissions shown underlined.
5.6.2 16) ENQ from the host to bid for the line. 17) ACK0 response from the CG. 18) Confirmation Message (Transmission Code 30 decimal) from the host to indicate successful receipt of the Restore Message. 19) ACK1 response from the CG.
5.6.2 1) 3 3 3 3 3 3 2 F 2 2 2 2 2 2 D F 2) 3 3 3 3 3 1 7 F 2 2 2 2 2 0 0 F 3) 3 3 3 3 3 3 1 0 0 1 0 0 0 0 0 0 0 0 5 4 . . . . . . . 1 0 8 3 F 2 2 2 2 2 2 0 2 0 F 0 B 0 1 0 1 0 1 5 E 0 3 3 C F 4) 3 3 3 3 3 1 6 F 2 2 2 2 2 0 1 F 5) 3 3 3 3 3 3 3 F 2 2 2 2 2 2 7 F 6) 3 3 3 3 3 3 2 F 2 2 2 2 2 2 D F 7) 3 3 3 3 3 1 7 F 2 2 2 2 2 0 0 F 8) 3 3 3 3 3 3 1 0 0 1 0 0 0 0 0 0 0 0 5 4 . . . . . . .
5.6.
5.6.
5.7 5.7 SYSTEM ERROR JOURNAL REPORTS Reports are issued by the CG to the LCN System Error Journal in the event of certain data link communications errors. Each error type is assigned both a primary and secondary code for identification as follows.
6 CG DATABASE CONTENT Section 6 This section covers the content and use of information in the CG database. 6.1 INTRODUCTION The three user-specified components of the CG database are Advanced Control Interface Data Points (ACIDP) with their associated Custom Data Segments, the Calculated Results Data Points (CRDP), and the Internal Data Tables (internal DDT). Creation of the Internal Data Tables is explained in paragraph 4.5, while ACIDP and CRDP preparation are explained in Appendix E.
6.2.2 You can copy the schematic to an existing volume that is already listed in a Pathname Catalog, or you can add its pathname to a Pathname Catalog and then do an Area Change at a US to make it available. Detailed instructions for adding a schematic to a Pathname Catalog are under subsection 29.2 in the Engineer's Reference Manual, in the Implementation/Startup and Reconfiguration - 2 binder. 6.2.
6.3 6.3 VIEWING AND CHANGING ACIDP AND CRDP POINTS 6.3.1 Viewing and Changing Parameter Values From the Universal Station The current values of certain ACIDP and CRDP parameters can be viewed—and some scheduling-related parameters can be changed—from the area Universal Station in the Operator Personality, through the Group and Detail displays of these points. You can also create custom Universal Station displays with similar capabilities (see the Picture Editor Reference Manual for details).
6.3.
6.4 6.4 ACIDP/CRDP PARAMETER DESCRIPTIONS The following are brief descriptions of the ACIDP and CRDP parameters that are visible through a Universal Station's standard displays. For details of all CG parameters, see the Computer Gateway Parameter Reference Dictionary. ABORTCOD—Four ASCII characters indicating the reason for termination of ACP execution by the host processor. The value 0000 (zeros) is used to designate a normal ACP termination. Other value assignments are defined by the host processor.
6.5 RTPERIOD—The time period between runs of a scheduled ACP, in format HH:MM:SS. Minimum period is 10 seconds; maximum period is 24 hours. Not used if ACT_TYPE is DEMAND only. RUN_INIT—When ON, tells the CG scheduler to turn on the ACP immediately after completing an initialization event (see note on this page). STIME—The first time of day that a periodic program runs, in format HH:MM:SS (eight ASCII characters). The maximum time is 24:00:00. Not used if ACT_TYPE is CYCLIC, CYC_DMD, or DEMAND.
A CG POINT PREPARATION Appendix A This appendix summarizes the requirements for preparation of specialized CG data points that regulate the execution of control programs and hold results of control calculations for exchange with other LCN nodes. A.1 CG POINT BUILDING OVERVIEW As explained in Section 2, there are two types of data points that reside in the CG, the Advanced Control Interface Data Point (ACIDP) and the Calculated Results Data Point (CRDP).
A.2.1 A.2.1 Custom Data Segment Heading The Custom Data Segment Heading consists of the word CUSTOM followed by three optional attribute assignments, which change the default values for Class, Access, and Build Visible for this CDS. Either the standard or heading-specified default values are overridden by any individual parameter attribute assignments. Always use the default value for Class when preparing a CDS to be used with an ACIDP or CRDP. A.2.
A.2.3 A.2.3 Custom Data Segment Example CUSTOM PARAMETER swdbd1: NUMBER "switch deadband value" TYPE number ACCESS engineer EU "psi" VALUE 0.5 BLD_VISIBLE PARAMETER swdbd2 EU "psi" VALUE 0.5 END CUSTOM Notice that the two parameters generated by this example will be identical in all but their names. There is no name associated with the CDS because it is identified by the name of the file into which it is compiled (only one CDS for each file). A.2.
A.3 Compiling a CDS does not set aside storage for the parameter values; it simply defines the parameters to the system. The next required step is to build a point that uses the CDS parameters. Once a data point is built, the parameters of the CDS are part of the data point and are undifferentiated from other parameters of the data point. At this point, you should back up the .SE and .SP files on &ASY and should also checkpoint the CG. A.
B HARDWARE INSTALLATION/CHECKOUT/SERVICE Appendix B This appendix contains hardware information useful in the installation, checkout, and service of the Host Processor-to-CG data link. B.1 CG INSTALLATION, SERVICE AND TESTING B.1.1 CG Installation General information on site planning for and installation of TDC 3000X LCN Nodes such as the CG is found in the LCN Site Planning Manual, the LCN System Installation Manual, and the LCN System Checkout Manual. B.1.
B.2.1 B.2.1 RS-449 CLI Adapter Board Connections Figure B-1 illustrates the Line 1 and Line 2 cable connections at the CG's RS-449 Communications Line adapter board (part number 80360230-001). ASSY. 80360230-001 REV.
B.2.2 B.2.2 RS-449 Standard (Modem Connection) Cable • • • • 15 meters, male-to-male connection Modem connected Both transmit and receive clocks are supplied by the modem RS-449 standard connector-pin assignment Function CG Side 1 19 2 20 3 21 4 22 5 23 6 24 7 25 8 26 9 27 10 28 11 29 12 30 13 31 14 32 15 33 16 34 17 35 18 36 37 Shield ground Signal ground/common return not used not used Line present (not RS-449 spec.
B.2.3 B.2.3 RS-449 Direct Connect Cable • 700 meters, male-to-male connection • Direct connect • Each data terminal (CG and host processor) supplies a transmit clock and a receive clock. Function Shield ground Signal ground/common return not used not used Line present (not RS-449 spec.
B.2.4 B.2.4 RS-449 Loopback Cable • Connects channels 0 to 3 and 2 to 1 for CLIF test 13 • Male-to-male connection Function Shield ground Signal ground/common return not used not used Line present (not RS-449 spec.
B.2.5 B.2.5 RS-449 Loopback Connector • Male connector • RS-449 standard connector pin assignments • Connects channels 0 to 1 and 2 to 3 for CLIF test 14 Function Shield ground Signal ground/common return not used not used Line present (not RS-449 spec.
B.2.6 B.2.6 RS-232C CLI Adapter Board Connections Figure B-6 illustrates the Line 1 and Line 2 cable connections at the CG's RS-232C Communications Line adapter board (part number 80360209-001). ASSY. 80360209-001 REV.
B.2.7 B.2.
B.2.8 B.2.8 RS-232C Direct Connect Cable (Type I) • 15 meters, male-to-male connection • Direct connect • Only one end (either CG or host processor) supplies the clock. If it is to supply the clock, the CG must be set in the direct connect mode. • RS-232C standard connector-pin assignment CAUTION Because the two cable ends are pinned differently, care should be taken to position the cable correctly.
B.2.9 B.2.9 RS-232C Direct Connect Cable (Type II) • • • • 15 meters, male-to-male connection Direct connect Each end supplies its own transmit clock and a receive clock.
B.2.10 B.2.10 RS-232C Loopback Cable • Male-to-male connection • Connects channels 0 to 3 and 2 to 1 for CLIF test 13 CAUTION Because the two cable ends are pinned differently, care should be taken to position the cable correctly.
B.2.11 B.2.
B.2.12 B.2.12 CG to CG Switch Cable The Group Number is the Cable Length in Meters 4,5 4,5 1 Computer Gateway 37 Pin Male Conn. Switch 37 Pin Male Conn. 3 3 X-End Y-End Signal Pin Number Pin Number Signal Shield 1 1 Shield Signal Ground 19 (Note 3) 19 Signal Ground Cable Present 3 21 3 21 Cable Present XMIT DataXMIT Data+ 4 22 4 22 XMIT DataXMIT Data+ Recv. DataRecv. Data+ 6 24 6 24 Recv. DataRecv. Data+ XMIT CLKXMIT CLK+ 5 23 5 23 XMIT CLKXMIT CLK+ Recv. CLK Recv.
B.2.12 B.2.12 CG to CG Switch Cable Item No. Part Number Description 1 51190868-110 Cable, 10 twist pair QTY=Length in meters 2 51190831-030 Wire #24 AWG 3 51190670-303 4 5 Group No. Group No. 001 010 Group No. ### 1 10 ### Length in meters AR AR AR 37 pin connector hood with screw retainers 2 2 2 51190670-204 37 pin connector plug 2 2 2 51190670-203 connector contact male pin 44 44 44 Note: 1.
B.2.13 B.2.13 VAX Cable to CG Switch The Group Number is the Cable Length in Meters 4,5 1 6,7 Switch 37 Pin Male Conn. DEC VAX 37 Pin Female Conn. 3 3 X-End Y-End Signal Pin Number Pin Number Signal Shield 1 1 Shield Signal Ground 19 (Note 3) 19 Signal Ground Cable Present 3 21 XMIT DataXMIT Data+ Recv. DataRecv. Data+ 4 22 6 24 6 24 4 22 Recv. DataRecv. Data+ XMIT DataXMIT Data+ XMIT CLKXMIT CLK+ Recv. CLKRecv. CLK+ 5 23 8 26 17 5 23 8 26 35 TERM CLK+ XMIT CLK+ XMIT CLK Recv.
B.2.13 B.2.13 VAX Cable to CG Switch Item No. Part Number Description Group No. 010 Group No. 100 Group No.
C TIMING DATA AND PERFORMANCE CONSIDERATIONS Appendix C This appendix contains information on performance and CG database size. C.1 CG PROCESSING RESTRICTIONS The host processor should limit each ACP to one request message at a time. The CG allows the host processor to send multiple messages and can stack a maximum of 20 messages for processing. Actual concurrent processing, however, is limited by space limitations and by limitations on specific message types.
C.3 Get History performance has more variables; however, the essential thing to remember is that the difference in time required for a larger set of points (within the limit of 5986 data words) is relatively small. Throughput may be enhanced by using multiple ACPs to request the acquisition of history data because the CG can support up to four concurrent history requests. C.
D ASSIGNMENT OF PROCESS UNITS TO CG Appendix D This appendix contains information relating to the assignment of process units to the CG. 1. The number of process units that can be assigned to a CG is 63 minus the number of CGs assigned to the same checkpoint volume. For example, if you have two CGs assigned to one HM for checkpointing, there can be no more than 61 units assigned. 2.
Computer Gateway User Manual D-2 5/96
Index Topic Section Heading ABORTCOD (ACIDP parameter) ACCESSKEY (ACIDP parameter) ACIDP Definition Execution State Change Request List Return Mode Change Request Mode Change Return Parameter Descriptions Point Building Scheduling Recommendations Status Request Status Return Viewing and Changing ACP Definition Preparation Scheduling ACPROG (ACIDP parameter) ACT_TYPE (ACIDP parameter) Advanced Control Interface Data Points Advanced Control Programs Array Processing Bisynch Protocol Sequences, Dual-Link Seq
Index Topic Section Heading Calculated Results Data Points Communications Handler Level Messages Communications Handler Messages Configuring the CG Confirmation Message Connectors Convert Identifier Request Convert Identifier Return Custom Data Segment Data Access Data Access Status Codes Database List Request Message Database, memory requirements for Data Definition Tables Data Link Initialization Messages Message Structure Messages Format Messages, Analysis of Status Information Timeout Data Input Preco
Index Topic Section Heading Formats Data Link Messages Message Header Get Data Request (Internal DDT in CG) Request (Internal DDT in Host Processor) Return Get History Request Get History Return Get LCN Time Get Single Point Request (External Identifier) Get Single Point Request (Internal Address) Get Single Point Return (External Identifier) Get Single Value Return (Internal Address) Get Text Message Request Get Text Message Return GROUP_ID (ACIDP parameter) HDLC Protocol Header , Message History Average
Index Topic Section Heading Message Error Fields Format Sequences Structure Message Types ACIDP Execution State Change Request ACIDP List Return ACIDP Mode Change Request ACIDP Mode Change Return ACIDP Status Request ACIDP Status Return CG Database List Request CG Restore CRDP List Return Confirmation Convert Identifier Request Convert Identifier Return File Transfer Request/Response Internal DDT Build Request Internal DDT Build Return DDT Connect/Disconnect Request DDT Connect/Disconnect Return Internal
Index Topic Section Heading Store Single Return (Internal Address) Text Message Confirmation Text Message Timeout Time Synchronization Turn On ACP Messages Analysis of Communications Handler Level Communications Handler Internal DDT Preparation Data Link Initialization History Data Transfer Initialization Normal Operation Program Scheduling Program Status Startup NAME (ACIDP/CRDP parameter) Names, length of NEXT_RTM (ACIDP parameter) Normal Operation Messages OPER_DMD (ACIDP parameter) Parameter Array Pro
Index Topic Section Heading Sample Host Processor System 3.1 Scheduling by ACIDPs E.3.1 of ACPs 2.2.1, 2.3.1 Send Text Message Confirmation 4.9.5 Request 4.9.3 Response-Immediate 4.9.4 Timeout 4.9.5 Service B.1.2 Snapshots 4.8.2.1 Startup CG-Host Communications 2.4.2 Messages Sequence Figure 4-1 Recommendations 2.4.4 Status Codes, Data Access A.1 Status, Data Link 6.5 STIME (ACIDP parameter) 2.2, 6.3.2-Table 6-1, 6.4 Store Internal DDT in CG Request 4.5.3 Data Request 4.6.4 Data Return 4.6.
Index Topic Section Heading UNIT (ACIDP/CRDP parameter) Units, Process Viewing ACIDP & CRDP Points Computer Gateway User Manual 6.3.2-Table 6-1, 6.4 D.1 6.
Computer Gateway User Manual Index-8 5/96
READER COMMENTS Honeywell IAC Automation College welcomes your comments and suggestions to improve future editions of this and other publications. You can communicate your thoughts to us by fax, mail, or toll-free telephone call. We would like to acknowledge your comments; please include your complete name and address. BY FAX: Use this form and fax to us at (602) 313-4108. BY TELEPHONE: In the U.S.A.
Communications concerning technical publications should be directed to: Automation College Industrial Automation and Control Honeywell Inc. 2820 West Kelton Lane Phoenix, Arizona 85023-3028 FOLD FOLD From: NO POSTAGE NECESSARY IF MAILED IN THE USA FIRST CLASS PERMIT NO. 4332 Cut Along Line BUSINESS REPLY MAIL ` PHOENIX, ARIZONA POSTAGE WILL BE PAID BY ....
Industrial Automation and Control Honeywell Inc.
