These fault locating instructions shall serve as a guide for servicing an ASB 150 02 telephone exchange(PBX). This document presupposes that all installation and start-of-operation instructions have been ad-hered to. This document covers only such faults (errors) as equipment malfunctions or some incorrectprogramming. When beginning start by classifying the fault type (see page 8).
Generally, when servicing a PBX a hardware fault can only be remedied by replacing the faulty hard-ware on site and the faulty unit(s) are to be returned to the supplier with a claim for compensation. Norepairs are to be done in the field.
The PBX has operation and maintenance programs installed which can be accessed via the PC-pro-gram RASC and Cordless System Manager software (CSM). These programs run on a PC that can besituated either in a remote service centre or locally next to the PBX.
The service personnel shall be familiar with the system, in particular regarding RASC and CSM withtheir possibilities, as RASC and CSM are the best fault locating aids.
1.1 Tools for fault locating
Fault locating from an operation and maintenance (O&M) centre requires a PC with RASC and CSMinstalled and a Hayes-compatible V.32bis modem.
Fault locating on site requires a (portable) PC with RASC and a V.24-cable connected to a free V.24-port. Additionally required tools are: a voltmeter (DVM), a system telephone, board extractor and a set ofscrewdrivers. As the boards are sensitive to electrostatic discharges please use a grounding wrist strapcorrectly connected to ground when handling the boards.
The Cordless System Manager software contains functions for Cordless System part regardinginitialization, system maintenance and updating, system fault finding and repair. As RASC cannot detectIC-LU boards installed in the system it is advisable to locate these boards to the right of the IC-CU_board.
The Cordless System Statistics is an extension to the Cordless System Manager. It collects andinterprets statistical information from the Cordless System. It gives an overview of the traffic load of thetotal Cordless System, load per Base Station or per portable telephone. Important data of telephonecalls are stored, for example the duration of calls, the number of hand over and errors like failed calls orportable telephones that could not be reached.
The Cordless System Manager software has a menu driven user interface. Separate text files permityou to translate and obtain the menus in the desired language.
1.2 References
1 B/XU 93:027 Uen.SAR-routine for Fault reporting and fault handling
2 EN/LZB BS 103 1197 RASC
3 LZY NB 201 01 /n Cordless System Manager Software
Before handling printed board assemblies (PBAs) service personnel shall always connect themselves toground to prevent damage caused by static discharges.
Older system versions of the PBX must be restarted (e.g. switched OFF and ON) after the replacementhas taken place. As of BP 50/250 Version 3.1 (ASB15002 R10) boards can be replaced during poweron. The board can be exchanged during operation by a board with the same type and number of individ-uals. Prior to removing the board, it can be disabled for traffic (by RASC) and the new board is put in op-eration without the need of restarting the exchange. A new board can be inserted in a free slot and putin operation. When replacing boards be careful when inserting the board in the cabinet as not to dam-age the backplane connector (e.g. bending pins due to misalignment) or to cause a short circuit on thelayer side of neighbouring boards e.g. by elevated components such as transformers, capacitors.
Note that the PBX will generate warnings to this effect and is therefore advisable to read the relevantwarning log. Also bear in mind that restarts normally generate the alarm and if automatic alarm trans-mission is active, alarms will be generated to the relevant alarm centre. This can be avoided byre-classifying the restart codes or by deactivating the alarm transmission.
The changes done to avoid alarms from being issued while servicing shall be reset after final restart hasbeen effected and the system handed over to the customer.
The procedure for replacement of boards is described below:
1 Transfer the (if any) warning log to a file in RASC if possible for later evaluation and appropriatemeasures. Make a printout of the warning log.
2 Deactivate active alarm.
3 Save configuration data on file in RASC if possible when CPU-D is to be replaced or with the aid of theCordless System Manager if the failure concerns the IC-CU_ or IC-LU.
4 Connect portable equipment LYA 30101 to protect against static electricity.
5 Replace faulty PBA.
6 Restart PBX manually (switch power off and on) or via RASC. If the PBX comprises several cabinets thecabinet containing the CPU-D_ shall be switched ON as last .
7 Empty the warning log.
8 Reset active alarm if this is required.
9 When replacing the CPU-D_ perform a cold-start in the PBX and update it with the saved configurationdata from RASC in order to restart all programmable data.
Boards with Electrostatic Sensitive Devices (ESD) are marked with a sign.
In the interest of quality and reliability of the system boards, always handle static sensitive boards
Some of the benefits ofESD protection are:-less failures/service calls-lower maintenance costs-higher customer satisfaction
Use portable equipment LYA 30101as a protection against electrostaticdischarges.
with special care. Always use a wrist strap connected to a low resistance ground e.g. providedon the cabinet.
A blocked PBA is normally unable to process traffic. The state of the board is indicated on the board'sLEDs (see under section " Indication of LEDs on board(s)" on page 10) and read outs of revision (R)-states is made via RASC where the board position is indicated (marked).See user guide for RASC-menu Maintenance-HW/SW-RP.
Blocked directory number
An individual whose directory number has been blocked cannot generate nor receive traffic. A blockeddirectory is not indicated on the LEDs of the device board. See RASC-menu CONFIGURATION.
Cold start
Cold start denotes a restart of the PBX, whereby all programmed data is erased and replaced by defaultvalues initially assigned e.g. factory).
Cold start is performed by placing a strap in the socket provided for this purpose on the front of CPU-D_(see under section " Indication of LEDs on board(s)" on page 10) and thereafter switching off and on theDC supply voltage to the cabinet containing CPU-D_. Instead of switching the PBX OFF and ON againtwo pins are available in connector field 2 on the CPU-D_ which can be short circuited by a plug to in-voke restart (refer tosection 4.8).
CSM
The Cordless System Manager is a maintenance and configuration software program for the IntegratedCordless System. A PC with CSM software installed can connect directly to a CPU-D4 on a mainte-nance port or remotely via internal modem (similar as with RASC) but as in the past it is also possible toconnect CSM directly to the IC-CU_ or via an external modem.
CPU
The central processor unit and its programs.
Device
The PBX can be considered as an interworking unit of function blocks. Such a function block is some-times called a "device".
Examples of devices are: switch, tone sender, extension, trunk, MFC-register and voice memory.
The placing of the devices on PBAs is arbitrary.
Facility
The functions of a telephone exchange are called facilities. Often a facility consists of several connectioncases. A connection case is initiated by means of a certain procedure from a telephone or other unit(equipment) connected to the exchange.
Examples of facilities are: internal call, external call, inquiry, transfer, intrusion, conference, sector pag-ing, various types of diversion, programming of function keys and abbreviated numbers.
Hot swapping
A board of the PBX can be exchanged during operation by a board of the same type and with the samenumber of individuals. The board can be disabled for traffic (by RASC) prior unplugging it and the newboard is put in operation without the need of restarting the exchange. A new board can be inserted in afree slot and put in operation.
An individual member (unit) of a group. The PBX possesses, among others, groups of extensions wherean individual can connect a telephone.
On analogue trunks each individual can connect (is connected) to a trunk.
On digital trunks several individuals share a single line (cable/interface).
Installed PBA
A PBA is correctly installed if it is physically mounted in a board position stipulated in the appropriate in-stallation instructions. A correctly installed PBA is a prerequisite for traffic.
See the guide text for RASC-menu MAINTENANCE-HW/SP-RP.
The LEDs on the board identify different board conditions. An explanation of the conditions is given un-der FAULT LOCATING.
Line network with stubs:
Extension line with extra jacks in the form of a star network. See figure below.
Line signalling diagram with line test
Several line signalling diagrams for trunks include a line test that is done for both outgoing and incomingcalls. These tests are described in RASC, RASC-menu CONFIGURATION-TRUNKS.
Link supervision
Digital trunks are supervised by the exchange and the state conditions, errors on the digital link to thepublic exchange are monitored. The monitoring data can be read out via RASC-menu maintenance-sys-tem-link supervisor and stored in a file or printed out.
Minimum system size
A minimum system comprises one cabinet equipped a CPU-D_ and either one ELU-D, ELU-C or ELU-A.
Power supply
Transformers, battery chargers, batteries and appurtenant cables are all included in the concept "Powersupply".
Programmable parameters
The PBX possesses a considerable number of programmable parameters, which help O&M-personnelto adapt the function of the PBX to customer requirements. The majority of facilities and individuals canbe programmed. See RASC-menu CONFIGURATION and the Cordless System Manager Software.
PBXAlthough with appropriate termination this
connected to the BTU-B.
This configuration must never beNote:used for digital telephone extension linesconnected to boards like ELU-D and ELU-C.
Each warning code is described in RASC and recommended measures are offered.See item Warning below.
Remote SW upgrading
The system software can be downloaded from a remote maintenance centre. Setting a certain time anddate automatically loads the new software into the system non volatile memory and re-starts the ex-change.
RP (Regional Processor)
The control system of the PBX is handled by a central processor and a number of regional processors.A typical task for an RP is to handle the hardware check on the individuals on a PBA.
Update board position
The database contains, among other things, relevant data for all board (PBA) positions in the PBX. Thedatabase contains also details about the type of PBA that should be installed.
The update means that the database is adapted to physical reality. An update is required in conjunctionwith a configuration change of the PBX, e.g. on expansion with new PBAs, on removal of PBAs andwhen a PBA is replaced by a different type of PBA.
See RASC-menu Maintenance-HW/SW-RP.
Warm start
Restart of a PBX with no cold start strap installed. This is the normal procedure in conjunction with pow-er-up or controlled restart via RASC-menu Maintenance-log-reset.
All programmed data is retained.
Warning
The control system of the PBX is structured so that warnings are generated when abnormal situationsoccur. The warnings can be read out by O&M-personnel and also personnel who have access to thecontrol system's source code.
Warnings that are directed to O&M-personnel are complemented with a recommended measure.
Warnings without recommended measures shall be interpreted by persons with access to the controlsystem's source code.
2.1 General checks on start and completion of service
Start by identifying the type of fault by collecting as much information about the fault as possible, fromthe relevant customer, then (if possible) connect RASC and check the configuration of the PBX with re-gard to revision states (see point 4.15, Translation and verification of revision states) as soon as this ispossible.
The majority of faults can probably be eliminated from the O&M-centre by means of reprogramming orvia telephone contact with the respective customer (operational faults).
Consider to which one of the following main fault categories best describes your fault:
Use the following flow charts describing a methodical path for checks and tests to help locate andeliminate the fault. When the flow charts lead to a possible cause, this is indicated by a statement givingthe name of the defective part or the cause of the problem, e.g. a defective BTU-_ board is indicated bythe statement `BTU-_ board defect'. When there are more possible items, they are listed in order ofdecreasing probability.
Number TYPE OF FAULT Go to:
2.2 Indication of LEDs on board(s) page 10
2.3 No call procedures possible in the PBX page 15
2.4 Individual board not working page 16
2.5 A single individual does not work at all, e.g. an extension is "dead".The individual is not able to either initiate or receive calls
page 17
2.6 Digital trunk (BTU-D) does not work at all page 19
2.7 Individual malfunctions partly, intermittent faults, e.g. one connection case is successfuland another fails. The fault can be traced to an individual
page 20
2.8 A certain facility never functions. A certain facility is inaccessible, e.g. intrusion is neverpossible
page 21
2.9 A certain facility functions intermittently, that is a certain connection case succeeds on oneoccasion, not on another, and where the fault cannot be traced to an individual
page 22
2.10 An individual has no access to a certain facility page 22
2.11 Transmission fault (one way speech, line scratching, etc.) page 23
This symbol contains a question with two or three possibleanswers being YES (Y), NO (N) or text.Inputs are points 1 or 4 and outputs are points 2,3 or 4.
This symbol contains an instructionfor the maintenance engineer.
This symbol is used as: starting point for a procedure (e.g. START),as a reference to another flowchart, to end a procedure (END).
This symbol is used as a reference point within a flowchart. Thiscan be to a part of the flowchart on another page (e.g. B or C) or ata part of the flowchart on the same page (e.g.1).
Lines indicate the normal flow. The normal flow is always "down"
Arrows are used to indicate flows going "up" or left.
and "to the right" and in exceptional cases "to the left".
The front edge of all PBAs in the PBX are equipped with LEDs of different colours. Their purpose andsignalling cadence is described in the following. On system restart all LEDs are ON and go OFF duringstart-up sequence. Depending on their function the LEDs are in different positions on the front edge.
CPU-D_ RPs on BTU-_,ELU-_, IC-CU etc.
Connection field 2
Connection field 4
Connection field 6
1st pair (generally RP)
LEDs controlled
LEDs controlledby CP
Yellow LED flashes in different ca-dences during start sequence and isoff during normal operating.
by relevant RP
cold start strapPosition for
2nd pair (e.g. DSPs
3rd pair
4th pair
Not mountedon all boards
on BTU-D or REG)
Red LED is lit if CP is restartedThe LED can be ON for up to 2 min. duringupgrading or only 1 to 5 seconds duringstart-up conditions.
Go to: c
Yellow LED flashes in different cadencesduring start sequence and is off duringnormal operation go to page 11.Green LED that is directly connected toalarm log e.g.if warnings occur these war-ning codes are stored in the warning logand this LED is turned on go to page 11.
Red LED is ON if cold start strap(located below) is inserted go to page 11.
Red LED lights up during power on se-quence . Check if PROMS areplaced and if no yellow and green LEDsflashes. For LED flashing proceduresduring upgrading refer to MAINTENANCEINSTRUCTION (1541-ASB 150 02).
Go to: a
on CPU-D
cold start strapPosition for
on CPU-D_
Yellow and green LEDs indicating start,faults or active ports. During remote up-grading the number of flashes indicatewhich FLASH program memory is beingre-written go to page 11For LED flashing procedures during up-grading refer to MAINTENANCEINSTRUCTION (1541-ASB 150 02).For LEDs on Integrated Cordless boardsgo to page 11
red RP disconnects PCMbus and signallinginterface from backplane
This can occur if the CP on the CPU is restarted or a board failure isdetected by the RP. Check if it concerns just one or more board(s). Awatchdog reset on the board could cause a board restart. Systemsupervision will invoke a system restart if major faults occur. If LED iscontinuously ON check if the yellow and green LEDs flash otherwise the RPis not working
yellow This LED indicatesboard start-up or if theboard (individual) isblocked.
This condition is normal for a start-up sequence indicating initialisation orrunning self test. If this LED is ON during operation, this indicates blockingof one or more individual(s). The proper action is to check the wiring and ifthe connected equipment is operational (check it’s alarm indication)
green Port is active This indicates normal system operation and one port is active e.g. RASCLEDs inconnectionfield 4
red CP is reset This occurs during remote upgrading of the SW or if the watchdog detectsa fault. If LED is continuously on the FLASH PROMS could be re-written(refer to RP LED conditions)
yellow Flashes during start-up of CP
This LED flashes during start-up of the CP and is OFF during normaloperation
green Alarm log indication If this LED is ON, check the logged errors, save them to disk and deletethem in the log. Check in which intervals the system logs errors and ifpossible correct the cause
LEDs inconnectionfield 6
red Cold start strap active This LED turns on if the cold start strap below is inserted. This is a warningthat if this strap is not removed during operation the system will start withinitial values on restart. This occurs even if the mains fails intermittently! Allcustomer data will be lost in this case.
LED Correctionred yellow green
ON Communication to CPU-D_ terminated. Board failure is detected by the RP.OFF ON ON PROM error (invalid checksum)OFF ON Flash (4 Hz) RAM errorOFF ON 0,5s ON/4,5s OFF FPGAs not loadedOFF ON 0,5s ON/0,5s OFF/
0,5s ON/3,5s OFFEPIC initialization fault
OFF ON 0,5s ON/0,5s OFF/0,5s ON/0,5s OFF/0,5s ON/2,5s OFF
Initialization fault of process data
OFF ON 1s ON/1s OFF Invalid FECU connectedred SPU LED on
(see InstallationInstruction fordetails)
This LED flashes if the board’s SPU RP detects a fault. To correct the faultcheck entries in the CSM and follow suitable solution given.Flashing -> CPU fail, ON steady -> warning entries not read.
red CLU LED on(see InstallationInstruction fordetails)
This LED is turned on if the board’s CLU RP detects a fault and/or if a basestation is not initialized. Correct the fault, check entries in the CSM and followsuitable solution given.
LED Condition CorrectionLEDs inconnectionfield 2(upperpart)
red RP disconnects PCMbus and signallinginterface from backplane
This can occur if the CP on the CPU is restarted or a board failure isdetected by the RP. Check if it concerns just one or more board(s). Awatchdog reset on the board could cause a board restart. Systemsupervision will invoke a system restart if major faults occur. If LED iscontinuously ON check if the yellow and green LEDs flash, otherwisethe RP is not working.
yellow This LED indicates ifthe board is in start-upprocedure or if theboard (individual) isblocked.
This condition is normal for a start-up sequence indicating initialisationor running self test. If this LED is ON during operation, this indicatesblocking of one or more individual(s). The proper action is to check thewiring and if the connected equipment is operational (check it’s alarmindication).
green Individual is active This indicates normal system operation and at least one e.g. extension(individual) is active on the board.
LEDs inconnectionfield 2(lowerpart)
yellow Register is blocked This indicates that the register function on the board is blocked e.g. onBTU-D or VMU-HD.
green Register is active This indicates normal system operation. This register function is activeon the board e.g. on BTU-D or VMU-HD.
1 (power up) ON OFF RESTART Lights up immediately for about 20 seconds
ON ON PROM-fault Start up is interrupted if a fault is discovered duringself test.
ON R-FL1) RAM-fault
S-FL2) OFF WAITEntered after restart following fault-free self testand relevant RP is initiated. Waits for start orderfrom CPU.
R-FL1) OFF STARTEntered in state wait for receipt of start order fromCU. RP reports data to CPU, e.g. type of board
ON OFF BLOCKEDOccurs when database does not match withreported data from RP orif at least one individual is blocked4)
R-FL1) R-FL1) HD-fault
A-FL3)A-FL3)
OFF OFF NORMAL
OFF ON TRAFFIC Traffic on least one individual
Normal idle state that is entered after PBX has beenstarted. No traffic exists on relevant board/device
Hard disk is missing/not installed
DSP-fault VMU-HD only: DSP not loaded
2
3
4 (operation)
FAULT
FAULTFAULT
FAULT
Startsequenceaborted
Condition in case of database mismatchR-FL1) OFFData base-fault
1) Rapid Flash (Frequency=4Hz).2) Slow Flash (100 ms ON and 900 ms OFF).
4) Applies only for analogue and digital trunks. Individually blocked trunks are indicated in configuration data and not in RASC-menu Maintenance-HW/SW-RP.
3) Alternate Rapid Flash (Frequency=4Hz). Green and yellow LEDs toggle.
2.3 Flow chart: No possibility to make calls in PBX
Remove board after board incabinet and measure voltageson the backplane. Replaceboard causing the wrong volta-ge(s). If the boards are not thecause replace the back plane.
Verify that the exchange issupplied with power. Check48VDC/36VAC supply, thecabling and if the voltagesare present on the back-plane. (see point 4.7).
Remove front coveron cabinet containingthe CPU-D.
Insert cold start strap and remove itimmediately. Does the red LED(above cold start strap) light indica-ting a cold start and extinguisheswhen strap is removed.
Check all revisionstates(see point 4.15).
Check available (free) re-sources (see point 4.11).
Update to latestrevision state.
Configure mini-PBXcomprising one cabinetand CPU-D.Connect RASC.
Continue by increasing sizeof PBX with one deviceboard at a time. Replaceboards that malfunction.
Replace CPU-Dand restart PBX.
START
Y
N
All LEDsextinguished?
Y
N
Correct?
Connect to RASC.Verify proper commu-nication parameters
Turns off after No speech channels available in IC-CU, IC-LU orBase Stations. Try again later or in anotherlocation. If problem persists portable isdefect.
programmed Program portable General Alarm?N
Y
Check that associated extensionnumber is registered in PABX and
On completion of service disconnect RASC and check the warning log for entries. If this is the caseadopt the recommended measure(s). If no further measures can be taken note the logs (or printout ifpossible) and contact your local support facility.
Remaining faults are to be reported (see point 4.9, “Fault reporting”.)
If you cannot fix the problem at the moment start up the exchange again and give the customer instruc-tions how to cope with malfunctions, conclude by making a printout of the warning log and resetting it.Disconnect RASC and place the cover on the exchange.
Dial tone present?N
Y
Dial tone present?
Press the hook key onthe new portable
BC
Delete old portable
- Error in PBX
from system andinitialize new portable
with same PUN
- replace relevant IC-CU, IC-LU board- re-initialize old portable with
The digital system telephones have a built-in self test facility that can be initiated by pressing three keyssimultaneously for three seconds. Self test can only be initiated in idle state. Initiate self test and verifythat the telephone functions properly. If not replace the telephone.
If there is a voice communication problem also check the connection of the telephone handset to the tel-ephone and test using another handset if the original handset is suspected to be faulty.
3.2 Check RASC connection
When encountering communication failures to RASC verify proper settings for the V.24-port and the pro-grammable parameters for the built-in modem and corresponding parameters for RASC on the PC. Formore information consult document EN/LZB BS 103 1197 RASC Uen, "RASC".
Telephonetype
Keys for initiation ofself test
Result of self test ok
DBC 199 R-button, * and 4 LED glows steadily
DBC 201 C,*,4 for one second All LEDs light up
DBC 202 C,*,4 for one second ’Self test ok’ on display
DBC 203 C,*,4 for one second ’Self test ok’ on display
DBC 211 C,*,4 for one second All LEDs light up
DBC 212 C,*,4 for one second ’Self test ok’ on display
DBC 213 C,*,4 for one second ’Self test ok’ on display
DBC 214 C,*,4 for one second ’Self test ok’ on display
DBC 601 Transfer , * and 4 No LEDs shall flash
DBC 632 Transfer , * and 4 ’Self test ok’ on display
DBC 662 Transfer , * and 4 ’Self test ok’ on display
DBC 663 Bypass , * and 4 ’Self test ok’ on display
The Cordless System Manager software installed on a PC requires a connection to the maintenanceport on the Cordless System Central Unit (IC-CU_) or to the CPU-D4, either to the maintenance port orvia modem. Off-line menus include functions that do not require this connection. Go to the directory inwhich the Cordless System software has been installed. In most cases, you can start the Cordless Sys-tem software by just typing DCT <Enter>.
Typing DCT /B<bit rate>. Example: DCT /B9600. This option allows you to change the bit rate with theDesk Charger/Programmer. This may be useful when you want to down-load software to portables witha higher (non-default) bit rate. Valid bit rates are: 4800 (default), 9600, 19200 and 38400. Consult yourPC documentation to check which bit rates are supported for the COM2 port.
When the program has correctly started-up the welcome menu is displayed.
If there is no communication with the Cordless System the message ’No connection with DCT1800.Start Off-line program? Y (Yes/No)’ is displayed. By pressing the <Enter> key the Off-line program isstarted. If you want the connection with the Cordless System you must now check the connectionbetween the PC and the Cordless System and then select N(o). If communication has not beenestablished yet, the following message ’Waiting for DCT1800 response...’ is displayed. If there is still nocommunication with the DCT1800 system the message ’No connection with DCT1800. Do you wish tocontinue? (Yes/No)’ is displayed.
When the communication is established the message ’Loading data from DCT1800, please wait...’ isdisplayed.
If the Cordless System has been initialized before with a version of the Cordless System Manager olderthan revision R6, the message ’WARNING: SPU-S parameters not initialized yet. <Enter>’ is displayed.If so, do not forget to execute the ’Restore country data’ command.
3.4 Check on service display DT 288, DT 360, DT 368
The portable can be switched to service display mode (type DT 310 does not support this function) dis-playing information regarding the radio interface like BS number, carrier, time slot number, RSSI etc.
When the service display is active, calls cannot be made and incoming calls will terminate the servicedisplay mode. To make this display visible while calling, first setup the call and then, via the `R(inquiry)'menu, access the service display menu.
Note: Activating the service display reduces the normal functioning of the portable. It is therefore recom-mended only to use this facility in exceptional cases, e.g. when service requires such.
3.4.1 Activating Service Display Mode DT 360 (A-protocol)
1 Switch off portable
2 Switch on portable with special code: (Press the 3 keys
simultaneously for more than 1 second).
A `DCA-Service' menu will appear in the Preference menu. This menu can be removed by switching-offthe portable followed by a normal switch-on.
3 Access Preferences menu 2 x down, yes.
4 Access DCA-Service menu 1 x up, yes.
5 Access wanted service display option.
The DCA-Service menu has six options available to display different types of information.
Explanation of Service Displays
Data is always displayed in hexadecimal numbers. The Base Station number relates to the physical con-nection in the central Unit.
Note: A portable is always blind for the two adjacent time slots. For example, a portable is locked on aBase Station on TS 5. If it approaches a Base Station that has only one active channel (traffic or bea-con) on TS 4 or TS 6, the portable will not see that Base Station. The display remains unchanged untilthe current channel or the channel of the second Base Station changes. Consider this when using themenu's below.
Link Info
The Link Info option can be used for site surveys and commissioning of the system. All information re-garding the traffic/beacon channel to which the portable is locked, is visible. The signal strength theoret-ically varies between /00 and /3F. In practice, values will lie between /07 and /37, of which /07 meansnoise, /37 means optimum quality. Typical values are /20 .. /29.
All - FP + RSSI
8 2+ ON+ /MUTE
CS Fp SsQuLiH9 09 2A20-4
C : Carrier (A..J)S : Time Slot number (0..9,A, B)Fp : Base Station number (Fixed Part)Ss : Signal strength (RSSI)Qu : Quality of the signal (RQI)Li : Link type (0 = beacon, 4 = traffic)
This menu can be used to check the traffic that is offered on a certain location. It shows the number ofBase Stations within reach of the portable in order of their respective signal strength. The portable dis-plays a list of up to 7 different Base Stations, the maximum a portable can see.
FP - Info
This menu allows scrolling through the Base Stations (/00../FF) list. The default Base Station is the firstBase Station mentioned in the All-FP+RSSI display; the one with the highest signal strength. By press-ing `down/up', you can display other Base Stations. When a Base Station is not in the portable list, thedisplay remains blank. If it is, the display shows the data as specified in the lines above. `N' may changeduring the display if another Base Station from the portable list is getting a higher/lower signal strengththan the one currently displayed.
Channel Info
Not applicable to maintenance
Time Slots
Not applicable to maintenance
Select PUN
This menu is useful for testing purposes when more systems cover the same area. It allows a forced se-lection of one system on a portable that is programmed for both systems. By selecting a different PUNan engineer can test Base Stations of different systems on the same spot without having to re-initializehis portable.
When `A' is selected, the portable will automatically select systems for which it has access rights. Afterswitching on, the portable is always set to automatic selection.
FpSsFpSsFpSs092A1518XX--
Fp : Base Station numberSs : Signal strength of its best channelXX : No more Base Station number detected-- : No channel detected
N Fp Ss CB D0 09 2A 11 0
N : Number of Base Stations in list (0..6), see previous displayFp : Base Station numberSs : Signal strength of its best channelC : Number of channels in use on Base StationB : Number of channels in use on portable with current Base Station
D : Number of time slots disabled on Base Station (max. 10 seconds)
: 0 = no channels, portable locked on other Base Station: 1 = beacon or traffic: 2 = handover occurring
3.4.2 Activating Service Display Mode DT 368 (GAP-protocol)
1 Switch off portable
2 Switch on portable with special code: (Press the 3 keys
simultaneously for more than 1 second).
A ‘LinkInfo’ menu can then be accessed via the Info - DCA Service menu. This menu cannot be ac-cessed after a normal switch-on.
Access Info - DCA Service menu.
Access Linkinfo menu.
Note: It is also possible to access the DCA Service menu when the phone is ‘off-hook’ ie during a call.
The DCA-Service menu has two options available to display different types of information.
Link Info
The link info menu has two display options which can be selected by pressing either up or down. The fol-lowing display is entered by pressing up:
The following display is entered by pressing down:
The Link Info option can be used for site surveys and commissioning of the system. All information re-garding the traffic/beacon channel to which the portable is locked, is visible. The signal strength theoret-ically varies between /00 and /3F. In practice, values will lie between /07 and /37, of which /07 meansnoise, /37 means optimum quality. Typical values are /20 .. /29.
3.4.3 Activating Service Display Mode DT 288 (GAP-protocol)
1 Switch portable: ON
2 Press:
3 Press: one after the other
until you reach DevServices . Here you will find the Link Info, the FP Info, the Display Tests, Hardwareconditions.
8 2+ ON+ /MUTE
PARK10002140140
: PARK (Portable Access Rights Key) is displayed: The PARK number without the first two digits and the checksum: PARK 3110002140140-4 is represented as 10002140140: Signal strength (RSSI)
Upper lineLower line
CS Rp SsQu TH9 09 2A20 4
C : Carrier (A..J)S : Time Slot number (0..9,A, B)Rp : Base Station number (Fixed Part)Ss : Signal strength (RSSI)Qu : Quality of the signal (RQI)T : Link type (0 = beacon, 4 = traffic)
down until Information appears then press YESdown until Total calls appears then press YES
When checking configuration data for trunks verify the following:
• That the selected line signalling diagram agrees with the public network for the relevant trunk and thecountry specific session is loaded.
• That the country specific RASC session is loaded.
• This can vary depending on the type of public exchange which type of trunk is connected.
• Signalling to public exchange; decadic, DTMF, MFC/MFE or ISDN.
• Supervision times.
3.6 Voltage measurements
System voltages can be measured either using the RASC tool (menu systems- ad-converters) or direct-ly on the backplane. As it is possible to cause a short on the lines during measurement all boards in thecabinet should be removed. Test points on the backplane are accessible only if the CPU-D_ in position 0is removed (refer to 1531-BDV11308 for details).
3.7 Check on power supply
Check the secondary voltage of the transformer(~36VAC), generally power supply (48VDC) and batterycharger regarding connection to mains and functioning fuses. Check (if installed) the battery condition ofthe power back-up. Replace (if any) faulty units. The voltages (see drawing below) can be verified on thebackplane. As there is always the risk of short circuits these measurements should be done when allboards have been removed.
Checks on the line network can vary in scope depending on the configuration of the line network andtype of connection. See the following schematic diagram and use the exclusion method by testing in theorder stated.
3.10 Check on programmable parameters for facilities
For facilities and various connection cases there exist a number of programmable parameters that needto be programmed correctly for the facility to function. See "Facilities" in RASC.
resetpins
There are several conditions needing a restart of the PBX. Inthis case there are two ways of restarting the system:
• Switch off the power supply either by disconnectingfrom mains (unplug, switch off the supply lines) orswitch off the exchange using the switch at the bottomof the cabinet.
• Make a short between the two pins(A32 and C32) on the connector at the front of theCPU-D. Be careful when shorting these two pins byusing a plug with a wired connection or a jumper.
26
28
30
32
A C
CPU-D_
MDF
MDF
Jack
PBX
1. The first MDF to which the PBX is connected. Disconnect thenetwork below this point and test by connecting a telephone orother unit here.
2. Test with telephone or other unit here.
3. Interim MDF (none, one or more). Disconnect the network be-low this point and test by connecting a telephone or other unit.
In addition there is a traffic group matrix that states the authorisation for different connection cases. Thetraffic group matrix can be used to verify connection paths, e.g. A may call B but B may not call A.
3.11 Check on resources
Free and utilised resources are specified in the RASC-menu Maintenance-system-resources. Here arestated the number of free PCM-channels, number of free references on VMU, etc. Only the number offree PCM-channels and free references on the VMU-board are of interest. Other information is usedonly during system testing in conjunction with new development. With the help of the stated informationit is possible to determine whether the PBX possesses sufficient capacity.
3.12 Fault checks / correction of intermittent faults
Intermittent faults constitute a considerable problem as it is difficult to verify whether remedial measureseliminated the fault. It is essential therefore to make great efforts to identify in which circumstances thefault occurs. If one is fully or partly successful then one has acquired a possibility of verifying whetherthe fault really has been eliminated by attempting to repeat the circumstances which gave rise to thefault. If this is not possible the PBX should be checked at suitable time intervals. This is often a matter ofjudgement and varies from case to case.
The following part of the fault checking relates to the Cordless system with a table describing the class,most probable reason and service class number.
• Column 1 - Fault numbers in sequence
• Column 2 - Service class:
• Class 1 Faults in this class mean that communication with a board or peripheral is lost. In most casesthere is a physical reason. Check on proper connection. Execute a Replace Board by the Systemmanager-Control menu and check that the fault disappears. If not successful, proceed to class 3.
• Class 2 Faults in this class can be minor faults that can be cleared by a board reset. Execute a ReplaceBoard by the System manager-Control menu and check that the fault disappears. If not successful,proceed to class 3.
• Class 3 Faults in this class are in most cases fatal errors that require board replacement. It is convenientto ensure that the fault is a hard fault by executing a Replace Board and checking if the fault disappears.If not successful, execute the Replace Board command from the System manager-Control menu andreplace the board by a spare board. The new board is automatically tested and taken into service. If thefault persists, call your local supplier for service.
• Column 3 - Fault threshold This column indicates the number of times a fault may occur intermittently. Thismeans that after detection of the fault, the fault does not reappear when tested, see paragraph 2.2. If thisintermittent occurrence exceeds its threshold number within 24 hours, a status code S (service) will be writtenin the Fault Table, a fault report is written in the Service Table and the General Alarm is activated. The countervalues are halved every 24 hours. Threshold value 99 is equivalent to infinite.
• Column 4 - Fault description This column gives a brief description of the fault that has occurred.
1 2 2 Unexpected message/primitive Message received but not within specified time
2 1 99 Board/CPU communication error or time out. Message corrupted or not received
3 2 99 Threshold Fault counter exceeded
4 3 1 Board controller ROM error
5 3 1 Board controller RAM error
6 3 2 Internal loop back error
7 2 5 Peripheral state error- state of periph. differs from state listed in CPU data base
8 1 6 Base Station not present - wiring fault or power lost
9 3 2 Peripheral ROM error
10 3 2 Peripheral RAM error
11 2 99 Peripheral status unknown. Two simultaneous faults: status can not be obtained
12/13 2 99 Board status unknown. No communication with board: status can not be obtained
14 2 5 Peripheral communication error or time out. Message corrupted or not received
15 2 2 Board signalling link was cut. When a board is not polled, it resets itself and aftercommunication has recovered it sends this message to CPU
16 1 10 Board controller poll response error
17 3 99 CPU main processor RAM error
18 3 99 CPU main processor ROM error
19 3 99 CPU EEPROM error
20 2 1 CPU real time clock failure
21 3 2 CPU-poll processor (8031) RAM error
22 3 2 CPU-poll processor (8031) ROM error
23 1 2 CPU-poll processor communication error
26 2 5 Internal buffer overflow
27 2 99 Board controller watchdog reset
28 1 2 HSCX error. Serial communication controller on CPU of signalling high way
29 3 99 Signalling high way down. No communication between CPU and all other boards
33 1 1 Initialization procedure not successful. Due to e.g.: no communication with board
34 1 99 Portable related circuit not present. DTU-channel.
39 PC communication error. When statistics run, logging is stopped. Statistics must beset ON again
50 1 Minimum configuration error
51 2 Subject unreliable. Fault not continuously present
52 Subject could not be tested after maintenance action due to a coincidence-Subjectmust be verified if operational. It may be ’AVE’ but not working. Reset subject
• Fault 17 ... 26, 28, 29 CPU faults. Replacement of the CPU requires up loading of its data to PC first. If notpossible any more, down load the new CPU with the most recent up load file ondisk.
• Fault 35, 36, 37 These faults may disappear automatically. The DTU sends a message to T&M andT&M clears the fault status: L1 = AVE and L2 = AVE. However, the Service Errormessage remains and the General Alarm as well. They must be cleared by 'Clear Service'.
• Fault 52 Maintenance personnel must verify if the subject is operational or not. It may occurthat a subject is given `AVE', but not working any more. If not working, reset thesubject and wait for new fault.
3.13 Fault reporting
Fault reporting, in accordance with current SAR-routines, shall be made to the support instance and thewarning log shall be enclosed either as printout or on diskette. To enable suitable action it is essentialthat the correct information is provided describing in the best possible way how the fault was initiated(sequences), under which circumstances (state) it occurred (traffic situation and time), how the fault re-vealed itself and whether it was repeatable. Also state the PBX configuration, which can be obtained byreading out the revision states (see point 4.15, "Translation and verification of revision states").
3.14 Update of board positions
Read the revision states of the hardware positions, RASC-menu Maintenance-HW/SW-RP.
Highlight the relevant row with the cursor and update the board. All programmable data is assigned de-fault values. For extensions and trunks it is also necessary to assign all individuals a telephone number.Normally it should be possible to load configuration data from RASC provided back-up exists.
3.15 Translation and verification of revision states
Ericsson identifies all products by means of a product number and revision state.
An ASB 150 02 exchange is built-up from several sub-products, each with its product number and revi-sion state. Via RASC-menu Maintenance-HW/SW-CPU it is possible to read the product number and re-vision state of the central program's PROM-set (LZY), PROM (RYS) and linkage unit (CXC).
Via RASC-menu Maintenance-HW/SW-RP it is possible to read the product number and revision stateof three different regional control programs per printed circuit board position. The same RASC-menualso permits the device board's product number to be read, however the revision state cannot be readdirectly although it can be determined with the help of the information in columns PCB and PS.
• PCB contains a digit that indicates the R-state of the PBA's printed circuit board.
• PS code contains a digit that can be related to a modification of the PBA that took place subsequent tothe manufacture of the PBA.
In the service advice is stated, for each board's (product number) revision state, the applicable PROM-set (RYS), PS-code and PCB-code.
Note: that there also exist prerequisites stipulating which revision states for which products maybe combined.
The BusinessPhone remote upgrading system is used to upgrade the current software running in anASB 150 02 exchange to a different or enhanced software version without the need of exchanging thePROMs on the CPU-D4. The software that should be upgraded to, must be based on the identical languageversion that is already installed in the system. If the language shall be changed, the system must beupgraded with the complete software in the new language.
Remote upgrading has the following prerequisites on the PBX side:
CPU-D4 equipped with FLASHPROMS and a FECU (KDU BS 130 06/_ or KDU BS 130 07/_)has to be installed. For details on FLASHPROMS refer to Requirements of the CPU-D4 on page 3.
On the maintenance side a PC is necessary with hardware requirements as mentioned in chapter 1.2.This PC can be connected to the CPU-D4 directly (V.24) or remotely. The PC requires an operating systemsuch as MS Win95 or MS WinNT 4.0. The terminal application program, provided by the operating system,such as HyperTerminal, Telix etc. manages the communication between PC and the CPU-D4.
The terminal program is used to load the new ASB 150 02 software upgrade file created by the "UPGRADEPROGRAM" into the CPU-D4. In order to keep the transmission time as short as possible the "UPGRADEPROGRAM" creates only a file comprising the differences between the existing software in the exchangeand the new software to which it should be upgraded to. Optionally a full software upgrade version can becreated too.
The basic principle of upgrading is that the CPU-D4, equipped with two separate program memory areasreceives an upgrade software and stores the changes in a temporary storage area, called the upgradeFLASH that is controlled by the RP. This upgrade software, called output file, is created by the "UPGRADEPROGRAM" chkdiff.exe, then transferred and stored directly into the upgrade FLASH. This file has to besent as a text file. The PBX continues operating while the program is loaded remotely or locally into theCPU-D4 upgrade FLASH as the CP operates on the program stored in the program memory area calledactive FLASH. The time to upgrade to the new software can be selected in a menu. As soon as the upgradetime is reached the CPU-D4 is automatically restarted.
During the restart several actions are performed. The content of the upgrade FLASH is verified. The basedata of the active FLASH is merged with the data stored in the upgrade FLASH. After final verification thedata of the upgrade FLASH is copied into the active FLASH if ordered. This process results in a delay ofthe start-up but is indicated by flashing LEDs (see page 16). Optionally no upgrade can be ordered andthe upgrade information is just stored in the upgrade FLASH. This is useful if an upgrade is required at alater date. In all cases it is necessary to create the output file based on the current system software versionand the in comparison to system software version that is to be upgraded to.
1.2 Requirements
HW: (main requirements)
486DX2 66MHz
at least 16 MB system memory
15MB free hard disk space
free COM port capable of up to 9,6 kBaud communication speed
SW: The PC operating system can be either Microsoft Win95 andWinNT 4.0.
The terminal application is used to build up the connection to the exchange. As an example forHyperTerminal the settings below are required.
Settings: select COM 1 or COM2data rate: 9600 Baudparity check OFFdata bits 8stop bit 1flow control XON/XOFF
ASCII sending - do not select echo typed characters locally- do not select send line ends with line feeds
1.3 Requirements of the CPU-D4
The firmware on the CPU-D4 must be at least RYS 102 533 Version R2A or higher. Verify that the FLASHPROMs are mounted on the CPU-D4. RASC displays this information in the RP menu such as:
Before starting refer to the hardware requirements mentioned before. The binary software files and theupgrading program chkdiff.exe are available on the support server at SEA.
Note: Chkdiff.exe requires a 32-bit operating system such as MS-Win95 and MS-WinNT4.0.
All registered users can download these files. Download the ASB15002 SW file for the required releasefrom the server. Copy the upgrade program and the ASB 150 02 software files into a dedicated directory.These files are compressed and after extraction the following binary ASB15002 files are available e.g. aslisted below:
Check in the read me file the version of the available program and compare it with the program versioninstalled in the PBX to be updated. All three binary files are needed to install a complete SW upgrade.
1.5 Creating the Output File
The first step is to create an output file that shall be loaded into the exchange. Refer to the read me filegiving details of the version of the software to be upgraded to and compare it with the program versioninstalled in the PBX to be updated. It is important to know your market version to perform the upgrade fordetails refer to the ORDERING INFORMATION (131 62-1x/ASB150 02) or the index of the software e.g.LZY 203 2230/x. The x states the market version needed to create the upload file.
Execute the 32 bit console application program chkdiff.exe in a DOS prompt. The program chkdiff.exegenerates the file which is used for uploading the new SW-version. This application verifies which partsof the SW has been changed, determines the differences between the two SW-versions and creates anoutput file (*.txt). The file is a specially coded (containing line number, checksum, ...) but must not beopened by any tool (e.g. editor) as in this case the data may be corrupted.
• readme.txt This file contains information on the software version
• 101RA21.me These files are necessary for the upgrading program
• A11R1AA.bin
• A21R1A.bin and These files are extracted from the current ASB15002 SW
• A31R1A.bin. . . . . zip files: They are available on the FTP site.
The file denominations used for remote upgrading are explained in the following:
For this procedure it is very important to have the correct link version. This could present a problem inexisting (running) SW-versions in a PBX. To find this value enter RASC. Menu maintenance -> HW/SW-> CPU. Here the LZY 203 223x/x R1A the highest link version number is the valid number to be used andentered in the field of the software version currently in the PXB.
The link version can be read out using RASC. Check the LZY information with link version of the PROMS.The highest value is the correct link version or by reading the information in the PROM me-file.
After executing chkdiff.exe and select whether a standard or full upgrade is needed and enter the dataaccordingly.
This standard upgrade is the common upgrade for the ASB 150 02 exchange. Choosing this option keepsthe transmission time as short as possible. The chkdiff.exe creates a file comprising only the differencesbetween the existing software in the exchange and the new software to which it should be upgraded to.
Enter the requested values in the fields above. The operation is terminated stating that the output filee.g. r10 1 A—r10 1 B.txt was generated.
As an alternative it is possible to execute the chkdiff.exe and add the upgrading parameters in the commandline such as:
E:\>chkdiffAA SSSS BBBB 1 5555 00 00 22
A A S S B B 11 5 5 0 0 0 0 2 2A A S B B 1 1 5 0 0 0 0 2 2A A S B B 1 1 5 0 0 0 0 2AAAAAA SSSS BBBB 1 1 555 0 0 0 0 2A A S B B 1 5 0 0 0 0 2A A S B B 1 5 0 0 0 0 2A A S S B B 1 5 5 0 0 0 0 2 2A A SSSS BBBB 1 555 00 00 2222
Welcome to the remote update file generation menu:Please insert the release , upgrading shall be based on: 10 (e.g. if R10 is selected)Please insert the market , upgrading shall be based on: 1 (e.g. if STANDARD is selected)Please insert the SW version ,upgrading shall be based on: A (select version)
Base information were checked successfully
Please insert the wanted upgrading release : 10 (e.g. if R10 is selected)Please insert the wanted market version: 1 (e.g. if STANDARD is selected)Please insert the upgrading version: B (select version)
Upgrade information checked successfullyBinary file names verified successfullyChecking maps:map number: 0 number of records different 0004
After entering the data this information issent back to verify operation. If an erroris encoutered retry with correct data.
chkdiff∩r10∩1∩A∩r10∩1∩B for standard upgrade or chkdiff∩r10∩1∩B for full upgrade.
OLD NEW
e.g.
NEW
The symbol ∩ denotes an empty space in the command line.
If the remote PBX has a software that requires a full upgrade then enter the letter "b". In this case thechkdiff.exe program executes a full software upgrade file. This results in the largest file size and thereforetakes the longest time to transmit.
Enter the requested values in the fields above. The operation is terminated stating that the output filee.g. Blank_r101B.txt was generated.
E:\>chkdiff
AA SSSS BBBB 1 5555 00 00 22A A S S B B 11 5 5 0 0 0 0 2 2
A A S B B 1 1 5 0 0 0 0 2 2A A S B B 1 1 5 0 0 0 0 2AAAAAA SSSS BBBB 1 1 555 0 0 0 0 2A A S B B 1 5 0 0 0 0 2A A S B B 1 5 0 0 0 0 2A A S S B B 1 5 5 0 0 0 0 2 2A A SSSS BBBB 1 555 00 00 2222
Welcome to the remote update file generation menu:Please insert the release , upgrading shall be based on: b (full release version is selected)
You wanted to base the output on a blank PROM set!
Please insert the wanted market : 1 (e.g. if STANDARD is selected)Please insert the upgrading version : B (select version)
Upgrade information checked successfullyBinary file names verified successfullyChecking maps:map number: 0 number of records different 0004
This statement confirms that a full up-grade not based on initial SW is chosen.
After entering the data this information issent back to assure correct operation
1.6 Terminal Application to load the file into the CPU-D4
Before starting the upgrading verify if the system time and date is correct otherwise correct it with RASC.Verify that the physical connection to the exchange has been established between the COM port of thePC (optionally via modem) and the V.24 interface/modem on the CPU-D4.
The upgrade program chkdiff.exe creates an output file called (____.txt). This is a binary file and must besent as a text file. The terminal application has to be set for this type of transmission. Depending on whichtype of upgrade is requested, the file is composed of either a complete new ASB 150 02 software versionor of only the differences in code between the existing software on the CPU-D4 and the new software, toreduce transmission time. In the latter case data is omitted that is already available in the active FLASHon the CPU-D4.
This shows that it is very important to know the actual software in the active FLASH running on the CPU-D4 and not depend on revision information stated on the PROMS mounted on the CPU-D4. Note that thesoftware version stated on the PROMS is obsolete after loading the new software. The output file (____.txt)must not be accessed by any editor as this action may destroy the content.
Start the terminal program as available on your operating system e.g. Hyperterminal. The terminalapplication starts the communication with the CPU-D4 and a selection menu is displayed prompting thenext actions. The CPU-D4 supervises the communication and if no input occurs for more than 15 minutesthe terminal is logged off and the connection is shut down. This is to prevent unnecessary connection fees.The CPU-D4 verifies all entered requests and the menu screen offers a selection of commands that areexecuted by typing in a letter.
Set up the connection to the ASB 150 02 system by using the terminal program on your PC and afterhaving configured the settings mentioned before. To start the communication quickly press the "S" key 3times. There is a timer surveillance monitoring the time between two key strokes and if it is greater than1 second the process is terminated.
If the connection was built up successfully a welcome screen (see below) greets the user and requests apassword entry.
1.6.1 Communication Start
If the correct password is entered the main menu will be displayed otherwise the session will beautomatically closed.
Select a function in the menu above by typing the related letter.
1.6.3 Menu item "S" - view information about active FLASH and upgrade FLASH
ACTIVE PROGRAM
This information applies to the actually running ASB 150 02 software program in the active FLASH.
UPGRADE PROGRAM
This information applies to the ASB 150 02 software program, which is stored in the upgrade FLASH. Thecontents is re-written by uploading the new SW. During every system restart the contents in the upgradeFLASH is checked. If an error is encountered (e.g. wrong checksum or last uploading of new SW was notfinished) the content of the active FLASH will be copied into the upgrade FLASH.
ASB 150 02 REMOTE UPGRADING MAIN MENU
S view information about active FLASH and upgrade FLASH
DATE: YY-MM-DD TIME: HH:MM shows the upgrade time.
SYSTEM TIME
DATE: YY-MM-DD TIME: HH:MM shows the current system time.
UPGRADE FLASH STATE
The upgrade FLASH state is indicated by the following messages displayed on the screen:
• NOT OK connection was broken?• OK OK indicates no backup has been ordered• ERROR DURING LAST UPLOAD repeat upload• UPGRADE WAS ORDERED• UNKNOWN connection was broken?
Press ENTER to continue:
To return to the main menu press ENTER.
1.6.4 Menu item "T" - view system, backup and upgrade time
This menu just displays the system and upgrade times. No change of time settings are permitted on thisscreen.
1.6.5 Menu item "U" - load new SW into upgrade FLASH
This screen requests to start the file transfer in the terminal application or press "E" to abort the procedure
To send the file execute send e.g. press the send icon on the terminal application. Verify that the file issent as a text file. The next screen shows the process of file uploading.
1.6.6 Uploading the file
After the file transfer is started this screen shows the progress of uploading. Each PROM is numbered(1 to 3) and the number shows which PROM and which MAP is currently re-written. A "X" is displayed asa progress indicator as data is stored.
If an error occurs during transmission a short error message describing the error cause is displayed.
If the file was transferred without any error „UPLOADING SUCCESSFULLY COMPLETED !“ is displayed.
The time to upgrade to the new software can be selected in this menu. The TAB key moves the cursorbetween the fields. Press ENTER after you have changed the upgrade time to activate the upgrade
NOTE: The entered upgrade time has to be a time later than the system time and the year of the upgradetime has to be the same as the year of the system time.
If changes in any field are entered a validation check is done. (e.g. 61 is not valid for the minutes)
The time is verified every 5 minutes thus after waiting up to 5 minutes upgrading is activated. If the programin the upgrade FLASH is valid and the system time reaches the upgrade time the system will automaticallyperform a re-start. The upgrade is also initiated if the system is restarted locally. During the restart the SWfrom the upgrade FLASH will be copied into the active FLASH and then the system restarts with the newsoftware.
1.6.8 Menu item "C" - cancel ordered upgrade time
After entering the letter "C" the system cancels the task and returns to the main menu.
Press E to exit without changing the upgrade time
Press ENTER after you have changed the upgrade time to activate theupgrade
The TAB key moves the cursor to the next field
The upgrade time entered must be later than the system time
SYSTEM TIME:DATE: 98-02-22 TIME: 17:55
UPGRADE TIME:DATE: 00-00-00 TIME: 00:00
Press E to exit without cancelling an ordered upgrade
NOTE: If upgrade is ordered, a system restart causes traffic interruption. Select a time that causes theleast customer disturbance.
2.1 Upgrading using a modem with the terminal program
If the maintenance centre is remotely located to the exchange the use of a modem is required to coverthe distance. In this case the application displays the same prompts and screens. The data rate betweenCPU-D4 and maintenance PC is up to 9.600 Baud. In case of problems verify that the modem speed isthe same data rate settings of the terminal application.
Error condition correction refer to:
Base information incorrect Verify that you have the link information correct for the softwarecurrently running on the CPU-D4.
page 6
Error input parameters are notwithin directory information file
Verify that all parameters were correct. Check that the marketversion is correct. Check that the upgrade version is correct.
page 7
Error condition correction refer to:
Check sum error If the CPU-D4 detects a checksum error e.g. the connectioncaused data to be corrupted or missing, re-transmit the output file.
In case of problems verify that the modem speed is the same datarate settings of the terminal application.
page 10
page 15
Terminal application does notstart
If a timeout is engaged it takes some 15 minutes before a terminalcan reconnect. Reasons: the session before was aborted or awrong file was sent to the CPU-D4 or the modem connectioncaused data corruption or the CPU-D4 is performing an upgrade/backup etc.
page 9
Upgrade Flash errors:
ERROR DURING LASTUPLOAD
The CPU-D4 monitors and verifies the data transfer. Corrupteddata is detected and the upload has to be repeated.
page 10
NOT OKIf the data is corrupted re-transmit the output file. Possible causese.g. broken link, PBX is restarted during upload etc.
page 10
UNKNOWN Cause of error not known and the upload has to be repeated. page 10
The data uploaded into the upgrade FLASH memory has to be copied into the active FLASH memory.This data move is invoked by entering the upgrade time. When the defined time is reached a restart isinvoked. The contents of the upgrade FLASH is copied into the active FLASH and the system starts up.The same procedure is started if the exchange is restarted either by power switching or reset on the CPU-D4 board. This copying process is indicated by the upper LEDs on the CPU-D4.
The CPU displays this process by lighting the LEDs on the front in a specific manner.
redyellowgreen
LEDRed Yellow Green
CPU-D4
on
one
two
repeated
Description of condition
The communication to the backplane is interrupted assoon as the red LED is on
on
flashes
Writing into PROM 1. After completing, the green LEDflashes several times to recalculate the checksum
flashesrepeated
Writing into PROM 2. After completing, the green LEDflashes several times to recalculate the checksum
threeflashes
repeated flashes
on
Writing into PROM 3. After completing, the green LEDflashes several times to recalculate the checkless
onrepeatedflashes
The green LED flashes during checksum recalcula-tion of the programming data. Then the system restartis invoked.
on
flashes
flash
fastflashing
Erasing of the upgrade FLASH. This takes some 30seconds.
This chapter explains the procedure of exchanging, adding or replacing a board in the ASB150 02without switching off the power. This procedure can be used for all system boards except the CPU,IC-LU, VMU-D and AUX boards. Changing boards without switching off the power should mainly beused to replace faulty boards or for expanding an existing hardware configuration.
4.2 Prerequisites
Boards can only be replaced by boards of the same type, with the same number of individuals . Thislimitation applies also for changing the number of individuals on an IC-CU-board. Just changing theFECU may cause serious memory allocation problems which may lead to a warmstart of the wholesystem. New boards shall be inserted in a vacant position only. If the RASC-PC is connected to thesystem via an AUX-board, this board must not be removed. If RASC is connected via a modem it isnot possible to perform any hot swapping action.
4.3 Procedure
This action can be invoked either by pressing the appropiate function keys (see Function keysoverview on page 18) or by executing the system command called ‘Shutdown’ in the pull down menulocated in the RASC menu ‘System data’:
System data/shut down/reroute position/cmd: 2095
To exchange (a) board(s) in a running system please follow the five steps below:
1 One or more boards need to be shutdown (see Shutdown of board(s) on page 18)
2 Change or insert new board(s) (see Adding (a) new board(s) to the system on page 19)
3 Search for and activate (a) new board(s) (see Search for new boards on page 19)
4 Re-programming of boards (if needed)
5 Check and erase warnings in the warning-log, which may have occurred because the board hasnot been available during hot swapping.
If all boards are registered in the system the keys below are only activated in the menu:
Admin/Maintenance/HW/SW/RP.
4.3.2 Shutdown of board(s)
The shutdown command is not needed if a new board is plugged into a formerly vacant slot.
In RASC this new command is located in the maintenance menu. The shutdown command must beissued before removing one or more board(s) from the system. If a board is removed from the systemthat was not shut down will cause a system restart. Move in the list to the boards (arrow keys) andpress the space bar to select them. Press the function key (F6) to shut down the board(s) or click thefield in the pull-down menu. This function key is only available in on-line condition (not availableduring remote access from e.g. the help desk). Enter the additional input parameter time to shut downif needed. The system waits during this selected time (0 to 11 minutes) and then forces all traffic todisconnect on the selected board(s). RASC displays in a window the remaining time until shutdown isinvoked. After this time has elapsed all active processes on the board(s) are terminated and RASCissues a prompt that the board is now ready to be removed. The user can neither exit this window noruse any other RASC function during this time.
Note: It is not possible to shut down CPU boards. The selected board(s) must be registered in the E2
memory on the CPU, so it is neither possible to shutdown MISPLACED or MISSING boardsnor boards of a wrong type. Additionally a detailed help text is accessible via the F1 key. If thePC crashes or a PC restart occurs during this waiting time, it is not possible to reconnect fromRASC to the system until the shutdown process has finished. In this case it is prohibited toenter system programming from a system instrument while a shutdown is in progress. Thismay cause serious configuration faults (mismatches) which could lead to a non-restartablesystem (in this case only a cold-start could get the system running again).
Transferring configuration data retrieved from a system with a different running/shutdown boardconfiguration (but everything else totally equal) causes serious configuration mismatches. Thismay lead to a system restart or, even worse, to a non restartable system. Therefore it isnecessary to be very careful with retrieving and storing of system configurations.
One or more boards can be added to the system. These boards can be new ones or updated oneswhich are still in shutdown state. There are two ways of adding a new board to an operating system:
a Replacing a board of the same type (& version)
After a board in shutdown state has been updated or replaced by a new one, it can be added to thesystem using the update command (F9) located in the RP menu in RASC. After the process iscomplete, RASC receives an acknowledge and this result is shown in the RP menu, now containingall the data of the operational board (PROM version, revision, etc.).
b A new board in a formerly vacant position (refer to next chapter 4.3.4).
4.3.4 Search for new boards
The search key (F5) in the RASC RP menu is available for finding new boards in formerly vacantpositions. RASC checks all board positions marked empty or new for boards. If a new board in anempty slot is found, it is marked as new. The new boards will be reported to RASC and will be shownin the RP menu. By pressing the update function key (F9) the boards are accepted by the system.After all boards have been accepted by the running system, the RP menu is built up new, nowdisplaying all the data of the operational board (PROM version, revision, etc.).Because the new board(s) is/are initialized with some default data only, (re)programming of theboard(s) may be necessary. After the initialization (and re-programming, if needed) is finished theboard(s) and all individuals are ready for traffic.
Note: When the search function is activated all new AUX-T boards are re-started (regardless whethernewly inserted or already existing in the system). RASC does not show them. When a board isinserted in a ‘SHUTDOWN’ position and does not exactly match (type & version) the board in-serted there before will cause the new board not to be accepted. In this case the slot remainsin ‘SHUTDOWN’ state.
4.3.5 Deletion of a board
Not available, restart the exchange to delete a board.
The central software block which handles ELU-A, ELU-C, ELU-D and IC-CU boards is EX.
Note: It is NOT possible to change the number of individuals of an IC-CU board by performing ashutdown of the board, replacing the FECU by another one (which may offer more/lessindividuals than the old one) and restarting the board.
5.1.1 Insertion of an ELU/IC-CU board
There are two possibilities when a new board is inserted at a certain position: There could have beena board of the same type and with the same number of individuals on it or the slot could have beenunused.
When adding an IC-LU board, this is handled only by IC-CU and does not involve the ASB 150 02central software. Thus neither further actions are required, nor is it possible to add nor to delete anIC-LU by the central software of the ASB 150 02.
Note: Before removing an IC-CU board, save the data by using the Cordless System Manager(CSM), and after replacing the IC-CU board transfer the configuration data from the previouslyinstalled board, otherwise all cordless telephone sets need to be re-programmed.
The main difference between insertion of a new board in a previously vacant slot and in a slot whereanother board of the same type was inserted before, is that in the first case no directory numbers areassigned to the individuals after the board has been started. This directory number assignment has tobe done from RASC and Cordless System Manager (CSM) afterwards.
5.1.2 Shut down of an ELU/IC-CU board
5.1.2.1 Operator Instrument
On an operator instrument calls can be parked with the loop keys, the OP-hold key and the monitorkey. If only one call is parked on the loop key and this is an incoming external call, it is rerouted backto the operator queue. If it is any other type of call the call is terminated. For the OP-hold and themonitor key the same applies as for the call on a loop key. If there are no more active operatorinstruments available for the OP-queue, all calls within the queue are re-routed to the shut down re-route position.
The new new command is:
• 2095 shut down reroute position (default = 0FFFFh).
If a master is shut down, no calls can be made to the slave extension. But calls to a master/slaveextension with a shutdown slave extension are presented on the master extension.
5.1.3 Insertion of an ELU/IC-CU board
5.1.3.1 Considerations for Diversion of an Extension
If an extension has activated any kind of diversion (e.g. follow-me) to a directory number that is notavailable in the system, the call is not diverted but instead starts ringing at the diverting extension. Soit is not necessary to check activated diversion during deletion of a board. If diversion of an extensionis deactivated, it is not possible to reactivate it again until a valid diversion address is programmed.
5.2 Considerations for BTU boards
All registers on the board are marked as busy. So these registers cannot be seized any longer. Thesystem tests the registers on the board to be shut down on their function (only for traffic or only forvoice or both). If one or both register types (traffic or voice) are no longer available within the systembecause the board is going to be shut down and was the only one or last one with this register type onthen the system responds with blocked function and lack of resources . These actions do notaffect an active call but background music or music-on-hold may be changed to silence. After a call isfinished the individual(s) are blocked automatically.
Check that the S/T switch settings are the same on the new BTU-B board as on the BTU-B board thatwas removed from the system. If a BTU-B is shut down, all data-calls (via the S-interface) areterminated too. This applies especially for automated calls.
Calls to a directory number belonging to an extension (also operator) located on a board which is inshut down state are rejected or diverted. While a board is removed from the system (the connectorsfrom the board front are removed) the Power Failure Circuit (PFC) is disabled.
5.2.0.1 Changing music channels
If a BTU-* board is hot swapped with one or more connected music sources, all extensions andoperators currently connected to one of these music sources (background music or music-on-hold)are switched to silence channels.
5.2.1 Insertion of a BTU board
When inserting a new board in a previously vacant slot there are no directory numbers assigned tothe individuals after the board has been started. Directory number are to be assigned by RASC lateron.
VMU-HD:After hot swapping a VMU-HD board all references to announcements are deleted. After re-insertion of a board of the same type and version it is possible to re-program theannouncements. Otherwise this could lead to wrong announcements.
5.3.1 Shutdown of a VMU-HD board
On a shutdown request all individuals on this board as well as all VMU-channels are blocked, so nonew requests to seize VMU-channels are possible and all queued VMU-channel requests arecancelled. All registers on the board are marked as busy. So these registers cannot be seized anylonger. This is exactly the same as for a shutdown of a BTU-D board.
As soon as a call and process is finished, all individual(s) affected will be blocked automatically. Notall calls with queued voice channel requests receive a channel, so these calls have to continue afterthe voice playing part or be re-routed. After the selected shut down time out elapses, all channels stillplaying announcements will be terminated.
5.3.2 Insertion of a VMU-HD board
There are two possibilities if a new board is inserted in a slot: There may have been a board of thesame type and version in this slot before or the slot may have been vacant. Before a new VMU-HDboard can be initialized, note that the references to the anouncements and messages of the old boardare deleted. This is necessary because there is no way for the system to check whether the voicestored on the new VMU-HD board is the same as it was on the old one. Set the command 4603 toYES to allow recording of announcments. Announcements stored on the board can be retrieved afteran update command by a system programming command via a system telephone (command No.4450).This does not apply for a new board in a previously vacant position.
5.4 Final Check
Generally a shutdown and restart of a board should generate no warnings. If some warnings arelogged due to this action, open the log, evaluate the warnings and forward them if necessary to thesupport centre and, if they are obsolete, erase them.
On re-start of the exchange the administration data is updated in the system hardware administration areaindicating the service technician where to re-insert the different shut down boards after a program upgrade.Using the information in the RP menu of RASC, reduces the risk of misplacing boards after the hotswapping. The most recent and valid configuration is stored on the CPU-D4 containing information suchas ROF number, RYS number and revision states, also during the shutdown state of these boards. Thebattery back-up RAM stores the complete administration information for up to a maximum of 64 boards.
To read out the configuration enter RASC, go to the item configuration or look under the maintenancemenu HW/SW the configuration list.
7 REPLACEMENT OF BATTERIES
The only components in the PBX requiring maintenance are the batteries used as power backup for theentire system and the battery on the VMU-boards.
To ensure sufficient battery capacity in the event of power failure, the batteries must be replaced periodically.
The replacement period for the power supply battery backup of the PBX, and for the battery on theVMU-board (ROF 157 5117/1) are five years.
For more information of the power supply battery backup of the PBX, see documentINSTALLATION INSTRUCTION 1531-BML BS 101 01,INSTALLATION INSTRUCTION 1531-BDV 113 08,INSTALLATION INSTRUCTION 1531-BML 351 048 andINSTALLATION INSTRUCTION 1531-BML 351 013.
To ensure proper function the batteries should be replaced by new ones every five years.
The replacement of the battery on the VMU-board is done easily:
1 be sure that the main supply is ON
2 then replace the battery package on the front of the VMU-board
The product No. for the battery on the VMU-board is RNV 991 942/001.
1(5)
Datum - Date Rev
Nr - No.Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other)
This document is to be used by service personnel when maintaining digital telephonesDBC 211 01, DBC 212 01 and DBC 213 01 with key panel DBY 409 01, designed for use withdefined releases of Ericsson's digital exchanges ASB 501 and ASB 150 02 or equivalent.
For spare parts, see 154 11-DBC 202+ Uen
2 Selftests
There are two types of selftest:
(1) automatic testing when the telephone is connected to a local power supply (48 V) or to anexchange.
(2) testing initiated by the user pressing a special key combination.
The latter test can also be carried out with the telephone connected to the exchange or to a localpower supply. The testing refers primarily to the DBC 211 01, DBC 212 01 and DBC 213 01telephones, whereas the test items applicable to DBY 409 01 are specially indicated in the text.
DBY 409 01 can only be tested together with the DBC 203 or DBC 213 telephone.
2.1 Automatic selftest (when connecting the telephone to ASB 501)
The automatic selftest is always carried out when connecting the telephone and comprises thefollowing functions/units: watchdog, RAM, D-channel, registers in the line communication circuit(DASL), registers in the speech transmission circuit (COMBO) and the display.
If no fault is detected, the LED in the INQUIRY key is lit, and for DBC 212 and DBC 213 themessage "SELFTEST OK" is shown on the display for one second.
If a fault is detected, this is reported to the exchange when the telephone is activated, but no faultindication is given on the telephone.
If no fault is detected in DBY 409 01, the bottom LED is lit for 1 second. If a fault is detected, noLED is lit.
None of the units (DBC 211 01,DBC 212 01, DBC 213 01 and DBY 409 01)should be repaired, except for replacement of parts listed in the spare parts listInstead, the purpose of this instruction is to decide whetherthe faults are located in the telephone set, in the exchange or line network.
3(5)
Datum - Date Rev
Nr - No.Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other)
This test is initiated by pressing the keys 'C', '*' and '4' at the same time for one second. Thetelephone abandons local test mode automatically after 30 seconds, or directly when the ’#’ keyis pressed.
The following objects are tested automatically: RAM, D-channel, registers in the linecommunication circuit (DASL), registers in the speech transmission circuit (COMBO) and thedisplay. In addition, the user may test the following objects keys, hook, LEDs, tone ringer, displayand speech transmission.
2.2.1 Local selftest
This selftest is carried out automatically when local test mode is activated. All LEDs are lit.
If no faults are found, the display shows "SELFTEST OK" and the product number of the ROMcontents of the telephone's microprocessor, for instance, "CAA1122856 R1A". If a fault is found,the LEDs in Table 1 below will start flashing, and fault messages will be shown on the display.
After 5 seconds, the display is filled with characters in descending ASCII order.
Table 1 Error messages presented on the display.
ERROR MESSAGE (DBC 212 01,DBC 213 01) written on the display
Keys for identification of error messages on DBC 211 01, DBC 212 01 and DBC 213 01
On DBY 409 01, the top LED flashes if a fault is found in the RAM test.
2.2.2 Local key and tone ringer test
The keys are tested by pressing them one at a time. Each keystroke should result in thegeneration of a tone signal; this applies to DBY 409 01 as well.
“Off hook” and “On hook” will also result in the generation of a tone signal.
The volume of the tone ringer can be changed by pressing the volume keys marked’+' and '-'. The levels will be the same after exit from the Local test mode.
2.2.3 Local speech and transmission test
Handset function:Off hook activates handset mode. The microphone signal in the handset is sent via COMBO andis looped back in DASL to the handset receiver. The transmission is tested by blowing into thehandset microphone and listening through the handset receiver. The "blow" sound shall now beheard in the receiver.
Loudspeaker function:The test is activated by pressing the key marked with a loudspeaker symbol. Then its function istested by blowing into the handset microphone and listening in the loudspeaker. The "blow"sound shall now be heard in the receiver.
Handsfree microphone:After the loudspeaker has been tested, the microphone for the loudspeaking function can betested by keeping the hook pressed. Sound from the microphone should then be heard in thehandset receiver.
5(5)
Datum - Date Rev
Nr - No.Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other)
Volume control:The volume of each transmission mode can be changed by pressing the volume keys marked '+'and '-'. The levels will be the same after exit from the Local test mode.
Mute functionThe mute function is tested by pressing the "Mute" key while blowing in the microphone andchecking if the sound in the handset receiver or loudspeaker ceases.
