UP30300E Data Manual

PREFACE
This manual guides you through the process of upgrading an SOPHO iS3010/iS3030 from
SSW 200/205 to SSW 300 and up.
The installer is expected to have experience with the installation of ISPBX exchanges and
also knows how to work with Project Generator 2 (PG2)
Note, that this book only deals with the upgrading process and not with implemetation of
additional hardware or facilities (which is probably the reason for upgrading).
9502 DB-A 9149e-351 0-1

© Philips Communication Systems B.V. 1995. All rights are reserved.
Reproduction in whole or in part is prohibited without the written consent of the copyright owner.
CONTENTS
0. MANUAL DATA Pages 0-1/0-4 (9502)
1. INTRODUCTION Pages 1-1/1-2 (9502)

1.1. NECESSARY TOOLS AND PROGRAMS . . . . . . . . . . . . . . . . . . . . . . . 1-1
2. UPGRADING AND ADAPTING SYSTEM

DATA Pages 2-1/2-4 (9502)
2.1. HOW TO UPGRADE A POM FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.1. The Pre-processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2. ADAPTION OF POM DATA ................................. 2-4
3. REPLACING HARDWARE Pages 3-1/3-4 (9502)

3.1. REMOVING OLD CARDS AND CABLES . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2. INSTALLING NEW CARDS AND CABLES . . . . . . . . . . . . . . . . . . . . . 3-1
3.2.1. SOPHO iS3010 and Single Cabinet SOPHO iS3030 . . . . . . . . . . . . . 3-1
3.2.2. Double Cabinet SOPHO iS3030 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
4. LOADING OF NEW SOFTWARE Pages 4-1/4-6 (9502)

4.1. LOADING OF CPU SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2. LOADING OF THE POM FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.3. LOADING OF PPU SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
5. MAKING A BACKUP OF THE SYSTEM Pages 5-1/5-2 (9502)
A. SHELF LAYOUT SOPHO iS3010/iS3030 Pages A-1/A-2 (9502)

A.1. SHELF LAYOUT SOPHO iS3010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A.2. SHELF LAYOUT SOPHO iS3030 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
9502 DB-A 9149e-351 0-3

AMENDMENTS
• Issue: 9211 9502
The manual update from issue 9301 to 9502 concerns the following items:
CHAPTER/
SECTION ISSUE DESCRIPTION
DIAGRAM CHANGE
all 9211→9502 Terminology changes
0-4 DB-A 9149e-351 9502

1. INTRODUCTION
SWW 300 introduces a number of new hardware items. The CPU-board is equipped with a
68K micro processor and the basic CPU and PPU software is now held by Electrically
Erasable PROMs (EEPROMs) or flash-EPROMs. The CPU and PPU programs can now be
loaded from a PC, thus replacing the labour-intensive replacing of EPROMs.
This release also introduces the double-cabinet SOPHO iS3030.
SSW 300 contains the following systems:
- SOPHO iS3010;
- SOPHO iS3030;
- SOPHO-S250;
- SOPHO-S1000.
A SOPHO iS3030 can be configured as a master-slave system. The master contains a

CPU board, which controls the PMCs of both cabinets. Cables from one PMC to the other
carry the control information between the master and slave cabinet.
Both the SOPHO iS3010 and the SOPHO iS3030 can be obtained by upgrading an existing
system or by buying a new one, whereas the SOPHO-S250 and SOPHO-S1000 (of SSW
300) can only be obtained by upgrading existing systems.
1.1. NECESSARY TOOLS AND PROGRAMS
Ugrading of a SOPHO iS3010/iS3030 requires the following cards en cables:
- The Central Processor Unit - Medium Extended (CPU-ME)

This card has a 68K micro processor and flash-EPROMs for holding the CPU programs
and the POM data.
- The Peripheral Module Controller - Medium extended and interConnectable (PMC-MC)
This card has flash-EPROMs for holding the PPU programs
- PMC to PMC cable;
- A V.24 Interface Card (VIC). Since functions of APU board are integrated in the CPU
software, there might be need for a few extra V.24 interfaces.
General requirements:
- Maintenance PC with corresponding MPC-CPU cable;

