PDI Modem Pooling Application Manual For TELARI/Intecom E. March COMPANY PROPRIETARY STATEMENT

Transcription

1 Intecom PDI Modem Pooling Application Manual For TELARI/Intecom E 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 in 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 Engineers (FEs) when performing daily operational and maintenance tasks for which they are responsible on a TELARI/Intecom E System. The document is organized in accordance with the approved outline established at the Home Office of Intecom. The scope of this manual reflects the type of Installation, Test, and Operations and Maintenance philosophy selected for this product. This document describes the procedures for installing and maintaining the PDI-1000 Modem Pooling Application. Installation considers the database and associated procedures. Maintenance considers the software approach and the hardware approach to troubleshooting. 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 MS 3A Liberty Plaza II 5057 Keller Springs Road Dallas, TX Second Edition March 1995 This edition of the PDI-1000 Modem Pooling 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 1995, All Rights Reserved, Intecom Printed in the U.S.A.

3 TABLE OF CONTENTS Titles 1. INTRODUCTION General Audience Contents OPERATION Modem Pooling Application Analog Digital Translator (ADT) Modems PDI-1000S Protocol: Smart Device Messaging PDI-1000S Message Format Generic And Application Dependent Subopcodes Marking Smart Ports PDI-1000S Address Types Of Smart Messages DATABASE INSTALLATION Database Parameters For Modem Pooling Creating Terminal Type (TTYP) Creating the Group and Application Name: GRPS COMMAND Creating the Port: CARD Command Firmware Identification Force Download To PDI-1000S FORCED PDI-1000S DOWNLOAD Download Program TROUBLESHOOTING General Maintenance Procedure Software Approach To Troubleshooting (Modem Pooling Application) Hardware Approach To Troubleshooting PDI-1000S Alarm Messages Page Figures 2-1. PDI-1000S Modem Pooling Hardware Configurations... 5 Page i

4 Tables TABLE OF CONTENTS 2-1. Smart Messages and Opcodes - from the MCU (Outbound) Smart Messages and Opcodes - to the MCU (Inbound) Service Address - from the MCU Service Address - to the MCU Condensed Download Procedure Page ii

5 CHAPTER 1 INTRODUCTION 1.1 General This manual contains general and technical information for the Programmable Data Interface (PDI)-1000S used in a Modem Pooling application. The information contained in this manual should be sufficient for understanding it's installation and operation with 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 in a Modem Pooling Application. CHAPTER 2. OPERATION General background information about the operation of the PDI-1000S is provided here. CHAPTER 3. DATABASE INSTALLATION Chapter 3 provides the basic installation model for installing the PDI-1000S to be used in a Modem Pooling Application. CHAPTER 4. FORCED PDI-1000S DOWNLOAD This chapter provides detailed, as well as condensed, procedures for initiating a forced download of a PDI-1000S. CHAPTER 5. TROUBLESHOOTING Maintenance and troubleshooting information for the PDI-1000S is provided in chapter 5. A discussion of common problems, database procedure and hardware checks are noted. 1

6 THIS PAGE INTENTIONALLY LEFT BLANK 2

