Intecom. March

Transcription

1 Intecom Intecom Systems PDI-1000S MKO Application Manual March COMPANY PROPRIETARY STATEMENT All information contained herein is considered company proprietary and is restricted solely to assist in the support of the Intecom systems. This information includes only the product changes prior to the release date of this document. Neither this document nor the contents may be disclosed, copied, revealed or used in whole or part for any other purpose without the prior written permission of Intecom. This document must be returned upon request of Intecom.

2 PREFACE This document is to be used by Field Support when performing maintenance tasks for which they are responsible on an Intecom System. The document is organized in accordance with the approved outline established by Intecom. The information contained in this document may change without notice. Any recommended changes, improvements, additions or modifications to this document should be directed to: Intecom Product Documentation M/S 3A, Liberty Plaza II, 5057 Keller Springs Road Dallas, TX Second Edition, March 1994 This edition of the PDI-1000S MKO Application Manual may only be used for the purpose as stated in the preface. Updates, changes, or revisions of this document may be published as information becomes available. Copyright 1994, All Rights Reserved, Intecom. Printed in the U.S.A.

3 TABLE OF CONTENTS Chapter Page 1.0 INTRODUCTION General Audience Contents OPERATION MKO Interface Device PDI-1000S Installation... 3 Figure 1. Block Diagrams of MKO and PDI-1000S PDI-1000S Protocol: Smart Device Messaging PDI-1000S Message Format Generic and Application Dependent Subopcodes Types Of Smart Messages... 6 Table 2-1. Smart Messages and Opcodes - from the MCU (Outbound)... 7 Table 2-2. Smart Messages and Opcodes - to the MCU (Inbound)... 8 Table 2-3. Service Address - from the MCU... 9 Table 2-4. Service Address to the MCU DATABASE INSTALLATION Programmable Transceiver Creating Terminal Type (TTYP) Creating the Group and Application Name: GRPS Command Creating the Port: CARD Command Force Download to PDI-1000S DOWNLOADING MODEL Download Program Table 4-1. Condensed Download Procedure TROUBLESHOOTING General Maintenance Procedure Software Approach to Troubleshooting Hardware Approach to Troubleshooting PDI-1000S Alarm Messages i

4 THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. ii

5 1.0 INTRODUCTION 1.1 General This manual contains general and technical information for the PDI-1000S used as a MKO interface device. The information contained in this manual should be sufficient for understanding how a PDI-1000S MKO application is installed and operates in the TELARI/Intecom E database. The information contained in this manual is subject to change without notice. 1.2 Audience This manual is intended for use by field engineers and system managers who have successfully completed the Intecom Training Department course covering TELARI/Intecom E Operations and Maintenance. 1.3 Contents The contents of this manual are structured as follows: CHAPTER 1. INTRODUCTION This chapter introduces the PDI-1000S used as a MKO interface device. CHAPTER 2. OPERATION This chapter provides general background information about the operation of the PDI-1000S. CHAPTER 3. DATABASE INSTALLATION This chapter provides basic installation model for installing the PDI-1000S to be used as an MKO interface device. CHAPTER 4. DOWNLOADING MODEL This chapter provides detailed Downloading model, including information on all inquiries and responses for the PDI-1000S/MKO as configured via the TELARI/Intecom E database. CHAPTER 5. TROUBLESHOOTING This chapter provides maintenance and troubleshooting information for the PDI-1000S used as a MKO Interface Device and a discussion of common problems, database procedure and hardware checks. 1

6 THIS PAGE INTENTIONALLY LEFT BLANK 2

7 2.0 OPERATION 2.1 MKO Interface Device Intecom's Machine Keyboard Origination (MKO) permits mnemonic or numeric data call origination from manual keyboard devices connected to the TELARI/Intecom E. In the operation mode, MKO performs a destination addressing function that is automatically released once the data destination path is established. This frees the MKO for access by another keyboard. MKO data calls are originated by sending a data off-hook status message, Data Terminal Ready (DTR) transition Low to High, from the originating device to the TELARI/Intecom E. The TELARI/Intecom E connects the originating device to the MKO and the user then responds to TELARI/Intecom E MKO generated prompts that define the destination of the data connection. When all necessary information is collected, the originating device is disconnected from the MKO and connected to the destination device. If the data call is aborted for any reason, the user must initiate another complete origination sequence. Data call disconnection is done by dropping the DTR signal (if so optioned) or by pressing the ITE DATA button once or twice (user-definable). 2.2 PDI-1000S Installation A Programmable Data Interface-1000S (PDI-1000S) may be used as a Machine Keyboard Origination (MKO) interface device. To accomplish this, the PDI-1000S Data Communication Equipment <DCE> type, Intecom Part number XXX (desk top) or XXX (rack mount) is configured in the MCU database as a transceiver. The MCU marks (for the SU) the port as a PDI-1000S (not as an IPC). A PDI-1000S must be connected to a TELARI/Intecom E ITE port and then download the MKO application program, to serve as an MKO interface. The download program is read from a hard disk under the control of the TELARI/Intecom E Master Control Unit (MCU). 3

