Operation; Introduction; General; Initial Start-Up (System Self-Diagnostics) - Siemens SIREC D Handbuch

3 Operation

3.1 INTRODUCTION

3.1.1 General.

This chapter contains infor-
mation concerning system operation and keystroke
commands. Explanations of the front panel, dis-
plays, and some menu selections are included. All
menus are accessed through specific MENU keys.
The DISPLAY Menu and the FUNCTION Menu are
discussed in detail in this chapter. The PROGRAM
Menu is discussed in Chapter 4, "Programming".
3.2 INITIAL START-UP
(System Self-Diagnostics)

3.2.1 Instrument Power-up.

corder executes multiple hardware tests at initial
start-up. These hardware tests are referred to as
Start-up Tests. As each test is performed, the sys-
tem displays a "WAIT" message to indicate that a
test is currently in progress. If it passes the current
test, the system will automatically proceed to the
next test. If the system fails the current test, an
error message will display. Be aware, however,
that certain test failures are considered non-
recoverable and will result in a complete shut-down
of the system. These failures require immediate
repair before the recorder can continue to
power-up. Other failures wait for operator acknowl-
edgment.

3.2.2 Start-up Tests.

graphs explain each test performed at initial
start-up along with any possible error messages
and recommended operator actions. Each of these
messages displays briefly as the system passes
each test.
A. Memory Test (RAM) - This routine tests all
volatile (RAM) memory. If this test fails, the unit will
halt, indicating the error, and must be repaired
before further operation is allowed.
B. ROM TEST - A test is performed to verify the
integrity of the system software by computing a 32
bit cyclic redundancy code and comparing this
code with a code stored in EPROM.
Siemens AG C79000-G7374-C211-01
SIREC D Manual
The Re-
The following para-
C. LOAD DATABASE (USER CONFIGURATION)
- Your configuration for the unit is stored in non-
volatile battery-backed memory. This memory con-
sists of two main sections, Profile (System Pa-
rameters) and Data Point Registers (DPR).
1. Blocks - The unit user Profile database is
grouped into blocks. Each block contains setup
parameters related to a particular instrument
function (IE. display, chart, scan, etc.) and is
protected by a checksum. The Points database is
also composed of discreet blocks, each block
containing all the set-up information for a par-
ticular programmed Point. Each point DPR is
protected by a checksum.
2. Bad Checksum - If the recorder finds a bad
checksum in any Profile block during the power-
up load database sequence, it will halt. You are
given a choice of ignoring the problem or per-
forming a Smart or Full initialization. (See Smart
and Full initialization under Initialize Database,
Paragraph 3.2.3D.).
3. Bypassing Initialization - Answering NO to
both "Smart" and "Full" initialization queries
forces the recorder to continue to power-up with
corrupt parameters in the User Profile Database.
This may be successful or the Recorder may
hang up or reset.

4. What To Do In Case of Database Failures -

Failures in the profile database should not occur,
however if this error occurs, a smart initialization
will have the least affect on the user profile data-
base and allow completion of the power-up se-
quence.
5. Bad Checksum in Point - If the recorder finds
a bad checksum in any Point DPR during the
power-up load sequence, it will not issue an error
message. Bad Points are internally flagged as
"CORRUPT". A corrupt DPR may only be cor-
rected by reviewing the associated point via the
display.
Operation
3-1