7 CHAPTER 2 OPERATION 2.1 Model Pooling Application PBX data users often have data communications requirements which can only be reached via public network facilities (TELCO). Typically, this requirement is met with a modem. Modem Pooling allows the TELARI/Intecom E to allocate modems on an "as needed" basis. In doing this, a group of modems become a shared resource for many system users. A Programmable Data Interface (PDI)-1000S may be used as a Modem Pooling interface. This application requires a PDI-1000S (Data Terminal Equipment (DTE) model), a Modem and an Analog-to-Digital Translator (ADT). Some configurations also require an additional power supply. A Modem Pooling application is shown in figure 2-1. The ADT is a modular interface device that provides conversion from the TELARI/Intecom E standard 144 KHZ Integrated Terminal Equipment (ITE) format to the Standard Telephone Equipment (STE) analog interface. The PDI-1000S is responsible for interpreting commands from the TELARI/Intecom E Master Control Unit (MCU) and sending appropriate control commands to the ADT for control of the analog interface. It is also responsible for controlling and monitoring the RS-232 type interface of the modem. The ADT provides analog/digital conversion, MI/MIC control, analog hook status and 20HZ ring current if required. A PDI-1000S located on an ITE circuit (when downloaded with an application specific software program) serves as a modem interface device. The download program is broadcast from a hard disk under the control of the TELARI/Intecom E MCU. The MCU connects to the PDI-1000S through the Switching Unit (SU). The PDI-1000S is attached to the TELARI/Intecom E, using the 144K line (ITE) interface. An ITE circuit built as a modem consumes two high speed information bus (HIB) timeslots. The PDI-1000S has three modes of operation: Boot Mode - Power up mode, run self-diagnostics and send load request for a particular application program. Load Mode - Receiving a particular application program from the hard disk assembly. Application Mode - Operating in a particular application software program that was downloaded from the hard disk assembly Analog Digital Translator (ADT) The ADT may be configured for many different applications. For Modem Pooling, specified internal connectors on the PC Board must be strapped to setup the ADT for the individual application. Refer to the ADT Support Manual, Intecom Part Number X, for the appropriate strapping connections and installation procedure. 3

8 2.1.2 Modems To properly implement a PDI Modem Pooling application, the type of modem being used must be known. Smart Modems that support the "AT" command set can be used. Dumb Modems (that do not support the "AT" command set) can be used if they support the MI/MIC configuration. To determine the type of modems you have and the configurations they can support, refer to the Modem's User or Installation Manual. There are two hardware configurations for Modem Pooling: with power supply or without power supply (refer to Figure 2-1). For dumb modems, and smart modems that do not support A/A1 off-hook supervision, an external power supply is required. Dumb Modem MI/MIC Configuration Dumb Modems require ring voltage to operate in answer mode, and MI/MIC contact closure to operate in the originate mode. Ring voltage (20HZ) is provided by the ADT's external power supply. Refer to the ADT manual for the proper operation of the ADT. Smart Modem A/A1 Configuration Smart Modems that can support A/A1 operation are enabled in a variety of ways (hardware strapping or "S" Registers). Refer to the Modem's User or Installation Manual. Dial Tone Detection must be disabled on the Modem, by modifying the call progress options (usually X0, X1, or X3). It is recommended that the Modem be configured to disconnect and hard reset when DTR is toggled (usually the &D3 switch). Also, disable the Command echo (usually E0). Command echo in itself will not adversely affect modem operations. But, it may cause confusion, by creating additional modem commands during the dialing process if enabled. Refer to the ADT manual for the proper operation of the ADT. Smart Modem No A/A1 Configuration Smart Modems, that do not provide the A/A1 off-hook supervision, use the -48 VDC loop current from the external power supply via the ADT. Dial Tone detection must be disabled on the Modem, by modifying the call progress options (usually X0, X1, or X3). It is recommended that the Modem be configured to disconnect and hard reset when DTR is toggled (usually the &D3 switch). Also, disable the Command echo (usually E0). Command echo in itself will not adversely affect modem operations. But, it may cause confusion, by creating additional modem commands during the dialing process if enabled. Refer to the ADT manual for the proper operation of the ADT. 4

9 A / A 1 C O N F I G U R A T I O N I B X P D I R S I T E J 1 A D T J 3 M O D E M R S R J 1 1 N O A / A 1 C O N F I G U R A T I O N I B X P D I R S I T E A D T J 4 J 1 J 3 R J 1 1 R S M O D E M R S C a b l e P O W E R S U P P L Y V D C l o o p C u r r e n t D i g i t a l I n t e r f a c e L i n e T o V A C A n a l o g L i n e M I / M I C C O N F I G U R A T I O N I B X PDI-1000 I T E R S A D T J 4 J 1 J 3 R J 1 1 M O D E M R S P O W E R S U P P L Y V D C L o o p C u r r e n t & R i n g V o l t a g e T o V A C Figure 2-1. PDI-1000S Modem Pooling Hardware Configurations 5