- Project Generator 2
- POM conversion programme (CNVPOM)
It is obvious that all programs must be valid for SSW 300. Besides, the MPC data package
for the existing system must be available (in order to generate an ADF)
9502 DB-A 9149e-351 1-1

2. UPGRADING AND ADAPTING SYSTEM DATA
This chapter describes how to upgrade the old DLF and ADF to a POM file for SSW 300. It
does not tell how to implement new SSW 300 items as this is already covered by the
Facility Implementation Manuals for SSW 300.
It is assumed that a DLF of the existing system is available, either as a file or on paper.
Other Items which are essential must be generated from the system before it is switched off
and the hardware is removed. These items are:
- Emergency Load File (ELF)

Retrieve an ELF with OM ”GEEMER”. The ELF can not be upgraded to SSW 300,
however this ELF is usefull if the upgrading is not successfull and you have to restore the
old (SSW 200/205) configuration.
- Administrative data File (ADF)
Retrieve an ADF with “SUBMIT: MOAD2XXX,,,;“
- Retrieve (additional = not generated by MOAD2XXX) OM information by “submitting“
MISSING.POM to the system.
- Dump toll ticketing records either straight from the CPU port or via a CMS80/90.
It is unavoidable to ask users to cooperate with the following items:
- User effectuated facilities

Some of these can be displayed by means of facility class marks and may even be
present in a generated ADF. Others must be written down by the user and initiated anew
after the upgrade process;
- User programmed data of terminals (SOPHO-SETs etc.)
Make people aware that (function key) data which is programmed by hand will be lost
and should be programmed anew after the upgrade process. This also goes for the name
directory of a SOPHO-SET which is powered by its line and does not have battery
backup.
If the PG2 database of the existing system is available, then this can be upgraded to SSW
300 by a PG2 conversion programme which is delivered together with the PG2 programme
files.
In this case, it is advised to only generate the DLF from the PG2 database, while the ADF
generated from the (ISPBX) system is more up to date and contains more information then
the ADF from PG2.
Table 2.1. shows the upgrade procedure. Column 1 gives the steps to be executed when
PG2 is available and column 2 describes what to do if PG2 is not available.
9502 DB-A 9149e-351 2-1

PG2 IS AVAILABLE PG2 IS NOT AVAILABLE
Upgrade the PG2 database to SSW 300* Upgrade the old DLF to SSW 300 using CNVPOM
(see section 2.1.)
Add new items to the PG2 database (if needed)* Add new items to the DLF using a text editor (if
needed)
Build the DLF from PG2*
Upgrade the ADF which was generated from the old Upgrade the ADF which was generated from the old
system using CNVPOM (see section 2.1.) system using CNVPOM (see section 2.1.)
Add new items to the ADF, if needed, using a text Add new items to the ADF, if needed, using a text
editor editor
Combine the DLF and the ADF to a POM file Combine the DLF and the ADF to a POM file
Table 2.1. Upgrade Procedure.
Note: Detailed user guidance for PG2 can be found in the PG2 User Guide.
2.1. HOW TO UPGRADE A POM FILE
DLFs and ADFs from SSW 200 and SSW 205 can be upgraded to SSW 300 using the
conversion programme CNVPOM. The following conversions are possible:
- SSW 200 to SSW 205;

- SSW 200 to SSW 300;
- SSW 205 to SSW 300.
To start this programme, type the following at the MS-DOS command line:
CNVPOM [-i <input_package>] [-o <output_package>] [-l <pre_file>]

[-d <dlf_file> | -a <adf_file> | -p <pom_file>] [-r <res_file>] [-c]
parameter description:
- -i <input_package> : Optional. It defines the input package for conversion and can
be either SSW 200 or SSW 205. The default is SSW 205.
- -o <output_package> : Optional. It defines the output package for conversion and
can be either SSW 205 or SSW 300. The default is SSW
300.
- -l <pre_file> : Optional. Defines the input file for the pre-processor. If
defined, pre-processing takes place else not.
- -d <dlf_file> : Defines input file used for conversion. This file contains PE
commands only.
- -a <adf_file> : Defines input file used for conversion. This file contains OM
commands only.
2-2 DB-A 9149e-351 9502