8 Figure 1. Block Diagrams of MKO and PDI-1000S 4

9 The PDI-1000S has three modes of operation: Boot Mode - Power up mode, run self-diagnostics, send load request to MCU for program. Load Mode - Receiving a particular application program from the MCU. Application Mode - Operating in a downloaded application software program that was downloaded from the MCU. 2.3 PDI-1000S Protocol: Smart Device Messaging The MCU and a PDI-1000S communicate using SMART DEVICE MESSAGING with the ITE Line Card relaying pass through messages between the two entities. 2.4 PDI-1000S Message Format In a typical PDI-1000S message, the first data byte contains a message address that identifies the PDI-1000S and is followed by a message number (SUBOPCODE) which identifies the action to be taken. For certain cases, the first byte will contain a service address and may contain a message number. The service address does not identify the PDI-1000S, but serves as an OPCODE. Service addresses have values in the range of F0 to FF; where, message addresses have values in the range of 1 to EF. 2.5 Generic and Application Dependent Subopcodes The SUBOPCODE of the PDI-1000S message is divided into two groups. The SUBOPCODES in the range between E0 and FF inclusive are generic to all PDIs. These OPCODES pertain to basic operations such as DOWNLINE LOADING and IDENTIFICATION. SUBOPCODES outside this range are application (or type) dependent, and their meaning is determined by the loaded program. NOTE The messages, explained in the preceding paragraphs, to and from PDI and MCU can be displayed using the Administrative Software Package (ASP) UTIL-SST command. 5

10 2.6 Types Of Smart Messages Smart messages are distinguished by message numbers (opcodes) and service address codes that specify what message is being transmitted or received. The tables included in this segment contain and show the following information: Table 2-1 Table 2-2 Table 2-3 Table 2-4 Message numbers sent from the MCU. Message numbers sent to the MCU. Service address definitions for messages from the MCU. Service address definitions for messages to the MCU. 6

11 Table 2-1. Smart Messages and Opcodes - from the MCU (Outbound) Message Number Smart Message 01 * Initialize MKO. 02 * Set Parameters. 03 * Send Statistics. 04 * Device Setup. 05 * Device Connected. 06 * Device Disconnected. 07 * Connection Failure. 08 * Load Sequence. 09 * Load String. 0A* Execute Sequence. 0B* 0C* 0D* Baud Programmed. 0E* Detect Data length and Parity EB EC Modify Memory. ED Examine Memory. EE Set Load Configuration Parameters. EF F0 Fl Undefined F2 Firmware ID Request. F3 Software ID Request. F4 Status Request. F5 Undefined F6 Software Match ID Request. F7 F8 F9 SMART IDOB. FA Restart. FB Reload. FC Exit Voice Load Mode. FD Enter Voice Load Mode. FE Exit Data Load Mode. FF Enter Data Load Mode * Messages 01 through 0F apply only if the PDI-1000S is running an MKO application. 7

12 Table 2-2. Smart Messages and Opcodes - to the MCU (Inbound) Message Number Smart Messages 01* Statistics Report. 02 * Channel Initialization Complete. 03 * Channel Failure. 04 * Device Off-line. 05 * Activity Timeout. 06 * Channel setup Complete. 07 * Sequence Complete. 08 * Sequence Error. 09 * Characters Received. 0A* Special Message Received. 0B* Device Disconnect. 0C* Baud Rate Indication. 0D* Auto Parity Complete. 0E* Excessive Data Load EC Memory Modified. ED Memory Examined. EE Received Load Configuration Parameters. EF Alarm. F0 Fl F2 Firmware ID Response. F3 Software ID Response. F4 Status Response. F5 F6 Software Match ID response. F7 F8 F9 FA FB FC Data Downline Load Complete. FD Data Segment Complete. FE Data Ready For Download. FF Data Load Request. * Messages 01 through 0F apply only if the PDI-1000S is running an MKO application. 8