10 2.2 PDI-1000S Protocol: Smart Device Messaging The MCU and a PDI-1000S communicate using SMART DEVICE MESSAGING with the ITE Line Card. 2.3 PDI-1000S Message Format In a typical PDI-1000S message, the first data byte contains a message address which 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.4 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. 2.5 Marking Smart Ports NOTE The messages, explained in the preceding paragraphs, to and from PDI and MCU can be displayed using the M/M UTIL-SST command. Circuits defined as modems in the MCU data base will be marked for Smart Device Protocol. If not marked, smart messaging to or from the PDI-1000S will be blocked by the MCU or line card. 2.6 PDI-1000S Address An address is assigned to the PDI-1000S, and the address appears in smart message to and from the device. The address represents the relative position of the PDI-1000S. When powered on, the device sends repeatedly an 'ADDRESS REQUEST' in the Inbound Direction. The MCU will respond with a 'SET ADDRESS to X' message. 2.7 Types Of Smart Messages Smart messages are distinguished by message numbers (opcodes) and service address codes which specify what message is being transmitted or received. The tables included in this segment contain and show the following information: 6

11 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. The following tables are a listing of some of the possible smart messages. MCU-to-circuit communication can be viewed via the Administrative Console UTIL-SST command.. 7

12 Table 2-1. Smart Messages and Opcodes - from the MCU (Outbound) Message Number Smart Message 01 * Control Modem and Polling States. 02 * Read Modem Status. 03 * Modem Pooling sequence abort. 04 * 05 * 06 * 07 * 08 * 09 * 0A* 0B* 0C* 0D* 0E* EB Idle Request. 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 a Modem Pooling application. 8

13 Table 2-2. Smart Messages and Opcodes - to the MCU (Inbound) Message Number Smart Messages 01* Modem Status Report. 02 * Modem Status Timeout. 03 * 04 * 05 * 06 * 07 * 08 * 09 * 0A* 0B* 0C* 0D* 0E* 15* 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 Voice Downline Load Complete. F9 Voice Segment Complete. FA Voice Ready for Download. FB Voice Load Request. 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 a Modem Pooling application. 9

14 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 10

15 3.1 Database Parameters For Modem Pooling CHAPTER 3 DATABASE INSTALLATION A PDI-1000S is configured in the database as a Programmable Modem Port. Port type "MODM" is added to ITE line card when the modem application feature is enabled. When a modem port is created on an ITE card, it will automatically be marked as a programmable device. It will function as a single port and take two facilities and two time slots (one for analog side, one for digital side). Both the digital and analog side will be marked as a programmable device. The modem group specified for the port should have an application name associated with it. If it hasn't, 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. NOTE Check Maintenance Information Bulletins (MIBs) for Current load names, SWID, SMID, etc Creating Terminal Type (TTYP) When the PDI-1000S enters the Application Mode, default data protocol is set in the unit's memory. This is a special TTYP to be used only in the modem group definition. To set the default protocol values of the PDI-1000S, perform the following steps: NOTE Do not use AUTO BAUD in the modem group definition. The PDI may get the wrong information. SELECT COMMAND => TTYP(CR) SELECT MODE: PRINT, DISPLAY, UPDATE => U(CR) UPDATE MODE: C=CREATE, M=MODIFY, OR D=DELETE => C(CR) SPECIFY DATA TERMINAL TYPE NUMBER...=> 4(CR) ENTER TITLE:... => MODEM(CR) ENTER LINE TYPE: A=ASYNCHRONOUS; L=LO-SPEED SYNC; H=HI-SPEED SYNC...A => A(CR) ENTER PROTOCOL: B=BISYNC; S=SDLC; H=HDLC; D=DDCMP...B => B(CR) IS THIS A MODEM? Y=YES OR N=NO...N => Y(CR) 11