- -p <pom_file> : Defines input file used for conversion. This file contains both
PE - and OM commands.
- -r <res_file> : Optional. Defines the name of the output file (or result file), if
the default name is not wanted. Default names are listed in
Table 2.2.
INPUT FILE(S) OUTPUT PACKAGE = P205 OUTPUT PACKAGE = P300
<dlf_file> only “dlf_205.pom“ “pom_300.pom“

<adf_file> only “adf_205.pom“ “pom_300.pom“
<dlf_file>and “pom_205.pom“ “pom_300.pom“
<adf_file>
<pom_file> “pom_205.pom“ “pom_300.pom“
Table 2.2. Default Output File Names.
- -c : Optional. Sets check flag which enables conversion

check in output files. When this parameter is omitted, no
conversion check will be done.
Note: Filenames can have up to 24 characters
2.1.1. The Pre-processor
Some OM commands can not be generated from the system, because it does not have a
GENADF command. Still, these missing OM commands are essential for the upgrading of a
system.
These missing OM commands can be generated with the help of a POM file called
MISSING.POM, which contains OM commands which display a number of items. When this
file is submitted to the system it results in a log file (MISSING.LOG probably) which can be
pre-processed by the CNVPOM programme. This pre-processing converts the contents of
the .LOG file to OM commands which assign and change items. These OM commands are
automatically incorporated in the actual ADF for the upgraded system.
The MISSING.POM for SSW 200 contains the following OM commands:

<DIBAUD: ; \* Display baudrate of printer *\
<DIDNDC: ; \* Display do not disturb class marks *\
<DIEMNR: ; \* Display emergency alarm number *\
<DIFFLM: ; \* Display fixed follow me *\
<DIFLME: ; \* Display follow me relations *\
<DISRVP: ; \* Display PMC status *\
<DITTCR: ; \* Display toll ticketing characteristics *\
\* Missing command parameters for fast projecting *\
9502 DB-A 9149e-351 2-3

<DIEPPS: ;
the MISSING.POM for SSW 205:

<DIBAUD: ; \* Display baudrate of printer *\
<DIDNDC: ; \* Display do not disturb class marks *\
<DIEMNR: ; \* Display emergency alarm number *\
<DIFATI: 1 ; \* Display facility timing*\
<DIFATI: 2 ;
<DIFATI: 3 ;
<DIFATI: 5 ;
<DIFFLM: ; \* Display fixed follow me *\
<DIFLME: ; \* Display follow me relations *\
<DISRVP: ; \* Display PMC status *\
<DITTCR: ; \* Display toll ticketing characteristics *\
\* Missing command parameters for fast projecting *\

<DIEPPS: ;
2.2. ADAPTION OF POM DATA
Note: If a SOPHO iS3030 with two cabinets is synchronised to a DTU, then this DTU must
be located in the master cabinet.
2-4 DB-A 9149e-351 9502

3. REPLACING HARDWARE
This chapter describes which boards are to be removed and how to install the new
hardware. Installation aspects of a double-cabinet SOPHO iS3030 are in a separate part,
because it involves a number of specific steps.
Note: Take the necessary precautions to protect the boards against the effects of static
discharge, while replacing them.
3.1. REMOVING OLD CARDS AND CABLES
After having carried out the instructions of chapter 2, switch off the power supply and
remove the CPU-SM and the PMC-ME. Remove the DOC or AOC (if present) from the
PMC-ME, at least if this card is wanted in the upgraded system.
3.2. INSTALLING NEW CARDS AND CABLES
A SOPHO iS3010 only exists in a single cabinet configuration. The SOPHO iS3030
however, can also appear as a master-slave configuration.
Their installation aspects are described in the following two sub-sections.
3.2.1. SOPHO iS3010 AND SINGLE-CABINET SOPHO iS3030
The procedure below describes how to install the new hardware in single-cabinet systems.
It applies to both the SOPHO iS3010 and the SOPHO iS3030, as they can both appear in
that form. The CPU and PMC positions however differ per system (see appendix A)
Before any hardware can be installed, make sure that the system power is (still) switched
off.
Installation of new hardware involves the following steps:
- Attach, if wanted, the DOC or AOC to the PMC-MC