13 Table 2-3. Service Address - from the MCU OPCODE NAME EF F0 General Broadcast. Fl F2 Set Address Broadcast. F3 F FA FB FC FD FE Cold Start Broadcast. FF Cold Start Broadcast. Table 2-4. Service Address to the MCU OPCODE NAME F0 Fl Address Request. F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF 9

14 THIS PAGE INTENTIONALLY LEFT BLANK 10

15 3.0 DATABASE INSTALLATION 3.1 Programmable Transceiver A Programmable Port Device may function as an MKO interface device emulating the IPC transceiver functions. It is configured in database as a Programmable Transceiver Port. The Port type XCVR is added as an available port type in the Administrative Software Package (ASP) Card command when the transceiver application feature is enabled. When creating a transceiver port, the ITE circuit will automatically be marked as a programmable device. The transceiver group specified for the port should have had an application name associated with it. If not, an additional prompt for the application name will be issued for the group. A dynamic help menu may be obtained to show the existing application names. The PDI-1000S is configured (after hardware and initial installation) via the ASP, using the commands TTYP, GRPS and CARD. The following is an example of a typical configuration using the underlined commands after the prompt (>) Creating Terminal Type (TTYP) When the PDI-1000S enters the Application Mode, default data protocol is set in the unit's memory. To create the default protocol values of the PDI-1000S enter the underlined commands after the prompt Enter N or (CR) because this prompt does not apply to this application. 11

16 3.1.2 Creating the Group and Application Name: GRPS Command A new prompt for APPLICATION NAME is added to GRPS command for the transceiver group. It appears for the transceiver group only when the transceiver application feature is enabled. The application name entered should be an existing name. A dynamic help menu may be obtained by entering "? ", which shows a listing of the available application names. The name corresponding to the MKO application must be entered. 12

17 3.1.3 Creating the Port: CARD Command 13

18 3.1.4 Force Download to PDI-1000S The PDI-1000S contains a volatile memory. When power is removed from the PDI-1000S, the application program will have to be loaded into memory. The download procedure will occur automatically, or it can be activated using the Administrative Software Package terminal. Use the following commands to start a download of the application program for the PDI-1000S. 14

19 4.0 DOWNLOADING MODEL 4.1 Download Program Table 4-1 illustrates condensed procedures that are required to download an application program from the hard disk to the PDI-1000S. Steps a. through q. describe the download procedure in more detail; steps r. through t. are additional procedural steps: a. Power Up PDI-1000S If power is removed from the PDI-1000S, the special application program will be destroyed. When power is re-applied to the PDI-1000S, an automatic download of the MKO application software will occur, as described in the remaining steps. A self test is initiated on the unit at this time to determine if the PDI-1000S is operational. The green MODE LED will light solid during this test. b. Assign Address to PDI-1000S An address is requested by and assigned to the PDI-1000S to identify the unit. The address appears in each smart message sent from the PDI-1000S to MCU. The assigned address represents the physical location of the PDI with respect to other smart devices that may be connected to the same ITE circuit (i.e., AP-Phone). The PDI-1000S requests its address from the MCU after power up self-test is complete. The procedure will start by the PDI-1000S initially sending an ADDRESS REQUEST to the MCU. The MCU will respond with a SET ADDRESS to XXX (XXX = assigned number) message to the requesting PDI-1000S. c. Request PDI-1000S Type The PDI-1000S will send a LOAD REQUEST message to the MCU every thirty seconds (after it has obtained its address). When the MCU receives a LOAD REQUEST from a PDI-1000S, it sends a request for the PDI's Software Match ID. When the MCU receives the requested SMID, it is compared with the application database to determine which program to DOWNLINE LOAD to the PDI-1000S. d. Downline Loading PDI-1000S Coordination between the MCU and PDI-1000S of the downline load process is managed through the use of Smart Device Signaling. The transfer of the program data occurs over a IOD/IOC load channel to the PDI-1000S. The MCU determines which LOAD contains the proper MKO application program (located on hard disk) to send to the PDI-1000S. e. Load Request DOWNLINE LOADING is initiated in response to a LOAD REQUEST from the PDI-1000S. The PDI-1000S sends a LOAD REQUEST whenever its load is determined to be corrupted or power is applied to the unit. The LOAD REQUEST is sent to the MCU after a random delay of. 3 to 30 seconds. The purpose of the random delay is to 15

20 Table 4-1. Condensed Download Procedure MCU TO PDI PDI TO MCU Power up PDI-1000S or load is corrupted. The MKO application program is destroyed when power is removed from the PDI-1000S. PDI-1000S in Boot state. Self-diagnostic is automatically performed, when power is applied to the PDI. Start loading operations Random delay between. 3 to 30 seconds before sending an ADDRESS REQUEST to MCU. Address Response to ADDRESS REQUEST. At this time the PDI-1000S is not available as an MKO device. Send message to PDI-1000S requesting SMID information. Sends load request. Sends SMID information to MCU. Verifies SMID. Sends SET LOAD CONFIGURATION PARAMETERS message to PDI-1000S. (Programmable Option). Replies to MCU that LOAD CONFIGURATION PARAMETERS message was received. Checks operation status of the REPLY message. (Programmable Option). Enter LOAD MODE message is sent to PDI-1000S, containing version, revision and patch information. Connects PDI to IOD/IOC port for downloading. Receives LOAD COMPLETE message from PDI-1000S. Responds to MCU "READY FOR DOWNLINE LOAD". Looking for LOAD (header on load). After it is found the PDI-1000S will receive DOWNLINE LOADING until completed. Send message to MCU that LOAD is completed. If the LOAD was not good the PDI-1000S will start with a LOAD REQUEST message every 30 seconds to MCU. Checks status of the LOAD COMPLETE message. Disconnects PDI from IOD/IOC. Sends EXIT LOAD MODE message to PDI-1000S. Sends INITIALIZE message to PDI. Receives Exit LOAD message. Send CHANNEL INITIALIZATION COMPLETED message to MCU. Enters MKO Application Mode. 16

21 to the MCU. The delay time is calculated by using the SMID of each PDI-1000S, located on the TELARI/Intecom E. This prevents a large number of LOAD REQUESTS from other PDI-1000S' being sent at the same time. f. Repetitive Load Requests The PDI-1000S repeats its LOAD REQUEST every 30 seconds until DOWNLINE LOADING begins or until it receives an IO Programming command. An I0 Programming Command indicates to the PDI-1000S that no DOWNLINE LOAD is forthcoming at this time. g. Downline Load Throttling When a LOAD REQUEST is received by MCU, an attempt is made to start Loading operation. MCU will disregard any messages if it can not handle it at that time. Load operations may be inhibited if all dedicated Information Links are NOT available because other Loading operations are in progress. Loading operations are also throttled to prevent overloading MCU/LC communications. h. Downline Load Re-attempt The MCU does not remember which ports have requested Loading. It relies on the thirty second repetition of the LOAD REQUEST from the PDI-1000S for a re-attempt at downline loading. The PDI-1000S remains in the LOAD MODE until another LOAD REQUEST is received by the MCU. At this time, the MCU attempts to start Loading operations. i. PDI-1000S Software ID Mapping When PDI-1000S powers up it executes a self-test. After this is completed it will be placed in a Requesting Load Mode by its Boot firmware. If conditions are OK to start loading, a message is sent to the PDI-1000S requesting the SMID. When the PDI-1000S returns this information, it is used by the MCU to determine the LOAD and CONFIGURATION PARAMETERS needed by the PDI-1000S. j. Set Load Configuration Parameters If LOAD CONFIGURATION PARAMETERS are required for the PDI-1000S, they are sent to the PDI-1000S in the SET LOAD CONFIGURATION PARAMETERS message. The PDI-1000S replies with a LOAD CONFIGURATION PARAMETERS RECEIVED message. The MCU checks the OPERATION STATUS of the reply message. If the parameters were received in error, the MCU terminates the DOWNLINE LOAD PROCESS and waits for another LOAD REQUEST from the PDI-1000S. 17

22 k. Enter LOAD MODE Once the PROPER LOAD is determined and CONFIGURATION PARAMETERS are sent, an ENTER LOAD MODE message is sent to the PDI-1000S. When the PDI-1000S responds with a READY FOR DOWNLINE LOAD message, MCU connects the PDI-1000S to one of six dedicated Information Links to receive a LOAD from the MCU. l. Data Blocking The command to ENTER LOAD MODE uses a BROADCAST ADDRESS message. The address of the PDI-1000S receiving the DOWNLOAD is contained in the DATA PORTION of the BROADCAST ADDRESS message. m. Downline Load Abort by the PDI-1000S Abort occurs with a checksum failure of any packet (record) or entire load failure. When aborting the DOWNLINE LOAD OPERATING, the PDI-1000S sends a LOAD COMPLETE MESSAGE with an indication of LOADING FAILURE. The PDI-1000S then returns the state of sending LOAD REQUESTS every thirty seconds to the MCU. n. Downline Load Complete When the MCU receives the LOAD COMPLETE message from the PDI-1000S, MCU disconnects the Information Link, sends an EXIT LOAD MODE message, and checks the status of the LOAD COMPLETE message. If the LOADING was successful, the PDI-1000S is placed in Application Mode; otherwise, it remains in the REQUESTING LOAD MODE. o. Downline Load TIMEOUT If the LOADING TIMEOUT (12 seconds <MCU programmable>) occurs before a LOAD COMPLETE message is received from the PDI-1000S, the MCU disconnects the IOD/IOC loading channel. An EXIT LOAD MODE message is sent to the PDI-1000S and it enters the REQUESTING LOAD mode. q. Exit LOAD MODE When the MCU terminates DOWNLINE LOADING, an EXIT LOAD MODE message is sent to the PDI-1000S. When exiting from LOAD MODE, the MESSAGE ADDRESS is broadcasted. The address of the DOWNLOADING PDI-1000S is contained in the data portion of the EXIT LOAD MODE message. The DOWNLOADING PDI-1000S then enters its APPLICATION MODE by passing control to its DOWNLOADED PROGRAM. p. Downline Loading Aborted by MCU When the MCU aborts a DOWNLINE LOAD OPERATION, it sends the PDI-1000S an EXIT LOAD MODE message. The PDI-1000S is left in the DOWNLINE LOAD 18

23 STATE. It is possible for the MCU to abort LOADING after the PDI-1000S has successfully completed LOADING but before the MCU has received the LOAD COMPLETE message. The MCU, however, will honor the LOAD COMPLETE message and place the PDI-1000S in the APPLICATION MODE. r. PDI-1000S Restart In response to an ASP request (UTIL/IDR/FLPT) the MCU will send a RESTART COMMAND to the PDI-1000S. The PDI-1000S, if able, will restart its application program. The RESTART COMMAND does not cause the PDI-1000S to reinitiate DOWNLOAD in the Application Mode. s. Forced Downline Load In response to an Administrative Software Package request (CFG/L. Load-Card, Access by circuit), the MCU will send a RELOAD COMMAND to the PDI-1000S causing the PDI-1000S to return to its REQUESTING LOAD MODE. t. PDI-1000S Firmware Identification In response to an Administrative Software Package FIRMWARE ID REQUEST for a PDI-1000S, the MCU will send two messages to the PDI-1000S. One message requests the FIRMWARE ID, and the other message requests the SOFTWARE ID. The second message is not sent until a RESPONSE is received from the first message. After both messages are received, MCU relays the information to the Administrative Software Package. 19

24 THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. 20

25 5.0 TROUBLESHOOTING 5.1 General This chapter provides maintenance and troubleshooting instructions for the PDI-1000S used as a MKO Interface device. 5.2 Maintenance There are no field replaceable parts in the PDI-1000S. CAUTION The cover of the PDI-1000S must NOT be removed when a problem occurs with the unit. 5.3 Procedure When a problem occurs with the an application, first retrace your work to determine if there may be a problem with the software application or the physical hardware. Often either an improperly configured database application or loose connection is the cause. The flowchart procedures assume that the MKO Application has operated at one time. Problems encountered during new installation are usually caused by system database options not enabled or defined. The flowchart is used to take a software approach to troubleshooting. If the problem is not found using this method, refer to the hardware approach to troubleshooting. 21

26 5.3.1 Software Approach to Troubleshooting 22

27

28 5.3.2 Hardware Approach to Troubleshooting a. Remove the PDI-1000S by disconnecting the TELARI/Intecom E line from the IBX Line jack (RJII Jack). b. Install a spare PDI-1000S and connect the cable removed in step a. c. Note if there are any alarm indications on the System Console. The message may help isolate the fault. Refer to PDI-1000S Alarm Messages on the following page. d. If the problem is still present after replacing the PDI-1000S, check the wiring from the PDI-1000S (back) to the TELARI/Intecom E/IU backplane. e. If the problem is still present after completing step d, refer to the maintenance manuals for the TELARI/Intecom E to correct the problem. 24

29 5.3.3 PDI-1000S Alarm Messages Should there be a failure with the PDI-1000S, an alarm may be indicated on the System Console and/or System Printer. The following is a list of information fields that are provided: Message Number: Equipment Class: PPD Alarm Type: MIN Reason: PROGRAMMABLE PORT DEVICE DOWNLINE LOAD FAILURE. Result: DEVICE REMAINS IN STATE WAITING FOR DOWNLINE LOAD. Data Word 0: PORT NUMBER Data Word 1: FAILURE CODE 1= FAILED TO CONNECT TO LOADER (X.CNCG) 2= DEVICE REPORTED LOAD FAILURE 3= TIMEOUT WAITING FOR LOAD COMPLETE FROM DEVICE Data Word 2: PROGRAMMABLE PORT DEVICE FACILITY NUMBER Data Word 3: LOADER FACILITY NUMBER Required Action: REPORT PROBLEM TO FIELD ENGINEER Message Number: Equipment Class: PPD Alarm Type: MAJ Reason: PDI 1000S 1SR Buffer Overflow Result: LOSS OF DATA, SERIOUS IMPACT, PROCESSOR REBOOT. Data Word 0: 1SR NOT EQUAL 0, CODE = 0 Data Word 1: ZERO Data Word 2: ASCII REPRESENT QUEUE NAME (i. e., F 41 FROM) Data Word 3: ASCII REPRESENT QUEUE NAME (i. e., DATA) Required Action: RE-DOWNLOAD Processor/Task: PDI 1000S Suspected Problem: PERIPHERAL DEVICE Message Number: Equipment Class: PPD Alarm Type: MAJ Reason: FAIL SELFTEST -RAM Result: Loss of Data Data Word 0: MEMORY ADDRESS WHERE SELFTEST FAILED Data Word 1: Data Word 2: 00, VALUE TESTED FOR, 00, VALUE READ Data Word 3: Required Action: Re-Download Processor/Task: PDI 1000S Suspected Problem: Peripheral Device 25

30 Message Number: Equipment Class: PPD Alarm Type: MAJ Reason: FAILED SELFTEST. ROM DOES NOT CHECKSUM Result: LOSS OF DATA Data Word 0: Data Word 1: Data Word 2: Data Word 3: Required Action: Re-Download, MOS PORT - SEVERAL FAILURES Processor/Task: PDI 1000S Suspected Problem: Peripheral Device Message Number: Equipment Class: PPD Alarm Type: MAJ Reason: BAD OPCODE RECEIVED Result: LOSS OF DATA Data Word 0: ISR Not Equal 0, Code 0 Data Word 1: Data Word 2: Data Word 3: Required Action: Re-DOWNLOAD, THRESHOLD Processor/Task: PDI 1000S Suspected Problem: Peripheral Device Message Number: Equipment Class: PPD Alarm Type: MAJ Reason: ILLEGAL NMI Result: LOSS OF DATA Data Word 0: Data Word 1: Data Word 2: Data Word 3: Required Action: Re-DOWNLOAD Processor/Task: PDI 1000S Suspected Problem: Peripheral Device Message Number: Equipment Class: PPD Alarm Type: MAJ Reason: RESET 38 PROCESSOR EXECUTED "FF" SOMEWHERE Result: LOSS OF DATA Data Word 0: Data Word 1: Data Word 2: Data Word 3: Required Action: Re-DOWNLOAD Processor/Task: PDI 1000S Suspected Problem: Peripheral Device 26

31 Message Number: Equipment Class: PPD Alarm Type: MAJ Reason: PROCESSOR MADE ILLEGAL INTERRUPT Result: LOSS OF DATA Data Word 0: I = INTERRUPT 1, 2 = INTERRUPT 2, 3 = PROGRAMMABLE TIMER 0, 4 = PROGRAMMABLE TIMER 1, 5 DIRECT MEMORY ACCESS 0, 6 = DIRECT MEMORY ACCESS 1, 7 CLOCKED SERIAL OUTPUT, 8 = ASYNC SERIAL COMM INTERFACE 0, 9 ASYNC SERIAL COMM INTERFACE I Data Word 1: ZERO Data Word 2: ZERO Data Word 3: ZERO Required Action: Re-DOWNLOAD Processor/Task: PDI 1000S Suspected Problem: Peripheral Device Message Number: Equipment Class: PPD Alarm Type: INF Reason: REBOOT DUE TO FORCED LOAD Result: Data Word 0: Data Word 1: Data Word 2: Data Word 3: Required Action: Re-DOWNLOAD Processor/Task: PDI 1000S Suspected Problem: Peripheral Device 27

32 THIS PAGE INTENTIONALLY LEFT BLANK. 28