16 TERMINAL SPEED CODE OR?...AUTO BAUD =>?(CR) These are the speeds actually used: 8 = = = = = TERMINAL SPEED CODE OR?...=> 15(CR) LOWER SPEED CODE OR N=NONE...UNDEFINED=>(CR) ENCODING: A=ASCII; E=EBCDIC; B=BAUDOT...A => A(CR) DATA TERMINAL EQUIPMENT (DTE)? Y=YES; N=NO...N => Y(CR) PARITY: E=EVEN; O=ODD; A=AUTO; M=MARK; S=SPACE; N=NONE...E => E(CR) STOP BITS: 1, 2, OR => 1(CR) DATA LENGTH IN BITS: 5, 6, 7, OR => 7(CR) *** VERIFY/DISPLAY *** MODEM ** DATA TERMINAL TYPE DEFINITION NUMBER 4 DATE TIME TYP...LINE TYPE... ASYNCHRONOUS PTC...PROTOCOL... BISYNC MDM...MODEM... YES SPD...TERMINAL SPEED SP2...LOWER SPEED (TWO-SPEED MODEMS)... UNDEFINED CDE...ENCODING... ASCII DTE...DATA TERMINAL EQUIPMENT... YES PAR...PARITY... EVEN STB...STOP BITS... 1 DLG...DATA LENGTH... 7 DATA BITS DOES UPDATE VERIFY? => Y(CR) TABLE CHANGE PERFORMED Creating the Group and Application Name: GRPS COMMAND A new prompt for "Application Name" is added to the GRPS command for Modem group. It only appears for Modem group when the Modem Pooling application feature is enabled. The application name entered should be an existing name. Typing "?", will give a listing of the available application names. If the PDI-1000's are not physicaly installed and connected to ITE cards, "N" (the default in create mode) should be entered as the application mode. A prompt for Application Name for the group will appear when there is a programmable port device defined for the group. 12

17 Caution needs to be taken when modifying one group's application name to 'N' there may be programmable port devices using this group. There will be no downline load for those programmable port devices, if there is no application name defined for the group. SELECT COMMAND => GRPS(CR) SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES, SEARCH => U(CR) UPDT: C-Create,M-Modify,D-Delete,P-Copy... => C(CR) SPECIFY GROUP NUMBER:... => 4(CR) ENTER GROUPS TYPE: OR?... => MGRP(CR) ENTER TITLE:... =>(CR) ***...MODEM GROUP...4 APPLICATION NAME or N=None or?...n =>?(CR) *** APPLICATION NAMES *** SIPC... MKO... MODM...MODEM POOLING XITE...XITE LINECARD... APPLICATION NAME or N=None or?...n => MODM(CR) TRUNK SELECTION: L=LONGEST IDLE; T=TOP DOWN; B=BOTTOM UP...L => L(CR) TERMINAL TYPE NUMBER... => 4(CR) RELEASE ON DTR: Y=YES; N=NO...Y => Y(CR) DATA EXCLUSION KEY: A=ASSERTED ALL TIME; (2-7)=SECONDS...A => A(CR) ANSWER MODE ALLOWED: Y=YES; N=NO...Y => Y(CR) DUAL SPEED INDICATION: Y=YES; N=NO...Y => N(CR) DTR ASSERTION: B=BEFORE RING; A=AFTER RING..B => B(CR) SPEED INDICATION DETECTION AFTER CARRIER DETECT T=USE CTS; D=USE CD...T => T(CR) ORIGINATE MODE ALLOWED: Y=YES; N=NO...Y => Y(CR) SPEED PROGRAMMING REQUIRED: Y=YES; N=NO...N => N(CR) CARRIER OR CTS DETECT TIME: (5-63)...SEC:20 => 20(CR) RING INDICATION TIME: (4-15)...SEC: 6 => 6(CR) OFF-HOOK DETECTION TIME: (3-15)...SEC: 5 => 5(CR) *** VERIFY/DISPLAY *** ***...MODEM GROUP...4 PDA...APPLICATION NAME...MODM UGP...USER GROUP NUMBER...1 SLC...TRUNK SELECTION...LONGEST TTY...TERMINAL TYPE NUMBER...4 DLR...RELEASE ON DTR...YES MDE...DATA EXCLUSION KEY...ASSERTED ALL THE TIME MAN...ANSWER MODE ALLOWED...YES MSI...DUAL SPEED INDICATION AVAILABLE...YES MDT...DTR ASSERTION SEQUENCE...BEFORE RING MCD...SPEED INDICATION DECT.AFTER.CD...USE CTS MOR...ORIGINATE MODE ALLOWED...YES MSP...SPEED PROGRAMMING REQUIRED...NO MPS...CARRIER OR CTS DETECT...SEC: 20 MRI...RING INDICATION...SEC: 6 MOT...OFF-HOOK DETECTION...SEC: 5 PORT ASSIGNMENT REPORT 13