- Attach, if wanted, a daughter board to the CPU-ME
This could be a V.24 Interface Card (VIC), which gives the CPU-ME three extra V.24
connectors. Note, that the CMS80 (or 90) is not supported anymore in SSW 300!
- Insert both the CPU-ME and the PMC-MC, whether or not combined with daughter
boards, in their apropriate card slots. (see appenix A).
9502 DB-A 9149e-351 3-1

3.2.2. DOUBLE-CABINET SOPHO iS3030
A SOPHO iS3030 can also appear as a double cabinet system. An existing system is then
extended with a second SOPHO iS3030 cabinet. The cabinet which holds the CPU is very
often denoted as the master and the other as the slave.
The installation must be done as follows:
- Install the second cabinet at a proper place. Make sure that the distance between the
cabinets can be covered by the cables who connect the PMCs of the two cabinets;
- Remove the CPU and PMC from the existing cabinet;
- Attach, if wanted, DOCs and/or AOCs to the PMC-MC(s)
- Attach, if wanted, a daughter board to the CPU-ME
This could be a V.24 Interface Card (VIC), which gives the CPU-ME three extra V.24
connectors. Note, that the CMS80 (or 90) is not supported anymore in SSW 300!
- Insert both the CPU-ME and the PMC-MCs, whether or not combined with daughter
boards, in their apropriate card slots. (see appenix A).
- Connect the PMCs by means of the two “PMC to PMC“ cables
If the system extracts the clock signal from a DTU, make sure that this DTU is located in the
master cabinet.
The PMC-MC has two clock signal inputs. The topmost has highest priority. If this fails then
the system automatically selects the second input.
3-2 DB-A 9149e-351 9502

PMC of master PMC of slave
1 1
0 0
0 0
FAA
FBA
B
aaaa
aaaa
aaaa
aaaa
aaaa
aaaa
aaaa
aaaa
C
FCA
C
P P
M M
C C
D
Figure 3.1. PMC to PMC Connection for a SOPHO iS3030 Double-Cabinet

Configuration.
9502 DB-A 9149e-351 3-3

4. LOADING OF NEW SOFTWARE
This chapter gives the loading procedures for CPU software, POM file and PPU software.
Figure 4.1. shows a flow chart for this, which should be sufficient for those who have some
experience in upgrading. Sections 1 up to 4 give additional information.
section 4.1. section 4.2.

Load POM data
1
Connect MPC
1 to system
Give a cold
2 start
Switch on the
2 system
POM file is
display CPU loaded
3 identity
section 4.3.
No
CPU package Display PPU
1 package
available?
4
Yes No
PPU package
present?
2
No
Old CPU Yes
package?
5 No
Yes Old PPU
package?
3
delete existing
6 package Yes
erase existing
load CPU 4 PPU package
7 package
Load PPU
Start CPU 5 package
8 package
Set the PMC(s)

6 in service
CPU package
up to date
PPU package
up to date
Figure 4.1. Loading of CPU and PPU data package.
9502 DB-A 9149e-351 4-1

The POM file must be loaded after the CPU software, because the latter validates the PE
commands.
It is also possible to load the PE and the OM separately. The PE must then be loaded
directly after the CPU software whereas the OM has to loaded (with“SUBMIT“) after the
PPU software. This way of loading allows separate error correction for PE and OM data.
The PPU software can only be loaded when the PMCs are projected and out of service.
Therefor, first load the POM file, then set the PPUs out of service (they were set to not
installed) and then load the PPU software.
Now, the system can be customised by manual entered OM commands and finally backup
the POM data
4.1. LOADING OF CPU SOFTWARE
The following procedure describes how to load the CPU data package:
1 Start the maintenance PC and let it try to communicate to the system.