18 NO PORTS ASSIGNED DOES UPDATE VERIFY? => Y(CR) TABLE CHANGE PERFORMED Creating the Port: CARD Command Use the CARD command to create a port for the Modem Pooling application. SELECT COMMAND => CARD(CR) SELECT MODE: PRINT, DISPLAY, UPDATE, MOVE => U(CR) UPDT MODE: C-Create M-Modify D-Delete P-Copy. => C(CR) ENTER PORT NUMBER or?... => WW.X.YY.ZZ(CR) ENTER PORT TYPE OR?...DRPT =>?(CR) ATDC...ATTENDANT CONSOLE DPRT...DATA PORT DTRK...DATA TRUNK MODM...PROGRAMMABLE MODEM PORT XCVR...PROGRAMMABLE TRANSCEIVER PORT ENTER PORT TYPE OR?...DRPT => MODM(CR) MODEM GROUP NUMBER... => 4(CR) APPLICATION NAME or?... => MODM(CR) *** VERIFY/DISPLAY *** ***...MODEM...PORT NUMBER: WW.X.YY.ZZ(CR) ***...PROGRAMMABLE DEVICE...YES(CR) ***...MODEM GROUP NUMBER...4(CR) DOES UPDATE VERIFY? => Y(CR) TABLE CHANGE PREFORMED Firmware Identification To identify the firmware and software version loaded in the PDI-1000S, perform the following steps: SELECT COMMAND => UTIL(CR) SELECT SUBCOMMAND or?...=>?(cr) SST...STATE STIMULUS TRACE AGP...ATTENDANT GROUP DLR...DIRECTORY LOOKUP AUTHCODE RECOVERY TVL...TABLE VALIDATOR CPF...COPYFILE LDR...LOADER MSY...MASTER CLOCK SYNC PRT...PART SSP...SURVIVABLE REMOTE SWITCHING PARTITION FRI...FACILITY RE-INITIALIZE SYS...SYSTEM BUFFER OLR...ON-LINE RETROFIT ILK...INFORMATION LINK VER...VERSION SELECT SUBCOMMAND or?...=>ver(cr) P=Print or D=Display Firmware Downloads...=>D(CR) ENTER:L=LINE CARD (100) or P=PDI1000 (101)...L=>P(CR) FIRMWARE DOWNLOAD TABLE OF CONTENTS

19 FIRMWARE DOWNLOAD FILE: LOAD SLOT NUMBER RECORD SEGMENT NAME INDEX START END SLOTS NUMBER NUMBER PATCHED wwwwwwww aa 1 N xxxxxxxx bb 2 N yyyyyyyy cc 1 N zzzzzzzz dd 2 N RETURN CONTINUES DISPLAY...=>(CR) P=Print or D=Display Firmware Downloads...=>@(CR) SELECT COMMAND => Force Download To PDI-1000S The PDI-1000S contains a volatile memory. Every time power is removed from the PDI-1000S, the application program will have to be loaded into memory, in order for the unit to operate. The download procedure will occur automatically or can be activated using the Man/Machine (M/M) terminal. To force download the PDI-1000S using the M/M, use the following commands: SELECT COMMAND => UTIL(CR) SELECT SUBCOMMAND or?...=>ldr(cr) SELECT LOADER SUBCOMMAND or?...=>?(cr) DEFL...DEFINE LOAD NUMBER LDLC...LOAD LINE CARD RSET...RESET LINE CARD RSLC...RESTART LINE CARD FLPT...FORCE LOAD PROGRAMMABLE PORT SELECT LOADER SUBCOMMAND or?...=>flpt(cr) PROGRAMMABLE PORT NUMBER or?...=>?(cr) Enter a port number or range of ports:...=> WW.X.YY.ZZ Specify port, where WW = Cabinet number X = Shelf number YY = Card number ZZ = Offset number...=> - All ports...=> WW.X.YY.ZZ-WW.X.YY.ZZ Range of ports (lo#-hi#)...=> WW.X.YY.ZZ- Range of ports (lo#-max)...=> -WW.X.YY.ZZ Range of ports (0-hi#) PROGRAMMABLE PORT NUMBER or?...=>ww.w.yy.zz(cr) APPLICATION NAME or?...n=>?(cr) *** APPLICATION NAMES **** MKO... ADIE... MODM... AARD... MM... LPRT... OAI... 15

20 VMP... CDR... ITAP... S56... SEC... TITE... STE... 2WT... 4WT... T1... DID... DITE... OPX... DTI... BXI... LMS... EITE... MSFS... MSFM... MSFE... MSFD... MSFC... MSFT... FXL... IXL... PRIA... IDRA... PRIB... PRIC... BRI... SCS... APPLICATION NAME or?...n=>xite (X=proper ITE type)(cr) *** SYSTEM PORT: WW.X.YY.ZZ FORCE LOAD REQUEST INITIATED PROGRAMMABLE PORT NUMBER SELECT COMMAND => 16

21 CHAPTER 4 FORCED PDI-1000S DOWNLOAD 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 u. 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 Modem Pooling 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. 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 if it is the correct type of device (i.e. PDI) as defined by the circuit database. 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, by use of the circuit database, which LOAD contains the proper Modem Pooling 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 17

22 MCU Table 4-1. Condensed Download Procedure PDI-1000S Power up PDI-1000S or load is corrupted. The Modem Pooling 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 At this time the PDI-1000S is not in SERVICE. Random delay between. 3 to 30 seconds before sending an ADDRESS REQUEST to MCU. Address Response LOAD REQUEST every 30 seconds to MCU. Send message to PDI-1000S requesting SMID information (Programmable Option). Verifies SMID> Sends SET LOAD CONFIGURATION PARAMETERS message to PDI-1000S. (Programmable Option). Sends SMID information to MCU. 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. Responds to MCU "READY FOR DOWNLINE LOAD". Connects PDI to IOD/IOC port for downloading. Receives LOAD COMPLETE message from PDI-1000S. 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, or not received, 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 Modem Pooling Application Mode. 18

23 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 prevent a large number of LOAD REQUESTS from other PDI-1000S' being sent at the same time to the MCU. The delay time is calculated by using the SMID of each PDI-1000S, located on the TELARI/Intecom E. 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. 19

24 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. p. 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. q. 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 20

25 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 a M/M request (CFG/RESTART/Circuit address) 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 a Man/Machine 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 a Man/Machine 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 Man/Machine. 21

26 THIS PAGE HAS BEEN INTENTIONALLY LEFT BLANK. 22

27 CHAPTER 5 TROUBLESHOOTING 5.1 General This chapter provides maintenance and troubleshooting instructions for the PDI-1000S used in a Modem Pooling Application. 5.2 Maintenance There are no field replaceable parts in the PDI-1000S 5.3 Procedure CAUTION The cover of the PDI-1000S must NOT be removed when a problem occurs with the unit. When a problem occurs with 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 Modem Pooling Application has once operated. 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. 23

28 5.3.1 Software Approach To Troubleshooting (Modem Pooling Application) 24

29

30 5.3.2 Hardware Approach To Troubleshooting 1. Remove the PDI-1000S by disconnecting the IBX line from the RJ11 jack. 2. Install a spare PDI-1000S and connect the cable removed in step 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. 4. Verify that the PDI-1000S is operational. 5. If the problem is still present after changing out the PDI-1000S, check all wiring connections, including the wiring from the PDI-1000S (back) to the ITE backplane. Refer to the PDI-1000S Hardware Manual P/N for more information. 6. If the ADT or Modem is suspected of being bad, test the unit(s) by substitution. 7. If the problem is still present after completing step 11, refer to the maintenance manuals for the TELARI/Intecom E to correct the problem 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) 26

31 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 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 27

32 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 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: 28

33 Data Word 3: Required Action: Processor/Task: Suspected Problem: Re-DOWNLOAD PDI 1000S Peripheral Device 29

34 THIS PAGE INTENTIONALLY LEFT BLANK. 30