Although communication to the system is not possible yet, it permits the system to
establish communication when it is switched on.
2 Switch on the system power
The CPU-ME will start up and establish communication to the maintenance PC. It is
controlled by the CPU boot-program at this stage. During startup, the lamps of the CPU
and PMC should react as follows: Initially, the red lamp should be on and after some time
the green lamp should go on.
3 Display package identities of CPU programmes by means of the OM command: DIPACK:
; (DISPLAY PACKAGE)
This displays the identity of the boot program and of any existing CPU package.
4 Is there a CPU package present? or in other words, did the DIPACK command give a
CPU package identity?
5 Was it an old CPU package? Was the CPU package identity the same as the one which
is required or is it an older package?
6 Delete existing package by OM: DEPACK: , 0/1 ; (DELETE PACKAGE)
This erases the existing CPU package and, depending on parameter 2, an existing POM
data package as well. The first parameter must be left blank. The second parameter
specifies whether the POM memory must be cleared: 1 means yes and 0 means no.
7 Load the CPU package by OM: LDPACK: , <FILENAME>, <SYSTEM-ID>; (LOAD
PACKAGE)
<FILENAME> tells the MPC which file to load.
<SYSTEM-ID> tells the system what it`s identity is. Because it does not know yet
whether it is SOPHO iS3010 or a SOPHO iS3030.
While loading this package, the maintenance PC indicates the progress of the package
transfer. When this package has been downloaded go to the next step.
8 Start the CPU package by OM: STPACK: ; (START PACKAGE)
The CPU boot-program will hand over control to the CPU package, which has just
4-2 DB-A 9149e-351 9502

been loaded. This control transition stops communication to the MPC for a while. After
the communication is re-established the MPC will display the identity of the package just
loaded.
4.2. LOADING OF THE POM FILE
The system accepts POM data when the CPU package has been loaded and stored. The
POM data is stored in the POM memory which consists of flash-EPROMs and is built-up of
two equal parts:
flash-EPROMs RAM
POM DATA AREA
“part 1“
Serial
port
RUN-TIME
MPC DATABASE AREA
“part 2“
Figure 4.2. POM Memory Structure.
The advantage of a separate POM memory is that POM data can be loaded in an
operational system. The system is only down during the cold start which validates the POM
data and copies it from the POM memory to the run time database.
The advantage of the flash-EPROMs is that they hold their contents when no voltage is
applied.
The two equal parts enable loading of new POM data without overwriting the old. This
allows to make a backup without loosing the original POM data.
A POM memory part can be in one of the following states:
- Not programmed;
- Cleared, ready to program;
- Busy with programming;
- Programmed and error;
- Programmed not certified;
- Programmed and certified;
- Programmed and projecting error
- Programmed out of date;
- Programmed and Autonomously blocked.
9502 DB-A 9149e-351 4-3

A POM file loaded from the MPC, is stored in one of the two POM memory parts. It is
copied to the run time database and validated by means of a cold start.
A memory part which is not used (yet) is Not programmed. If it has been filled with POM
data then it gets the state Programmed not certified and when a cold start has been carried
out it gets the state Programmed and certified.
A memory part can either be filled with POM data downloaded from the MPC or with POM
data which is a backup of the system. When requested for one of these actions, the
systems chooses the memory part which is not used yet or which contains the eldest POM
information. The system realises this by choosing the memory part which is Programmed
not certified or programmed out of date.
Suppose that part 1 is loaded from the MPC and a cold start has been carried out (it is
Programmed and certified ) and you want to make a backup, then the system picks out part
2 for this. When the system has finished storing the backup information in part 2, it gives
this part the state Programmed and certified and changes part 1 to Programmed out of
date.
Loading of the POM file takes the following steps:
1 Load the POM data with OM: LDPOMD:<DLF file name>;

The MPC shows the flashing “BUSY“ indication when it prepares the POM data to be
sent to the ISPBX, when finished it starts clearing the applicable POM memory part if this
has not been done yet. The state of this becomes then Cleared, ready to program.
Finally it loads the POM data into the flash EPROM memory of the CPU.
If the POM data does not fit into the POM memory or anything else goes wrong then the
system activates the alarm “POM memory full“ (alarm 1006, error type 20). The state of
the particular POM memory part is set to Programmed and error.
Another error that can appear at this stage is that a flash-EPROM is faulty. The system
then generates system alarm code 1006, error type 10 (Program fail) and sends the
message “FEPROM Program error“ to the MPC. The state of the particular POM memory
part is set to Programmed and Autonomously blocked. If this happens then the CPU card
should be replaced.
2 Execute the POM data by giving the system a cold start (COLDST). A cold start takes
about 10 minutes.
If projecting (validation) errors occur, then the system generates system alarm code
1006, error type 30 (Projecting data error) and changes the state of the particular POM
memory part to Programmed and projecting error. These errors can be read out with OM
“DUPOME“.
4-4 DB-A 9149e-351 9502

4.3. LOADING OF PPU SOFTWARE
The PPU software is downloaded from the CPU into the PMC. This loading can not take
place unless the PMCs are projected and out of service. If the PMCs are in service and
they need to be loaded with a (new) PPU package, then first set them out of service (with
OM: SETODS) and subsequently give a warm start (OM: WARMST). The OM command
SETODS can not take the PMC really out of service, it only attempts to do this. But after the
warm start it has really been taken out of service.
The PMCs are to be downloaded as follows:
1 Display the identity of the PPU package by OM: DIPACK: <EHWA>;

This diplays the identity of the PPU boot-program and of the PPU software, if any.
If the system does not accept the hardware address of a PMC, then it is simply not yet
projected. Check the POM data in that case, whether it defines the PMCs properly.
2 Is there already a PPU package present, or in other words, did the DIPACK command of
step 1 give the identity of a certain PPU package?
3 Is it an old PPU package or is it exactly the one which is required?
4 enter OM: DEPACK: <EHWA>,;
<EHWA> points to a particular PMC, it can be entered either as a single parameter or as
a series.
5 enter OM: LDPACK: <EHWA>, <FILENAME>,;
<EHWA> points to the PMC(s) to be loaded and <FILENAME> is the file name of the
PPU data package file on the maintenance PC. If the PPUs are still in service condition
NIN (Not Installed) then set them out of service using “SETODS“.
6 Enter OM: SETSDS:<EHWA>; This sets a certain PPU into service.
9502 DB-A 9149e-351 4-5

5. MAKING A BACKUP OF THE SYSTEM
When the system has become operational and been adjusted to the customers wishes,
then make a backup of the system. This backup is a POM file which is retrieved from the
system and exactly reflects its current state.
Make a backup in the following way:
- Enter BKPOMD: ;
This generates OM data from the run time database and stores it in the POM memory
part which is not Programmed and Certified.
When finished, the state of this memory part changes to Programmed and Certified. This
allows any subsequent cold start to affect it. The state of the other memory part changes
to Programmed and out of date.
- Enter DUPOMD: [<PART>] ;

This retrieves POM data from a specific POM memory part to the Maintenance PC. If the
parameter <PART> is omitted, then the system picks out that part which is Programmed
and Certified.
9502 DB-A 9149e-351 5-1

APPENDIX A
A. SHELF LAYOUT SOPHO iS3010/iS3030
A.1. SHELF LAYOUT SOPHO iS3010
SOPHO iS3010
UG0 UG1
001 002 003 004 005
P P P P P
C C C C S
T T T T U
1 2 3 4
101 102 103 104 105
P P P C TRANSFORMER
C C M P
T T C U &
5 6 - - BATTERY
M M
C E COMPARTMENT
UG2
Figure A.1. Shelf Layout of SOPHO iS3010.
9502 DB-A 9149e-351 A-1

A.2. SHELF LAYOUT SOPHO iS3030
A double-cabinet SOPHO iS3030 (as depicted below) consists of a master and a slave
cabinet. The master is the one which holds the CPU.
A single-cabinet SOPHO iS3030 only consists of the master.
SOPHO iS3030 Master Cabinet SOPHO iS3030 Slave Cabinet
UG0 UG1 UG2 UG3 UG4 UG0 UG1 UG2 UG3 UG4
001 002 003 004 005 006 007 008 009 010 011 201 202 203 204 205 206 207 208 209 210 211
P P P P P P P P P P P P P P P P P P P P P P
C C C C C C C C C C S C C C C C C C C C C S
T T T T T T T T T T U T T T T T T T T T T U
1 2 3 4 5 6 7 8 9 10 - 1 2 3 4 5 6 7 8 9 10 -
M M
L L
101 102 103 104 105 106 107 108 109 110 301 302 303 304 305 306 307 308 309 310
P P P P P P P C P TRANSFORMER, P P P P P P P P P TRANSFORMER,
C C C C C C M P C C C C C C C M C C
T T T T T T C U T RECTIFIER T T T T T T C T T RECTIFIER
- - & - &
11 12 13 14 15 16 M M 19 11 12 13 14 15 16 M 18 19
C E BATTERY C BATTERY
COMPARTMENT COMPARTMENT
UG5 UG6 UG7 UG9 UG5 UG6 UG7 UG8 UG9
Figure A.2. Shelf Layout of SOPHO iS3030.
A-2 DB-A 9149e-351 9502


UP30300E Data Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UP30300E Data Manual

Uploaded by

Copyright:

Available Formats

PREFACE

9502 DB-A 9149e-351 0-1

0. MANUAL DATA Pages 0-1/0-4 (9502)

1. INTRODUCTION Pages 1-1/1-2 (9502)

2. UPGRADING AND ADAPTING SYSTEM

3. REPLACING HARDWARE Pages 3-1/3-4 (9502)

4. LOADING OF NEW SOFTWARE Pages 4-1/4-6 (9502)

5. MAKING A BACKUP OF THE SYSTEM Pages 5-1/5-2 (9502)

A. SHELF LAYOUT SOPHO iS3010/iS3030 Pages A-1/A-2 (9502)

9502 DB-A 9149e-351 0-3

• Issue: 9211 9502

all 9211→9502 Terminology changes

0-4 DB-A 9149e-351 9502

SSW 300 contains the following systems:

A SOPHO iS3030 can be configured as a master-slave system. The master contains a

1.1. NECESSARY TOOLS AND PROGRAMS

Ugrading of a SOPHO iS3010/iS3030 requires the following cards en cables:

- The Central Processor Unit - Medium Extended (CPU-ME)

- Maintenance PC with corresponding MPC-CPU cable;

9502 DB-A 9149e-351 1-1

- Emergency Load File (ELF)

It is unavoidable to ask users to cooperate with the following items:

- User effectuated facilities

9502 DB-A 9149e-351 2-1

Table 2.1. Upgrade Procedure.

2.1. HOW TO UPGRADE A POM FILE

- SSW 200 to SSW 205;

CNVPOM [-i <input_package>] [-o <output_package>] [-l <pre_file>]

2-2 DB-A 9149e-351 9502

INPUT FILE(S) OUTPUT PACKAGE = P205 OUTPUT PACKAGE = P300

<dlf_file> only “dlf_205.pom“ “pom_300.pom“

Table 2.2. Default Output File Names.

- -c : Optional. Sets check flag which enables conversion

Note: Filenames can have up to 24 characters

2.1.1. The Pre-processor

The MISSING.POM for SSW 200 contains the following OM commands:

\* Missing command parameters for fast projecting *\

9502 DB-A 9149e-351 2-3

the MISSING.POM for SSW 205:

\* Missing command parameters for fast projecting *\

2.2. ADAPTION OF POM DATA

2-4 DB-A 9149e-351 9502

3.1. REMOVING OLD CARDS AND CABLES

3.2. INSTALLING NEW CARDS AND CABLES

3.2.1. SOPHO iS3010 AND SINGLE-CABINET SOPHO iS3030

- Attach, if wanted, the DOC or AOC to the PMC-MC

9502 DB-A 9149e-351 3-1

The installation must be done as follows:

3-2 DB-A 9149e-351 9502

Figure 3.1. PMC to PMC Connection for a SOPHO iS3030 Double-Cabinet

9502 DB-A 9149e-351 3-3

section 4.1. section 4.2.

Set the PMC(s)

Figure 4.1. Loading of CPU and PPU data package.

9502 DB-A 9149e-351 4-1

4.1. LOADING OF CPU SOFTWARE

1 Start the maintenance PC and let it try to communicate to the system.

4-2 DB-A 9149e-351 9502

4.2. LOADING OF THE POM FILE

Figure 4.2. POM Memory Structure.

A POM memory part can be in one of the following states:

9502 DB-A 9149e-351 4-3

Loading of the POM file takes the following steps: