Fail Safe Control

Fail Safe Control
Software Manual
Release 531
Revision 01 (03/2001)
FS80-531
Copyright, Notices and Trademarks
© 2000 – Honeywell Safety Management Systems B.V.
Release 531
Revision 01 (03/2001)
While this information is presented in good faith and believed to be accurate,

Honeywell Safety Management Systems B.V. disclaims the implied warranties of
merchantability and fitness for a particular purpose and makes no express warranties
except as may be stated in its written agreement with and for its customer.
In no event is Honeywell Safety Management Systems B.V. liable to anyone for any
indirect, special or consequential damages. The information and specifications in this
document are subject to change without notice.
TotalPlant, TDC 3000 and Universal Control Network are U.S. registered trademarks of
Honeywell International Inc.
PlantScape is a trademark of Honeywell International Inc.
FSC, DSS and QMR are trademarks of Honeywell Safety Management Systems B.V.
QuadPm and QPM are pending trademarks of Honeywell Safety Management Systems
B.V
Other brands or product names are trademarks of their respective holders.
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of
Honeywell Safety Management Systems B.V.
TABLE OF CONTENTS
SECTION 1: FSC PRIMER

1.1 Introduction .................................................................................................... 1-1
1.2 FSC System Overview.................................................................................... 1-3
1.3 Standards Compliance and Certification...................................................... 1-8
1.4 Fail Safe Controller Configurations ............................................................ 1-10
1.4.1 Introduction..................................................................................................................... 1-10
1.1.2 Single Central Part and Single I/O ................................................................................. 1-11
1.1.3 Redundant Central Parts and Single I/O........................................................................ 1-12
1.1.4 Redundant Central Parts and Redundant I/O ................................................................ 1-14
1.1.5 Redundant Central Parts with Redundant and Single I/O ............................................. 1-16
1.1.6 Quadruple Modular Redundant (QMR™) Architecture .................................................. 1-18
1.5 FSC Configuration and Programming ........................................................ 1-20
1.6 FSC Main Features ....................................................................................... 1-23
1.6.1 FSC Hardware Modules................................................................................................. 1-23
1.6.2 FSC Diagnostics............................................................................................................. 1-24
1.6.3 Flash-Memory Operation ............................................................................................... 1-25
1.6.4 On-Line Modification (OLM) ........................................................................................... 1-26
1.6.5 Safety Checker............................................................................................................... 1-26
1.6.6 Application Verification................................................................................................... 1-27
1.6.7 Sequence-of-Event Recording (SER) ............................................................................ 1-28
1.6.8 FSC Communication Facilities ....................................................................................... 1-30
1.6.9 FSC Networks ................................................................................................................ 1-31
1.6.10 Simulation....................................................................................................................... 1-32
1.6.11 Alarm Functions ............................................................................................................. 1-33
1.6.12 I/O Signal Forcing........................................................................................................... 1-34
1.6.13 Safety Relation ............................................................................................................... 1-35
1.6.14 Voting ............................................................................................................................. 1-36
1.7 FSC Variables ............................................................................................... 1-38
1.7.1 Variable Types ............................................................................................................... 1-38
1.7.2 Variable Attributes .......................................................................................................... 1-38
1.7.3 Variable Characteristics ................................................................................................. 1-46
1.8 Standard System Variables ......................................................................... 1-49
1.8.1 Introduction..................................................................................................................... 1-49
1.8.2 Pulse Generators ........................................................................................................... 1-49
1.8.3 Real-Time Clock Functions ............................................................................................ 1-50
1.8.4 System Inputs and Outputs............................................................................................ 1-50
1.8.5 System Reset ................................................................................................................. 1-51
1.8.6 Force Enable .................................................................................................................. 1-52
1.8.7 Clock Synchronization Input........................................................................................... 1-52
1.8.8 Secondary Switch-Off .................................................................................................... 1-53
1.8.9 System Markers (Alarm Markers) .................................................................................. 1-54
Software Manual
Table of Contents i
TABLE OF CONTENTS (continued)
SECTION 2: INSTALLATION GUIDE

2.1 Installation Requirements .............................................................................. 2-1
2.2 Serial Interface Module 07177/1/x.................................................................. 2-3
2.3 SCC-07177 Communication Driver................................................................ 2-6
2.3.1 Introduction....................................................................................................................... 2-6
2.3.2 Installing the SCC-07177 Driver....................................................................................... 2-7
2.3.3 Configuring the SCC-07177 Driver .................................................................................. 2-9
2.4 FSC Navigator Packages.............................................................................. 2-11
2.5 Preparing the FSC User Station................................................................... 2-12
2.6 Installing FSC Navigator .............................................................................. 2-14
2.7 Copying PlantScape Messages to PlantScape Server ............................... 2-22
2.8 Error Messages............................................................................................. 2-23
2.9 Uninstalling FSC Navigator.......................................................................... 2-25
SECTION 3: USING FSC NAVIGATOR

3.1 Program Overview .......................................................................................... 3-1
3.2 FSC Navigator Packages................................................................................ 3-4
3.3 Menu Bar ......................................................................................................... 3-5
3.4 Button Bar..................................................................................................... 3-10
3.5 Navigation Area ............................................................................................ 3-11
3.5.1 FSC Project Configuration Screen ................................................................................. 3-12
3.5.2 FSC Safety Compliance Screen .................................................................................... 3-15
3.5.3 FSC On-Line Environment Screen................................................................................. 3-18
3.6 Password Protection .................................................................................... 3-21
3.6.1 Using Passwords............................................................................................................ 3-21
3.6.2 Password Types............................................................................................................. 3-21
3.6.3 Password Maintenance .................................................................................................. 3-22
3.6.4 Passwords in Converted Projects .................................................................................. 3-24
3.7 Communication Port .................................................................................... 3-25
3.8 User and Version Information...................................................................... 3-27
3.9 Working with Projects .................................................................................. 3-28
3.9.1 Creating a New Project .................................................................................................. 3-28
3.9.2 Opening an Existing Project........................................................................................... 3-29
3.9.3 Project Conversion ......................................................................................................... 3-30
3.9.4 Project Files.................................................................................................................... 3-31
Software Manual
ii Table of Contents
SECTION 3: USING FSC NAVIGATOR (continued)

3.10 Symbol Libraries .......................................................................................... 3-32
3.11 Color Settings............................................................................................... 3-34
3.12 Scaling Factor .............................................................................................. 3-38
3.13 Basic Operations in Program Components................................................ 3-40
SECTION 4: SYSTEM CONFIGURATION

4.1 Introduction .................................................................................................... 4-1
4.2 Basic Configuration Procedure..................................................................... 4-2
4.3 System Configuration Menus ........................................................................ 4-3
4.3.1 Menu Structure................................................................................................................. 4-3
4.3.2 Main Menu........................................................................................................................ 4-4
4.3.3 Install Menu ...................................................................................................................... 4-5
4.3.4 Signal Specs Menu .......................................................................................................... 4-8
4.4 General Application Information ................................................................. 4-10
4.5 Basic System Configuration........................................................................ 4-12
4.5.1 Introduction..................................................................................................................... 4-12
4.5.2 Requirement Class......................................................................................................... 4-13
4.5.3 Central Part Configuration.............................................................................................. 4-15
4.5.4 SER Channel Specification ............................................................................................ 4-16
4.5.5 Modbus Base Address Configuration............................................................................. 4-20
4.5.6 Memory Chip Size Configuration ................................................................................... 4-21
4.5.7 Process Safety Time ...................................................................................................... 4-22
4.5.8 Interval Time Between Faults ("Second Fault Timer") ................................................... 4-23
4.5.9 FSC-FSC Communication Configuration ....................................................................... 4-25
4.5.10 Simulation Mode............................................................................................................. 4-26
4.5.11 Memory Type ................................................................................................................. 4-29
4.5.12 Power-On Mode ............................................................................................................. 4-29
4.5.13 On-Line Modification Wanted......................................................................................... 4-30
4.6 Defining the Physical Cabinet Layout......................................................... 4-31
4.7 Installing Modules ........................................................................................ 4-34
4.7.1 Overview ........................................................................................................................ 4-34
4.7.2 Installing a Power Supply Unit (PSU)............................................................................. 4-39
4.7.3 Central Part (CP) Definition............................................................................................ 4-44
4.7.4 Installing a Central Processing Unit (CPU) .................................................................... 4-48
4.7.5 Installing a Watchdog (WD) ........................................................................................... 4-49
4.7.6 Installing a Communication Module (COM) ................................................................... 4-49
4.7.7 Installing a Safety Manager Module (SMM)................................................................... 4-58
4.7.8 Installing a PlantScape Interface Module....................................................................... 4-60
4.7.9 Installing a Diagnostic and Battery Module (DBM) ........................................................ 4-63
4.7.10 Installing a Single Bus Driver (SBD) .............................................................................. 4-66
Software Manual
Table of Contents iii
SECTION 4: SYSTEM CONFIGURATION (continued)

4.7 Installing Modules (continued)
4.7.11 Installing a Vertical Bus Driver (VBD) ............................................................................ 4-66
4.7.12 Installing a Horizontal Bus Driver (HBD) ........................................................................ 4-69
4.7.13 Installing Input and Output Modules (I/O) ...................................................................... 4-71
4.8 Signal Specification...................................................................................... 4-77
4.8.1 Introduction..................................................................................................................... 4-77
4.8.2 Adding Signals ............................................................................................................... 4-79
4.8.3 Browsing Through Signals ............................................................................................. 4-81
4.8.4 Modifying and Deleting Signals...................................................................................... 4-81
4.8.5 Searching for Variables .................................................................................................. 4-84
4.9 Importing and Exporting Variables using dBASE Files ............................. 4-85
4.9.1 Introduction..................................................................................................................... 4-85
4.9.2 dBASE File Format......................................................................................................... 4-86
4.9.3 Writing Variables to a dBASE File.................................................................................. 4-88
4.9.4 Reading Variables from a dBASE File ........................................................................... 4-89
4.10 Hardware Specification ................................................................................ 4-94
4.10.1 Introduction..................................................................................................................... 4-94
4.10.2 Allocation of Inputs and Outputs to I/O Modules............................................................ 4-95
4.10.3 Allocation of Inputs and Outputs to COM Modules ...................................................... 4-101
4.10.4 Automatic Allocation of Variables................................................................................. 4-104
4.10.5 Automatic Allocation of SER Sequence Numbers ....................................................... 4-104
4.10.6 Reviewing Allocations using the <F2> Function Key ................................................... 4-106
4.11 Configuration of Digital Input Signals (I) .................................................. 4-113
4.11.1 Location = 'COM' .......................................................................................................... 4-113
4.11.2 Location = 'FSC' ........................................................................................................... 4-116
4.11.3 Location = 'ANN'........................................................................................................... 4-118
4.11.4 Location = 'SYS' ........................................................................................................... 4-120
4.11.5 Other Locations ............................................................................................................ 4-122
4.12 Configuration of Analog Input Signals (AI)............................................... 4-125
4.12.1 Location = 'SYS' ........................................................................................................... 4-125
4.12.2 Other Locations ............................................................................................................ 4-128
4.13 Configuration of Binary Input Signals (BI)................................................ 4-131
4.13.1 Location = 'COM' .......................................................................................................... 4-131
4.13.2 Location = 'FSC' ........................................................................................................... 4-133
4.13.3 Location = 'MUX' .......................................................................................................... 4-135
4.13.4 Other Locations ............................................................................................................ 4-137
4.14 Configuration of Multiplexer Inputs (XI).................................................... 4-139
4.15 Configuration of Digital Output Signals (O).............................................. 4-142
4.15.1 Location = 'COM' .......................................................................................................... 4-142
4.15.2 Location = 'FSC' ........................................................................................................... 4-144
4.15.3 Location = 'ANN'........................................................................................................... 4-146
4.15.4 Location = 'SYS' ........................................................................................................... 4-148
4.15.5 Other Locations ............................................................................................................ 4-150
Software Manual
iv Table of Contents
SECTION 4: SYSTEM CONFIGURATION (continued)

4.16 Configuration of Analog Output Signals (AO).......................................... 4-152
4.17 Configuration of Binary Output Signals (BO)........................................... 4-154
4.17.1 Location = 'COM'.......................................................................................................... 4-154
4.17.2 Location = 'FSC' ........................................................................................................... 4-157
4.17.3 Location = 'MUX' .......................................................................................................... 4-159
4.17.4 Other Locations ............................................................................................................ 4-161
4.18 Configuration of Multiplexer Outputs (XO) ............................................... 4-163
4.19 Configuration of Markers (M)..................................................................... 4-165
4.20 Configuration of Counters (C) ................................................................... 4-167
4.21 Configuration of Timers (T) ....................................................................... 4-169
4.22 Configuration of Registers (R) .................................................................. 4-171
4.23 Configuration of PIDs (P) ........................................................................... 4-173
4.24 Configuration of Alarms (A)....................................................................... 4-176
4.25 Rebuilding an Application ......................................................................... 4-178
4.25.1 Off-Line Rebuilds.......................................................................................................... 4-178
4.25.2 On-Line Rebuilds.......................................................................................................... 4-179
SECTION 5: EDITING REPORTS AND SER FORMAT

5.1 Introduction .................................................................................................... 5-1
5.2 Layout Editor .................................................................................................. 5-3
5.3 Reports ........................................................................................................... 5-5
5.3.1 Introduction....................................................................................................................... 5-5
5.3.2 Editing Report Files .......................................................................................................... 5-5
5.3.3 Report Text....................................................................................................................... 5-8
5.3.4 Report Header................................................................................................................ 5-11
5.3.5 Time-Based Report Generation ..................................................................................... 5-12
5.3.6 Conditional Report Generation....................................................................................... 5-15
5.3.7 Report Printer Configuration .......................................................................................... 5-17
5.4 SER Format File............................................................................................ 5-20
5.4.1 Introduction..................................................................................................................... 5-20
5.4.2 Editing the SER Format File........................................................................................... 5-20
5.4.3 SER Messages............................................................................................................... 5-22
5.4.4 SER Printer Configuration.............................................................................................. 5-25
5.5 Deleting Files................................................................................................ 5-28
Software Manual
Table of Contents v
SECTION 5: EDITING REPORTS AND SER FORMAT (continued)

5.6 Default SER Event Format ........................................................................... 5-30
5.6.1 Introduction..................................................................................................................... 5-30
5.6.2 Default SER Header....................................................................................................... 5-30
5.6.3 Default Variable Event Format ....................................................................................... 5-30
5.6.4 Standard SER Messages ............................................................................................... 5-34
SECTION 6: FUNCTIONAL LOGIC DIAGRAMS

6.1 Introduction .................................................................................................... 6-1
6.2 FLD Editor Menus ........................................................................................... 6-4
6.2.1 Menu Structure................................................................................................................. 6-4
6.2.2 Main Menu........................................................................................................................ 6-6
6.2.3 Symbol Menu ................................................................................................................... 6-9
6.2.4 Block Menu..................................................................................................................... 6-11
6.3 Getting Started.............................................................................................. 6-12
6.3.1 Starting the Editor........................................................................................................... 6-12
6.3.2 Editor Controls................................................................................................................ 6-14
6.3.3 Working with FLDs ......................................................................................................... 6-15
6.3.4 Working with Individual Symbols.................................................................................... 6-18
6.3.5 Working with Groups of Symbols (Blocks) ..................................................................... 6-22
6.3.6 Drawing Connection Lines ............................................................................................. 6-25
6.3.7 Entering Information ....................................................................................................... 6-27
6.1.8 Selection Lists ................................................................................................................ 6-30
6.4 FLD Types (Block Types) ............................................................................. 6-32
6.5 Title Block ..................................................................................................... 6-35
6.6 Revision Control ........................................................................................... 6-39
6.6.1 FLD Revisions ................................................................................................................ 6-39
6.6.2 Application Revisions ..................................................................................................... 6-41
6.7 Appending Applications............................................................................... 6-43
6.8 FLD Symbols................................................................................................. 6-46
6.8.1 Non-Functional Symbols ................................................................................................ 6-46
6.8.2 Connection Lines............................................................................................................ 6-48
6.8.3 Logical Functions ........................................................................................................... 6-49
6.8.4 Compare Functions ........................................................................................................ 6-53
6.8.5 Calculation Functions ..................................................................................................... 6-55
6.8.6 Mathematical Functions ................................................................................................. 6-56
6.8.7 Counters and Registers.................................................................................................. 6-58
6.8.8 Constants and Signal Conversions ................................................................................ 6-60
6.8.9 Function Blocks .............................................................................................................. 6-61
6.8.10 Equation Blocks.............................................................................................................. 6-62
6.8.11 PIDs................................................................................................................................ 6-63
6.8.12 Time Functions............................................................................................................... 6-64
Software Manual
vi Table of Contents
SECTION 6: FUNCTIONAL LOGIC DIAGRAMS (continued)

6.8 FLD Symbols (continued)
6.8.13 I/O Symbols.................................................................................................................... 6-69
6.8.14 Sheet Transfers.............................................................................................................. 6-73
6.8.15 Flip-Flops........................................................................................................................ 6-77
6.8.16 Texts............................................................................................................................... 6-78
6.9 Design Considerations ................................................................................ 6-79
6.9.1 Logical Functions, Compare, and Calculation Functions............................................... 6-79
6.9.2 Counters, Registers, and Constants .............................................................................. 6-79
6.9.3 Signal Conversions ........................................................................................................ 6-80
6.9.4 Function Blocks .............................................................................................................. 6-81
6.9.5 Equation Blocks ............................................................................................................. 6-82
6.9.6 Timers ............................................................................................................................ 6-85
6.9.7 PIDs................................................................................................................................ 6-88
6.9.8 Inputs and Outputs ......................................................................................................... 6-88
6.9.9 Sheet References........................................................................................................... 6-90
6.9.10 Flip-Flops and Pulses..................................................................................................... 6-91
6.10 Sheet Transfers ............................................................................................ 6-92
6.10.1 Characteristics................................................................................................................ 6-92
6.10.2 Off-Sheet Transfers........................................................................................................ 6-94
6.10.3 On-Sheet Transfers........................................................................................................ 6-97
6.10.4 Selecting a Sheet Transfer Symbol Using a Selection List............................................ 6-99
6.11 FLD Formats ............................................................................................... 6-100
6.12 Error Messages .......................................................................................... 6-104
SECTION 7: PRINTING
7.1 Introduction .................................................................................................... 7-1
7.2 Printing the Project Configuration ................................................................ 7-2
7.2.1 Introduction....................................................................................................................... 7-2
7.2.2 Selecting the Item for Printing .......................................................................................... 7-3
7.2.3 Previewing the Printer Output .......................................................................................... 7-4
7.2.4 Setting the Page Options ................................................................................................. 7-6
7.2.5 The First Page of All Printouts ......................................................................................... 7-7
7.2.6 Jumper Settings ............................................................................................................... 7-8
7.2.7 Installation Descriptions ................................................................................................... 7-9
7.2.8 Allocation of Hardware Modules .................................................................................... 7-10
7.2.9 Allocation Errors ............................................................................................................. 7-11
7.2.10 I/O Checklist ................................................................................................................... 7-12
7.2.11 Tag Number Allocations: Per I/O Module ...................................................................... 7-13
7.2.12 Tag Number Allocations: Per Rack ................................................................................ 7-14
7.2.13 Tag Number Allocations: Alphabetical/Loop Number .................................................... 7-17
7.2.14 Communication Configuration........................................................................................ 7-21
7.2.15 Alarm Configuration ....................................................................................................... 7-22
7.2.16 Graphic Rack Layout...................................................................................................... 7-23
Software Manual
Table of Contents vii
SECTION 7: PRINTING (continued)

7.3 Printing Functional Logic Diagrams............................................................ 7-25
7.3.1 Introduction..................................................................................................................... 7-25
7.3.2 Selecting FLDs for Printing............................................................................................. 7-27
7.3.3 Setting the Printing Options ........................................................................................... 7-28
7.3.4 Setting the Page Options ............................................................................................... 7-29
7.3.5 Previewing the FLD Output ............................................................................................ 7-30
SECTION 8: TRANSLATING AN APPLICATION

8.1 Introduction .................................................................................................... 8-1
8.2 Prerequisites................................................................................................... 8-2
8.3 Compiler Operation ........................................................................................ 8-3
8.3.1 Translation Process.......................................................................................................... 8-3
8.3.2 Output Files ...................................................................................................................... 8-4
8.3.3 Compiler Registers and Markers...................................................................................... 8-6
8.3.4 Simulation Mode............................................................................................................... 8-6
8.4 Error Messages and Warnings ...................................................................... 8-8
SECTION 9: LOG FILES

9.1 Introduction .................................................................................................... 9-1
9.2 Selecting a Log File ........................................................................................ 9-3
9.3 Log File Viewer ............................................................................................... 9-4
9.3.1 Viewing a Log File ............................................................................................................ 9-4
9.3.2 Font Type and Size .......................................................................................................... 9-5
9.3.3 Printing a Log File ............................................................................................................ 9-7
9.3.4 Saving a Log File to Disk ................................................................................................. 9-8
SECTION 10: LOADING SOFTWARE

10.1 Introduction .................................................................................................. 10-1
10.2 Loading Methods.......................................................................................... 10-3
10.2.1 Downloading vs. EPROMs ............................................................................................. 10-3
10.2.2 Module Support .............................................................................................................. 10-3
10.3 Downloading to Memory .............................................................................. 10-5
10.3.1 Introduction..................................................................................................................... 10-5
10.3.2 Important Considerations for Downloading to Memory.................................................. 10-5
10.3.3 Basic Download Procedure ............................................................................................ 10-7
10.3.4 Starting the Download Option ........................................................................................ 10-8
10.3.5 Selecting the Central Part for Downloading ................................................................. 10-10
Software Manual
viii Table of Contents
SECTION 10: LOADING SOFTWARE (continued)

10.3 Downloading to Memory (continued)
10.3.6 Download Screen (RAM Mode) ................................................................................... 10-11
10.3.7 Download Screen (Flash Memory Mode) .................................................................... 10-12
10.3.8 Shutting Down the Central Part.................................................................................... 10-13
10.3.9 Download Menu ........................................................................................................... 10-15
10.3.10 Switching Between Central Parts................................................................................. 10-16
10.3.11 Download Matrix (Flash Memory Mode) ...................................................................... 10-17
10.3.12 Download Dependencies ............................................................................................. 10-21
10.3.13 Configured Hardware vs. Detected Hardware ............................................................. 10-21
10.3.14 Downloading to Flash Memory..................................................................................... 10-22
10.3.15 Downloading to RAM ................................................................................................... 10-24
10.3.16 After the Download....................................................................................................... 10-25
10.4 Programming EPROMs .............................................................................. 10-30
10.4.1 Introduction................................................................................................................... 10-30
10.4.2 Important Considerations for Programming EPROMs ................................................. 10-30
10.4.3 Starting the EPROM Programming Option .................................................................. 10-31
10.4.4 Main Menu.................................................................................................................... 10-33
10.4.5 Setting the Programming Options ................................................................................ 10-35
10.4.6 Programming EPROMs................................................................................................ 10-37
10.4.7 Reading EPROMs ........................................................................................................ 10-38
10.4.8 Blank-Checking EPROMs ............................................................................................ 10-39
10.4.9 Verifying EPROMs ....................................................................................................... 10-40
10.5 EPROM Programming Algorithms ............................................................ 10-41
10.5.1 Intel Intelligent Algorithm.............................................................................................. 10-41
10.5.2 Intel Quick Pulse Algorithm .......................................................................................... 10-41
10.5.3 Flash Algorithm ............................................................................................................ 10-42
10.6 Supported EPROMs ................................................................................... 10-43
10.7 Error Messages .......................................................................................... 10-44
SECTION 11: VERIFYING AN APPLICATION

11.1 Introduction .................................................................................................. 11-1
11.2 Verification Process ..................................................................................... 11-3
11.3 Verification of FSC Application Using the FSC Database ......................... 11-5
11.4 Verification of FSC Application Software Using the Functional Logic
Diagrams....................................................................................................... 11-7
11.5 Revision Control........................................................................................... 11-8
11.6 Error Messages .......................................................................................... 11-10
11.6.1 Introduction................................................................................................................... 11-10
11.6.2 Common Error Messages ............................................................................................ 11-10
11.6.3 Error Messages for Verification Using the FSC Database........................................... 11-13
11.6.4 Error Messages for Verification Using FLDs................................................................ 11-14
Software Manual
Table of Contents ix
SECTION 12: ON-LINE ENVIRONMENT

12.1 Introduction .................................................................................................. 12-1
12.1.1 Overview......................................................................................................................... 12-1
12.1.3 On-Line vs. Off-Line Menu ............................................................................................. 12-3
12.1.4 Date and Time Format ................................................................................................... 12-4
12.2 Off-Line Menu ............................................................................................... 12-5
12.3 On-Line Menu................................................................................................ 12-7
12.4 'FSC System' Menu..................................................................................... 12-11
12.4.1 Introduction................................................................................................................... 12-11
12.4.2 'Sys Info' Submenu....................................................................................................... 12-12
12.4.3 'Inputs' Submenu.......................................................................................................... 12-14
12.4.4 'Outputs' Submenu ....................................................................................................... 12-16
12.4.5 'Diag to Disk' Submenu ................................................................................................ 12-17
12.5 'Process Status' Menu................................................................................ 12-19
12.5.1 Introduction................................................................................................................... 12-19
12.5.2 'FLD' Submenu............................................................................................................. 12-20
12.5.3 'Var Status' Submenu................................................................................................... 12-21
12.6 Selecting an Application to Monitor .......................................................... 12-23
12.7 Retrieving FSC System Information .......................................................... 12-24
12.7.1 Introduction................................................................................................................... 12-24
12.7.2 Viewing Configuration Parameters............................................................................... 12-24
12.7.3 Viewing Software Version Information ......................................................................... 12-25
12.7.4 Reading the DBM Status.............................................................................................. 12-27
12.7.5 Setting the Real-Time Clock ........................................................................................ 12-29
12.7.6 Viewing Communication Statistics ............................................................................... 12-30
12.8 Monitoring the I/O Status ........................................................................... 12-32
12.8.1 Introduction................................................................................................................... 12-32
12.8.2 Monitoring Individual Inputs and Outputs..................................................................... 12-32
12.8.3 Selecting an Input/Output by Position or Tag Number................................................. 12-36
12.8.4 Viewing 'High' or 'Low' Inputs ....................................................................................... 12-38
12.8.5 Monitoring Inputs for Status Changes.......................................................................... 12-39
12.9 Monitoring the Process and Variable Status ............................................ 12-40
12.9.1 Introduction................................................................................................................... 12-40
12.9.2 Monitoring the Status of FLDs...................................................................................... 12-41
12.9.3 Monitoring the Status of All Variables in an FLD ......................................................... 12-45
12.9.4 Monitoring the Status of Selected Variables ................................................................ 12-47
12.9.5 Monitoring the Status of Variables by Type ................................................................. 12-49
12.9.6 Working with Variable Status Screens ......................................................................... 12-50
12.9.7 Rebuilding the Screen File ........................................................................................... 12-51
12.10 Viewing the I/O Loop Status ...................................................................... 12-53
12.10.1 Loop Status for the Entire Application.......................................................................... 12-53
12.10.2 Loop Status for the Selected Central Part.................................................................... 12-55
Software Manual
x Table of Contents
SECTION 12: ON-LINE ENVIRONMENT (continued)

12.11 Forcing Inputs and Outputs....................................................................... 12-57
12.11.1 Introduction................................................................................................................... 12-57
12.11.2 Setting a Force ............................................................................................................. 12-57
12.11.3 Clearing Individual Forces............................................................................................ 12-60
12.11.4 Clearing All Forces ....................................................................................................... 12-62
12.11.5 Listing the Forced Variables......................................................................................... 12-62
12.12 Writing to Inputs and Outputs ................................................................... 12-64
12.13 Calibrating Analog Inputs and Outputs .................................................... 12-66
12.13.1 Calibrating Analog Inputs ............................................................................................. 12-66
12.13.2 Calibrating Analog Outputs .......................................................................................... 12-70
12.14 Working with PIDs...................................................................................... 12-72
12.14.1 Viewing the PID Status ................................................................................................ 12-72
12.14.2 Adjusting PIDs.............................................................................................................. 12-75
12.15 Working with System Diagnostics ............................................................ 12-78
12.15.1 Introduction................................................................................................................... 12-78
12.15.2 Retrieving Diagnostics from the FSC System.............................................................. 12-79
12.15.3 Selecting the FSC System(s) for Diagnostics Retrieval............................................... 12-81
12.15.4 Retrieving Diagnostics Continuously............................................................................ 12-82
12.15.5 Reading Diagnostic Information from Hard Disk.......................................................... 12-83
12.15.6 Backing Up the Diagnostics Message File................................................................... 12-84
12.16 Extended Diagnostic Messages ................................................................ 12-86
12.16.1 Introduction................................................................................................................... 12-86
12.16.2 Messages Not Related to Specific Hardware Modules................................................ 12-87
12.16.3 Vertical Bus Drivers (10001/1/1, 10001/R/1) ............................................................... 12-91
12.16.4 Central Processing Units (10002/1/2, 10012/1/2, 10020/1/1)...................................... 12-92
12.16.5 Communication Modules (10004/./., 10014/./., 10024/./., 10008/2/U, 10008/3/P,
10018/2/U).................................................................................................................... 12-94
12.16.6 PlantScape Interface Modules (10018/E/E, 10018/E/1) .............................................. 12-97
12.16.7 Watchdog Modules (10005/1/1) ................................................................................... 12-98
12.16.8 Diagnostic and Battery Modules (10006/./.)................................................................. 12-99
12.16.9 Single Bus Drivers (10007/1/1) .................................................................................... 12-99
12.16.10 Horizontal Bus Drivers (10100/./.) .............................................................................. 12-100
12.16.11 Digital Input Modules 10101/./.................................................................................... 12-100
12.16.12 Analog Input Modules 10102/./. ................................................................................. 12-101
12.16.13 Analog Input Module 10105/2/1 ................................................................................. 12-101
12.16.14 Digital Input Module 10106/2/1 .................................................................................. 12-102
12.16.15 Digital Output Modules 10201/./................................................................................. 12-103
12.16.16 Digital Output Module 10203/1/2................................................................................ 12-104
12.16.17 Analog Output Modules 10205/./................................................................................ 12-104
12.16.23 Watchdog Repeater Modules (10302/./.) ................................................................... 12-108
Software Manual
Table of Contents xi
SECTION 12: ON-LINE ENVIRONMENT (continued)

12.17 Error Messages......................................................................................... 12-109
SECTION 13: SAFETY CHECKER

13.1 Introduction .................................................................................................. 13-1
13.2 Safety Checker Operation ............................................................................ 13-3
13.3 Reviewing Safety Inconsistencies............................................................... 13-6
13.4 Log File.......................................................................................................... 13-7
13.5 Safety Relation of FLD Symbols.................................................................. 13-8
13.5.2 Compare Functions ...................................................................................................... 13-10
13.5.3 Calculation Functions ................................................................................................... 13-12
13.5.4 Mathematical Functions ............................................................................................... 13-13
13.5.5 Counters and Registers................................................................................................ 13-14
13.5.6 Constants and Signal Conversions .............................................................................. 13-15
13.5.7 Function Blocks ............................................................................................................ 13-15
13.5.8 Equation Blocks............................................................................................................ 13-16
13.5.9 PIDs.............................................................................................................................. 13-16
13.5.10 Timers .......................................................................................................................... 13-16
13.5.11 I/O Symbols .................................................................................................................. 13-18
13.5.12 Flip-Flops...................................................................................................................... 13-19
13.6 Error Messages........................................................................................... 13-20
APPENDIX A: ALARM FUNCTIONS

A.1 Introduction ................................................................................................... A-1
A.2 Alarm Types ................................................................................................... A-3
A.3 Alarm Sequences .......................................................................................... A-6
A.3.1 Alarm Symbols .................................................................................................................A-6
A.3.2 Alarm Sequence AF: Basic Flashing................................................................................A-7
A.3.3 Alarm Sequence AM: Manual Lamp Reset ......................................................................A-7
A.3.4 Alarm Sequence FR: Flasher Reset ................................................................................A-8
A.3.5 Alarm Sequence FRM: Flasher/Lamp Reset ...................................................................A-9
A.3.6 Alarm Sequence AR: Ringback........................................................................................A-9
A.3.7 Alarm Sequence ARR: Double Audible Ringback .........................................................A-10
A.3.8 Alarm Sequences TFS, TFS_COM1, and TFS_COM2: First Up Indication ..................A-11
A.4 Alarm Configuration Examples....................................................................A-13
A.4.1 AF Alarm Configuration ..................................................................................................A-13
A.4.2 First Up Alarm Configuration Via Communication Links ................................................A-18
A.4.3 Flasher for Alarm Functions ...........................................................................................A-21
Software Manual
xii Table of Contents
APPENDIX B: SEQUENCE-OF-EVENT RECORDING

B.1 Introduction ....................................................................................................B-1
B.2 Sequence-of-Event Recording to FSCSOE...................................................B-3
B.2.1 Introduction.......................................................................................................................B-3
B.2.2 Configuration ....................................................................................................................B-4
B.3 Sequence-of-Event Recording to PlantScape ..............................................B-6
B.3.1 Introduction.......................................................................................................................B-6
B.4 Sequence-of-Event Recording to a Modbus Device ....................................B-9
B.4.1 Introduction.......................................................................................................................B-9
B.4.3 Reading the SER Event Records...................................................................................B-10
B.5 Sequence-of-Event Recording to a Printer .................................................B-13
B.5.1 Introduction.....................................................................................................................B-13
B.5.2 Configuration ..................................................................................................................B-13
B.6 Numerical SER..............................................................................................B-15
B.6.1 Introduction.....................................................................................................................B-15
B.6.2 Configuring the SER Channel ........................................................................................B-16
B.6.3 Setting the SER Range ..................................................................................................B-18
B.6.4 SER-Enabling of FSC Variables ....................................................................................B-19
B.7 Text SER .......................................................................................................B-21
B.7.1 Introduction.....................................................................................................................B-21
B.7.3 Specifying the Printer Type ............................................................................................B-22
B.8 Event Specification ......................................................................................B-26
B.8.1 Variable Events ..............................................................................................................B-26
B.8.2 Force Events ..................................................................................................................B-29
B.8.3 Fault Events ...................................................................................................................B-29
B.9 SER Characteristics .....................................................................................B-30
B.9.1 SER Resolution ..............................................................................................................B-30
B.9.2 SER Buffer Capacity ......................................................................................................B-30
B.9.3 SER Format....................................................................................................................B-31
B.10 SER Channel Specification..........................................................................B-32
B.10.1 SER Channels in Communication Networks..................................................................B-32
B.10.2 Single SER Channel ......................................................................................................B-35
B.10.3 Redundant SER Channels .............................................................................................B-35
B.10.4 Dual SER Channels .......................................................................................................B-36
B.10.5 SER Channel Availability ...............................................................................................B-36
Software Manual
Table of Contents xiii
APPENDIX C: SAFETY-RELATED INPUTS WITH NON FAIL-SAFE SENSORS

C.1 Introduction ................................................................................................... C-1
C.2 Safety-Related Digital Inputs with Non Fail-Safe Sensors.......................... C-3
C.2.1 FSC Systems with Single Central Part............................................................................ C-3
C.2.2 FSC Systems with Redundant Central Parts .................................................................. C-5
C.3 Safety-Related Analog Inputs with Non Fail-Safe Transmitters ................. C-8
C.3.1 FSC Systems with Single Central Part............................................................................ C-8
C.3.2 FSC Systems with Redundant Central Parts ................................................................ C-11
C.4 Function Blocks........................................................................................... C-14
APPENDIX D: ON-LINE MODIFICATION

D.1 Introduction ................................................................................................... D-1
D.2 Important Considerations ............................................................................. D-2
D.2.1 FSC Navigator Functionality............................................................................................ D-2
D.2.2 Limitations ....................................................................................................................... D-2
D.2.3 Sheet Differences............................................................................................................ D-3
D.3 Preparations................................................................................................... D-4
D.3.1 Installation Tools ............................................................................................................. D-4
D.3.2 Preparing EPROMs......................................................................................................... D-4
D.3.3 Electrostatic Discharge (ESD)......................................................................................... D-5
D.4 Procedure Overview ...................................................................................... D-7
D.5 Preparing the On-Line Modification ........................................................... D-11
D.5.1 Overview........................................................................................................................ D-11
D.5.2 Verifying TPS Compatibility With FSC System Software.............................................. D-11
D.5.3 Comparing Applications in FSC System and User Station ........................................... D-13
D.5.4 Making a Backup of the Application Files ..................................................................... D-14
D.5.5 Verifying the On-Line Modification Option..................................................................... D-15
D.6 Modifying the Application ........................................................................... D-17
D.6.1 Overview........................................................................................................................ D-17
D.6.2 Making the Required Modifications to the Application .................................................. D-17
D.6.3 Translating the Application ............................................................................................ D-18
D.6.4 Programming EPROMs................................................................................................. D-19
D.6.5 Making a Backup of the Modified Application Files....................................................... D-20
D.7 Upgrading the FSC System (FLASH Mode) ............................................... D-21
D.7.1 Overview........................................................................................................................ D-21
D.7.2 Checking the System .................................................................................................... D-22
D.7.3 Shutting Down Central Part 1........................................................................................ D-23
D.7.4 Downloading the Software for Central Part 1................................................................ D-24
D.7.5 Reloading the Personality Image (PI) for Central Part 1............................................... D-27
D.7.6 Starting Up Central Part 1 ............................................................................................. D-28
Software Manual
xiv Table of Contents
APPENDIX D: ON-LINE MODIFICATION (continued)

D.7 Upgrading the FSC System (FLASH Mode) (continued)
D.7.7 Shutting Down Central Part 2.........................................................................................D-29
D.7.8 Downloading the Software for Central Part 2.................................................................D-30
D.7.9 Reloading the Personality Image (PI) for Central Part 2................................................D-31
D.7.10 Starting Up Central Part 2 ..............................................................................................D-32
D.7.11 Making a Backup of the Modified Application Files........................................................D-33
D.8 Upgrading the FSC System (RAM Mode)....................................................D-34
D.8.1 Overview ........................................................................................................................D-34
D.8.2 Checking the System .....................................................................................................D-35
D.8.4 Exchanging the CPU System EPROMs in Central Part 1..............................................D-37
D.8.5 Exchanging the Communication EPROMs in Central Part 1 .........................................D-39
D.8.6 Exchanging the FSC-SMM EPROM in Central Part 1 ...................................................D-40
D.8.7 Downloading the CPU Application Program in Central Part 1 .......................................D-41
D.8.11 Exchanging the CPU System EPROMs in Central Part 2..............................................D-48
D.8.14 Downloading the CPU Application Program in Central Part 2 .......................................D-52
D.9 Upgrading the FSC System (EPROM Mode) ...............................................D-58
D.9.1 Overview ........................................................................................................................D-58
D.9.4 Exchanging the CPU EPROMs in Central Part 1...........................................................D-61
D.9.7 Preparing Central Part 1 for Start-Up.............................................................................D-65
D.9.11 Exchanging the CPU EPROMs in Central Part 2...........................................................D-69
D.9.14 Preparing Central Part 2 for Start-Up.............................................................................D-73
D.10 Extended Diagnostics During OLM.............................................................D-76
D.10.1 Overview ........................................................................................................................D-76
D.10.2 Compatibility Check .......................................................................................................D-77
D.10.3 FSC Networks ................................................................................................................D-78
Software Manual
Table of Contents xv
APPENDIX D: ON-LINE MODIFICATION (continued)

D.11 Error Diagnostics ........................................................................................ D-79
D.11.1 Diagnostics Relating to Internal On-Line Modification Check ....................................... D-79
D.11.2 Diagnostics Relating to FSC Network Configuration Check ......................................... D-81
D.12 On-Line Rebuild........................................................................................... D-82
D.13 Modifying Tag Numbers On-Line................................................................ D-84
D.13.1 Input Tag Numbers........................................................................................................ D-84
D.13.2 Output Tag Numbers..................................................................................................... D-86
APPENDIX E: PID CONTROLLERS

E.1 Introduction ....................................................................................................E-1
E.2 Theoretical Approach.....................................................................................E-3
E.3 Configuration and Implementation of PID Controllers in the
FSC System.....................................................................................................E-6
E.4 Practical Application of PIDs .........................................................................E-8
APPENDIX F: COMMUNICATION
F.1 Introduction ....................................................................................................F-1
F.2 Definitions.......................................................................................................F-2
F.3 Communication with the TotalPlant Solution (TPS) System .......................F-5
F.4 Communication with the PlantScape System...............................................F-6
F.4.1 Introduction.......................................................................................................................F-6
F.4.2 Architecture ......................................................................................................................F-7
F.4.3 Hardware ..........................................................................................................................F-8
F.4.4 Sequence-of-Event (SOE) Data.......................................................................................F-8
F.4.5 Extended Diagnostics and System Events ......................................................................F-8
F.4.6 Communication Redundancy ...........................................................................................F-9
F.5 Communication with Distributed Control Systems (DCSs) Using
the Modbus Protocol .................................................................................... F-10
F.5.1 Introduction.....................................................................................................................F-10
F.5.2 Supported Networks.......................................................................................................F-11
F.5.3 Data Exchange...............................................................................................................F-11
F.5.4 Supported Function and Error Codes ............................................................................F-13
F.5.5 Real-Time Clock Synchronization ..................................................................................F-14
F.5.6 Addressing .....................................................................................................................F-15
F.5.7 Response Times ............................................................................................................F-17
F.5.8 Fault Handling ................................................................................................................F-18
F.5.9 Link Types and Baud Rates ...........................................................................................F-19
F.5.10 Cable Lengths ................................................................................................................F-20
F.5.11 Modbus for Communication with Contronic E/P ............................................................F-21
Software Manual
xvi Table of Contents
APPENDIX F: COMMUNICATION (continued)

the RKE3964R Protocol ............................................................................... F-22
F.6.1 Introduction..................................................................................................................... F-22
F.6.2 Supported Networks....................................................................................................... F-23
F.6.3 Data Exchange............................................................................................................... F-24
F.6.4 Timeouts......................................................................................................................... F-26
F.6.5 Supported Commands and Error Messages.................................................................. F-26
F.6.6 Real-Time Clock Synchronization .................................................................................. F-27
F.6.7 Block Definition............................................................................................................... F-28
F.6.9 Fault Handling ................................................................................................................ F-32
F.6.10 Link Types and Baud Rates ........................................................................................... F-33
F.6.11 Cable Lengths ................................................................................................................ F-34
F.7 Communication Between FSC Systems Using the FSC-FSC Protocol..... F-35
F.7.1 Introduction..................................................................................................................... F-35
F.7.3 Data Exchange............................................................................................................... F-37
F.7.4 Timeouts......................................................................................................................... F-38
F.7.7 Configuration .................................................................................................................. F-40
F.7.8 Copying Allocations to Ensure Consistency of Connected Systems ............................. F-44
F.7.10 Cable Lengths ................................................................................................................ F-46
F.8 Communication Between FSC Systems Using the RKE3964R Protocol .. F-47
F.8.1 Introduction..................................................................................................................... F-47
F.8.3 Data Exchange............................................................................................................... F-49
F.8.4 Timeouts......................................................................................................................... F-51
F.8.11 Cable Lengths ................................................................................................................ F-58
F.9 Communication With the FSC User Station Using the Development System
(DS) Protocol ................................................................................................ F-59
F.9.1 Introduction..................................................................................................................... F-59
F.9.3 Data Exchange............................................................................................................... F-60
F.9.6 Cable Lengths ................................................................................................................ F-62
Software Manual
Table of Contents xvii
APPENDIX F: COMMUNICATION (continued)

F.10 Communication With the FSC User Station Using a Modem..................... F-63
F.10.1 Using a Modem ..............................................................................................................F-63
F.10.2 Configuring a Modem Channel in the Application..........................................................F-64
F.10.3 Configuration Requirements ..........................................................................................F-65
F.10.4 Establishing a Modem Link ............................................................................................F-66
F.10.5 Direct Control .................................................................................................................F-68
F.11 Output to Printers Using the Printer Protocol ............................................ F-70
F.11.1 Introduction.....................................................................................................................F-70
F.11.3 Data Exchange...............................................................................................................F-70
F.11.4 SER Printing...................................................................................................................F-71
F.11.5 Reports Printing..............................................................................................................F-72
F.11.7 Handshaking ..................................................................................................................F-73
F.11.9 Cable Lengths ................................................................................................................F-75
F.12 Real-Time Clock Synchronization ............................................................... F-76
F.12.1 Introduction.....................................................................................................................F-76
F.12.2 Synchronization Priorities...............................................................................................F-76
F.12.3 Multiple Synchronization Sources ..................................................................................F-78
F.12.4 Synchronization Commands from Time Sources...........................................................F-79
APPENDIX G: FSC MULTIPLEXERS

G.1 Introduction ................................................................................................... G-1
G.2 Output Multiplexers ....................................................................................... G-3
G.3 Input Multiplexers .......................................................................................... G-5
G.4 Multiple I/O That Uses Multiplexers.............................................................. G-7
G.5 Configuring Multiplexers............................................................................... G-8
G.5.1 Multiplexers ..................................................................................................................... G-8
G.5.2 Multiplexed I/O .............................................................................................................. G-10
G.6 Using Multiplexers....................................................................................... G-13
Software Manual
xviii Table of Contents
APPENDIX H: SIMULATION MODE

H.1 Introduction ....................................................................................................H-1
H.2 Using Simulation Mode..................................................................................H-2
H.2.1 Introduction.......................................................................................................................H-2
H.2.2 Specifying the Simulation Unit .........................................................................................H-2
H.2.3 Defining the Communication Channel Assignment..........................................................H-5
H.2.4 Translating the Simulated Application..............................................................................H-6
H.2.5 Loading the Simulated Application into the Simulation Unit ............................................H-6
H.2.6 Using the On-Line Environment to Simulate the Application ...........................................H-7
H.2.7 Considerations .................................................................................................................H-7
H.3 Hardware Layout of Simulation/Training Units ............................................H-8
H.3.1 Single-Rack FSC Unit 23260/4/1 (EPM, ECM, Flash Memory) .......................................H-8
H.3.2 Single-Rack FSC Unit 23260/4/2 (EPM, ECM, Flash Memory, FSC-SMM) ..................H-10
H.3.3 Single-Rack FSC Unit 23260/4/3 (EPM, ECM, Flash Memory, PlantScape) ................H-12
H.3.4 Single FSC Unit 23250/4/1 (EPM, ECM, Flash Memory) ..............................................H-14
H.3.5 Single FSC Unit 23250/4/2 (ECM, EPM, Flash Memory, FSC-SMM) ...........................H-16
H.3.6 Single FSC Unit 23250/4/3 (Flash Memory, PlantScape)..............................................H-18
H.3.7 Redundant FSC Unit 23270/4/1 (EPM, ECM, Flash Memory).......................................H-20
H.3.8 Redundant FSC Unit 23270/4/2 (Flash Memory, FSC-SMM)........................................H-22
H.3.9 Redundant FSC Unit 23270/4/3 (EPM, ECM, Flash Memory, PlantScape) ..................H-24
H.3.10 Single-Rack FSC Unit 23260/3/1 (Flash Memory).........................................................H-26
H.3.11 Single-Rack FSC Unit 23260/3/2 (Flash Memory, FSC-SMM) ......................................H-27
H.3.12 Single-Rack FSC Unit 23260/3/3 (Flash Memory, PlantScape) ....................................H-29
H.3.13 Single FSC Unit 23250/3/1 (Flash Memory) ..................................................................H-31
H.3.14 Single FSC Unit 23250/3/2 (Flash Memory, FSC-SMM) ...............................................H-33
H.3.16 Redundant FSC Unit 23270/3/1 (Flash Memory)...........................................................H-37
H.3.18 Redundant FSC Unit 23270/3/3 (Flash Memory, PlantScape) ......................................H-41
H.3.19 Single-Rack FSC Unit 23260/1/1 (EPROMs/RAM)........................................................H-43
H.3.20 Single-Rack FSC Unit 23260/2/1 (EPROMs/RAM, FSC-SMM).....................................H-44
H.3.21 Single FSC Unit 23250/1/1 (EPROMs/RAM) .................................................................H-45
H.3.22 Single FSC Unit 23250/2/1 (EPROMs/RAM, FSC-SMM) ..............................................H-47
H.3.23 Redundant FSC Unit 23251/1/1 (EPROMs/RAM) .........................................................H-49
H.3.24 Redundant FSC Unit 23270/2/1 (EPROMs/RAM, FSC-SMM) ......................................H-51
Software Manual
Table of Contents xix
REFERENCES
FSC Documentation:
Publication Publication
Title Number
FSC Safety Manual R531 FS90-531
FSC Software Manual R531 FS80-531
FSC Hardware Manual FS02-500
FSC Obsolete Modules FS02-501
FSC Service Manual FS99-504
FSCSOE Documentation:
Title Number
FSCSOE – Basic Version FS50-xxx*
FSCSOE – Network Option FS51-xxx*
FSCSOE – Foxboro I/A Interface Option FS52-xxx*
FSCSOE – Yokogawa CS Interface Option FS53-xxx*
FSCSOE – Ronan Interface Option FS55-xxx*

* 'xxx' is the release number. For example, the manuals for FSCSOE R130 are referred to
as FS50-130, FS51-130, etc.
FSC-SM Documentation:
Title Number
FSC Safety Manager Installation Guide FS20-500
FSC Safety Manager Implementation Guidelines FS11-500
FSC Safety Manager Control Functions FS09-500
FSC Safety Manager Parameter Reference Dictionary FS09-550
FSC Safety Manager Configuration Forms FS88-500
FSC Safety Manager Service Manual FS13-500
Software Manual
xx Table of Contents
READER COMMENTS
Honeywell Safety Management Systems welcomes your comments and suggestions to improve future editions of this
and other documents.
You can communicate your thoughts to us by fax or mail using this form, or by sending an e-mail message. We would
like to acknowledge your comments — please include your complete name, address and telephone number.
BY FAX: Use this form and fax to us at +31 (0)73-6219125 (attn. Worldwide Marketing dept.)
BY E-MAIL: Send an e-mail message to sms-info@honeywell.com

BY MAIL: Use this form and mail to us at:
Attn. Worldwide Marketing Department
P.O. Box 116
5201 AC 's-Hertogenbosch
The Netherlands
Title of Document: Fail Safe Control Issue Date: 03/2001

Software Manual
Release 531 Rev. 01
Document Number: FS80-531 Writer: HSMS Worldwide Marketing
COMMENTS:
RECOMMENDATIONS:
Name: Date:
Position:
Company:
Address:
Country:
Telephone: Fax:
E-mail address:
.
Fail Safe Control
Section 1:
FSC Primer
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

Quad PM and QPM are pending trademarks of Honeywell Safety Management Systems
B.V.
TABLE OF CONTENTS
Section 1: FSC Primer
1.1 Introduction .................................................................................................... 1-1
1.2 FSC System Overview.................................................................................... 1-3
1.3 Standards Compliance and Certification...................................................... 1-8
1.4 Fail Safe Controller Configurations ............................................................ 1-10

1.4.1 Introduction..................................................................................................................... 1-10
1.1.2 Single Central Part and Single I/O ................................................................................. 1-11
1.1.3 Redundant Central Parts and Single I/O........................................................................ 1-12
1.1.4 Redundant Central Parts and Redundant I/O ................................................................ 1-14
1.1.5 Redundant Central Parts with Redundant and Single I/O ............................................. 1-16
1.1.6 Quadruple Modular Redundant (QMR™) Architecture .................................................. 1-18
1.5 FSC Architecture and Programming........................................................... 1-20
1.6 FSC Main Features ....................................................................................... 1-23

1.6.1 FSC Hardware Modules................................................................................................. 1-23
1.6.2 FSC Diagnostics............................................................................................................. 1-24
1.6.3 Flash-Memory Operation ............................................................................................... 1-25
1.6.4 On-Line Modification (OLM) ........................................................................................... 1-26
1.6.5 Safety Checker............................................................................................................... 1-26
1.6.6 Application Verification................................................................................................... 1-27
1.6.7 Sequence-of-Event Recording (SER) ............................................................................ 1-28
1.6.8 FSC Communication Facilities ....................................................................................... 1-30
1.6.9 FSC Networks ................................................................................................................ 1-31
1.6.10 Simulation....................................................................................................................... 1-32
1.6.11 Alarm Functions ............................................................................................................. 1-33
1.6.12 I/O Signal Forcing........................................................................................................... 1-34
1.6.13 Safety Relation ............................................................................................................... 1-35
1.6.14 Voting ............................................................................................................................. 1-36
1.7 FSC Variables ............................................................................................... 1-38

1.7.1 Variable Types ............................................................................................................... 1-38
1.7.2 Variable Attributes .......................................................................................................... 1-38
1.7.3 Variable Characteristics ................................................................................................. 1-46
1.8 Standard System Variables ......................................................................... 1-49

1.8.1 Introduction..................................................................................................................... 1-49
1.8.2 Pulse Generators ........................................................................................................... 1-49
1.8.3 Real-Time Clock Functions ............................................................................................ 1-50
1.8.4 System Inputs and Outputs............................................................................................ 1-50
1.8.5 System Reset ................................................................................................................. 1-51
1.8.6 Force Enable .................................................................................................................. 1-52
1.8.7 Clock Synchronization Input........................................................................................... 1-52
1.8.8 Secondary Switch-Off .................................................................................................... 1-53
1.8.9 System Markers (Alarm Markers) .................................................................................. 1-54
Software Manual
Section 1: FSC Primer i
FIGURES
Figure 1-1 FSC basic architecture................................................................................................ 1-3

Figure 1-2 Single Central Part, single I/O configuration ............................................................. 1-11
Figure 1-3 Functional diagram: single Central Part, single I/O................................................... 1-11
Figure 1-4 Redundant Central Parts, single I/O configuration.................................................... 1-12
Figure 1-5 Functional diagram: redundant Central Parts, single I/O .......................................... 1-13
Figure 1-6 Redundant Central Parts, redundant I/O configuration............................................. 1-14
Figure 1-7 Functional diagram: redundant Central Parts, redundant I/O ................................... 1-15
Figure 1-8 Redundant Central Parts with redundant and single I/O configuration.................... 1-16
Figure 1-9 Functional diagram: redundant Central Parts with redundant and single I/O ........... 1-17
Figure 1-10 Functional diagram: QMR™ architecture.................................................................. 1-18
Figure 1-11 Instrumentation parameter configuration .................................................................. 1-20
Figure 1-12 Programming via functional logic diagrams (FLDs) .................................................. 1-21
Figure 1-13 Safety relation of I/O variables .................................................................................. 1-35
Figure 1-14 Example of FSC variable configuration screen......................................................... 1-39
Figure 1-15 COM-I/O variables .................................................................................................... 1-51
Figure 1-16 Input failure alarm marker function ........................................................................... 1-54
TABLES
Table 1-1 FSC communication interfaces ................................................................................... 1-5

Table 1-2 FSC input and output interfaces ................................................................................. 1-6
Table 1-3 FSC configurations.................................................................................................... 1-10
Table 1-4 FSC digital I/O modules ............................................................................................ 1-23
Table 1-5 FSC analog I/O modules........................................................................................... 1-24
Table 1-6 Voting schemes for single FSC components ............................................................ 1-36
Table 1-7 Voting schemes for redundant components ............................................................. 1-36
Table 1-8 Redundancy voting schemes .................................................................................... 1-37
Table 1-9 FSC variable types .................................................................................................... 1-38
Table 1-10 Reserved locations in FSC system ........................................................................... 1-40
Table 1-11 FSC register types .................................................................................................... 1-44
Table 1-12 Characteristics of FSC input variables ...................................................................... 1-46
Table 1-13 Characteristics of FSC output variables.................................................................... 1-47
Table 1-14 Characteristics of FSC non-I/O variables.................................................................. 1-47
Table 1-15 Characteristics of standard FSC system variables ................................................... 1-48
Table 1-16 Standard system variables: pulse generators........................................................... 1-49
Table 1-17 Standard system variables: real-time clock functions ............................................... 1-50
Table 1-18 Standard system variables: system inputs and outputs............................................ 1-50
Table 1-19 Standard system variables: system reset ................................................................. 1-51
Table 1-20 Standard system variables: force enable.................................................................. 1-52
Table 1-21 Standard system variables: clock synchronization ................................................... 1-52
Table 1-22 Standard system variables: secondary switch-off..................................................... 1-53
Table 1-23 Secondary switch-off requirements........................................................................... 1-53
Table 1-24 Standard system variables: system markers ............................................................ 1-54
Software Manual
ii Section 1: FSC Primer
Section 1 – FSC Primer
1.1 Introduction
General overview The Honeywell Fail Safe Control (FSCä) system is a highly reliable,
high-integrity safety system for safety-critical control applications.
It is a user-programmable, modular, microprocessor-based safety
system which can perform a wide range of high-integrity process
control and safety functions, including:
• high-integrity process control,
• burner/boiler management systems,
• process safeguarding and emergency shutdown,
• turbine and compressor safeguarding,
• fire and gas detection systems, and
• pipeline monitoring.
The design of the FSC system is based on both qualitative and

quantitative safety system technologies.
From a qualitative perspective, the system continuously monitors the
correct operation of its hardware, thus ensuring that it is able to
respond accurately to any defined process demand. The system is also
able to detect faults in field loops and field equipment. The extensive
system and field diagnostics support plant operators in assessing the
consequences of faults for process operation, and aid maintenance
engineers in allocating and resolving detected problems efficiently and
effectively.
High quantitative rating (optimal Mean Time Between Failure) is
accomplished through a redundant system architecture and the use of
high-quality electronic components and design methods.
Proven safety Through dedicated software and hardware, all system parts are
and availability continuously and actively involved in the execution of the system
tasks, and are continuously subjected to self-tests. The FSC system
can always guarantee its ability to lead the process to a safe state in
case of any potential hazard, which results in:
PROVEN SAFETY
Software Manual
Section 1: FSC Primer 1-1
In redundant FSC architectures, it is guaranteed that in case of failure
of either of the redundant Central Parts, the other Central Part is able
to continue the process control (while maintaining proven safety),
which results in:
PROVEN AVAILABILITY
Scope and This primer provides a bird's-eye view of the FSC system. It
references describes the basic FSC system setup and configurations (sections 1.2
and 1.4), and explains some of the system's main features (section
1.6).
More detailed information can be found in the following documents:

• FSC Safety Manual : FSC system safety aspects.
• FSC Hardware Manual : System hardware component
documentation.
• FSC Software Manual : FSC Navigator user documentation.
• FSC Service Manual : FSC service and maintenance
information
• FSC-SM documentation set : Implementation of the FSC Safety
Manager.
• FSCSOE Manuals : FSCSOE user documentation.
For details on document references refer to the last page of the general
table of contents of this manual.
Software Manual
1-2 Section 1: FSC Primer
1.2 FSC System Overview
Basic architecture Figure 1-1 shows the basic architecture of the FSC system. Two
major system parts can be distinguished:
• the Central Part, and
• the Input/Output interfaces.
FSCTM
Central Part
Communication Control Procesor Watchdog

To Redundant Processor
Central Part
Communication I/O Access Monitor
Interfaces & Protocols Safety Interlock Control Processor
To Process Computer User Programming Operation and
Systems, Printers and Self-diagnostics Operating Conditions
the FSC User Station
Input / Output interfaces
Digital Input Analog Input Digital Output Analog Output
24 Vdc - 60 Vdc 0 (4) - 20 mA 24 Vdc - 220 Vdc 0 (4) - 20 mA

120 Vac 0 (1) - 5 Vdc 120 Vac
[EEx ia] IIC 0 (2) - 10 Vdc [EEx ia] IIC
Figure 1-1 FSC basic architecture
Central Part The Central Part (CP) is the heart of the FSC system. It is a modular
microprocessor-based system specifically designed for safety-critical
applications which can be tailored to the needs of any application.
The most important Central Part modules are:
• the Control Processor,
• the Watchdog module, and
• the Communication Processor.
Control Processor The Control Processor (or Central Processing Unit, CPU) reads the
process inputs and executes the control program as created by the
user in graphical Functional Logic Diagrams (FLDs).
The results of the control program are then transmitted to the output
interfaces. In FSC architectures with redundant Central Parts, the
Software Manual
Control Processors synchronize their operation through a dedicated
communication link. Continuous testing of the FSC hardware by the
Control Processor ensures safe control of the process and extensive
system and process equipment diagnostics.
Watchdog The Watchdog monitors the operation and the operating conditions
of the Control Processor. The operation of the processor is monitored
by verifying if the processor executes all its tasks within a
precalculated time frame, which depends on the configuration. The
operating conditions monitored include the data integrity of the
processor memory and the voltage range of the supply power (both
undervoltage and overvoltage). If the Watchdog detects a fault in the
operation of the Control Processor or its operating conditions, it will
deactivate the safety-critical output interfaces of the FSC system,
independent of the Control Processor status.
Communication The Communication Processor allows the FSC system to exchange

Processor information with other computer equipment via serial communication
links. Each Central Part can accommodate up to four communication
modules, providing a maximum of eight communication links per
Central Part. Dedicated modules are available which provide
communication capabilities with other systems:
• the FSC Safety Manager Module (FSC-SMM), which integrates the
FSC system into the Universal Control Network (UCN) of
Honeywell's TotalPlant Solution (TPS) system, and
• the PlantScape interface module, which integrates the FSC system
into Honeywell's PlantScape system.
Interconnections The Central Part interfaces with the I/O system through a Vertical
Bus (V-bus), which is a flatcable that runs vertically in the FSC
cabinet. The V-bus is controlled by the Vertical Bus Driver (VBD)
module, which is located in the Central Part rack.
Each of the I/O racks contains a Horizontal Bus Driver (HBD)

module, which connects to the V-bus. The HBD module drives the
Horizontal Bus (H-bus), which relays the signals from the V-bus to
the I/O modules via a flatcable. The H-bus module is located on top of
each I/O rack. The horizontal bus and the flatcables are covered with a
sheet steel cover which provides optimum EMC/RFI immunity. The
cover plate contains a paper strip which holds the relevant process
tagging for signal identification.
Software Manual
Communication Table 1-1 below lists the equipment that the FSC system can
communicate with as well as the available physical interfaces and
communication protocols.
Table 1-1 FSC communication interfaces

Equipment Physical Interface Protocol
Modbus,
RS-232, RS-485, Current Loop
RKE3964R
Process Computers UCN (TPS Network) UCN Token Bus
PlantScape Ethernet
Printers RS-232, Current Loop Printer
FSC User Station RS-232, RS-485 FSC-DS
FSC System and FSC-FSC,
RS-232, RS-485, Fiber Optic
FSC Safety Manager RKE3964R
All communication interfaces are galvanically or optically isolated.

If the FSC architecture contains redundant Control Processors, the
system supports redundant communication. Each Central Part then has
its dedicated connection to the communication peer system.
Note:
For details on FSC communication refer to Appendix F of this
manual ("Communication").
Input/output The FSC system provides a wide range of digital and analog input
interfaces and output interfaces, each with different characteristics to meet the
demands of a wide range of field equipment. Table 1-2 lists the input
and output interfaces that are available in the FSC system.
Note:
For technical details on the FSC input and output modules refer
to the FSC Hardware Manual.
All FSC I/O modules contain galvanic or optical isolation between the
input and output circuitry and the FSC-internal supply power.
The fail-safe I/O modules support the diagnostic capabilities of the
FSC system, and can be used for safety-critical monitoring and control
functions. When used for such applications, the system may be
configured to respond automatically if it detects a fault in its own
hardware or in the field equipment. The fail-safe modules may also be
used for non safety-critical applications, which will then benefit from
FSC's diagnostic functions and fault-reporting capabilities.
Software Manual
Table 1-2 FSC input and output interfaces
Digital Input 24 Vdc, 48 Vdc, 60 Vdc and 110 Vdc
24 Vdc (loop-monitored)
120-230 Vac
Class I, Division 2, Groups ABCD;
Class II, Division 2, Groups FG
(1)
Class [Eex ia] IIC intrinsically safe
Digital Output 24 Vdc, 48 Vdc, 60 Vdc and 110 Vdc
24 Vdc, 48 Vdc and 220 Vdc (loop-monitored)
120-230 Vac
(1)
Analog Input 0-20 mA and 4-20 mA
0-5 V, 1-5 V, 0-10 V and 2-10 V
(1)
Resistance Temperature Device (RTD)
(1)
Thermocouple, types E, J, K and T
Analog Output 0-20 mA and 4-20 mA
(1) through external devices.
I/O redundancy The input and output interfaces of the FSC system can be
implemented in redundant or non-redundant (single) architectures.
Redundant I/O Redundant I/O architectures can be used in FSC systems with
redundant Central Parts. In this fully redundant architecture, each
Central Part has its own I/O system to which it has exclusive access.
The result is a highly reliable fault-tolerant system. Every program
cycle each Central Part reads its own input interfaces. After input
matching, both Central Parts execute the user-defined control
program and update their output interfaces according to the results. In
addition, the Central Parts compare the calculated output results to
ensure identical operation. Redundant I/O architectures are typically
used for critical control and safety functions in combination with the
high reliability offered by this concept.
Non-redundant Non-redundant (single) I/O architectures can be used in systems

(single) I/O with a non-redundant Central Part as well as in systems with
redundant Central Parts.
Fully non-redundant systems are typically used for safety applications
where redundancy is present in the process.
Software Manual
In FSC systems with redundant Central Parts, both Central Parts
alternately assume responsibility for the non-redundant I/O interfaces.
This ensures that both Central Parts can always access the I/O
interfaces correctly. FSC architectures with redundant Central Parts
and non-redundant I/O interfaces are typically used for critical control
applications with medium demands for system availability, e.g.
because of redundancy in plant equipment.
An FSC system architecture may also comprise redundant Central

Parts with a combination of redundant and non-redundant I/O
interfaces. Such architectures are extremely powerful, with process
control functions that demand high reliability being controlled through
the redundant I/O interfaces and less demanding control functions
through the non-redundant I/O interfaces.
Multiple-sensor and Unlike earlier safety standards, the international standards ANSI/ISA
transmitter S84.01 and IEC 61508 do not only focus on the safety system (called
architectures "logic solver", e.g. the FSC system), but also demand compliance of
the field equipment to the Safety Integrity Level (SIL) of the control
loop. This may not always be possible. The control loop, for example,
may be rated SIL 3, whereas a transmitter that measures one of the
loop input variables is only suited for SIL 1 and SIL 2. In such cases,
the required level of safety can be realized by using multiple sensors
or transmitters.
The FSC system supports multiple input architectures for digital and
analog input signals. The multiple-input function allows the use of
two or three sensors or transmitters to measure the same process
quantity. The resulting process value is fed to the control program on
the basis of one of the available standard matching algorithms, e.g.
2-out-of-3 (2oo3). The FSC system monitors if discrepancies occur
between the values obtained from the independent sensors or
transmitters, and reports any detected faults through its diagnostics.
The diagnostic status is also available to the control program.
Software Manual
1.3 Standards Compliance and Certification
Standards Since functional safety is at the core of the FSC design, the system
compliance has been certified for use in safety applications all around the world.
FSC was developed specifically to comply with the strict German
DIN/VDE functional safety standards, and has been certified by TÜV
for use in AK 1 to 6 applications. FSC has also obtained certification
in the United States for the UL 1998 and ANSI/ISA S84.01
standards.
FSC-based safety solutions and related Honeywell services can help
you comply with the new ANSI/ISA S84.01 standard for safety-
instrumented systems up to Safety Integrity Level (SIL) 3, as well as
the new international standard IEC 61508 for functional safety. These
new standards address the management of functional safety
throughout the entire life cycle of your plant.
Certification FSC has been certified to comply with the following standards:
TÜV Bayern (Germany) — Certified to fulfill the requirements of

"Class 6" (AK6) safety equipment as defined in the following
documents: DIN V VDE 19250, DIN V VDE 0801 incl. amendment
A1, DIN VDE 0110, DIN VDE 0116, DIN VDE 0160 incl.
amendment A1, DIN EN 54-2, DIN VDE 0883-1, DIN IEC 68,
IEC 61131-2.
Instrument Society of America (ISA) — Certified to fulfill the

requirements laid down in ANSI/ISA S84.01.
Canadian Standards Association (CSA) — Complies with the

requirements of the following standards:
CSA Standard C22.2 No. 0-M982 General Requirements – Canadian
Electrical Code, Part II;
CSA Standard C22.2 No. 142-M1987 for Process Control Equipment.
Underwriters Laboratories (UL) — Certified to fulfill the

requirements of UL 508, UL 991, UL 1998, and ANSI/ISA S84.01.
CE compliance — Complies with CE directives 89/336/EEC (EMC)

and 73/23/EEC (Low Voltage).
Software Manual
Factory Mutual (FM) — Certified to fulfill the requirements of
FM 3611 (non-incendive field wiring circuits for selected modules).
The FSC functional logic diagrams (FLDs) are compliant with

IEC 61131-3.
The design and development of the FSC system are compliant with
IEC 61508:1999, Parts 1-7 (as certified by TÜV).
Software Manual
1.4 Fail Safe Controller Architectures
1.4.1 Introduction
Basic architectures The Fail Safe Controller can be supplied in a number of architectures,
each with its own characteristics and typical applications. Table 1-3
below provides an overview of the available architectures.
Table 1-3 FSC architectures

Central Part I/O
CPU type Remarks See section
architecture configuration
10002/1/2 or 1oo1D architecture;

1.4.2
10012/1/2 Applications up to AK4
Single Single
DMR architecture;
10020/1/1 (QPM) 1.4.2
Applications up to AK6
10002/1/2 or 1oo2D architecture;

Single, 1.4.3
10012/1/2 Applications up to AK6
redundant,
Redundant
single and QMR™ architecture;
redundant 10020/1/1 (QPM) 1.4.6
Applications up to AK6
DMR = Dual Modular Redundant

QPM = Quad Processor Module
QMR = Quadruple Modular Redundant
All FSC archtiectures can be used for safety applications. The

preferred architecture depends on the available requirements.
The FSC architecures defined in Table 1-3 are discussed in more
detail in subsections 1.4.2 to 1.4.6.
Software Manual
1.4.2 Single Central Part and Single I/O
This FSC architecture has a single Central Part and single input and
output (I/O) modules (see Figure 1-2).
The I/O modules are controlled via the Vertical Bus Driver (VBD),
which is located in the Central Part, and the Vertical bus (V-Bus),
which controls up to 10 I/O racks. Each I/O rack is controlled via the
Horizontal Bus Driver (HBD). No redundancy is present except as
built into those modules where redundancy is required for safety
(memory and watchdog).
If the Central Part contains an Quad Processor Module (QPM,

10020/1/1), the system is suitable for applications up to AK6 (SIL 3).
System Bus
CPU COM WD PSU DBM VBD Up to 14 VBD

CENTRAL PART
H-Bus V-Bus
FS NFS FS NFS HBD Up to 10 HBD
INPUTS OUTPUTS
Figure 1-2 Single Central Part, single I/O configuration
ESD Watchdog
Module SMOD
Sensor
Input Output
xx
yyy Module Processor Module
Input Interfaces Central Part Output Interfaces Final Element
Figure 1-3 Functional diagram: single Central Part, single I/O
Software Manual
1.4.3 Redundant Central Parts and Single I/O
This FSC architecture has redundant Central Parts and single input
and output (I/O) modules (see Figure 1-4 and Figure 1-5).
The I/O modules are controlled via the VBDs, which are located in
each Central Part, and the V-Bus, which controls up to 10 I/O racks.
Each I/O rack is controlled via the HBD. The processor is fully
redundant, which allows continuous operation and bumpless
(zero-delay) transfer in case of a Central Part failure.
Even though there is a bumpless transfer between Central Parts if the
first failure occurs, the remaining risk must be limited within a certain
time. This time can be derived in a quantitative manner through the
Markov modeling techniques using the mathematics defined in
IEC 61508 and ANSI/ISA S84.01. A more pragmatic approach, which
is actually recommended by TÜV Product Services, is to allow
continued operation for 72 hours, leaving sufficient fault tolerance
time (FTT) for the organization to act upon the failure annunciation.
If the Central Parts contain Quad Processor Modules (QPM,
10020/1/1), there are no second fault timer (SFT) restrictions if one of
the Central Parts is down. (For details on the second fault timer refer
to section 4.5.8 of this manual.)
System Bus
CENTRAL PART 1 CPU COM WD PSU DBM VBD
H-Bus
V-Bus
FS NFS OR FS NFS HBD
INPUTS OUTPUTS
Figure 1-4 Redundant Central Parts, single I/O configuration
Software Manual
Central Part1
ESD Watchdog
Module
V+
Processor
SMOD
Sensor
Input
xx
yyy Module
Output
Module
Processor
Final Element
Watchdog
Module
Input Interfaces Central Part2 Output Interfaces
Figure 1-5 Functional diagram: redundant Central Parts, single I/O
Software Manual
1.4.4 Redundant Central Parts and Redundant I/O
This FSC architecture has redundant Central Parts and redundant

input and output (I/O) modules (OR function on outputs) (see Figure
1-6 and Figure 1-7).
each Central Part and the V-Bus, which controls up to 10 I/O racks.
Each I/O rack is controlled via the HBD. The processor and I/O are
fully redundant, which allows continuous operation and bumpless
(zero-delay) transfer in case of a Central Part or I/O failure.
OUTPUTS NFS NFS FS FS HBD HBD
INPUTS FS FS NFS NFS HBD HBD
Figure 1-6 Redundant Central Parts, redundant I/O configuration
Software Manual
Central Part 1
ESD Watchdog
Module
Output
Module
Input
Module Processor
SMOD
Sensor
xx Quad
yyy
Voter
SMOD
Input
Module Processor
Output
Module
Watchdog
Module
Input Interfaces Central Part 2 Output Interfaces
Final Element
Figure 1-7 Functional diagram: redundant Central Parts,

redundant I/O
Software Manual
1.4.5 Redundant Central Parts with Redundant and Single I/O
This FSC architecture has redundant Central Parts and redundant

input and output (I/O) modules (OR function on outputs) combined
with single input and output modules (see Figure 1-8 and Figure 1-9).
each Central Part, and the V-Bus, which controls up to 10 I/O racks.
Each I/O rack is controlled via the HBD. The processor and I/O are
fully redundant, which allows continuous operation and bumpless
(zero-delay) transfer in case of a Central Part or I/O failure of the
redundant I/O modules.
CENTRAL PART 1 CPU COM WD PSU DBM VBD VBD
CENTRAL PART 2 CPU COM WD PSU DBM VBD VBD
FS NFS
WDR FS NFS HBD
INPUTS / NFS NFS FS FS HBD HBD

OUTPUTS
FS FS NFS NFS
HBD HBD
Figure 1-8 Redundant Central Parts with redundant and

single I/O configuration
Software Manual
Central Part 1
ESD Watchdog
Module
Watchdog
Repeater
Output
Module
Input
Module Processor V+
SMOD
Sensor SMOD
xx Input Quad
yyy
Module Voter
Output
Module
SMOD
Input
Module Processor
Output
Module
Watchdog
Module
Final Element
Figure 1-9 Functional diagram: redundant Central Parts

with redundant and single I/O
Software Manual
1.4.6 Quadruple Modular Redundant (QMR™) Architecture
QMR™ The Quadruple Modular Redundant (QMR™) architecture with

architecture 2oo4D voting is an evolution of the proven 1oo2D concept. The
QMR™ architecture with 2oo4D voting is based on dual-processor
technology, and is characterized by a high level of diagnostics and
fault tolerance.
The QMR™ architecture is used in conjunction with the 10020/1/1
Quad Processor Module (QPM) and the 10024/x/x Enhanced
Communication Modules (ECM). Redundant Central Parts each
contain two main processors (see Figure 1-10 below), which provides
quadruple redundancy and, combined with 2oo4D voting, boosts the
overall safety performance of the system.
Central Part 1
ESD Watchdog
Module
CPU Output
Processor Module
Input
Module
Processor SMOD
Sensor
xx Quad
yyy
Voter
CPU
Processor SMOD
Input
Module
Processor Output
Module
Watchdog
Module
Final Element
Figure 1-10 Functional diagram: QMR™ architecture
The 2oo4D voting is realized by combining 1oo2 voting for both main
processors on one module, and 1oo2D voting between the two
modules (i.e. between Central Parts). Voting is therefore applied on
two levels: on a module level and between the Central Part modules.
Software Manual
With redundant I/O architectures, each path is primarily controlled by
one of the Central Parts, including an independent switch which is
controlled by the Central Part's Watchdog module. Furthermore, each
Central Part is able to switch off the output channels of the other
Central Part through dedicated SMOD (Secondary Means Of De-
energization) hardware circuitry which is located on the FSC fail-safe
output modules.
There are no second fault timer (SFT) restrictions if one of the Central
Parts is down.
Software Manual
1.5 FSC Architecture and Programming
FSC architecture The specific tasks of the FSC system within the process environment
and programming are determined by the system architecture and the application
program.
The FSC Navigator software provides support for the tasks that must
be carried out during the architecture and design stages. With FSC
Navigator, project documentation can be generated automatically and
is readily available.
System architecture During the architecture stage, the FSC system type, specification,
system parameters and the field instrumentation parameters are
defined (see Figure 1-11).
Figure 1-11 Instrumentation parameter configuration
Note:
For details on configuring the FSC system refer to Section 4 of
this manual ("System Architecture").
Software Manual
Application The FSC system's safety-critical control functions (contained in the
design control program) are determined by the safety functions assigned to
the system for the specific application. FSC Navigator supports the
design of the control program by the user.
The control functions are defined via graphical Functional Logic
Diagrams (IEC 61131-3: Continuous Function Charts). Figure 1-12
shows an example of a Functional Logic Diagram (FLD).
Note:
For details on designing FLDs refer to Section 6 of this manual
("Functional Logic Diagrams").
14TX711
Low Temperature Product Separator (14D-105)
Input Diagnostic 2515 1 14TI711BPV C

Bypass 3 Input Diagnostics O
S I/O type: AI 15 Xmtr OK A "Xmtr OK" M
Y 14TX711 13 B
S "Not faulty" 1 Xmtr OK
A
FB C
Bypass Time Remaining 41519 1 14TI711TMR
3 Bypass Time Remain
C
O
&
S I/O type: SensAI 15 913 Diagnostic Bypass Active A Signal type: F M
Y 14TX711 13 D
S "Not faulty" 1
Xmtr OK 170 14D-105 Product Sep

>1
_
F 15 40515 175 "Temperature OK"
14TX711 A 2
L 13 S &
14D-105 Product Sep D 0 t
D 1
>
t=2 s 576 1 14TALL711 C
F 45 R 3 14D-105 Product Sep O
A "Temperature OK" M
LL Setpoint
(DegF) 42526 1 14TSLL711TP C
3 LL Setpoint O
A Signal type: F M
Temperature OK
14ESV711
Propylene Feed To
Deethanizer Chiller
Reset Required 591 1 14EA711 C
& 3 14E-26 C3= Chiller O
A "Reset Required" M
Deenergize to Close 1523 16 14TO711 F

F 14ES711 15 552 Field Reset & 5 14E-26 C3= Chiller L
L 14E-26 C3= Chiller 1 1 "Run (Not Closed)" D
D "Reset" 11
>1
_
Deethanizer Overhead Chiller (14E-26)

Customer : Phillips Petroleum Company REFERENCE DWG. No.
Functional Logic Diagrams Unit 14 Shutdown Blocks #5
Principal : Honeywell IAC RDAS-14-VAR-MF-6
1 6-22-2000 ADD CONSTANTS Your Plant's Name Unit 14 Deethanizer Chiller
Plant 1 : Unit 11/14
0 10-8-1998 IFC Tel (713)780-5000 Date 6/22/1998 By: D.D. Ward
B 8-6-1998 ISSUED FOR TEST

Plant 2 : East Area Phase III
Honeywell Safety Fax (713)780-6676
8440 Westglen Dr.
Drawing number:
A
Rev
6/22/1998
Date
FIRST ISSUE
Description Chk'd
Req/Order No:
Management Systems Houston, TX 77063
HSMS (TX40)
Serial
U11_11
Project
Unit
170
Sheet
175
Cnt'd
Code Code
Figure 1-12 Programming via functional logic diagrams (FLDs)
FLD layout A Functional Logic Diagram (FLD) is split into four main areas:
• the information area (bottom).
• the input area (left),
• the control function area (center), and
• the output area (right).
Software Manual
FLD information The FLD information area, at the bottom of the FLD, provides
area information to identify the Functional Logic Diagram, including
revision data.
FLD input area The FLD input area, on the left-hand side of the FLD, contains all
the variables that serve as the input to the control function. Input
variables may originate from the field equipment or from other
computer equipment (Process Computer, FSC).
Special input functions are provided for:
• the diagnostic status of the FSC I/O interfaces,
• the status of field loops, and
• system alarm summary, e.g. temperature pre-alarm or device
communication failure.
Data can be exchanged between FLDs via sheet transfer functions.

This allows a structured design of complex functions across multiple
diagrams.
FLD control The FLD control function area, which is the central area of the FLD,
function area contains the actual implementation of the control function. The
function is realized by interconnecting predefined symbols which
provide a variety of functions including logical, numerical and
time-related functions. In addition to these standard functions,
user-definable blocks are supported:
• Function Blocks — standard FLDs for repetitive use within the
control program, and
• Equation Blocks — for tabular definition of complex functions,
e.g. non-linear equations.
FLD output area The FLD output area, on the right-hand side of the FLD, contains
the results of the control function. These variables may be used to
drive the field equipment or may be transferred to other computer
equipment, e.g. a process computer or another FSC system.
Software Manual
1.6 FSC Main Features
FSC features This section discusses a number of important FSC features. They are:
• FSC hardware modules (see subsection 1.6.1),
• FSC diagnostics (see subsection 1.6.2),
• Flash-memory operation (see subsection 1.6.3),
• On-line modification (OLM) (see subsection 1.6.4),
• Safety Checker (see subsection 1.6.5),
• Application verification (see subsection 1.6.6),
• Sequence-of-event recording (see subsection 1.6.7),
• FSC communication facilities (see subsection 1.6.8),
• FSC networks (see subsection 1.6.9),
• Alarm functions (see subsection 1.6.11),
• I/O signal forcing (see subsection 1.6.12),
• Safety relation (see subsection 1.6.13), and
• Voting (see subsection 1.6.14).
1.6.1 FSC Hardware Modules
I/O modules Table 1-4 and Table 1-5 below list the I/O module types that are
supported by the FSC system.
Table 1-4 FSC digital I/O modules

Type Safety relation Interface
24 Vdc, 48 Vdc, 60 Vdc, 110 Vdc and 115 Vac
Fail-safe
8 Vdc (loop-monitored)
Digital Input
24 Vdc
Non fail-safe (1)
24 Vdc, 48 Vdc, 60 Vdc, 110 Vdc
Fail-safe and 115/230 Vac
Digital Output 24 Vdc, 48 Vdc and 220 Vdc (loop-monitored)

24 Vdc
Non fail-safe (1)
(1) through external devices.
Software Manual
Table 1-5 FSC analog I/O modules
Type Safety relation Interface
0-20 mA and 4-20 mA
Analog Input Fail-safe
0-5 V, 1-5 V, 0-10 V, and 2-10 V
Analog Output Fail-safe 0-20 mA and 4-20 mA
Other modules In addition to the I/O modules, the FSC system also supports a
number of other modules:
− Central Processing Units (CPU),
− Quad Processing Modules (QPM),
− Watchdog modules (WD),
− Communication modules (COM),
− Enhanced Communication Modules (ECM),
− Diagnostic and Battery Modules (DBM),
− I/O bus driver modules,
− Power Supply Units (PSU), and
− Watchdog Repeater modules (WDR).
Note:
For technical details on the FSC modules refer to the FSC
Hardware Manual.
1.6.2 FSC Diagnostics
FSC diagnostics FSC's continuous self-tests enable the system to collect valuable
information on the diagnostic status of its own hardware and the field
equipment. The system uses this information to ensure uninterrupted
functional safety of the plant. In addition, the system provides the
diagnostic information to the user, via the diagnostic displays of FSC
Navigator. Through its diagnostics, the FSC system supports
maintenance engineers in allocating and resolving failures
effectively, thus reducing the Mean Time To Repair (MTTR) and
minimizing the risk of a plant trip.
Software Manual
If the FSC system is integrated into the TPS system, the FSC
diagnostics are also available at the TPS operator stations.
Note:
For details on FSC's diagnostics and monitoring capabilities
refer to Section 12 of this manual ("On-Line Environment").
1.6.3 Flash-Memory Operation
Flash-memory FSC Releases 510/520/530 support the use of flash memory to store
operation all system-related software. This feature combines the flexibility of
RAM with the data integrity of EPROM. It allows direct
downloading of the system firmware, system software, application
software and system architecture from the FSC user station to the
FSC system. This eliminates the need of making new EPROMs and
exchanging them with EPROMs on modules in the running cabinet,
which is a laborious procedure. This functionality is in full
accordance with TÜV approvals, and is protected against
unauthorized use by a password and key-lock protection mechanism.
Another advantage of flash-memory operation is that it reduces the

time to do an on-line modification (OLM). After the first full
download, only the changes will be loaded after a modification. This
should not be confused with the 'download changes' option that other
vendors are offering. The FSC system allows you to download
unlimited changes, even in a running installation while continuing
plant operation in a safe manner.
Notes:
1. Flash-memory operation requires special hardware modules
that support this feature.
2. For details on loading software refer to Section 10 of this
manual ("Loading Software").
Software Manual
1.6.4 On-Line Modification (OLM)
On-line On-line modification (OLM) is a TÜV-approved FSC system option

modification that is supported by FSC architectures with redundant Central Parts.
It enables modification of the application software, system software
and FSC hardware architecture, while maintaining the system's
critical control function for the operational plant. This means that the
system can be upgraded without the need of a plant shutdown.
During on-line modification, the changes are carried out in one
Central Part at a time. Meanwhile, the other Central Part continues to
monitor the process. The system will always perform a compatibility
check across the control program in order to guarantee a safe
changeover from the old control function to the new one. It will also
report the numbers of the functional logic diagrams (FLDs) that have
been changed, which complies with the 'verification requirements' of
IEC 61508 and ANSI/ISA S84.01.
Note:
For details on the FSC system's on-line modification capabilities
refer to Appendix D of this manual ("On-Line Modification").
1.6.5 Safety Checker
Safety Checker FSC Release 531 includes the Safety Checker, a static analysis tool
which helps engineers verify the safety consistency of an FSC
application. If the Safety Checker detects any inconsistencies in the
application that affect its safety integrity, it will report them on screen
and store them in a log file. This allows engineers to correct any
safety-related design errors at an early stage, and verify that the
safety application suits its projected purpose. The Safety Checker
supports the verification process that is part of the safety lifecycle as
laid down in IEC 61508 and ANSI/ISA S84.01.
An FSC control application can only be considered safe if all its

outputs are safety-related and the entire logic path leading to the
outputs is safety-related as well. An inconsistent configuration can
lead to hazardous situations. The Safety Checker will alert the
programmer to these inconsistencies. If, for example, an analog input
for a pressure trip has been configured as safety-related, but the output
that drives the shutdown valve has not been configured safety-related,
Software Manual
an inconsistency is detected in the loop and the programmer is alerted.
Conversely, an output that drives a non safety-critical function but is
configured as being safety-related, could display unwanted behavior if
a fault is detected in the output channel.
The Safety Checker will highlight the safety-critical functions in an
FSC application.
An additional function of the Safety Checker reports any off-sheet

references to a destination FLD with a lower number than the source
FLD, which might be design errors.
Note:
For details on the Safety Checker refer to Section 13 of this
manual ("Safety Checker").
1.6.6 Application Verification
Application FSC Navigator has a powerful feature that allows the user to compare
verification the control program in the FSC system with the application databases
on the FSC user station.
This feature can be used in two ways: as a project verification tool, or
as a Management Of Change (MOC) tool.
If used as a project verification tool, the verification option will

confirm that no translation or transfer faults have occurred to the
control program. FSC Navigator will then compare the translated
control program as it is present in the FSC system with the FSC
databases and functional logic diagrams (FLDs) that are stored on the
FSC user station. This allows the user to verify that the defined
control program has been loaded correctly. This verification process is
part of the safety lifecycle as laid down in IEC 61508 and ANSI/ISA
S84.01.
As a Management Of Change (MOC) tool, the verification option is

used to compare different versions of the control programs in the FSC
system and the FSC user station (revision control). This option is
typically used to list all the differences (modifications) between the
'old' version, which is stored in the FSC system, and the 'new' version,
which is stored on the FSC user station. This method can be used to
check if all modifications have been implemented correctly.
Software Manual
All differences found between the control program in the FSC system
and on the FSC user station are recorded in a verification log file,
which can be viewed on screen, printed or saved to disk for further
analysis.
Note:
For details on application verification refer to Section 11 of this
manual ("Verifying an Application").
1.6.7 Sequence-of-Event Recording (SER)
Sequence-of-event The FSC system contains an integrated sequence-of-event recording

recording (SER) (SER) function, which allows the system to detect and record events
that indicate or may cause deviations from normal process operation.
Examples of such events are:
• change of state of a valve limit switch,
• steam pressure becoming too high,
• maintenance override effected by a maintenance engineer,
• faults in the field (e.g. open transmitter loop), and
• faults in FSC input/output interfaces.
Once per program scan, the FSC system inspects all defined process
quantities, both digital and analog, for a change of state, in line with
the execution of the control program. An event is logged for any
changed process quantity, in an event buffer that resides within the
system. Events that result from operator interaction or from detected
faults are logged as soon as they are handled by the system. The
integrated list of the detected exceptions thus provides excellent
information for post-mortem analysis of abnormal process behavior,
in line with the 'traceability requirements' of IEC 61508 and
ANSI/ISA S84.01.
The logged events are reported to event management systems through

the FSC system's communication interfaces. Events may be reported
to:
• a personal computer running Honeywell's dedicated FSCSOE event
management software package, which allows users to view and
analyze (anomalous) process events (see below), or
• a line printer or matrix printer connected to the FSC system for
direct reporting on paper, or
• a distributed control system (DCS) (PlantScape, TPS, or third-party
system) for incorporation of the events into an overall event journal.
Software Manual
Until events have been successfully reported (via the SER
communication channel), the FSC system stores the logged events in
its internal SER event buffer. The exact size of the SER buffer
depends on the system architecture, but the buffer can hold at least
448 events. If the number of detected events exceeds the buffer
capacity, all subsequent events are ignored. This will ensure that the
start of a plant upset is preserved for post-mortem analysis. If the FSC
event buffer overflows as a result of communication failures with the
event management system, the FSC system will start overwriting
events older than four hours.
FSCSOE FSC Sequence of Events (FSCSOE) is the safety historian for

Honeywell's Fail Safe Control (FSC) product line. This Windows
software package records and logs process events, alarm events and
diagnostic events that are detected by the connected FSC system(s),
and stores them in its event database including detailed time-stamp
information. These events can be displayed, analyzed, printed and
exported based on user-definable selection criteria (filters).
FSCSOE enables users to analyze and monitor (abnormal) process

behavior. Any anomalies in a process may upset the process as a
whole. In order to understand why they occurred and to find the first
event that caused the process upset, accurately time-stamped and
archived information is essential. Equally important is the ability to
retrieve and analyze the logged information. This enables any process
anomaly to be reported rapidly and remedied effectively. This helps
the user keep the process on-line and maximize the plant profitability.
Note:
For details on the FSC system's SER functions refer to
Appendix B of this manual ("Sequence-of-Event Recording").
For details on the FSCSOE software package refer to the
FSCSOE manuals.
Software Manual
1.6.8 FSC Communication Facilities
Communication The FSC system has facilities for communication with:

• the Universal Control Network (UCN) of Honeywell's TotalPlant
Solution (TPS) system,
• PlantScape, via Ethernet,
• Distributed Control Systems (DCSs), via the Modbus RTU or
RKE3964R protocol,
• Other FSC systems, via the FSC-FSC or RKE3964R protocol,
• FSCSOE data collecting devices,
• Hartmann & Braun, and
• FSC user station running FSC Navigator, via the FSC Development
System (FSC-DS) protocol.
Available interfaces include:

• RS-232,
• RS-422/RS-485,
• Ethernet (e.g. for PlantScape),
• Fiber optic, and
• Current loop.
For optimum availability and fail-safe communication, the redundant

FSC system architectures allow the use of redundant communication
links as well.
The communication configuration of the FSC system is specified

during the system configuration. The functional logic diagrams are
used to realize the interaction of communication data with the FSC
application.
Note:
For details on the FSC system's communication features refer to
Appendix F of this manual ("Communication").
Software Manual
1.6.9 FSC Networks
FSC networks The FSC system supports Distributed Safety Systems (DSSTM)
through its extensive networking capabilities. FSC networks provide
the means to decentralize process safeguarding with central process
monitoring and control capabilities.
In a DSS network, multiple FSC systems are interconnected via
dedicated serial communication links. Both point-to-point and
multidrop networks are supported.
For optimum availability of the communication, the redundant FSC
system architectures require the use of redundant communication links
as well.
The DSS concept supports safety solutions in line with the plant
design, with every independent process unit being safeguarded by a
separate FSC system. This minimizes the risk of nuisance plant trips
during unit maintenance.
Note:
For detail on FSC's communication capabilities refer to
Communication The communication in an FSC network is based on either of two

protocol protocols:
• the Honeywell proprietary, TÜV-approved FSC-FSC
communication protocol (recommended), or
• the RKE3964R communication protocol.
FSC-FSC protocol The protocol normally used for communication between FSC systems
is the FSC-FSC communication protocol. This protocol includes a
high level of error detection and recovery, which makes it suitable for
exchanging safety-related information while maintaining optimum
availability.
The FSC-FSC protocol, in combination with the RS-232 F-interface,
can also be used in network architectures where large time delays are
to be expected, e.g. modem communication, communication over
telephone lines, satellite links, etc.
Note:
For details on the FSC-FSC communication protocol refer to
Software Manual
RKE3964R protocol The protocol normally used for communication between FSC systems
is the FSC-FSC communication protocol. This protocol includes a
high level of error detection and recovery, which makes it suitable for
exchanging safety-related information while maintaining optimum
availability.
can also be used in network architectures where large time delays are
to be expected, e.g. modem communication, communication over
Even though the RKE3964R protocol can be used in such situations as
well, it is recommended that you use the FSC-FSC protocol.
Note:
For details on the RKE3964R communication protocol refer to
1.6.10 Simulation
Simulation The FSC simulation option allows any FSC application to be loaded
into the standard FSC demo units. In simulation mode, the FSC
Control Processor executes the control program using the serial
interface with the FSC user station as its field interface. The actual
defined Central Part hardware is ignored and "mapped" to the
hardware of the simulation/demo units.
Input values are applied by the user via the FSC Navigator software,
using the input signal force feature. The output values can be
monitored through various displays at the FSC user station.
In combination with the standard "live" FLD viewing feature of FSC

Navigator, the simulation option provides an excellent means for
design engineers to validate the FSC control program prior to initial
installation and to verify modifications before an on-line upgrade. The
interfaces with TPS (FSC-SMM) and PlantScape are also supported in
simulation mode, which allows an integrated validation of the entire
safety application.
Note:
For details on simulation refer to Appendix H of this manual
("Simulation Mode").
Software Manual
1.6.11 Alarm Functions
Alarm functions The FSC system contains a number of integrated standard alarm
functions, which comply with the ISA S18.1 standard for annunciator
sequences:
• first-up (TFS) with single or dual flash frequency,
• basic flashing (AF),
• manual lamp reset (AM),
• flasher reset (FR),
• flasher / lamp reset (FRM),
• ringback (AR),
• double audible ringback (ARR).
The first-up alarm function may be split into two parts: an alarm-
detecting part and an alarm-display part. The two parts may be
implemented in different FSC systems which are interconnected in a
distributed safety network. This allows the integration of alarms that
are detected by independent FSC systems to be combined in the same
first-up alarm group.
The alarm-display part may also be located in a process computer. The
two parts are then connected through data exchange via the
communication link between the FSC system and the process
computer.
Note:
For details on the FSC system's alarm functions refer to
Appendix A of this manual ("Alarm Functions").
Software Manual
1.6.12 I/O Signal Forcing
I/O signal forcing For maintenance reasons, it may be desirable to force an input or an
output signal to a certain fixed state, e.g. when exchanging a
defective input sensor. This allows the sensor to be exchanged
without affecting the continuation of the production. During the
exchange, the applicable input is forced to its normal operational
state. While being desirable in some situations, forcing a signal to a
specific, fixed value may also create a potentially hazardous
condition.
The FSC system provides a force function which supports

maintenance personnel in applying forces consciously. It only allows
forcing of signals that were specifically selected during the system
design. During operation, the system is protected against unauthorized
forces via a key switch. Forcing of FSC signals is only possible via the
FSC Navigator software using a password-protected software
function. All forcing actions are included in the FSC event reports for
traceability purposes.
Note:
For details on I/O signal forcing refer to Section 12 of this
manual ("On-Line Environment").
Software Manual
1.6.13 Safety Relation
Safety relation The safety relation of the I/O variables is specified in a tree structure.
Each leaf of the tree can be safety-related only if the complete path
from root to leaf is safety-related.
This means that an I/O signal can only be safety-related if the I/O
module is safety-related. An I/O module can only be safety-related if
the HBD module in the same rack is safety-related.
Safety-related variables can only be allocated to safety-related I/O.
The safety-related outputs in the application program should depend
only on safety-related inputs. The compiler will check for conflicts of
the safety relation in the application program.
I/O modules can only be safety-related if the hardware is fail-safe.
Figure 1-13 Safety relation of I/O variables
Software Manual
1.6.14 Voting
Voting The FSC system is available in single and redundant mode, both for
Central Part and I/O, in several combinations. For details on the
various FSC architectures refer to subsection 1.4.
If the Central Part and I/O are operating in single mode, it is obvious
what will happen in case a fault is detected: the Central Part or I/O
will go to the safe (i.e. non-operational) state. For redundant Central
Parts and/or I/O, this is less obvious, and users may want to define the
system response in case a fault is detected in one part of the redundant
components. This is the reason that voting has been incorporated into
the system, which allows the users to optimize the system response to
his safety needs.
Single components For all single components in the FSC system, two voting schemes are
available depending on the hardware that is being used. The table
below lists the various options.
Table 1-6 Voting schemes for single FSC components

Voting scheme Used for hardware modules... Fault results in...
1oo1D diagnostics capabilities switch-off

(e.g. 10101/x/x digital input modules)
1oo1 without diagnostic capabilities incorrect operation

(e.g. 10104/x/x digital input modules) or switch-off
Redundant Redundant components have more voting schemes to choose from,

components depending on the hardware that is being used and on the primary
action in case a fault is detected: switch-off or continue. Table 1-7
and Table 1-8 below list the various options.
Table 1-7 Voting schemes for redundant components

Hardware
Primary action at fault Fail-safe Non fail-safe
Safety (switch-off) 1oo2D 1oo2
Availability (continue) 2oo2D 2oo2
Software Manual
Table 1-8 Redundancy voting schemes
Voting Used for hardware Primary action Response to faults
scheme modules... directed at...
1oo2 without diagnostics safety The first fault may result in switch-off as
capabilities (switch-off) the faulty module may overrule the
(e.g. 10104/x/x digital input correct one.
modules)
2oo2 without diagnostics availability The first fault may result in incorrect
capabilities (continue) operation as the faulty module may
(e.g. 10104/x/x digital input overrule the correct one.
modules)
1oo2D with diagnostics capabilities safety For detected faults, operation continues
(e.g. 10101/x/x digital input (switch-off) as desired. A fault that cannot be
modules) detected by the diagnostics (probability
= 1 – diagnostic coverage) may result in
switch-off as the faulty module may
overrule the correct one.
2oo2D with diagnostics capabilities availability For detected faults, operation continues
(e.g. 10101/x/x digital input (continue) as desired. A fault that cannot be
modules) detected by the diagnostics (probability
= 1 – diagnostic coverage) may result in
incorrect operation as the faulty module
may overrule the correct one.
2oo4D with diagnostics capabilities safety + For detected faults and the first fault,
(e.g. 10105/./. analog input availability operation continues as desired. The first
modules or 10106/./. digital fault that cannot be detected by the
input with line monitoring or diagnostics (probability = 1 –
safety-related digital output diagnostics coverage of single leg) will
modules). result in safe operation due to the 1oo2
voting.
Software Manual
1.7 FSC Variables
1.7.1 Variable Types
Variable types Table 1-9 below lists the variable types that are available in the FSC
system.
Table 1-9 FSC variable types

Type Description Type Description
I Digital input M Marker
AI Analog input C Counter
BI Binary input T Timer
XI Input multiplexer R Register
O Digital output P PID control function
AO Analog output A Alarm
BO Binary output
XO Output multiplexer
1.7.2 Variable Attributes
Variables attributes This section discusses the attributes and properties that each FSC
variable has. The variable attributes and parameters are defined
during FSC system architecture. Figure 1-14 on the next page shows
the variable configuration screen for an analog output (AO) variable.
Notes:
1. Attributes that are not relevant for a particular variable type
will never be displayed on screen. This means that the
variable configuration screen will look differently depending
on the variable type.
2. For details on how to configure FSC variables refer to
Section 4 of this manual ("System Architecture").
Software Manual
Figure 1-14 Example of FSC variable configuration screen
Tag numbers FSC Navigator allows a variable type and tag number to be combined
only once. This means that any FSC variable is uniquely identified by
the combination of its type and tag number.
A typical tag number for I/O (I, AI, BI, XI, O, AO, BO, XO, A, P)
consists of three parts:
Tag number = <Prefix>'_'<Description>'_'<Loop number>
The underscore sign ('_') may also be replaced by a hyphen ('-').

Tag numbers may consist of any ASCII characters, except spaces (' '),
semicolons (';'), commas (',') and question marks ('?'). The maximum
length of a tag number is 16 characters.
Examples of valid tag numbers are UNIT1, 01_UNIT1_115,
SP2-UNIT#1, and 10-Kühlung-301.
Note:
Tag numbers are case-sensitive, which means that 'Tag' is not
the same as 'TAG'.
Software Manual
The tag number is sometimes followed by a sequence of characters
that provides further information, e.g.:
01-HLS-320HH (HLS for high-low switch, HH for high-high)
Tag numbers of internal variables are automatically created from the

program block number and a sequence number. These tag numbers
cannot be changed.
Examples: T32_1 First timer in program block 32.
10_12_3 Third reference between program blocks
10 and 12.
Service The service attribute provides a description about the tag number,
e.g. 'Level glycol tower'.
Qualification The qualification attribute provides information about the '1' (or
active) status of boolean variables. If the qualification is TRUE or '1',
then the status of the variable is TRUE or '1'. It is only used for
variables of type I, O, M, C, T.
Location The location attribute provides information about the location of the
sensor or the actuator. The location is specified as an abbreviation of
three characters. It is only used for I/O variables (I, AI, BI, XI, O,
AO, BO, XO, and A). The FSC system has a number of reserved
locations, which are listed in Table 1-10.
Table 1-10 Reserved locations in FSC system

Location Description
ANN Alarm function (I, O, A only).
COM Variable that can be altered or read via a communication link

(I, BI, O, BO only).
MUX Multiplexer variable (BI, BO, XI, XO only).
SYS System variable (reserved for use by the FSC programs).
FSC Variable that can be altered or read by another FSC system

Unit The unit attribute specifies the name of the unit for which this
variable is used in the application program, e.g. F-210 (Furnace 210).
Software Manual
Subunit The subunit attribute specifies the name of the subunit for which this
variable is used in the application program, e.g. B-210 (Burner on
Furnace 210).
FLD(s) This is number of the Functional Logic Diagram(s) that contain(s) the
variable.
Address This attribute specifies the address of the variable if an address has
been defined for the variable type.
Relative address Some I/O variables will be allocated to an address within a memory
area that is reserved for a certain application (e.g. a communication
link). The relative address is the address within such a reserved area.
Safety-related This attribute specifies the safety relation of the variable. For I/O
variables (I, AI, BI, XI, O, AO, BO, XO and A), this attribute
specifies the action to be taken in case of a hardware fault of the I/O
module which the variable is connected to.
Force enable This attribute specifies for each variable whether it is possible to
force the variable (i.e. set it to a certain fixed state). It is possible to
force I/O variables and on-sheet references. The "forced" value will
be valid until the force of the variable is disabled. All forces are
controlled by a force-enable input (IO-FORCED). Forces are only
allowed if the force-enable input is high and the force-enable flag is
TRUE. Forces will be cleared if the force-enable input is low.
Write enable This attribute specifies for each variable whether it is possible to
write a variable, which means that the value assigned to the variable
will be overwritten in the next program cycle (unless the variable is
an input with location 'COM' or 'FSC').
SER enable This attribute specifies whether sequence-of-event recording (SER)

should take place for the variable. If an SER sequence range has been
specified and the variable is SER-enabled, then an SER sequence
number is also displayed. This field can be used to specify a unique
number for numerical SER format.
Software Manual
Fault reaction This attribute only applies to non safety-related digital and analog
input signals (I and AI) that have been allocated to fail-safe modules.
It defines what the signal value should become in case of a fault. If
the safety relation is set to 'Yes', the fault reaction field is
automatically set to 'Low' (for digital signals) or 'Bottom scale' (for
analog signals). If the safety relation is set to 'No', the fault reaction
field can be set to either 'Scan' or 'Hold'. 'Scan' means that the signal
value remains to be scanned, even after a fault, whereas 'Hold' means
it gets the last valid value that was detected.
Transmitter alarm This attribute specifies the minimum value for an analog input. If the
setpoint low analog input goes below the minimum setpoint, the system will give
an analog sensor break alarm.
Transmitter alarm This attribute specifies the maximum value for an analog input. If the
setpoint high analog input exceeds the maximum setpoint, the system will give an
analog sensor break alarm.
SER setpoint low If the value which is read or written for an analog I/O is lower than
SER setpoint low, sequence-of-event recording takes place (providing
the SER-enable flag is set to 'Yes'). The SER setpoint low should be
higher than, or equal to, the bottom scale, and lower than the SER
setpoint high.
SER setpoint high If the value which is read or written for an analog I/O is higher than
the SER setpoint high, sequence-of-event recording takes place
(providing the SER-enable flag is set to 'Yes'). The SER setpoint high
should be lower than, or equal to, the top scale, and higher than the
SER setpoint low.
Power-up value This attribute specifies the value which the variable will get after a
power-up sequence. The power-up value can be specified for binary
inputs (BI) with location 'COM', 'FSC' or 'MUX', binary outputs
(BO), analog outputs (AO), counters (C), and registers (R).
Software Manual
Power-up status This attribute specifies the value which the variable will get after a
power-up sequence. The power-up status can be specified for digital
inputs (I) with location 'COM' or 'FSC', digital outputs (O), and
markers (M).
Sensor is fail-safe This attribute specifies if the sensor is fail-safe, i.e. goes to a defined
state ('0' or OFF) in case of a sensor failure. It is only used for
safety-related digital and analog inputs (I and AI).
Sensor is redundant When a sensor is not fail-safe and the digital input (I) or analog input
(AI) is safety-related, a redundancy type should be selected.
Redundancy is used to increase the reliability of the data read
operation. Depending on the redundancy type, more channels should
be allocated to this variable. For details refer to Appendix C of this
manual ("Safety-related inputs with non-fail-safe sensors").
Signal type The signal type is used for analog inputs and outputs (AI and AO). It
should match the hardware configuration used. The following signal
types are available:
− 0 to 20 mA
− 4 to 20 mA
− 0 to 5 V
− 1 to 5 V
− 0 to 10 V
− 2 to 10 V
Engineering units The engineering units are used with analog inputs (AI), analog
outputs (AO), PIDs (P), and binary outputs (BO). The engineering
units are defined as a string with a maximum length of five characters
of the unit which is read or written with the variable, e.g. °C, Psi, %.
Bottom scale The bottom scale of an analog variable should contain a value in
engineering units which is read or written on the bottom value of the
defined signal type. If, for example, a temperature of 20°C is
measured at a sensor voltage of 2 V (for a signal type of 2-10 V), you
should enter 20 as the bottom scale value.
For details refer to Section 4 of this manual ("System Architecture").
Software Manual
Top scale The top scale of an analog variable should contain a value in
engineering units which is read or written on the top scale value of
the defined signal type.
Register type The register type defines the format of the data stored. There are four
different register types. The first three are integer values, the last
(Float) is a real value which consists of an exponent and a mantissa.
Table 1-11 below shows the characteristics of the various register
types.
Table 1-11 FSC register types

Register type Integer/Real Minimum value Maximum value
Byte (8-bit) Integer –128 +127
Word (16-bit) Integer –32,768 +32,767
Long (32-bit) Integer –2,147,483,648 +2,147,483,647

38 38
Float (32-bit) Real –10 +10
MUX tag number A BI variable is "linked" to the XI variable via the MUX tag number.
The tag number of the accessory multiplexer is the MUX tag number.
A BO variable will be "linked" to an XO variable.
For details refer to Appendix G of this manual ("FSC Multiplexers").
Number of input This attribute specifies the number of input bits of a BI (with
bits locations other than 'COM' and 'FSC') or an XI, and has a range of
1 to 32 bits. All bits of the variable will be allocated to sequential
channels. If the number of bits does not fit on the first module, a
second module must be defined. On this next module, the allocation
starts at channel 1, and continues with the next channels. It may be
necessary to specify as much as three modules.
Selection output The selection output rack is the rack where the selection outputs of
rack the multiplexed variable will be allocated. For details refer to
Appendix G of this manual ("FSC Multiplexers").
Software Manual
Selection output The selection output position is the position in the rack where the
position multiplexed variable will be allocated. Remember to allocate a BI
variable with location 'MUX' to a digital output! All the selection
outputs must be allocated. The selection output channel is the first
channel of the first module which the multiplexed variable will be
allocated to. For details refer to Appendix G of this manual ("FSC
Multiplexers").
Sel OUT active time The select output active time is the time in which the select output
should be true with multiplexed I/O. Select output active time should
be in the range from 1 to 127 ms. It is only used for multiplexed I/O
(XI and XO variables). For details refer to Appendix G of this manual
("FSC Multiplexers").
Sel OUT active The select output active status defines the value which is used for the
status select outputs of multiplexed I/O. When select output active status is
ON and the select output is HIGH, the data of the multiplexed I/O is
read or written to the data path (defined with the connected XI or
XO). For details refer to Appendix G of this manual ("FSC
Multiplexers").
Number of output This attribute specifies the number of output bits of a BO (with
bits locations other than 'COM' and 'FSC') or an XO, and has a range of
1 to 32 bits.
All bits of the variable will be allocated to sequential channels. If the
number of bits does not fit on the first module, a second module must
be defined. On this next module, the allocation starts at channel 1, and
continues with the next channels. It may be necessary to specify as
much as three modules.
DCS address This attribute specifies a unique identification of a variable in the

FSC system. It is used by a Distributed Control System (DCS) to
access the attributes of this variable. The address range depends on
the DCS that is used:
− UCN (TPS): 1 to 65534
− PlantScape: 1 to 8192 (I and O variables)
10001 to 18192 (AI, AO, BI, and BO variables)
The DCS address can only be specified if the applicable interface has
been configured.
Please note that the maximum number of DCS addresses in an FSC
application is 12,000. The maximum number for the FSC-SMM is
2,500.
Software Manual
1.7.3 Variable Characteristics
FSC variable Table 1-12 to Table 1-15 below provide an overview of the
characteristics characteristics of the various variable types.
Table 1-12 Characteristics of FSC input variables

Variable type Location Safety-related Force enable Write enable SER enable
Digital inputs (I) COM N X Y X
FSC X X N X
ANN N N N X
SYS Standard system variables; see Table 1-15 on page 1-48
other X X N X
1)
Analog inputs (AI) SYS N N N X
other X X N X
Binary inputs (BI) COM N N Y N
FSC X N N N
MUX N N N N
SYS Real-time clock functions; see Table 1-15 on page 1-48
other X N N N
Multiplexer inputs (XI) any N N N N

N = Will always be 'No' Y = Will always be 'Yes'. X = Can be either 'Yes' or 'No'.
Notes:
1)
This is the external voltage readback input of the high-density
analog input module 10105/2/1 (the "17th channel").
Software Manual
Table 1-13 Characteristics of FSC output variables
Digital outputs (O) COM N N N X
FSC X N N X
1) 2)
ANN N X/N N N/X
3)
SYS N N N X/Y/N
other X X N X
Analog outputs (AO) any X X N X
Binary outputs (BO) COM N N N X
FSC X N N X
MUX N N N N
other X N N N
Multiplexer outputs
any N N N N
(XO)
Notes:
1)
Can only be modified for annunciator variables with a hardware
location.
2)
Can only be modified for first-up alarm indication.
3)
X: Secondary switch-off (SEC.SWITCH-OFF) and COM-IO
N: RKE triggers
Y: BO SER triggers.
Table 1-14 Characteristics of FSC non-I/O variables

Alarms (A) – N N N N
1) 2)
Markers (M) – N N/X X/N X
Counters (C) – N N X X
Timers (T) – N N X X
2)
Registers (R) – N N X/N N
PIDs (P) – N N N N
Notes:
1)
Cannot be modified for off-sheet references.
2)
Cannot be modified for on/off-sheet references.
Software Manual
Table 1-15 Characteristics of standard FSC system variables
Standard system Variable Safety- Force Write SER
Location
variables: type related enable enable enable
Flasher-xxHz
I SYS N N N N
(see subsection 1.8.2)
Real-time clock variables

BI SYS N N N N
COM-I/O
I SYS N N N X
COM-I/O
O SYS N N N X
System reset (RESET)

I SYS X N N X
Force enable (ENABLE)
I SYS X N N X
CLOCK-SYNC
I SYS N N N X
SEC.SWITCH-OFF
O SYS N N N X
System markers
(alarm markers) I SYS Y N N X
Software Manual
1.8 Standard System Variables
1.8.1 Introduction
Standard system Whenever a new project is created, 29 system variables are stored in
variables the variable database. These variables can be used in the application
software. The variables are related to a number of different system
areas:
• Pulse generators: 4 variables
• Real-time clock functions: 7 variables
• System inputs and outputs: 2 variables
• System reset: 1 variable
• Force enable: 1 variable
• Clock synchronization input: 1 variable
• Secondary switch-off: 1 variable
• System markers: 12 variables
———
29 variables
Each of these areas is discussed in more detail below.
1.8.2 Pulse Generators
Pulse generators Table 1-16 below lists the standard system variables that are related
to pulse generators. Each variable represents a pulse of different
frequency.
Table 1-16 Standard system variables: pulse generators

Variable Name Safety- Remarks
type (tag number) related
I Flasher-0.5Hz No –
I Flasher-1Hz No –
I Flasher-2Hz No –
I Flasher-5Hz No Only for single FSC 1oo1D, DMR

architectures
Software Manual
1.8.3 Real-Time Clock Functions
Real-time clock Table 1-17 below lists the standard system variables that are related
functions to real-time clock functions. These variables indicate the date and
time as available in the FSC system.
Table 1-17 Standard system variables: real-time clock functions

BI MONTH No Byte
BI DATE No Byte
BI DAY No Byte
BI HOURS No Byte
BI MINUTES No Byte
BI SECONDS No Byte
BI YEAR No Byte
1.8.4 System Inputs and Outputs
System inputs Table 1-18 below lists the standard system variables that are related
and outputs to system inputs and outputs. These variables are only used in fully
redundant architecures.
If FSC communication fails, the Central Part can use these COM I/O
variables to see if the other Central Part is still running (see Figure
1-15). This will be the case if the input is high (the connected output is
also high).
Table 1-18 Standard system variables: system inputs and outputs

I COM-I/O No –
O COM-I/O No –
Software Manual
I I
FSC-FSC
CP1 CP2
O O
Figure 1-15 COM-I/O variables
The COM-I/O system variables must be allocated to specific channels.

The variables may only be allocated to the following locations:
Input COM-IO The COM-IO system variable for digital inputs (I) must be allocated
to channel 1 or 5 of a 10101/2/1 module, which must be located in
one of the next adjacent positions: 1-2, 11-12, 13-14, 15-16, or 17-18.
Output COM-IO The COM-IO system variable for digital outputs (O) may be
allocated to channel 1 or 3 of a 10201/2/1 module, or to channel 1 or
2 of a 10215/2/1 module, which must be located in one of the next
adjacent positions: 1-2, 11-12, 13-14, 15-16, or 17-18.
1.8.5 System Reset
System reset Table 1-19 below lists the standard system variable that is related to
system reset. All errors detected and stored in memory will be
cleared. This hardware input is edge-triggered.
Important!
Always read diagnostic data prior to a system fault reset.
Otherwise diagnostic data information will be lost.
Table 1-19 Standard system variables: system reset

Variable Name Safety-related Remarks
type (tag number)
I RESET user- The default variable name
configurable ("RESET") may be modified without
(default = yes) affecting its function.
Software Manual
1.8.6 Force Enable
Force enable Table 1-20 below lists the standard system variable that is related to
enabling force command.
If this hardware input is high, forces to other variables can be given.
This input must also be high if you want to download the application
file to the FSC system.
Table 1-20 Standard system variables: force enable

Variable Name Safety-related Remarks
type (tag number)
I ENABLE user- The default variable name
configurable ("ENABLE") may be modified
(default = yes) without affecting its function.
1.8.7 Clock Synchronization Input
Clock
synchronization Table 1-21 below lists the standard system variable that is related to
input clock synchronization input.
This hardware input is used to synchronize the real-time clock of the
FSC system. It can be used in combination with the clock set option
via the Modbus or RKE3964R protocol. When the input is asserted,
the clock value (set by the DCS) is accepted by the FSC system. If the
input is asserted while no clock set command was initiated by the
DCS, the FSC system will set its clock at 03.00.00 am. This allows
simple adaptation to daylight saving time.
Table 1-21 Standard system variables: clock synchronization

I CLOCK-SYNC No The default variable name
("CLOCK-SYNC") may be modified
without affecting its function.
Software Manual
1.8.8 Secondary Switch-Off
Secondary Table 1-22 below lists the standard system variable that is related to
switch-off secondary switch-off.
Table 1-22 Standard system variables: secondary switch-off

O SEC.SWITCH-OFF No The default variable name
("SEC.SWITCH-OFF") may be
modified without affecting its function.
Whether or not the secondary switch-off needs to be allocated depends

on the requirement class (AK), the presence of 10216/./. modules in
the system, and the output voting scheme. Table 1-23 below shows
when the secondary switch-off is mandatory and what will be reported
when it is not allocated.
Table 1-23 Secondary switch-off requirements

AK5/6* AK1 to AK4
10216/./. No 10216/./. 10216/./. No 10216/./.
1oo2D 2oo2D 1oo2D 2oo2D
Mandatory Optional Optional Mandatory Optional Optional
(error) (warning) (warning) (error) (no error or (no error or
warning) warning)
* If 10002/x/x or 10012/x/x CPUs are used, secondary switch-off is mandatory for all AK6
applications (regardless of the 10216/x/x architecture). An error will otherwise be reported.
In normal operation this output is low. If a condition occurs which

requires a Central Part to deactivate the outputs of the other Central
Part, the output is set high and an emergency shutdown is effected on
the watchdog module of the other Central Part. The shutdown
becomes active when allocated to a hardware output channel
(10201/1/1, 10201/2/1, 10216/1/1 or 10215/2/1).
Important!
This output may never be used in the application program to
initiate a shutdown at a user-defined condition.
The SEC.SWITCH-OFF system variable for digital outputs (O) may

be allocated to channel 1 or 3 of a 10201/2/1 module , or to channel 1
or 2 of a 10215/2/1 module, which must be located in the adjacent
positions: 1-2.
Software Manual
1.8.9 System Markers (Alarm Markers)
System markers Table 1-24 on the next page lists the system markers that are used in
(alarm markers) the FSC system to indicate abnormal input situations. This is why
they are also called alarm markers.
The normal state of the markers, if no fault is present, is '1'. If the first
fault occurs, the associated alarm marker changes to '0'. Any
subsequent fault will cause the alarm marker to be pulsed to '1' for one
application program cycle (see Figure 1-16).
The system markers are available in the application program, e.g. to
generate an alarm.
1 2 3 4
INPUT FAILURE
FSC SYSTEM FAULT
1 No faults present in FSC system
2 First input fault
3 Second input fault
4 Faults corrected and acknowledged via fault reset
Figure 1-16 Input failure alarm marker function
Table 1-24 Standard system variables: system markers

Variable Name Safety- Function
I CENTR.PART-FAULT Yes This input is normally high, but if a fault is
detected in a module connected to this
Central Part, it will go low.
I DEVICE-COM.FLT Yes This input is normally high, but if a device
fails (e.g. Modbus link, FSCSOE station), it
will go low. If a subsequent device
communication error occurs, it will give a
pulse.
I EXT.COMMUNIC.FLT Yes This input is normally high, but if an error in
the external communication is detected, it will
go low. If another fault of this kind is
detected, it will give a pulse.
Software Manual
Table 1-24 Standard system variables: system markers (continued)
Variable Name Safety- Function
I FSC-SYSTEM-FAULT Yes This input is normally high, but if any fault is
detected in the FSC system, it will go low. If
another fault of this kind is detected, it will
give a pulse.
I INPUT-FAILURE Yes This input is normally high, but if a fault is
detected in an input test routine, it will go low.
If a subsequent fault on inputs is detected, it
will give a pulse.
I INT.COMMUNIC.FLT Yes This input is normally high, but if a Central
Part has shut down, it will go low.
I IO-COMPARE Yes This input is normally high, but if the status of
an input or output variable in Central Part 1
differs from the status of that variable in
Central Part 2 and the discrepancy cannot be
attributed to an existing hardware fault, it will
go low. If another fault of this kind is
This variable is not available in FSC systems
with only one Central Part.
I IO-FORCED Yes This input is normally high, but if any input,
output or sheet reference has been forced, it
will go low. If a subsequent variable is forced,
it will give a pulse.
I OUTPUT-FAILURE Yes This input is normally high, but if a fault is
detected in an output test routine, it will go
low. If a subsequent fault on inputs is
I RED.INPUT-FAULT Yes This input is normally high, but if a fault has
been detected in redundant input sensors
(e.g. discrepancy), it will go low. If another
fault of this kind is detected, it will pulse.
This variable is only used for safety-related
inputs with non fail-safe sensors.
I TEMP.PRE-ALARM Yes This input is normally high, but if the
temperature of the Diagnostic and Battery
Module (DBM) is too high or too low, it will go
low. The default threshold is 55°C (131°F).
For details refer to the data sheet of the
10006/./. module in the FSC Hardware
Manual.
I TRANSMIT.-FAULT Yes This input is normally high, but if an analog
input exceeds the transmitter setpoint alarms,
it will go low. If another fault of this kind is
Software Manual
Left blank intentionally.
Software Manual
Fail Safe Control
Section 2:
Installation Guide
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 2: Installation Guide
2.1 Installation Requirements.............................................................................. 2-1
2.2 Serial Interface Module 07177/1/x.................................................................. 2-3
2.3 SCC-07177 Communication Driver................................................................ 2-6

2.3.1 Introduction....................................................................................................................... 2-6
2.3.2 Installing the SCC-07177 Driver....................................................................................... 2-7
2.3.3 Configuring the SCC-07177 Driver .................................................................................. 2-9
2.4 FSC Navigator Packages ............................................................................. 2-11
2.5 Preparing the FSC User Station .................................................................. 2-12
2.6 Installing FSC Navigator .............................................................................. 2-14
2.7 Copying PlantScape Messages to PlantScape Server............................... 2-22
2.8 Error Messages ............................................................................................ 2-23
2.9 Uninstalling FSC Navigator ......................................................................... 2-25
Software Manual
Section 2: Installation Guide i
FIGURES
Figure 2-1 07177/1/. serial interface module ................................................................................ 2-3

Figure 2-2 Selecting the I/O address range of the 07177 module ............................................... 2-8
Figure 2-3 07177 module driver settings ...................................................................................... 2-9
Figure 2-4 Setting the correct file display options ...................................................................... 2-13
Figure 2-5 Choosing the setup language ................................................................................... 2-15
Figure 2-6 Software license agreement...................................................................................... 2-15
Figure 2-7 Entering the user information .................................................................................... 2-16
Figure 2-8 Entering the license number ..................................................................................... 2-17
Figure 2-9 Choosing the destination folder................................................................................. 2-18
Figure 2-10 Uninstalling a previously installed version ................................................................ 2-18
Figure 2-11 Previously installed version cannot be uninstalled.................................................... 2-19
Figure 2-12 Selecting a program folder ........................................................................................ 2-19
Figure 2-13 Installation summary window .................................................................................... 2-20
Figure 2-14 FSC Navigator shortcut on desktop .......................................................................... 2-21
Figure 2-15 Uninstalling FSC Navigator ....................................................................................... 2-25
Figure 2-16 Confirming uninstall................................................................................................... 2-26
TABLES
Table 2-1 07177/1/. module addresses....................................................................................... 2-4

Table 2-2 FSC Navigator packages .......................................................................................... 2-11
Software Manual
ii Section 2: Installation Guide
Section 2 – Installation Guide
2.1 Installation Requirements
Hardware FSC Navigator and its installation program are both Windows
requirements applications, so you must already have Windows NT 4.0 or Windows
2000 running on the target computer to install FSC Navigator. The
installation program creates folders as needed and copies files from
the distribution CD-ROM to your hard disk.
The target PC should meet the following hardware requirements:

• CD-ROM drive
• 233-MHz Pentium-class processor or higher
• 64 MB of RAM (128 MB recommended)
• PC serial interface module 07177/1/x installed (1)
(see subsections 2.2 and 2.3)
• 15 MB of hard disk space for the FSC Navigator application files
• Sufficient free hard disk space to hold all project files. The exact
disk space required depends on the number and complexity of the
projects, but an average of 2 MB per project should be sufficient.
Note:
(1) The PC serial interface module 07177/1/x is only required if
you want to program applications to EPROMs.
Software
requirements The software requirements (prior to installation) are as follows:
• Windows NT 4.0 with Service Pack 6 or higher running or
Windows 2000 running, and
• Microsoft Internet Explorer 4.0 or higher installed.
FSC Navigator was specifically developed to run under Windows NT

4.0 or Windows 2000. It is not supported by any other Windows
versions. Using FSC Navigator under any Windows version other than
Windows NT 4.0 or Windows 2000 is considered improper use of the
software. Honeywell Safety Management Systems cannot be held
liable in any way for any damages that result from using FSC
Navigator under a Windows version other than Windows NT 4.0 or
Windows 2000.
Software Manual
Section 2: Installation Guide 2-1
Note:
There are some restrictions if FSC Navigator is to run under
Windows 2000. For details refer to the release note that is
shipped with the software.
Printer
requirements FSC basically uses two types of printers:
• Printers connected to the FSC user station
These printers are used to print the system configuration and
functional logic diagrams (FLDs) from FSC Navigator. Any printer
configured in Windows NT/2000 can be used for this purpose.
For details on this type of printing refer to Section 7 of this manual.
• Printers directly connected to the FSC system
These printers are used to print reports generated by the FSC
system, and can also be used to directly print sequence-of-event
(SOE) data from the FSC system. They are typically line printers or
matrix printers.
For details on this type of printing refer to Section 5 of this manual.
Software Manual
2-2 Section 2: Installation Guide
2.2 Serial Interface Module 07177/1/x
Introduction The 07177/1/x serial interface module (see Figure 2-1) is only
required in the following two cases:
• You want to program EPROMs. The 07177/1/x interface module is
then used to connect the EPROM programmer (07170/1/1) to the
FSC user station.
• You want to communicate with the FSC system using one of the
serial interfaces of the 07177/1/x module. If you use a different
serial interface – e.g. a standard COM port of the FSC user station –
you do not need the 07177/1/. interface module or the
communication driver.
Notes:
1. If you use the 07177/1/x serial interface module, you need to
install a special communication driver (see subsection 2.3).
2. For technical details on the serial interface module 07177/1/.
and the EPROM programmer 07170/1/1 refer to the FSC
Hardware Manual.
Figure 2-1 07177/1/. serial interface module
Software Manual
Installing the
module To install the 07177/1/. serial interface module, do the following:
1. Turn off your PC.
2. Remove the cover from your PC.
3. Select an unused ISA expansion slot and remove its bracket.
4. Verify that the address setting of the 07177/1/. serial interface
module (see below) does not interfere with any other modules
(e.g. network interface modules).
5. Hold the serial interface module by its top edges and press it
firmly into an unused expansion slot. After positioning the
module, tighten the screw to secure the module bracket.
6. Put the PC cover back into place.
7. Turn on your PC.
Note:
PCs which have on-board modules (e.g. sound card, network
card) may claim recourses that are used by the 07177/1/. serial
interface module. To enable the serial interface module to work
properly, you may need to free these resources (using the Setup
of your PC).
Module The FSC software uses interrupt level 5 (IRQ5), DMA channel 3 and
base address hexadecimal I/O address 300h for the serial interface module
07177/1/.
The interrupt level and the DMA channel cannot be changed. The
hardware address can, however, be changed by modifying the setting
of jumpers J1 and J2 on the serial interface module (see Figure 2-1).
Table 2-1 below shows the jumper settings for the various module
addresses.
Table 2-1 07177/1/. module addresses

Jumper settings Base address
J1 J2
0 0 300 (default)
1 0 320
0 1 340
Software Manual
Modifying the FSC Navigator assumes hexadecimal module address 300h. If you
base address wish to use a different address, you need to modify the settings of the
special SCC-07177 communication driver that is required for using
the 07177/1/x interface module.
For details refer to subsection 2.3.3 on page 2-9.
Software Manual
2.3 SCC-07177 Communication Driver
2.3.1 Introduction
07177/1/x Communication between the FSC system and the FSC user station
interface module can be done through industry-standard PC serial interfaces or the
HSMS 07177/1/x serial interface module. This module, which is
installed in the FSC user station, provides two serial interfaces for
communication with the FSC system, and can also be used to
interface with the 07170/1/1 EPROM programmer.
Notes:
The functionality offered on the 07177/1/x modules depends on
the exact type. For technical details refer to the FSC Hardware
Manual.
SCC-07177 driver If you wish to use the 07177/1/x serial interface module to
communicate with the FSC system, you need to install a special
software communication driver onto the FSC user station.
Maximum If the SCC-07177 driver has been installed, the maximum baud rate
baud rate for RS-485 communication between the FSC system and the FSC
user station is 1 Mbaud.
Software Manual
2.3.2 Installing the SCC-07177 Driver
Important!
You need administrator rights in Windows NT/2000 to be able
to install the SCC-07177 driver software.
Installing the The SCC-07177 software driver is not automatically installed with
SCC-07177 driver FSC Navigator. You need to install it separately. To install the
SCC-07177 communication driver onto the FSC user station, follow
the procedure below:
1. Put the FSC Navigator CD-ROM in the CD-ROM drive.
2. Close all Windows applications that are open.
3. From the Start menu, choose the Run command. This will open
the Run dialog box. Click the Browse button, select the CD-ROM
drive and double-click SETUP.EXE to select this file and close
the Browse dialog box. Click OK to start the Setup program.
4. An installation menu will appear, with an option called Install
SCC-07177 Driver. Click this option to start the driver setup
program.
5. A welcome screen will appear. Click the Next button to proceed
with the installation.
6. The window as shown in Figure 2-2 on the next page will appear.
Here you can specify the I/O address range of the 07177 serial
interface module. The default address of the 07177/1/x module is
300-31F. After setting the I/O address range, click the Next button
to proceed with the installation.
Note: The I/O address is defined by two jumpers on the module.
For details refer to the 07177/1/x module data sheet in the FSC
Hardware Manual.
7. Setup will now install the driver software onto your hard disk.
After all files have been copied, you will be prompted to restart
your computer.
Note: You must restart your computer for the driver to work
properly.
The 07177/1/x interface module can now be used to communicate

with the FSC system.
Software Manual
Figure 2-2 Selecting the I/O address range of the 07177 module
Important!
If you use the 07177 interface module for communication with
the FSC system, the FSC user station must not have a sound
driver installed. If there is, interrupt conflicts may occur, since
sound drivers will typically use the same interrupt request as the
07177 communication driver (05). If you want to use sound,
make sure it does not use interrupt request (IRQ) 05.
Software Manual
2.3.3 Configuring the SCC-07177 Driver
Important!
1. You need administrator rights in Windows NT/2000 to be
able to modify the setting of the SCC-07177 communication
driver.
2. You cannot modify the SCC-07177 driver settings when you
are logged in as another user. If you try, an error message
will appear saying that registry entries could not be created.
Setting the module Should the I/O address range need to be changed after the driver
I/O address range software has been installed, you can proceed as follows:
1. In Control Panel, double-click the FSC – 07177 Module icon:
This will open the dialog as shown in Figure 2-3 below.
Figure 2-3 07177 module driver settings

2. Choose the appropriate address range from the drop-down menu
in the Base Address field, and click OK to confirm the change.
Note: The other two fields are for information purposes only;
they cannot be changed.
3. You will be prompted to restart your computer.
Note: You must restart your computer for the new settings to take
effect.
Software Manual
The 07177/1/x interface module can now be used to communicate
with the FSC system using the new address settings.
Important!
If you use the 07177 interface module for communication with
the FSC system, the FSC user station must not have a sound
driver installed. If there is, interrupt conflicts may occur, since
sound drivers will typically use the same interrupt request as the
07177 communication driver (05). If you want to use sound,
make sure it does not use interrupt request (IRQ) 05.
Software Manual
2.4 FSC Navigator Packages
FSC Navigator FSC Navigator is available in four packages. The customer will
packages always purchase a particular package. A unique license number is
then issued which allows the customer to install and use the
appropriate package. The four FSC Navigator packages are:
• Demo
This package has limited functionality and is primarily for
demonstration purposes.
• Standard
This package offers all FSC Navigator functions.
• Contractor
This package has limited functionality and allows FSC
contractors to design a system.
• Hartmann & Braun
This package is functionally identical to the Standard package,
but it also supports the Hartmann & Braun (H&B)
communication protocol.
Table 2-2 below lists the differences between the various software
packages.
Table 2-2 FSC Navigator packages
FSC Navigator packages
Function Demo Contractor Standard H&B
System configuration = = = =
Print = = = =
Design FLDs = = = =
Max. number of FLDs in project 10* 999** 999** 999**
View log files = = = =
Translate application – = = =
Program EPROMs – – = =
Load into flash memory – – = =
Edit SER formats – – = =
Verify application – – = =
Monitor system and view
– – = =
process status
Modem functionality – – = =
FSC-SMM support = = = =
PlantScape support = = = =
Safety Checker – = = =
H&B comm. protocol + P-Bus – – – =
* Function blocks can be defined in FLD 5 and higher.
** Function blocks can be defined in FLD 500 and higher.
Software Manual
2.5 Preparing the FSC User Station
Preparations to There is one important consideration that should be taken into

FSC user station account in conjunction with FSC Navigator. It is related to the file
display options in Windows.
File display options You should make sure that Windows NT/2000 shows all files, and
does not hide certain system files. If you do not, you may encounter
problems if any of your projects has a functional logic diagram (FLD)
with the number 386. (Please note that this is not a problem related to
FSC Navigator, but a Windows-related issue.)
FLDs are stored on the hard disk, with the sheet number as the
extension. If the FLD number (and thus the file extension) is 386,
Windows will consider this a virtual device driver. By default,
Windows will hide a number of system files from the user, including
virtual device drivers with the extension 386. This means that an FLD
with the number 386 will not be shown in Windows Explorer, because
it has the file extension 386 (even though it is not a device driver of
any kind). Since this FLD is not displayed, it will also not be copied or
compressed into a file if you attempt to transfer the project files to
another folder or computer. The result is that your project is no longer
complete, and can no longer be translated successfully (because of a
missing FLD).
To ensure this problem will not occur, you need to make sure that
Windows displays all files, and not hide system files. To check – and
where required, change – this setting, follow the procedure below:
1. Start Windows Explorer (e.g. by right-clicking the Start button
and choosing the Explore option).
2. From the View menu, choose the Options item. The dialog as
shown on the next page will appear.
3. Make sure the Show all files option button is selected. If it is not,
click on it to select it. This will stop Windows from hiding system
files from the user.
4. Choose the OK button to confirm the change. The changes will
take effect immediately. You do not need to reboot your
computer.
Software Manual
Figure 2-4 Setting the correct file display options
Software Manual
2.6 Installing FSC Navigator
Installing The FSC Navigator software is supplied on a CD-ROM. If required,

FSC Navigator make sure that the serial interface module (07177/1/x) has been
properly installed in your PC (see subsections 2.2 and 2.3).
Notes:
1. Every purchased FSC Navigator license allows you to install
the software onto a maximum of five computers.
2. The installation procedure as described below assumes that
you use the English version of Windows NT 4.0 and that
you choose English as the Setup language.
3. You need administrator rights in Windows NT/2000 to be
able to install the FSC Navigator software.
Previous Setup automatically detects if another instance of the FSC Navigator

installations of FSC software has been installed on your PC. If that is the case, Setup will
Navigator software provide you with the option of uninstalling the "old" software or
installing the "new" software in an alternative folder.
Installation
procedure To install FSC Navigator, do the following:
Starting Setup 1. Close all Windows applications that are open.

2. Put the FSC Navigator distribution CD-ROM in the CD-ROM
drive.
3. The installation program will start automatically. If it does not,
start SETUP.EXE in the root of the CD-ROM.
4. An installation menu will appear, with an option called Install
FSC Navigator. Click this option to start the Setup program for
the FSC Navigator software.
Setup language 5. You will first be asked to choose which language should be used
for the setup process (see Figure 2-5). Select either English or
German from the drop-down list and click the OK button to
continue.
Software Manual
Figure 2-5 Choosing the setup language
Software license 6. A Welcome window will appear. Click the Next button to open
the Software License Agreement window (see Figure 2-6).
Carefully read the license agreement before proceeding. You must
accept the license agreement before you can continue. To accept
the license agreement and continue with the installation, click the
Yes button. If you decline the license agreement, click the No
button, and the setup procedure will be aborted.
Figure 2-6 Software license agreement
Software Manual
User information 7. If you clicked the Yes button in the Software License
Agreement window, the User Information dialog box will open
(see Figure 2-7).
Figure 2-7 Entering the user information
Serial number Enter the user name and the company name. In the Serial text
box, enter the serial number that was provided with the
distribution CD-ROM. Please note that any letters in the serial
number are case-sensitive (i.e. 'x' is not the same as 'X'). You
must enter a valid serial number before you can install FSC
Navigator. After you have successfully completed the User
Information dialog box, click the Next button.
License number 8. A dialog box will appear which prompts you to enter the license
number that was supplied with the distribution CD-ROM (see
Figure 2-8).
The license number determines which package of FSC Navigator
you are entitled to use. The Setup program will automatically
install the correct package.
Please note that any letters in the serial number are case-sensitive
(i.e. 'x' is not the same as 'X'). You must enter a valid license
number before you can proceed.
After you have entered a valid license number, click the Next
button.
Software Manual
Figure 2-8 Entering the license number
Destination folder 9. The window as shown in Figure 2-9 will appear.

This window prompts for the folder on the hard disk where the
FSC Navigator application files should be installed. The suggested
destination folder is X:\FSC, where 'X' is the drive that contains
the Windows NT/2000 operating system (usually drive C:). You
can accept this default suggestion, or you can use the Browse
button to specify a different folder. When you are done, click the
Next button.
Please note the following:

1. The installation folder must be called 'FSC'.
2. Long file names are supported.
3. Folder and file names may not contain spaces.
4. Folder and file names (without extension) shorter than nine
characters may only contain one dot.
This means that the following path names are invalid:
− C:\PROGRAM FILES\FSC
− C:\HSMS\FSCNAV
− D:\F.S.C.
The following path names are valid:
− C:\SMS_SOFTWARE\FSC
− C:\HSMS\FSC
− D:\FSC
Software Manual
Figure 2-9 Choosing the destination folder
Another version At this point, Setup may detect that another version of FSC
Navigator has already been installed in the destination folder. If
this version can be uninstalled, the window as shown in Figure
2-10 will appear.
If no other FSC software version is detected, the step below will
be skipped and Setup will continue with step 10.
Figure 2-10 Uninstalling a previously installed version
If you choose Yes, the previously installed version of the FSC

user software will be uninstalled. If you choose No, this version
will not be uninstalled. You must then choose a different
destination folder for FSC Navigator.
Software Manual
If the existing FSC software in the destination folder cannot be
uninstalled, the following window will appear:
Figure 2-11 Previously installed version cannot be uninstalled
Program folder 10. The window as shown in Figure 2-12 will appear.
Figure 2-12 Selecting a program folder
This window prompts for the name of the program folder that will
contain the shortcut to FSC Navigator. You can accept the default
suggestion (Honeywell SMS), or you can enter a different
program folder. When you are done, click the Next button.
Note:
Please note that the program group of all other FSC-related
software applications will also default to 'Honeywell SMS'.
Software Manual
Summary window 11. The window as shown in Figure 2-13 will appear.
Figure 2-13 Installation summary window
This window presents a brief summary of the installation

parameters before the setup program will start copying the files to
your hard disk. If you want to change any of the parameters, use
the Back button to move to the appropriate window and change
the parameter. Then use the Next button(s) to return to this
window. If you are ready to install FSC Navigator, click the Next
button in this window. The files will now be copied to hard disk.
Finalizing Setup 12. If any of your system files were modified, you will be prompted
to restart your computer. Click the Finish button to complete the
setup process and restart your computer (if required).
Note:
If you are prompted to restart your system, FSC Navigator
will only operate correctly after you reboot your computer.
Software Manual
Starting If the FSC Navigator application has been properly installed on the
FSC Navigator FSC user station, two items have been added to the Windows user
interface:
• A shortcut on the Windows desktop called 'FSC Navigator 5xx'
(where '5xx' is the version number) (see Figure 2-14), and
• An item called 'FSC Navigator 5xx' in the program group
'Honeywell SMS' (under Start / Programs).
Figure 2-14 FSC Navigator shortcut on desktop
You can start FSC Navigator by double-clicking the desktop shortcut,

or by moving to the 'Honeywell SMS' program group and choosing
the 'FSC Navigator 5xx' option (where '5xx' is the version number).
Software Manual
2.7 Copying PlantScape Messages to PlantScape Server
FSC and FSC Release 530 supports an Ethernet communication interface with
PlantScape Honeywell's PlantScape system, which means that FSC-related data
can easily be exchanged between FSC and PlantScape. This allows
this information to be shared and made available on the PlantScape
server displays.
Message files The PlantScape server uses two FSC-related message files called
FSC_MODULE.TXT and FSC_FAULT.TXT. These files contain the
identifications for all FSC modules as well as their diagnostic
messages. If an event occurs for an FSC module, PlantScape takes the
correct identification and diagnostic message from these files and
displays them on the PlantScape server screen. In order to ensure that
PlantScape always uses the most up-to-date information (including
the newest FSC hardware developments), the most recent messages
files are shipped with FSC Navigator.
If you intend to use the FSC-PlantScape interface, always make sure
that you copy these message files to the PlantScape server. To do this,
follow the procedure below:
1. Close all Windows applications that are open.
2. Put the FSC Navigator distribution CD-ROM in the CD-ROM
drive.
3. The installation program will start automatically. If it does not,
start SETUP.EXE in the root of the CD-ROM.
4. An installation menu will appear, with an option called Copy
PlantScape Message Files. Click this option.
5. Follow the instructions on screen.
Software Manual
2.8 Error Messages
Error messages The following error messages may appear while installing the FSC
Navigator software on your system.
English: A fatal error has occurred during setup. Error: <code>.

German: Fataler Fehler während des Setup. Fehler: <Kode>.
This message appears if an error occurs that prevents Setup from
continuing the installation procedure. The setup process will be
terminated. <Code> is an internal error code that helps HSMS
engineers determine what went wrong.
English: An error occurred during the move data process. Error:

<code>.
German: Fehler während der Übertragung der Daten. Fehler:
<Kode>.
This message appears if an error occurs while data is being copied
from the distribution CD-ROM to your hard disk. <Code> is an
internal error code that helps HSMS engineers determine what
went wrong.
English: An error occurred while uninstalling the FSC software.

Please select another destination folder.
German: Fehler beim Deinstallieren der FSC-Software. Wählen
Sie bitte einen anderen Zielordner.
This message appears if an error occurs while the previously
installed FSC software is being uninstalled from your system. You
can only continue with the setup process if you select a different
destination folder for FSC Navigator.
English: FSC Navigator requires Windows NT 4.0. Setup will be

aborted.
German: FSC Navigator erfordert Windows NT 4.0. Setup wird
abgebrochen.
This message appears if you attempt to install FSC Navigator on a
computer which contains a different Windows version than
Windows NT. The setup process will be terminated.
Software Manual
English: Invalid license number entered.
German: Die eingegebene Lizenznummer ist ungültig.
This message appears if you enter an incorrect license number.
Make sure that the license number that you enter is exactly as it
was provided to you. (Please note that the letters are case-sensitive,
i.e. 'x' is not the same as 'X'.)
This message may also appear if the serial number that you entered
earlier is not correct.
English: Invalid serial number entered.

German: Die eingegebene Seriennummer ist ungültig.
This message appears if you enter an incorrect serial number. Make
sure that the serial number that you enter is exactly as it was
provided to you. (Please note that the letters are case-sensitive, i.e.
'x' is not the same as 'X'.)
English: This program requires VGA or better resolution.

German: Dieses Programm benötigt VGA- oder bessere
Auflösung.
This message appears if you attempt to install FSC Navigator on a
computer that does not have sufficient graphic capabilities. Make
sure that your computer has a VGA-compatible video card.
English: Unable to write to registry.

German: Schreiben in die Registrierdatei ist nicht möglich.
This message appears if Setup cannot carry out the modifications to
the Windows registry which are required for FSC Navigator to
work properly.
English: Uninstaller setup failed to initialize. You may not be

able to uninstall the program.
German: Setup-Deinstallationsprogramm konnte nicht
initialisiert werden. Sie können das Programm nicht
deinstallieren.
This message appears if Setup cannot initialize the program
component that logs the FSC Navigator installation. This log
allows FSC Navigator to be uninstalled later, and if it is
compromised in any way, uninstalling may not be possible.
Software Manual
2.9 Uninstalling FSC Navigator
FSC Navigator has an uninstall facility which allows it to be

completely removed from your system.
Uninstall procedure To uninstall FSC Navigator, do the following:

1. Double-click the Add/Remove Programs applet from Control
Panel. (Please note that in Windows versions other than English
these program components are called differently.)
The following window will appear:
Figure 2-15 Uninstalling FSC Navigator
2. From the list of applications that can be automatically removed by

Windows NT/2000, select FSC Navigator 5xx (where '5xx' is the
version number) and click the Add/Remove button. The window
as shown in Figure 2-16 will appear.
Software Manual
Figure 2-16 Confirming uninstall
If you want to remove FSC Navigator from your system, choose Yes.
All FSC Navigator files will now be removed.
Any files and registry entries that were created after FSC Navigator
was installed on your system will not be removed. This means that the
project files in the project subfolders will not be deleted from your
hard disk. If you want to remove them, you should delete them
manually (e.g. using Windows Explorer).
Software Manual
Fail Safe Control
Section 3:
Using FSC Navigator
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 3: Using FSC Navigator
3.1 Program Overview.......................................................................................... 3-1
3.2 FSC Navigator Packages ............................................................................... 3-4
3.3 Menu Bar......................................................................................................... 3-5
3.4 Button Bar..................................................................................................... 3-10
3.5 Navigation Area ............................................................................................ 3-11

3.5.1 FSC Project Configuration Screen ................................................................................. 3-12
3.5.2 FSC Safety Compliance Screen .................................................................................... 3-15
3.6 Password Protection.................................................................................... 3-21

3.6.1 Using Passwords............................................................................................................ 3-21
3.6.2 Password Types............................................................................................................. 3-21
3.6.3 Password Maintenance.................................................................................................. 3-22
3.6.4 Passwords in Converted Projects .................................................................................. 3-24
3.7 Communication Port .................................................................................... 3-25
3.8 User and Version Information ..................................................................... 3-27
3.9 Working with Projects.................................................................................. 3-28

3.9.1 Creating a New Project .................................................................................................. 3-28
3.9.2 Opening an Existing Project........................................................................................... 3-29
3.9.3 Project Conversion ......................................................................................................... 3-30
3.9.4 Project Files.................................................................................................................... 3-31
3.10 Symbol Libraries .......................................................................................... 3-32
3.11 Color Settings............................................................................................... 3-34
3.12 Scaling Factor .............................................................................................. 3-38
3.13 Basic Operations in Program Components................................................ 3-40
Software Manual
Section 3: Using FSC Navigator i
FIGURES
Figure 3-1 FSC Navigator shortcut on desktop ............................................................................ 3-2

Figure 3-2 FSC Navigator main screen ........................................................................................ 3-3
Figure 3-3 Unavailable menu options........................................................................................... 3-5
Figure 3-4 FSC Navigator menu structure.................................................................................... 3-6
Figure 3-5 Button bar.................................................................................................................. 3-10
Figure 3-6 Button bar with submenu .......................................................................................... 3-10
Figure 3-7 FSC design and maintenance cycle ......................................................................... 3-11
Figure 3-8 FSC Project Configuration screen............................................................................. 3-12
Figure 3-9 Button in navigation area with submenu ................................................................... 3-13
Figure 3-10 FSC Safety Compliance screen ................................................................................ 3-15
Figure 3-12 FSC On-Line Environment screen ............................................................................ 3-18
Figure 3-14 Password definition screen ....................................................................................... 3-23
Figure 3-15 Setting the communication port................................................................................. 3-25
Figure 3-16 Port icon in Control Panel (Windows NT) ................................................................. 3-26
Figure 3-17 User and version information .................................................................................... 3-27
Figure 3-18 Version information ................................................................................................... 3-27
Figure 3-19 Creating a new project .............................................................................................. 3-28
Figure 3-20 Project name in main screen's title bar ..................................................................... 3-29
Figure 3-21 Opening an existing project....................................................................................... 3-29
Figure 3-22 Project properties ...................................................................................................... 3-32
Figure 3-23 Setting the colors in FSC Navigator .......................................................................... 3-34
Figure 3-24 Resizing a window by dragging its edges ................................................................. 3-38
Figure 3-25 Scaling factor............................................................................................................. 3-38
TABLES
Table 3-1 FSC Navigator packages ............................................................................................ 3-4

Table 3-2 Links between speed buttons and menu items......................................................... 3-10
Table 3-3 Links between buttons and menu items (FSC Project Configuration screen) .......... 3-14
Table 3-4 Links between buttons and menu items (FSC Safety Compliance screen).............. 3-17
Table 3-5 Links between buttons and menu items (FSC On-Line Environment screen).......... 3-20
Table 3-6 Available symbol libraries.......................................................................................... 3-32
Table 3-7 Exchangeability of symbol libraries ........................................................................... 3-33
Table 3-8 Color settings for the various color schemes ............................................................ 3-36
Table 3-9 Shortcut keys for data input ...................................................................................... 3-41
Software Manual
ii Section 3: Using FSC Navigator
Section 3 –Using FSC Navigator
3.1 Program Overview
Note:
It is assumed that you have a good understanding of Windows
basics and are comfortable using the Windows environment. If
this is not the case, please refer to the Windows documentation
for more information on how to use Microsoft Windows NT or
Windows 2000.
Program overview FSC Navigator provides a Windows NT/2000 user interface with the
FSC system. It is a powerful tool which supports the user in
performing a number of design and maintenance tasks. FSC
Navigator can be used to:
• configure the FSC system,
• design the application program,
• load software into the FSC system,
• generate application documentation, and
• monitor the FSC system.
The interface between the FSC user station and the FSC system is
established through a serial communication link. FSC Navigator uses
this link to communicate with the FSC system.
For installation issues refer to Section 2 ("Installation Guide") of this

manual.
Important!
It is strongly recommended that you use the FSC user station
with FSC Navigator exclusively for FSC-related design and
maintenance tasks. Other tasks may affect the stability and
integrity of the Windows NT/2000 environment.
Software Manual
Section 3: Using FSC Navigator 3-1
Starting If the FSC Navigator application has been properly installed on the
FSC Navigator FSC user station, two items have been added to the Windows user
interface:
• A shortcut on the Windows desktop called 'FSC Navigator 5xx'
(where '5xx' is the version number) (see Figure 3-1), and
• An item called 'FSC Navigator 5xx' in the program group
'Honeywell SMS' (under Start / Programs).
Figure 3-1 FSC Navigator shortcut on desktop
You can start FSC Navigator by double-clicking the desktop shortcut,

or by moving to the 'Honeywell SMS' program group and choosing
the 'FSC Navigator 5xx' option (where '5xx' is the version number).
It is not possible to run two instances of FSC Navigator. If you

attempt to start FSC Navigator for a second time, the instance that was
started last will be closed automatically.
Closing
FSC Navigator FSC Navigator can be closed in any of the following four ways:
• From the File menu on FSC Navigator's menu bar, choose Exit.
• From the Control menu (which is called up by clicking the box in
the upper left corner of the application window), choose Close.
• With the main application window active, hold down the ALT key
and press F4.
• Click the icon in the upper right corner of the application
window.
Software Manual
3-2 Section 3: Using FSC Navigator
Main screen After FSC Navigator has started up successfully, the main screen will
be displayed (see Figure 3-2). This screen contains the following
areas:
• the title bar, which contains the project name and system number
(if an FSC project has been selected),
• the menu bar (see subsection 3.2), which can be used for selecting
the functions of FSC Navigator,
• the button bar (see subsection 3.4), with speed buttons for quick
access to certain functions, and
• the navigation area (see subsection 3.5), which provides links to
various parts of FSC Navigator and provides a good "guideline" for
the design and maintenance cycle.
Figure 3-2 FSC Navigator main screen
Software Manual
3.2 FSC Navigator Packages
FSC Navigator FSC Navigator is available in four packages. The customer will
packages always purchase a particular package. A unique license number is
then issued which allows the customer to install and use the
appropriate package. The four FSC Navigator packages are:
• Demo
This package has limited functionality and is primarily for
demonstration purposes.
• Standard
This package offers all FSC Navigator functions.
• Contractor
This package has limited functionality and allows FSC
contractors to design a system.
• Hartmann & Braun
This package is functionally identical to the Standard package,
but it also supports the Hartmann & Braun (H&B)
communication protocol.
Table 3-1 below lists the differences between the various software
packages.
Table 3-1 FSC Navigator packages

FSC Navigator packages
Function Demo Contractor Standard H&B
System configuration = = = =
Print = = = =
Design FLDs = = = =
Max. number of FLDs in project 10* 999** 999** 999**
View log files = = = =
Translate application – = = =
Program EPROMs – – = =
Load into flash memory – – = =
Edit SER formats – – = =
Verify application – – = =
Monitor system and view
– – = =
process status
Modem functionality – – = =
FSC-SMM support = = = =
PlantScape support = = = =
Safety Checker – = = =
H&B comm. protocol + P-Bus – – – =
* Function blocks can be defined in FLD 5 and higher.
** Function blocks can be defined in FLD 500 and higher.
Software Manual
3.3 Menu Bar
Menu bar The FSC Navigator application provides a menu bar for easy access
to all program functions. Figure 3-4 on the next page shows an
overview of the program's menu structure.
As shown in Figure 3-2, the menu bar is made up of a number of
drop-down menus, which can be easily accessed by clicking on them.
The following drop-down menus can be selected from the menu bar:
• File
• Project
• On-Line
• Options
• Help
Each drop-down menu or menu item contains an underlined shortcut
character, which allows direct access to that menu or menu item by
holding down the ALT key on the keyboard and pressing the shortcut
character. For example, the File drop-down menu can be called up by
pressing ALT + F (or f).
Figure 3-4 on the next page shows a diagram with all available menu
options.
Menu availability If no FSC project has been selected, the Project menu and On-Line
menu (and all their related buttons and shortcuts) are not available.
Menu options will only be available if they are valid options. If, for
example, certain log files are not available for viewing, the
corresponding options on the View Log submenu will be disabled:
Figure 3-3 Unavailable menu options

Some menu options may not be available, depending on the FSC
Navigator package (see subsection 3.2). Menu options will also not be
available if there are any errors, e.g. if the corresponding application
component does not exist or is corrupted.
Software Manual
FSC Navigator File New Project…
Open Project… Project Configuration
Print Functional Logic Diagrams
View Log Translate Application
Exit Safety Checker
Project System Configuration… Verify Application
Design FLDs… Append FLDs
SER Formats… Database Conversion
Translate Application… Database Integrity
Safety Checker... On-Line Rebuild
Program EPROMs… Menu Selection
Download…
Properties…
On-Line Monitor FLDs…
Monitor System…
Extended Diagnostics…
Diagnostics to Disk
Verify Application…
On-Line Rebuild…
Communication Port…
Options Colors…
Scaling Factor...
Help Contents
About…
Figure 3-4 FSC Navigator menu structure
Software Manual
File drop-down The File drop-down menu has the following menu items:
menu
• New Project…
Use this option to create a new FSC project. (For details refer to
subsection 3.9 on page 3-28.)
• Open Project…
Use this option to open an existing FSC project. (For details
refer to subsection 3.9 on page 3-28.)
• Print
Use this option to create hardcopy of the system configuration
or functional logic diagrams of the current FSC project. This
menu option has a submenu, which allows you to choose what
you wish to print. (For details refer to Section 7 of this manual.)
• View Log
Use this option to view the various log files that are available in
FSC Navigator. This menu option has a submenu, which allows
you to choose the specific log file you wish to view. (For details
refer to Section 9 of this manual.)
• Exit
Use this option to quit the FSC Navigator program.
Project drop-down The Project drop-down menu will only be available if an FSC project
menu has been selected. It has the following menu items:
• System Configuration...
Use this option to configure and maintain the system in the
current FSC project. (For details refer to Section 4 of this
manual.)
• Design FLDs...
Use this option to design the functional logic diagrams (FLDs)
which are used to create the application logic. (For details refer
to Section 6 of this manual.)
• SER Formats...
Use this option to define the layout of the sequence-of-event
(SER) messages and reports. (For details refer to Section 5 of
this manual.)
• Translate Application...
Use this option to convert the project function specification
(designed using FLDs) into application code that the FSC
system can use. (For details refer to Section 8 of this manual.)
Software Manual
Project drop-down • Safety Checker...
menu (continued) Use this option to check the safety integrity of the FLDs in
your project. (For details refer to Section 13 of this manual.)
• Program EPROMs...
Use this option to program application EPROMs or
communication EPROMs. (For details refer to Section 10 of
this manual.)
• Download...
Use this option to load software files from your hard disk into
the FSC system. (For details refer to Section 10 of this manual.)
• Properties...
Use this option to set the symbol library that will be used for the
current FSC project. (For details refer to subsection 3.9.4 on
page 3-31.)
On-Line drop-down The On-Line drop-down menu will only be available if an FSC
menu project has been selected. It has the following menu items:
• Monitor FLDs...
Use this option to view the actual status of the variables in the
FLDs of the current FSC project. (For details refer to Section 12
of this manual.)
• Monitor System...
Use this option to monitor the FSC system and view the process
status. (For details refer to Section 12 of this manual.)
• Extended Diagnostics...
Use this option to view and store all diagnostics of the Central
Part(s) in the FSC system. (For details refer to Section 12 of this
manual.)
• Diagnostics to Disk...
Use this option to back up the extended diagnostic database to
hard disk or retrieve a previously stored database. (For details
• Verify Application...
Use this option to verify the integrity of an FSC application by
comparing the application in the FSC system to the project
database in FSC Navigator. (For details refer to Section 11 of
this manual.)
• On-Line Rebuild
Use this option to rebuild the FSC project databases. (For
details refer to Section 4 of this manual.)
Software Manual
On-Line drop-down • Communication Port...
menu (continued) Use this option to set the communication port that FSC
Navigator uses to communicate with the FSC system. (For
details refer to subsection 3.7 on page 3-25.)
Options drop-down Use this menu option to set a number of program options. The
menu Options drop-down menu has the following menu item:
• Colors…
Use this option to change the color settings of FSC Navigator.
(For details refer to subsection 3.11 on page 3-34.)
• Scaling Factor…
Use this option to set the scaling factor of FSC Navigator (For
details refer to subsection 3.12 on page 3-38.)
Help drop-down Use this menu option to access the help information of FSC
menu Navigator. The Help drop-down menu has the following menu items:
• Contents
Use this option to call up the Windows help facility that comes
with FSC Navigator.
• About...
Use this option to display a window which contains information
about the application (including version numbers). (For details
Software Manual
3.4 Button Bar
Button bar FSC Navigator's main screen contains a button bar with a number of
speed buttons that provide quick access to certain program functions
(see Figure 3-5). If any program options are unavailable, the
corresponding speed buttons will be disabled.
Figure 3-5 Button bar
If there is a down arrow ( ) to the right of the button icon, clicking the
speed button will open a submenu (see Figure 3-6).
Figure 3-6 Button bar with submenu
The speed buttons basically act as "shortcuts" to menu items on the

menu bar. Table 3-2 shows the links between the speed buttons and
the menu bar. For details on the menu bar refer to subsection 3.3 on
page 3-5.
Table 3-2 Links between speed buttons and menu items

Speed button... Links to menu item...
New File / New Project
Open File / Open Project
Print File / Print
I/O Project / System Configuration
FLD Project / Design FLDs
Translate Project / Translate Application
Diagnostics On-Line / Extended Diagnostics
Verify On-Line / Verify Application
Monitor On-Line / Monitor System
View Log File / View Log
Software Manual
3.5 Navigation Area
Navigation area The navigation area in FSC Navigator's main screen contains a
chronological representation of the FSC design and maintenance
cycle (see Figure 3-7).
Figure 3-7 FSC design and maintenance cycle
This visualization provides a good guideline when designing and

maintaining FSC systems. The route has been subdivided into three
main components (represented by three yellow circles):
• Project Configuration,
• Safety Compliance, and
• On-Line Environment.
Each component represents a stage in the design and maintenance

cycle, with a number of distinct tasks.
Clicking any of the three circles in the navigation area will take you to
the corresponding screen (see Figure 3-8, Figure 3-9 and Figure 3-10).
Software Manual
3.5.1 FSC Project Configuration Screen
Project The FSC Project Configuration screen is the starting point for each
configuration new FSC project. It consists of a number of stages:
− creation of the FSC project,
− configuration of the FSC project,
− definition of the FSC project logic,
− translation of the FSC project logic into application code, and
− transfer of the FSC application to memory and/or EPROMs.
If you click the 'Project Configuration' circle in the navigation area,

the FSC Project Configuration screen will appear:
Figure 3-8 FSC Project Configuration screen
Software Manual
This screen presents a chronological sequence of tasks that must be
accomplished to successfully create and implement an FSC project.
Clicking any of the yellow buttons will take you to the corresponding
FSC Navigator option. If there is a down arrow ( ) to the right of the
button text, clicking the button will open a submenu (see Figure 3-9).
Figure 3-9 Button in navigation area with submenu

If any program options are unavailable, the corresponding buttons or
menu options in the navigation area will be disabled.
The buttons at the bottom of the screen allow you to go back to the
main screen or move forward to the FSC Safety Compliance screen or
FSC On-Line Environment screen.
Options The FSC Project Configuration screen contains the following buttons:
• New
Use this option to create a new FSC project. (For details refer to
subsection 3.9 on page 3-28.)
• Open
Use this option to open an existing FSC project. (For details
• System Configuration
Use this option to configure and maintain the system(s) in the
manual.)
• Design Functional Logic Diagrams
Use this option to design the functional logic diagrams (FLDs)
which are used to create the application logic. (For details refer
• Translate Application
Use this option to convert the application function specification
(designed using FLDs) into program code that the FSC system
can use. (For details refer to Section 8 of this manual.)
• Load Software / Program EPROMs
Use this option to program application EPROMs or
communication EPROMs. (For details refer to Section 10 of
this manual.)
• Load Software / Download
Use this option to load software files from your hard disk into
the FSC system. (For details refer to Section 10 of this manual.)
Software Manual
The buttons and submenu options in the FSC Project Configuration
screen basically act as "shortcuts" to menu items on the menu bar.
Table 3-3 shows the links between the buttons and the menu bar. For
details on the menu bar refer to subsection 3.2 on page 3-4.
Table 3-3 Links between buttons and menu items

(FSC Project Configuration screen)
Button... Links to menu item...
New File / New Project
Open File / Open Project
System Configuration Project / System Configuration
Design Functional Logic Diagrams Project / Design FLDs
Translate Application Project / Translate Application
Load Software / Program EPROMs Project / Program EPROMs
Load Software / Download Project / Download
Software Manual
3.5.2 FSC Safety Compliance Screen
Safety compliance The FSC Safety Compliance screen provides a number of links that
allow you to:
− view the log files that are available in FSC Navigator,
− print the system configuration or FLDs,
− verify the application that was created in the FSC Project
Configuration screen, and
− check the safety integrity of the FLDs in your project.
If you click the 'Safety Compliance' circle in the navigation area, the
FSC Safety Compliance screen will appear:
Figure 3-10 FSC Safety Compliance screen
Software Manual
This screen presents a number of individual tasks that allow you to
verify the integrity of an application and create output of system
information (on screen or to a printer).

main screen or the FSC Project Configuration screen, or move
forward to the FSC On-Line Environment screen.
Options The FSC Safety Compliance screen contains the following buttons
and options:
• View Log
Use this option to view the various log files that are available in
FSC Navigator. This menu option has a submenu, which allows
you to choose the specific log file you wish to view. (For details
• Print
Use this option to create hardcopy of the system configuration
or functional logic diagrams of the current FSC project. This
menu option has a submenu, which allows you to choose what
you wish to print. (For details refer to Section 7 of this manual.)
• Safety Checker
Use this option to check the safety integrity of the FLDs in your
project. (For details refer to Section 13 of this manual.)
• Verify Application
Use this option to verify the integrity of an FSC application by
comparing the application program in the FSC system to the
application database in FSC Navigator.
This is a very important option. It verifies if the FSC
application software as present in the FSC system is consistent
with the FSC database and the functional logic diagrams as
maintained by FSC Navigator on the user station. (For details
Software Manual
The buttons and submenu options in the FSC Safety Compliance
screen basically act as "shortcuts" to menu items on the menu bar.

(FSC Safety Compliance screen)
View Log (with submenu) File / View Log (with submenu)
Print (with submenu) File / Print (with submenu)
Verify Application On-Line / Verify Application
Safety Checker Project / Safety Checker
Software Manual
3.5.3 FSC On-Line Environment Screen
On-line environment The FSC On-Line Environment screen provides a number of links
that allow you to:
− monitor the FSC system,
− view the status of I/O signals, system variables and FLDs,
− access and process extensive diagnostic information.
If you click the 'On-Line Environment' circle in the navigation area,

the FSC On-Line Environment screen will appear:
Figure 3-12 FSC On-Line Environment screen
Software Manual
This screen presents a number of individual tasks that allow you to
monitor the FSC system and access diagnostic information.

main screen, the FSC Safety Compliance screen or the FSC Project
Configuration screen.
Options The FSC On-Line Environment screen contains the following

buttons:
• Process Status Monitoring / Monitor FLDs
Use this option to view the actual status of the variables in the
FLDs of the current FSC project. (For details refer to Section 12
of this manual.)
• Process Status Monitoring / Variable Status
Use this option to view the actual status of the variables of the
manual.)
• Process Status Monitoring / List Forces
Use this option to view a list of all forced variables in the FSC
system. (For details refer to Section 12 of this manual.)
• I/O Signal Status
Use this option to view the status of the input/output loops. This
menu option has a submenu, which allows you to choose which
loops you wish to view. (For details refer to Section 12 of this
manual.)
• Diagnostics / Extended Diagnostics
Part(s) in the FSC system. (For details refer to Section 12 of this
manual.)
Software Manual
• Diagnostics / Diagnostics to Disk
Use this option to back up the extended diagnostic database to
hard disk or retrieve a previously stored database. (For details
• Diagnostics / I/O Loop Diagnostics
Use this option to view all diagnostics of the I/O loops in the
FSC system. (For details refer to Section 12 of this manual.)
• Diagnostics / System Information
Use this option to view important system parameters of the FSC
system. (For details refer to Section 12 of this manual.)
Some of the buttons and submenu options in the FSC On-Line

Environment screen act as "shortcuts" to menu items on the menu bar.

(FSC On-Line Environment screen)
Process Status Monitoring / On-Line / Monitor FLDs
Monitor FLDs
Diagnostics / On-Line / Extended Diagnostics
Extended Diagnostics
Diagnostics / On-Line / Diagnostics to Disk
Diagnostics to Disk
Software Manual
3.6 Password Protection
3.6.1 Using Passwords
Using passwords Passwords are used to prevent unauthorized users from accessing
certain options in FSC Navigator. If an option is password-protected
and the password has been enabled, you will be asked to enter the
corresponding password. You have three attempts to enter the correct
password before being denied access to the password-protected
program option.
If you enter a password, any valid (i.e. alphanumeric) key stroke is
echoed on screen as an asterisk ('*'). Typing errors can be corrected
using the BACKSPACE key.
Whenever a password is required, the supervisor password will be
accepted as a correct password.
3.6.2 Password Types
Passwords There are five different password types:

• Forcing variables,
• Writing variables,
• Loading software,
• Engineering, and
• Supervisor.
Forcing variables The 'Forcing variables' password secures the access to the 'Force'
options in the on-line environment of FSC Navigator.
If the password has been disabled, no password is required.
Writing variables The 'Writing variables' password secures the access to the 'Write'
options in the on-line environment of FSC Navigator.
Loading software The 'Loading software' password secures all software download
options of FSC Navigator.
Software Manual
Engineering The 'Engineering' password secures the access to the following FSC
Navigator options:
Menu bar: – Project / System Configuration
– Project / Design FLDs
– Project / SER Format
– Project / Translate Application
– On-Line / On-Line Rebuild
Speed buttons: – I/O
– FLD
– Translate
Navigation area: In FSC Project Configuration screen:
– System Configuration button
– Design Functional Logic Diagrams button
– Translate Application
Supervisor The 'Supervisor' password is used to prevent unauthorized users from

changing and/or deleting passwords. It can also be used to access any
password-protected FSC Navigator option.
3.6.3 Password Maintenance
Password Some options of FSC Navigator are password-protected to prevent

protection unauthorized access to these options. Enabling and disabling the use
of passwords is accomplished through the System Configuration
option, which can be called up in three ways:
• Clicking the System Configuration button in the FSC Project
Configuration screen,
• Clicking the I/O speed button on the button bar, or
• Choosing the System Configuration option from the Project
menu.
To set the passwords, choose Install / Password from the menu line. If
you choose the Password option, you will first be asked to enter the
supervisor password. This is a special password that prevents
unauthorized users from changing and/or deleting passwords. In the
application's initial state, the supervisor password is 'SUPER' (in
capital letters) and all other passwords are disabled. If you have
entered the correct supervisor password, the screen as shown in Figure
3-14 on the next page will appear.
Software Manual
Figure 3-14 Password definition screen
If a password is enabled, it is identified by eight asterisks ('*'), which

are displayed to the right of the password. A disabled password is
identified by the text 'Unused'. All passwords can be disabled, except
for the supervisor password.
Setting To enable a password, move the cursor to the line of the password
a password you wish to set, and press 'C'. Enter a password of four to eight
alphanumeric characters. You will be asked to re-enter the password
to confirm. The text to the right of the selected password will change
to eight asterisks ('∗').
Please note that the passwords are case-sensitive (i.e. 'PASSWORD' is
a different password than 'password' or 'PassWord').
Software Manual
Changing If a password is already enabled, there will be eight asterisks ('∗') to
a password its right. To modify a password, move the cursor to the appropriate
line, and press 'C'. If you want to change the supervisor password,
you will first have to enter the old supervisor password. Enter a new
password of 4 to 8 alphanumeric characters. You will be asked to re-
enter the password to confirm.
Disabling Only enabled passwords can be disabled (except the supervisor

a password password). To disable a password, move the cursor to the line of the
password you wish to disable, and press 'D'. You will be asked to
confirm the action. The eight asterisks ('*') to the right of the selected
password will change to 'Unused'.
3.6.4 Passwords in Converted Projects
Passwords in Existing projects that were created with an FSC software release prior
converted projects to R500 are automatically converted to the current R5xx release when
they are opened in FSC Navigator. If these projects include password
protection, all passwords in the converted project are set to their
defaults:
Supervisor: SUPER (in capital letters)
Forcing variables: empty (i.e. not used)
Writing variables: empty (i.e. not used)
Loading software: empty (i.e. not used)
Engineering: empty (i.e. not used)
Software Manual
3.7 Communication Port
FSC Navigator uses a serial communication link (RS-232 or RS-485)

to interface with the FSC system. The program can only communicate
with the FSC system if the communication port has been set correctly.
Setting the To set the communication link for the current project, do the
communication port following:
1. From the On-Line menu, choose Communication Port.
2. The dialog window as shown in Figure 3-15 will appear.
Figure 3-15 Setting the communication port
3. Select the appropriate communication port from the drop-down

list (see below).
4. Choose the OK button to confirm or Cancel to abort the
operation. Any changes will become effective immediately.
Supported The following communication ports are supported:

communication – COM1 (standard PC serial port)
ports – COM2 (standard PC serial port)
− COM3 (serial port on a third-party serial interface module)
− COM4 (serial port on a third-party serial interface module)
− 07177 - RS232 (serial port on the HSMS-proprietary PC serial
interface module 07177/1/1)
− 07177 - RS485 (serial port on the HSMS-proprietary PC serial
interface module 07177/1/1)
The default FSC communication port is COM1.
Software Manual
Defining ports in Communication ports need to be defined in Windows NT/2000 and
Windows NT/2000 their settings need to be specified. It is not sufficient for the port
hardware to be present in the FSC user station. Ports are defined in
Control Panel, via the Ports icon:
Figure 3-16 Port icon in Control Panel (Windows NT)
For details on how to define ports in Windows NT/2000 refer to the

Windows documentation or Help file.
Note:
The drop-down list in Figure 3-15 will always list all supported
port types, regardless of whether they are actually present and/or
defined on the FSC user station. If you choose a communication
port that does not exist or whose settings are not correct,
communication with the FSC system will not work properly.
Software Manual
3.8 User and Version Information
User information FSC Navigator is licensed to a particular "user" (which may also be a
company). To view the license information, choose the About option
from the Help menu. This will open the window as shown in Figure
3-17. This window shows the user that FSC Navigator is licensed to,
as well as the application's serial number.
Figure 3-17 User and version information
Version information The About box has an extra button called More Info. If you choose
this button, a new window will open (see Figure 3-18), which
provides detailed information about the versions of the various
application components of FSC Navigator.
Figure 3-18 Version information
Software Manual
3.9 Working with Projects
3.9.1 Creating a New Project
Creating
a new project To create a new project, do any of the following:
• From the File menu on FSC Navigator's menu bar, choose New
Project.
• On the speed button bar, choose the New button.
• In the FSC Project Configuration screen, choose the New button.
This will open the following window:
Figure 3-19 Creating a new project
The OK button will initially be disabled and cannot be selected. It will

become available as soon as a valid project name and system number
have been entered. A valid project name has a maximum length of
five or six alphanumeric characters (e.g. PROJ1), depending on the
system number. The system number must be between 1 and 63. If you
use a double-digit system number (≥ 10), the length of the project
name is limited to a maximum of five characters.
If you enter the name and system number of an existing project, the
OK button will remain disabled. To open an existing project, use the
Open option (see below).
The Project Name box accepts alphanumeric characters (i.e. letters
and numbers) and dashes ('-'). No other special characters are accepted
(including '_', &, ä, Ü, é, etc.). The System Number box only accepts
numeric input (between 1 and 63).
Note:
You cannot create a new project with diacritics (e.g. ä, Ü, é) in
its name, but it is possible to open (i.e. import) an existing
project.
Software Manual
When creating a new project, you must also select a symbol library
from the Symbol Library drop-down list. For details on symbol
libraries refer to subsection 3.9.4 on page 3-31.
After you have specified all required data for the new project and you
choose the OK button, the following message will be displayed:
Missing <project name> application database.
Create new? (Y/N) (Enter=Y)
Press 'Y' to create the required application database.
After you have created a new project, its name will be shown in the
main screen's title bar to indicate it is now active:
Figure 3-20 Project name in main screen's title bar
3.9.2 Opening an Existing Project
Opening
an existing project To open an existing project, do any of the following:
• From the File menu on FSC Navigator's menu bar, choose Open
Project.
• On the speed button bar, choose the Open button.
• In the FSC Project Configuration screen, choose the Open button.
This will open the following (resizeable) window:
Figure 3-21 Opening an existing project
Software Manual
To open a project, select a project from the list of available projects
and choose the OK button.
The OK button will initially be disabled and cannot be selected. It will
become available as soon as an existing project has been selected from
the list. (If the selected project is the currently open project, the OK
button will remain disabled.)
Note:
You can open (i.e. import) an existing project with diacritics
(e.g. ä, Ü, é) in its name, but you cannot create a new project.
After you have opened an existing project, its name will be shown in
the main screen's title bar (see Figure 3-20 on page 3-29).
When you quit FSC Navigator with a project opened, the program
remembers which project was open. It will then automatically load
this project the next time you start FSC Navigator, unless the project's
integrity has been compromised, e.g. if one of the project files (see
'Project files' below) has become corrupt. In that case no project will
be loaded.
3.9.3 Project Conversion
Project conversion If you open an existing project that was created with an earlier
version of the FSC user software, you may be asked whether the
project should be converted:
FSC application database conversion is required.
Convert? (Y/N)
If you choose Yes, the project will be converted and opened. If you
choose No, the project will not be opened. If the project cannot be
converted, a message will be displayed on screen.
Notes:
1. If a project is converted from a previous version, its version
counter is incremented by one.
2. A subfolder '\BACKUP.TMP' is used to store a temporary
backup of the application being converted. If this folder
already exists, conversion of the application will be aborted.
In that case you should remove this folder and convert the
application again.
Software Manual
Conversion log file After the conversion, a log file is created which can be viewed using
the View Log option of the File menu. (For details on log files refer
Important!
Before you continue, make sure you inspect the conversion log
file to verify that the conversion was successful.
3.9.4 Project Files
Project files FSC Navigator creates a number of files for every project, and stores
them in a subfolder of the main application folder (C:\FSC by
default). The subfolder is created automatically upon creation of the
project, and will have the same name as the project name (e.g.
PROJ1). The project files are identified by their project name and
system number, which are separated by an underscore sign (e.g.
PROJ1_1). The various file types are identified by their file
extension.
The project files are essential for the project, and if any of them are
corrupted or deleted, the project integrity is compromised. This may
mean that the project can no longer be opened and will not be shown
in the list of available projects. In some cases, the project can be
opened, but the error will become apparent as soon as a particular
program option is called which needs the corrupted or deleted file.
The project subfolder also contains an initialization (INI) file, which

stores which symbol library is used for the project (SYM1 by default).
If this file is corrupted or deleted and the project is opened, SYM1
will be assumed as the symbol library.
Note:
You should make sure that Windows NT/2000 shows all files,
and does not hide certain system files. If you do not, you may
encounter problems if any of your projects has a functional logic
diagram (FLD) with the number 386. (Please note that this is not
a problem related to FSC Navigator, but a Windows-related
issue.) For details refer to subsection 2.5 of this manual.
Software Manual
3.10 Symbol Libraries
New projects When creating a new project, you must also select the symbol library
that will be used with the new project. A symbol library contains the
symbols that can be used to create the functional logic diagrams
(FLDs). Table 3-6 below lists the available symbol libraries and their
characteristics. The default symbol library is SYM1.
Table 3-6 Available symbol libraries

Library name Contents Orientation
SYM1 DIN standard symbols Landscape
SYM2 DIN standard symbols Portrait
Existing projects It is possible to change the symbol library of an existing project. To

change the symbol library, do the following:
1. Make sure that the current project is the project whose symbol
library you wish to change.
2. From the Project menu, choose Properties.
3. The dialog window as shown in Figure 3-22 will appear.
Figure 3-22 Project properties
The Project Name box and System Number box are disabled and
cannot be changed.
To change the symbol library, select the new symbol library from the
drop-down list and choose the OK button. The OK button will
initially be disabled and cannot be selected. It will become available
as soon as a new symbol library has been selected from the list.
Choose the OK button to confirm the change or Cancel to abort the
operation.
Software Manual
Exchangeability of There are some limitations as to the "exchangeability" of symbol
symbol libraries libraries. Table 3-7 below shows which symbol libraries can be
exchanged in which situations.
Table 3-7 Exchangeability of symbol libraries

Current Any FLDs Symbol library can
symbol library in project? be changed to...
No SYM2, SYM3, SYM4

SYM1
Yes SYM2
No SYM1, SYM3, SYM4

SYM2
Yes no changes possible
No SYM1, SYM2, SYM4

SYM3
Yes SYM4
No SYM1, SYM2, SYM3

SYM4
Yes no changes possible
Note:
Within an FSC network, the application of the FSC systems that
are interconnected via an FSC-FSC communication link must be
designed using the same symbol library.
Software Manual
3.11 Color Settings
Colors FSC Navigator uses particular default color settings for the various
program items. These can, however, be modified to suit your
particular needs. To change the color settings, choose Colors… from
the Options menu. The following window will appear:
Figure 3-23 Setting the colors in FSC Navigator
Warning!
Changing the color settings may affect the visibility of
safety-related items.
Color schemes In the window shown in Figure 3-23 you can define which colors
should be used to display the various program items. The Color
Scheme drop-down list allows you to choose between a number of
color sets:
• FSC Navigator: This is the preset color scheme that is used for
FSC R530.
• FSC Classic: This is the preset color scheme that was used for
FSC releases prior to R500.
• (user-defined): This is a color scheme that allows you to specify
your own set of colors.
The color settings are stored in the FSC.INI initialization file, which is
located in the FSC Navigator application folder (C:\FSC by default).
Software Manual
Color items The list below the Color Scheme drop-down list specifies a number
of color items whose colors you can review. If you chose
"(user-defined)" as the color scheme, you can also modify their color
settings (see next page). To select an item, simply click on it. The
following program items are listed:
• Normal Items:
This color is basically used for all items that do not match any of
the items below, e.g. normal text on screens.
• Selected Text:
This color is typically used to show the cursor position in menu
bars or to indicate active data entry fields.
• Highlighted Text:
This color is typically used to indicate valid (navigation)
keystrokes on the keyboard, e.g. <Enter> or <PgUp> in status bar
messages or help screens.
• Safety-Related Items:
This color is typically used in the FLD design editor to indicate
that an I/O symbol is safety-related. Non safety-related symbols
are typically shown in the 'normal' color.
• Progress Bar:
This color is used for the progress bars, which indicate the
completion status of an operation (as a percentage bar running
from 0% to 100%), e.g. during software download.
• Error Text:
This color is used for error messages in the status bar, e.g. after
illegal keyboard input or communication errors.
• Borders:
This color is used for any borders other than in FLDs, e.g. the
lines around popup windows.
• Disabled Items:
This color is used to indicate items that are not available in a list,
e.g. unavailable modules in signal allocation screens.
• PID Setpoint:
This color is used to indicate PID setpoints in PID screens.
• PID Input:
This color is used to indicate PID inputs in PID screens.
• PID Output:
This color is used to indicate PID outputs in PID screens.
• Logic:
This color is used for the symbols and lines in FLDs.
Software Manual
Color matrix The color matrix shows the foreground and background color that are
currently used for the selected item, and the available colors you can
choose from.
The foreground color currently used for the selected item is indicated
by the letters 'FG' in the corresponding color box, and the background
color by the letters 'BG'. In the window shown in Figure 3-23, for
example, "Normal Items" are shown in black in a white background
(in accordance with the preset user-defined color scheme).
Default colors Table 3-8 below lists the default colors that are used for the various
color schemes.
Table 3-8 Color settings for the various color schemes

Color schemes
Program item FSC Navigator FSC Classic User-defined

(defaults)
Normal items FG: black FG: green FG: black
BG: light gray* BG: black BG: light gray*
Selected text FG: dark blue FG: black FG: dark blue
BG: light gray* BG: green BG: light gray*
Highlighted text FG: blue FG: yellow FG: blue
Safety-related items FG: red FG: red FG: red
Progress bar FG: dark blue FG: green FG: dark blue
Error text FG: red FG: red FG: red
Borders FG: black FG: green FG: black
Disabled items FG: dark gray FG: dark green FG: dark gray
PID setpoint FG: cyan FG: cyan FG: cyan
PID input FG: yellow FG: yellow FG: yellow
PID output FG: red FG: red FG: red
Logic FG: dark blue FG: white FG: dark blue
* is displayed as white in graphical screens (e.g. related to FLDs and PIDs).
Software Manual
Changing If you chose "(user-defined)" as the color scheme, you can modify
the colors the color settings for each individual program item.
You can change the foreground color by moving the mouse cursor to
the desired color box and clicking the left mouse button (or, if the
mouse button function has been reversed, the right button). The
selected color box will now contain the letters 'FG' to indicate that the
new foreground color has been set.
You can change the background color by moving the mouse cursor to
the desired color box and clicking the right mouse button (or, if the
mouse button function has been reversed, the left button). The selected
color box will now contain the letters 'BG' to indicate that the new
background color has been set.
If you are done changing the color settings, click the OK button. The
new color settings will take effect immediately.
To abort the operation and discard any changes you made, click the
Cancel button.
Software Manual
3.12 Scaling Factor
Scaling factor All FSC Navigator screens can be resized. However, if you resize a
text-oriented window by dragging its edges, only the window as such
is resized, not its contents. Thus, if you reduce the size of a window
so that it is smaller than its contents, a portion of the contents will no
longer be visible, and horizontal and/or vertical scroll bars will then
appear (see Figure 3-24).
Figure 3-24 Resizing a window by dragging its edges
If you want the contents of text-oriented screens to be displayed larger

or smaller, you need to adjust the scaling factor, which determines the
"magnification" of FSC Navigator's screens.
To change the scaling factor, do the following:
1. From the Options menu, choose Scaling Factor. The following
window will appear:
Figure 3-25 Scaling factor
Software Manual
2. Choose the desired magnification from the Scaling Percentage
drop-down list. The initial default is 100% (i.e. no magnification).
You can choose any value between 100% and 200% (in steps of
10%).
3. When you are done, click the OK button. The new settings will
take effect immediately. The next time you open a text-oriented
FSC Navigator screen, it will be displayed according to the new
setting. The scaling factor will remain effective until it is changed
again.
Notes:
1. The scaling factor does not affect FSC Navigator's main
screen or the Print dialogs.
2. This option is particularly useful for high screen resolutions,
especially for displaying FLDs. By increasing the scaling
factor, you can view them in high detail.
Software Manual
3.13 Basic Operations in Program Components
Mouse support Most of the program components of FSC Navigator are text-oriented.
Besides the main program, the only graphical components are the
program options that involve functional logic diagrams (FLDs) and
printing features.
Mouse support is only available in the graphical components of FSC
Navigator. In text-oriented screens, the mouse cursor will be visible
but cannot be used in the screens.
If mouse support is available, clicking the left mouse button is then
the same as pressing the <Enter> key on the keyboard. It can, for
example, be used to accept the input or to acknowledge an on-screen
message.
Clicking the right mouse button is the same as pressing the <Esc> key
on the keyboard. It can, for example, be used to abort an input action
and return to the menu.
Moving through You can use keys on the keyboard to move through the menus of the
menus program components. If mouse support is available (in graphical
screens), you can also use the mouse.
Mouse If the graphical screen shows a menu, you can move the mouse to
select the desired menu item. A selected menu item is shown
highlighted. If you wish to select the menu item, press the left mouse
button. Either a submenu will be shown or, if there are no more
submenus, the program will execute the selected menu item. The
right mouse button brings you back to the next higher menu level.
Keyboard Use the left and right cursor keys to move left and right in the menu.
A selected menu item will be shown highlighted. If you wish to select
the menu item, press <Enter>. Either a submenu will be shown or, if
there are no more submenus, the program will execute the selected
menu item.
Every menu item has a shortcut key. Pressing the shortcut key is an
easy and fast way to select a menu item. The rightmost menu item
'Main' can be used to return to the next higher menu level. If you are
on the highest menu level, the rightmost menu item will be 'eXit'.
Selecting this menu item will quit the program component and return
to FSC Navigator's main screen.
Software Manual
The following keys can be used to move through the menus in the
FSC Navigator program components: PGUP, PGDN, TAB, ESC, ß, à,
á, â and ENTER.
Intelligent menus Sometimes a different menu may be shown than you might expect,
with menu items added or deleted from the menu. The reason for this
is that "intelligent menu building" has been used throughout the
application software. If, for example, the FSC system configuration is
not known yet, the hardware specification of variables cannot be
edited. The 'Hardware specs' menu option will therefore only be
shown if the FSC system configuration has been defined.
Keyboard input When entering strings (text or values), you can use all standard
ASCII characters with ASCII values between 32 and 127 (letters,
digits, and common symbols) as well as non-graphical extended
ASCII characters (e.g. é, Ä, and Ö). Table 3-9 below lists the various
shortcut keys for keyboard input in the text-oriented FSC Navigator
program components.
Table 3-9 Shortcut keys for data input

Shortcut key Action
<Ctrl> + <A> Moves the cursor to the first character of the string.
<Home> Moves the cursor to the first character of the string.
<Ctrl> + <F> Moves the cursor to the last character of the string.
<End> Moves the cursor to the last character of the string.
<Ctrl> + <V> Toggles between insert and overwrite mode.
<Insert> Toggles between insert and overwrite mode.
<Ctrl> + <G> Deletes the character under the cursor.
<Delete> Deletes the character under the cursor.
<Ctrl> + <H> Deletes the character left of the cursor.
<Backspace> Deletes the character left of the cursor.
<Ctrl> + <T> Deletes all characters after the cursor position.
<Ctrl> + <Y> Deletes the complete string.
<ß/à> Moves the cursor left or right through the entered string.
Software Manual
Function keys In the text-oriented program components, the following function keys
are available for on-line help:
<F1>: A window will appear which provides specific information
about the item that the cursor is on.
<F2>: A window will appear which provides specific information
about variable allocations (only available in the 'System
Configuration' program component). For details refer to
section 4.10.6 of this manual.
Software Manual
Fail Safe Control
Section 4:
System Configuration
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 4: System Configuration

4.1 Introduction .................................................................................................... 4-1
4.2 Basic Configuration Procedure..................................................................... 4-2
4.3 System Configuration Menus ........................................................................ 4-3

4.3.1 Menu Structure................................................................................................................. 4-3
4.3.2 Main Menu........................................................................................................................ 4-4
4.3.3 Install Menu ...................................................................................................................... 4-5
4.3.4 Signal Specs Menu .......................................................................................................... 4-8
4.4 General Application Information ................................................................. 4-10
4.5 Basic System Configuration........................................................................ 4-12

4.5.1 Introduction..................................................................................................................... 4-12
4.5.2 Requirement Class......................................................................................................... 4-13
4.5.3 Central Part Configuration.............................................................................................. 4-15
4.5.4 SER Channel Specification ............................................................................................ 4-16
4.5.5 Modbus Base Address Configuration............................................................................. 4-20
4.5.6 Memory Chip Size Configuration ................................................................................... 4-21
4.5.7 Process Safety Time ...................................................................................................... 4-22
4.5.8 Interval Time Between Faults ("Second Fault Timer") ................................................... 4-23
4.5.9 FSC-FSC Communication Configuration ....................................................................... 4-25
4.5.10 Simulation Mode............................................................................................................. 4-26
4.5.11 Memory Type ................................................................................................................. 4-29
4.5.12 Power-On Mode ............................................................................................................. 4-29
4.5.13 On-Line Modification Wanted......................................................................................... 4-30
4.6 Defining the Physical Cabinet Layout......................................................... 4-31
4.7 Installing Modules ........................................................................................ 4-34

4.7.1 Overview ........................................................................................................................ 4-34
4.7.2 Installing a Power Supply Unit (PSU)............................................................................. 4-39
4.7.3 Central Part (CP) Definition............................................................................................ 4-44
4.7.4 Installing a Central Processing Unit (CPU) .................................................................... 4-48
4.7.5 Installing a Watchdog (WD) ........................................................................................... 4-49
4.7.6 Installing a Communication Module (COM) ................................................................... 4-49
4.7.7 Installing a Safety Manager Module (SMM)................................................................... 4-58
4.7.8 Installing a PlantScape Interface Module....................................................................... 4-60
4.7.9 Installing a Diagnostic and Battery Module (DBM) ........................................................ 4-63
4.7.10 Installing a Single Bus Driver (SBD) .............................................................................. 4-66
4.7.11 Installing a Vertical Bus Driver (VBD) ............................................................................ 4-66
4.7.12 Installing a Horizontal Bus Driver (HBD) ........................................................................ 4-69
4.7.13 Installing Input and Output Modules (I/O) ...................................................................... 4-71
4.8 Signal Specification ..................................................................................... 4-77

4.8.1 Introduction..................................................................................................................... 4-77
4.8.2 Adding Signals ............................................................................................................... 4-79
4.8.3 Browsing Through Signals ............................................................................................. 4-81
4.8.4 Modifying and Deleting Signals...................................................................................... 4-81
4.8.5 Searching for Variables.................................................................................................. 4-84
Software Manual
Section 4: System Configuration i
4.9 Importing and Exporting Variables using dBASE Files ............................. 4-85
4.9.1 Introduction..................................................................................................................... 4-85
4.9.2 dBASE File Format......................................................................................................... 4-86
4.9.3 Writing Variables to a dBASE File.................................................................................. 4-88
4.9.4 Reading Variables from a dBASE File ........................................................................... 4-89
4.10 Hardware Specification ................................................................................ 4-94

4.10.1 Introduction..................................................................................................................... 4-94
4.10.2 Allocation of Inputs and Outputs to I/O Modules............................................................ 4-95
4.10.3 Allocation of Inputs and Outputs to COM Modules ...................................................... 4-101
4.10.4 Automatic Allocation of Variables................................................................................. 4-104
4.10.5 Automatic Allocation of SER Sequence Numbers ....................................................... 4-104
4.10.6 Reviewing Allocations using the <F2> Function Key ................................................... 4-106
4.11 Configuration of Digital Input Signals (I) .................................................. 4-113

4.11.1 Location = 'COM' .......................................................................................................... 4-113
4.11.2 Location = 'FSC' ........................................................................................................... 4-116
4.11.3 Location = 'ANN'........................................................................................................... 4-118
4.11.4 Location = 'SYS' ........................................................................................................... 4-120
4.11.5 Other Locations ............................................................................................................ 4-122
4.12 Configuration of Analog Input Signals (AI)............................................... 4-125

4.12.1 Location = 'SYS' ........................................................................................................... 4-125
4.12.2 Other Locations ............................................................................................................ 4-128
4.13 Configuration of Binary Input Signals (BI)................................................ 4-131

4.13.1 Location = 'COM' .......................................................................................................... 4-131
4.13.2 Location = 'FSC' ........................................................................................................... 4-133
4.13.3 Location = 'MUX' .......................................................................................................... 4-135
4.13.4 Other Locations ............................................................................................................ 4-137
4.14 Configuration of Multiplexer Inputs (XI).................................................... 4-139
4.15 Configuration of Digital Output Signals (O).............................................. 4-142

4.15.1 Location = 'COM' .......................................................................................................... 4-142
4.15.2 Location = 'FSC' ........................................................................................................... 4-144
4.15.3 Location = 'ANN'........................................................................................................... 4-146
4.15.4 Location = 'SYS' ........................................................................................................... 4-148
4.15.5 Other Locations ............................................................................................................ 4-150
4.16 Configuration of Analog Output Signals (AO) .......................................... 4-152
4.17 Configuration of Binary Output Signals (BO) ........................................... 4-154

4.17.1 Location = 'COM' .......................................................................................................... 4-154
4.17.2 Location = 'FSC' ........................................................................................................... 4-157
4.17.3 Location = 'MUX' .......................................................................................................... 4-159
4.17.4 Other Locations ............................................................................................................ 4-161
4.18 Configuration of Multiplexer Outputs (XO) ............................................... 4-163
Software Manual
ii Section 4: System Configuration
4.19 Configuration of Markers (M)..................................................................... 4-165
4.20 Configuration of Counters (C) ................................................................... 4-167
4.21 Configuration of Timers (T) ....................................................................... 4-169
4.22 Configuration of Registers (R) .................................................................. 4-171
4.23 Configuration of PIDs (P) ........................................................................... 4-173
4.24 Configuration of Alarms (A)....................................................................... 4-176
4.25 Rebuilding an Application ......................................................................... 4-178

4.25.1 Off-Line Rebuilds.......................................................................................................... 4-178
4.25.2 On-Line Rebuilds.......................................................................................................... 4-179
Software Manual
Section 4: System Configuration iii
FIGURES
Figure 4-1 System configuration: menu structure ........................................................................ 4-3
Figure 4-2 System configuration: main menu............................................................................... 4-4
Figure 4-3 System configuration: install menu ............................................................................. 4-5
Figure 4-4 System configuration: modules menu......................................................................... 4-6
Figure 4-5 System configuration: central parts menu................................................................... 4-7
Figure 4-6 System configuration: signal specification menu ........................................................ 4-8
Figure 4-7 General application information ................................................................................ 4-10
Figure 4-8 Basic configuration parameters ................................................................................ 4-12
Figure 4-9 SER channel specification ........................................................................................ 4-16
Figure 4-10 Modbus base address configuration ......................................................................... 4-20
Figure 4-11 Memory chip size configuration................................................................................. 4-21
Figure 4-12 Setting the FSC-FSC communication timeout .......................................................... 4-25
Figure 4-13 Simulation mode ....................................................................................................... 4-26
Figure 4-14 Defining rack positions .............................................................................................. 4-32
Figure 4-15 Installation: PSU modules (10300/1/1) ..................................................................... 4-39
Figure 4-16 Installation: power supply units (Delta/external) ....................................................... 4-42
Figure 4-17 Central Part definition................................................................................................ 4-45
Figure 4-18 Selecting the communication module type ............................................................... 4-47
Figure 4-19 Defining the channel configuration............................................................................ 4-50
Figure 4-20 Editing the connected systems ................................................................................. 4-52
Figure 4-21 Defining the link specification.................................................................................... 4-53
Figure 4-22 Defining a secondary link .......................................................................................... 4-55
Figure 4-23 Protocol definition for communication with the TPS system ..................................... 4-58
Figure 4-24 Protocol definition for communication with the PlantScape system ......................... 4-60
Figure 4-25 Diagnostic and battery module (DBM) ...................................................................... 4-63
Figure 4-26 Receiving radius of DCF signal................................................................................. 4-64
Figure 4-27 Vertical bus driver ..................................................................................................... 4-67
Figure 4-28 Horizontal bus drivers ............................................................................................... 4-69
Figure 4-29 Placing I/O modules .................................................................................................. 4-71
Figure 4-30 Selection of a module................................................................................................ 4-74
Figure 4-31 Signal specifications.................................................................................................. 4-77
Figure 4-32 Browsing through signals .......................................................................................... 4-82
Figure 4-33 Variable selection screen .......................................................................................... 4-94
Figure 4-34 Allocation of a I/O variable to a module .................................................................... 4-98
Figure 4-35 Allocation of a I/O variable to a channel ................................................................... 4-99
Figure 4-36 Allocation to a communication module (location 'FSC') .......................................... 4-101
Figure 4-37 Allocation to a communication module (location 'COM')......................................... 4-103
Figure 4-38 Reviewing I/O signal allocations ............................................................................. 4-107
Figure 4-39 Reviewing SER signal allocations........................................................................... 4-109
Figure 4-40 Reviewing DCS signal allocations .......................................................................... 4-110
Figure 4-41 Reviewing communication signal allocations.......................................................... 4-111
Figure 4-42 Reviewing address allocations................................................................................ 4-112
Figure 4-43 Hardware specification: digital inputs (location 'COM') ........................................... 4-113
Figure 4-44 Hardware specification: digital inputs (location 'FSC') ............................................ 4-116
Figure 4-45 Hardware specification: digital inputs (location 'ANN')............................................ 4-118
Figure 4-46 Hardware specification: digital inputs (location 'SYS') ............................................ 4-120
Figure 4-47 Hardware specification: digital inputs (other locations)........................................... 4-122
Figure 4-48 Hardware specification: analog inputs (voltage monitoring for 10105/2/1) ............. 4-125
Figure 4-49 Hardware specification: analog inputs .................................................................... 4-128
Figure 4-50 Hardware specification: binary inputs (location 'COM') .......................................... 4-131
Figure 4-51 Hardware specification: binary inputs (location 'FSC')............................................ 4-133
Figure 4-52 Hardware specification: binary inputs (location 'MUX') ........................................... 4-135
Software Manual
iv Section 4: System Configuration
FIGURES (continued)
Figure 4-53 Hardware specification: binary inputs (other locations) .......................................... 4-137
Figure 4-54 Hardware specification: multiplexer inputs.............................................................. 4-139
Figure 4-55 Hardware specification: digital outputs (location 'COM')......................................... 4-142
Figure 4-56 Hardware specification: digital outputs (location 'FSC').......................................... 4-144
Figure 4-57 Hardware specification: digital outputs (location 'ANN') ......................................... 4-146
Figure 4-58 SER event trigger of a BO variable with location 'COM' or 'FSC' ........................... 4-148
Figure 4-59 Hardware specification: digital outputs (other locations) ........................................ 4-150
Figure 4-60 Hardware specification: analog outputs .................................................................. 4-152
Figure 4-61 Hardware specification: binary outputs (location 'COM') ........................................ 4-154
Figure 4-62 Hardware specification: binary outputs (location 'FSC') ......................................... 4-157
Figure 4-63 Hardware specification: binary outputs (location 'MUX')......................................... 4-159
Figure 4-64 Hardware specification: binary outputs (other locations) ........................................ 4-161
Figure 4-65 Hardware specification: multiplexer outputs ........................................................... 4-163
Figure 4-66 Hardware specification: markers............................................................................. 4-165
Figure 4-67 Hardware specification: counters............................................................................ 4-167
Figure 4-68 Hardware specification: timers................................................................................ 4-169
Figure 4-69 Hardware specification: registers............................................................................ 4-171
Figure 4-70 Hardware specification: PIDs .................................................................................. 4-173
Figure 4-71 Hardware specification: alarms (A) ......................................................................... 4-176
Figure 4-72 Allocation in variables to locations in system memory............................................ 4-180
Figure 4-73 On-Line Rebuild option ........................................................................................... 4-180
TABLES
Table 4-1 Relation between FSC configurations and requirement classes AK1-6,
according to DIN V 19250 ......................................................................................... 4-14
Table 4-2 Central Part configurations ....................................................................................... 4-15
Table 4-3 Conditions for starting the second fault timer ........................................................... 4-24
Table 4-4 Behavior of second fault timer .................................................................................. 4-24
Table 4-5 Simulation hardware units......................................................................................... 4-27
Table 4-6 Memory types............................................................................................................ 4-29
Table 4-7 Central Part modules ................................................................................................ 4-35
Table 4-8 Special modules........................................................................................................ 4-35
Table 4-9 FSC input modules (plug-and-play) .......................................................................... 4-36
Table 4-10 FSC input modules (non plug-and-play) ................................................................... 4-36
Table 4-11 FSC output modules (plug-and-play) ........................................................................ 4-37
Table 4-12 FSC output modules (non plug-and-play) ................................................................. 4-38
Table 4-13 Supported Delta power supply units ......................................................................... 4-43
Table 4-14 Link specification....................................................................................................... 4-54
Table 4-15 DBM temperature settings ........................................................................................ 4-65
Table 4-16 VBD I/O configuration ............................................................................................... 4-67
Table 4-17 VBD module type ...................................................................................................... 4-68
Table 4-18 Voting type per I/O module ....................................................................................... 4-73
Table 4-19 Reserved tag numbers.............................................................................................. 4-80
Table 4-20 Variable field characteristics ..................................................................................... 4-83
Table 4-21 dBASE file format...................................................................................................... 4-86
Table 4-22 Field interpretation for dBASE imports (inputs) ........................................................ 4-90
Table 4-23 Field interpretation for dBASE imports (outputs) ...................................................... 4-91
Table 4-24 I/O modules suited for the different variable types ................................................... 4-97
Table 4-25 Various allocation overview windows called by <F2>............................................. 4-106
Software Manual
Section 4: System Configuration v
Software Manual
vi Section 4: System Configuration
Section 4 – System Configuration
4.1 Introduction
System The 'System Configuration' option of FSC Navigator is used to define

configuration and configure the FSC application (hardware, signals, etc.). The
configuration is stored in a number of databases which can be viewed
and modified.
The 'System Configuration' option of FSC Navigator will only be

available if a project is open. If no project is open, you must either
create a new project or open an existing one (for details refer to
Section 3 of this manual).
The 'System Configuration' option can be called in three ways:
• Menu bar: Project / System Configuration

• Button bar: I/O
• Navigation area: FSC Project Configuration /
System Configuration
Note:
If the Engineering password is active, you must enter the correct
password to start up the 'System Configuration' option of FSC
Navigator. (For details on passwords refer to Section 3 of the
FSC Software Manual or the FSC Navigator Help file.)
Software Manual
Section 4: System Configuration 4-1
4.2 Basic Configuration Procedure
Basic configuration The basic configuration procedure of an FSC application is as

procedure follows:
1. Description of the application.
At this stage you specify general information about the
application, such as the application name and site.
For details refer to subsection 4.4.
2. Definition of the basic configuration.
At this stage you specify a number of basic configuration
parameters, such the safety class, redundancy, and the memory
type used. For details refer to subsection 4.5.
3. Definition of the physical layout of the cabinet(s).
At this stage you define how many cabinets the application
consists of, the number of racks in each cabinet, and what their
positions are in the rack. For details refer to subsection 4.6.
4. Definition of the hardware module positions in the cabinet(s).
At this stage you define which modules are located at what
positions in the cabinet(s). This is normally done in the following
order (for details refer to subsection 4.7):
− Central Part (CP) modules
− Horizontal Bus Drivers (HBD)
− Input and output (I/O) modules.
5. Specification of the signals used in the FSC application.
At this stage you specify the characteristics of all signals that are
used in the FSC application. This can be done manually, but the
signal specification can also be imported from a dBASE file.
For details refer to subsection 4.8 and 4.9.
6. Allocation of I/O variables to I/O module channels or COM
module channels.
At this stage you define the hardware specifications of all input
and output variables that are used in the FSC application.
For details refer to subsections 4.10 to 4.24.
After completing the above configuration procedure, you can proceed

with defining the actual safety application (using the 'Design FLDs'
option of FSC Navigator; see Section 6 of this manual) and translating
the application for use (see Section 8 of this manual).
Software Manual
4-2 Section 4: System Configuration
4.3 System Configuration Menus
4.3.1 Menu Structure
Menu structure Commands can be entered by choosing an option from any of the
configuration menus. Figure 4-1 below shows the menu structure of
the 'System Configuration' option of FSC Navigator.
Main
Install Description
Configuration
Modules PSU
Passwords Central parts Definition
mAin HBD CPU
I/O WD
Signal specs Add mAin COM
Search DBM
Write dBASE SBD
Read dBASE VBD
Main mAin
Hardware specs
Rebuild
eXit
Figure 4-1 System configuration: menu structure
Software Manual
Availability of Menus will always only display options that are relevant for the
menu options current situation. This means that options are only available if they
are meaningful. For example, I/O modules can only be defined if a
horizontal bus driver (HBD) has already been defined. This means
that the 'I/O' option in the Install\Modules menu will not be available
as long as no HBD has been defined.
Activating The 'System Configuration' option of FSC Navigator is entirely

menu options menu-driven. The menus are placed on the bottom line of the screen.
The menus can be accessed using the keyboard. Menu options can be
activated in two ways:
• Use the left and right arrow keys on the keyboard (← and →) to
move the block cursor to the menu option, and press <Enter>.
• Press the first uppercase letter of the menu option. For example, to
activate the 'Hardware specs' command, you should press the <H>
key. If two menu items have the same first uppercase letter, the
rightmost item will use its second uppercase letter as the shortcut
(e.g. \Install\Modules\Central parts\DBM).
If you press <Esc> at any time, you will go back to the menu of the
next highest level.
4.3.2 Main Menu
Main menu The Main menu has two options that open a new menu (Install and
Signal specs). It has the following menu items:
MAIN
Install Signal specs Hardware specs Rebuild eXit
Figure 4-2 System configuration: main menu
Install This menu option will open a new menu that provides a number of
options related to defining the FSC application (see subsection 4.3.3).
Software Manual
Signal specs This menu option will open a new menu that provides a number of
options related to defining and modifying the input and output
variables (see subsection 4.3.4).
Hardware specs Choose this option to define or modify the hardware allocation of all
input and output variables that are used in the FSC application (see
subsections 4.10 to 4.23).
Note:
The 'Hardware specs' option will only be available if the
configuration has already been defined.
Rebuild Choose this option to create new index files in case one or more
index files have become corrupted (e.g. due to a power failure of your
PC). This may, for example, manifest itself if variables appear twice
in the signal specification screen (or not at all). You can also use this
option to change the address allocation if you want to optimize the
memory usage (see subsection 4.25).
eXit Choose this option to return to the main FSC Navigator screen.
4.3.3 Install Menu
Install menu The Install menu provides a number of options related to defining the
FSC application (see subsection 4.7). It has one option that opens a
new menu (Modules). The Install menu has the following options:
MAIN
Install
Description Configuration Modules Passwords mAin
Figure 4-3 System configuration: install menu
Software Manual
Description Choose this option to enter or modify general information about the
application, such as the application name and site. For details refer to
subsection 4.4.
Configuration Choose this option to specify a number of basic configuration

parameters, such the safety class, redundancy, and the memory type
used. For details refer to subsections 4.5 and 4.6.
Modules This menu option will open a new menu that provides a number of
options related to defining and configuring the modules in the FSC
cabinet(s) (see below).
Note:
The 'Module' option will only be available if the configuration
has already been defined.
Passwords Choose this option to define the passwords that restrict access to
certain features of the FSC Navigator software. For details refer to
Section 3 of this manual ("Using FSC Navigator").
mAin Choose this option to go back to the Main menu.
Modules submenu The Modules submenu provides a number of options that are related
to defining and configuring the modules in the FSC cabinet(s). It has
one option that opens a new menu (Central parts). The Modules menu
has the following menu items:
MAIN
Install
Modules
PSU Central parts HBD I/O mAin
Figure 4-4 System configuration: modules menu
PSU Choose this option to install and configure a power supply unit
(PSU). For details refer to subsection 4.7.2.
Software Manual
Central parts This menu option will open a new menu that provides a number of
options related to installing and configuring Central Part (CP)
modules (see below).
HBD Choose this option to install and configure a horizontal bus driver
(HBD). For details refer to subsection 4.7.12.
I/O Choose this option to install and configure a input and output (I/O)
modules. For details refer to subsection 4.7.13.
mAin Choose this option to return to the previous menu.
Central Parts The Central parts submenu provides a number of options that are
submenu related to defining and configuring Central Part (CP) modules. It has
the following menu items:
MAIN
Install
Modules
Central Parts
Definition CPU WD COM DBM SBD VDB mAin
Figure 4-5 System configuration: central parts menu
Definition Choose this option to specify the physical characteristics of Central

Part modules. For details refer to subsection 4.7.3.
CPU Choose this option to install and configure a central processing unit
(CPU). For details refer to subsection 4.7.4.
WD Choose this option to install and configure a watchdog module (WD).

For details refer to subsection 4.7.5.
COM Choose this option to install and configure a communication module

(COM). For details refer to subsections 4.7.6 and 4.7.7.
DBM Choose this option to install and configure a diagnostic and battery
module (DBM). For details refer to subsection 4.7.9.
Software Manual
SBD Choose this option to install and configure a single bus driver (SBD).
VBD Choose this option to install and configure a vertical bus driver
(VBD). For details refer to subsection 4.7.11.
mAin Choose this option to return to the previous menu.
Note:
The options DBM, VBD and SBD will only be available if the
corresponding modules have been defined.
4.3.4 Signal Specs Menu
Signal specs The Signal specs menu provides a number of options related to
menu specifying the characteristics of all signals used in the FSC
application. It has the following options:
MAIN
Signal specs
Add Search Write dBASE Read dBASE Main
Figure 4-6 System configuration: signal specification menu
Add Choose this option to manually add variables to the variable database.
Search Choose this option to search for a variable by (part of the) tag
number, and to view or edit its signal specifications (service,
qualification, location, unit and subunit). For details refer to
subsection 4.8.3.
Write dBASE Choose this option to write the I/O variables of the variable database
to a dBASE compatible file. For details refer to subsection 4.9.
Note:
The 'Write dBASE' option will only be available if at least one
variable has been created (other than the standard system
variables).
Software Manual
Read dBASE Choose this option to read I/O variables from a dBASE compatible
file into the FSC variables database. For details refer to subsection
4.9.
Main Choose this option to return to the previous menu.
Software Manual
4.4 General Application Information
Application When you create a new application, you can enter general
information information about the application, such as the customer name and
site.
To enter or edit this information, choose the following menu options:
Install Description
The following screen will appear:
Figure 4-7 General application information
The standard texts are retrieved from the message file

FSC_INIT.MSG, which is located in the FSC Navigator installation
folder (C:\FSC by default). They can all be customized by the user.
If you change any of the default descriptions, you will be asked
whether the changes should be saved to disk:
Default descriptions changed. Save new defaults? (Y/N)
If you press <Y>, the changes will be saved to the message file.
If you press <N>, the changes are discarded.
Software Manual
Every new application will now use these new default descriptions
until you change them again.
Note:
Information entered in this screen is also used in printouts of the
functional logic diagrams (FLDs). For details refer to Section 7
of this manual ("Printing").
Software Manual
4.5 Basic System Configuration
4.5.1 Introduction
Basic configuration Before you can configure the FSC application and cabinet(s) in detail,
parameters you need to set a number of basic configuration parameters.
To enter or edit these parameters, choose the following menu options:
Install Configuration
The following screen will appear:
Figure 4-8 Basic configuration parameters

The configuration parameters can be divided into two main groups:
• Parameters that define the basic application configuration
(top half of the screen, see subsections 4.5.2 to 4.5.13), and
• Parameters that define the physical layout of the FSC cabinet(s)
(bottom half of the screen, see subsection 4.6).
Software Manual
Basic configuration The top half of the configuration screen as shown in Figure 4-8
parameters contains a number of fields that allow you to specify the following
basic configuration parameters.
• Requirement class (see subsection 4.5.2),
• Central Part architecture (see subsection 4.5.3),
• SER channel configuration (see subsection 4.5.4),
• Modbus base address configuration (see subsection 4.5.5),
• Memory chip size configuration (see subsection 4.5.6),
• Process safety time (see subsection 4.5.7),
• Interval time between faults (see subsection 4.5.8),
• FSC-FSC communication configuration (see subsection 4.5.9),
• Simulation mode (see subsection 4.5.10),
• Memory type (see subsection 4.5.11),
• Power-on mode (see subsection 4.5.12),
• On-line modification wanted (see subsection 4.5.13), and
• Physical cabinet layout (see subsection 4.6).
4.5.2 Requirement Class
Requirement class The 'Requirement class' field in the configuration screen as shown in
Figure 4-8 on page 4-12 allows you to define the safety level that the
application offers. In accordance with DIN V 19250, six requirement
classes (Anforderungsklassen, or AK) can be selected (AK1 to AK6).
AK1 is the lowest requirement class (low safety level), and AK6 the
highest (high safety level).
Use <Space> to toggle between the requirement classes. The default
requirement class is AK4. Table 4-1 below shows the relation between
FSC architectures, requirement classes, and availability.
Note:
For details on FSC architectures and voting refer to the FSC
Safety Manual.
Software Manual
Table 4-1 Relation between FSC architectures and requirement
classes AK1-6, according to DIN V 19250
INCREASED SAFETY
Maximum requirement class (AK)

FSC architectures AK4 (= SIL 2) AK5 (= SIL 3) AK6 (= SIL 3)
INCREASED AVAILABILITY
single Central Part +

= =* =*
single I/O
redundant Central Parts +

= = =
single I/O

= = =
redundant & single I/O

= = =
redundant I/O
* Only possible if a 10020/1/1 Quad Processor Module (QPM) is used.
If you change the requirement class and the current architecture

requires some modification in order to meet the demands of the new
requirement class, a warning will be displayed. This will typically
happen if the Central Part architecture is set to 'Single' and you change
the requirement class to AK5 or AK6. The following warning will
then be displayed:
Architecture only possible in FLASH mode with QPM
10020/1/1. Continue? (Y/N)
If you press <N>, the new requirement class is ignored.
If you press <Y>, the new requirement class is activated. The installed
CPU module will automatically be set to 10020/1/1, and the memory
type will be set to 'FLASH'.
Software Manual
4.5.3 Central Part Architecture
Central Part The 'Central part architecture' field in the configuration screen as
architecture shown in Figure 4-8 on page 4-12 allows you to specify the number
of Central Parts in the system. You can choose between 'Single' (i.e.
one Central Part) or 'Redundant' (i.e. two Central Parts).
As long as no Central Part architecture has been defined, the field will
contain the word 'Undef'. Use <Space> to toggle between the available
system architectures, or press <?> to choose from a list.
Table 4-2 Central Part architectures

Requirement Class (AK)
Architecture AK1 AK2 AK3 AK4 AK5 AK6
Single = = = = =* =*
Redundant = = = = = =
* Only possible if a 10020/1/1 Quad Processor Module (QPM) is used.
If you change the FSC system architecture of an existing application,

all module placement is cleared and all variable allocations are
deallocated. You will be asked to confirm the operation:
Changing will clear the module placement and the I/O
allocation. Change FSC system type? (Y/N)
Once the system configuration has been defined, the remaining

parameters in the configuration screen can be set.
Software Manual
4.5.4 SER Channel Specification
SER channel The 'SER channel specification' option in the configuration screen as
specification shown in Figure 4-8 on page 4-12 allows you to specify the
characteristics of the communication channel that is used for
sequence-of-event recording (SER). This option is only available if a
communication (COM) module has already been defined in the
current system. Press <E> to edit the specification. The window as
shown in Figure 4-9 will appear.
Notes:
1. For details on sequence-of-event recording (SER) refer to
Appendix B of this manual ("Sequence-of-Event Recording")
2. If the SER channel configuration is modified, any SER data
which remains behind in the modified system is lost.
Figure 4-9 SER channel specification
Software Manual
The selected channel may be configured to use any of the following
communication protocols:
• Development System protocol (for use with FSCSOE),
• Modbus protocol (numerical SER only),
• PlantScape protocol (numerical SER only), or
• Printer protocol (for direct connection to a printer).
It is possible to concentrate event collection at a single communication

port. For optimum availability of the SER function, two SER channels
may be used (primary and secondary).
SER channel An SER channel is configured by toggling the Primary SER

channel or Secondary SER channel field to 'Yes' (using <Space>).
Only then can the other fields for that SER channel be accessed.
The primary SER channel allocation will be removed in any of the
following cases:
• The SER channel field is toggled to 'No'.
• The system number is changed.
• The Central Part number is changed (communication module and
channel will then become zero).
If the primary SER channel is edited and the restrictions mentioned

are violated, the secondary SER channel allocation will be removed.
System number As long as no system number has been specified (i.e. the field
contains the value '0'), the SER channel cannot be allocated. Valid
system numbers are 1 to 63. You can enter the number of the current
FSC system, but also any other system in an FSC network.
If the system number you enter is identical to the system's own
number, the SER channel is located in the current system. In that case
you can select all variable communication channels that either have an
undefined communication protocol, the Development System
protocol, or the Printer protocol.
Dual SER channels For optimum availability of the SER function, two SER channels may
be used (dual SER channels). This allows two independent SER PCs
(or printers) to be connected, each of them receiving all SER data.
Should one PC (or printer) fail, the other will still be able to receive
and process the events generated by the system. The secondary SER
channel can only be configured if a valid primary SER channel has
already been defined.
Software Manual
There are some restrictions that must be taken into account when
configuring a secondary channel:
1. If the primary SER channel has been configured in the current
system, it must be configured at a 'lower' channel than the
secondary SER channel. For example, if the primary SER channel
is at Central Part 1 / COM module 2 / channel B, the secondary
SER channel cannot be configured at Central Part 1 / COM
module 1 / channel B, but it can be configured at Central Part 1 /
COM module 3 / channel A or Central Part 2 / COM module 2 /
channel B.
2. If you configure redundant SER (with connected Central Parts),
the two SER channels per Central Parts must be allocated to two
different COM modules. If you do not, any failure of one SER
link will block the other link for a period of more than four hours
after a complete buffer of events has been generated.
3. The secondary channel can only be configured in the current
system. Therefore, the system number of the secondary SER
channel cannot be modified (it is always the current system
number).
If the allocation of the primary SER channel is changed and any of the
restrictions above are violated, the secondary SER channel will be
deallocated.
Numerical Numerical SER allows event recording with minimal overhead. It is

SER ranges used for event recording to FSCSOE (the event historian of the FSC
product portfolio), PlantScape, or a Modbus device (e.g. a DCS). If
numerical SER is used, a unique sequence number is assigned to all
FSC variables that are SER-enabled. If an event then occurs for an
SER-enabled variable, its sequence number is contained in the event
report. The receiving end (typically FSCSOE or PlantScape) is then
able to relate the sequence numbers to the original process variable.
The SER base and SER maximum define the SER range, which is
the maximum number of FSC variables that are available for
sequence-of-event recording (they are "SER-enabled"). The sequence
numbers of the SER-enabled FSC variables will all be in the range
specified. The SER base must be between 1 and 65518, and the SER
maximum between 17 and 65534. (Also, the SER maximum must be
higher than the SER base.)
Please note that FSC will always reserve space for 16 system markers,
which means you should make the range at least 16 larger than the
number of variables you wish to SER-enable. In the example shown in
Figure 4-9 on page 4-16, the first available sequence number is 200
Software Manual
and the last 1216. This means that a total of 1017 sequence numbers
are available, but since 16 of them are reserved for system markers, a
maximum of 1001 FSC variables can be SER-enabled. (If you attempt
to SER-enable more, an error message will be displayed saying you
should increase the SER range.)
Please note the following considerations:

1. As soon as you specify a non-zero value for the SER base or SER
maximum, numerical SER is assumed.
2. If SER is used in conjunction with the Printer protocol or the
Development System protocol (i.e. FSCSOE), the SER ranges for
different FSC systems in an FSC network do not need to be
identical. They may be totally different or they may overlap.
3. If SER is used in conjunction with the Modbus protocol or
PlantScape protocol, the SER ranges for different FSC systems in
an FSC network must be identical.
4. The ranges for the primary SER channel and secondary SER
channel must either be identical or totally different (i.e. there may
be no overlap). The 'System Configuration' option of FSC
Navigator does not check for overlapping numerical SER ranges,
but the application compiler does. If the compiler detects an
overlap, you will get an error message.
5. If you enter an SER maximum that is smaller than the SER base,
the SER base will automatically be set to the SER maximum value
minus 16. Thus, if the SER base is 500 and you set the SER
maximum to 450, then the SER base will automatically be set to
434 (450-16).
6. It is possible to specify the SER base and SER maximum without
setting the associated primary or secondary SER channel field to
'Yes'. This allows you to provide FSC variables with sequence
numbers, and actually activate the SER channel later.
Software Manual
4.5.5 Modbus Base Address Configuration
Modbus base The 'Modbus base address configuration' option in the configuration
address screen as shown in Figure 4-8 on page 4-12 allows you to specify the
configuration Modbus base addresses which are used for dBASE imports/exports
and for printing the system configuration and FLDs. Press <E> to
open a window in which you can edit the Modbus base addresses (see
Figure 4-10).
Figure 4-10 Modbus base address configuration
Software Manual
4.5.6 Memory Chip Size Configuration
Memory chip size The 'Memory chip size configuration' option in the configuration
configuration screen as shown in Figure 4-8 on page 4-12 allows you to specify the
type of COM and CPU memory chips used in the FSC system (RAM,
EPROM). The compiler will generate files of the correct size in
accordance with the selected memory chip size.
Press <E> to edit the memory chip size. The window as shown in
Figure 4-11 will appear. Use <Space> to toggle between the available
chip sizes.
Figure 4-11 Memory chip size configuration
COM chip size For communication chips, you can choose 512 KBit, 1 MBit, 2 MBit,
or Variable. If you choose Variable (which is also the default), the
required memory chip size depends on the compiler output. The
smallest possible memory chip size will then be selected.
For FLASH mode, this field will always be set to 'Variable'.
Software Manual
CPU chip size The selection of the CPU memory chip size depends on the
configuration. You can only select the CPU chip size if the
application is on the CPU.
If the memory type is EPROM (see page 4-29), you can select
512 Kbit, 1 Mbit, 2 Mbit, 4 Mbit, and Variable. In RAM mode or
simulation mode you can select 512 Kbit, 1 Mbit, and 4 Mbit.
For FLASH mode, this field will always be set to 'Variable'.
Notes:
1. If you have made a selection for the chip size which turns
out to be incompatible with the memory type, the chip size
will automatically be reset to 'Variable'.
2. If the chip size you selected turns out to be too small for the
application, the compiler will issue a warning. While
programming EPROMs, you will then only be able to select
chip sizes that are big enough to hold the application.
4.5.7 Process Safety Time
Process safety time The 'Process safety time' field in the configuration screen as shown in
Figure 4-8 on page 4-12 allows you to specify the time that a fault
may be present in the safety system without possible danger for an
installation or the environment. In the FSC system it specifies the
period in which a complete self-test is executed. The process safety
time has a range of 1 to 20 seconds (in steps of one second). The
default value is 3 seconds.
Software Manual
4.5.8 Interval Time Between Faults ("Second Fault Timer")
Interval time The 'Interval time between faults' field in the configuration screen as
between faults shown in Figure 4-8 on page 4-12 allows you to specify the interval
time between faults.
During operation, each Central Part of the FSC system performs
constant self-tests on itself and all allocated I/O modules. If a fault is
detected during self-testing, the Central Part will report the failure and
take action to guarantee a safe operational result. If possible, the
failure will be isolated and Central Part operation continues. If failure
isolation cannot be guaranteed, the Central Part shuts down. Isolation
of failures is possible for the majority of failures, but safe operation
can only be guaranteed as long as no additional faults occur which, in
correlation with the first failure, may lead to unsafe operation.
Therefore, when continuing operation, a certain risk is present that
such an additional, correlating fault occurs. The longer the Central
Part operates, the larger the risk becomes.
In order to keep the risk within acceptable limits, a time interval (in
minutes) must be defined which reflects the maximum period of time
the Central Part is allowed to operate after the first failure has
occurred (the "interval time between faults"). When this interval time
between faults expires, the Central Part will shut down.
The interval time between faults can be defined between 0 minutes
(direct Central Part shutdown) and 22 days, or it can be completely
deactivated. To deactivate the interval time between faults altogether,
press <D>. The field value will then be set to 'Not used'.
The probability of failure occurring depends on the quantity of

components used and their quality. Fully in line with the applicable
standards (especially IEC 61508 in respect of SIL levels), the
probability of failure occurrence is to be assumed or calculated.
The following considerations can be made for this time management
concept:
• TÜV recommends a pragmatic approach, in line with support/repair
capabilities of the maintenance organization, which sets the second
fault timer to 72 hours, sufficient to bridge a two-day weekend. This
is the default setting of any configured FSC system.
• Based on a "proven-in-use" approach, during the lifetime of the
FSC product, and based on numerous quantitative analyses made, a
setting of 1,500 hours can be justified.
• For truly accurate time settings, a full performance analysis must be
done for the actual installed hardware configuration. This report can
be provided on request.
Software Manual
Table 4-3 and Table 4-4 below outline the behavior of the second fault
timer.
Note:
For more information on FSC system response to failures refer
to the FSC Safety Manual.
Behavior of The behavior of the second fault timer depends on the error type and
second fault timer requirement class (AK), as shown in Table 4-3 and Table 4-4 below.
Table 4-3 Conditions for starting the second fault timer

The second fault timer (SFT) will start after… AK1-4 AK5 AK6
Any fail-safe error on safety-related output modules. = = =
Internal communication failure (e.g. if only one Central Part 1) 1)
– = =
of a redundant system is running).
Any fault detected on hardware specific to a Central Part
(e.g. Central Part hardware and I/O hardware).
2) – – =
Any fault detected on hardware "shared" by Central Parts

(e.g. single I/O in a redundant system)
3) – – =
1) If the Central Parts contain 10020/1/1 Quad Processor Modules (QPMs), the second fault
timer will not be started.
2) The second fault timer will start for the affected Central Part. It will be reset upon a fault
reset, providing no Central Part failure has occurred.
3) The second fault timer will start for both Central Parts. It will be reset upon a fault reset,
providing no Central Part failure has occurred.
Table 4-4 Behavior of second fault timer

Fault SFT for CP 1 SFT for CP 2 SFT for CP 1 SFT for CP 2
before reset before reset after reset after reset
1)
CP 1 shutdown; will Starts or Reset and Reset and
Nothing happens 2)
start on fault reset Nothing happens stopped stopped
1)
CP 2 shutdown; will Starts or Reset and Reset and
2) Nothing happens
start on fault reset Nothing happens stopped stopped
1)
CP 1 shutdown; will Starts or Continues
Nothing happens 2) Nothing happens
not start on fault reset Nothing happens to run (if running)
1)
CP 2 shutdown; will Starts or Continues
2) Nothing happens Nothing happens
not start on fault reset Nothing happens to run (if running)
Fail-safe output fault Reset and
Starts Nothing happens 3) Nothing happens
in CP 1 stopped
Fail-safe output fault Reset and
Nothing happens Starts Nothing happens 3)
in CP 2 stopped
Fail-safe output fault Reset and Reset and
Starts Starts 3) 3)
in single I/O section stopped stopped
1) If 10002/1/2 or 10012/1/2 CPU is used. SFT = Second fault timer
2) If 10020/1/1 Quad Processor Module (QPM) is used.
3) Only if the fault has disappeared. If it is still present, it will be reported, and the SFT will be
reset and restarted.
Software Manual
4.5.9 FSC-FSC Communication Architecture
FSC-FSC The 'FSC-FSC communication architecture' option in the

communication configuration screen as shown in Figure 4-8 on page 4-12 allows you
architecture to specify the FSC-FSC communication timeout and the application
names for each connected system.
Press <E> to edit the FSC-FSC communication architecture. The
screen as shown in Figure 4-12 will appear.
Figure 4-12 Setting the FSC-FSC communication timeout
The communication timeout is the total timeout for scanning all

connected FSC systems. In other words, the FSC master expects all
FSC slaves in a network to respond to a command within the given
time frame. The timeout can be set to a value between 1.2 and 30
seconds (in steps of 0.01 second). The default value is 1.2 seconds. If
you enter three decimal digits, they will be round up or down to the
nearest hundredth second (i.e. 1.468 will become 1.47).
All FSC systems in an FSC network must have the same
communication timeout. If they do not, communication errors may
occur and the compiler will report differences.
Software Manual
The system numbers for FSC-FSC communication must be unique.
The correct application name must be entered for each connected
system number. The configuration is used by the application compiler
to verify the correctness of the FSC communication network.
4.5.10 Simulation Mode
Simulation mode The 'Simulation mode' option in the configuration screen as shown in
Figure 4-8 on page 4-12 allows you to specify that you want your
application to run in simulation mode, which allows it to be tested in
a non-operational environment. You can also specify which
simulation hardware should be used as well as the communication
channel assignment.
Press <E> to edit the simulation mode configuration. The window as
shown in Figure 4-13 will appear.
Figure 4-13 Simulation mode
Software Manual
Note:
For details on simulation mode, including a detailed description
of the simulation hardware, refer to Appendix H of this manual
("Simulation Mode").
Setting the The Simulation mode field in Figure 4-13 allows you to specify the
simulation mode simulation hardware unit that should be used in conjunction with
your simulated application. Use <Space> to toggle between the
available options or press <?> to select from a list. The default is
'None' (i.e. no simulation). Table 4-5 below provides an overview of
the available simulation hardware units, with their main
characteristics.
Table 4-5 Simulation hardware units

Simulation Memory type CP module Architecture FSC-SMM PlantScape Software
units type* versions
23260/4/1 FLASH QPM+ECM Single-rack – – ≥ R530
23260/4/2 FLASH QPM+ECM Single-rack = – ≥ R530
23260/4/3 FLASH QPM+ECM Single-rack – = ≥ R530
23250/4/1 FLASH QPM+ECM Single – – ≥ R530
23250/4/2 FLASH QPM+ECM Single = – ≥ R530
23250/4/3 FLASH QPM+ECM Single – = ≥ R530
23270/4/1 FLASH QPM+ECM Redundant – – ≥ R530
23270/4/2 FLASH QPM+ECM Redundant = – ≥ R530
23270/4/3 FLASH QPM+ECM Redundant – = ≥ R530
23260/3/1 FLASH CPU+COM Single-rack – – ≥ R510
23260/3/2 FLASH CPU+COM Single-rack = – ≥ R510
23260/3/3 FLASH CPU+COM Single-rack – = ≥ R520
23250/3/1 FLASH CPU+COM Single – – ≥ R510
23250/3/2 FLASH CPU+COM Single = – ≥ R510
23250/3/3 FLASH CPU+COM Single – = ≥ R520
23270/3/1 FLASH CPU+COM Redundant – – ≥ R510
23270/3/2 FLASH CPU+COM Redundant = – ≥ R510
23270/3/3 FLASH CPU+COM Redundant – = ≥ R520
23260/1/1 RAM CPU+COM Single-rack – – ≥ R3.00
23260/2/1 RAM CPU+COM Single-rack = – ≥ R510
23250/1/1 RAM CPU+COM Single – – ≥ R3.00
23250/2/1 RAM CPU+COM Single = – ≥ R510
23251/1/1 RAM CPU+COM Redundant – – ≥ R3.00
23270/2/1 RAM CPU+COM Redundant = – ≥ R510
* QPM = 10020/1/1 Quad Processor Module,
ECM = 10024/x/x Enhanced Communication Module
Software Manual
Note:
Make sure the simulation mode is compatible with the selected
memory type (see page 4-29).
Channel The bottom section of the screen as shown in Figure 4-13 allows you
assignment to define the communication channel assignment that will be used in
simulation mode. You can specify which communication channels of
your application are mapped to the simulated channels.
The left columns show all available communication channels in the
selected simulation hardware unit. The channel configuration shown
depends on the selected simulation/training unit. The right columns
show which communication channels of your application have been
assigned to the simulated channels. For ease of verification, the
communication protocols are shown as well.
Mapping channels You can specify which of the actual communication channels in your
application should appear in the simulation unit. This allows you to
use the application itself to test whether the communication for any
particular channel is working correctly.
You map a communication channel to a simulated channel by
specifying its location in the FSC system (CP number, module
position, channel, e.g. 1,1B). Use <Space> to toggle between the
available channels or press <?> to select from a list. You can only
select channels in your application whose interface hardware is
identical to that of the simulation hardware. This means that if the
simulation hardware contains a particular interface, you can only
select all communication channels of your application that contain the
same interface.
For each user-configurable channel, you can also choose 'None'. This
means that no mapping is done. This option is useful if you do not
want to test the communication, but the behavior of the application as
defined in the FLDs. It will cause the simulated system to use the
Development System protocol, providing this is allowed on the
available hardware interface. (For the UCN interfaces, for example,
the Development System protocol is not supported, and therefore it
cannot be selected.)
For all redundant simulation modes, the internal FSC-FSC

communication channel (channel 1A) is not user-configurable. This
means that the Channel field will always be set to 'None' and cannot
be modified.
Software Manual
4.5.11 Memory Type
Memory type The 'Memory type' field in the configuration screen as shown in
Figure 4-8 on page 4-12 allows you to specify the memory type that
is used in the FSC system. There are three options to choose from:
• EPROM,
• RAM, and
• FLASH.
Press <Space> to toggle, or press <?> to choose from a list.
The memory type determines how the FSC-related software is
transferred to the FSC system as shown in the table below:
Table 4-6 Memory types

EPROM RAM FLASH
COM software EPROMs EPROMs download**
CPU software (system) EPROMs EPROMs download**
CPU software (application) EPROMs download* download**
* To on-board RAM or additional 1-Mb or 4-Mb memory boards.
** To flash memory (requires suitable hardware modules).
Notes:
1. Communication software larger than 2 Mb cannot be loaded
into EPROMs. This must be loaded to flash memory.
4.5.12 Power-On Mode
Power-on mode The 'Power-on mode' field in the configuration screen as shown in
Figure 4-8 on page 4-12 allows you to set the power-on mode, which
defines the conditions for the start-up of the FSC system. There are
two options:
• Cold start
A cold-start power-on means that the system starts up with the
values of the variables being reset to their power-on values as laid
down in the variable database.
• Warm start
A warm-start power-on means that the system starts up with the
values of the variables set to their last process values.
Software Manual
Use <Space> to toggle between the power-on modes.
Notes:
1. If the system starts up for the first time, a cold start is
performed.
2. If the system is started up after a shutdown that was caused
by a fault, there will always be a cold start, regardless of the
setting in this configuration screen.
Important!
Using the warm start option in combination with on-line
modification of the application program may result in spurious
diagnostic messages and Central Part shutdown.
4.5.13 On-Line Modification Wanted
On-line modification The 'On-line modification wanted' field in the configuration screen as
wanted shown in Figure 4-8 on page 4-12 allows you to specify that the
application can be modified on-line. The TÜV-approved on-line
modification (OLM) option allows you to exchange software in an
operational FSC system without shutting down the process.
If you have chosen a redundant system architecture, you may activate
the on-line modification option. Use <Space> to toggle to 'Yes', and
press <Enter> to record the status. Please note that you can only
perform on-line modifications if this field is set to 'Yes'.
Note:
For details on on-line modification, including a detailed
step-by-step procedure, refer to Appendix D of this manual
("On-Line Modification").
Software Manual
4.6 Defining the Physical Cabinet Layout
Physical The bottom lines of the configuration screen as shown in Figure 4-8
cabinet layout on page 4-12 contain a number of parameters that allow you to define
the physical characteristics of the FSC cabinet(s).
Number of cabinets An FSC system may be accommodated in multiple cabinets. Here

you can specify the number of cabinets that the FSC system consists
of. The default number of cabinets is 1, and the maximum 11.
For single-rack architectures the number of cabinets is fixed at 1.
Number of racks per The modules of an FSC system can be accommodated in several
cabinet racks. Here you can specify the number of racks that each of the FSC
cabinets consists of. The default number of racks per cabinet is 9, and
the maximum 10. The maximum number of racks for an entire FSC
application is 99 (divided over a number of cabinets).
You can edit the number of racks at any time. If you want to lower the
number, FSC Navigator will check that no racks have been defined in
the part that is to be deleted. A warning will then be displayed.
Rack positions After entering the number of cabinets and the number of racks per
cabinet, you should define the position of the racks in the cabinets.
This is done by assigning a unique number to every rack position that
is to be used. FSC Navigator will use these numbers to check the
validity of rack numbers that you enter at other places in the program.
Press <E> to edit the rack positions. The window as shown in Figure
4-14 on the next page will appear. Here you can enter unique rack
numbers for all racks used in the FSC cabinet(s). Racks can be given
any number between 1 and 99. If you enter 0 (zero), the rack number
will be removed, providing no modules have already been installed in
that rack.
Renumbering racks If you attempt to delete a rack number (by entering the value 0) and
the rack is not empty, the following message will be displayed:
Rack in use. Cannot be removed.
If you give an existing rack a new number which has already been
assigned to another rack, the following message is displayed:
Rack with same number already placed.
Software Manual
If you give an existing, non-empty rack or a Central Part rack a new
number which has not yet been assigned to another rack, the following
message is displayed:
Rack in use. Renumber? (Y/N)
If you press <Y>, the rack is renumbered and its new number written
to the FSC database. This means that the placement information of all
modules placed in that rack is converted, including I/O variable
allocations to these modules. Please note that if the existing rack is
empty, the new number will be assigned without any user
intervention.
If you give a new rack a number which has already been assigned to
another rack, the following message is displayed:
Replace rack? (Y/N)
If you press <Y>, the existing rack will be deleted, and new rack will
get its number.
Figure 4-14 Defining rack positions
Software Manual
Central Part After defining the racks in the cabinets, you should define the Central
rack number Part rack number(s). If there is more than one Central Part, they must
be accommodated in the same cabinet on consecutive positions (e.g.
racks 2 and 3), or both in the same rack (e.g. rack 2).
Notes:
1. No modules can be placed as long as no Central Part rack
numbers have been defined. (The Install menu will then not
contain the 'Modules' option.)
2. If modules have been placed in the Central Part rack(s), their
rack numbers cannot be altered.
Software Manual
4.7 Installing Modules
4.7.1 Overview
Installing modules After you have defined the basic system architecture (see subsections
4.4 to 4.6), you can install modules in the system.
To install modules, choose the following menu options:
Install Modules
Please note that the Install menu will only contain a 'Modules' option
if all of the following conditions have been met:
• The requirement class (AK) has been specified (see subsection 4.5.2
on page 4-13).
• The Central Part architecture has been specified (single or
redundant, etc.) (see subsection 4.5.3 on page 4-15).
• The physical cabinet and rack definition has been specified
(see subsection 4.6 on page 4-31).
• A Central Part rack number has been specified (see page 4-33).
You can use the 'Modules' option to place modules in the racks, and to
configure the related hardware (e.g. safety relation), if necessary.
A distinction is made between modules that are placed in the Central
Part (PSU, PSD, CPU, WD, SBD, VBD, COM, and DBM), and
modules that are not placed in the Central Parts (PSU, PSD, HBD, and
I/O).
For the Central Part modules, you only need to define the desired
number of modules of every type. The modules are automatically
placed. For the other modules the rack and position need to be
defined.
All modules take up one rack position, except the PSU, COM and
DBM modules, which occupy two positions.
The PSU, CPU, WD, COM, SBD, VBD and DBM are always
safety-related. The same is true for HBD 1. The safety relation for the
other HBDs and the I/O modules are user-definable.
Note:
If you edit the Central Part definition (e.g. modify the number of
bus slots), the Central Part module positions may change even
though no changes were made to these modules.
Software Manual
Module types Table 4-7 to Table 4-12 below list the available module types.
(Refer to the FSC Hardware Manual for technical details.)
Central part (CP)

modules The following module types belong to the Central Part(s):
Table 4-7 Central Part modules

Module type Abbreviation Description
10001/1/1 VBD Vertical bus driver module
10001/R/1 VBD Vertical bus driver module with relay
10002/1/2 CPU Central processor unit
10004/./. COM Communication module
10005/1/1 WD Watchdog module
10006/1/1 DBM Diagnostic and battery module
10006/2/1 DBM Diagnostic and battery module (RTC)
10006/2/2 DBM Diagnostic and battery module (DCF)
10007/1/1 SBD Single bus driver module
10008/2/U FSC-SMM FSC-SMM communication module
10008/3/P P-BUS FSC to P-bus communication module
10012/1/2 CPU Central processor unit
10014/./. COM Communication module
10018/E/1 COM PlantScape communication module
10018/E/E COM PlantScape communication module
10018/2/U FSC-SMM FSC-SMM communication module
10020/1/1 QPM Quad Processor Module
10024/./. ECM Enhanced communication module
Special functions The following modules have a special function:
Table 4-8 Special modules

Module type Abbreviation Description
10100/1/1 HBD Horizontal bus driver module
10100/2/1 HBD Horizontal bus driver module
10300/1/1 PSU 24 Vdc to 5 Vdc/12 A converter
10302/1/1 WDR Watchdog repeater module
10302/2/1 WDR Watchdog repeater module
10303/1/1 PSD Power supply distribution module
10305/1/1 AIC 0-20 mA to 0-5 V analog input converter
(16 channels)
Software Manual
Input modules Table 4-9 and Table 4-10 below list the input modules that are
available. The default voting schemes for input modules that support
different voting schemes are as follows:
• New projects: 1oo2D.
• Existing projects with requirement class AK1-4, after conversion
from an FSC release that does not have voting (< R500) to FSC
R530: 2oo2D.
R530: 1oo2D.
Table 4-9 FSC input modules (plug-and-play)

Module Fail- Single Redundant
type Description Tested safe architectures architectures EFM
Suited? Voting Suited? Voting
2oo2D
10101/2/1 Fail-safe digital input module (24 Vdc, 16 ch.) Yes Yes Yes 1oo1D Yes n/a
1oo2D
2oo2D
1oo2D
2oo2D
1oo2D
2oo2D
10102/2/1 Fail-safe analog input module (4 channels) Yes Yes Yes 1oo1D Yes n/a
1oo2D
10104/2/1 Digital input module (24 Vdc, 16 channels) No No Yes 1oo1 Yes 2oo2 n/a
Fail-safe high-density analog input module 2oo2D
10105/2/1 Yes Yes Yes 1oo1D Yes n/a
(24 Vdc, 16 channels) 1oo2D
Fail-safe line-monitored digital input module 2oo2D on
10106/2/1 Yes Yes Yes 1oo1D Yes
with earth fault monitor 1oo2D off
EFM = earth fault monitoring
Table 4-10 FSC input modules (non plug-and-play)

Module Fail- Single Redundant
type Description Tested safe architectures architectures EFM
2oo2D
1oo2D
2oo2D
1oo2D
2oo2D
1oo2D
–
10102/1/1 Fail-safe analog input module (4 ch.) Yes Yes Yes 1oo1D No n/a
–
2oo2D
10102/1/2 Fail-safe analog input module (4 ch.) Yes Yes Yes 1oo1D Yes n/a
1oo2D
10103/1/1 Intrinsically safe input module (4 ch.) No No Yes 1oo1 No – n/a
10103/1/2 Intrinsically safe input module (4 ch.) No No Yes 1oo1 No – n/a
10104/1/1 Digital input module (24 Vdc, 16 ch.) No No Yes 1oo1 Yes 2oo2 n/a
Software Manual
Output modules Table 4-11 and Table 4-12 below list the output modules that are
available. The default voting schemes for output modules that support
different voting schemes are as follows:
• New projects: 1oo2D.
R530: 2oo2D.
R530: 2oo2D (except 10216/./. modules, which are set to 1oo2D).
Table 4-11 FSC output modules (plug-and-play)

Module Tested Fail- Single Redundant
type Description safe architecture architecture EFM
Fail-safe digital output module 2oo2D
(24 Vdc, 0.55 A, 8 channels) 1oo2D
10205/2/1 Fail-safe analog output module (0(4)-20 mA, 2 ch.) Yes/No Yes Yes 1oo1D No – n/a
10206/2/1 Digital output module (24 Vdc, 0.55 A, 12 ch.) No No Yes 1oo1 Yes 2oo2 n/a
10208/2/1 Relay output module (contacts, 10 ch.) No No Yes 1oo1 Yes 2oo2 n/a
2oo2D
10213/2/1 Fail-safe digital outp. mod. (110 Vdc, 0.32 A, 4 ch.) Yes Yes Yes 1oo1D Yes n/a
1oo2D
2oo2D
10213/2/2 Fail-safe digital output mod. (60 Vdc, 0.67 A, 4 ch.) Yes Yes Yes 1oo1D Yes n/a
1oo2D
2oo2D
1oo2D
2oo2D
10215/2/1 Fail-safe digital output module (24 Vdc, 2 A, 4 ch.) Yes Yes Yes 1oo1D Yes n/a
1oo2D
Fail-safe loop-monitored digital output module 2oo2D
(24 Vdc, 1 A, 4 ch.) 1oo2D
(48 Vdc, 0.5 A, 4 ch.) 1oo2D
Software Manual
Table 4-12 FSC output modules (non plug-and-play)
Module Tested Fail- Single Redundant
type Description safe architecture architecture EFM
Fail-safe digital output module 2oo2D
(24 Vdc, 0.55 A, 8 ch.) 1oo2D
Fail-safe digital output module with double –
10203/1/2 Yes Yes Yes 1oo1D No n/a
switch-off (24 Vdc, 0.9 A, 4 ch.) –
10205/1/1 Fail-safe analog output module (0(4)-20 mA, 2 ch.) Yes Yes Yes 1oo1D No – n/a
10207/1/1 Intrinsically safe optocoupler output module (8 ch.) No No Yes 1oo1 No – n/a
10208/1/1 Relay output module (contacts, 12 ch.) No No Yes 1oo1 Yes 2oo2 n/a
10212/1/1 Digital output module (24 Vdc, 0.9 A, 8 channels) Yes Yes/ Yes 1oo1D Yes 2oo2D n/a
No 1oo2D
2oo2D
1oo2D
2oo2D
1oo2D
2oo2D
1oo2D
2oo2D
1oo2D
2oo2D
10215/1/1 Fail-safe digital output module (24 Vdc, 2 A, 4 ch.) Yes Yes Yes 1oo1D Yes n/a
1oo2D
(24 Vdc, 1 A, 4 ch.) 1oo2D
Software Manual
4.7.2 Installing a Power Supply Unit (PSU)
PSU To install a power supply unit (PSU), choose the following menu
options:
Install Modules PSU
There are basically two types of power supply units in an FSC system:
• 5 Vdc power supply unit (10300/1/1), and
• Delta/external power supply units.
Each of these is discussed in more detail below.
5 Vdc If you choose the Install\Modules\PSU option, the configuration

power supply screen for the 5 Vdc power supply unit (10300/1/1) will open:
Figure 4-15 Installation: PSU modules (10300/1/1)
Software Manual
Here you can install and configure the 5 Vdc power supply units
(10300/1/1) in your application. A 10300/1/1 module uses two rack
positions. You can do any of the following:
• Add and delete 5 Vdc power supply units,
• Assign a rack position to 5 Vdc power supply units,
• Configure a 5 Vdc power supply distribution (PSD) module
(providing there is a VBD that controls single I/O in a redundant
FSC system), and
• Reserve the space of a PSD module.
Note:
Press <PgDn> to move to the configuration screen for
Delta/external power supplies.
The first PSU is the Central Part PSU, which is configured

automatically. The rack number and position of this PSU cannot be
modified, nor can it be deleted.
The 5 Vdc power supply distribution (PSD) module is not placed and
no space is reserved for it unless the system is redundant and contains
a VBD that controls single I/O. If the configuration allows it, you can
reserve PSD space of a PSU to accommodate for future expansion.
You should then use <Space> to toggle the PSD space field to 'Yes'.
By default, no PSD space is reserved. The PSD will be configured
automatically if the FSC architecture is a redundant system with single
I/O and the current PSU is the last one. You cannot delete this PSD.
PSUs must be configured in ascending order. For example, it is not

possible to configure PSU 10 if PSU 6 has not been configured yet.
The PSUs can only be deleted in descending order. This means that
you can only delete the PSU module that was added last (i.e. has the
highest number). A PSU can be deleted by setting the PSU type to
'Undefined' or by deallocating the PSU. The Central Part PSU cannot
be removed.
Error messages The following error messages may appear during the definition and
configuration of 5 Vdc PSU modules:
Cannot allocate the PSD to the last PSU.

If, in a redundant architecture, you tried to delete the last PSU, a
PSD must be allocated for the PSU that becomes the last module.
Software Manual
More than one central part in central part rack. Not allowed to
place PSU.
If two Central Parts are configured in one rack, extra PSUs cannot
be configured in the Central Part rack:
Not allowed to define PSUs in other central part than the first.
You can configure PSUs in the Central Part racks. However, only
Central Part 1 can be selected. You tried to place a PSU in Central
Part 2.
Only last module can be deleted. Restore? (Y/N)

You tried to remove a PSU that is not the last PSU.
Position in use for central part.

You tried to assign the PSU to a position in the Central Part, which
is not allowed.
Position allocated to <Module>

You tried to allocate the PSU to a position that has already been
allocated to the specified module.
Position for possible PSD already allocated to <Module>

You tried to reserve space for the PSD module on a position that
has already been allocated to the specified module.
Position for PSD allocated to <Module>

You tried to allocate the PSD module to a position that has already
been allocated to the specified module.
Position for PSD has already been allocated to <Module>

The position for the PSD module could not be allocated because it
has already been allocated to the specified module.
Position for PSD out of range.

The position number for the PSD module is invalid.
Position out of range.

You entered an invalid position number.
Rack does not exist.

You tried to select an undefined rack.
SBD placed, only one PSU allowed in the central part rack.
You tried to select the Central Part rack of a configuration that uses
an SBD.
Software Manual
Delta To call up the configuration screen for Delta/external power supplies,
power supplies press <PgDn> or <PgUp> in the configuration screen for the 5 Vdc
PSU (see Figure 4-15). This will open the following screen:
Figure 4-16 Installation: power supply units (Delta/external)
Here you can install and configure the Delta/external power supply
units in your application. A maximum of 99 Delta power supply units
can be configured. The screen will always show 11 Delta PSU
positions. You can use the <PgUp> and <PgDn> keys to browse
through the list of Delta PSUs.
Note:
Press <PgDn> or <PgUp> (repeatedly) to move to the
configuration screen for 5 Vdc power supplies.
You can do the following:

• Add and delete Delta power supply units,
• Assign rack positions to Delta power supply units,
• Alter the type of Delta power supply units.
Software Manual
Table 4-13 below lists the Delta power supply units that are supported.
Table 4-13 Supported Delta power supply units

Delta PSU model Supply voltage Space requirement
24-20HE 24 Vdc full rack
24-12HE 24 Vdc half rack
48-10HE 48 Vdc full rack
Note:
No power supplies are available in the 110 and 220 Vdc voltage
classes.
You can change the power supply type by toggling between available
options using <Space>. Alternatively, you can press <?> to choose
from a list. It may be that the type cannot be changed. This could, for
example, occur if the type changes from 24-12HE to 24-20 HE and it
is not possible to allocate the entire rack to the 24-20HE. In that case
the following message will be displayed:
Changing the type will deallocate the Delta unit.
Change? (Y/N)
If you press <Y>, the new Delta power supply will be added to the
list, but its position will be undefined (rack = 0, position = Undef).
If you press <N>, the change is discarded.
The position of Delta power supplies can only be changed for units
that use only half a rack. You can use <Space> to toggle the Position
field to 'Left' or 'Right' (i.e. the left or right half of the rack). The
default value is 'Left'. If any of the halves has already been allocated
to another Delta unit, the position cannot be changed. It will then
automatically be set to the empty half.
Delta power supply units may be placed in any defined and unused
rack, also between a Central Part and I/O racks, or between I/O racks.
Software Manual
External power An external power supply can be selected for each voltage class
supply (except 5 Vdc). To activate external power supply, move the cursor to
the appropriate field and use <Space> to toggle its value to 'Yes'. If
you select the external power supply for a specific voltage class and
Deltas have already been configured for this voltage class, the
following message is displayed:
Delete Delta power supplies of this voltage class? (Y/N)
If you press <Y>, the Delta power supply is deleted.
If you press <N>, the change is discarded.
Error messages The following error messages may appear during the definition and
configuration of Delta/external PSU modules:
<Delta type> can only be configured in racks that are empty or

contain PSUs.
You tried to assign the specified Delta type to a rack that is already
used by modules other than Delta and 5 Vdc PSU modules.
Rack already in use by other power supply unit(s).

You tried to assign a Delta power supply to a rack that has already
been allocated to one or more other power supplies.
Rack number does not exist.

You tried to assign a Delta power supply to a rack that has not been
configured.
4.7.3 Central Part (CP) Definition
CP definition To define a Central Part (CP), choose the following menu options:
Install Modules Central parts Definition
This will open the Central Part definition screen, which enables you to
view and modify the definition of the Central Part(s) in your system
(see Figure 4-17).
Software Manual
Figure 4-17 Central Part definition
The following configuration parameters can be modified.

• The size of the Central Part bus (i.e. the number of slots)
• The type of central processing unit (CPU)
• The type of the COM module(s)
• The number of the Central Part modules: CPU, WD, COM, VBD,
SBD, and DBM.
Each of these items is discussed in more detail below.
Note:
If you edit the Central Part definition (e.g. modify the number of
bus slots), the Central Part module positions may change even
though no changes were made to these modules.
Software Manual
Slots of central part The first item in this option is the size of the system bus. There are
bus(es) system buses that have 5, 7, 12, and 17 slots. If the FSC architecture
has two Central Parts in one rack, only a 5-slot or 7-slot bus can be
selected. Use <Space> to toggle between the available options or
press <?> to select from a list.
CPU module type This field shows the type of central processing unit (CPU) that is
used in the application. All CPUs in the application are of the same
type. The following CPU module types are supported:
− 10002/1/2 This CPU module allows the application program
to be loaded into on-board RAM or additional
memory boards. This module will be used if the
memory type (see page 4-29) has been set to
'EPROM' or 'RAM'.
− 10012/1/2 This CPU module allows the system software and
application program to be loaded into non-volatile
flash memory. This module can be used if the
memory type (see page 4-29) has been set to
'FLASH'.
− 10020/1/1 This Quad Processor Module (QPM) has two
processors and two memory sets. This module can
be used if the memory type (see page 4-29) has
been set to 'FLASH'.
COM module type(s) Here you can specify which communication (COM) modules are used
in the application (see Figure 4-18). The following COM module
types are supported:
− 10004/1/1 Communication module.
− 10008/2/U FSC-SMM communication module.
− 10008/3/P P-Bus communication module.
− 10014/1/1 Communication module (flash memory).
− 10018/1/1 PlantScape interface module (flash memory).
− 10018/2/U FSC-SMM communication module (flash memory).
− 10024/1/1 Enhanced communication module (ECM).
The options that are actually available depend on the memory type
that was specified (see page 4-29). If the memory type has been set to
'FLASH', the 10004/1/1 module will not be available. If the memory
type is 'EPROM' or 'RAM', the modules with only flash memory
(10014/1/1 and 10018/x/x) will not be available. By default, all
modules will be configured as 10024/1/1 (which supports both
EPROM and flash memory operation).
Software Manual
If desired, the communication module with the highest number may
be changed to 10008/2/U (FSC-SMM), 10018/2/U (FSC-SMM),
10008/3/P (P-Bus), or 10018/1/1 (PlantScape).
Figure 4-18 Selecting the communication module type
If a module has already been defined for a COM module position, you
can only change the module type for that position after you have
deallocated the existing module by setting its protocol to 'Undefined'
(see page 4-50).
Number of modules This option allows you to define how many COM, DBM and VBD
per central part modules you want to place in every Central Part.
Central Part 2 is always identical to Central Part 1, except for the
number of COM modules. Central Part 2 may have one less COM
module. If you leave the option by pressing <Esc> , the modules you
selected are placed in the Central Parts.
The positions of the Central Part modules within the rack are allocated
automatically and cannot be modified.
Software Manual
The default numbers for the various module types are as follows:
– CPU: 1 – DBM: 1
– WD: 1 – VBD: 1
– COM: 1 – SBD: 0
A single bus driver (SBD) can only be placed in configurations that

meet all of the following conditions:
1. The system bus used has either 5, 7 or 12 slots.
2. There is only one Central Part per rack.
3. There is only one PSU per Central Part.
If an SBD is placed, only one VBD is possible.
If modules cannot be placed because you selected more modules than

the number of slots of the system bus allows, you will be asked
whether you want to return to the situation that existed immediately
before you entered the option.
4.7.4 Installing a Central Processing Unit (CPU)
CPU modules To define a central processing unit (CPU), choose the following
menu options:
Install Modules Central parts CPU
This will open a screen that lists the position(s) of the CPU module(s)
in the Central Part rack(s). Their positions cannot be modified since
they are calculated automatically, based on the configuration. No
additional hardware configuration is required.
The CPU module type is specified in the Central Part definition screen
(see subsection 4.7.3).
Software Manual
4.7.5 Installing a Watchdog (WD)
WD modules To define a watchdog (WD), choose the following menu options:

Install Modules Central parts WD
This will open a screen that lists the position(s) of the WD module(s)
in the Central Part rack(s). Their positions cannot be modified since
they are calculated automatically, based on the configuration. No
additional hardware configuration is required.
The number of watchdogs is specified in the Central Part definition
screen (see subsection 4.7.3).
4.7.6 Installing a Communication Module (COM)
COM modules To define a communication module (COM), choose the following

menu options:
Install Modules Central parts COM
This will open a configuration screen that allows you to define the
module characteristics and communication parameters (see Figure
4-19). Please note that the number and type of communication
modules in the system are specified in the Central Part definition
screen (see subsection 4.7.3).
For every Central Part, you can configure channels A and B of each
communication module (COM). Use <Space> to toggle between
Central Parts and channels. In redundant architectures, channel A of
COM module 1 in Central Part 1 and 2 will always have protocol
FSC-FSC (used for internal communication).
The configuration screen has a number of fields that are used to define
the communication setup. Depending on the COM module type (see
page 4-46) and communication protocol that you select, some fields
may not be displayed or editable. The following fields may be
presented on screen:
– Protocol – Interface
– Redundant – Baud rate
– Network – Handshake
– Link status – Number of stop bits
– Connected systems – Number of bits per character
– Link specification – Parity
– Timeout
Software Manual
Figure 4-19 Defining the channel configuration
If more than one communication module has been defined, you can
use <PgUp> and <PgDn> to browse through them.
To deallocate ("remove") a communication module, set its protocol to
'Undefined'.
Each of the communication parameters is discussed in more detail
below.
Protocol Here you can select the communication protocol to be used. The
following protocols are supported:
– Undefined – Modbus H&B (optional)
– FSC-FSC – RKE3964R (optional)
– Development System – DS (Modem)
– Printer – UCN (TotalPlant Solution)
– Modbus RTU – PlantScape
Not all protocols may be available for all communication modules.
Use <Space> to toggle between the available protocols or press <?> to
select from a list.
Software Manual
Note:
For details on the communication protocols refer to Appendix F
of this manual ("Communication").
Redundant Here you can define a redundant link by changing the redundant field
to 'Yes'. The link definition will be copied to the second Central Part
automatically. You are only allowed to change the architecture of
Central Part 1.
A redundant link can also be configured for a single architecture with
redundant communication links. The configuration of channel A will
then be copied to channel B automatically. You are only allowed to
change the configuration of channel A.
Network Here you can select the network type that will be used. The following
network types are supported:
– Point to point
– Multidrop
For details on network types refer to Appendix F of this manual

("Communication").
Link status This parameter is only defined for the following communication
protocols:
– FSC-FSC – Modbus RTU
– Development System – Modbus H&B
– RKE3964R
FSC-FSC If the protocol is FSC-FSC, the link status can be defined as Master,
Slave, or Communication server. Multiple FSC systems may be
interconnected to form a safety network. In such configurations, one
FSC system – the master – controls the operation of one or more
other systems, the slaves. Communication servers are not end users of
exchanged data, but merely act as a routing device between master
and slave systems.
Development System, If the protocol is Development System, Modbus RTU or Modbus

Modbus RTU & H&B, the link status can be defined as Primary or Secondary.
Modbus H&B
Secondary communication links can serve as backup channels which
are used if the primary channel fails. For primary protocols a memory
area can be reserved that should be used for communication.
Software Manual
Secondary links use the same memory area as their primary link. All
you need to do for their link specification is refer to the primary
channel whose configuration they should use (see page 4-55).
RKE3964R If the protocol is RKE3964R, the link status can be defined as

Master primary, Master secondary, Slave primary, or Slave
secondary.
Secondary communication links can serve as backup channels which
are used if the primary channel fails. If a channel is configured as the
master, it can initiate data exchange itself. A slave will only exchange
data if it is requested by another system.
Connected systems This parameter is only defined for multidrop protocols and
point-to-point FSC-FSC protocols. All available system numbers are
shown in a popup window (see Figure 4-20).
Figure 4-20 Editing the connected systems

If a connection to a system already exists, the system is shown
highlighted (blue by default). Use the cursor keys to select a system.
Press <S> to establish a connection with a system, and <D> to remove
a connection. If the protocol is FSC-FSC, all systems can be selected
Software Manual
which communicate with the system via the communication channel.
If the network is point-to-point, only one connection can be made.
This is also the case if the system acts as a slave in a network — in
that case only the connection to the master system can be established.
If the system serves as the master in a network, multiple connections
to the slaves can be defined.
Link specification This parameter is only defined for the following communication
protocols:
– FSC-FSC – Modbus RTU – UCN
– Development System – Modbus H&B – PlantScape
– RKE3964R – Printer
Primary/Master link If the protocol is not Printer and the link status is Primary/Master (not
for PlantScape), the amount of memory (marker bytes and register
bytes) that is used for the communication with the connected FSC
system(s) or device needs to be defined. If you press <E> in the Link
Specification field, a popup window will appear which allows you to
define the amount of memory used. Figure 4-21 below shows the link
specification of a Modbus protocol.
Figure 4-21 Defining the link specification
Software Manual
FSC Navigator automatically allocates the required amount, and all
inputs and outputs that are to be used for the communication with a
particular system are allocated within the reserved area. (See also
subsection 4.10.3, which deals with the allocation of inputs and
outputs to COM modules.) The start addresses of the allocated marker
and register areas are displayed.
Printer If the protocol is Printer and the printer channel is the SER channel, a
number of output bytes can be defined (BO SER). If the SER event
for one of these BOs then occurs, the value of the BO will be printed.
Copying allocations In an FSC-FSC network architecture, the bytes reserved for

communication between two FSC systems must be consistent.
This means that the number of bytes for written to system X must be
the same as the number of bytes read by system X. The tag numbers
must also be the same. Table 4-14 below shows an example.
Table 4-14 Link specification

Application → TEST_1 TEST_2
Marker bytes To FSC1 from FSC2: 4 To FSC2 from FSC1: 0

From FSC1 to FSC2: 0 From FSC2 to FSC1: 4
Tag number I "test" (loc.='FSC') O "test" (loc.='FSC')

connected from system 2. connected to system 1.
Relative address 3. Relative address 3.
This is a correctly defined link for transferring digital information

from system 2 to system 1 via the variable "test".
To make it easier to correctly set up the FSC-FSC communication, a

'copy allocation' feature is available for the FSC-FSC protocol. This
feature allows you to copy the allocation from another connected
system into the current system. You can only do this if a link
specification has already been defined for the other system and
variables have already been allocated in that system. To copy the
allocations of another system, press <C> in the link specification
popup window for the FSC-FSC protocol. If more than one system is
available to copy from, you will be asked to choose which system's
allocations should be copied.
FSC Navigator will then first check whether the defined link in the
databases of both systems are correct. If that is the case, it will copy
the bytes defined in the other system's database with the accessory
variables (tag number, service, qualification, unit and subunit), in such
Software Manual
way that the link is correct. Variables that have been allocated
incorrectly are deallocated.
If you have a link to more than one system (e.g. a master or
communication server to more slaves), you have the additional option
of copying the information of all slaves at once.
Make sure the application names of the connected system have been
defined (FSC-FSC architecture window, see Figure 4-20). In all the
other applications, the name of the application you are currently
configuring must be defined.
Block numbers If the protocol is RKE3964R, you can define block number that
should be used. For further details refer to Appendix F of this manual
("Communication").
Secondary link If the link status has been set to 'Secondary', all you need to do for its
link specification is refer to the primary channel whose configuration
it should use. In the example shown in Figure 4-22, channel B on
module 1 in Central Part 1 will be the primary Modbus protocol.
Figure 4-22 Defining a secondary link
Software Manual
Note:
If you change the configuration of a channel to which inputs or
outputs have been allocated (FSC-FSC, Development System,
Modbus RTU, Modbus H&B or RKE3964R protocols) and
these changes affect the allocation of these variables, you will be
prompted to confirm the modification.
Timeout This parameter is only defined for the following communication

protocols:
– Modbus RTU
– Modbus H&B
– RKE3964R
A communication channel is regarded faulty if no valid frame was
received within the device communication timeout, which is defined
here. This timeout is user-configurable.
Modbus RTU & You can enter any value between 1.0 and 25.0 seconds (in steps of
Modbus H&B 0.1 second), or press <D> to deactivate the timeout altogether. If the
timeout has been deactivated, the field will contain the text 'Not used'.
RKE3964R You can enter any value between 1.0 and 90.0 (in steps of 0.1
second). The default is 3 seconds. If the RKE protocol is used for
communication between FSC and a DCS, this timeout must be set to
a multiple of 3 seconds. If any other value is entered, RKE
communication between FSC systems is assumed.
Interface The following interfaces are supported:

− RS-232C, point-to-point (B-interface)
− RS-232, not isolated
− RS-422, not isolated
− Current loop (E-interface)
− RS-232, multidrop (F-interface)
− Fiber optic, no encoding (G-interface)
− Fiber optic, Manchester (G-interface)
− Fiber optic, FM0 (G-interface)
− Fiber optic, FM1 (G-interface)
− RS-422, readback (H-interface)
− RS-485, no encoding (I-interface)
− RS-485, Manchester (I-interface)
− RS-485, FM0 (I-interface)
Software Manual
− RS-422, no encoding (I-interface)
− RS-422, Manchester (I-interface)
The interfaces that can be selected depend on the selected protocol and
network type.
Baud rate The following baud rates are supported:

– 2M – 57k6 – 9600
– 1M – 50k – 4800
– 125k – 38k4 – 2400
– 115k2 – 19k2 – 1200
The values that can be selected depend on the selected communication

protocol and interface type. For details refer to Appendix F of this
Note:
The maximum baud rate for modem communication is
9600 baud.
Handshake The following handshake types are supported:

– Hardware
– Xon-Xoff
– None
Number of stop bits The following options are available:

– 1
– 2
Number of bits/char The following options are available:

– 7
– 8
Parity The following parity types are supported:

– Even
– Odd
– None
Software Manual
4.7.7 Installing a Safety Manager Module (SMM)
SMM modules To define a Safety Manager Module (SMM), make sure the COM
module type (see page 4-46) is set to '10018/2/U' (with flash memory)
or '10008/2/U' (without flash memory).
Notes:
1. Please note that the number and type of communication
modules in the system are specified in the Central Part
definition screen (see subsection 4.7.3).
2. Only the communication module with the highest number
may be changed to 10008/2/U or 10018/2/U.
If you then choose the Install\Modules\Central parts\COM option, the

screen as shown in Figure 4-23 will appear. (Please note that you may
need to press <PgUp> or <PgDn> a number of times to get to the
correct communication channel.)
Figure 4-23 Protocol definition for communication with

the TPS system
Software Manual
The following fields are shown:
Protocol This field will always be set to 'UCN'. The only other value it can
have is 'Undefined' (to deallocate the module).
Redundant This field defines the Central Part redundancy. It cannot be modified,
and will automatically be set to 'Yes' or 'No':
Yes: The Safety Manager Module is configured in an FSC system
with redundant Central Parts.
No: The Safety Manager Module is configured in an FSC system
with a single (non-redundant) Central Part.
Link specification The amount of memory (marker bytes and register bytes) that is used
for the communication with the TotalPlant Solution (TPS) system
needs to be defined. If you press <E>, a popup window will appear
which allows you to define the amount of memory used (see Figure
4-21 on page 4-53). FSC Navigator automatically allocates the
required amount, and all inputs and outputs that are to be used for the
communication are allocated within the reserved area.
(See also subsection 4.10.3, which deals with the allocation of inputs
and outputs to COM modules.)
UCN node number Here you should enter the UCN node number of the FSC-SMM.
The node number must be an odd number between 1 and 63. This
node number will be used for Central Part 1. The node number of
Central Part 2 is the node number of Central Part 1 plus one.
Time synchronization If an FSC system is connected to a Universal Control Network

(UCN), you need to specify whether the FSC system should be
synchronized to the UCN time or to the FSC time master in the
network.
Use <Space> to toggle between the available options or press <?> to
select from a list. The following options are available:
FSC Network: The FSC system is synchronized to the FSC time
master in the network.
UCN: The FSC system is synchronized to the UCN.
For further details on time synchronization refer to Appendix F of this

Software Manual
4.7.8 Installing a PlantScape Interface Module
PlantScape To define a PlantScape interface module, make sure the COM

interface module module type (see page 4-46) is set to '10018/1/1'.
Notes:
1. Please note that the number and type of communication
modules in the system are specified in the Central Part
definition screen (see subsection 4.7.3).
2. Only the communication module with the highest number
may be changed to 10018/1/1.
If you then choose the Install\Modules\Central parts\COM option, the

screen as shown in Figure 4-24 will appear. (Please note that you may
need to press <PgUp> or <PgDn> a number of times to get to the
correct communication channel.)
Figure 4-24 Protocol definition for communication with

the PlantScape system
Software Manual
The following fields are shown:
Protocol This field will always be set to 'PlantScape'. The only other value it
can have is 'Undefined' (to deallocate the module).
Redundant This field defines the channel redundancy. If the module is

configured in an FSC system with redundant Central Parts, it will
always be set to 'Yes' and it cannot be modified. For single
configurations, you can use <Space> to toggle between 'Yes' and
'No'.
Link specification The amount of memory (marker bytes and register bytes) that is used
for the communication with the PlantScape system needs to be
defined. If you press <E>, a popup window will appear which allows
you to define the amount of memory used (see Figure 4-21 on page
4-53). FSC Navigator automatically allocates the required amount,
and all inputs and outputs that are to be used for the communication
are allocated within the reserved area.
(See also subsection 4.10.3, which deals with the allocation of inputs
and outputs to COM modules.)
IP address Here you should enter the IP address that the interface module will
have on the PlantScape network. Make sure the IP address you enter
is valid (as defined in the Ethernet specification).
Each of the four numbers must be between 0 and 255. You cannot use
127, which is a reserved number.
In case of redundancy, only the IP address of the redundant channel
can be edited.
Exchanging When exchanging 10018/E/x Ethernet interface modules in the FSC

10018/E/x modules system, please note the following important consideration which
applies to the PlantScape side.
Each 10018/E/x module has its own unique (factory-installed)

physical Ethernet address. To set up a TCP/IP connection, Windows
NT uses an Address Resolution Protocol (ARP) table filled with IP
addresses and their associated physical Ethernet addresses. If a new
FSC system is added to the Ethernet network, a new IP address is
introduced (for a 10018/E/x module). Windows NT will then first
request the associated physical Ethernet address on the Ethernet
network, and add the Ethernet address it receives to the ARP table.
If a 10018/E/x module is exchanged in the FSC system, this results in
a new physical Ethernet address. The ARP table is then not updated
automatically because Windows NT is not aware of this change. The
Software Manual
result is that Windows NT is not able to make a new connection since
it uses the wrong combination of Ethernet address and IP address.
This situation can be resolved in either of two ways:
• Solution 1: Type the following command at the command-line
prompt in order to delete the IP address and physical Ethernet
address from the ARP table: ARP -d [IP address] <Enter>.
• Solution 2: Restart Windows NT.
Software Manual
4.7.9 Installing a Diagnostic and Battery Module (DBM)
DBM module To define a diagnostic and battery module (DBM), choose the
following menu options:
Install Modules Central parts DBM
This will open a configuration screen that allows you to modify a

number of DBM characteristics:
Figure 4-25 Diagnostic and battery module (DBM)
You can modify the following DBM characteristics:

• Module type, and
• Temperature settings.
Software Manual
Module type The following DBM module types are supported:
– 10006/1/1 (RTC)
– 10006/2/1 (RTC)
– 10006/2/2 (DCF)
Use <Space> to toggle between the available module types or press
<?> to select from a list.
The 10006/2/2 DBM module has DCF capability, which means it is

capable of receiving atomic clock information from the DCF-77 radio
time beacon, which is located near Frankfurt, Germany. Figure 4-26
shows the receiving range of the DCF-77 signal. The inner circle
shows the region of Europe in which reception of the DCF signal is
usually good. The outer circle shows the region where the reception of
the DCF signal is usually possible. The DCF-77 atomic clock
information is received on a continuous basis.
Frankfurt
Figure 4-26 Receiving radius of DCF signal
DBM temperature
settings The following DBM temperature setting can be modified:
• Degree type (Celsius, Fahrenheit or Kelvin)
• Low temperature shutdown
• Low temperature alarm
• High temperature alarm
• High temperature shutdown
Table 4-15 below lists the defaults for the various temperature
setpoints as well as their ranges.
Software Manual
Table 4-15 DBM temperature settings
Description Celcius (C) Fahrenheit (F) Kelvin (K)
Default Range Default Range Default Range

Low temperature shutdown 0 0 to 20 32 32 to 68 273 273 to 293
Low temperature alarm 5 5 to 25 41 41 to 77 278 278 to 298
High temperature alarm 55 35 to 55 131 95 to 131 328 308 to 328
High temperature shutdown 60 40 to 60 140 104 to 140 333 313 to 333
The minimum difference between the low temperature shutdown and

low temperature alarm must be 5°C, 5°K or 9°F. This is also true for
the high temperature alarm and high temperature shutdown.
Date format The date and time format used on the DBM status display (see
subsection 12.8.4) depends on the Regional Settings as laid down in
the Windows NT/2000 Control Panel.
Note:
FSC Navigator will always display the century indicator, even if
you do not specify it in Regional Settings. This means that if
you set the year to 'yy' (i.e. without century indicator), the date
will still show '2000' rather than '00'.
Important!
The date format is stored in the application data files after
translation. This means that the date format for an application is
always determined by the settings of the FSC user station on
which the application was translated. For example, if an
application was translated in a European "date format zone"
(dd-mm-yy), but is subsequently shipped to the U.S.
(mm/dd/yy), it will continue to use the European date format,
regardless of the Regional Settings of the FSC user station in
the U.S. If you want the application to switch to the U.S. date
format, you should translate it again on the "American" user
station, and reload it.
Software Manual
4.7.10 Installing a Single Bus Driver (SBD)
SBD To define a single bus driver (SBD), choose the following menu
options:
Install Modules Central parts SBD
This will open a screen that lists the position(s) of the SBD in the
Central Part rack(s). No additional hardware configuration is required.
Note:
A single bus driver can only be placed in configurations that
meet all of the following conditions:
1. The system bus used has either 5, 7, or 12 slots.
2. There is only one Central Part per rack.
3. There is only one PSU per Central Part.
4.7.11 Installing a Vertical Bus Driver (VBD)
VBD To define a vertical bus driver (VBD), choose the following menu
options:
Install Modules Central parts VBD
This will open a configuration screen that allows you to specify the
VBD characteristics (see Figure 4-27 on the next page).
If more than one VBD have been defined, you can move between
them by pressing <PgUp> and <PgDn>. Depending on the
configuration, you may be able to modify the following VBD
characteristics:
• I/O configuration, and
• Module type.
Note:
The VBD function cannot be changed if one or more HBDs
have already been connected to a VBD.
Software Manual
Figure 4-27 Vertical bus driver
I/O configuration This field determines the type of I/O that the VBD controls.
Depending on the Central Part configuration of the FSC system (see
subsection 4.5.1 on page 4-12), you may use <Space> to modify this
field. There are two options:
• Single The VBD controls single I/O.
• Redundant The VBD controls redundant I/O.
Table 4-16 below shows the various VBD I/O configuration options.
Table 4-16 VBD I/O configuration

If CP architecture is...
.... then I/O configuration is...
Single Single
Redundant Single or
Redundant
Software Manual
If HBDs have already been connected to a VBD, its VBD function
(i.e. the 'I/O configuration' field) can no longer be changed.
Consecutive VBDs must always have the same VBD function. It is not
allowed to mix VBD functions, as shown in the examples below.
Correct:
VBD no.: 1 2 3 4 5 6
VBD function: R R R R S S
Incorrect:
VBD no.: 1 2 3 4 5 6
VBD function: S R S S R R
Module type This field determines the type of VBD that is used. Depending on the
Central Part architecture of the FSC system (see subsection 4.5.1 on
page 4-12) and the VBD I/O configuration (see above), you may use
<Space> to modify this field. There are two options:
• 10001/R/1, and
• 10001/1/1.
Note:
For new applications always use 10001/R/1, regardless of
whether you can select 10001/1/1 or not.
Table 4-17 below shows the various VBD module type options.
Table 4-17 VBD module type

If CP architecture is... .... and I/O configuration .... then VBD module
(see subsection 4.5.1) (see above) is... type is...
10001/R/1 or
Single Single
10001/1/1*
10001/R/1 or
Redundant Redundant
10001/1/1*
Redundant Single 10001/R/1
* For new applications only use 10001/R/1.
Module type 10001/R/1 means that the VBD is equipped with a relay
to isolate the VBD from the vertical bus in case of a VBD fault.
Software Manual
4.7.12 Installing a Horizontal Bus Driver (HBD)
HBD To define a horizontal bus driver (HBD), choose the following menu
options:
Install Modules HBD
This will open a configuration screen that allows you to place HBDs
and specify their characteristics (see Figure 4-28 below). For every
placed VBD, a maximum of 10 HBDs can be placed. If more than one
VBD has been defined, you can use <PgUp> and <PgDn> to browse
through the HBD configuration screens of each VBD.
Figure 4-28 Horizontal bus drivers
The following configuration parameters can be modified for each

HBD:
• The safety relation of the HBD, and
• The position of the HBD.
Software Manual
Safety relation The safety relation of an HBD can normally be altered, except if
HBDs have safety-related I/O connected to them. In that case they
will always be safety-related, and their safety relation cannot be
modified. Safety-related I/O modules can only be connected to a
safety-related HBD. Use <Space> to modify the safety relation.
Rack number The rack number of the each HBD must be specified. Please note the
following considerations:
1. If I/O has already been placed for the HBD, the rack number can
no longer be changed.
2. The rack number cannot be a Central Part rack number.
3. The rack may not already be controlled by another HBD.
4. An HBD can be removed by entering '0' (zero), but you can only
remove the HBD with the highest number.
5. An HBD cannot be placed in a rack that is located above the
Central Part rack(s).
6. I/O racks and Delta power supply racks cannot be mixed.
If the VBD controls redundant I/O, the HBD can control one
additional rack. You will then be prompted to enter two rack numbers
(e.g. HBD 2 in Figure 4-28). Please note the following considerations
for the second rack number:
1. The rack number cannot be a Central Part rack number.
2. The numbers for the first rack and the additional rack must be
consecutive.
3. The additional controlled racks must be in the same cabinet as the
one in which the HBD is placed, and they must be on consecutive
positions.
Rack position(s) The rack position(s) where the HBD is placed are added
automatically. They depend on the type of I/O that the VBD controls:
• single I/O: position 21.
• redundant I/O: position 20 for Central Part 1, and
position 21 for Central Part 2.
Software Manual
4.7.13 Installing Input and Output Modules (I/O)
I/O modules To define an input or output module (I/O), choose the following
menu options:
Install Modules I/O
This will open a configuration screen that allows you to place I/O
modules and specify their characteristics (see Figure 4-28).
Figure 4-29 Placing I/O modules
I/O modules can be placed in any rack in which an SBD or HBD has
been placed or which is controlled by an HBD. If more than one I/O
rack has been defined, you can use <PgUp> and <PgDn> to browse
through the I/O racks.
Software Manual
The following configuration parameters can be specified for each I/O
position:
• The safety relation of the I/O module,
• The I/O module type,
• Whether or not the I/O module is tested by the CPU,
• The voting scheme used for the I/O module,
• Whether or not the I/O module is actually placed in the system, and
• Whether or not earth fault monitoring (EFM) is active.
Safety relation The 'Safe' field defines whether the I/O module is safety-related or
not. The safety relation of an I/O module can only be set after the
module has been placed (i.e. its rack location has been defined).
It can normally be modified, except in the following cases:
• If a module is non fail-safe, it can only be non safety-related.
• If a module has safety-related signals connected to it, it cannot be
made non safety-related.
• If the controlling HBD is non safety-related, the I/O modules will
also be non safety-related.
Tested Fail-safe I/O modules are normally always tested by the FSC system.
You may, however, disable the test for the fail-safe modules.
Use <Space> to toggle between 'Yes' (tested) and 'No' (not tested), or
press <?> to choose from a list.
Disabling the test for fail-safe modules is only possible for analog
output modules. Non fail-safe I/O modules are always
non safety-related and they are not tested.
Voting The voting scheme determines how the FSC system responds in case
a fault is detected in the I/O module. Table 4-18 on the next page lists
which voting schemes are possible for each module. Use <Space> to
toggle between the available options or press <?> to select from a list.
Software Manual
Table 4-18 Voting type per I/O module
Module VBD controls redundant I/O VBD controls single I/O
10101/./. 2oo2D / 1oo2D 1oo1D
10102/./. 1oo2D 1oo1D
10103/1/. – 1oo1
10104/./. 2oo2 1oo1
10105/2/1 2oo2D / 1oo2D 1oo1D
10106/2/1 2oo2D / 1oo2D 1oo1D
10201/./. 2oo2D / 1oo2D 1oo1D
10203/1/. 2oo2D 1oo1D
10205/./. – 1oo1D
10206/./. 2oo2 1oo1
10208/./. 2oo2 1oo1
10209/./. 2oo2 1oo1
10212/1/. 2oo2D / 1oo2D 1oo1D
10213/./. 2oo2D / 1oo2D 1oo1D
10214/1/2 2oo2D / 1oo2D 1oo1D
10215/./. 2oo2D / 1oo2D 1oo1D
10216/./. 2oo2D / 1oo2D 1oo1D
10100/./. – –
Note:
For details on voting refer to the FSC Safety Manual.
If the current rack is a Central Part rack with an SBD, all positions
that are not in use for the Central Part modules can be selected for I/O
modules. If a module is placed for a VBD that controls redundant I/O,
then the module is automatically placed at the adjacent positions for
the higher Central Parts.
Software Manual
I/O module The 'I/O module' field allows you to select the type of module that
should be placed on the indicated position. You can use the following
keys to select or delete a module:
<D> Press this key to delete the module that is placed at the position
indicated by the cursor.
<C> Press this key to copy the module that has been placed last in the
selected rack.
<S> Press this key to display a window listing all the modules that can be
placed at the selected position (see Figure 4-30). The list will only
contain valid choices.
Figure 4-30 Selection of a module
Software Manual
Placed The 'Placed' field defines whether or not the I/O module is actually
placed in the system. Use <Space> to toggle between 'Placed' and
'Not placed', or press <?> to choose from a list.
Choose 'Placed' if the module will indeed be used in the system.
Choose 'Not placed' if the module will not be used at this time, but in
a future expansion of the system. I/O variables can only be allocated
to placed modules.
EFM This field specifies whether or not earth fault monitoring (EFM) is
active for the module. The 10106/2/1 module is the only module that
supports earth fault monitoring. Use <Space> to toggle between 'Yes'
and 'No' for this module. For all other modules the field value is fixed
at 'N/A' (no earth fault monitoring available).
Please specify whether earth fault monitoring (EFM) should be active
for the module. The earth fault monitor detects two things:
1. a connection between any of the input wires and earth (for sensors
without earth connection).
2. a loss of connection between the Vdc power supply and earth (for
sensors with earth connection).
Placing modules Please note the following considerations when placing I/O modules:
1. If the 'Safe' field is set to 'Yes', only fail-safe modules can be
placed.
2. Depending on the VBD function and HBD type(s), only certain
modules can be placed.
3. If you want to place intrinsically safe (Ex-i) modules (10103/1/.
and 10207/1/1) in the same rack as non intrinsically safe modules,
the intrinsically safe modules must be placed at rack positions
lower than the non intrinsically safe modules. There must also be
at least one free position between the two groups.
4. If you want to place high-voltage modules (10101/./2, 10101/./3,
10213/./., and 10214/1/2) in the same rack as low-voltage
modules, the high-voltage modules must be placed at rack
positions lower than the low-voltage modules. There must also be
at least one free position between the two groups.
5. High-voltage modules cannot be placed in the same rack as
intrinsically safe (Ex-i) modules.
Note:
High-voltage modules are all modules operating at voltages
higher than 50 Vdc.
Software Manual
Deleting or When a module is deleted or replaced by another module, FSC
replacing modules Navigator checks if any signals are connected to that module. If that
is the case, you will be asked whether these signals should be
deallocated (only then can the module be deleted):
Signals connected to I/O module. Deallocate? (Y/N)
If you press <Y>, the signals are deallocated and the module is deleted
or replaced. If you press <N>, the operation is aborted.
The following modules are exchanged without the need of

deallocating any connected signals:
− 10101/1/1 ↔ 10101/2/1 – 10206/1/1 ↔ 10206/2/1
− 10101/1/2 ↔ 10101/2/2 – 10209/1/1 ↔ 10209/2/1
− 10101/1/3 ↔ 10101/2/3 – 10213/1/1 ↔ 10213/2/1
− 10104/1/1 ↔ 10104/2/1 – 10213/1/2 ↔ 10213/2/2
− 10102/1/2 ↔ 10102/2/1 – 10213/1/3 ↔ 10213/2/3
− 10201/1/1 ↔ 10201/2/1 – 10215/1/1 ↔ 10215/2/1
− 10205/1/1 ↔ 10205/2/1 – 10216/1/1 ↔ 10216/2/1
Other modules cannot be exchanged due to functional differences
between the /1/ and /2/ versions or due to different voltage classes.
Software Manual
4.8 Signal Specification
4.8.1 Introduction
Signal After all hardware has been defined, you need to specify the
specification characteristics of all I/O signals that are used in the FSC system. This
can be done in two ways:
• manually (see subsections 4.8.2 to 0), or
• importing them from a dBASE file (see subsection 4.9).
If you choose the 'Signal specs' option from the main menu, the
following screen will open:
Figure 4-31 Signal specifications
Software Manual
Menu options The menu in the signal specification screen provides a number of
options related to specifying the characteristics of all I/O signals used
in the FSC application. It has the following options:
Add Choose this option to manually add variables to the variable database.
Search Choose this option to search for a variable by (part of the) tag
number, and to view or edit its signal specifications (service,
qualification, location, unit and subunit). For details refer to
subsection 0.
Write dBASE Choose this option to write the I/O variables of the variable database
to a dBASE compatible file. For details refer to subsection 4.9.3.
Note:
variables).
Read dBASE Choose this option to read I/O variables from a dBASE compatible
file into the FSC variables database. For details refer to subsection
4.9.4.
Main Choose this option to return to the previous menu.
Signal The screen as shown in Figure 4-31 shows a number of columns that
characteristics list the characteristics of the I/O variables. The following fields are
shown:
V This field specifies the variable type (I, AI, BI, XI, O, AO, BO, XO,
A, or P).
Tag number This field specifies the variable tag number.
Service This field specifies the description of the variable (e.g. "Level in
glycol tower").
Qualification For boolean variables, this field provides information about the '1' (or
active) status of the variable (e.g. HIGH).
Software Manual
Loc This field provides information about the location of the sensor or the
actuator (e.g. FLD). It is only valid for I/O signals. A number of
locations are reserved for special use:
– ANN Alarm function (I, O, A only).
– COM Variable that can be altered or read via a communication
link (I, BI, O, BO only).
– MUX Multiplexer variable (BI, BO, XI, XO only).
– SYS System variable (reserved for use by the FSC programs).
– FSC Variable that can be altered or read by another FSC system
Unit This field specifies the name of the unit for which this variable is
used in the application program, e.g. F-210 (Furnace 210).
Subunit This field specifies the name of the subunit for which this variable is
used in the application program, e.g. B-210 (Burner on Furnace 210).
4.8.2 Adding Signals
Adding signals To add a signal, choose the following menu options:

Signal specs Add
This allows you to add a new signal to the FSC database (see Figure
4-32 on the next page). The following fields are mandatory:
• V (variable type), and
• Tag number.
Signals are identified by these two characteristics, which means that
their combination must be unique for each I/O signal. Please note that
the tag numbers are case-sensitive (i.e. 'psu' is not the same as 'PSU').
If you attempt to enter a combination that is already in use, the
following error message will be displayed:
Variable type + tag number is not unique.
If you have entered a valid new combination of variable type and tag
number, the variable will be added to the FSC database.
If you press <?> with the cursor in a field, a list will be displayed that
either shows the available options (e.g. 'V' field) or an overview of
values that have already been allocated (e.g. 'Tag number' field).
Software Manual
Notes:
1. System variables (i.e. variables with location 'SYS'), markers
(M), counters (C), registers (R) and timers (T) cannot be
added.
2. The total number of multiplexer inputs (XI), multiplexer
outputs (XO) and alarms (A) in the application is 64.
Tag number
considerations Please note the following considerations when entering a tag number:
1. Empty tag numbers are not allowed.
2. Tag numbers cannot contain a comma, semicolon or question
mark.
3. Tag numbers can only contain trailing spaces (i.e. spaces at the
end). This means that tag numbers like 'Input 1 ' or 'HLS 34'
are not allowed.
4. The tag numbers of default system variables are reserved. Table
4-19 below lists the reserved tag numbers.
Table 4-19 Reserved tag numbers

V Tag number V Tag number
1)
AI VM r/p/17 I FSC-SYSTEM-FAULT
BI DATE I INPUT-FAILURE
BI DAY I INT.COMMUNIC.FLT
BI HOURS I IO-COMPARE
BI MINUTES I IO-FORCEDI OUTPUT-FAILURE
BI MONTH I RED.INPUT-FAULT
BI SECONDS I TEMP.PRE-ALARM
BI YEAR I TRANSMIT.-FAULT
2)
I CENTR.PART-FAULT I WD r/p/s
3)
I COM-I/O O BO SER triggers
I DEVICE-COM.FLT O COM-I/O
4)
I EXT.COMMUNIC.FAULT O E cp_com_ch_blk
I FLASHER-0.5Hz O SEC.SWITCH-OFF
I FLASHER-1Hz
I FLASHER-2Hz
I FLASHER-5Hz
Software Manual
Notes:
1) r/p/17 = rack / position, e.g. VM 3/8/17
2) r/p/s = rack / position / sequence no., e.g. WD 3/7/1
3) Depends on corresponding BO.
4) RKE block triggers: cp_com_ch_blk = central part_COM
module_channel_block no., e.g. E 1_1_B_23
4.8.3 Browsing Through Signals
Browsing through To browse through the signals that have already been defined, choose
signals the following menu options:
Signal specs Search
The list will be empty at this point, with the cursor in the first 'V' field.
If you now press <PgDn>, the screen will be updated to list all
variables in the database, starting with the first one, sorted by variable
type ('V' field). If you press <PgUp>, you will go the end of the
database.
You can use the <PgUp>, <PgDn>, ↑, and ↓ keys to browse through
the list of existing variables (see Figure 4-32 on the next page). As
you go through the list, one variable will always be highlighted. The
message bar will indicate what actions can be performed on the
selected variable. For example, the selected variable in Figure 4-32
can be changed and deleted. For details on changing and deleting
variables refer to subsection 4.8.4.
4.8.4 Modifying and Deleting Signals
Modifying and Use the arrow keys to select the field that you wish to modify. The
deleting signals message bar will indicate whether the signal can be changed and/or
deleted. The variable type can never be changed.
If a variable can be deleted, you can do so by pressing <Ctrl> + <U>.
If the variable has already been allocated, you will be asked to confirm
the operation.
Software Manual
Notes:
1. System variables (with location 'SYS') cannot be deleted.
2. Markers (M) cannot be changed, but they can be deleted.
Please note that markers that belong to a non fail-safe digital
input (tag number starts with 'I') can only be deleted by
deleting the digital input itself.
3. Timers (T) cannot be changed, but they can be deleted.
Please note that timers that belong to a non fail-safe digital
input (tag number starts with 'I') can only be deleted by
deleting the digital input itself.
4. Counters (C) cannot be changed, but they can be deleted.
Please note that counters that belong to a PID (tag number
starts with 'P') can only be deleted by deleting the PID itself.
5. Registers (R) cannot be changed, but they can be deleted.
Please note that registers that belong to a PID (tag number
starts with 'P') can only be deleted by deleting the PID itself.
Figure 4-32 Browsing through signals
Software Manual
Variable fields Table 4-20 below shows the variable fields that can be changed.
Table 4-20 Variable field characteristics

Type Tag number Service Qualification Location Unit Subunit Delete?
4)
I Y Y Y Y Y Y Y
1)
I N Y Y N (SYS) N N N
O Y Y Y Y Y Y Y
6)
O N Y Y N (SYS) N N N
5)
AI Y Y N Y Y Y Y
AI N N N N (SYS) N N N
5)
AO Y Y N Y Y Y Y
BI Y Y N Y Y Y Y
BI N Y N N (SYS) N N N
BO Y Y N Y Y Y Y
3)
XI Y Y N N (MUX) Y Y Y
3)
XO Y Y N N (MUX) Y Y Y
3)
A Y Y N N (ANN) Y Y Y
3)
P Y N N N Y Y Y
2)
M N N N N N N N
2)
R N N N N N N N
T N Y N N N N N
C N Y N N N N N
Notes:
1) Tag number can be edited if the system input is the fault
reset input (RESET), force enable input (ENABLE), or the
clock synchronization input (CLOCK-SYNC).
2) The service of function block tag numbers can be changed.
3) The number of XI, XO, A and P variables are limited to a
specific maximum. The maximum number of XI and XO
variables is 16. The maximum number of A and P variables
is 64. If this number is reached, you can no longer add any
more variables of this type.
4) If the location of a variable is 'SYS' or 'MUX', you cannot
change it to another location type: These locations are
reserved and cannot be assigned to variables either.
5) The location cannot be changed to any of the reserved
locations: COM, FSC, MUX, SYS or ANN.
6) For BO SER triggers, the 'Unit' field shows the engineering
units of the BO.
Software Manual
4.8.5 Searching for Variables
Searching To search for a signal, choose the following menu options:

Signal specs Search
This allows you to search for signals in the FSC database. You can
enter a variable type, (part of) the tag number, and the location. All
variables with matching type, tag number and location are displayed
on screen. You can pause the display by pressing <F2>. Pressing
<F2> once more starts the display again. To break off the display,
press <Esc>.
Software Manual
4.9 Importing and Exporting Variables using dBASE Files
4.9.1 Introduction
Using dBASE In addition to adding signals manually (see subsection 4.8.2), you can
also import signals from a dBASE file, or export variable to a dBASE
file. This allows you to change the specification of existing variables.
It is also possible to add variables to the database. You cannot delete
variables from the variable database by simply removing them from
the dBASE file. These variables remain unchanged after a read
dBASE command.
Examples of dBASE usage are:
1. Creation of lots of tag numbers using a small dBASE program.
FSC Navigator does not provide options to create lots of variables
automatically. By writing a small dBASE program, you could, for
example, create tag numbers like 01-HLS-xxxHH, where 'xxx' is a
number from 000 to 999.
2. Allocation of hardware or communication (FSC or COM)
variables. FSC Navigator does not provide options to allocate
variables to hardware automatically. After writing the variables to
a dBASE file, variables with location 'FLD' can be allocated
easily by using a simple dBASE program.
3. Updating of variable allocations if lots of variables are moved
from, for example, one rack to another or from one
communication channel to another. FSC Navigator does not
provide options to reallocate hardware allocated variables
automatically. If for some reason multiple I/O modules must be
moved from rack X, position Q to rack Y, position R, a simple
dBASE program can be used to reallocate the variables.
4. Updating the SER sequence numbers of variables. FSC Navigator
does not provide an option to, for example, automatically allocate
SER sequence numbers for all the variables that do not have an
SER sequence number yet. By using a simple dBASE program,
these SER sequence numbers can be generated quickly.
5. Creating tables containing, for example, all SER sequence
numbers with accompanying tag numbers. By using a simple
dBASE program all variables with an SER sequence number can
be filtered and stored in a different dBASE file.
Software Manual
4.9.2 dBASE File Format
dBASE The following dBASE file format is used:

file format
Table 4-21 dBASE file format

FIELD LENGTH TYPE DESCRIPTION REMARKS
TYPE 2 Character Type General variable information Type

TAGNUMBER 16 Character Tag number and tag number are a unique
SERVICE 19 Character Service combination.
QUALIFICAT 16 Character Qualification
UNIT 8 Character Unit
SUB_UNIT 8 Character Subunit
LOC 3 Character Location
SHEET 3 Numeric Sheet 1 Sheet number(s) of the variable if

SHT 2 3 Numeric Sheet 2 they are allocated on a sheet.
SHT 3 3 Numeric Sheet 3 (These fields are not used.)
SHT 4 3 Numeric Sheet 4
RACK 2 Numeric Rack Hardware allocation

POS 2 Numeric Position
CHAN 2 Numeric Channel
SAFETY 1 Character Safety relation

FORCE 1 Character Force enable
WRITE 1 Character Write enable
SER 1 Character SER enable
SERSEQ 6 Numeric SER enable
CNTPT 1 Numeric Central Part Communication allocation for

COM 1 Numeric COM module variables with location 'COM'.
CHANNEL 1 Character COM channel
RKEBLOCK 3 Numeric RKE3964R block
number
SYSTEM 2 Numeric System number Communication allocation for

variables with location 'FSC'.
ADDRESS 5 Numeric Relative address The relative address (or Modbus

1)
(Modbus address ) address) of a variable with
location 'COM' or 'FSC'.
DCS_ADDR 5 Numeric DCS address Alias address for FSC system

used for data exchange with
process computers. In the case of
TPS, it is the counterpart of the
PLCADDR parameter of a TPS
point allocated to the FSC UCN
interface.
Software Manual
Table 4-21 dBASE file format (continued)
FIELD LENGTH TYPE DESCRIPTION REMARKS
AENGUNIT 5 Character Analog eng. unit Scaling range of an analog

2)
ANTOP 19 Numeric AN top scale input/output engineering unit
2)
ANBOTTOM 19 Numeric AN bottom scale indication.
REGTYPE 1 Character Register type Register type for the variable:

W = word
B = binary
L = long
F = float
2)
POWERON 19 Numeric Power-on value Power-on value of the variable.
VARADDRESS 10 Numeric Relative address Relative address compared to

start address of variable type.
Applies to following variable types:
I: loc. = FLD / COM /FSC
AI: loc. = FLD
BI: loc. = COM / FSC
O: loc. = FLD / COM / FSC
AO: loc. = FLD
BO: loc. = COM / FSC
SENSORTYPE 13 Character Sensor type For variables of type I.
RECORD_NO 5 Character Record number Range: 1…23999.
PVRAWLO 4 Character Raw count scaling Only for variable types AI and AO
factor (low value) (used to scale between
engineering units and binary
values). See note 3 below.
PVRAWHI 4 Character Raw count scaling Only for variable types AI and AO
factor (high value) (used to scale between
engineering units and binary
values). See note 4 below.
Notes:
1. For a detailed specification of the Modbus addresses refer to
2. With the decimal point at the 10th position (i.e. there are 9 digits in
front of the decimal point and 9 digital after). This means that
range is –999999999.999999999 to 999999999.999999999.
3. The scaling factor used depends on the type of analog signal:
– 0..20 mA, 0..10 V, 0..5 V: value = 0.
– 4..20 mA, 2..10 V, 1..5 V: value = 655.
4. Always set to 3276, except for voltage monitoring (VM) channel of
10105/2/1 module (in that case it is set to 3934).
Software Manual
4.9.3 Writing Variables to a dBASE File
Writing to To write variables to a dBASE file, choose the following menu

dBASE file options:
Signal specs Write dBASE
Note:
variables).
You are prompted to specify the name of the dBASE file that the
variables should be written to. The extension '.DBF' (dBASE file
extension) is automatically added. An error message will be displayed
if you enter an invalid file name. If you enter the name of an existing
file, you will be asked whether this file should be overwritten. If the
file does not exist yet, you will be asked whether the file should be
created.
The following variables with the following variable type will be

written to the dBASE file:
– I with locations 'FLD' (hardware), 'COM', 'FSC', 'ANN', 'SYS'
– O with locations 'FLD' (hardware), 'COM', 'FSC', 'ANN', 'SYS'
– BI with locations 'FLD' (hardware), 'COM', 'FSC', 'ANN', 'SYS'
– BO with locations 'FLD' (hardware), 'COM', 'FSC', 'ANN', 'SYS'
– AI
– AO
– T
– C
– R
– M
The system variables (with location 'SYS') that are used for the FSC
system are also written to the dBASE file, but they are ignored if the
dBASE file is read. They are only added for inspection purposes, e.g.
to generate a complete list of SER sequence numbers in dBASE
(which is also allowed for the system markers).
Note:
If you modify the export file in dBASE, make sure that you pack
it before importing it into FSC.
Software Manual
Using If you use Microsoft Excel to edit the exported dBASE file, the
Microsoft Excel following considerations apply:
• Make sure that you do not append, but insert new or copied
records.
• If you modify the width of any of the columns, only the 'visible'
data will be imported. This means that if the original column width
is 15, and you decrease the width to 8, then only the first 8
characters of the field will be imported. This may mean that new
variables may be created.
Using If you use Microsoft Access to edit the exported database file, the
Microsoft Access following consideration applies:
• Make sure that you do not import, but link the dBASE file.
4.9.4 Reading Variables from a dBASE File
Reading from To write variables to a dBASE file, choose the following menu
dBASE file options:
Signal specs Read dBASE
You are prompted to specify the dBASE file name that should be used
to import variables. If a file name you entered does not exist, an error
message will be displayed. FSC Navigator will first show the format
of the dBASE file. After that, the contents of the dBASE file are read.
The screen will then display the type and tag number of new or
changed variables. The data read from the dBASE file is checked for
consistency in accordance with Table 4-22 and Table 4-23 below.
Only variables types that are supported by FSC will be imported. All
other variable types are ignored. If you added variables with location
'MUX' or 'SYS' (reserved locations) or if you changed the location of
a variable to 'MUX' or 'SYS', the location is reset to location 'FLD'.
Notes:
1. If you have modified the export file in dBASE, make sure
that you pack it before importing it into FSC.
2. The maximum number of fields in the dBASE file is 40.
Software Manual
Table 4-22 Field interpretation for dBASE imports (inputs)
Variable type → I I I I AI BI BI BI
Location → COM FSC ANN FLD any COM FSC FLD
↓ Field ↓
Service / Copy Copy Copy Copy Copy Copy Copy Copy

Qualification
Unit / Subunit Copy Copy Copy Copy Copy Copy Copy Copy
Safety No Y=Yes No Y=Yes Y=Yes No Y=Yes Y=Yes

N=No N=No N=No N=No N=No
Other=Undef. Other=Undef. Other=Undef. Other=Undef. Other=Undef.
Rack / Position / Ignored Ignored Copy (*1) Copy (*1) Copy (*1) Ignored Ignored Copy (*1)
Channel
Force enable Y=Yes Y=Yes No Y=Yes Y=Yes No No No

Other=No Other=No Other=No Other=No
Write enable Yes No No No No Yes No No
Engineering units Ignored Ignored Ignored Ignored Copy (*3) Ignored Ignored Ignored
Top scale Ignored Ignored Ignored Ignored Copy (if <>0) Ignored Ignored Ignored
(*4-*7, *9-*13)
Bottom scale Ignored Ignored Ignored Ignored Copy (if <>0) Ignored Ignored Ignored
(*4-*7, *9-*13)
SER / Y=Yes Y=Yes Y=Yes Y=Yes Y=Yes No No No

SER sequence Other=No Other=No Other=No Other=No Other=No
Copy SER Copy SER Copy SER Copy SER Copy SER
seq. (*10) seq. (*10) seq. (*10) seq. (*10) seq. (*10)
Central Part / Copy (*11) Ignored Ignored Ignored Ignored Copy (*11) Ignored Ignored
COM mod. ch. /
RKE3964 block
(location 'COM')
System Ignored Copy (*12) Ignored Ignored Ignored Ignored Copy (*12) Ignored
(location 'FSC')
Relative address Copy (*13) Copy (*13) Ignored Ignored Ignored Copy (*13) Copy (*13) Ignored
(Modbus address)
(*14)
DCS address Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13)
Register type Ignored Ignored Ignored Ignored Ignored Copy Copy Ignored
(*13,*16) (*13,*16)
Power-on value Ignored Ignored Ignored Ignored Ignored Copy (*16) Copy (*16) Ignored
Variable address Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
Sensor type Ignored Ignored Ignored Copy (*15) Ignored Ignored Ignored Ignored
Record number Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
PVRAWLO Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
PVRAWHI Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
See the notes on page 4-92.
Software Manual
Table 4-23 Field interpretation for dBASE imports (outputs)
Variable type → O O O O AO BO BO BO
Location → COM FSC ANN FLD any COM FSC FLD
↓ Field ↓
Service / Copy Copy Copy Copy Copy Copy Copy Copy

Qualification
Unit / Subunit Copy Copy Copy Copy Copy Copy Copy Copy
Safety No Y=Yes No Y=Yes Y=Yes No Y=Yes Y=Yes

N=No N=No N=No N=No N=No
Other=Undef. Other=Undef. Other=Undef. Other=Undef. Other=Undef.
Rack / Position / Ignored Ignored Copy (*1) Copy (*1) Copy (*1) Ignored Ignored Copy (*1)
Channel
Force enable No No Y=Yes (*2) Y=Yes Y=Yes No No No

Other= Other=No Other=No
Nodbase1.tbl
Write enable No No No No No No No No
Engineering units Ignored Ignored Ignored Ignored Copy (*3) Ignored Ignored Ignored
Top scale Ignored Ignored Ignored Ignored Copy (if <>0) Ignored Ignored Ignored
(*4-*8,*10-
*13)
Bottom scale Ignored Ignored Ignored Ignored Copy (if <>0) Ignored Ignored Ignored
(*4-*8,*10-
*13)
SER / Y=Yes Y=Yes No Y=Yes Y=Yes Y=Yes Y=Yes No

SER sequence Other=No Other=No Other=No Other=No Other=No Other=No
Copy SER Copy SER Copy SER Copy SER Copy SER Copy SER
seq. (*10) seq. (*10) seq. (*10) seq. (*10) seq. (*10) seq. (*10)
Central Part / Copy (*11) Ignored Ignored Ignored Ignored Copy (*11) Ignored Ignored
COM mod. ch. /
RKE3964 block
(location 'COM')
System Ignored Copy (*12) Ignored Ignored Ignored Ignored Copy (*12) Ignored
(location 'FSC')
Relative address Copy (*13) Copy (*13) Ignored Ignored Ignored Copy (*13) Copy (*13) Ignored
(Modbus address)
(*14)
DCS address Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13) Copy (*13)
Register type Ignored Ignored Ignored Ignored Ignored Copy Copy Ignored
(*13,*16) (*13,*16)
Power-on value Ignored Ignored Ignored Ignored Ignored Copy (*16) Copy (*16) Ignored
Variable address Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
Sensor type Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
Record number Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
PVRAWLO Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
PVRAWHI Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored
See the notes on page 4-92.
Software Manual
Notes:
(*1) If the hardware requirements for the allocation of a hardware channel
are met. Otherwise the location is reset.
For digital outputs (O) with location 'ANN', this means that only
variables with alarm type 'Alarm(s)' are copied (since this alarm type is
the only one with hardware allocation). Please note that alarm group
type TFSCOM1 is never copied (even with alarm type 'Alarm(s)') since
it does not have hardware allocation at all.
(*2) If the variable is allocated. Otherwise No.
(*3) If this field is missing in the dBASE file, then the engineering units field
contents of the variable in the FSC database is left unchanged. If it
concerns a new variable, then the initial contents of the engineering
units field will be 5 spaces.
(*4) If illegal situations occur (i.e. top–bottom < 0.001), the values of
bottom and top as specified in the dBASE file will not be accepted.
The top and bottom field contents of the variable in the FSC database
are then left unchanged. If it concerns a new variable, then the initial
contents of the top and bottom value will be 0.
-6
(*5) If the bottom scale or top scale values are > 10 -1 (maximum value)
-5
or < –10 +1 (minimum value), then these new value settings are not
imported nor clamped to the maximum values. If it concerns a new
variable, then the initial contents of the top and bottom value will be 0.
(*6) If neither the top scale and bottom scale are available, then the top
and bottom field contents of the variable in the FSC database is left
unchanged. If it concerns a new variable, then the initial contents will
be 0.
If the top scale is available and the bottom scale is not (or vice versa),
then FSC Navigator will NOT import the contents of just one field (both
fields must be available).
(*7) If bottom and top have been imported, the SER setpoints can have
values outside the range of the new top and bottom scale values! SER
setpoints will be re-scaling if necessary.
(*8) Analog outputs only: if necessary, FSC Navigator will set the power-on
value of an AO to its limit (if it exceeds the range).
(*9) Analog inputs only: note that if the analog range setting changes, the
maximum discrepancy value of the AI will automatically be
recalculated.
(*10) If the requirements for the SER and allocation of an SER sequence
number are met.
(*11) If a communication channel exists with a device's protocols, the RKE
block number must exist also. Otherwise the allocation is reset.
(*12) If the connection with this system is already made. Otherwise the
allocation is reset.
(*13) If the address is in the range and can be located. Otherwise the
allocation is reset.
(*14) See Appendix F of this manual ("Communication") for a specification
of Modbus addresses.
(*15) Only if a 10106/2/1 module has been installed on the rack/position
and if there is no mix of P&F and Namur sensors. Otherwise ignore.
(*16) Only if it fits in the register type. Otherwise ignore.
Software Manual
Field Please note that there are a number of field dependencies in the
dependencies import dBASE file. This means that certain combinations of fields
must be present for the record to be imported:
• Tag + tag number
(i.e. TYPE + TAGNUMBER)
• Rack + Position + Channel (hardware allocation of variables with
location 'FLD')
(i.e. RACK + POS + CHAN)
• SER Enable + SER sequence number
(i.e. SER + SERSEQ)
• Analog engineering unit + Top value + Bottom value
(i.e. AENGUNIT + ANTOP + ANBOTTOM)
• Central Part + COM module + Channel + Address
(i.e. CNTPT + COM + CHANNEL + ADDRESS)
• Central Part + COM module + Channel + Address + RKE block
(if RKE defined)
(i.e. CNTPT + COM + CHANNEL + ADDRESS + RKEBLOCK)
• Power-on value + Register type + Address (of variables with
location 'COM' and 'FSC')
(i.e. POWERON + REGTYPE + ADDRESS)
• Power-on value + Register type (for hardware-allocated variables)
(i.e. POWERON + REGTYPE)
• System number + Address
(i.e. SYSTEM + ADDRESS)
Software Manual
4.10 Hardware Specification
4.10.1 Introduction
Hardware If you choose the 'Hardware specs' option from the System
specification Configuration main menu, you can define the hardware allocation of
all input and output variables that are used in the FSC application.
Every variable type has its own kind of hardware specification.
First you need to specify the variable whose hardware allocation you
wish to define or modify:
Figure 4-33 Variable selection screen
Software Manual
Variable type Enter the variable type, or press <?> to choose from a list of available
options. If you enter 'NA', FSC Navigator will show all unallocated
variables.
Tag number Enter the tag number of the variable you want to examine. If you
enter an incomplete tag number, you will be shown all variables that
match the partial tag number.
You can also press <?> to choose from a list of existing tag numbers.
4.10.2 Allocation of Inputs and Outputs to I/O Modules
Allocation of All I/O variables need to be allocated before they can be used.
I/O variables Variables with allocation 'COM' or 'FSC' must be allocated to the
channel of a COM module. Other variables must be allocated to the
channels of I/O modules.
Allocation to Inputs and outputs that are not used for communication (i.e. location
I/O modules is not 'COM' or 'FSC') must be allocated to channels of I/O modules.
(Digital inputs and outputs with location 'ANN' do not need to be
allocated, except for outputs whose alarm type is 'Alarm').
Therefore a rack number, position and channel must be defined per
variable. For safety-related variables of type I and AI with non
fail-safe input sensors, one or two redundant channels may be
allocated. For multiple inputs and outputs (BI, XI, BO, XO), channels
must be allocated for every input or output (see page 4-100). A useful
tool to see the allocations of variables is the <F2> function key. This
will show the hardware allocations (see subsection 4.10.6).
Variable allocation The variable location is determined by three things:

• Rack number,
• Rack position, and
• Channel number.
Software Manual
Rack The 'Rack' field specifies the number of the rack that contains the
module which the variable can be allocated to.
FSC Navigator checks whether the rack number has been defined and
whether it is a Central Part rack with an SBD or a rack that is
controlled by a VBD. For inputs it also checks whether the rack for
redundant inputs is controlled by the same VBD as the main rack.
If you enter '0' (zero) or change the rack number, all the channels that
are allocated to the variable are deallocated.
After you have entered a valid rack number, a picture in the lower left
corner of the screen shows you which modules are placed in the rack.
Modules that can be selected for the variable are highlighted. If one or
more modules are highlighted, the position can be entered, otherwise
the position field is skipped.
Note:
The COM-I/O and SEC.SWITCH-OFF system variables must
be allocated to specific channels. If you change the rack, this
will result in a warning: "Limited I/O positions and channels
allowed". The variables may only be allocated to the following
locations:
– I COM-IO: The COM-IO system variable for digital inputs
(I) must be allocated to channel 1 or 5 of a
10101/2/1 module, which must be located in
one of the next adjacent positions: 1-2, 11-12,
13-14, 15-16, or 17-18.
– O COM-IO: The COM-IO system variable for digital
outputs (O) may be allocated to channel 1 or 3
of a 10201/2/1 module, or to channel 1 or 2 of
a 10215/2/1 module, which must be located in
one of the next adjacent positions: 1-2, 11-12,
13-14, 15-16, or 17-18.
– O SEC.SWITCH-OFF: The SEC.SWITCH-OFF system
variable for digital outputs (O) may be
allocated to channel 1 or 3 of a 10201/2/1
module , or to channel 1 or 2 of a 10215/2/1
module, which must be located in the adjacent
positions: 1-2.
Software Manual
Position The 'Position' field specifies the position in the selected rack that
contains the module which the variable can be allocated to. Enter the
position of a module that is highlighted in the lower left corner of the
screen. A module can be selected if the following conditions are met:
• Its position is within the set of possible positions:
− for Central Part racks with a SBD: all positions that are left in the
Central Part.
− if the VBD controls single I/O: 1 to 18.
− if the VBD controls redundant I/O: 1, 3, 5, 7, 9, 11, 13, 15, 17.
• The module is of a type suited for the variable (see Table 4-24
below). For example, an analog input can only be connected to an
analog input module.
• The module is safety-related if the variable is also safety-related.
• There are free channels on the module.
• The module has been defined as being placed.
Table 4-24 I/O modules suited for the different variable types
Inputs Outputs
I, BI, XI AI O, BO, XO AO
10101/1/1 10102/1/1 10201/1/1 10213/1/2 10205/1/1
10101/1/2 10102/1/2 10201/2/1 10213/1/3 10205/2/1
10101/1/3 10102/1/3 10203/1/2 10213/2/1
10101/2/1 10102/1/4 10206/1/1 10213/2/2
10101/2/2 10102/2/1 10206/2/1 10213/2/3
10101/2/3 10105/2/1 10207/1/1 10214/1/2
10103/1/1 10208/1/1 10215/1/1
10103/1/2 10208/2/1 10215/2/1
10104/1/1 10209/1/1 10216/1/1
10104/2/1 10209/2/1 10216/2/1
10106/2/1 10212/1/1 10216/2/3
10213/1/1
Software Manual
Figure 4-34 Allocation of a I/O variable to a module
In the example shown in Figure 4-34, The modules at positions 1 to 10

cannot be chosen because they are input modules. The modules at
positions 13 to 18 are of the correct type but cannot be chosen
because they are, for example, not safety-related whereas the signal
is, or there are no free channels left on the module. The 10201
modules remain, but only position 11 can be selected, because the
VBD that controls the rack controls redundant I/O.
If you enter '0' (zero) or change the rack position, all the channels that
were already allocated are deallocated.
After you have entered a valid rack position, a picture in the lower left
corner of the screen shows you which channels are still free on the
module.
Software Manual
Channel The 'Channel' field specifies the channel of the selected module
which the variable can be allocated to. If you select a channel that has
already been allocated, you will be asked if you wish to change the
allocation. The channels that are still free and can be selected are
shown in the lower left corner of the screen.
Figure 4-35 Allocation of a I/O variable to a channel
In the example shown in Figure 4-35 above, channel 6 is still free and
can be selected to allocate the variable to. Channels 1 to 5 and 7 to 16
have already been allocated.
After you have entered a value, FSC Navigator checks the following:
• The entered value is not greater than the number of channels on the
module.
• All the inputs and outputs can be allocated starting at this channel
and taking the following into account:
– the maximum number of channels of the selected module type,
and
– the number of extra modules that can be selected (one for
variables of type BI and BO with location 'MUX', and three
otherwise).
Software Manual
• You did not attempt to connect a safety-related variable to channels
5 to 8 of a 10212/1/1 module, as these channels can only be used for
non safety-related variables.
• The channel is still free. If it is not, the message line will tell you to
which variable the channel has already been allocated.
• There are enough channels free. Starting at the selected channel,
there must be enough free channels to allocate all inputs/outputs. If
the number of inputs and outputs is too high to allocate them all, all
the channels until the end of the module should be free, and another
module needs to be selected to allocate the rest of the inputs and
outputs.
If you enter '0' (zero) or change the channel, a channel that was
already allocated is deallocated.
Multiple inputs For variables of type BI, XI, BO and XO, channels need to be
and outputs allocated for the total number of bits. The 'Rack', 'Position' and
'Channel' fields now define where the allocation starts.
Starting with the defined channel, either sufficient consecutive
channels must be free to allocate all the bits, or all the channels until
the end of the module must be free. In the latter case, extra modules
can be used to allocate the remaining bits: up to three extra modules
for the BIs and BOs and for the XIs and XOs.
Apart from the considerations above, the following applies:

• All the channels needed must be allocated at once.
Changing the allocation will deallocate all channels that were
already allocated. You can abort the allocation by pressing <Esc>.
• For BI's and BO's with location 'MUX', and for XI and XO, only
single I/O is allowed. This means the VBD controlling the rack
cannot control redundant I/O.
• The extra racks must be controlled by the same VBD as the main
rack.
• When extra modules are used, allocation always starts with the first
channel. Sufficient consecutive channels must be free to allocate all
remaining unallocated bits, or all channels must be free.
• The extra modules must be of the same type as the main module
Software Manual
4.10.3 Allocation of Inputs and Outputs to COM Modules
Allocation to Inputs and outputs that are used for communication (i.e. location is
COM modules 'COM' or 'FSC') must be allocated to a channel of a communication
module.
Location 'FSC' Inputs and outputs with location 'FSC' must be allocated to a channel
with protocol FSC-FSC. Inputs with location 'FSC' only require a
system number to be defined. If you press <F2> in a record with
location 'FSC', you can see all allocated variables (see subsection
4.10.6).
Figure 4-36 Allocation to a communication module (location 'FSC')
Software Manual
System number Variables with location 'FSC' are used for the communication with
another FSC system. Variables are allocated to an FSC-FSC link by
selecting the number of the target FSC system. The program will
show you all available FSC systems that can be selected. This means
that the link must be defined in the communication channel
definition. The allocated system is highlighted in the window.
You can (re)allocate a system by pressing <S>.
You can deallocate a system by pressing <D> on the spot of the
highlighted system number.
You will be asked whether the variable should be allocated

automatically. If you confirm, the variable will be allocated to the first
free address. Otherwise you can enter a free address manually.
Relative address In general, a variable is automatically allocated to a free address in

the memory area reserved for the system number. The address
displayed is relative to the start address of the reserved memory area.
This address should be the same as the address of the corresponding
variable in the connected FSC system.
Location 'COM' Inputs and outputs with location 'COM' must be allocated to a
channel with protocol UCN, PlantScape, Modbus RTU, Modbus
H&B, Development System, or RKE3964R.
For inputs with location 'COM', a Central Part, communication
module and channel need to be defined per input. If you press <F2> in
a record with location 'COM', you can see all allocated variables (see
subsection 4.10.6).
Central Part Use <Space> to select a Central Part. The possible values depend on
the FSC system type. If you select 'Undef', an existing allocation will
be removed.
Communication After you have selected a Central Part, you can use <Space> to select
module a communication module that is placed in that Central Part. If you
select 'Undef', an existing allocation will be removed.
Channel You can use <Space> to select a channel (A or B) on the specified

communication module. If you select 'Undef', an existing allocation
will be removed.
Variables with location 'COM' can only be allocated to channels with
protocol Development System, UCN, PlantScape, Modbus RTU,
Modbus H&B, RKE3964R, or Printer (for BO SER variables only).
Software Manual
If the amount of memory available allows it, the variable is allocated
to the selected channel. The relative address (compared to the start of
the memory area of the COM channel) is displayed at the bottom of
the left column on the screen.
Relative address In general a variable is automatically allocated to a free address in the

memory area reserved for the channel. The address displayed is
relative to the start address of the reserved memory area.
Figure 4-37 Allocation to a communication module (location 'COM')
Scaling values The range of an analog input value can be determined from the
bottom and top scale values. These values contain the bottom and top
scale values. If the bottom scale value is smaller than the top scale
value, the scaling is positive, else the scaling is negative. This means
that the bottom scale value does not always contain the lowest value
and the top scale does not always contain the highest value.
Software Manual
4.10.4 Automatic Allocation of Variables
Automatic After you have allocated a variable, the following question is

allocation displayed on screen:
Do you want to step through the database to copy this
allocation? (Y/N)
If you answer 'Yes', you can copy the allocation you just made to
other variables of the same type and with the same location that have
not yet been allocated. The next question will then be:
Do you want to confirm the allocation of every variable?
(Y/N)
If you answer 'No', the allocation will automatically be copied to
every suitable unallocated variable found. If you answer 'Yes', FSC
Navigator will display every unallocated variable it finds and will ask
for confirmation.
For variables of type BI and BO you may change the register type of
the variables selected for copying, because the address depends on the
register type.
For variables connected to FSC-FSC channels, each relative address
can be entered either manually or automatically. The following
question will be displayed on screen:
Allocate all variables automatically? (Y/N)
If you answer 'Yes', the address is allocated automatically. Otherwise
you can edit the relative address of each variable manually.
You can interrupt the copying process at any time by pressing <Esc>.
4.10.5 Automatic Allocation of SER Sequence Numbers
SER sequence If you activate numerical SER, SER sequence numbers must be
numbers allocated for variables that are SER enabled. You have the option of
allocating SER sequence numbers for variables that are SER-enabled,
but do not yet have an SER sequence number.
This option can, for example, be used in the following situations:
• The SER sequence range changes. SER sequence numbers falling
out of the range will then be deallocated.
• SER has been enabled for a lot of variables and the user activates
numerical SER.
Software Manual
The option is activated if the SER sequence number is assigned for a
variable. The following question is then displayed on screen:
Do you want to step through the database to allocate
sequence numbers? (Y/N)
If you answer 'Yes', FSC Navigator will scan the variable database for
variables that are SER-enabled, but do not yet have a sequence
number. If no such variables are found, the following message will be
displayed on screen:
No more unallocated SER sequence numbers.
If such variables are found, the following question will be displayed:
Allocate all sequence numbers automatically? (Y/N)
If you answer 'Yes', the sequence numbers are allocated automatically.
FSC Navigator will then run through the variable database to allocate
SER sequence numbers. If the area for SER sequence numbers is full,
automatic allocation is aborted, and the following message is
displayed:
Area for SER sequence numbers is full.
If the automatic SER sequence allocation has been completed
successfully, the following message is displayed:
If no automatic allocation is requested, FSC Navigator searches for

the first unallocated SER sequence number and allows you to enter a
sequence number manually. A free sequence number is already
displayed by default. You can accept this sequence number or you can
enter another (unused) number. After you have entered a sequence
number, FSC Navigator searches for the next unallocated SER
sequence number. If no unallocated SER sequence numbers are
available, the following message will be displayed:
FSC Navigator will always return to the variable where the automatic
allocation of SER sequence numbers was started.
You can interrupt the allocation process at any time by pressing

<Esc>.
Software Manual
4.10.6 Reviewing Allocations using the <F2> Function Key
Reviewing FSC Navigator offers a very useful feature that allows you to review
allocations all signal allocations to the modules in the FSC cabinet rack(s). You
can call up this feature by pressing <F2> in any of the hardware
specification screens (e.g. Figure 4-34 on page 4-98). You can call up
any of the following overviews:
• All I/O signal allocations in the system (see page 4-107).
• All SER sequence number allocations in the system
(see page 4-109).
• All DCS address allocations in the system (see page 4-110).
• All communication signal allocations in the system
(see page 4-111).
The allocation overview window that will be displayed depends on the

type of variable (as defined by its location) and the position of the
cursor. Table 4-25 below lists the various possibilities.
Table 4-25 Various allocation overview windows called by <F2>

Screen Variable type Cursor position Allocation overview
(defined by location) window displayed
I/O signal allocation Anything but 'COM' Not in SER sequence All I/O signal
(e.g. Figure 4-34 on or 'FSC'. number field or DCS allocations
page 4-98) address field. (see page 4-107).
I/O signal allocation Any. In SER sequence All SER sequence

(e.g. Figure 4-34 on number field. number allocations
page 4-98) (see page 4-109.
I/O signal allocation Any. In DCS address field. All DCS address
(e.g. Figure 4-34 on allocations
page 4-98) (see page 4-110).
I/O signal allocation 'COM' or 'FSC'. Not in SER sequence All communication
(e.g. Figure 4-37 on number field or DCS signal allocations
page 4-103) address field. (see page 4-111).
Variable selection — Anywhere. All I/O signal

(see Figure 4-33 on allocations
page 4-94) (see page 4-107).
Software Manual
I/O allocations To display a window that lists all I/O signal allocations in the system,
press <F2> in the I/O signal allocation screen (e.g. Figure 4-34 on
page 4-98). Please note that the following conditions must be met:
• The current variable is a non-communication variable
(i.e. its location is not 'COM' or 'FSC').
• The cursor is not positioned in the SER sequence number field,
to the right of SER enable (sequence).
• The cursor is not positioned in the DCS address field.
Note:
This list is also displayed if you press <F2> in the variable
selection screen (see Figure 4-33 on page 4-94).
The following screen will be displayed:
Figure 4-38 Reviewing I/O signal allocations
Software Manual
This screen lists which variables have been allocated to which
channels of the modules in the rack. The allocation list specifies the
type and tag number of the allocated variable. The module whose
signal allocations are shown is displayed highlighted (blue by default).
The example shown in Figure 4-38 lists the signal allocations for the
10209 output module that is located on position 15 of rack 4. You can
press <Esc> to close the window and return to the I/O signal
allocation screen.
Browsing through To browse through the module positions within a rack, make sure that
rack positions the cursor is located in the 'Position' field, and press <PgUp> or
<PgDn>. You can use the left and right arrow keys to move between
the 'Position' field and the 'Rack' field.
Every time you press a key, the screen is refreshed to show the signal
allocations of the current module. If you have reached the last position
of a rack and you press <PgDn>, you will go to the first position of the
next rack. If you have reached the first position of a rack and you
press <PgUp>, you will go to the last position of the next rack.
Browsing through To browse through the available racks, make sure that the cursor is
racks located in the 'Rack' field, and press <PgUp> or <PgDn>. You can
use the left and right arrow keys to move between the 'Position' field
and the 'Rack' field. If you press <PgUp> or <PgDn>, you will move
to the first position of the previous or next rack, respectively.
If you have reached the last rack and you press <PgDn>, you will go
to the first position of the first rack. If you have reached the first rack
and you press <PgUp>, you will go to the first position of the last
rack.
Software Manual
SER allocations To display a window that lists all SER sequence number allocations
in the system, press <F2> in the I/O signal allocation screen (e.g.
Figure 4-34 on page 4-98). Please note that the cursor must be
positioned in the SER sequence number field, to the right of SER
enable (sequence).
The screen as shown in Figure 4-39 will be displayed. This screen lists
which SER sequence numbers have been allocated to which variables
in the system. The variables are specified by their type and tag
number.
If the list contains more than 16 variables, you can use <PgUp> and
<PgDn> to browse through the list. There will then also be an SER
Number field at the bottom of the list, which you can use to quickly
jump to a particular SER number (or, if the SER number you entered
does not exist, to the number closest to it). Press <Esc> to close the
window and return to the I/O signal allocation screen.
Figure 4-39 Reviewing SER signal allocations
Software Manual
DCS allocations To display a window that lists all DCS address allocations in the
system, press <F2> in the I/O signal allocation screen (e.g. Figure
4-34 on page 4-98). Please note that the cursor must be positioned in
the DCS address field.
The screen as shown in Figure 4-40 will be displayed. This screen lists
which DCS addresses have been allocated to which variables in the
system. The variables are specified by their type and tag number.
If the list contains more than 16 variables, you can use <PgUp> and
<PgDn> to browse through the list. There will then also be a DCS
address field at the bottom of the list, which you can use to quickly
jump to a particular DCS address (or, if the DCS address you entered
does not exist, to the number closest to it). Press <Esc> to close the
window and return to the I/O signal allocation screen.
Figure 4-40 Reviewing DCS signal allocations
Software Manual
Communication To display a window that lists all communication signal allocations in
allocations the system, press <F2> in the I/O signal allocation screen (e.g. Figure
4-34 on page 4-98). Please note that the following conditions must be
met:
• The current variable is a communication variable
(i.e. its location is 'COM' or 'FSC').
• The cursor is not positioned in the SER sequence number field,
to the right of SER enable (sequence).
• The cursor is not positioned in the DCS address field.
The following screen will be displayed:
Figure 4-41 Reviewing communication signal allocations
This screen shows which communication channels have been defined

in the system and which variables have been allocated to them. The
screen lists the communication channel parameters:
• Location of the communication channel (CP, COM module and
channel),
• Rack position of the communication module,
Software Manual
• Communication protocol for the specified channel, and
• The reserved memory areas for the specified channel.
You can use <PgUp> and <PgDn> to browse through the available
communication channels.
One of the marker byte or register byte numbers will be displayed

highlighted (blue by default), depending on the signal type of the
current variable. If you then press <Enter>, a popup window will
appear which shows the memory bytes that the current variable has
been allocated to. For each byte of the reserved memory, the list
specifies which variable has been allocated to it (see Figure 4-42).
This allows you to check the memory usage, and increase the reserved
memory areas, if required.
Figure 4-42 Reviewing address allocations
Software Manual
4.11 Configuration of Digital Input Signals (I)
Digital inputs (I) There are several kinds of inputs, depending on their location:
− Location = 'COM': The input is received via a non-FSC
communication channel.
− Location = 'FSC': The input is received from another FSC
system.
− Location = 'ANN': The input is an annunciator control input.
− Location = 'SYS': The input is a system variable.
− Other locations: The input is a normal digital input.
4.11.1 Location = 'COM'
Figure 4-43 Hardware specification: digital inputs (location 'COM')
Software Manual
Safety-related This field cannot be modified. It will always be set to 'No'.
Force enable Press <Space> to set the force-enable status.
Write enable This field cannot be modified. It will always be set to 'Yes'.
SER enable (sequence) Press <Space> to set the SER-enable status.

If SER is enabled and an SER sequence range has been specified, an
SER sequence number must be entered. Any unique number between
the SER base and SER maximum of the primary or secondary SER
channel can be entered as the SER sequence number. The default is
the first free sequence number. You can accept this default, or you can
choose the enter a different number. Use the right and left arrow keys
(← and →) to switch between the SER-enable status and SER
sequence number.
Fault reaction This field can only be modified for non safety-related signals that
have been allocated to fail-safe modules. It defines what the signal
value should become in case of a fault. If the safety relation is set to
'Yes', the fault reaction field is automatically set to 'Low'. If the safety
relation is set to 'No', the fault reaction field can be set to either 'Scan'
or 'Hold'. 'Scan' means that the signal value remains to be scanned
even after a fault, whereas 'Hold' means it will get the last valid value
that was detected.
If the signal is safety-related, the field value is 'N.a.' (not applicable),
and cannot be changed.
Power-up status Press <Space> to set the power-up status. If this field is set to 'On',
the input is set to '1' after power-up. If it is set to 'Off', the input is set
to '0' after power-up. The default value is 'Off'.
Central Part Press <Space> to select the Central Part.
Communication
module Press <Space> to select the communication module.
Channel Press <Space> to select the channel.
Relative address If you have chosen to allocate the addresses automatically, this
address is calculated by FSC Navigator, otherwise you must enter it
manually.
Software Manual
DCS address Enter the unique identification used for accessing the attributes of this
variable. Enter '-1' to deallocate the address. The address range
depends on the DCS that is used:
− UCN (TPS): 1 to 65534
− PlantScape: 1 to 8192
been configured.
Software Manual
4.11.2 Location = 'FSC'
For more information refer to Appendix F of this manual

("Communication").
Figure 4-44 Hardware specification: digital inputs (location 'FSC')
Safety-related Press <Space> to set the safety relation.

Write enable This field cannot be modified. It will always be set to 'No'.

Software Manual
sequence number.
or 'Hold'. 'Scan' means that the signal value remains to be scanned,
even after a fault, whereas 'Hold' means it gets the last valid value
that was detected.
the input is set to '1' after power-up. If it is set to 'Off', the input is set
to '0' after power-up. The default value is 'Off'.
System number Select the system number in the window that appears on screen. The
highlighted number is the selected system number. With the cursor on
a highlighted number, press <S> to (re)select the system or <D> to
deallocate the system.
manually.
− UCN (TPS): 1 to 65534
been configured.
Software Manual
4.11.3 Location = 'ANN'
For more information refer to Appendix A of this manual ("Alarm

Functions").
Figure 4-45 Hardware specification: digital inputs (location 'ANN')

Software Manual
sequence number.
that was detected.
Alarm group Press <S> to select the alarm group. If you press <D>, the variable
will be deallocated from the alarm group.
Alarm type Press <Space> to select the alarm type. The available alarm types
depend on the alarm sequence of the alarm group the input is
connected to. Every alarm type can only be selected once per alarm
group.
Relative address The relative address is always calculated automatically.
Software Manual
4.11.4 Location = 'SYS'
Figure 4-46 Hardware specification: digital inputs (location 'SYS')
Safety-related This field cannot be modified. It will always be set to 'Yes'.
Force enable This field cannot be modified. It will always be set to 'No'.

sequence number.
Software Manual
that was detected.
− UCN (TPS): 1 to 65534
been configured.
Software Manual
4.11.5 Other Locations
Figure 4-47 Hardware specification: digital inputs (other locations)
Write enable This field cannot be modified. It will always be set to 'No'

sequence number.
Software Manual
that was detected.
Rack Enter the rack number which the variable will be allocated to.
Position Enter the position in the rack which the variable will be allocated to.
Channel Enter the channel number of the module which the variable will be
allocated to.
− UCN (TPS): 1 to 65534
been configured.
Sensor is fail-safe Press <Space> to set the fail-safe status, which defines whether the
sensor goes to a defined state (0 or OFF) in case of a sensor failure.
This field can only be modified if the variable is safety-related.
If the sensor is non fail-safe, define the type of redundancy required.

For more information refer to Appendix C of this manual
("Safety-Related Inputs with Non Fail-Safe Sensors").
Sensor is redundant If a sensor is not fail-safe, a redundancy type can be selected.

Redundancy is used to increase the reliability of the data which is
read. Depending on the redundancy type selected, more channels may
need to be allocated to the variable. The possible redundancy types
depend on the VBD function of the VBD controlling the rack.
Press <Space> to set the redundancy type.
Max. discrepancy time Enter the maximum discrepancy time. The value must be in the range
1 to 2047 seconds. The default value is 10 seconds.
Software Manual
Maximum on-time The inputs of redundant sensors need to switch within a certain time
period, and that is why you need to specify the maximum time that
the inputs of redundant input sensors may be active. It is also possible
to deactivate the maximum on-time altogether, which means that the
inputs of redundant input sensors may be active for an indefinite
period of time.
The value must be in the range of 10 to 122820 seconds (2047
minutes). The default value is 28800 seconds (= 8 hours). Press <D>
to deactivate the maximum on-time.
Note:
If the value you entered is greater than 2047, the value is
converted and stored in minutes. As a result, the stored value
may differ slightly from the value entered.
Second and third input Enter the second and third input rack, position and channel
rack, position and (depending on the redundancy type).
channel
Software Manual
4.12 Configuration of Analog Input Signals (AI)
10105/2/1 module If one or more high-density analog input modules 10105/2/1 have
been defined, you need to define the voltage-monitoring settings for
each of these modules.
This is done in the screen as shown in Figure 4-48. Please note that
the tag number and allocation are predefined. The tag number consists
of 'VM'+rack+position+channel. The rack, position and channel are
automatically derived from allocation data that was entered earlier for
the 10105/2/1 module.
Figure 4-48 Hardware specification: analog inputs (voltage

monitoring for 10105/2/1)
Software Manual

sequence number.
'Yes', the fault reaction field is automatically set to 'Bottom scale'. If
the safety relation is set to 'No', the fault reaction field can be set to
either 'Scan' or 'Hold'. 'Scan' means that the signal value remains to be
scanned, even after a fault, whereas 'Hold' means it gets the last valid
value that was detected.
Signal type This field cannot be modified. It will always be set to '0..5 V'.
Trm. Alarm setp. Low You must enter the minimum and the maximum alarm values. If the
Trm. Alarm setp. High analog input goes below the minimum setpoint or exceeds the
maximum setpoint, the system will give an analog sensor break
alarm. You can press <D> to deactivate each setpoint, which means
that no alarms is generated in case of an analog sensor break.
Engineering units Enter the units of measurements for this variable. You can enter a
maximum of 5 characters.
Bottom scale Enter the lowest possible value (in engineering units) of the variable
that is measured.
Top scale Enter the highest possible value (in engineering units) of the variable
that is measured.
Software Manual
SER setpoint low If the 'SER enable' field has been set to 'Yes', you can specify the
SER setpoint low. As soon as the analog input goes below this value,
an SER message will be generated. The default is the bottom scale.
SER setpoint high If the 'SER enable' field has been set to 'Yes', you can specify the
SER setpoint high. As soon as the analog input exceeds this value, an
SER message will be generated. The default is the top scale.
Rack This field cannot be modified.
Position This field cannot be modified.
Channel This field cannot be modified.
− UCN (TPS): 1 to 65534
been configured.
Software Manual
Figure 4-49 Hardware specification: analog inputs

sequence number.
Software Manual
'Yes', the fault reaction field is automatically set to 'Bottom scale'. If
the safety relation is set to 'No', the fault reaction field can be set to
either 'Scan' or 'Hold'. 'Scan' means that the signal value remains to be
scanned, even after a fault, whereas 'Hold' means it gets the last valid
value that was detected.
Signal type Press <Space> to select the signal type that matches your
configuration.
Trm. alarm setp. low The minimum and the maximum alarm value must be entered. If the
and Trm. Alarm setp. analog input goes below the minimum setpoint or the analog input
high
goes above the maximum setpoint, the system will give an analog
sensor break alarm. You can press <D> to deactivate each, which
means that no alarms is generated in case of an analog sensor break.
Engineering units Enter the units of measurements for this variable. You can enter a
maximum of 5 characters.
Bottom scale Enter the lowest possible value (in engineering units) of the variable
that is measured.
Top scale Enter the highest possible value (in engineering units) of the variable
that is measured.
SER setpoint low. As soon as the analog input goes below this value,
an SER message will be generated. The default is the bottom scale.
SER setpoint high. As soon as the analog input exceeds this value, an
SER message will be generated. The default is the top scale.
allocated to.
Software Manual
Sensor is fail-safe Press <Space> to set the fail-safe status, which defines whether the
sensor goes to a defined state (0 or OFF) in case of a sensor failure.
This field can only be modified if the variable is safety-related.
− UCN (TPS): 1 to 65534
been configured.
If the sensor is non fail-safe, define the type of redundancy required.

For more information refer to Appendix C of this manual
("Safety-Related Inputs with Non Fail-Safe Sensors").
Sensor is redundant If a sensor is not fail-safe, a redundancy type can be selected.

Redundancy is used to increase the reliability of the data which is
read. Depending on the redundancy type selected, more channels may
need to be allocated to the variable. The possible redundancy types
depend on the VBD function of the VBD controlling the rack.
Press <Space> to set the redundancy type.
Max. discrepancy Enter the maximum discrepancy value between redundant analog
value inputs. This is the maximum difference between all redundant input
sensors of an analog variable. It is necessary to determine if the
sensor is still functioning correctly. The maximum is 10% of the span
of the analog input, and the minimum is 0.1 % of the span.
Software Manual
4.13 Configuration of Binary Input Signals (BI)
Binary inputs (BI) The variable type BI can have four different kinds of hardware
specifications, depending on the location:
− Location = 'COM': The BI variable is received via a non-FSC
− Location = 'FSC': The BI variable is received from another FSC
system.
− Location = 'MUX': The BI variable is part of multiplexed I/O.
− Other locations: The BI variable is a binary input, but is not
part of multiplexed I/O.
Figure 4-50 Hardware specification: binary inputs (location 'COM')
Software Manual
Write enable This field cannot be modified. It will always be set to 'Yes'.
SER enable This field cannot be modified. It will always be set to 'No'.
Register type Press <Space> to select the register type (Byte, Word, Long, or
Float). If the register type is changed, the power-up value may
automatically be adjusted to the maximum value of that register type.
Power-up value This field specifies the value that the register will take when the FSC
system is switched on (e.g. after a power-up). The range of this value
depends on the register type. The default value is 0.
Communication
manually.
− UCN (TPS): 1 to 65534
been configured.
Note:
For PlantScape, a DCS address can be allocated to BI and BO
variables of register types Byte, Word, Long, and Float.
For TPS (UCN), a DCS address can only be allocated to BI and
BO variables of register type Float.
Software Manual

("Communication").
Figure 4-51 Hardware specification: binary inputs (location 'FSC')
Software Manual
manually.
− UCN (TPS): 1 to 65534
been configured.
Note:
Software Manual
4.13.3 Location = 'MUX'
For more information refer to Appendix G of this manual ("FSC

Multiplexers").
Figure 4-52 Hardware specification: binary inputs (location 'MUX')
Mux tag number Press <S> to select an XI variable from a list. If you press <D>, the
selected XI will be deallocated.
Data representation Press <Space> to select binary representation or BCD representation.
Software Manual
Number of input bits Enter the number of bits of the variable. This value should be in the
range of 1 to 32 bits.
Register type This field cannot be changed. Its value depends on the number of
input bits.
Selection output rack Enter the rack number which the variable will be allocated to.
Selection output pos. Enter the position in the rack which the variable will be allocated to.
Make sure that you allocate a BI variable with location 'MUX' to
output modules.
Selection output chn. Enter the first channel number of the module which the variable will
be allocated to.
2nd, 3rd and 4th If it is not possible to allocate all selection output bits on the module
selection output rack defined by the position fields, then one or more extra modules need to
and output position
be defined to allocate the remaining bits.
Software Manual
Figure 4-53 Hardware specification: binary inputs (other locations)
input bits.
Software Manual
Channel Enter the first channel number of the module which the variable will
be allocated to.
Second, third and If it is not possible to allocate all selection output bits on the module
fourth input rack and defined by the position fields, then one or more extra modules need to
input position
Software Manual
4.14 Configuration of Multiplexer Inputs (XI)

Multiplexers").
Figure 4-54 Hardware specification: multiplexer inputs
Mux tag number This field cannot be modified. The MUX tag number is automatically
allocated.
Software Manual
Scan time Enter the scan time. This is the time in which all connected BI
variables should be read. It should be in the range of 100 to 60000
milliseconds (= 0.1 second to 1 minute). The minimum must be
greater than the application time. If an application has not yet been
translated, the minimum scan time will be 100 ms for systems with
only one Central Part and 200 ms for systems with multiple Central
Parts.
Debounce Press <Space> to set the debounce value. If the debounce value is set
to 'Yes', the value which is read will be compared to the last value
read. If these values are equal, the last value will be transferred to the
application program.
Sel OUT active time Enter the select output active time. This is the time during which the
select output should be true before the data is valid. The select output
active time must be greater than twice the delay time of the inputs on
the module which the XI variable has been allocated to. If the XI has
not yet been allocated, the minimum select output active time is 2 ms.
The maximum time is 100 ms. The delay times of the various digital
input modules are as follows:
10101/1/1: 20 ms 10103/1/2: 1 ms
10101/1/2: 20 ms 10103/1/1: 1 ms
10101/1/3: 20 ms 10104/1/1: 1 ms
10101/2/1: 20 ms 10104/2/1: 1 ms
10101/2/2: 20 ms
10101/2/3: 20 ms
Data hold time Enter the data hold time. This is the time in which the data stabilizes
on the input multiplexer data bus. It should be in the range of 0 to
100 ms.
Sel OUT active status This field defines the value which is used for the selection outputs. If
the status is 'On', the data of the multiplexed I/O is read from, and
written to, the data path when the selection output is high.
Press <Space> to set the status to 'On' or 'Off'.
MUX data bus status Press <Space> to set the MUX data bus status. The MUX data bus
status can be used to invert the data read from the input multiplexer
data bus. You can choose between 'Inverted' and 'Normal' (i.e. no
inversion).
Software Manual
be allocated to.
Second, third and If it is not possible to allocate all selection input bits on the module
input position
Software Manual
4.15 Configuration of Digital Output Signals (O)
Digital outputs (O) There are several kinds of outputs, depending on their location:
− Location = 'COM': The output is sent via a non-FSC
− Location = 'FSC': The output is sent to another FSC system.
− Location = 'ANN': The output is an annunciator control output.
− Location = 'SYS': The output is a system variable.
− Other locations: The output is a normal digital output.

("Communication").
Figure 4-55 Hardware specification: digital outputs (location 'COM')
Software Manual

sequence number.
the output is set to '1' after power-up. If it is set to 'Off', the output is
set to '0' after power-up. The default value is 'Off'.
Communication
manually.
− UCN (TPS): 1 to 65534
been configured.
Software Manual

("Communication").
Figure 4-56 Hardware specification: digital outputs (location 'FSC')

Software Manual
sequence number.
manually.
− UCN (TPS): 1 to 65534
been configured.
Software Manual
4.15.3 Location = 'ANN'
For more information refer to Appendix A of this manual ("Alarm

Functions")
Figure 4-57 Hardware specification: digital outputs (location 'ANN')
Force enable Press <Space> to set the force-enable status. (Control outputs are
always 'No'.)
SER enable If the alarm type is 'Alarm', this field can be modified by pressing
<Space>. Otherwise it will always be set to 'No', and it cannot be
modified.
Alarm group Press <S> to select the alarm group. If you press <D>, the variable
will be deallocated from the alarm group.
Software Manual
Alarm type Press <Space> to select the alarm type. The available alarm types
depend on the alarm sequence of the alarm group the output is
connected to. Every alarm type can only be selected once per alarm
group. The only exception is alarm type 'Alarm', which is used for the
actual alarm outputs. This alarm type can be selected as many times
as the group size defined for the alarm function. This alarm type is
the only type for which a rack, position and channel need to be
defined.
manually.
− UCN (TPS): 1 to 65534
been configured.
If the alarm type is 'Alarm', the hardware allocation must also be

defined:
allocated to.
Software Manual
There are two kinds of digital outputs with location 'SYS':

• The RKE event triggers for transmitting an RKE block.
• The SER event trigger for printing the value of a BO with location
'COM' or 'FSC'.
Both are generated automatically. Figure 4-58 shows an example of an

SER event trigger of a BO variable with location 'COM' or 'FSC'.
Figure 4-58 SER event trigger of a BO variable with location

'COM' or 'FSC'
Software Manual
The only thing that can be edited is the DCS address:
− UCN (TPS): 1 to 65534
been configured.
Software Manual
Figure 4-59 Hardware specification: digital outputs (other locations)

sequence number.
Software Manual
allocated to.
− UCN (TPS): 1 to 65534
been configured.
Software Manual
4.16 Configuration of Analog Output Signals (AO)
Figure 4-60 Hardware specification: analog outputs

sequence number.
Software Manual
Signal type Press <Space> to select the signal type that matches your
configuration.
Engineering units Enter the units of measurements of the controlling variable. You can
enter a maximum of 5 characters.
Bottom scale Enter the lowest possible value (in engineering units) of the
controlling variable.
Top scale Enter the highest possible value (in engineering units) of the
controlling variable.
SER setpoint low. As soon as the analog output goes below this
value, an SER message will be generated. The default is the bottom
scale.
SER setpoint high. As soon as the analog output exceeds this value,
an SER message will be generated. The default is the top scale.
allocated to.
− UCN (TPS): 1 to 65534
been configured.
Software Manual
4.17 Configuration of Binary Output Signals (BO)
Binary outputs (BO) The variable type BO can have four different kinds of hardware
specifications, depending on the location:
− Location = 'COM': The BO variable is sent via a non-FSC
− Location = 'FSC': The BO variable is sent to another FSC
system.
− Location = 'MUX': The BO variable is part of multiplexed I/O.
− Other locations: The BO variable is a binary output, but is not
part of multiplexed I/O.
Figure 4-61 Hardware specification: binary outputs (location 'COM')
Software Manual

sequence number.
Communication
manually.
Engineering units If the 'SER enable' field has been set to 'Yes', the engineering units
can be entered (max. 5 characters). These units can be printed in the
SER message.
− UCN (TPS): 1 to 65534
been configured.
Software Manual
Note:
Software Manual

("Communication").
Figure 4-62 Hardware specification: binary outputs (location 'FSC')

Software Manual
sequence number.
a highlighted number, press <S> to select the system or <D> to
manually.
Engineering units If the 'SER enable' field has been set to 'Yes', the engineering units
can be entered (max. 5 characters). These units can be printed in the
SER message.
− UCN (TPS): 1 to 65534
been configured.
Note:
Software Manual
4.17.3 Location = 'MUX'

Multiplexers").
Figure 4-63 Hardware specification: binary outputs (location 'MUX')
Mux tag number Press <S> to select an XI variable from a list. If you press <D>, the
selected XI will be deallocated.
Software Manual
Number of output bits Enter the number of bits of the variable. This value should be in the
Blank code This field can only be modified if BCD representation has been
selected. The blank code is used to clear part of the variable on a
BCD display. The default is 0, which means there is no blanking.
This field cannot be modified if the number of output bits is larger
than 0.
Selection output rack Enter the rack number which the variable will be allocated to.
Selection output
position Enter the position in the rack which the variable will be allocated to.
Selection output Enter the first channel number of the module which the variable will
channel be allocated to.
2nd, 3rd and 4th If it is not possible to allocate all selection output bits on the module
selection output rack defined by the position fields, then one or more extra modules need to
and output position
Software Manual
Figure 4-64 Hardware specification: binary outputs (other locations)
Software Manual
Blank code This field can only be modified if BCD representation has been
selected. The blank code is used to clear part of the variable on a
BCD display. The default is 0, which means there is no blanking.
output bits.
allocated to.
fourth output rack and defined by the position fields, then one or more extra modules need to
output position
Software Manual
4.18 Configuration of Multiplexer Outputs (XO)

Multiplexers").
Figure 4-65 Hardware specification: multiplexer outputs
Mux tag number This field cannot be modified. The MUX tag number is automatically
allocated.
Software Manual
Scan time Enter the scan time. This is the time in which all connected BO
variables should be written. It should be in the range of 100 to 60000
milliseconds (= 0.1 second to 1 minute).
Data setup time Enter the data setup time. This time should be in the range from 0 to
100 ms. The data setup time is the time which the data lines should
have the correct data status before the select output will be activated.
Sel OUT active time Enter the select output active time. This is the time during which the
select output should be true before the data is valid. It should be in
the range of 1 to 100 ms.
Data hold time Enter the data hold time. This is the time in which the data must stay
active after the select output is deactivated. It should be in the range
of 1 to 100 ms.
Sel OUT active status This field defines the value which is used for the selection outputs. If
the status is 'On', the data of the multiplexed I/O is read from, and
written to, the data path when the selection output is high.
Press <Space> to set the status to 'On' or 'Off'.
MUX data bus status Press <Space> to set the MUX data bus status. The MUX data bus
status can be used to invert the data. You can choose between
'Inverted' and 'Normal' (i.e. no inversion).
be allocated to.
input position
Software Manual
4.19 Configuration of Markers (M)
Figure 4-66 Hardware specification: markers

Markers can only be forced for on-sheet references. Markers used in a
sheet or off-sheet references cannot be forced.
Write enable Press <Space> to set the write-enable status.

The write-enable status of on/off-sheet references cannot be modified.
It will then always be set to 'No'.

Software Manual
sequence number.
the marker is set to '1' after power-up. If it is set to 'Off', the marker is
FLD(s) This field cannot be modified. It lists the destination FLD of a

reference between two or more FLDs.
Software Manual
4.20 Configuration of Counters (C)
Figure 4-67 Hardware specification: counters

sequence number.
Software Manual
Maximum counter This is the maximum value that the counter can reach after
value subsequent count-up pulses. After this value has been reached, the
counter automatically resets to 0.
Power-up value This field specifies the value that the counter will take when the FSC
system is switched on (e.g. after a power-up). The value should be in
the range of 0 to the maximum counter value. The default value is 0.
FLD(s) This is the FLD where the counter is placed.
Software Manual
4.21 Configuration of Timers (T)
Figure 4-68 Hardware specification: timers

sequence number.
Software Manual
Timer type This field defines the timer function type. If no type has been
specified, this field will contain the value 'None'. There are basically
two types of timers:
1. Timers whose timer value depends on the application program.
2. Timers with constant time values as defined in the FLDs. This
type of timer are indicated by the added '2' to the timer type (see
Figure 4-68).
The following timer types are supported:

− Pulse: Pulse time function on rising edge of the timer input.
− Pulse R: Pulse time function on rising edge of the timer input.
The time is restarted after every rising edge.
− Del ON: Delay On time function on rising edge of the timer
input.
− Del ON M: Delay On time function on rising edge of the timer
input. The timer continues to count even if the time
input goes to zero state.
− Del OFF: Delay Off function on falling edge of the timer
input.
Timer base This can be 100 milliseconds (100 mS), 1 second (1 S), or 1 minute
(1 M). The timer base is the period in which the timer is counted
down by one.
Timer value This is the multiplier value for the time base. This value has a range
of 0 to 2047. Please note that this value is not necessarily the same as
the value that you initially entered in the functional logic diagram
(FLD). Depending on the timer value you entered in the FLD, the
time base of the timer may be changed in order to optimize the timer
resolution. For details refer to subsection 6.8.5 of this manual.
DCS address This field is only available for pulse retriggerable timers (Pulse R)
with variable time value. It specifies the unique identification that
TPS (UCN) uses for accessing the attributes of this variable. The
address range is between 1 and 65534. Enter '-1' to deallocate the
address. Please note that PlantScape does not support this timer.
Note:
The timer type, timer base and timer value cannot be changed
using the 'System Configuration' option of FSC Navigator. If
you want to change any of these parameters, you should use the
FLD design editor.
Software Manual
4.22 Configuration of Registers (R)
Figure 4-69 Hardware specification: registers

The write-enable status of off-sheet references cannot be modified.
It will then always be set to 'No'.
Register type This field cannot be modified here.
This field can only be modified if the address is ≤ 7000.
Software Manual
Note:
Registers are also used for off-sheet references.
Software Manual
4.23 Configuration of PIDs (P)
For more information refer to Appendix E of this manual ("PID

Controllers").
Figure 4-70 Hardware specification: PIDs
PID number This field cannot be modified. The PID number is automatically
generated and is for internal use only. The maximum number of PID
functions is 64.
Sample time Enter the sample time. This is the time between two samples. It has a
range of 0.1 to 204.7 seconds.
Software Manual
Power-on mode This field specifies the power-on mode which is used for the PIDs in
the FSC system. There are four options:
• Auto: The output is calculated each sample time, from of the
difference between the input and the setpoint in
accordance with the setup of the parameters.
• Manual: Only the output can be entered. This value is copied
to the PID output and is not a calculated value.
• Test: In this mode, the input (a virtual input) and the
setpoint (virtual setpoint) can be entered. The output
is calculated using these values. This option can be
used to check the PID function.
• Cascade: The PID will act as a slave, and is controlled by another
master slave (chain) or a master PID in Auto mode.
Proportional band This field specifies the change (as a percentage) in the difference
between the setpoint and the input for doubling the output. The value
may not be 0.
Reset factor The reset factor defines the number of times per minute in which the
integration is calculated. It must be larger than 0 rep/min.
Rate time The rate time is the time period over which the differentiations are
made discrete. It has a range of 0 to 3276.7 seconds.
Engineering units Enter the units of measurement of the input and output of the PID
(two fields). You can enter a maximum of 5 characters.
Bottom scale Enter the lowest possible value (in engineering units) of the input and
output of the PID (two fields).
Top scale Enter the highest possible value (in engineering units) of the input
and output of the PID (two fields).
PID deviation limit This is the high clamp for the difference between the PID input and
PID analog setpoint (in engineering input units). Please note that
control will not be correct if this parameter is set to '0' (zero). The
deviation limit must exceed 1% of the input range.
PID analog output The field defines the minimum value of the PID analog output (in
low clamp engineering units). The analog output will never become smaller than
this value.
Software Manual
PID analog output The field defines the maximum value of the PID analog output (in
high clamp engineering units). The analog output will never exceed this value.
PID setpoint The field defines the minimum value of the PID setpoint (in
low clamp engineering units). The setpoint will never become smaller than this
value.
PID setpoint The field defines the maximum value of the PID setpoint (in
high clamp engineering units). The setpoint will never exceed this value.
Cascade input If the PID is in cascade mode and the current PID is the slave, this
field should be set to 'Yes'. Otherwise it should be set to 'No'. Use
<Space> to toggle.
If the PID is used in cascade, the tag number of the cascade input, the
master PID, needs to be defined.
Tag number If the PID is in cascade mode, this field must contain the tag number
of the master PID.
Software Manual
4.24 Configuration of Alarms (A)
Alarms For more information refer to Appendix A of this manual ("Alarm

Functions").
Figure 4-71 Hardware specification: alarms (A)
Alarm group This field cannot be modified. The alarm group number is
automatically generated. The maximum number of alarm groups
is 64.
Software Manual
Alarm sequence This field defines the alarm sequence type. Press <Space> to select
the alarm sequence. The available options are:
− AF Basic flashing
− AM Manual lamp reset
− FR Flasher reset
− FRM Flasher / lamp reset
− AR Ringback
− ARR Double audible ringback
− TFS First out indication
− TFS_COM1 First out indication transmitter FSC system.
− TFS_COM2 First out indication receiver FSC system.
Note:
The alarm sequences supported by FSC are a subset of the
annunciator sequences specified by the ISA S18.1 standard.
Group size This field specifies the number of digital outputs with location 'ANN'
and the alarm type 'Alarm' that can be connected to the alarm.
The minimum group size is 8, the maximum group size is 256.
Start address markers Memory is allocated in the marker area for each alarm group. Inputs
and outputs connected to the alarm are allocated within this area. This
field specifies the start address of the allocated memory area. It is
generated automatically and cannot be modified. The number of
markers allocated depends on the selected alarm sequence and the
alarm group size.
Software Manual
4.25 Rebuilding an Application
Rebuilding an Sometimes it is useful to rebuild the databases of an application.

application There are two types of rebuilds:
• Off-line rebuilds, and
• On-line rebuilds.
Each of these is discussed on more detail below.
4.25.1 Off-Line Rebuilds
Off-line rebuilds Off-line rebuilds (i.e. without communication with the FSC system)
can be used to:
• check the integrity of the databases,
• clear and compact the databases, and
• repair a corrupted database.
To rebuild the databases off-line, choose the 'Rebuild' option from the
System Configuration main menu. The procedure that will be
followed depends on the status of the on-line modification (OLM)
option (see subsection 4.5.13).
OLM option = 'Yes' If the on-line modification option has been set to 'Yes', you will first
be asked whether you really want to rebuild the databases:
Do you want to rebuild the databases? (Y/N)
If you answer 'Yes', you are asked whether you want to rebuild
on-line:
Do you want to rebuild on-line ? (Y/N)
Answer 'No'. FSC Navigator will then not attempt to establish
communication with the FSC system. Before the actual rebuild
process will start, you are first asked to confirm the rebuild:
Are you sure? (Y/N)
If you answer 'Yes', the rebuild process will start.
Software Manual
OLM option = 'No' If the on-line modification option has been set to 'Yes', you will first
be asked whether you really want to rebuild the databases:
Do you want to rebuild the databases? (Y/N)
If you answer 'Yes', you are asked whether you want to rebuild
on-line:
Do you want to rebuild on-line ? (Y/N)
Answer 'No'. FSC Navigator will then not attempt to establish
communication with the FSC system. The next question will be:
Do you want to change the address allocation? (Y/N)
If you answer 'No', the address allocation remains the same and only
the index files are rebuilt. If you answer 'Yes', the address allocations
are changed as well.
Before the actual rebuild process will start, you are first asked to
confirm the rebuild:
Are you sure? (Y/N)
If you answer 'Yes', the rebuild process will start.
4.25.2 On-Line Rebuilds
On-line rebuilds On-line rebuilds are only possible if the on-line modification (OLM)
option has been activated (see subsection 4.5.13).
When an application is created, variables are allocated to locations in

system memory (see Figure 4-72). If the application is then changed,
variable allocations will change as well. This is partly because of user
interaction (e.g. removal of a variable allocated to a hardware
channel), and partly because of actions by the FSC Navigator
software, e.g. change in the number of internal compiler variables
(feedback markers) required to realize a functional logic diagram.
If the application has been configured for on-line modification, the

allocation of any variable that is deleted from the application is
blocked for further use (Figure 4-72) in order to guarantee application
compatibility with the previous version. As a consequence of this
mechanism, the required amount of system memory will increase,
while the allocated memory becomes more and more fragmented.
Software Manual
Initial application memory allocation memory allocation
memory allocation after modifications after on-line rebuild
Free Allocated Blocked
Figure 4-72 Allocation in variables to locations in system memory
The only way to release blocked allocations is via the 'On-Line

Rebuild' option of FSC Navigator (see Figure 4-73). This option
should only be used if the amount of memory is not enough to
continue design or configuration.
Figure 4-73 On-Line Rebuild option
If you choose this option, you will be asked to confirm the on-line
rebuild:
Are you sure? (Y/N)
If you answer 'Yes', the on-line rebuild process will start.
Considerations Please note the following considerations:

• If a tag number has been changed after translation and programming
EPROMs and the allocation is still the same, the variable will be
deallocated or set to undefined.
• If the allocation of a variable has been changed during on-line
modification, the variable will be reallocated to its previous
allocation.
Software Manual
• If an I/O module has been deleted and all variables on it have been
deallocated, the module as well as the accessory variables will be
reallocated to the rack and position they were allocated to before.
• If the rack of an HBD has been changed (after deleting the I/O
modules), the HBD will be reallocated to the rack it was allocated
to before.
Software Manual
Software Manual
Fail Safe Control
Section 5:
Editing Reports and SER Format
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 5: Editing Reports and SER Format
5.1 Introduction .................................................................................................... 5-1
5.2 Layout Editor .................................................................................................. 5-3
5.3 Reports ........................................................................................................... 5-5

5.3.1 Introduction....................................................................................................................... 5-5
5.3.2 Editing Report Files .......................................................................................................... 5-5
5.3.3 Report Text....................................................................................................................... 5-8
5.3.4 Report Header................................................................................................................ 5-11
5.3.5 Time-Based Report Generation ..................................................................................... 5-12
5.3.6 Conditional Report Generation....................................................................................... 5-15
5.3.7 Report Printer Configuration .......................................................................................... 5-17
5.4 SER Format File............................................................................................ 5-20

5.4.1 Introduction..................................................................................................................... 5-20
5.4.2 Editing the SER Format File........................................................................................... 5-20
5.4.3 SER Messages............................................................................................................... 5-22
5.4.4 SER Printer Configuration.............................................................................................. 5-25
5.5 Deleting Files................................................................................................ 5-28
5.6 Default SER Event Format ........................................................................... 5-30

5.6.1 Introduction..................................................................................................................... 5-30
5.6.2 Default SER Header....................................................................................................... 5-30
5.6.3 Default Variable Event Format ....................................................................................... 5-30
5.6.4 Standard SER Messages............................................................................................... 5-34
Software Manual
Section 5: Editing Reports and SER Format i
FIGURES
Figure 5-1 Edit Reports and SER Format: start-up screen .......................................................... 5-2
Figure 5-2 Selecting a report file for editing.................................................................................. 5-6
Figure 5-3 Edit menu for report files ............................................................................................. 5-7
Figure 5-4 Edit menu for report text.............................................................................................. 5-8
Figure 5-5 Edit menu for report header ...................................................................................... 5-11
Figure 5-6 Editing the report frequency ...................................................................................... 5-12
Figure 5-7 Defining the parameters for conditional report generation........................................ 5-15
Figure 5-8 Report printer configuration screen........................................................................... 5-18
Figure 5-9 Edit menu for SER format file.................................................................................... 5-21
Figure 5-10 Edit menu for SER messages ................................................................................... 5-23
Figure 5-11 SER printer configuration screen .............................................................................. 5-25
Figure 5-12 FSCSER format ........................................................................................................ 5-27
Figure 5-13 Delete menu .............................................................................................................. 5-28
TABLES
Table 5-1 Time-based report generation................................................................................... 5-13

Table 5-2 Available conditions for various variable types ......................................................... 5-17
Table 5-3 Supported report printers .......................................................................................... 5-18
Table 5-4 Supported SER printers ............................................................................................ 5-26
Table 5-5 Variable event format ................................................................................................ 5-31
Software Manual
ii Section 5: Editing Reports and SER Format
Section 5 – Editing Reports and SER Format
5.1 Introduction
Overview The 'Edit Reports and SER Format' option of FSC Navigator serves
two purposes:
1. It is used to define the journal of the SER messages.
2. It is used to create the layout for up to 99 reports and to define the
conditions under which each of the reports must be generated by
the FSC system. FSC Navigator provides a screen editor and a
number of other editing features for creating the layouts.
Note:
The 'Edit Reports and SER Format' option of FSC Navigator is
only available if no SER channel has been defined with
numerical SER (see subsection 4.5.4 of this manual). If there is
such a channel and you attempt to start this option anyway, the
following message will be displayed:
Editing reports or SER format not allowed.
After you press <Esc>, you will then return to the FSC
Navigator main screen.
The 'Edit Reports and SER Formats' option of FSC Navigator can be
called by choosing the SER Formats command in the Project menu.
If it is allowed to start this option (see note above), the window as
shown in Figure 5-1 on the next page will appear.
The following options may be available in the main menu:

• Report file
Choose this option to edit a report file. For details refer to
subsection 5.3.
• SER format file
Choose this option to edit an SER format file. For details refer to
subsection 5.4.
• Delete file
Choose this option to delete an existing file. Please note that this
option will only be available if there are any files that can be
deleted. For details refer to subsection 5.5.
• eXit
Choose this option to return to the FSC Navigator main screen.
Software Manual
Section 5: Editing Reports and SER Format 5-1
Figure 5-1 Edit Reports and SER Format: start-up screen
Software Manual
5-2 Section 5: Editing Reports and SER Format
5.2 Layout Editor
Layout editor FSC Navigator provides a layout editor that allows you to define the
message layout of the SER journal and report layouts.
You can enter and manipulate text, and set graphic attributes such as
bold printing, background colors, etc. It is also possible to indicate
where, for example, in the text a date or a page number should be
included in the current SER message or report generated by the FSC
system.
Note:
An empty line is indicated by a dash ('-'). This character is not
inserted into the actual text.
Editing commands The available editing commands are listed below. They are activated
by pressing the key or key combination shown between brackets.
<Ins> or Use this key to switch between insert and overwrite mode. The
<Ctrl>+<V> current mode is displayed in the upper right corner of the screen.
Arrow keys Use the arrow keys (←, →, ↑, ↓) to move around on the screen.
<Enter> SER format header and messages:

If you press <Enter>, the cursor will move to the beginning of the
next line. If the current line is the last line, the cursor will move to the
beginning of the last line.
Report header:
The number of header lines is fixed. If you press <Enter>, the cursor
will move to the beginning of the next line. If the current line is the
last line, the cursor will move to the beginning of the last line.
Report text:
If the cursor is located in report text and you press <Enter>, the
position of the cursor on the line determines what will happen:
− If the cursor is at the beginning of the line, a new line is inserted
above the cursor.
− If the cursor is at the end of the line, a new line is inserted below the
cursor.
− If the cursor is anywhere between the beginning and the end of the
line, a line break will be inserted at the cursor position and anything
right of the cursor will move to the next line.
Software Manual
à>
<Ctrl> + <à Use this key combination to move the cursor to the beginning of the
next word or to the end of the line (if there are no more words on the
line).
ß>
<Ctrl> + <ß Use this key combination to move the cursor to the beginning of the
current word. If the cursor is already at the beginning of a word, or is
in between words, it moves to the beginning of the previous word.
<Home> Use this key to move the cursor to the beginning of the current line.
<End> Use this key to move the cursor to the end of the line (after the last
character).
<Del> Use this key to delete the character at the current cursor position.
<Backspace> Use this key to delete the character left of the current cursor position.
<Ctrl> + <T> Use this key combination to delete all characters from the current
cursor position to the beginning of the next word (including spaces).
<Ctrl> + <Y> Use this key combination to delete an entire line (regardless of the
cursor position on the line).
Software Manual
5.3 Reports
5.3.1 Introduction
Reports Reports can be generated by the FSC system and output to a printer
that is directly connected to the FSC system. The communication
protocol used is the Printer protocol.
Not only abnormal situations may be of interest in a running plant.
You may, for example, also want to print out a daily report that
contains important information about a number of process variables
for evaluation of process efficiency.
FSC Navigator allows you to define a maximum of 99 reports, each of
which is stored in a report file that contains the layout and conditions
of the report.
5.3.2 Editing Report Files
Editing To edit a report file, choose the 'Report file' option from the main
report files menu (see Figure 5-1). You are first asked to enter the number of the
report you wish to edit (see :Figure 5-2 on the next page).
Choosing a report The existing reports are displayed highlighted (blue by default). A
to edit report is stored in the project folder under the name <application
name>.R<report number>, so a report file for the application TEST_1
could be TEST_1.R05. If you enter the number of a report that does
not exist, a new, empty report is created automatically.
After you have selected a report file, the data is read and checked for
invalid data. If the file is found to be corrupted, the following prompt
will appear:
Report is corrupted. Do you want to delete the file? <Y/N>
If you press <Y>, the report will be deleted.
If you press <N>, you will return to the main menu.
If the report file has been successfully verified, the screen as shown in
Figure 5-3 on page 5-7 will appear.
Software Manual
Figure 5-2 Selecting a report file for editing
Edit menu
for reports The following options are available in the edit menu for reports:
Text Use this option to enter and edit the report text. For details refer to
subsection 5.3.3 below.
Header Use this option to enter and edit the report header. For details refer to
subsection 5.3.4 below.
Frequency Use this option to define the frequency with which reports are
generated. It allows you to generate reports on a certain time basis.
For details refer to subsection 5.3.5 below.
Conditions Use this option to define the conditions that should be met for a
report to be generated. For details refer to subsection 5.3.6 below.
Printer config. Use this option to define the configuration of the printer that is used
to output the current report. For details refer to subsection 5.3.7
below.
Software Manual
Main Use this option to return to the main menu (see Figure 5-1).
If the report has been changed, you are first asked whether you wish to
save the changes or discard them.
Figure 5-3 Edit menu for report files
Software Manual
5.3.3 Report Text
Report text If you choose the 'Text' option from the edit menu for report files (see
Figure 5-3), an editor will open (see Figure 5-4 below) which allows
you to enter and edit the report text. Refer to subsection 5.2 for
details on the available editing commands.
Figure 5-4 Edit menu for report text
While inserting text, you can press <Esc> to access an edit menu that
provides a number of special commands:
Graphic This menu option provides access to a submenu that is used to set
graphic attributes of the text. The attributes are valid from the current
cursor position to the end of the line.
If you choose the attribute once more, it is switched off again. Only
valid attributes are displayed. The available attributes are:
− Bold: The text will be shown bold.
− Underline: The text will be underlined (only for printer output).
Software Manual
Color This menu option provides access to a submenu that allows you to set
the foreground colors. This option is only available for color printers.
Date If you choose this option, an indicator will be inserted in the text that
specifies where the current date will be shown in the report. This is
indicated by the dummy text '- date ----------------'. You cannot edit
this text, and the cursor can only be positioned on the first character
of the text.
To remove the date indicator, move the cursor to the first character of
the dummy text, and press <Del>. Alternatively, you can use the
<Backspace> key at the end of the indicator.
Time If you choose this option, an indicator will be inserted in the text that
specifies where the current time will be shown in the report. This is
indicated by the dummy text '- time ----'. You cannot edit this text,
and the cursor can only be positioned on the first character of the text.
To remove the time indicator, move the cursor to the first character of
Page number If you choose this option, an indicator will be inserted in the text that
specifies where the page number will be shown in the report. This is
indicated by the dummy text 'PN'. You cannot edit this text, and the
cursor can only be positioned on the first character of the text.
To remove the page number indicator, move the cursor to the first
character of the dummy text, and press <Del>. Alternatively, you can
use the <Backspace> key at the end of the indicator.
Edit If you choose this option, you will return to the text editor.
Main If you choose this option, you will return to the report editor main
menu.
Special functions There are a number of special functions that allow you to insert tag
numbers, services, values, etc. into the report. They are:
<Alt> + <T> Use this key combination to insert a tag number into the report. A
prompt will appear that asks for the variable type and tag number.
You can use the <?> command to see a list of available variable types
and tag numbers.
You cannot edit the tag number indicator, and the cursor can only be
positioned on the first character of the text. To remove the tag number,
move the cursor to the first character of its indicator, and press <Del>.
Software Manual
Alternatively, you can use the <Backspace> key at the end of the
indicator.
<Alt> + <S> Use this key combination to insert the service of a variable into the
report. A prompt will appear that asks for the variable type and tag
number. You can use the <?> command to see a list of available
variable types and tag numbers.
You cannot edit the service indicator, and the cursor can only be
positioned on the first character of the text. To remove the service,
indicator.
<Alt> + <Q> Use this key combination to insert the qualification of a variable into
the report. A prompt will appear that asks for the variable type and
tag number. You can use the <?> command to see a list of available
You cannot edit the qualification indicator, and the cursor can only be
positioned on the first character of the text. To remove the
qualification, move the cursor to the first character of its indicator, and
press <Del>. Alternatively, you can use the <Backspace> key at the
end of the indicator.
<Alt> + <V> Use this key combination to insert the current value of a variable into
the report. A prompt will appear that asks for the variable type and
tag number. You can use the <?> command to see a list of available
The variable value is indicated by the dummy text '- value --------'.
You cannot edit this indicator, and the cursor can only be positioned
on the first character of the text. To remove the variable value, move
the cursor to the first character of its indicator, and press <Del>.
indication.
Software Manual
5.3.4 Report Header
Report header If you choose the 'Header' option from the edit menu for report files
(see Figure 5-3), an editor will open (see Figure 5-4 below) which
allows you to enter and edit the report header. The report header has a
maximum of four lines. Refer to subsection 5.2 for details on the
available editing commands.
Figure 5-5 Edit menu for report header
provides a number of special commands. The available commands and
their function are the same as for report text (see subsection 5.3.3).
Software Manual
5.3.5 Time-Based Report Generation
Time-based If you choose the 'Frequency' option from the edit menu for report
report generation files (see Figure 5-3), you are first asked whether you wish to
generate the report on a time base. Use <Space> to toggle between
'Yes' and 'No'.
Note:
Time-based report generation is only possible if you have placed
a Diagnostic and Battery Module (DBM) module in the Central
Part.
If you choose to generate the report on a time base, a number of

additional time-related fields appear which specify the frequency with
which the report must be generated (see Figure 5-6).
Defining the The frequency with which a report is generated is determined by the
report frequency values given to the Month, Date, Day, Hour and Minute fields in the
screen shown in Figure 5-6 below.
Figure 5-6 Editing the report frequency

Software Manual
To change the value of a field, use the arrow keys on the keyboard to
move the cursor to the field whose value you wish to change.
The way to edit the field value depends on the field:
• Month: Press space bar to toggle between months.
You can also press <?> to display a popup menu that
lists the months, and use the arrow keys to select the
appropriate value. Press <Enter> to record the changes
(the cursor will move to the next field).
• Date: Press <S> to display a popup menu that lists the dates.
Select the appropriate value or press <A> to select
'Any'. Press <Esc> to record the changes.
Please note that this field can only be modified if the
Day field has been set to 'Any'.
• Day: Press space bar to toggle between days.
You can also press <?> to display a popup menu that
lists the days, and use the arrow keys to select the
appropriate value. Press <Enter> to record the changes
(the cursor will move to the next field).
Please note that this field can only be modified if the
Date field has been set to 'Any'.
• Hour: Press <S> to display a popup menu that lists the hours
(please note that a 24-hour clock is used). Select the
appropriate value or press <A> to select 'Any'. Press
<Esc> to record the changes.
• Minute: Press <S> to display a popup menu that lists the
minutes. Select the appropriate value or press <A> to
select 'Any'. Press <Esc> to record the changes.
Table 5-1 below specifies what values the various fields should have
for different frequencies of time-based reports.
Table 5-1 Time-based report generation

Type of report Month Date Day* Hour** Minute
Yearly specify specify 'Any' specify specify
Monthly 'Any' specify 'Any' specify specify
Weekly 'Any' 'Any' specify specify specify
Daily 'Any' 'Any' 'Any' specify specify
Hourly 'Any' 'Any' 'Any' 'Any' specify
* This is the day of the week (Monday, Tuesday, etc.)

** A 24-hour clock is used.
Software Manual
Examples:
1. To generate a yearly report on January 1 at 12 o'clock (noon), the
following values should be used (see Figure 5-6):
− Month: January
− Date: 1
− Day: Any
− Hour: 12
− Minute: 0
2. To generate a weekly report on every Monday at 6:30 pm, the
following values should be used:
− Month: Any
− Date: Any
− Day: Monday
− Hour: 18
− Minute: 30
3. To generate an hourly report at every full hour, the following
values should be used:
− Month: Any
− Date: Any
− Day: Any
− Hour: Any
− Minute: 0
Software Manual
5.3.6 Conditional Report Generation
Conditional If you choose the 'Conditions' option from the edit menu for report
report generation files (see Figure 5-3), you can specify the conditions that must be met
before the report is generated. You can specify up to four conditions.
Figure 5-7 below shows the conditions definition screen.
Figure 5-7 Defining the parameters for conditional report generation
Defining conditions Defining the parameters for conditional report generation consists of
three steps:
1. You must select the type of condition under which to generate a
report.
2. You must name the variable for which the condition will be tested
(variable type and tag number).
3. You must specify the condition that must be met.
Software Manual
Condition types To select the condition type, move the cursor to the Condition
column. If any of the fields contains the value 'Undefined', no
condition has been specified yet.
Use <Space> to toggle between the three available options:
• SER event
A report is generated if the specified SER event takes place for the
specified variable.
• Counter value
A report is generated if the specified counter reaches the specified
value.
• Register value
A report is generated if the specified register reaches the specified
value.
Note:
The condition type 'SER event' is not possible if numeric SER
format has been configured.
Variable type After you have selected the condition type, press the right arrow key
(→) on your keyboard to further specify the condition.
If you chose 'SER event' as the condition type, you will need to
provide the variable type for which the condition will be tested. You
can use the <?> command to choose from a list of available variable
types. All variable types that can be SER-enabled are allowed (I, O,
M, C, T).
If you chose 'Counter value' or 'Register value' as the condition type,
the variable type will automatically be set to 'C' or 'R' respectively,
and you will move on the tag number column.
Tag number The next step is to specify the variable in the database for which the
condition will be tested. You can enter the tag number, or you can use
the <?> command to choose from a list of available tag numbers.
If the specified condition type is 'SER event' and you select a variable
that has not been SER-enabled, the following prompt will appear:
Variable is not SER enabled. Make SER enabled? (Y/N)
If you choose 'Yes', the database is updated and the variable is

accepted. Otherwise you need to choose a different variable.
Software Manual
Condition Finally, the actual condition must be specified. This is done in the last
column (Event/Value).
For the condition types 'Counter value' and 'Register value', a numeric
value must be entered. The status line indicates the permitted range.
For the condition type 'SER event', you can use <Space> to toggle
between the available options. These depend on the variable type as
shown in Table 5-2 below.
Table 5-2 Available conditions for various variable types

Variable type Available conditions
− I (digital input) − Any transition

− O (digital output) − Transition to low
− M (marker) − Transition to high
− T (timer)
− C (counter)
− AI (analog input) − Exceed setpoint
− AO (analog output) − Exceed setpoint low
− Exceed setpoint high
5.3.7 Report Printer Configuration
Report printer If you choose the 'Printer config.' option from the edit menu for report
configuration files (see Figure 5-3), you can define the configuration of the printer
that is directly connected to the FSC system and that is used to output
the current report. Figure 5-8 on the next page shows the report
printer configuration screen.
The following printer parameters can be configured:
Printer type Use <Space> to toggle between the available printers. You can also
use the <?> command to choose from a list. Table 5-3 on the next
page lists the available printers.
A special option is the dummy printer. If you select this printer, all
attributes specified in the report text will be ignored.
Software Manual
Table 5-3 Supported report printers
Supported report printers
NEC P6 Plus EPSON FX80 Dummy printer
NEC P7 Plus EPSON FX80+ Siemens PT88-11
NEC P6 Color EPSON FX100 Siemens PT89-11
NEC P7 Color EPSON FX800
EPSON FX1000
EPSON RX80
Figure 5-8 Report printer configuration screen
Software Manual
Page length Use <Space> to toggle between the available paper lengths. You can
also use the <?> command to choose from a list. There are two paper
lengths: 66 (11" fanfold paper) or 72 (12" fanfold paper).
Header margin This specifies the number of lines that are left blank at the start of a
page before the header is printed. The valid header margin range
depends on the page length and the current footer margin. Enter a
value between the boundaries specified.
Footer margin This specifies the number of lines that are left blank at the end of a
page before the footer is printed. The valid footer margin range
depends on the page length and the current header margin. Enter a
Characters on line Use <Space> to toggle between the available options. You can also
use the <?> command to choose from a list. The available options
depend on the selected printer type.
Software Manual
5.4 SER Format File
5.4.1 Introduction
SER format file The SER format file contains the definition of how the sequence-of-
event recording (SER) messages will be printed on the printer that is
directly connected to the FSC system. You can define the output
format for each variable type. This means that you can indicate
yourself which data is of interest to you when printing SER events
and which data is not.
SER format The SER format messages for an application are stored in a file called
messages <application name>.FMT. If you want to edit the SER format file and
this file does not exist, a default file will be created. This default file
has the same layout as the default format file used by the 'Translate
Application' option (compiler) of FSC Navigator. The difference is
the value of the qualification of markers. The compiler default file
generates no marker qualification table, whereas the user format file
will.
5.4.2 Editing the SER Format File
SER format file The SER format file defines how the sequence-of-event recording
(SER) messages will be printed on the printer that is directly
connected to the FSC system. To edit the SER format file, choose the
'SER format file' option from the main menu (see Figure 5-1).
Please note that this option is not available if no communication
channel has been defined (System Configuration / Install / Modules /
Central Parts / COM).
FSC Navigator will first check whether there is already an SER format
file. If there is, the file is read and checked for invalid data. If the SER
format file has been successfully verified, the screen as shown in
Figure 5-9 on the next page will appear.
Software Manual
Figure 5-9 Edit menu for SER format file
Edit menu The following options are available in the edit menu for the SER
for SER format file format file:
SER messages Use this option to define the SER report layout and edit the SER
messages. For details refer to subsection 5.4.3 below.
Printer config. Use this option to define the configuration of the printer that is used
to output the SER messages. For details refer to subsection 5.4.4
below.
Main Use this option to return to the main menu (see Figure 5-1).
If the SER message file has been changed, you are first asked whether
you wish to save the changes or discard them.
Software Manual
Note:
The 'Edit reports and SER format' option of FSC Navigator can
be used to change the default format to include service and
qualification for the variables (see subsection 5.4.4).
As the service and qualification are stored in the communication
module's EPROMs, inclusion is only possible as long as the
<Application>.Cxx files do not exceed the capacity of 2 Mbit
EPROMs.
5.4.3 SER Messages
SER messages If you choose the 'SER messages' option from the edit menu for the
SER format file (see Figure 5-9), an editor will open (see Figure
5-10) which allows you to edit the SER messages and define the
layout. Refer to subsection 5.2 for details on the available editing
commands.
provides a number of special commands:
Graphic This menu option provides access to a submenu that is used to set
graphic attributes of the text. The attributes are valid from the current
cursor position to the end of the line. If you choose the attribute once
more, it is switched off again. Only valid attributes are displayed. The
available attributes are:
− Bold: The text will be shown bold.
− Underline: The text will be underlined (only for printer output).
Color This menu option provides access to a submenu that allows you to set
the foreground colors. This option is only available for color printers.
Date If you choose this option, an indicator will be inserted in the text that
specifies where the current date will be shown. This is indicated by
the dummy text '- date ----------------'. You cannot edit this text, and
the cursor can only be positioned on the first character of the text.
To remove the date indicator, move the cursor to the first character of
Software Manual
Figure 5-10 Edit menu for SER messages
Time If you choose this option, an indicator will be inserted in the text that
specifies where the current time will be shown. This is indicated by
the dummy text '- time ----'. You cannot edit this text, and the cursor
can only be positioned on the first character of the text.
To remove the time indicator, move the cursor to the first character of
Page number If you choose this option, an indicator will be inserted in the text that
specifies where the page number will be shown. This is indicated by
the dummy text 'PN'. You cannot edit this text, and the cursor can
only be positioned on the first character of the text.
To remove the page number indicator, move the cursor to the first
character of the dummy text, and press <Del>. Alternatively, you can
use the <Backspace> key at the end of the indicator.
Edit If you choose this option, you will return to the text editor.
Main If you choose this option, you will return to the SER format editor
main menu.
Software Manual
Special functions There are a number of special functions that allow you to insert tag
numbers, services, values, etc. into the SER messages. They are:
<Alt> + <T> Use this key combination to insert the tag number of a variable into
the current SER message. A total of 16 positions in the message are
reserved for the tag number (indicated by '- tag number ---').
You cannot edit the tag number indicator, and the cursor can only be
positioned on the first character of the text. To remove the tag number,
indicator.
<Alt> + <S> Use this key combination to insert the service of a variable into the
current SER message. A total of 19 positions in the message are
reserved for the service (indicated by '- service ---------').
You cannot edit the service indicator, and the cursor can only be
positioned on the first character of the text. To remove the service,
indicator.
Note:
The service message is not defined for register outputs (BO).
<Alt> + <Q> Use this key combination to insert the qualification of a variable into
the current SER message. A total of 22 positions in the message are
reserved for the qualification (indicated by '- qualification ------').
You cannot edit the qualification indicator, and the cursor can only be
positioned on the first character of the text. To remove the
qualification, move the cursor to the first character of its indicator, and
press <Del>. Alternatively, you can use the <Backspace> key at the
end of the indicator.
<Alt> + <V> Use this key combination to insert the current value of a variable into
the current SER message. This is only possible for variable types AI,
AO and BO. A total of 22 positions in the message are reserved for
the value (indicated by '- value --------------').
You cannot edit the value indicator, and the cursor can only be
positioned on the first character of the text. To remove the variable
value, move the cursor to the first character of its indicator, and press
<Del>. Alternatively, you can use the <Backspace> key at the end of
the indication.
Software Manual
5.4.4 SER Printer Configuration
SER printer If you choose the 'Printer config.' option from the edit menu for the
configuration format file (see Figure 5-9), you can define the configuration of the
printer that is directly connected to the FSC system and that is used to
output the SER data.
Figure 5-11 below shows the SER printer configuration screen.
Figure 5-11 SER printer configuration screen
Software Manual
The following printer parameters can be configured:
Printer type Use <Space> to toggle between the available printers. You can also
use the <?> command to choose from a list. Table 5-4 below lists the
available printers.
Table 5-4 Supported SER printers

NEC P7 Plus EPSON FX80+ FSC SER format
EPSON FX1000
EPSON RX80
There are two special printer types:

• Dummy printer
If you select this printer, all attributes specified in the report text
will be ignored.
• FSC SER format
If the FSC SER format has been selected, the marker service and
marker qualification may be available in the SER. To specify
marker services in the SER, use <Space> to toggle the 'Marker
service in EPROM' field to 'Yes'. To specify the marker
qualification in the SER, use <Space> to toggle the 'Marker
qualification in EPROM' field to 'Yes (see Figure 5-12 on the
next page).
page before the footer is printed. The valid header margin range
Software Manual
Figure 5-12 FSCSER format
Software Manual
5.5 Deleting Files
Deleting files To delete a report file or the SER format file, choose the 'Delete file'
option from the main menu (see Figure 5-1). The screen as shown in
Figure 5-13 below will appear.
Please note that the 'Report file' and 'SER format file' options will only
be displayed if there are any report files and/or SER format file to
delete.
Figure 5-13 Delete menu
Deleting a report file To delete a report file, choose 'Report file' from the delete menu (see
Figure 5-13). You are first asked to enter the number of the report
you wish to delete. This is done in the selection screen as shown in
Figure 5-2. After you have selected a report to be deleted, the
following question will be asked:
Do you want to delete the report file? (Y/N)
If you press <Y>, the report file will be deleted.
If you press <N>, you will return to the delete menu.
Software Manual
Deleting the To delete the SER format file, choose 'SER format file' from the
SER format file delete menu (see Figure 5-13). The following question will be asked:
Do you want to delete the SER format file? (Y/N)
If you press <Y>, the SER format file will be deleted.

If you press <N>, you will return to the delete menu.
Software Manual
5.6 Default SER Event Format
5.6.1 Introduction
SER event format This subsection describes the default format of the SER reports. The
default SER format is used in combination with FSCSOE, which is a
separate Windows application.
A distinction is made between event reports for process variables and

SER messages. The SER header and variable event formats can be
changed using the 'SER Format' option of FSC Navigator. The format
of the SER messages is fixed.
5.6.2 Default SER Header
SER header The SER header is printed at the top of every new page. It is a fixed
text string of 87 characters:
'Type', <space>, 'Tag number', <4 spaces>, 'Service', <12 spaces>,
'Qualification', <9 spaces>, 'Date', <19 spaces>, 'Time'.
The SER header is preceded by a printer control sequence that

consists of an ASCII formfeed character and four CR-LF character
combinations. The header is terminated by two CR-LF character
combinations.
5.6.3 Default Variable Event Format
Variable event An identical format is used for all variable types. The format consists
format of 104 ASCII printable characters. Table 5-5 below specifies the
fields that are used.
Software Manual
Table 5-5 Variable event format
Field Description Length
Margin Line margin of 8 spaces 8
Type Type identification 3
Tag number Variable tag number 16
Service Variable service 19
Qualification Variable qualification 22
Date Date stamp 23
Time Time stamp 11
Terminator Carriage Return + Line Feed 2
Total length: 104
Each field is explained in more detail below.
Type The type identification field consists of a fixed string of 3 characters.

If the type identification is less than 3 characters, the remaining part
of the field is filled with trailing spaces. Depending on the variable
type, the string is:
− I for digital inputs,
− O for digital outputs,
− M for markers,
− T for timers,
− C for counters,
− AI for analog inputs,
− AO for analog outputs,
− BO for register outputs.
Tag number The tag number field contains the tag number of the variable as
assigned in the system configuration or FLDs. If the tag number has
fewer than 16 characters, the remaining part of the field is filled with
trailing spaces.
Software Manual
Service The service field contains the service of the variable as assigned in
the system configuration or FLDs. If the service is less than 19
characters, the remaining part of the field is filled with trailing
spaces. The service is only printed for variable types I, O, AI, AO and
optionally for M. For variable types BO, T and C, the field is
completely filled with spaces.
Qualification The contents of the qualification field depend on the variable type.
Variable types For types I, O and M, the field consists of two parts. The first part is 6
I, O and M characters long and is used to indicate the current status of the
variable.
If the status is high, the field is filled with spaces. If the status is low,
a text of five characters plus a trailing space is printed. The text is
derived from the compiler message file and depends on the language.
For the English version, the text is 'NOT'.
The second part of the qualification field contains the qualification of

the variable as assigned in the system configuration or FLDs. If the
qualification is less than 16 characters, the remaining part of the field
is filled with trailing spaces.
Notes:
1. By default, the qualification for markers is not printed. If you wish
to include the marker qualification in the event report, refer to
page 5-26 of this manual.
2. It is quite common that the qualification represents a negation, e.g.
'not low'. In this case, when the variable status is low, both the
'not' in the first part of the qualification field and the 'not' text
within the qualification itself are suppressed, i.e. the string that is
printed is 'low' instead of 'not not low'. The remaining part of the
field is filled with spaces.
Variable types
T and C For variable types T and C, the field is completely filled with spaces.
Variable types For the variable types AI and AO, the qualification field is used to
AI and AO report the type of event.
Three different texts can appear to indicate that the analog value
exceeded the configured SER high value, became less than the SER
low value, or re-entered the healthy range between SER low and SER
high. The messages are derived from the compiler message file and
depend on the language. For the English version, the texts are
Software Manual
'maximum', 'minimum' and 'healthy', respectively. A total of 20
characters is reserved for the texts. The last two characters of the
qualification field are always filled with spaces.
Variable type BO For type BO, the qualification field contains the value of the BO
variable followed by the configured engineering units.
Force events If a variable in the FSC system is forced to a specific value, or a

previous force is cleared, an event report is generated.
In this case, the qualification field is used to indicate the type of force
event. The texts that are printed are derived from the compiler
message file and depend on the language. For the English version, the
texts are 'force set' and 'force cleared', respectively. The force texts
may be 22 characters long. The remaining characters are filled with
spaces.
Date The date field consists of the following parts: weekday, date and
month. The weekday and date parts are separated by a comma and a
space. The date and month parts are separated by a dash ('-').
The weekday part contains a text that is derived from the compiler
message file and depends on the language. For the English version the
following texts are used: 'Sunday', 'Monday', 'Tuesday', 'Wednesday',
'Thursday', 'Friday', and 'Saturday'. A number of 16 characters is
reserved for the weekday. The weekday text is always immediately
followed by a comma and a space character. If the text is less than 16
characters, the remaining characters of the date field are filled with
trailing spaces.
The date and month parts are printed as a two-character decimal value.
If the value of the date or month is less than 10, a space is printed at
the first character position. (This means there are no leading zeros.)
Time The time field consists of the following parts: hours, minutes,
seconds and hundredths of seconds.
The hours, minutes and seconds parts are separated by a dot ('.'). The
seconds and hundredths of seconds parts are separated by a colon (':').
All parts of the time field are printed as two-character decimal values.
If the value of the hours is less than 10, a space is printed at the first
character position. If any of the other values is less than 10, a zero is
printed at the first character position.
Software Manual
5.6.4 Standard SER Messages
SER messages The FSC system contains several standard SER messages.
These messages cannot be suppressed. The texts are derived from the
compiler message file and depend on the language.
System fault The system fault message is printed if a fault is detected within the
message FSC system. The message indicates the system number, rack and
position where the fault occurred and the date and time. The format
of the message is adapted to the formats for variable events. The
default format consists of fixed text an five variable fields (explained
in more detail below):
− 12 leading spaces,
− text: 'System fault ',
− system number field,
− rack number field,
− position number field,
− date field,
− time field.
− carriage return, line feed.
The system, rack and position number fields are separated by a

comma and a space character. The total length of the message is equal
to the length of the variable event report, i.e. 104 characters for the
default format.
System number field The system number field consists of the text 'System:' and the system
number in decimal representation.
The system number field is aligned with the service field of the
variable event formats as described above. The length of the field
depends on the system number. If the system number is less than 10,
the field is 9 characters long. If the system number is 10 or higher, the
field is 10 characters.
If the service field is not configured in the variable SER format, the
system number field is not printed.
Rack number field The rack number field consists of the text 'Rack:' and the rack number
in decimal representation.
The rack number value always occupies two character positions. If the
rack number is less than 10, a space is printed at the first character
Software Manual
position. The rack number field is aligned with the qualification field
of the variable event formats as described above.
If the qualification field is not configured in the variable SER format,
the rack number field is not printed.
Position number field The position number field consists of the text 'Position:' and the
position number in decimal representation.
The position number value always occupies two character positions. If
the position number is less than 10, a space is printed at the first
character position. The position number field is printed directly after
the rack number field.
If the qualification field is not configured in the variable SER format,
the position number field is not printed.
Date field and The format of the date and time fields is identical to the format used
Time field in the variable event reports.
The fields are aligned to the corresponding fields in the variable event
formats.
All forces cleared This message is generated if a command was issued from the FSC
message user station to clear all forces. The message consists of the text 'All
forces cleared' and the date and time.
The text is aligned with the service field of the variable event formats
as described above. If no service field is configured, the text is aligned
with the qualification field. If neither the service and qualification
field is configured, no text is printed.
The format of the date and time fields is identical to the format used in
the variable event reports. The fields are aligned to the corresponding
fields in the variable event formats.
SER message error The SER message error text is printed if an invalid SER message is
selected.
The message consists of a text 'SER message error'. The text is aligned
with the service field of the variable event formats as described above.
If no service field is configured, the text is aligned with the
qualification field. If neither the service and qualification field is
configured, no text is printed.
This SER message error should never appear. If it does, please contact
Honeywell Safety Management Systems.
Software Manual
Software Manual
Fail Safe Control
Section 6:
Functional Logic Diagrams
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 6: Functional Logic Diagrams
6.1 Introduction .................................................................................................... 6-1
6.2 FLD Editor Menus........................................................................................... 6-4

6.2.1 Menu Structure................................................................................................................. 6-4
6.2.2 Main Menu........................................................................................................................ 6-6
6.2.3 Symbol Menu ................................................................................................................... 6-9
6.2.4 Block Menu..................................................................................................................... 6-11
6.3 Getting Started ............................................................................................. 6-12

6.3.1 Starting the Editor........................................................................................................... 6-12
6.3.2 Editor Controls................................................................................................................ 6-14
6.3.3 Working with FLDs ......................................................................................................... 6-15
6.3.4 Working with Individual Symbols.................................................................................... 6-18
6.3.5 Working with Groups of Symbols (Blocks)..................................................................... 6-22
6.3.6 Drawing Connection Lines ............................................................................................. 6-25
6.3.7 Entering Information....................................................................................................... 6-27
6.3.8 Selection Lists ................................................................................................................ 6-30
6.4 FLD Types (Block Types)............................................................................. 6-32
6.5 Title Block ..................................................................................................... 6-35

6.6.1 FLD Revisions ................................................................................................................ 6-39
6.6.2 Application Revisions ..................................................................................................... 6-41
6.7 Appending Applications .............................................................................. 6-43
6.8 FLD Symbols ................................................................................................ 6-46

6.8.1 Non-Functional Symbols ................................................................................................ 6-46
6.8.2 Connection Lines............................................................................................................ 6-48
6.8.4 Compare Functions ........................................................................................................ 6-53
6.8.5 Calculation Functions ..................................................................................................... 6-55
6.8.6 Mathematical Functions ................................................................................................. 6-56
6.8.7 Counters and Registers ................................................................................................. 6-58
6.8.8 Constants and Signal Conversions ................................................................................ 6-60
6.8.9 Function Blocks .............................................................................................................. 6-61
6.8.10 Equation Blocks ............................................................................................................. 6-62
6.8.11 PIDs................................................................................................................................ 6-63
6.8.12 Time Functions............................................................................................................... 6-64
6.8.13 I/O Symbols.................................................................................................................... 6-69
6.8.14 Sheet Transfers.............................................................................................................. 6-73
6.8.15 Flip-Flops........................................................................................................................ 6-77
6.8.16 Texts............................................................................................................................... 6-78
Software Manual
Section 6: Functional Logic Diagrams i
6.9 Design Considerations................................................................................. 6-79

6.9.1 Logical Functions, Compare, and Calculation Functions............................................... 6-79
6.9.2 Counters, Registers, and Constants .............................................................................. 6-79
6.9.3 Signal Conversions ........................................................................................................ 6-80
6.9.4 Function Blocks .............................................................................................................. 6-81
6.9.5 Equation Blocks.............................................................................................................. 6-82
6.9.6 Timers ............................................................................................................................ 6-85
6.9.7 PIDs................................................................................................................................ 6-88
6.9.8 Inputs and Outputs ......................................................................................................... 6-88
6.9.9 Sheet References........................................................................................................... 6-90
6.9.10 Flip-Flops and Pulses..................................................................................................... 6-91
6.10 Sheet Transfers ............................................................................................ 6-92

6.10.1 Characteristics................................................................................................................ 6-92
6.10.2 Off-Sheet Transfers........................................................................................................ 6-94
6.10.3 On-Sheet Transfers........................................................................................................ 6-97
6.10.4 Selecting a Sheet Transfer Symbol Using a Selection List............................................ 6-99
6.11 FLD Formats ............................................................................................... 6-100
6.12 Error Messages........................................................................................... 6-104
Software Manual
ii Section 6: Functional Logic Diagrams
FIGURES
Figure 6-1 FLD layout (hardcopy)................................................................................................. 6-2

Figure 6-2 Menu structure of FLD design editor........................................................................... 6-5
Figure 6-3 Main menu structure ................................................................................................... 6-6
Figure 6-4 Symbol menu structure ............................................................................................... 6-9
Figure 6-5 Symbol menu structure ............................................................................................. 6-11
Figure 6-6 FLD design editor: start-up screen............................................................................ 6-12
Figure 6-7 FLD design screen (with main menu) ....................................................................... 6-13
Figure 6-8 Selection sheet of a program block as defined in SYM1 .......................................... 6-18
Figure 6-9 Connection lines........................................................................................................ 6-25
Figure 6-10 Example of a selection list ........................................................................................ 6-30
Figure 6-11 Title block screen ...................................................................................................... 6-35
Figure 6-12 Title block on FLD printout ........................................................................................ 6-38
Figure 6-13 Revision window ....................................................................................................... 6-39
Figure 6-14 Revision data in title block ........................................................................................ 6-41
Figure 6-15 Example of basic sheet symbol as defined in symbol library SYM1 (screen view) .. 6-47
Figure 6-16 Lines: boolean signals and binary signals ................................................................ 6-48
Figure 6-17 Lines: Analog I/O converter ...................................................................................... 6-48
Figure 6-18 Lines: crossing of signals .......................................................................................... 6-49
Figure 6-19 Selection symbol for mathematical functions in FLD ................................................ 6-56
Figure 6-20 Function block inputs ................................................................................................ 6-62
Figure 6-21 Function block outputs .............................................................................................. 6-62
Figure 6-22 Timers with constant timer value: pulse.................................................................... 6-65
Figure 6-23 Timers with constant timer value: pulse retriggerable .............................................. 6-65
Figure 6-24 Timers with constant timer value: delayed ON ......................................................... 6-65
Figure 6-25 Timers with constant timer value: delayed ON memorize ........................................ 6-66
Figure 6-26 Timers with constant timer value: delayed OFF ....................................................... 6-66
Figure 6-27 Timers with variable timer value: pulse..................................................................... 6-67
Figure 6-28 Timers with variable timer value: pulse retriggerable ............................................... 6-67
Figure 6-29 Timers with variable timer value: delayed ON .......................................................... 6-68
Figure 6-30 Timers with variable timer value: delayed ON memorize ......................................... 6-68
Figure 6-31 Timers with variable timer value: delayed OFF ........................................................ 6-68
Figure 6-32 I/O symbols: digital input (I) ...................................................................................... 6-69
Figure 6-33 I/O symbols: digital output (O) .................................................................................. 6-70
Figure 6-34 I/O symbols: digital input (with sheet reference) ....................................................... 6-70
Figure 6-35 I/O symbols: digital output (with sheet reference)..................................................... 6-70
Figure 6-36 I/O symbols: diagnostic input .................................................................................... 6-70
Figure 6-37 I/O symbols: binary input (BI).................................................................................... 6-71
Figure 6-38 I/O symbols: binary output (BO)................................................................................ 6-72
Figure 6-39 I/O symbols: binary coded decimal input (BI) ........................................................... 6-72
Figure 6-40 I/O symbols: binary coded decimal output (BO) ....................................................... 6-72
Figure 6-41 I/O symbols: analog input combined with analog-to-digital converter ...................... 6-73
Figure 6-42 I/O symbols: analog output combined with digital-to-analog converter .................... 6-73
Figure 6-43 Sheet transfers: boolean on-sheet transfer .............................................................. 6-74
Figure 6-44 Sheet transfers: binary on-sheet transfer.................................................................. 6-74
Figure 6-45 Sheet transfers: on-sheet transfer for repeated digital input..................................... 6-75
Figure 6-46 Sheet transfers: on-sheet transfer for repeated binary input .................................... 6-75
Figure 6-47 Sheet transfers: boolean off-sheet transfer .............................................................. 6-76
Figure 6-48 Sheet transfers: binary off-sheet transfer ................................................................. 6-76
Figure 6-49 Sheet transfers: multiple boolean off-sheet transfer ................................................. 6-76
Figure 6-50 Sheet transfers: multiple binary off-sheet transfer .................................................... 6-77
Software Manual
Section 6: Functional Logic Diagrams iii
FIGURES (continued)
Figure 6-51 Flip-flop symbols: s-r flip-flop .................................................................................... 6-77

Figure 6-52 Flip-flop symbols: r-s flip-flop .................................................................................... 6-78
Figure 6-53 Texts in FLDs ............................................................................................................ 6-78
Figure 6-54 Example of equation function.................................................................................... 6-82
Figure 6-55 Equation block symbol .............................................................................................. 6-82
Figure 6-56 Approximating an output value to an input value ...................................................... 6-84
Figure 6-57 Off-sheet transfer (boolean signal) ........................................................................... 6-92
Figure 6-58 On-sheet transfer (binary signal)............................................................................... 6-93
Figure 6-59 Example of an FLD designed with SYM1 ............................................................... 6-100
TABLES
Table 6-1 Available logical functions in FLDs ........................................................................... 6-49

Table 6-2 Available compare functions in FLDs........................................................................ 6-53
Table 6-3 Available calculation functions in FLDs..................................................................... 6-55
Table 6-4 Available mathematical functions in FLDs ................................................................ 6-56
Table 6-5 Available I/O symbols in FLDs .................................................................................. 6-69
Software Manual
iv Section 6: Functional Logic Diagrams
Section 6 – Functional Logic Diagrams
6.1 Introduction
FLDs The FSC system's safety-critical control functions are defined by

means of functional logic diagrams (FLDs). These FLDs are created
using the FLD design editor, which allows you to use the screen as a
drawing sheet and the cursor as a pencil. The FLD design editor is
started by choosing the 'Design FLDs' option of FSC Navigator.
FLD files The functional logic diagrams (FLDs) are saved to disk in the project
folder under the following name: <Application name>.<FLD no.>.
For example, PROJ1_1.110 is FLD 110 for application PROJ1_1.
If the FLD number has less than three digits, leading zeros are used in
the extension (i.e. FLD number 4 is saved as '004').
FLD symbols The functional logic diagrams (FLDs) are made up of a predefined set
of symbols that define the safety application (see subsection 6.6).
When designing FLDs, you can select a symbol from a special
symbol selection sheet (see subsection 6.3.4). Certain symbols need
additional data, such as symbol height, width or I/O tag number. If
required, you will be asked to enter the data on the bottom line of the
screen. In a number of cases you can select data like tag numbers,
sheet references or FLD numbers from a pop-up window. The FLD
design editor will assist in selecting a position for a symbol by means
of a grid and a snap-to-grid function, which automatically selects the
nearest grid position or half grid position of the cursor.
FLD layout Figure 6-1 shows an example of a Functional Logic Diagram (FLD),
which is split into four main areas:
• the information area (bottom).
Software Manual
Section 6: Functional Logic Diagrams 6-1
Information area The FLD information area, at the bottom of the FLD, provides
information to identify the Functional Logic Diagram, including
revision data.
Input area The FLD input area, on the left-hand side of the FLD, contains all
the variables that serve as the input to the control function. Input
variables may originate from the field equipment or from other
computer equipment (Process Computer, FSC).
14TX711
Low Temperature Product Separator (14D-105)
Input Diagnostic 2515 1 14TI711BPV C

Bypass 3 Input Diagnostics O
S I/O type: AI 15 Xmtr OK A "Xmtr OK" M
Y 14TX711 13 B
S "Not faulty" 1
&
Xmtr OK
A
FB C
Bypass Time Remaining 41519 1 14TI711TMR
3 Bypass Time Remain
C
O
S I/O type: SensAI 15 913 Diagnostic Bypass Active A Signal type: F M
Y 14TX711 13 D
S "Not faulty" 1
Xmtr OK 170 14D-105 Product Sep

>1
_ "Temperature OK"
F 14TX711 15 40515 A 175
2
L 13 S &
14D-105 Product Sep D 0 t
D 1
>
t=2 s 576 1 14TALL711 C
F 45 R 3 14D-105 Product Sep O
A "Temperature OK" M
LL Setpoint
(DegF) 42526 1 14TSLL711TP C
3 LL Setpoint O
A Signal type: F M
Temperature OK
14ESV711
Propylene Feed To
Deethanizer Chiller
Reset Required 591 1 14EA711 C
& 3 14E-26 C3= Chiller O
A "Reset Required" M
Deenergize to Close 1523 16 14TO711 F

F 14ES711 15 552 Field Reset & 5 14E-26 C3= Chiller L
L 14E-26 C3= Chiller 1 1 "Run (Not Closed)" D
D "Reset" 11
>
_1
Deethanizer Overhead Chiller (14E-26)

Customer : Phillips Petroleum Company REFERENCE DWG. No.
Functional Logic Diagrams Unit 14 Shutdown Blocks #5
Principal : Honeywell IAC RDAS-14-VAR-MF-6
1 6-22-2000 ADD CONSTANTS Your Plant's Name Unit 14 Deethanizer Chiller
Plant 1 : Unit 11/14
0 10-8-1998 IFC Tel (713)780-5000 Date 6/22/1998 By: D.D. Ward
B 8-6-1998 ISSUED FOR TEST

Plant 2 : East Area Phase III
Honeywell Safety Fax (713)780-6676
8440 Westglen Dr.
Drawing number:
A
Rev
6/22/1998
Date
FIRST ISSUE
Description Chk'd
Req/Order No:
Management Systems Houston, TX 77063
HSMS (TX40)
Serial
U11_11
Project
Unit
170
Sheet
175
Cnt'd
Code Code
Figure 6-1 FLD layout (hardcopy)
Data can be exchanged between FLDs via sheet transfer functions.

This allows a structured design of complex functions across multiple
diagrams.
Control function area The FLD control function area, which is the central area of the FLD,
contains the actual implementation of the control function. The
function is realized by interconnecting predefined symbols which
provide a variety of functions including logical, numerical and
time-related functions.
Software Manual
6-2 Section 6: Functional Logic Diagrams
In addition to these standard functions, user-definable blocks are
supported:
• Function Blocks — standard FLDs for repetitive use within the
control program (see subsection 6.8.9), and
• Equation Blocks — for tabular definition of complex functions,
e.g. non-linear equations (see subsection 6.8.10).
Output area The FLD output area, on the right-hand side of the FLD, contains
the results of the control function. These variables may be used to
drive the field equipment or may be transferred to other computer
equipment, e.g. a process computer or another FSC system.
Software Manual
6.2 FLD Editor Menus
6.2.1 Menu Structure
Menu structure Commands can be entered by choosing an option from any of the
FLD editor menus. Figure 6-2 on the next page shows the menu
structure of the FLD design editor. For a further explanation of the
individual menu options refer to subsections 6.2.2 to 6.2.4.
Activating The FLD design editor is entirely menu-driven. The menus are placed
menu options on the bottom line of the screen. The menus can be accessed using the
keyboard or the mouse. Menu options can be activated in three ways:
• Use the mouse to move the block cursor to the menu option, and
click the left mouse button.
• Press the uppercase letter of the menu option. For example, to
activate the 'draG' command, you should press the <G> key.
are meaningful. For example, if an FLD is empty, no symbol
manipulation options are available (change, move, drag, delete or
copy), because there are no symbols to perform these operations on.
Also, you cannot choose the undelete option if you did not recently
delete something.
A menu command can be canceled at any point where input is asked.

This is done by pressing <Esc>. In that case the FLD design editor
returns to the situation before the start of the canceled command.
Software Manual
Main
Symbol New
Last
Copy
Move
draG
cHange
Delete
Undelete redraW
mAin Symbol set
Forward Back
Block Move
New Delete Zoom
Save Copy Delete
redraW Load Undelete
Title block Save Copy
Equation file redraW Renumber
eXit Undelete Append appl.
mAin aPpl. revision
Forward Back
Figure 6-2 Menu structure of FLD design editor
Software Manual
6.2.2 Main Menu
Main menu The Main menu provides a number of options that apply to the entire
FLD project. It has three options that open a new menu. The Main
menu has the following menu items:
MAIN
Symbol Forward
Block
Zoom
New
Delete
Save
Undelete
redraW
Copy
Title block
Renumber
Equation file
Append appl.
eXit
aPpl. revision
Back
Figure 6-3 Main menu structure
Each of the menu items is explained in more detail below.
Symbol This menu option will open a new menu that provides a number of
options related to individual symbols in an FLD. For details refer to
subsection 6.2.3.
Block This menu option will open a new menu that provides a number of
options related to groups of symbols in an FLD (see subsection
6.2.4).
New Choose this option to open another FLD or add a new FLD to the
application (see subsection 6.3.3).
Software Manual
Save Choose this option to save the current FLD, but not close it. It is
recommended that you use this option regularly as it can save you
from losing your data in case of a power dip or a computer problem
redraW Choose this option to redraw the current FLD and refresh the screen
Title block Choose this option to open the title block screen, which allows you to
edit the FLD information. For details refer to subsection 6.5.
Equation file This option is only available for equation blocks. You can use it to
specify the file that contains the equation table (located in the project
folder). For details on using equation files refer to subsection 6.9.5.
eXit Choose this option to exit the FLD design editor and return to the
main FSC Navigator screen. The current FLD will be saved to disk.
Forward Choose this option to go to the second part of the Main menu
(see below).
Second part of The second part of the Main menu can be called up by choosing the
Main menu Forward option from the Main menu. This menu has a number of
additional commands:
Zoom Choose this option to scale the current FLD in such a way that it can
be displayed on your screen. Please note that this option is only active
if the size of the FLD is too big to be displayed on your screen,
depending on the symbol library used (see subsection 6.3.3).
Delete Choose this option to close and delete the current FLD (see
subsection 6.3.3).
Undelete Choose this option to recover an FLD that was recently deleted (see
subsection 6.3.3).
Software Manual
Copy Choose this option to copy an entire FLD from the current application
or another application into the current FLD (see subsection 6.3.3).
This option is not available if the FLD is empty or if on-line
modification is active.
Renumber Choose this option to change the number of the current FLD. This
option is not available if the FLD is empty or if on-line modification
is active (see subsection 6.3.3).
Append appl. Choose this option to append one or more subapplications to the
current application (see subsection 6.7). This option is not available if
the FLD is empty or if on-line modification is active.
aPpl. revision Choose this option to create revision updates for an entire project. For
details refer to subsection 6.6.2.
Back Choose this option to return to the first part of the main menu.
Software Manual
6.2.3 Symbol Menu
Symbol menu The Symbol menu provides a number of options that are related to
individual symbols in an FLD. It has one option that opens a new
menu. The Symbol menu has the following menu items:
SYMBOL
New Forward
Last
redraW
Copy
Symbol set
Move
Back
draG
cHange
Delete
Undelete
mAin
Forward
Figure 6-4 Symbol menu structure
New Choose this option to add a new symbol to the FLD (see subsection
6.3.4).
Last Choose this option to select the last symbol that was selected from
the selection sheet (see subsection 6.3.4).
Copy Choose this option to copy a symbol to another location on the FLD
Software Manual
Move Choose this option to move a symbol to another location on the FLD,
with all connections of this symbol broken (see subsection 6.3.4).
draG Choose this option to move a symbol to another location on the FLD,
with all connections of this symbol remaining intact (see subsection
6.3.4).
Change Choose this option to change the variable data of a symbol on the
FLD (see subsection 6.3.4).
Delete Choose this option to delete a symbol from the current FLD (see
subsection 6.3.4).
Undelete Choose this option to recover a symbol that was recently deleted (see
subsection 6.3.4).
mAin Choose this option to go back to the main menu.
Forward Choose this option to go to the second part of the Symbol menu (see
below).
Second part of The second part of the Symbol menu can be called up by choosing
Symbol menu the Forward option from the Symbol menu. This menu has the
following menu items:
redraW Choose this option to redraw the current FLD and refresh the screen
Symbol set Choose this option to toggle between the symbol set for a function
block FLD and that of a program block FLD. This option is only
available if you are editing a comment sheet (see subsection 6.4).
Back Choose this option to go back to the first part of the Symbol menu.
Software Manual
6.2.4 Block Menu
Block menu The Block menu provides a number of options that are related to
groups of symbols in an FLD. The Block menu has the following
menu items:
BLOCK
Move Delete Copy Load Save redraW Undelete mAin
Figure 6-5 Symbol menu structure
Move Choose this option to move a group of symbols to another location on

the FLD (see subsection 6.3.5).
Delete Choose this option to delete a group of symbol from the current FLD
Copy Choose this option to copy a group of symbols to another location on

Load Choose this option to load a block from disk and place it anywhere on
Save Choose this option to save a block to disk (see subsection 6.3.5).
Undelete Choose this option to recover a block that was recently deleted (see
subsection 6.3.5).
RedraW Choose this option to redraw the current FLD and refresh the screen
mAin Choose this option to go back to the main menu.
Software Manual
6.3 Getting Started
6.3.1 Starting the Editor
Starting the
FLD editor The FLD design editor can be started in three ways:
• Menu bar: Project / Design FLDs

• Button bar: FLD
Design Functional Logic Diagrams
Start-up screen If you activate the 'Design FLDs' option of FSC Navigator, the
start-up screen of the FLD design editor appears:
Figure 6-6 FLD design editor: start-up screen
The name of the current project is shown in the top left corner of the
screen. To open a functional logic diagram, enter its number (between
1 to 999). You can also press <?> on the keyboard to open a pop-up
window that lists the existing FLD numbers with their descriptions.
Move the cursor bar to the FLD you wish to open, and press <Enter>.
Software Manual
Design screen If the FLD you entered at the start-up screen already exists, it will be
loaded (see Figure 6-7 below). If it does not exist, the title block
appears on screen (see subsection 6.4).
Figure 6-7 FLD design screen (with main menu)
You can easily step through the available FLDs by pressing the
<PgDn> and <PgUp> keys. Pressing <PgDn> will open the next
available FLD, and <PgUp> the previous one. The current FLD will
then be saved to disk and closed. Please note that this browsing
feature is only available in the FLD design editor's main menu.
Note:
The number of the FLD that is being edited will always be
shown in the bottom left corner of the screen.
Software Manual
6.3.2 Editor Controls
Message line The bottom line of the design screen is used to display messages, ask
for input or display menus. The same line is also used for entering
and editing input information.
Input can be given with the mouse or the keyboard. Error messages
are displayed for two seconds. They will also disappear as soon as you
press any key, click a mouse button, or move the mouse to another
position.
Cursor The shape of the cursor depends on the function:

• A cross-shaped cursor (+) is used to mark the current screen
position.
• A block-shaped cursor is used to mark the current option in a
menu.
• A text cursor (underscore) is used to mark the current position in a
text entry field.
The cursors can be controlled with the mouse or the arrow keys of the
keyboard.
Grid The design screen has a grid that makes it easier to choose a position
on the screen. The FLD design editor has a snap-to-grid function.
This means that only grid positions and half grid position can be
selected, and that objects are automatically placed at the nearest valid
grid position.
Software Manual
6.3.3 Working with FLDs
Creating/opening If you start the FLD design editor, the start-up screen appears (see
an FLD Figure 6-6). To open a functional logic diagram, enter its number
(between 1 to 999). You can also press <?> on the keyboard to open a
pop-up window that lists the existing FLD numbers with their
descriptions. Move the cursor bar to the FLD you wish to open, and
press <Enter>. The FLD will then be loaded and displayed on screen
(see Figure 6-7 on page 6-13).
If you enter an FLD number that does not exist yet, the title block will
appear (see subsection 6.4). Here you can enter FLD-specific
information before moving on to an empty design screen in which you
can create the new FLD.
To open an existing FLD or create a new one while you are already in
the design screen, choose the following menu options:
Main New
The current FLD will then be saved to disk, and you will be asked to
enter another FLD number (see above). The FLD number that is
shown by default is the current FLD number.
Saving an FLD To save the current FLD to disk without closing it, choose the
Main Save
It is recommended that you use this option regularly as it can save you
from losing your data in case of a power dip or a computer problem.
Redrawing an FLD If you want to redraw the current FLD on screen, choose any of the
Main redraW
Main Symbol Forward redraW
Main Block redraW

.
This option can be useful when the FLD is not displayed entirely
correctly after a connection is made and lines are drawn.
Software Manual
Zooming an FLD To display the current FLD in such a way that it can be displayed on
your screen, choose the following menu options:
Main Forward Zoom
Please note that this option is only available if the size of the FLD is
too big to be displayed on your screen (depending on the symbol
library used).
Copying an FLD To copy an entire FLD from the current application or another
application into the current FLD, choose the following menu options:
Main Forward Copy
Please note that this option is not available if the FLD is empty or if
on-line modification is active.
Make sure the FLD to be copied has been drawn using the same
symbol library. You will be prompted to enter a file name, which must
have the following format: <Appl.>_<Sys. no.>.<FLD no.>, where:
Appl. = Application folder from which a functional logic diagram
is to be copied.
Sys. no. = System number of the application from which a functional
logic diagram is to be copied.
FLD no. = Number of the functional logic diagram to be copied
(always 3 digits).
For example, if you want to copy the second FLD from application
TEST1, which has system number 1, then the file name should be
'TEST1_1.002'.
If the file you entered does not exist, a beep will sound, and you can
enter another file name. If the file does exist, all data of the selected
file is converted to data that is compatible with the current FLD.
All inputs, outputs and PIDs will get the illegal, non-existing tag
number '?'. This tag number must be changed afterwards (using the
'cHange' option in the Symbol menu). All sheet references are set to
zero. You must connect them afterwards using the 'cHange' option in
the Symbol menu. If the contents of the copied FLD is smaller than
the screen size, you can move it to another position on the screen.
otherwise it is placed directly into the new FLD, providing no overlap
is detected.
Software Manual
Renumbering To change the number of the current FLD, choose the following
an FLD menu options:
Main Forward Renumber
You need to specify a new number for the current FLD. This number
must be within the range specified, and it must be a number of an
empty FLD. If you entered a valid FLD number, all data from the
current FLD is moved to the new FLD number. The old FLD is
cleared from the disk and can be used again. (Make sure that you
modify any sheet references to accommodate for the new FLD
number.)
Note:
The 'renumber sheet' option is not available if the FLD is empty
or if on-line modification is active.
Deleting an FLD To close and delete the current FLD, choose the following menu
options:
Main Forward Delete
Before the FLD is actually deleted, you are asked to confirm the
operation. A backup copy is made which allows you to recover it later.
Undeleting an FLD To recover an FLD that was recently deleted, choose the following
menu options:
Main Forward Undelete
The undelete function can only be carried out immediately after a

delete operation. You can still undelete a deleted FLD if you choose
any of the following options: redraW, Delete, Forward or Back. Once
you choose any other option, the undelete option is no longer
available.
Software Manual
6.3.4 Working with Individual Symbols
Adding To add a new symbol to the current FLD, choose the following menu
a symbol options:
Main Symbol New
This will open a selection window, which will either be the selection
window for program blocks or for function blocks, depending on the
block type you entered in the title block (see subsection 6.4). Figure
6-8 below shows the selection sheet of a program block.
Figure 6-8 Selection sheet of a program block as defined in SYM1
The selection sheet for a function block is slightly different from that
of a program block. A function block has no system outputs or
off-sheet transfers, but it has two symbols that cannot be used on
program blocks: function block inputs and function block outputs.
After you have successfully selected a symbol to be added, the design

screen is displayed again and the selected symbol can be placed (see
below).
Software Manual
To add the last symbol that was selected from the selection sheet,
choose the following menu options:
Main Symbol Last
This allows you to quickly add the same symbol more than once to the
current FLD without having to go to the selection sheet every time.
The symbol is immediately available for placement on the FLD, and
no selection sheet is displayed.
Selecting a symbol To select an individual symbol in the FLD design screen or the
symbol selection screen (see Figure 6-7 and Figure 6-8, respectively),
proceed as follows:
1. Use the arrow keys on the keyboard or the mouse to move the
cursor to the appropriate symbol.
2. Make sure that the cursor is located anywhere on the appropriate
symbol.
3. Press <Enter> or click the left mouse button to select the symbol.
Placing a symbol Before you can place a symbol in the FLD, you must first choose its
(new) position. This can be done in two ways:
• use the arrow keys on the keyboard to move the symbol, or
• click the left mouse button, hold it, and "drag" the symbol.
Press <Enter> or click the left mouse button to "drop" the symbol into
its new position. The screen grid helps you choose the desired
position. If the symbol overlaps another symbol, a beep will sound
and a message is displayed on screen. You must then select another
position. You can cancel the operation by pressing <Esc>.
Copying a symbol To copy a symbol to another position in the current FLD, choose the
Main Symbol Copy
You must select a symbol in the design screen and a new position for
that symbol (see above). If required, you are prompted to enter the
symbol's variable data. The copied symbol will not have any
connections, which means that the existing connections of the
"source" symbol are not copied along.
Software Manual
Moving a symbol To move a symbol to another position in the current FLD with all
connections of this symbol broken, choose the following menu
options:
Main Symbol Move
that symbol (see page 6-19).
Moving inverters If you move a symbol, any inverters connected to it are replaced by
single lines.
Moving FSQRT, SQR, If you move square-root gates (FSQRT), square gates (SQR) or signal
or signal conversions conversions, their symbols are replaced by double lines.
Moving pulses If you move pulses, their symbols are replaced by single lines.
Dragging a symbol To move a symbol to another position in the current FLD with all
connections of this symbol remaining intact, choose the following
menu options:
Main Symbol draG
that symbol (see page 6-19). The new position that can be selected is
limited (because all connections must remain intact).
Changing a symbol To change the variable data of a symbol in the current FLD, choose
the following menu options:
Main Symbol Change
You must select the symbol in the design screen whose data you wish
to change (see page 6-19). You can then change all variable data of
that symbol. The old values are displayed as the default input. They
can be edited using the standard text-editing functions (see subsection
6.3.7). This option allows you, for example, to modify the tag number
of an input or the height of a gate without having to delete the symbol
first and replace it.
If the symbol to be changed is a line, you cannot change the type of

the line but only its length. If you select a line to be changed, the
cursor will jump to the nearest end point of the line.
Software Manual
If you change the tag number of an input, output or PID, you basically
choose a new I/O or PID from the variable database. The old I/O or
PID is then free for use again. If the new tag number you choose does
not already exist, all data must be entered again.
If you change the tag number using the 'System Configuration' option
of FSC Navigator, the variable will stay the same, only the tag number
will be different. You will then need to change all I/O or PIDs in the
FLDs to the new tag number.
Deleting a symbol To delete a symbol from the current FLD, choose the following menu
options:
Main Symbol Delete
You must select the symbol in the design screen that you wish to
delete (see page 6-19). The selected symbol is deleted from the screen
and the database. Before the symbol is actually deleted, you are asked
to confirm the operation. A backup copy is made which allows you to
recover it later. As long as the 'Undelete' option is displayed in the
Symbol menu, you can undelete the last deleted symbol.
Deleting inverters If you delete a symbol, any inverters connected to it are replaced by
single lines.
Deleting FSQRT, SQR, If you delete square-root gates (FSQRT), square gates (SQR) or
or signal conversions signal conversions, their symbols are replaced by double lines.
Deleting pulses If you delete pulses, their symbols are replaced by single lines.
Deleting transfer If you delete an off-sheet transfer symbol, the on-sheet transfer
symbols symbol on the destination FLD is deleted as well (providing it is not
connected to a signal line). If the on-sheet transfer on the destination
FLD is not deleted, the source in that transfer symbol is replaced by
'0' (zero), and all variables in the variable database are also deleted
(providing it is not connected to a signal line and it is not a
multi-transfer symbol). If the off-sheet transfer on the source FLD is
not deleted, the destination in that transfer symbol will be replaced by
'0' (zero), and all variables in the variable database belonging to it are
modified accordingly.
Software Manual
Undeleting To recover a symbol that was recently deleted, choose the following
a symbol menu options:
Main Symbol Undelete
A symbol can no longer be undeleted as soon as you have added a

new symbol to the FLD. As long as the 'Undelete' option is displayed
in the Symbol menu, you can undelete the last deleted symbol.
6.3.5 Working with Groups of Symbols (Blocks)
Defining a block In addition to manipulating individual symbols in the FLD design

screen (see Figure 6-7), you can also select groups of symbols
(blocks) that you can manipulate as a single unit. After you choose a
block manipulation command, you must first define the block. To do
this, proceed as follows:
1. "Draw" the rectangle that defines the block area. This can be done
in two ways:
− use the arrow keys on the keyboard, or
− click the left mouse button, hold it, and "drag" the block
rectangle.
All symbols in that area will be part of the block. The block is
marked by a dashed line.
2. Press <Enter> or click the left mouse button to select the block.
You can now manipulate the block as a whole.
To cancel the block definition or block manipulation, press <Esc> or

click the right mouse button.
Placing a block Before you can copy or move a selected block in the FLD, you must
first choose its new position. This can be done in two ways:
• use the arrow keys on the keyboard to move the block, or
• click the left mouse button, hold it, and "drag" the block.
Press <Enter> or click the left mouse button to "drop" the block into
its new position. The screen grid helps you choose the desired
position. If the block overlaps other symbols or if any connections are
incorrect, a beep will sound and a message is displayed on screen.
You must then select another position. You can cancel the operation
by pressing <Esc>.
Software Manual
Copying a block To copy an entire group of symbols to another position in the current
FLD, choose the following menu options:
Main Block Copy
You must first define the block in the design screen and a new
position for the select block (see above). If you then press <Enter> or
click the left mouse button to drop the block, FSC Navigator will
check the new position and the connections, and will perform any
border corrections, if required. If you enter <Esc>, you will return to
the situation that existed before this option was chosen.
If the block includes an input, output or transfer symbol, the x-

position of the block (or the y-position if the FLD is vertically
oriented) retains its old value, and only the y-position can be varied.
If you copy an I/O or a PID, their tag number is replaced by the
illegal, non-existing tag number '?'. This tag number must be changed
afterwards (using the 'cHange' option in the Symbol menu). On-sheet
transfers get the source number '0' (zero), and off-sheet transfers the
destination number '0' (zero).
If symbols with a sequence number are copied, sequence number
overflow can occur.
Moving a block To move an entire group of symbols to another position in the current
FLD with all connections of the symbols broken, choose the
Main Block Move
You must first define the block in the design screen and a new
position for the select block (see above). If you then press <Enter> or
click the left mouse button to drop the block, FSC Navigator will
check the new position and the connections, and will perform any
border corrections, if required. If you enter <Esc>, you will return to
the situation that existed before this option was chosen.
If the block includes an input, output or transfer symbol, the x-

position of the block (or the y-position if the FLD is vertically
oriented) retains its old value, and only the y-position can be varied.
If you move an I/O or a PID, their tag number is replaced by the
illegal, non-existing tag number '?'. This tag number must be changed
afterwards (using the 'cHange' option in the Symbol menu). On-sheet
transfers get the source number '0' (zero), and off-sheet transfers the
destination number '0' (zero).
Software Manual
If symbols with a sequence number are moved, sequence number
overflow can occur.
Deleting a block To delete an entire group of symbols from the current FLD, choose
Main Block Delete
You must define the block in the design screen that you wish to delete.
The block contents are deleted from the screen and the database.
Before the block is actually deleted, you are asked to confirm the
operation. A backup copy is made which allows you to recover it later.
As long as the 'Undelete' option is displayed in the Block menu, you
can undelete the block.
Undeleting To recover an entire group of symbols that was recently deleted,

a block choose the following menu options:
Main Block Undelete
This option can only be executed immediately after you have deleted a
block. As long as the 'Undelete' option is displayed in the Block menu,
you can undelete the block that was deleted earlier.
Saving a block To save an entire group of symbols to your hard disk, choose the
Main Block Save
You must define the block in the design screen whose contents you
wish to save to disk. You will be prompted to enter a file name. The
extension 'BLK' is assumed, and should not be entered. You should
also not enter a path. Long file names are not supported. If the file
name you entered already exists, you will be asked whether this file
should be overwritten. If you choose to overwrite, the block contents
are written to that file. The saved block can be loaded into any FLD
using the 'Load' option.
Software Manual
Loading a block To load a block that was previously saved to disk into the current
FLD, choose the following menu options:
Main Block Load
This option is only available if a file with extension BLK is present in

the project folder. If you choose this option, you will be prompted to
enter a file name. The extension 'BLK' is assumed, and should not be
entered. You should also not enter a path. Long file names are not
supported. If the file name you entered does not exist, you can enter
another name. If it does exist, FSC Navigator will load the block from
that file into the current FLD. It will check whether this block fits
within the screen size and if it does, it will display the block on the
screen. You can then drag it to its position. If the block size is almost
as large as the complete screen, you cannot drag it to another position.
It will then be placed at the center of the FLD, providing no block
overlap is detected. If the block cannot be placed anywhere because of
symbol overlap, you can abort the operation by pressing <Esc>. The
block is then deleted from the screen, but not from the hard disk.
The block will usually first be positioned on the place where it was
when it was saved. If the sheet borders are exceeded, the positions will
be corrected, if possible.
If the block contains symbols that are illegal for the sheet type, these
symbols are deleted, e.g. any output symbols in a block that is loaded
into a function block.
6.3.6 Drawing Connection Lines
Connection lines If you select a line (boolean or binary) on the selection sheet (see
Figure 6-9), you will return to the design screen.
Figure 6-9 Connection lines
Software Manual
You can draw lines in two ways:
• using the keyboard, and
• using the mouse.
Drawing lines using

the keyboard To draw connections lines using the keyboard, proceed as follows:
1. Use the arrow keys on the keyboard to move the cursor to the
starting point of the line, and press <Enter>.
2. If you now move the cursor (using the arrow keys) in any
direction, a line will be drawn in the design sheet.
3. If you want to make a 90° angle, press <Enter>, and continue in
the desired direction. If you press <Esc>, the line segment that
was drawn last is deleted.
4. To end the line at a connection point, press <Enter>. You will
then return to the menu.
Note:
You can only draw horizontal and vertical lines.
Drawing lines using

the mouse To draw connections lines using the mouse, proceed as follows:
1. Use the mouse to move the cursor to the starting point of the line,
and click the left mouse button.
2. If you now move the cursor (using the mouse) in any direction, a
line will be drawn in the design sheet.
3. If you want to make a 90° angle, click the left mouse button, and
continue in the desired direction. If you press <Esc>, the line
segment that was drawn last is deleted.
4. To end the line at a connection point, click the left mouse button.
You will then return to the menu.
Note:
You can only draw horizontal and vertical lines.
Making connections If you draw a line in the FLD and define a starting point or an end
point inside a symbol, the FLD design editor will automatically make
a connection to that symbol.
The line is automatically cut at the outer border of the symbol. You
will be asked for connection points again until the last drawn line is
Software Manual
connected at both ends. This means that you can continue drawing
lines until you press <Esc> or connect to the point that was chosen
last. A line is also automatically cut at the borders of the FLD control
function area. This cutting point is regarded as a connection point. An
input, output or transfer can later be connected there.
If you cross two lines, the vertical line will be broken at the cross
point, which means no connection is made between the lines. If lines
overlap, they will be combined into one single line.
If you try to make an invalid connection, a beep will sound. The
connection is not made, and the line segment that was drawn last will
be undone. Invalid connections are connections of incorrect signals to
certain symbols. For example, a timer can only have a boolean input
signal at its set input. Analog outputs can only be connected to a
binary signal, and calculation functions can only have binary inputs
and/or outputs.
Inputs and outputs of a function block are drawn as part of the

function block symbol to help the user make valid connections. The
same is true for registers and counters.
For logic functions, calculations, inputs, outputs, constants and timers,
the FLD design editor shifts connections that are made at the output
side of the symbol to the half height of the symbol.
If a line is drawn across a symbol, the largest of the line parts on the
input side, or the output side of the symbol is accepted as a connection
and the other part is erased from the screen.
6.3.7 Entering Information
Entering If any information needs to be entered, a prompt is displayed at the

information bottom of the screen.
Entering numbers If the input must be numeric, the editor will check after each
character input whether this condition is satisfied. A beep will sound
when anything else but a number is entered, and the character will not
be accepted.
Software Manual
Choosing If you must choose from a number of predefined options, you can
from a list toggle between them by pressing <Space>. If it is possible to toggle
between options, the following message will be displayed on screen:
'Press <Space> to alter'.
Entering text Characters that you enter may be turned into uppercase characters
(e.g. when location for input is entered).
The editor only accepts a certain number of characters depending on
the type of input. If you try to enter more characters than allowed, a
beep will sound. If you enter fewer characters than allowed, the
remaining positions are filled with spaces. If you enter any invalid
characters, a beep will sound.
There are two keys that can be pressed to exit a text box:
• <Enter>, and
• <Esc>.
<Enter> Use this key to end and confirm the text input (and move to the next
line, if applicable).
<Esc> Use this key to abort the text input and return to the menu.
Please note that if you press <Esc> while entering an FLD number for
a multiple sheet transfer, the references that were entered before the
current one are accepted and placement continues.
Editing single The FLD design editor generates a default value for most input,
text lines which is either an empty string or a value that was previously entered.
If you wish to edit the default input, the following key commands are
available:
à> or
<à
<Ctrl>+<D> Use this key to move the cursor one position to the right.
ß> or
<ß
<Ctrl>+<S> Use this key to move the cursor one position to the left.
<Backspace> or
<Ctrl>+<H> Use this key to delete the character left of the current cursor position.
<Home> or
<Ctrl>+<A> Use this key to move the cursor to the beginning of the line.
Software Manual
<End> or Use this key to move the cursor to the end of the line (after the last
<Ctrl>+<F> character).
<Del> or
<Ctrl>+<G> Use this key to delete the character at the current cursor position.
<Ins> or
<Ctrl>+<V> Use this key to switch between insert and overwrite mode.
<Ctrl> + <T> Use this key combination to delete all characters from the current
cursor position to the end of the line.
<Ctrl> + <Y> Use this key combination to delete the entire line (regardless of the
cursor position on the line).
<Ctrl> + <P> Use this key combination to make a printout of the displayed screen.
You can go on with editing after the printout is completed (Epson
MX-80 only).
<PgUp> Use this key combination to make the cursor step twice as big. The
maximum value is 22x grid.
<PgDn> Use this key combination to make the cursor step twice as small. The
minimum value is 0.5x grid.
Editing multiple When editing text blocks rather than single lines, the following key
text lines commands are available (in addition to the ones mentioned above):
à> or
<à Use this key to move the cursor one position to the right. If the cursor
<Ctrl>+<D> is at the end of a line, it will move to the first position of the next line.
ß> or
<ß Use this key to move the cursor one position to the left. If the cursor
<Ctrl>+<S> is at the begin of a line, it will move to the last position of the
previous line.
↑> or
<↑
<Ctrl>+<E> Use this key to move the cursor one line up.
↓> or
<↓
<Ctrl>+<X> Use this key to move the cursor one line down.
<PgUp> or
<Ctrl>+<R> Use this key to move the cursor to the first line.
<PgDn> or
<Ctrl>+<C> Use this key to move the cursor to the last line.
Software Manual
6.3.8 Selection Lists
Selection lists There are several situations in which the FLD design editor can help
you select data to be inserted by means of a selection list that contains
valid input data. You can call these selection lists by pressing <?>
during editing. Figure 6-10 below shows an example of a selection
list.
Figure 6-10 Example of a selection list
To select a component, move the cursor to the appropriate line and

press <Enter>. If you must enter a string that is non-numerical (e.g. a
tag number), you can also enter some characters first and then enter
<?>. In that case only the input options that start with these characters
are listed. The following key commands are available in selection
lists:
<Esc> Use this key to exit a selection list and return to editing mode.
←>, <→
<← →>, <↑
↑>, <↓
↓> Use these keys to move the cursor bar to the appropriate line.
<PgDn> Use this key to view the next page of options.
<PgUp> Use this key to view the previous page of options.
<Enter> Use this key to select the highlighted option.
Software Manual
Calling up
selection lists Selection lists can be called up in the following cases:
• Input of tag numbers of inputs or outputs.
The selection list contains the tag number, service and qualification
(see Figure 6-10).
• Input of source FLD or destination FLD for the selection of a
sheet reference.
The selection list contains all unlinked sheet references as well as
the service text and the FLD number. Also listed are all off-sheet
references which do not contain the maximum allowed number of
sheet references.
• Input of sequence number for selection of a sheet reference.
The selection list contains all unlinked sheet references on the
destination FLD that was entered before (together with their Service
attribute).
• During input of service of a sheet reference, the tag number of an
input or an output that is directly connected to the reference symbol
on the source FLD of the sheet reference. The selection list only
contains the inputs and outputs that are placed on the source FLD.
• Input of a tag number of a PID.
The selection list also includes the PID number.
• Input of the sheet number of a function block or equation block
when you want to select a function block or equation block. The
selection list contains the fourth descriptive text of the title block as
well as the FLD number of the function block or the equation block.
• Input of an FLD number in the option "New".
All FLD numbers of existing FLDs and the fourth descriptive text
of the title block will be listed.
Software Manual
6.4 FLD Types (Block Types)
Block type The FLD type (block type) is specified in the title block (see
subsection 6.5). There are six different block types:
• Program block
• Function block
• Equation block
• Comment block
• FLD index
• Tag number index.
Program block This is a normal FLD that defines the application.
Function block This is an FLD that is used as a subroutine function in other FLDs
(program blocks or other function blocks). Please note that function
block FLDs can only be called by FLDs that have a lower number
than the function block FLD.
Function blocks must have an FLD number of 500 or higher (except

when it is converted from a software version before 2.78). In the demo
version of FSC Navigator, function blocks can be defined in FLD 5 or
higher.
Function block FLD numbers must all be higher than the program
block FLD numbers. Between the program block FLDs and the
function block FLDs, there must be at least one FLD with a block type
that is not a program block or a function block.
For design considerations for function blocks refer to subsection 6.9.4

on page 6-81.
Equation block This is an FLD that contains an equation approximation, which can
be used as a macro function on other functional logic diagrams.
Please note that equation block FLDs can only be called by FLDs that
have a lower number than the equation block FLD.
Equation blocks must have an FLD number of 500 or higher (except

when it is converted from a software version before 2.78). In the demo
version of FSC Navigator, function blocks can be defined in FLD 5 or
higher.
Software Manual
Equation block FLD numbers must all be higher than the program
block FLD numbers. Between the program block FLDs and the
equation block FLDs, there must be at least one FLD with a block
type that is not a program block or a function block.
For design considerations for equation blocks refer to subsection 6.9.5

on page 6-82.
Comment block This is an FLD that contains descriptive texts and/or symbols which
are not placed in the variable database (e.g. cover sheet, legend of
symbols). FLDs of this type are ignored by the compiler.
This type of FLD is typically used as a cover sheet, legend of symbols
or just a comment between two normal FLDs.
A useful editor command in this respect is:

Main Symbol Forward Symbol set
This option is only active when you are editing a comment block. It
allows you to select another symbol selection sheet. Press <Space> to
toggle between the available options, and press <Enter> to select an
option. The new selection sheet is now loaded into memory. If you
then choose the 'New' option in the Symbol menu to select a symbol,
you will see another selection sheet.
Example:
You wish to make a legend of symbols and you want to select a
function block input symbol. The current selection sheet is the
program block selection sheet. By pressing <Space> once, the
command line displays 'Function block'. Press <Enter>, and the
function block selection sheet will be loaded.
FLD index This type of FLD contains no logics, but is only used for printing
FLDs. It is used to generate an index of all FLDs used in the
application. Once an FLD index has been defined, it is updated
automatically by FSC Navigator. FLDs of this type are ignored by the
compiler.
For each FLD, the FLD index lists:

• the last revision date, and
• a description (Text4 field from the title block).
Software Manual
If the list of FLDs does not fit on a single FLD, it is continued on the
next FLD(s). You must therefore make sure that sufficient empty
FLDs are reserved after the FLD index.
Since this FLD type contains no logics, no design screen is displayed,
and only a limited main menu is available (Title block / New / eXit).
An FLD index can only be defined once. The only way to delete an
FLD index is to change the block type to a non-index FLD. Next,
open this FLD and close it again (if desired after making a design).
Note:
For details on printing FLDs refer to Section 7 of this manual
("Printing").
Tag number index This type of FLD contains no logics, but is only used for printing
FLDs. It is used to generate an index of all I/O tag numbers used in
the application. Once a tag number index has been defined, it is
updated automatically by FSC Navigator. FLDs of this type are
ignored by the compiler. For each I/O, the tag number index lists:
− the I/O type,
− the tag number, and
− the FLD(s) on which the I/O signal is used.
The list also includes any on-sheet transfers where the service attribute
is identical to a tag number (e.g. repeated inputs).
Since this FLD type contains no logics, no design screen is displayed,
and only a limited main menu is available (Title block / New / eXit).
Note:
For details on printing FLDs refer to Section 7 of this manual
("Printing").
Software Manual
6.5 Title Block
Title block The title block screen is always the first screen to appear if a new
FLD is defined. It can also be called up later by choosing the 'Title
block' option from the main menu. This allows you to modify the title
block information at any time.
The title block contains information that is needed during the design
of the FLDs: block type, unit, subunit, revision, engineer, design date,
and a maximum of nine descriptive texts. Most of this data is also
used in the hardcopy of the FLD.
The title block will usually not be entirely empty, even if a new FLD
is defined. Some data fields will normally already be filled. Their
values are copied from the last FLD you worked on (e.g. engineer,
design date, unit, subunit). This is done to minimize the required user
input.
Figure 6-11 Title block screen
Software Manual
Fields The title block screen contains the following fields:
• FLD number,
• Block type,
• Unit,
• Subunit,
• Revision,
• Engineer,
• Design date, and
• Text1 to Text9.
Each of these fields is explained in more detail below.
FLD number This field displays the number of the FLD whose title block is being
edited. It cannot be modified.
Block type This field specifies the type of the current FLD:
• Program block
• Function block
• Equation block
• Comment block
• FLD index
• Tag number index.
For details refer to subsection 6.4 on page 6-32.
Unit and Here you can enter the unit and subunit of the FSC system that the
subunit FLD applies to. These fields can only be edited if the block type is set
to 'Program block'. In all other cases, these fields contain the text
'Undefined', and cannot be modified.
Note:
A function block can be used in any part of the logics, which
means that the unit and subunit are not set. This is why the unit
and subunit of all variables in a function block are identified
when the function block is placed in another FLD.
Software Manual
Revision Here you can enter revision data for the current FLD. You can add a
maximum of six revisions for each FLD. A revision consists of a
revision number, revision date, and revision description.
For a new FLD, the revision number will be set to its "zero revision",
the date will be set to today's date (retrieved from the real-time clock
in your PC), and the description will be 'FIRST ISSUE'.
For details on FLD revision control refer to subsection 6.6.1.

Please note that the revision data in the title block only applies to the
current FLD. There is also an option that allows you to edit the
revision of the entire application. For details refer to subsection 6.6.2.
Engineer Here you can enter your name or initials, with a maximum length of
10 characters.
Design date Here you can enter the creation date of the FLD. For a new FLD, this
field will default to the current date (retrieved from the real-time
clock in your PC). To store the date, simply press <Enter>. You can
also edit it first, and then press <Enter> to record it.
The default date format is DD-MM-YYYY (e.g. 24-01-1999).
Text1 to Text9 These fields allow you to enter descriptive information on the current
FLD. They are primarily used when printing FLDs. The position
where these texts will be printed on the hardcopy depends on the
symbol library that is used for the FLD. For symbol library SYM1,
Text4 is always used as the FLD description (e.g. in an FLD index).
Key commands The following key commands are available in the title block screen:
↓>
<Enter> or <↓ Press this key to move the cursor to the next field.
<PgDn> Press this key to move the cursor to go to the last field in the screen
(Text9). If you press this key in the Revision pop-up window, this
window will be closed and you will move to the 'Text9' field.
If you press <PgDn> at the bottom of the title block (Text9 field), you
will leave the title block screen and go to the design screen (see Figure
6-7).
<PgUp> Press this key to move the cursor to go to the first editable field in the
screen (Block type). If you press this key in the Revision pop-up
window, this window will be closed and you will move to the 'Block
type' field.
Software Manual
If you press <PgUp> at the top of the title block (Block type field),
you will move to the last field (Text9).
↑>
<↑ Press this key to move the cursor to the previous field.
If you press <↑> at the top of the title block (Block type field), you
will move to the last field (Text9).
<Esc> Press this key to leave the title block screen and go to the design
screen (see Figure 6-7). If you press this key in the Revision pop-up
window, this window will be closed and you will go (or return) to the
design screen.
Title block Information from the title block is used on printouts of FLDs. An
in printouts FLD printout will always have an information block at the bottom:
E Customer: Text5 Text1 Text2

D Text3 Text4
Principal: Text6
C
SAFETY MANAGEMENT Tel.: +31 73-6273273 Date: By:
B Plant 1: Text7 SYSTEMS Fax: +31 73-6219125 Drawing number:
A Plant 2: Text8 P.O. Box 116
0 5201 AC Serial Project Unit Sheet Cont’d
Rev. Date Description Chk’d Req/Order no.: Text9 's-Hertogenbosch Code Code
Figure 6-12 Title block on FLD printout
Please note that the information block also contains data from the
description fields which were defined using the 'System
Configuration' option of FSC Navigator (Installation \ Description).
Software Manual
6.6 Revision Control
6.6.1 FLD Revisions
FLD revisions Revision data for every individual FLD is recorded in the FLD's title
block (in the Revisions field). This enables you to use version control
and keep track of modifications. There are two ways to update the
revision of an FLD:
• by editing the revision window that is displayed automatically after
any modification to the FLD, or
• by editing the Revision field in the FLD's title block.
Revision window If you changed something in an FLD and you save or close that FLD,
a revision window will first be displayed (see Figure 6-13).
This window will only appear if:
• the application was compiled before, and
• you did not make any changes in the FLD on the same day.
This means there will only be one revision per day.
Figure 6-13 Revision window
Software Manual
The cursor will be located in the 'No.' field immediately below the last
revision. You can accept the default suggestion, or provide a different
revision indicator. Press <Enter> or <→> to move to the 'Date' field.
This field will contain the current date (as retrieved from the real-time
clock of your PC). You can accept this date, or modify it accordingly.
(Please note there is no date validity check whatsoever, so you can
enter any text.) Press <Enter> to move to the 'Description' field. Here
you can enter a description of the revision, although this is not
required. If you press <Enter> in the 'Description' field, the revision is
recorded, and the revision window is closed.
If you press <Esc> at any time, the revision window is closed and any
changes to the revision data are discarded.
Notes:
1. The FLD whose revision data is being edited is shown in the
header of the pop-up window.
2. As the revision date is taken from the real-time clock in your
PC, you must make sure the clock is correctly set.
3. The date format used in the revision window depends on the
Regional Settings as laid down in the Windows NT/2000
Control Panel.
Title block You can also review and modify the revision data of an FLD at any
time by calling up its title block (choose the 'Title block' option from
the main menu) (see Figure 6-14 on the next page)
The cursor will be located in the 'No.' field immediately below the last
revision. You can accept the default suggestion, or provide a different
revision indicator. Press <Enter> or <→> to move to the 'Date' field.
This field will contain the current date (as retrieved from the real-time
clock of your PC). You can accept this date, or modify it accordingly.
(Please note there is no date validity check whatsoever, so you can
enter any text.) Press <Enter> to move to the 'Description' field. Here
you can enter a description of the revision, although this is not
required. To close the revision window and record the new revision
data, press <PgUp>, <PgDn> or <Esc>. If you press <PgUp> or
<PgDn>, you will remain in the title block screen; pressing <Esc> will
bring you back to the main menu.
To cancel a previous revision, simply delete both the date and

description and press <PgUp>, <PgDn> or <Esc>.
Software Manual
Figure 6-14 Revision data in title block
Notes:
1. The FLD whose revision data is being edited is shown in the
header of the pop-up window.
Control Panel.
6.6.2 Application Revisions
Application In addition to FLD-specific revisions, you can also create revision

revisions updates for an entire project rather than for individual FLDs.
To use the application revision option, do the following:
1. From the main FLD editor menu, choose the 'Forward' option.
2. From the submenu, choose the 'aPpl. revision' option.
FSC Navigator will now search for the FLD with the highest
revision number (i.e. the most recent date), and will display that
FLD's revision information (see Figure 6-13).
Software Manual
3. You can now enter a revision indication (or accept the default
suggestion), the revision date, and a description that will apply to
the entire project.
The new project revision becomes effective as soon as you press the
<Enter> key with the cursor in the last 'Description' field. FSC
Navigator will then automatically modify the revision of all FLDs in
the application.
You can press <Esc> any time to abort the revision change. Any
modifications made will then be discarded.
Notes:
1. The FLD in the application whose revision date is the most
recent is shown in the header of the pop-up window.
2. You must enter a value in all fields, including the
'Description' field, before the global revision is accepted and
all FLDs are modified.
Control Panel.
Software Manual
6.7 Appending Applications
Appending To append one or more subapplications to the current application,

an FLD choose the following menu options:
Main Forward Append appl.
Please note that this option is not available if the FLD is empty or if
on-line modification is active. If you append an application, all actions
and changes on the appended application are logged in a special log
file (with extension APP) that can be viewed or printed later (using the
'View Logs' option of FSC Navigator). The log file also lists any
inconsistencies in either application. Some inconsistencies with regard
to the functional logic diagrams are corrected. For example, an output
or PID that is used twice is automatically deleted. Also, an input that
is used more than once per CPU is replaced by a repeated input
symbol (if possible).
Considerations Please note the following considerations:

1. You can successively append a subapplication to the main
application from which you do all append operations. You can
keep on appending applications until you enter <Esc> or until you
have appended 255 applications.
2. No backup is made of the original main application that other
applications are appended to. All subapplications to be appended
will remain unchanged. It is therefore recommended that you back
up the main application before appending anything.
3. There are two ways to append an application.
− The subapplication to be appended must be located in the same
FSC path as the main application. You only need to enter the
name of the subapplications and not their paths. The path to the
application is automatically generated.
− You can also append an application from a floppy disk. No FSC
path is used in that case. Just enter the name of the drive and the
name of the subapplication, e.g. A:\TEST1_1. The application
files must all be located in the root of the floppy disk.
4. FLD numbers in the main application are not allowed to be
present in any of the subapplication folders.
5. All function block FLDs in the subapplications must have an FLD
number which is at least two higher than the largest FLD number
of the program block FLD in the main application.
Software Manual
6. No check is performed whether tag number indexes or sheet
indexes are placed more than once. If they are present in more
than one application, they will be generated more than once
during printing/plotting. It is recommended that you place such
FLDs in the main application.
7. If the configuration type has been defined in both applications,
they must be identical. It is therefore recommended that you
create a main application first and then make copies of the main
application while giving new names to the subapplications.
8. If the configuration type has been defined in both applications, the
rack positions in each cabinet must be the same in both
applications. It is therefore recommended that you create a main
application first and then make copies of the main application
while giving new names to the subapplications.
9. If the configuration type has been defined in both applications, the
Fault Reset and Force Enable tag numbers must be identical in
both applications. It is therefore recommended that you create a
main application first and then make copies of the main
application while giving new names to the subapplications.
10. If a module has been defined in a certain rack and position in both
applications, they must be identical (including their safety
relation). If a rack and position have been defined in a
subapplication, but not in the main application, it is copied to the
main application.
11. The main application has priority over subapplications with regard
to the use of certain I/O, hardware allocations, etc. If possible, I/O
is copied, otherwise it is deleted or replaced by a repeated input
and placed in the subapplication. I/O that exists in the data file but
is not placed in the main application, will be copied to the main
application. Inputs that are used in both applications but for
different CPUs, are also copied to the main application.
12. PIDs may only be placed once in the FLDs. This means PIDs will
be deleted when they are placed in both applications. If a PID
from a subapplication does not exist in the main application, it is
copied to the main application. If required, the PID number may
be changed. If a PID from a subapplication already exists in the
main application but has not been placed in the FLDs yet, the
adjustments of the PID in the subapplication are copied to the
main application and the PID number remains unchanged.
13. If the hardware allocation of an I/O is not already used in the main
application, it is copied to the main application, otherwise it is
cleared. The same is true for the COM port assignment of
variables with location 'COM' or 'FSC'.
Software Manual
14. Multiplexer numbers or alarm group numbers may be changed
during an append operation. If no more multiplexers or alarms can
be placed in the main application, the variable will be deleted.
15. All delete or replace operations and all errors during the append
are written to a log file named <main application name>.APP.
You can output this file to a printer afterwards or displayed it on
screen using the 'View Log' option of FSC Navigator. For details
on log files refer to Section 9 of this manual.
Note:
Two variables are considered identical if both their types and tag
numbers are identical.
Software Manual
6.8 FLD Symbols
Symbol set The FLD design editor uses a symbol set which is divided into a
number of subsets:
1. Non-functional symbols (see subsection 6.8.1)
2. Connection lines (see subsection 6.8.2)
3. Logical functions (see subsection 6.8.3)
4. Compare functions (see subsection 6.8.4)
5. Calculation functions (see subsection 6.8.5)
6. Registers and counters (see subsection 6.8.7)
7. Constants and signal conversions (see subsection 6.8.8)
8. Function blocks (see subsection 6.8.9)
9. Equation blocks (see subsection 6.8.10)
10. PIDs (see subsection 6.8.11)
11. Timers (see subsection 6.8.12)
12. Inputs and outputs (I/O) (see subsection 6.8.13)
13. Sheet transfers (see subsection 6.8.14)
14. Flip-flops (see subsection 6.8.15)
15. Texts (see subsection 6.8.16)
Each of these symbols is explained in the subsequent subsections.
6.8.1 Non-Functional Symbols
Non-functional
symbols The non-functional symbols are:
• Basic sheet symbol,
• Sheet identification symbol (title block), and
• Revision cloud.
Each of these symbols is explained in more detail below.
Software Manual
Basic sheet symbol The basic sheet is a symbol which divides the FLD into three areas:
The basic sheet symbol is automatically placed when an FLD is

created.
Figure 6-15 Example of basic sheet symbol as defined in symbol

library SYM1 (screen view)
FLD identification Each FLD also has a title block at the bottom, which contains all
symbol (title block) FLD-specific data. The FLD identification symbol is not visible for
the user, but when you print the FLD, this symbol is drawn as an
information block under the FLD.
For details on the title block refer to subsection 6.4.
The FLD identification symbol (title block) is automatically placed

when an FLD is created.
Software Manual
Revision cloud This symbol consists of dashed lines which, during drawing, are
automatically connected by FSC Navigator until the first point is
connected to the last point or <Esc> is pressed. Clouds are used to
mark parts of the logics that have been revised.
6.8.2 Connection Lines
Connection lines Lines represent the connection between two components. They can be
drawn vertically or horizontally, but the direction has no functional
meaning. When lines cross each other, they are not connected (the
program automatically makes a break in the vertical line). When lines
intersect, they are connected, and the line is split into two lines at the
connection point, unless a connection is made at an end point of a
line.
Single lines and Single lines in FLDs represent boolean signals.

double lines Double line in FLDs represent binary signals.
Boolean signals, Binary signals,

e.g. 0 / 1 e.g. 23
On / Off -13
Start / Stop 19.75
High / Low 2.47E13
Figure 6-16 Lines: boolean signals and binary signals
Analog I/O converter A third line type (thick line) is used for analog signals as represented
in the analog I/O converter symbols:
Analog signals
Figure 6-17 Lines: Analog I/O converter
Software Manual
Crossing of signals Crossing of signals is represented as follows:
Boolean signals Binary signals
Figure 6-18 Lines: crossing of signals
6.8.3 Logical Functions
Logical functions The table below lists the logical functions that are available in FLDs:
Table 6-1 Available logical functions in FLDs

AND functions OR functions Inverter functions
AND gate OR gate INVERTER
AND filter XOR gate BUFFER INVERTER
NAND gate NOR gate
Rotated AND gate XNOR gate
Rotated AND filter Rotated OR gate
Each of these logical functions is discussed in more detail below.
AND functions The following AND functions are available:

• AND gate,
• AND filter,
• NAND gate,
• Rotated AND gate, and
• Rotated AND filter.
Software Manual
AND gate The symbol height of the AND gate can be varied to connect binary
input signals or to upgrade the layout of the drawing.
a The maximum number of boolean inputs is 26.
b & d
c Function: d=a·b·c · = AND
AND filter The symbol height of the AND filter can be varied to connect binary
d
The maximum number of boolean inputs is 26.
a & e There may only be one binary input. The position of this input can be
b
chosen at the input side of the symbol.
c
Function: d=a·b·c=1 Þ e=d · = AND

d=a·b·c=0 Þ e=0
NAND gate The symbol height of the NAND gate can be varied to connect binary
b & d
c Function: d = –(a · b · c) · = AND
Rotated AND gate The symbol width of the AND gate can be varied to connect binary
a b c
& Function: d=a·b·c · = AND
Rotated AND filter The maximum number of boolean inputs is 25. The number of binary
a b c d inputs can only be one. The position of this input can be chosen at the
input side of the symbol.
& Function: a·b·c=1 Þ e=d · = AND

a·b·c=0 Þ e=0
e
Software Manual
OR functions The following OR functions are available:
• OR gate,
• XOR gate,
• NOR gate,
• XNOR gate, and
• Rotated OR gate.
OR gate The symbol height of the OR gate can be varied to connect binary
b ≥ 1 d
c Function: d=a+b+c + = OR
XOR gate The XOR gate only allows two inputs.

The symbol height cannot be varied.
a
=1 c Function: c = (–a)·b + a·(–b)

b
Results: a b c · = AND
0 0 0 + = OR
0 1 1 (–) = Inversion
1 0 1
1 1 0
NOR gate The symbol height of the NOR gate can be varied to connect binary
b ≥1 d
c Function: d = –(a + b + c) + = OR
(–) = Inversion
XNOR gate The XNOR gate only allows two inputs.

a
=1 c Function: c = (–a)·(–b) + a·b
b
Results: a b c · = AND
0 0 1 + = OR
0 1 0 (–) = Inversion
1 0 0
1 1 1
Software Manual
Rotated OR gate The symbol height of the OR gate can be varied to connect binary
a b c input signals or to upgrade the layout of the drawing.
≥1 Function: d=a+b+c + = OR
Inverter
functions The following INVERTER functions are available:
• Inverter, and
• Buffer inverter.
INVERTER The inverter can be placed:

a b − at the front of logical functions
− at the output side of a pulse
− at the end of a timer or a flip-flop
− at the set and reset input of a timer or a flip flop
− at the front or the end of rotated logical functions.
Function: b = (–a)
INVERTER (example)
This is an example of an INVERTER function:
a Function: c = (–a) · b · = AND
& c (–) = Inversion
b
BUFFER INVERTER The buffer inverter only allows one input.

a 1 b Function: b = (–a) (–) = Inversion
Software Manual
6.8.4 Compare Functions
Compare functions The table below lists the compare functions that are available in
FLDs:
Table 6-2 Available compare functions in FLDs

Equal functions Greater than functions Smaller than functions
EQUAL gate GREATER THAN gate LESS THAN gate
NOT EQUAL GREATER THAN OR LESS THAN OR

gate EQUAL gate EQUAL gate
Each of these compare functions is discussed in more detail below.
Equal functions The following EQUAL functions are available:

• EQUAL gate, and
• NOT EQUAL filter.
EQUAL (EQ) gate The EQUAL gate only allows two inputs.
a
= c Function: a=b Þc=1 <> = NOT EQUAL
b a <> b Þ c = 0 = = EQUAL
NOT EQUAL (NEQ) gate The NOT EQUAL gate only allows two inputs.
a
= c Function: a <> b Þ c = 1 <> = NOT EQUAL
b a=b Þc=0 = = EQUAL
Software Manual
Greater than
functions The following GREATER THAN functions are available:
• GREATER THAN gate (GT), and
• GREATER THAN OR EQUAL gate (GTE).
GREATER THAN (GT) The GREATER THAN gate only allows two inputs.
gate The symbol height cannot be varied.
a
Function: a>bÞc=1 > = GREATER THAN
> c
a≤bÞc=0
b
GREATER THAN OR The GREATER THAN OR EQUAL gate only allows two inputs.
EQUAL (GTE) gate The symbol height cannot be varied.
a
Function: a≥bÞc=1 ≥ = GREATER THAN
≥ c
a<bÞc=0 OR EQUAL
b
Less than
functions The following LESS THAN functions are available:
• LESS THAN gate (LT), and
• LESS THAN OR EQUAL gate (LTE).
LESS THAN (LT) gate The LESS THAN gate only allows two inputs.
a
< c Function: a<bÞc=1 < = LESS THAN

b a≥bÞc=0
LESS THAN OR EQUAL The LESS THAN OR EQUAL gate only allows two inputs.
gate (LTE) The symbol height cannot be varied.
a
Function: a≤bÞc=1 ≤ = LESS THAN
≤ c
a>bÞc=0 OR EQUAL
b
Software Manual
6.8.5 Calculation Functions
Calculation The table below lists the calculation functions that are available in
functions FLDs:
Table 6-3 Available calculation functions in FLDs

ADDITION MULTIPLY
SUBTRACT DIVIDE
Each of these calculation functions is discussed in more detail below.
Important!
1. Calculations on invalid numbers (e.g. divide by 0, or square
root of negative numbers) or results out of range of the
chosen signal type (e.g. 100 + 73 is out of range for signal
type byte) will result in a total system shutdown.
2. If an overflow occurs for a binary code decimal (BCD)
signal, it is clamped to its maximum value.
ADDITION (ADD) gate The symbol height of the ADDITION gate can be varied to connect
binary input signals or to upgrade the layout of the drawing.
a The maximum number of binary inputs is 26.
b + d
c Function: d·= a + b + c + = ADDITION
SUBTRACT (SUB) gate The SUBTRACT gate only allows two inputs.
a
_ c Function: c=a–b – = SUBTRACT
b
MULTIPLY (MUL) gate The MULTIPLY gate only allows two inputs.
a
X c Function: c=axb x = MULTIPLY
b
Software Manual
DIVIDE (DIV) gate The DIVIDE gate only allows two inputs.
a
÷ c Function: a÷b ÷ = DIVIDE
b
For floating point numbers, a real divide is taken.
For byte/word/ long numbers, a divide-with-truncation (DIV) function
is used (e.g. 16 ÷ 5 = 3).
Important!
If b = 0, the system will shut down!
6.8.6 Mathematical Functions
Mathematical The table below lists the mathematical functions that are available in
functions FLDs:
Table 6-4 Available mathematical functions in FLDs

SQUARE ROOT NATURAL LOGARITHM
SQUARE EXPONENT
Each of these calculation functions is discussed in more detail below.
Important!
1. Calculations on invalid numbers (e.g. divide by 0, or square
root of negative numbers) or results out of range of the
chosen signal type (e.g. 100 + 73 is out of range for signal
type byte) will result in a total system shutdown.
2. If an overflow occurs for a binary code decimal (BCD)
signal, it is clamped to its maximum value.
The mathematical functions can be selected by choosing the following

symbol in the symbol selection sheet:
Figure 6-19 Selection symbol for mathematical functions in FLD
Software Manual
You are then prompted to choose which mathematical function should
be used: SQR (square), SQRT (square root), EXP (exponent), or LN
(natural logarithm). Press <Space> to toggle between the available
options, or press <?> to choose from a list.
SQUARE ROOT The SQUARE ROOT gate only allows one input.
(SQRT) gate The symbol height cannot be varied.
Function: b = √a
a √Χ b
A square root function always gives a floating point result.
Important!
If a < 0, the system will shut down!
SQUARE (SQR) gate The SQUARE gate only allows one input.
a x² b Function: b = a² = a x a x = MULTIPLY
A square function always gives a floating-point result.
NATURAL LOGARITHM The NATURAL LOGARITHM gate only allows one input.
(LN) gate The symbol height cannot be varied.
Function: b = ln(a)
a ln(x) b
A natural logarithm function always gives a floating-point result.
x
EXPONENT (E ) gate The EXPONENT gate only allows one input.
a ex b Function: b = ea e = base of natural logarithm

system
An exponent function always gives a floating-point result.
Software Manual
6.8.7 Counters and Registers
COUNTER All input and output signal types are specified in the symbol.
a CU =Max f
b CD A counter can be used for counting functions.
g
c S Output f become 1 if the counter reaches the maximum counter value
d Counter (1 ≤ Max ≤ 8191). If the counter reaches the value Max+1, it is
O h
e R automatically reset to 0.
a = Count up f = Counter maximum

b = Count down g = Counter output value
c = Set h = Counter value '0'
d = Preset counter value
e = Reset
Function a b c d e f g h
Reset – – – – 1 0 0 1
Set – – 1 x 4) 0 – 1) x – 2)
Count down 0 1 0 – 0 0 g–1 0
Count up 1 0 0 – 0 0 g+1 0
No change – – 0 – 0 f g – 3)
– = value does not matter.
Notes:
1) If x = Max, then f = 1; else f = 0
2) If x = 0, then h = 1; else h = 0
3) If g = 0, then h = 1; else h = 0
If g = Max, then f = 1; else f = 0
4) If x < 0 or x > Max, then trip.
The boolean inputs CU and CD are edge-sensitive only (rising edge).
Valid connection combinations are:

− Set and value; others arbitrary.
− Count up; others arbitrary.
− Count down; others arbitrary.
Software Manual
REGISTER All input and output signal types are specified in the symbol.
a CU
b CD A register can be used as a:
f
− storage element of intermediate calculation results,
c L
d Register
− memory element for numbers, and
e C T
− counter for large numbers.
a = Count up d = Preset register value

b = Count down e = Clear
c = Load f = Register output value
Function a b c d e f
Clear – – – x 1 0
Load – – 1 y 0 y
Count down 0 1 0 f 0 f–1 (every cycle)
Count up 1 0 0 f 0 f+1 (every cycle)
Unchanged – – 0 v 0 x
– = value does not matter.
T=B Byte (8 bits)

T=W Word (16 bits)
T=L Long (32 bits)
T=F Floating point (32 bits)
The boolean inputs CU and CD are level-sensitive. This means that, in

order to prevent CU/CD every program cycle, a pulse gate should be
connected to the corresponding signal.
Count up and count down are not possible for floating point registers.
If T= Float, the CU and CD inputs may not be connected.
Valid input combinations are:

− Load and value; others arbitrary.
− Count up, Load and value; others arbitrary.
− Count up and Clear; others arbitrary.
− Count down, Load and value; others arbitrary.
− Count down and Clear; others arbitrary.
Software Manual
6.8.8 Constants and Signal Conversions
CONSTANTS Function: constant value.

T value
T: B = Byte (8 bits)
W = Word (16 bits)
L = Long (32 bits
F = Floating point (32 bits)
The constant is entered in the logics and cannot be changed during

program execution but only by modification of the logics.
Function: i = 1
This is a constant boolean signal. Only one boolean output or an
1 i
inverter may be connected.
SIGNAL CONVERSION
Function:
S This function checks whether the value of the input symbol is within
the range of the type T. If the input value is out of range, the FSC
T system will shut down due to calculation overflow.
If the source value does not fit into the target (e.g. conversion of
-40000 from 'F' to 'W'), the FSC system will shut down.
S = Source signal type (before conversion)

T = Target signal type (after conversion)
Only downward conversions are allowed (see table below).

Source Target ('To')
('From') B W L F
B – No No No
W Yes – No No
L Yes Yes – No
F Yes Yes Yes –
B = Byte (8 bits)
W = Word (16 bits)
L = Long (32 bits
Software Manual
Notes:
1. If, for example, a word-to-byte conversion has been defined
and during translation it appears that the destination type
must be word, the conversion symbol is corrected to the
trivial word-to-word conversion, which is ignored by the
compiler. You can use the FLD design editor to delete the
conversion.
2. In a float-to-word conversion, all decimal digits are
discarded. Decimal numbers are not rounded, but they are
truncated. This means that 4.9 becomes 4, and –4.9 becomes
–4. To retain accuracy, you should keep in mind what the
possible range of the floating point signal is. For a signal
between 1 and 1000, the maximum deviation is 1/1000 =
0.1%. For a signal between 0 and 5, the maximum deviation
is 1/5 = 20%, which is quite significant. In the latter case, it
could be better to increase the scale.
6.8.9 Function Blocks
A
A function block is a subroutine symbol that must be created on
D
another FLD first. This FLD must have a higher number. When
B
FB
placed, the FLD number (Sht) is characteristic for that function block.
C
sht
E A function block has no system outputs and no off-sheet references. It
does, however, have function block inputs and outputs to transfer
values from and to the calling FLD.
At least one output must be connected. All connected symbols must be
of a compatible type. For example, signals of type Byte can be
connected to Byte, Word or Float inputs.
For details on how to use equation blocks refer to subsection 6.9.4.
Function block Function block inputs and outputs are symbols that represent the
inputs and outputs signals entering the function block or leaving the function block.
They are essentially different from the FSC system inputs and
outputs. The function block I/O can be boolean or binary. Boolean
inputs or outputs are represented by single lines, and binary inputs or
outputs by double lines (see Figure 6-20 and Figure 6-21).
Software Manual
Description
A Function block boolean input
Description
Signal type: T B Function block binary input
Figure 6-20 Function block inputs
Description
Functional block boolean output A
Description
Functional block binary output B Signal type: T
Figure 6-21 Function block outputs
W = Word (16 bits)
L = Long (32 bits
6.8.10 Equation Blocks
Equation block An equation block is a symbol that must be designed on another FLD
first. When placed, the FLD number (Sht) is characteristic for that
equation block. Both the binary input and binary output must be
x EB y
connected. The signal type at the output side is Float. If required, the
sht
signal type at the input side is converted internally to type Float.
For details on how to use equation blocks refer to subsection 6.9.5.
Software Manual
6.8.11 PIDs
PID This symbol specifies a PID control function.

I = (Analog) input (Float)
a I
PID S = Setpoint (Float)
b S CS = Setpoint (Float)
PNr
CS O F
c M = Manual output condition
d M OM = Manual output value (Float)
e OM O = (Analog) output (Float)
The PID function is calculated using the trapezium integration

function. You can place a PID using the 'System Configuration' option
of FSC Navigator, or define it directly using the FLD design editor.
Parameters can be set using the 'System Configuration' option of FSC
Navigator.
If the PID is in Cascade mode, the CS setpoint will be used, otherwise

the S setpoint is used for the PID control function.
At least the input of the setpoint must be connected. The input signals
must be of a compatible type. The manual output condition must be
both connected or both not connected.
The cascade setpoint must be connected to the PID tag number as
configured in the variable database, unless it is not defined in the
variable database.
If M = 1, the PID mode will be switched to manual mode and the

value OM will be copied to the PID output O.
If M = 0, the PID stays in its current mode and no value of OM will be
copied to the PID output O.
For details on PID controllers refer to Appendix E of this manual.
Software Manual
6.8.12 Time Functions
Time functions The following time functions are available:

• Pulses,
• Timers with constant timer value, and
• Timers with variable timer value.
Each of these time functions is discussed in more detail below.

For design considerations regarding timers refer to subsection 6.9.6 on
page 6-85.
Pulse This function can be used to create a pulse with a duration of one
program cycle, e.g. for a CU input of a register.
a b After a pulse has been generated, 'a' must become zero first in order to
make a new pulse possible.
Function: N a b N is the number

1 1 1 of the program cycles
>1 1 0 after 'a' becomes active
Timers with
constant timer value The following timers with constant timer value are available:
• Pulse
• Pulse retriggerable
• Delayed ON
• Delayed ON memorize
• Delayed OFF
The following symbols are used in the diagrams below:

• S = Start timer (1 = start)
• R = Reset timer (1 = reset)
• Q = Timer output
• t = Time value + base (time constant)
• u = Remaining time value
All timers with constant timer value require that the start timer input
and the Q output must be connected.
Software Manual
Pulse This is a pulse time function on the rising edge of the timer start
input. If only one input is connected (e.g. in the middle), it is assumed
to be the start input.
S N Q
u
t=
R
Figure 6-22 Timers with constant timer value: pulse
Pulse retriggerable This is a pulse time function on the rising edge of the timer start
input. The time is restarted after every rising edge. If only one input
is connected (e.g. in the middle), it is assumed to be the start input.
S R Q
u
t=
R
Figure 6-23 Timers with constant timer value: pulse retriggerable
Delayed ON This is a delayed ON time function on the rising edge of the timer
start input. If only one input is connected (e.g. in the middle), it is
assumed to be the start input.
S Q
t O
u
R
Figure 6-24 Timers with constant timer value: delayed ON
Software Manual
Delayed ON memorize This is a delayed ON time function on the rising edge of the timer
start input. The timer continues to count even if the timer start input
goes back to the zero state. Both inputs (S and R) need to be
connected.
S M Q
t O
u
t=
R
Figure 6-25 Timers with constant timer value: delayed ON memorize
Delayed OFF This is a delayed OFF time function on the falling edge of the start
timer input. If only one input is connected (e.g. in the middle), it is
assumed to be the start input.
S Q
O t
u
t=
R
Figure 6-26 Timers with constant timer value: delayed OFF
Timers with
variable timer value The following timers with variable timer value are available:
• Pulse
• Pulse retriggerable
• Delayed ON
• Delayed ON memorize
• Delayed OFF
The following symbols are used in the diagrams below:

• S = Start timer (1 = start)
• R = Reset timer (1 = reset)
• Q = Timer output
Software Manual
• a = The time value that is loaded when the timer is started.
• Base = The time base of the timer: 100 milliseconds (100 ms),
1 second (1 s), or 1 minute (1 m).
• u = Remaining time value
All timers with variable timer value require that the start timer input,
the value input, and the Q output must be connected.
Pulse This is a pulse time function on the rising edge of the timer start
input.
S N Q
a u
Base
R
Figure 6-27 Timers with variable timer value: pulse
Pulse retriggerable This is a pulse time function on the rising edge of the timer start
input, the time is restarted after every rising edge.
S Q
R
a u
Base
R
Figure 6-28 Timers with variable timer value: pulse retriggerable
Software Manual
Delayed ON This is a delayed ON time function on the rising edge of the timer
start input.
S Q
t O
a u
Base
R
Figure 6-29 Timers with variable timer value: delayed ON
Delayed ON memorize This is a delayed ON time function on the rising edge of the timer
start input. The timer continues to count even if the timer start input
goes back to the zero state. All inputs (S, R and 'a') need to be
connected.
S M Q
t O
a u
Base
R
Figure 6-30 Timers with variable timer value: delayed ON memorize
Delayed OFF This is a delayed OFF time function on the falling edge of the timer
start input.
S Q
O t
a u
Base
R
Figure 6-31 Timers with variable timer value: delayed OFF
Software Manual
6.8.13 I/O Symbols
I/O symbols The table below lists the I/O symbols that are available in FLDs:
Table 6-5 Available I/O symbols in FLDs

Digital I/O symbols Multiple I/O Analog I/O symbols
symbols
Digital input (I) Binary input (BI) Analog input (AI) combined
with A/D converter
Digital output (O) Binary output (BO) Analog input (AI) combined
with A/D converter
Digital input with Binary Coded

sheet reference Decimal input (BI)
Digital output with Binary Coded

sheet reference Decimal output (BO)
Diagnostic input
Each of these I/O symbols is discussed in more detail below.
Digital I/O signals The following digital I/O signals are available:
• Digital input (I),
• Digital output (O),
• Digital input with sheet reference,
• Digital output with sheet reference, and
• Diagnostic input.
Digital input (I) Digital inputs (I) are used for boolean signals, e.g. ON/OFF or
START/STOP.
L Tag number
O Service
C Qualification
Figure 6-32 I/O symbols: digital input (I)
Software Manual
Digital output (O) Digital outputs (O) are used for boolean signals, e.g. START/STOP
or RUNNING/STOPPED.
Tag number L
Service O
Qualification C
Figure 6-33 I/O symbols: digital output (O)
Digital input Digital inputs with sheet reference are used for boolean signals that
(with sheet reference) have a direct digital output. The sequence letter refers to the
connected digital output. This symbol is always accompanied by its
corresponding output symbol (see below). This combination is
identified by a unique sequence letter, where "A" is the first sheet
reference, "B" the second, etc.).
L Tag number
SQ
O Service
C Qualification
Figure 6-34 I/O symbols: digital input (with sheet reference)
Digital output Digital outputs with sheet reference are used for boolean signals
(with sheet reference) where the digital output is a direct copy of the digital input. The
sequence letter refers to the connected digital input. This symbol is
always accompanied by its corresponding digital input symbol (see
above).
Tag number L
SQ Service O
Qualification C
Figure 6-35 I/O symbols: digital output (with sheet reference)
Diagnostic input I/O type : I, O, AI, AO, LoopO, LoopI, SensAI.

Tag number : Tag number of I/O (I, O, AI, AO) allocated to a
fail-safe I/O module.
S I/O type : T
Y Tag number
S “Not faulty”
Figure 6-36 I/O symbols: diagnostic input
Software Manual
Function:
I, O, AI, AO: The diagnostic input is low when the channel is faulty,
else it is high.
LoopO: The diagnostic input is low when a loop-monitoring
error is detected by the system, else it is high (only for
outputs allocated to a module with loop-monitoring
features).
LoopI: The diagnostic input is low when a sensor digital input
alarm is generated by the system and the digital input is
not forced, else it is high.
SensAI: The diagnostic input is low when a sensor analog input
alarm is generated by the system and the analog input is
not forced, else it is high.
Binary I/O signals The following binary I/O signals are available:
• Binary input (BI),
• Binary output (BO),
• Binary coded decimal input (BI), and
• Binary coded decimal output (BO)
Binary input (BI) Binary inputs are used for binary signals.
L Tag number
O Service
C Signal type : T
Figure 6-37 I/O symbols: binary input (BI)
W = Word (16 bits)
L = Long (32 bits
For variables with location 'COM' or 'FSC', the signal type may also
be: F = Floating point (32 bits)
Software Manual
Binary output (BO) Binary outputs are used for binary signals.
Tag number L
Service O
Signal type : T C
Figure 6-38 I/O symbols: binary output (BO)
W = Word (16 bits)
L = Long (32 bits
For variables with location 'COM' or 'FSC', the signal type may also
be: F = Floating point (32 bits)
Binary coded decimal Binary coded decimal (BCD) signals are always converted to a binary
input (BI) signal through a decimal-to-binary converter.
L Tag number DEC
O Service
C Signal type: T BIN
Figure 6-39 I/O symbols: binary coded decimal input (BI)
W = Word (16 bits)
L = Long (32 bits
Binary coded decimal Binary signals are converted to a binary coded decimal (BCD)
output (BO) through a binary-to-decimal converter.
BIN Tag number L
Service O
DEC Signal type: T C
Figure 6-40 I/O symbols: binary coded decimal output (BO)
W = Word (16 bits)
L = Long (32 bits
Software Manual
Analog I/O signals The following analog I/O signals are available:
• Analog input combined with A/D converter, and
• Analog output combined with A/D converter.
Analog input combined Analog inputs combined with analog-to-digital converter are used to
with analog-to-digital convert analog signals to binary signals with signal type 'F' (float).
converter
An analog signal is always converted to a binary signal through an
analog-to-digital converter.
L A
Tag number
O
Service
C D
Figure 6-41 I/O symbols: analog input combined with

analog-to-digital converter
Analog output Analog outputs combined with digital-to-analog converter are used to
combined with convert binary signals to analog signals with signal type 'F' (float)
digital-to-analog
The digital signal is converted to an analog signal through a digital-
converter
to-analog converter.
D L
Tag number
O
A Service
C
Figure 6-42 I/O symbols: analog output combined with

digital-to-analog converter
6.8.14 Sheet Transfers
Sheet transfers Sheet transfers are used to connect signals between FLDs for those
functions that cannot be incorporated on a single FLD.
A sheet transfer contains information on the originating (source) FLD
and the destination FLD. In order to distinguish more than one sheet
transfer between two FLDs, a sheet transfer sequence number is
added. For a better understanding, a service (and qualification) may be
entered as well.
Software Manual
Note:
For sheet transfers which are directly connected to an input
(I, BI) or an output (O, BO), the service text is used as a tag
number of the connected input or output. This is done to create
the correct corresponding symbol for the on-sheet transfer on the
destination FLD, as repeated inputs have different symbols than
normal on-sheet transfers. The tag number is combined with the
variable type (I, O, BI, BO) to search in the variable database. If
the combination is found, the service (and qualification) of this
variable are taken and drawn in the symbol.
On-sheet transfers The following on-sheet transfers are available:

• Boolean on-sheet transfer,
• Binary on-sheet transfer,
• On-sheet transfer for repeated digital input, and
• On-sheet transfer for repeated binary input,
Boolean on-sheet
transfer Boolean on-sheet transfers are used for boolean signals.
Service SRC
Qualification
DES
SQ
Figure 6-43 Sheet transfers: boolean on-sheet transfer
Binary on-sheet
transfer Binary on-sheet transfers are used for binary signals.
Service SRC
Signal type: T
DES
SQ
Figure 6-44 Sheet transfers: binary on-sheet transfer
W = Word (16 bits)
L = Long (32 bits
Software Manual
On-sheet transfer for This symbol can be used to show that this sheet transfer originates
repeated digital input (I) directly from a digital input without intermediate functions. The tag
number must therefore be identical to the tag number of the original
input.
L Tag number
SRC
O Service
DES
C Qualification
SQ
Figure 6-45 Sheet transfers: on-sheet transfer for repeated

digital input
On-sheet transfer for This symbol can be used to show that this sheet transfer originates
repeated binary input directly from a binary input, analog input or BCD input without
(BI)
intermediate functions. The tag number must therefore be identical to
the tag number of the original input.
L Tag number
SRC
O Service
DES
C Signal type: T
SQ
Figure 6-46 Sheet transfers: on-sheet transfer for repeated

binary input
W = Word (16 bits)
L = Long (32 bits
Off-sheet transfers The following off-sheet transfers are available:

• Boolean off-sheet transfer,
• Binary off-sheet transfer,
• Multiple boolean off-sheet transfer, and
• Multiple binary off-sheet transfer
Software Manual
Boolean off-sheet
transfer Boolean off-sheet transfers are used for boolean signals.
SRC Service
Qualification
DES
SQ
Figure 6-47 Sheet transfers: boolean off-sheet transfer
Binary off-sheet
transfer Binary off-sheet transfers are used for binary signals.
SRC Service
Signal type: T
DES
SQ
Figure 6-48 Sheet transfers: binary off-sheet transfer
W = Word (16 bits)
L = Long (32 bits
Multiple boolean Multiple boolean off-sheet transfers are used for boolean signals to
off-sheet transfer create more than one transfer from this sheet originating from the
same signal. Destination sheets must be defined (max. 5 references).
SRC Service
Qualification
DES To 2,3
SQ
Figure 6-49 Sheet transfers: multiple boolean off-sheet transfer
Software Manual
Multiple binary Multiple binary off-sheet transfers are used for binary signals to
off-sheet transfer create more than one transfer from this sheet originating from the
same signal. Destination sheets must be defined (max. 5 references).
SRC Service
Signal type: T
DES To 2,3
SQ
Figure 6-50 Sheet transfers: multiple binary off-sheet transfer
W = Word (16 bits)
L = Long (32 bits
6.8.15 Flip-Flops
Flip-flops The following flip-flops are available:

• S-R flip-flops, and
• R-S flip-flops.
S-R flip-flop This is a set-reset flip-flop with Set dominant.
S S Q
R R Q
Figure 6-51 Flip-flop symbols: s-r flip-flop
Function: S R Q –Q
0 1 0 1
1 0 1 0
0 0 Qt – 1 – (Qt – 1) State unchanged
1 1 1 0 Set is dominant
'Qt – 1' is the state after the previous cycle.

The set input and the reset input must both be connected, and at least
one of the outputs must be connected.
Software Manual
R-S flip-flop This is a reset-set flip-flop with Reset dominant.
S S Q
R R Q
Figure 6-52 Flip-flop symbols: r-s flip-flop
Function: S R Q –Q
0 1 0 1
1 0 1 1
0 0 Qt – 1 – (Qt – 1) State unchanged
1 1 0 0 Reset is dominant
'Qt – 1' is the state after the previous cycle.

The set input and the reset input must both be connected and at least
one of the outputs must be connected.
6.8.16 Texts
Texts You can add text to an FLD as an explanation or description. Any

single-line text up to 60 characters can be added. Text can be placed
anywhere. No position checking is done, which means you can even
place texts across symbols.
The character size (scale factor) can be selected in the range of 1 to
10.
If the character size is more than 1, the number of strokes can be
selected in the range of 1 up to the character size. This allows you to
set the boldness of the text. Figure 6-53 below shows some examples
of text in FLDs.
Figure 6-53 Texts in FLDs
Software Manual
6.9 Design Considerations
6.9.1 Logical Functions, Compare, and Calculation Functions
Logical, compare If you choose to place any symbol that has a variable height
and calculation (depending on the library definition), you are asked to enter its height
functions and/or width (size) expressed in half grid points. A default value is
given which you can accept or edit. If the symbol exceeds the sheet
borders, it will be positioned at the border. If there is any overlap
with another symbol that is already placed, a beep will sound.
6.9.2 Counters, Registers, and Constants
Counters If you choose to place a counter in the current FLD, you need to
specify the maximum counter value, which must be in the range of 1
to 8191. When a counter reaches this value after a count-up, it is
restarted to count at zero.
The maximum number of counters per FLD is 32.
The maximum number of counters per application is 510.
Registers If you choose to place a register in the current FLD, you need to
specify the register type. The following types are supported:
− B: Byte register which can contain 8-bit integers.
− W: Word register which can contain 16-bit integers.
− L: Long register which can contain 32-bit integers.
− F: Floating-point register which can contain floating-point reals.
The maximum number of registers per FLD is 32.
Software Manual
Constants If you choose to place a constant in the current FLD, you need to
specify the register type (see above under 'Registers'). Next, you are
asked to enter the constant value. The range of this value depends on
the signal type that you specified:
− B: –128 to +127
− W: –32,768 to +32,767
− L: –2,147,483,648 to +2,147,483,647
− F: –1038 to +1038
6.9.3 Signal Conversions
Conversions If the input value of a signal conversion is out of range, the FSC
system will shut down due to calculation overflow.
If the source value does not fit into the target (e.g. conversion of
-40000 from 'F' to 'W'), the FSC system will shut down.
If, for example, a word-to-byte conversion has been defined and

during translation it appears that the destination type must be word,
the conversion symbol is corrected to the trivial word-to-word
conversion, which is ignored by the compiler. You can use the FLD
design editor to delete the conversion.
In a float-to-word conversion, all decimal digits are discarded.

Decimal numbers are not rounded, but they are truncated. This means
that 4.9 becomes 4, and –4.9 becomes –4. To retain accuracy, you
should keep in mind what the possible range of the floating point
signal is. For a signal between 1 and 1000, the maximum deviation is
1/1000 = 0.1%. For a signal between 0 and 5, the maximum deviation
is 1/5 = 20%, which is quite significant. In the latter case, it could be
better to increase the scale.
Software Manual
Function block If you choose to place a function block in the current FLD, you will
be asked to enter an FLD number which the function block has been
designed on. If that FLD is not a function block, the following
message is displayed:
The sheet you entered is not a function block.
In addition to entering an FLD number by hand, you can also press
<?> to display a pop-up window that lists all existing function blocks.
If you enter one or more digits and then press <?>, you will see a list
of FLDs whose number start with the digit(s) you entered. You can
press <Esc> to abort the operation.
After you have entered a valid FLD number, the corresponding
function block is displayed on screen. All flip-flops, counters,
registers and timers have now been copied to the current FLD and to
the variable database. The size of the function block depends on the
number of function block inputs and outputs. All function block I/O is
drawn at the function block symbol. Binary I/O is drawn as double
lines, and boolean I/O as single lines.
Notes:
1. The function block number must be higher than the current
FLD number.
2. Once a function block has been defined on an FLD, the
following FLDs may only be equation blocks or function
blocks.
Changing a If you change a function block, you must change all function block
function block calls on other FLDs. The compiler will also change these function
block calls. When you changed the number of function block inputs
or outputs, their connections will be lost. You must then reconnect
these signals.
Software Manual
Equation blocks An equation block symbol can be used to approximate complex

calculations. Logarithmic, exponential, differential functions, etc.,
can be approximated using an approximation table. This is an
example of a square approximation table for values between 0 and 5:
25 X Y
20 0 0
0.5 0.25
15 1 1
1.5 2.25
10
2 4
5 2.5 6.25
3 9
0 3.5 12.25
0 1 2 3 4 5 4 16
4.5 20.25
Figure 6-54 Example of equation function 5 25
The equation can be approximated using the equation block symbol

(see Figure 6-55) and a generated equation table.
x
EB y
sht
Figure 6-55 Equation block symbol
'Sht' stands for the FLD number on which the equation block is
defined. This FLD number is characteristic for an equation block.
Equation block Before the equation block symbol can be used on any functional logic
definition diagram, an equation block FLD must be defined. This is
accomplished by defining an FLD as an equation block FLD (see
subsection 6.4). The FLD number of an equation block FLD must be
between 500 and 999. Next, the equation table for the required
calculation must be stored in the logic diagram. Once an equation
block has been defined on an FLD, the following FLDs may only be
equation blocks or function blocks.
Software Manual
Equation table The equation table can be specified using the 'Equation file' option
from the main menu of an equation block FLD.
If you choose this option, you will be prompted to enter the name of
the equation file, which is an ASCII text file that defines an equation
table. After you have entered a valid file name, the layout of the
equation file is checked and the equation table is stored in the equation
block FLD. To remove an equation table from an equation block FLD,
simply enter the name of a non-existing ASCII text file. Once an
equation table is stored in the equation block FLD, the original ASCII
text file is no longer needed by FSC Navigator.
Equation table The equation table file is an ASCII file which can be created using
design any popular text editor. The equation file consists of two columns.
The first column contains the input (x) values, and the second column
the output (y) values. One row with an 'x' and 'y' value together form
one point pair (x,y).
The following rules apply to the layout of an equation table:

• Each line must contain an input and an output value with at least
one space between the first and the second value. Empty lines are
not allowed.
• The minimum number of rows in an equation table is 3, and the
maximum number is 200.
• The input values must be in ascending numerical order (i.e. from
low to high).
• Both normal and exponential notations may be used. For example,
0.05 is the same as 5.0E-2.
• The input values (x) and output values (y) must be between –1038
and +1038.
Equation block Once you have defined an equation table in an equation block FLD, it
usage can be used on any functional logic diagram with a lower FLD
number. Both the input (x) and the output (y) values must be
connected. The output (y) signal is of type 'Float', the input (x) value
is internally converted to type 'Float', if required.
Software Manual
Algorithm used The FSC CPU software uses linear interpolation to approximate the
output value for an input value that is located between two input
values (see Figure 6-56).
F(X1)
F(P)
F(X0)
X0 P X1
Figure 6-56 Approximating an output value to an input value
The approximation algorithm used is as follows:
f ( X1) − f ( X 0 )
f ( P) = f ( X 0 ) + * ( P − X 0)
X1 − X 0
Note:
The input (x) value is clamped on the first and the last values in
the equation table. This means that a value smaller than the first
input value in the equation table will result in an output value
equal to the first output value of the equation table. Similarly, an
input value larger than the last input value in the equation table
will result in an output value equal to the last output value of the
equation table.
Software Manual
6.9.6 Timers
Timer types There are basically two types of timers:

• Timers with a variable timer value, which is defined by
connecting a binary signal (byte or word) to the input side of the
timer symbol (i.e. input 'a' of the timer in the FSC application), and
• Timers with a constant timer value, which is configured in the
timer itself.
Placing timers If you choose to place a timer in the current FLD, you will be asked
to specify the timer base. For timers with a constant timer value, you
must also enter the timer value. (You can then use the left and right
arrow keys (← and →) or <Enter> to switch between the two fields.)
Timer identification Each timer has a unique identification (tag number), which is
generated automatically. It is made up as follows:
'T' + <FLD no.> + '_' + <seq. no.>,
e.g. 'T101_2' (i.e. the second timer in FLD 101).
Timer base The following timer bases can be selected:

• 100ms: 100 milliseconds (0.1 second)
• s: 1 second
• m: 1 minute
Note:
The timer base of timers with a variable timer value is fixed and
will never change. For each of the three timer bases, the CPU
module keeps a common timer: one to update all 100ms timers
(once per 100 milliseconds), one to update all 1s timers (once
per second), and one to update all 1m timers (once per minute).
The timer base of timers with a constant timer value may
automatically be changed to achieve better accuracy of the timer
value (see the next page).
Software Manual
Timer value For timers with a constant timer value, you also need to specify the
timer value in addition to the timer base. The timer value multiplied
by the timer base is the total time of the timer.
If the timer base is 100 milliseconds (ms), you must enter an integer
timer value (i.e. no decimal values are allowed). If the timer base is
seconds (s) or minutes (m), you can use decimal values. During live
monitoring of the FLDs, however, this decimal value will always be
rounded to the nearest whole number (e.g. 15.4 will become 15).
Illegal timer values (< 0) are not accepted. The value '0' (zero) is
changed to the nearest legal value. The maximum values that can be
entered for the timer depend on the selected timer base:
• 100ms: 99 (= 9.9 seconds)
• s: 9999 (= 167 minutes)
• m: 2047 (= 34 hours and 7 minutes) (if you enter a higher
value, it is automatically reset to 2047)
Depending on the specified timer value, the timer base may

automatically be changed to achieve better timer accuracy (see
below).
Important!
For programmable timers, make sure that you do not use a timer
value higher than 2047. If you do, there may be a total system
shutdown.
Maximum number The maximum number of timers that can be used in one application
of timers depends on the timer base:
• 100ms: max. 748
• s: max. 748
• m: max. 446
The maximum number of timers per FLD is 32 (including timers in

function blocks).
Timer accuracy The timer accuracy depends on the timer type:
Timers with a The timer base of timers with a variable timer value is fixed and will
variable timer value never change. For each of the three timer bases, the CPU module
keeps a common timer: one to update all 100ms timers (once per 100
milliseconds), one to update all 1s timers (once per second), and one
to update all 1m timers (once per minute).
Software Manual
As a result, a timer with a 1m timer base and value 1 (i.e. a
one-minute timer) can expire anywhere between 1 and 60 seconds, a
two-minute timers can expire anywhere between 61 and 120 seconds,
etc. Similarly, a timer with timer base 1s can expire anywhere
between 100 ms and 1 second.
You should always be aware of this when programming the

application, and select the timer base with the best resolution. To
improve the timer accuracy, you may want to use a different timer
base (especially if the timer value is very close to the "time base
conversion boundaries").
Consider, for example, a 20-minute timer. If it is configured as a timer
with timer base 'm' (minutes) and timer value '20', the timer will run a
minimum of 19:01 minutes and a maximum of 20:00 minutes. The
worst-case deviation is 59 seconds, which is 4.91% of the configured
time. If that is unacceptable, you can also configure the timer with
timer base 's' (seconds) and a timer value of '1199' (i.e. 19:59
minutes). This will then remain a second-based timer, but show a
value of 20 minutes on the FLD. This timer will run at least for 1198
seconds (i.e. 19:58 minutes). The worst-case deviation here is one
second, which is only 0.08% of the configured time.
Timers with a For timers with a constant timer value, FSC Navigator will
constant timer value automatically change the timer base, where required, in order to
optimize the timer resolution and achieve better timer accuracy:
Minute timers:
0.01 m ... 10 m: timer base will be changed to seconds (s).
10.01 m ... 2027 m: timer base will not be changed.
Second timers:
0.01 s ... 10 s: timer base will be changed to 100 ms.
10.01 s... 1199 s: timer base will not be changed.
1200 s ... 9999 s: timer base will be changed to minutes (m).
100 millisecond timers:

The timer base will never be changed. (The maximum is 99 ∗ 100 ms,
which is 9.9 seconds.)
Examples:
− Base 's', value '9' Þ Base '100ms', value '90'.
− Base 's', value '1800' Þ Base 'm', value '30'.
− Base 'm', value '9' Þ Base 's', value '540'.
Software Manual
6.9.7 PIDs
PIDs If you choose to place a PID in the current FLD, you will be asked to
enter its tag number. If this tag number has already been placed, the
following error message will be displayed on screen:
PID already placed on FLD <FLD no.>
If the tag number is a new PID, it is included in the variable database,
and the PID settings are set to their defaults. You can change them
using the 'System Configuration' option of FSC Navigator (see Section
4 of this manual).
In addition to entering a PID number by hand, you can also press <?>
to display a pop-up window that lists all existing PID tag numbers. If
you enter a number of characters and then press <?>, you will see a
list of PID tag numbers that start with the character(s) you entered.
Please note that tag numbers are case-sensitive (i.e. 'Tag' is not the
same as 'TAG').
6.9.8 Inputs and Outputs
Normal I/O If you choose to place a normal input or output in the current FLD,
you will be asked to enter its type and tag number. FSC Navigator
uses this combination to identify the input or output in the variable
database. If the input has already been placed on an FLD for the same
CPU, the following message is displayed on screen (except for
flasher inputs):
Input already placed on FLD <FLD no.>
If the output is already placed on an FLD, the following message will
be displayed on screen:
Output already placed on FLD <FLD no.>
If you deleted an I/O before, you can use it again. If the tag number
you entered is found in the variable database, all the variable data is
taken from the database and no further input needs to be entered
(unless the data is invalid). The data is displayed on screen.
In addition to entering a type and tag number by hand, you can also
press <?> to display a pop-up window that lists all existing I/O types
and tag numbers. If you enter a number of characters and then press
<?>, you will see a list of tag numbers that start with the character(s)
Software Manual
you entered. Please note that tag numbers are case-sensitive (i.e. 'Tag'
is not the same as 'TAG').
If the tag number you entered is not found (i.e. a new input or output),
you need to enter some additional attributes:
• Service,
• Qualification, and
• Location.
Service This attribute is a brief description of the tag number.
Qualification This attribute only needs to be specified for boolean I/O. It provides
information about the '1' (or active) state of the input or output.
Location This attribute provides information about the location of the input of
output in the installation. It is specified as a three-character
abbreviation. There are a number of reserved locations:
• ANN:
This input/output must be assigned to an alarm function (using the
'System Configuration' option of FSC Navigator).
• COM:
This input/output must be assigned to a communication port (using
the 'System Configuration' option of FSC Navigator).
• FSC:
This input/output must be assigned to an FSC system (using the
• MUX:
This input/output must be assigned to a multiplexer (using the
• SYS:
This input is used for internal system variables. You cannot use this
location.
You can use the up and down arrow keys (↑ and ↓) to switch between
the configuration fields. The value that was selected last will be the
default for the I/O symbol. If the input or output is new, its
information is stored in the variable database.
Note:
Inputs that are safety-related are shown in the 'safety-related
items' color (red by default). For details on color settings refer to
Section 3 of this manual ("Using FSC Navigator").
Software Manual
Diagnostic input If you choose to place a diagnostic input or output in the current FLD
(red symbol in bottom left corner of selection sheet), you will be
asked to choose the I/O type. You can use <Space> to toggle between
the available options: I, O, AI, AO, LoopO, and SensAI. You can also
press<?> to choose from a list of available options.
I, O, AI or AO Choose I, O, AI or AO for detection of a channel fault, depending on

the module type which the I/O is allocated to.
LoopI Choose LoopI for detection of a sensor alarm of a digital input.
LoopO Choose LoopO for detection of a loop-monitoring error of a fail-safe

digital output.
SensAI Choose SensAI for detection of a sensor alarm of an analog input.

You cannot choose SensAI for safety-related analog inputs with
non fail-safe sensors. In that case you should use type AI instead.
Next, you are prompted to enter a tag number of an I/O that is

allocated to a fail-safe I/O module. If you enter a non-existing or
invalid tag number, the following message is displayed on screen:
Input/output does not exist: <Tag no.>
In addition to entering a tag number by hand, you can also press <?>
to display a pop-up window that lists all selectable I/O for diagnostic
input (i.e. all existing tag numbers allocated to a fail-safe I/O module).
If you enter a number of characters and then press <?>, you will see a
list of tag numbers that start with the character(s) you entered. Please
note that tag numbers are case-sensitive (i.e. 'Tag' is not the same as
'TAG').
6.9.9 Sheet References
Sheet references Sheet references allow you to quickly combine directly connected
inputs and outputs. If you choose to add a sheet reference to the
current FLD, you will first be asked to enter the tag number of the
input and then the tag number of the output. In addition to entering a
tag number by hand, you can also press <?> to display a pop-up
window that lists all available tag numbers.
If you enter a number of characters and then press <?>, you will see a
list of tag numbers that start with the character(s) you entered. Please
Software Manual
note that tag numbers are case-sensitive (i.e. 'Tag' is not the same as
'TAG').
Each marker has a unique identification (tag number), which is made
up as follows: <FLD no.> + '_' + <seq. letter>, e.g. 101_A. Both the
FLD number and the sequence letter are generated automatically.
If no space is available for the related transfer symbol, an error

message is displayed on screen, and the sheet reference is not placed.
Otherwise, the transfer and its related symbol are displayed on screen.
The maximum number of marker I/O symbols per FLD is 26. The
service field of the marker in the variable database contains the tag
number of the input, and the qualification field contains the tag
number of the output. If the input has already been placed on an FLD,
the following message is displayed on screen:
Input already placed on FLD: <FLD no.>
If the output has already been placed on an FLD, the following
message is displayed on screen:
Output already placed on FLD: <FLD no.>
6.9.10 Flip-Flops and Pulses
Flip-flops If you choose to place flip-flops or pulses to the current FLD, they are
and pulses added to the variable database. Every flip-flop gets a sequence
number which is needed to create a unique code for searching in the
variable database. Each flip-flop and pulse has a unique identification
(tag number), which is made up as follows: <FLD no.> + '_' + <seq.
no.>, e.g. 101_1. Both the FLD number and the sequence number are
generated automatically.
Only a limited number of sequence numbers is available. When all
sequence numbers are in use, an error message is displayed, and no
flip-flop or pulse can be placed anymore.
Software Manual
6.10 Sheet Transfers
6.10.1 Characteristics
Characteristics Sheet transfers allow you to transfer a signal value to one or more
other FLDs. A sheet transfer is characterized by two FLD numbers
and a sequence number. The first FLD is the source FLD, which is
the FLD the signal is transferred from. The second FLD is the
destination FLD, which is the FLD the signal is transferred to. The
sequence number is a number which is unique on the source FLD in
order to distinguish between signal transfers that have the same
source and destination FLDs.
Note:
Make sure that the destination FLD number is always greater
than the source FLD number. If that is not the case, the response
of the FSC system will increase by one program cycle.
There are two types of sheet transfers:

• Off-sheet transfer symbol (i.e. from the source FLD), and
• On-sheet transfer symbol (i.e. from the destination FLD).
Off-sheet
transfer symbol This symbol is placed on the source FLD at the output side.
SRC Service
DES Qualification
SQ
Figure 6-57 Off-sheet transfer (boolean signal)
There are four different off-sheet transfer symbols:

1. Single boolean off-sheet transfers.
2. Multi boolean off-sheet transfers (up to five transfers of boolean
signals to five different FLDs).
3. Single binary off-sheet transfers.
4. Multi binary off-sheet transfer (up to five transfers of binary
signals to five different destination FLDs).
Software Manual
On-sheet
transfer symbol This symbol is placed on the destination FLD at the input side.
Service SRC
Signal type : T DES
SQ
Figure 6-58 On-sheet transfer (binary signal)
There are four different on-sheet transfer symbols:

1. Boolean on-sheet transfers.
2. Repeated input transfers (this signal is connected to a digital input
on the source FLD).
3. Binary on-sheet transfers.
4. Binary repeated input transfers (this signal is connected to a
binary input on the source FLD).
Each sheet transfer has a unique identification (tag number), which is

made up as follows: <source FLD> + '_' + <destination FLD> + '_' +
<seq. no.>, e.g. 101_250_1. Both the FLD numbers and the sequence
number are generated automatically.
If the type is 'M' (boolean sheet transfer), a marker is placed in the
variable database for each reference you make.
If the type is 'R' (binary sheet transfer), a register is placed in the
variable database for each reference you make.
Making
sheet transfers There a two ways to make a sheet transfer:
• On the source FLD, by selecting an off-sheet transfer symbol.
• On the destination FLD, by selecting an on-sheet transfer symbol.
Each of these methods is described in more detail below. There are

minor differences between linking FLDs from the source FLD and
from the destination FLD. There are also two different ways to realize
a connection from the destination FLD or from the source FLD:
• Only use the FLD number and a sequence number. This method
requires knowledge about the sheet transfer mechanism.
• Use a list of existing sheet transfers which provides all transfers that
can be linked to the current FLD. This method does not require
much knowledge about the sheet transfer mechanism, but instead
makes use of a tag number, service and qualification.
Software Manual
6.10.2 Off-Sheet Transfers
Sheet transfer from Off-sheet transfers are transfers from the source FLD. To add an
the source FLD off-sheet transfer to the FLD, first select an off-sheet transfer symbol
from the selection sheet. This can either be a single or multi sheet
transfer symbol. FSC Navigator will always convert this symbol to a
multi sheet transfer symbol, which means that you can create a
maximum of five transfers to five different FLDs.
Next, select a valid position in the FLD design sheet. You will be
prompted to enter the FLD number of the destination FLD, which
must be a number between 0 and 999. If you do not know which FLD
you want to transfer a signal to, enter '0' (zero). This means that the
signal is not yet connected to a destination FLD. You can only transfer
to an existing FLD. If you enter the number of a non-existing FLD,
that number will automatically be replaced by '0' (zero). You can
connect an unconnected transfer symbol afterwards using the 'cHange'
option from the menu, or by selecting it from the destination FLD (see
subsection 6.10.3).
In order to identify a sheet transfer symbol, each on-sheet transfer
symbol gets a unique sequence number, which is assigned
automatically.
If you enter the number of an existing FLD, you are asked to provide
the sequence number of a sheet transfer on the destination FLD
(range: 1 to 36).
You now have two options:

1. You want to connect the signal to an existing, unconnected
on-sheet transfer symbol on the destination FLD
(source FLD = '0').
You must then enter the sequence number of that on-sheet transfer
symbol. FSC Navigator will subsequently search for this transfer,
and connect it (providing it is not yet connected and is of the same
type as the source signal). The sequence number of that on-sheet
transfer symbol is changed into the sequence number of the source
symbol (off-sheet transfer). Also, the identification code (tag
number) is changed according to the new situation: the source
FLD '0' is replaced by the current FLD number, and the old
sequence number is replaced by the new one. If the transfer is not
found, the sequence number is changed into '0' (see item 2).
Software Manual
2. You do not want to connect the signal to an existing on-sheet
transfer symbol on the destination FLD (or the sequence
number you entered did not result in a link (see item 1)). In that
case enter '0' for the sequence number. A new on-sheet transfer
symbol will now be placed on the destination FLD. If there is no
space on the destination FLD, the following error message will be
No space on referenced sheet.
The sequence number of this new symbol will be copied from the
source symbol which is automatically generated.
Note:
The sequence number you enter is only meant to point out which
connection you want to make, or whether you want to make a
connection. It is not a way to assign a number to the transfer
symbol you want to place.
Next, you must enter some additional data:

1. Service or I/O tag number.
2. Qualification (only for boolean sheet references).
3. Signal type (only for binary sheet references).
Service You can enter any text of up to 19 characters. The service text can
have two meanings:
• A descriptive text.
• An I/O tag number of an I/O which is connected directly to the
off-sheet transfer symbol. The service, qualification and signal type
are then copied from the I/O, otherwise you must enter them
yourself (see below). FSC Navigator uses the service text (first 16
characters) to search for an I/O on the FLD that contains the
off-sheet reference symbol. The type is automatically determined in
the following order of priority:
For boolean I/O: I, O
For binary I/O: AI, AO, BI, BO
If the type is I, AI or BI, the transfer symbol on the destination FLD is
converted to a repeated input symbol.
Note:
If an I/O tag number is entered and the connection is not direct,
the compiler will issue an error message. If it is not directly
connected, you can better use a service text which is slightly
different from the tag number.
Software Manual
Qualification This text only needs to be provided for boolean sheet transfers.
You can enter a text of up to 16 characters. This text describes the '1'
status of the signal. Thus, "ALARM ACTIVE" means that the alarm is
active when the value of the reference marker is '1'.
Note:
The interpretation of the qualification is your responsibility. It is
meant as a description of the signal status.
Signal type The signal type only needs to be specified for binary sheet transfers.
You can press <Space> to toggle between the available signal types:
• B = Byte
• W = Word
• L = Long
• F = Float
Multiple transfers If you did not enter a destination FLD '0', you can make four
additional transfers to different destination FLDs. The service,
qualification and signal type for these transfers are the same as those
you entered for the first transfer. If you try to refer to a destination
FLD that is already used, the following error message will be
Duplicate reference not allowed.
You must then use a new off-sheet transfer symbol which will
automatically be given a new sequence number. All on-sheet transfer
symbols on the specified destination FLD get the same sequence
number, which is the one that was automatically assigned to the
on-sheet transfer symbol on the source FLD.
If you enter <Esc>, all completed destination FLDs are accepted and
you are no longer prompted to specify more destination FLDs. This
will also happen if you enter a destination FLD '0' (zero). If you only
specified one destination FLD, FSC Navigator will automatically
convert the multi off-sheet transfer symbol to a single off-sheet
transfer symbol.
Software Manual
Changing an To change an off-sheet transfer, choose the 'cHange' option from the
off-sheet transfer Symbol menu. The old values will be displayed as the default. You
can now enter the same or different destination FLDs. If you press
<Esc>, all completed destination FLDs are accepted and you are no
longer prompted to specify more destination FLDs. The modified
destinations are accepted, and all other existing destinations are not
modified.
6.10.3 On-Sheet Transfers
Sheet transfer from On-sheet transfers are transfers from the destination FLD. To add an
the destination FLD on-sheet transfer to the FLD, first select an on-sheet transfer symbol
from the selection sheet. Next, select a valid position in the FLD
design sheet. Making a sheet transfer from the destination FLD is
almost identical to making a sheet transfer from the source FLD.
There are, however, some small differences:
1. You can only make one transfer. Two different source signals
cannot be transferred to one destination.
2. You can connect an on-sheet transfer to an off-sheet transfer
which does not yet contain the maximum number (5). If you enter
the source FLD and the sequence number of a single off-sheet
transfer, it will be converted to a multi sheet transfer. That symbol
will then be extended with the new destination. You cannot make
a connection to an off-sheet reference which already contains a
transfer to the current FLD. In that case the following error
message will be displayed on screen:
If you connect the on-sheet transfer symbol to an off-sheet transfer

symbol whose service is identical to the tag number of an I/O on the
source FLD, the on-sheet transfer symbol is converted to a repeated
on-sheet transfer symbol. This means that it does not really matter
which on-sheet transfer symbol you choose. If you entered the
sequence number of an existing off-sheet transfer symbol on the
source FLD, the sequence number of that transfer symbol is copied to
the destination symbol, and a new marker or register is stored in the
variable database. You can also enter a source '0' (zero), which means
you do not want to make a connection to the source FLD yet. You can
connect this signal afterwards using the 'cHange' option from the
Software Manual
menu, or by connecting it from the source FLD (see subsection
6.10.2).
A new off-sheet reference symbol will be placed on the source FLD in

any of the following situations:
• You entered the sequence number of an off-sheet reference symbol
which already contains five transfers.
• You entered a sequence number that has no corresponding off-sheet
reference.
• You entered sequence number '0' (zero).
If there is no space on the source FLD, the following error message is
No space on reference sheet.
You cannot change the service, qualification or signal type if you

connected the sheet transfer to an off-sheet transfer on a source FLD
that already contains another transfer.
If a new off-sheet reference symbol is created on the source FLD, a

new sequence number will automatically be assigned to it. This
number is copied to the on-sheet transfer symbol on the destination
FLD. This means that the sequence number you entered before was
just to point out which link you want to make, or whether you want to
make a connection. You do not have any influence on the final choice
of this number.
Changing an To change an on-sheet transfer, choose the 'cHange' option from the
on-sheet transfer Symbol menu. The old values will be displayed as the default. You
can now enter the same or another source FLD. If you press <Esc> or
enter '0' (zero), the old source FLD is replaced by '0'. The off-sheet
transfer symbol on the source FLD is then deleted or replaced by an
unlinked on-sheet transfer symbol, and all variables in the variable
database belonging to it are erased or changed accordingly.
When you change an on-sheet transfer which is connected to a multi

off-sheet transfer, you cannot change the service, qualification or
signal type, because they are also related to the other sheet transfers
which are stored in that off-sheet transfer symbol. It is possible to
change the signal type when the source FLD reference is '0' (zero). If
you want to change it nevertheless, you must go to the source symbol
on the source FLD and replace it there.
Software Manual
6.10.4 Selecting a Sheet Transfer Symbol Using a Selection List
Selecting a sheet Often you do not know which FLD you want to transfer a particular
transfer symbol using a signal to. You can then deliver the signal in an off-sheet transfer
selection list
symbol with destination FLD '0' (i.e. unlinked). Afterwards you can
make a link by means of an on-sheet transfer symbol on the
destination FLD(s). You can then press <?> to display a popup
window that lists all existing unlinked sheet transfers. You can do
this on two places during the defining of sheet transfers.
1. When you are asked to enter the destination or source FLD
number.
Suppose you are placing an on-sheet transfer. If you then enter
<number>+<?>, a popup window will appear which lists all
unlinked off-sheet transfers on all FLDs that start with the number
you entered. If you did not specify a number but only pressed <?>,
all unlinked off-sheet transfers are listed. If no such sheet transfers
exist, the following error message is displayed on screen:
No such tag number found.
The list contains the tag number, service and qualification. Move
the cursor bar to the sheet transfer you want to select, and press
<Enter>. The list will then disappear from the screen. Since you
already specified which transfer you want to make, you are no
longer prompted to enter a sequence number. If you do not want
to select a transfer from the list, press <Esc>. You will then return
to the situation that existed before you pressed <?>. You can go
on defining a source FLD.
2. You did not select a transfer from the list yet. Instead, you
entered a source or destination FLD number.
You are asked to enter a sequence number to point to a sheet
transfer on the FLD whose number you entered. You can still
select a transfer from the list. Press <?>, and the list described
above will appear. However, it will now only list the unlinked
transfers from the FLD whose number you had entered earlier.
In both cases the service, qualification and signal type are copied.
Software Manual
6-100
6.11
FLD Formats
69HZ004B F
A A RESET S
F 69HS004 >1
_ "1=PRESSED" C
S RESET S
C "1=PRESSES" 0 t 69FY002B F
69FIC A/M STATUS S
t=2 S "1=AUTO,0=MANUAL" C
R
69UZ011 F
AIR TO SEP SOV S
69 ESD TRIP 231 "1=OPEN" C
251 1 &
69UZ011B F
Figure 6-59 Example of an FLD designed with SYM1
AIR TO SEP SOV S

"1=OPEN" C
F 69QT002 2 A 69QZ002A F
L 3 OXYGEN ANLYSR ALARM S
D OXYGEN ANALYSER 1 D "0=ALARM" C
<
_
F 999 >1
_
ENAB 271 69QZ002M F

251 1 REMOTE MOSON S
A H "1=ON" C
69KEY 221 B I 251 ORGATE
251 2
C J 267 1
P 69QZ002M 2 FB
N MOSBUTTON 1 D K
981 69QZ002P F
L "1=PRESSED" 3
E L REQUEST PERMIT S
PERMIT 221 "1=REQUEST" C
F M
251 1
G N 251 LOCKOUT
REMOVE GRANTED 221 271 2
Section 6: Functional Logic Diagrams
251 3
S FLASHER-0.5Hz 251 REMOVE REQUEST

Y System marker 275 3
S
C LAMPTEST 69QI002M C
O BACKLIGHT O
M "I=TEST" "1=on" M
Software Manual
E
Customer :
D
C Principal :
C
B Plant 1 : Date: 8-4-1992 By: H.K.
A Drawing number
Plant 2 : H_1 251 267
O 8-4-1992 FIRST ISSUE
Req/Ordernr : Serial Appl. Unit
Rev: Date: Description Chk'd Code Code Sheet Cont'd
69HZ004B F
A A RESET S
F 69HS004 >1 "1=PRESSED" C
S RESET S
C "1=PRESSES" 0 t 69FY002B F
69FIC A/M STATUS S
R t=2 S "1=AUTO,0=MANUAL" C
69UZ011 F
AIR TO SEP SOV S
231 "1=OPEN" C
69 ESD TRIP &
251 1 69UZ011B F
AIR TO SEP SOV S
"1=OPEN" C
F 69QT002 2 A 69QZ002A F
L 3 OXYGEN ANLYSER S
D OXYGEN ANALYS 1 D "0=ALARM" C
>1
F 999 >1
ENAB 271 F
251 1
69QZ002M
REMOTE MOSON S
A H "1=ON" C
69KEY 221
251 2
B I 251 ORGATE
2
C FB J 267 1
P 69QZ002M
N MOSBUTTON 1 D K
L "1=PRESSED" 3 69QZ002P F
E 981 L REQUEST PERMIT S
PERMIT 221 "1=REQUEST" C
251 1
F M
G N 251
221 LOCKOUT
REMOVE GRANTED 271 2
251 3
S FLASHER-0.5Hz 251
275 3
REMOVE REQUEST
Y System marker
S
C LAMPTEST 69QI002M C
O BACKLIGHT O
M "I=TEST" "1=on" M
E Customer :
D
C
Principal :
B Plant 1 : Date:8-4-1992 By: H.K.
Drawing number
A
8-4-1992 FIRST ISSUE
Plant 2 : H_1 251 267
O
Serial Appl. Unit Sheet Cont'd
Rev: Date: Description Chk'd Req/Ordernr : Code Code
Software Manual
1 1
2 GENERAL-SS 2
3 3
US0100
4 4
5 KUEHLWASSER 5
6 6
7 7
8 8
9 1v3 / 2v3 1v3 ALARM 9
10 PS2701a DRUCK KUELWASSER PS2701 STOERUNG10 PA2701

W 2 1 5 "P > min = 1" "1v3-ALARM" W 2 5 1
A E
11 PS2701b DRUCK KUELWASSER 11
W 2 1 6 "P > min = 1" B FB F 2v3 SS
12 PS2701c DRUCK KUELWASSER C 912 G PS2701 SS 12 To 110_13
W 2 1 7 "P > min = 1" "1=OK"
13 HS2701-BR BRUECKE PS2701 D H
W 13
2 1 4 "GEBRUECKT=1"
14 14
15 2v3 ALARM 15
PS2701 SS PSA2701
16 "P < min=Alarm" 16 W
2 5 2
17 17
18 18
19 BRUECKE PS2701 19 HSA2701-BR

"ALARM" W 2 5 3
20 20
21 21
22 22
23 23
24 24
25 25
26 26
27 27
28 28
29 29
30 30
31 31
32 32
33 33
34 34
35 35
Customer : B Description Chk'd By: Drawing number
Principal : A HELP_1
O 8-4-1992 FIRST ISSUE Date:
Plant 1: Plant 2 : Req/Ordernr: Rev: Code 102
Software Manual
1 1
2 GENERAL-SS 2
3 3
US0100
4 4
5 KUEHLWASSER 5
6 6
7 7
8 8
9 1v3 / 2v3 1v3 ALARM 9
10 PS2701a
W
DRUCK KUELWASSER PS2701 STOERUNGPA2701 10
2 1 5 "P > min = 1" "1v3-ALARM" W 2 5 1
DRUCK KUELWASSER A E
PS2701b
11 W 11
2 1 6 "P > min = 1" B FB F 2v3 SS
12 PS2701c
W
DRUCK KUELWASSER
C 912 G
PS2701 SS To 110_13 12
2 1 7 "P > min = 1" "1=OK"
13 HS2701-BR BRUECKE PS2701 D H 13
W 2 1 4 "GEBRUECKT=1"
14 14
15 2v3 ALARM 15
PS2701 SS PSA2701
16 W 16
"P < min=Alarm" 2 5 2
17 17
18 18
19 BRUECKE PS2701 HSA2701-BR 19

"ALARM" W 2 5 3
20 20
21 21
22 22
23 23
24 24
25 25
26 26
27 27
28 28
29 29
30 30
31 31
32 32
33 33
34 34
35 35
36 36
Customer : B Description Chk'd By: Drawing number
Principal : A
O 8-4-1992 FIRST ISSUE Date:
Plant 1 : Plant 2 : Req/Ordernr : Rev: Code 102
Software Manual
6.12 Error Messages
Error messages Error situations may result in an error message being displayed on
screen. This subsection lists the error messages in alphabetical order,
and also provides information on how to solve the problem indicated
by the error message. If an error message is displayed, a beep will
also sound. The message is displayed for several seconds. If,
however, a key is pressed or the mouse is moved within that time
period, the message will disappear at once.
Alarm function different. Variable not appended: <type + tag no.>

The alarm function in the appended application has the same name
but other parameters. All alarm I/O assigned to this alarm are not
appended.
Block does not exist:

1. You entered a block name which is not present in your project
folder or which is not found in the root of the floppy disk.
2. You entered a file name with extension.
Block does not fit on screen.

The block you want to copy is too big.
Cannot be converted (drawn with other type of library).

You can only copy an FLD if the application that the FLD is copied
from was drawn with the same type of symbol library.
COM/FSC assignment changed: <type + tag no.>

Inconsistent assignment. Reassign.
Communication buffer memory overflow.

No more communication variables can be allocated.
Constant will not fit in the internal area.

If the constant symbol is changed to a larger value, the symbol will
exceed the I/O borders.
Corrupted block. Deleted from disk: <block name>

The block you want to select contains corrupted data. It has been
deleted from the disk.
Software Manual
Corrupted data detected in I/O data file at record: <record no.>
A record in the variable database is corrupted. The FLD design
editor will abort immediately. To rebuild the data files, start one of
the other options of FSC Navigator.
Corrupted data detected in installation file at record: <record no.>

The FLD design editor will abort immediately. To rebuild the data
files, start one of the other options of FSC Navigator. Some FLDs
may be considered empty by the program. You can copy the FLD
from your backup disks.
Database of application has different version: <version no.>

The application you try to use for copying or appending an FLD
has another software version. Conversion is required. The operation
is aborted.
Data error in installation file at record: <file name>

A record of the data file contains corrupted data.
Data error in FLD: <FLD no.>

The FLD indicated contains corrupted data. If possible, restore the
application from a floppy, or delete the FLD and design it again.
Data file too large. Try 'Rebuild' option to optimize file.

Use the Rebuild option of the 'System Configuration' option of FSC
Navigator. This may create some new space.
Different number of bits for multiplexer. Variable not appended:

<type + tag no.>
The multiplexer functions in the appended application and the main
application differ because of a different number of bits. This means
that the multiplexer I/O assigned to this multiplexer variable is not
appended to the main application.
Directory path not found.

Your system is corrupted. Exit FSC Navigator. Reboot your system
(hardware reset) and restart FSC Navigator. If the problem persists,
consult the dealer of your system.
DISK READ ERROR.

The program cannot read the complete contents of a file.
Software Manual
DISK WRITE ERROR.
The disk is full or corrupted. The data has not been saved. Try to
free space on the disk and retry with a previous back-up of your
application.
Drawn with old editor version: <version no.>

You will be asked whether the FLD should be converted.

You are not allowed to make two sheet transfers to the same
destination FLD using one sheet transfer symbol. If you want to
create two sheet transfers to the same FLD, make a line splitting
and connect this signal to a second sheet transfer of that destination
FLD.
Empty block.
You defined a block which does not contain a symbol that can be
manipulated.
Empty diagram cannot be copied.

You entered the name of an undefined FLD.
Equation file not found: <file name>

The file name you specified could not be found in the current
project folder.
Fault reset and/or force enable tag numbers not identical.

They must be identical. The append action is canceled.
File creation failed: <file name>

FSC Navigator attempted to create a file, but that failed (e.g.
because the disk is full).
File opening failed: <file name>

FSC Navigator attempted to open a file, but the file could not be
found on the disk.
FLD already exists.

You must enter the number of an FLD which has not been defined
yet.
Software Manual
<FLD name> not found on disk. Erase from application? Press
<Space>: Y/N
An FLD that you created earlier with the FLD design editor could
not be found in the project folder. If you answer 'Yes', all variables
related to this FLD will be deleted from the variable database, and
the FLD is considered to be empty. You may have deleted the FLD
"outside" FSC Navigator. However, it is better to use the 'Delete'
option of the FLD design editor.
FLD number: <FLD no.>. Illegal signal type(s): R <FLD no.>

<tag no.> <conversion source> <conversion target>.
Example: "FLD number: 13. Illegal signal type(s): R 13_0_1 W L".
An invalid conversion was made for a binary output or an off-sheet
reference. Use the signal conversion symbol (see page 6-60) to
create a conversion. Only downward conversions are allowed, e.g.
from word to byte or from float to word. Make sure that only
downward conversions have been defined.
FLD is corrupted: <FLD no.>

Some data which must be present in the sheet database is not
found. You must delete this FLD manually (e.g. using Windows
Explorer) and redefine the FLD. You will be asked whether you
want to erase the data belonging to this FLD from the FSC
database. You must enter 'Yes'.
FLD used twice. Application cannot be appended. Renumber

FLD: <FLD name>
The application to be appended must only use FLDs which do not
exist in the main application.
For printing logics with a laser printer, select functional logic

plotting.
Make sure that you select a laser printer as your plotter, and use the
'Print/Functional Logic Diagrams' command on the File menu of
FSC Navigator.
FSC system configurations are not identical.

The FSC system configurations must be identical. The append
action is canceled.
Software Manual
FSC system memory overflow.
The FSC system reached its maximum for this type of variable,
which means you can no longer place variables of this type. You
can try to create new variables by deleting variables of this type
which you no longer use. If you are sure the number of variables of
this type does not exceed the maximum, it is possible that your
database is corrupted. Use the 'System Configuration' option of
FSC Navigator to rebuild the database (with address reallocation).
Function block cannot be referenced.

You cannot make a sheet transfer to the output side of a function
block sheet, as a function block cannot have an off-sheet transfer.
Function block diagram in program block area: <FLD no.>

During an append action, some program blocks of the appended
application are located in the function block area of the main
application, or some function blocks are located in the program
block area of the main application. The append action will not be
executed.
Hardware allocation changed: <type + tag no.>

Inconsistent allocation. Reallocate.
Hardware allocation cleared: <type + tag no.>

Inconsistent hardware allocation and no allocation possible.
Illegal application name or block name, or file does not exist.

You entered an invalid file name or the name of a non-existing file.
Illegal connection.
The connection you tried to make is not allowed, or the signal type
is illegal for this symbol.
Illegal FLD number

The FLD number you entered is out of range.
Illegal function block input exchange:

Two function block input symbols on a function block are
exchanged. Place the function block input symbols as before, or
remove the function block call from the FLD. This check is only
active if 'On-line modification' has been set to 'Yes'.
Software Manual
Illegal function block output exchange:
Two function block output symbols on a function block are
exchanged. Place the function block output symbols as before or
remove the function block call from the FLD. This check is only
active if 'On-line modification' has been set to 'Yes'.
Illegal input/output.
The I/O you entered for the diagnostic input is invalid. It must be
allocated to a fail-safe module. You will also get this message if the
data record is corrupted.
Illegal location for this type of I/O.

This type of input or output cannot have this special location.
Illegal operation in I/O data file at record: <record no.>

Your index file is probably corrupted. Try the 'Rebuild' option of
the 'System Configuration' option of FSC Navigator.
Infinite signal cycle.

You made a cycle of connection lines which is not allowed.
Input already placed on FLD: <FLD no.>

You are not allowed to make two inputs with the same type and tag
number per CPU.
Input/output does not exist: <type + tag no.>

The input or output you want to use for the diagnostic input does
not exist.
Insufficient memory.
You do not have enough internal memory to run the FLD design
editor. Try to make room by removing resident programs and
drivers from your system. Before you restart the FLD design editor,
do a hardware reset or switch off your system and switch it on
again.
Invalid library version. You need version <version>.

The library contains a version number which is not compatible with
the software version you are using.
Invalid numeric order in equation table.

The input value must be in an ascending numerical order.
Software Manual
Invalid software version. You need version <version no.>
The FLDs are drawn with a later software version. Use the correct
software version.
Invalid value in equation table.

A value defined in the equation file is out of range. The range is
1E-38 to 1E+38.
Inverter must be connected to non-line symbol.

An inverter may only be connected to any of the following
symbols:
– at the front of logical functions and pulses.
– at the back of timers, pulses and constant boolean signals.
– at the set and reset input of timers and flip-flops.
– at the top and the bottom of rotated logical functions.
Lack of memory: <no. of bytes>

The window needed to shift a block of logics cannot be stored in
the memory. Try to free the amount of specified memory by
removing memory resident programs or drivers.
Link specification(s) of communication are not compatible.

They must be identical. The append operation is canceled.
Location <location> is reserved for internal FSC variables.

You attempted to assign a reserved location to an input or output
(e.g. 'SYS').
Locations not compatible: <type + tag no.>

During an append action, two I/O variables with the same type and
tag number both have a special location, but they are different. The
location of the I/O of the main application is maintained.
Missing data file: <file name>

If you just started a new application, go back to FSC Navigator's
main screen and open the project again. A new data file will then
be created. If this error message appears for an existing application,
restore a recent backup of the complete application.
Missing index file(s). Use 'System Configuration' to rebuild.

One or more of the index file are missing. Try the 'Rebuild' option
of the 'System Configuration' option of FSC Navigator. Unless the
data file is corrupted, it is enough to rebuild without address
reallocation.
Software Manual
Missing installation file: <file name>
If you just started a new application, go back to FSC Navigator's
main screen and open the project again. A new installation file will
then be created. If this error message appears for an existing
application, restore a recent backup of the complete application.
Modbus - RKE protocol specification not equal.

Modules not identical.

They must either be identical or undefined in one of the
applications. The append action is canceled.
MUX number or alarm group or PID number changed: <type +

tag no.>
Inconsistency. Another group or number assigned.
No more non fail-safe, safety-related inputs: <type + tag no.>

The input is erased from the appended FLD.
No more PID functions available: <type + tag no.>

The maximum number of PIDs allowed in the system has been
reached. Delete all PIDs that you do not use in the application logic
to make room for new PIDs ('System Configuration' option of FSC
Navigator \ 'Signal specs' option).
No more square root functions.

The number of square root functions per FLD is limited to 10.
Another limitation is the execution time of one FLD, which
effectively reduces the maximum number of square roots to 1 or 2.
No more symbols on this FLD or on FLD to be linked.

The FLD is full, which means that no more symbols can be placed.
If you are placing a sheet transfer symbol, it is also possible that the
program cannot place the related symbol on the FLD which is
referred to. You can save space by decreasing the number of
unnecessary line splittings.
No space on referenced FLD.

You attempted to make an FLD transfer to another FLD, but there
is no room in the I/O area on the referenced FLD to place the
related symbol. You might create new space by moving the I/O
closer to each other.
Software Manual
No FLD with legal block type found.
You are asked for a list of FLDs to select from, but the system does
not contain an FLD with a valid block type.
No such tag numbers found.

You asked for a list of tag numbers starting with a string you
entered. The system does not contain such tag numbers. If you did
not enter a string before the question mark, the system does not
contain any tag number of this type of variable.
Not enough entries in equation table.

The minimum number of entries in an equation table file is 3.
Not enough free disk space. Program will be aborted.

At startup of the FLD design editor, at least 10 Kbytes of free disk
space must be available.
Number of input bits must be a multiple of 4 for decimal I/O.

A BI or BO with hexadecimal data representation must have a
number of data bits which is a multiple of 4. Use the 'System
Configuration' option of FSC Navigator to change the number of
data bits.
One or more illegal symbols deleted.

After a block type change, some symbols are incompatible with the
new block type, or they have an illegal position. These symbols are
deleted.
Output already placed on FLD: <FLD no.>

You are not allowed to make two outputs with the same type and
tag number.
Passwords not identical.

PID already placed on FLD: <FLD no.>

You are not allowed to place a PID with the same tag number more
than once.
Rack positions in cabinet(s) not compatible.

They must be identical in both applications. The append action is
canceled.
Software Manual
Reference tag number blocked during on-line modification.
This error message will only appear if the SYM3 or SYM4 symbol
library is used and on-line modification is set to 'On'. The sheet
reference you want to make is not allowed because it is deleted, but
is still in use in the system. Try another position (or sequence
number) on the source or the destination FLD.
Reference to mnemonic sheet or non-logic sheet is not allowed.

You cannot transfer a signal to a non-logic sheet or a mnemonic
sheet.
Reference to other CPU not allowed.

You cannot make a sheet transfer to an FLD which is executed by
another CPU.
Safety values of marker input and marker output cannot be made

equal.
The safety values of the input and output cannot be made identical
because of a special location or different I/O modules.
Selection sheet corrupted. Selection sheet will be rebuilt.

Automatic recovery.
SER channel specification not equal.

Symbol is too large to move.

Symbols which are larger than the screen cannot be moved.
Symbol library corrupted.

The symbol library is corrupted and needs to be reinstalled.
Symbol overlap.
You attempted to place a symbol on a location which is already
occupied by another symbol. Try a new position.
Syntax error in equation table.

The equation table contains an illegal entry or text.
Text too long.

The text is too long to be placed on the screen. Modify the text, or
change the scale and/or number of strokes.
Software Manual
The I/O exists but is not placed on the correct FLD.
The I/O tag number you entered while making a sheet reference
exists, but the I/O is not present on the source FLD of the sheet
transfer.
This FLD has wrong block type.

The FLD number you entered is invalid because it does not have
the required block type, e.g. you want to place a function block but
you specified the number of an empty FLD or a program block
FLD.
Too many connection lines.

You made a path of connection lines which contains too many
lines.
Too many entries in equation table.

The maximum number of entries in an equation table file is 200.
Remove items from the equation table until the number of entries is
lower than 200.
Too many multiplexers or alarms. Variable not appended: <type +

tag no.>
The maximum number of multiplexers or alarms is reached, which
means the specified variable cannot be appended.
Variable allocated.
The variable has been allocated before.
Variable not found in I/O data file:

The variable is found on the current FLD, but it does not exist in
the I/O data file. The program will try to regenerate the variable. If
this is not successful, the variable will be erased from the FLD.
Wrong block type.

The FLD you want to copy has a different block type than the FLD
you are editing. This is not allowed.
Software Manual
Fail Safe Control
Section 7:
Printing
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 7: Printing
7.1 Introduction .................................................................................................... 7-1
7.2 Printing the Project Configuration ................................................................ 7-2

7.2.1 Introduction....................................................................................................................... 7-2
7.2.2 Selecting the Item for Printing .......................................................................................... 7-3
7.2.3 Previewing the Printer Output .......................................................................................... 7-4
7.2.4 Setting the Page Options ................................................................................................. 7-6
7.2.5 The First Page of All Printouts ......................................................................................... 7-7
7.2.6 Jumper Settings ............................................................................................................... 7-8
7.2.7 Installation Descriptions ................................................................................................... 7-9
7.2.8 Allocation of Hardware Modules .................................................................................... 7-10
7.2.9 Allocation Errors ............................................................................................................. 7-11
7.2.10 I/O Checklist ................................................................................................................... 7-12
7.2.11 Tag Number Allocations: Per I/O Module ...................................................................... 7-13
7.2.12 Tag Number Allocations: Per Rack ................................................................................ 7-14
7.2.13 Tag Number Allocations: Alphabetical/Loop Number .................................................... 7-17
7.2.14 Communication Configuration........................................................................................ 7-21
7.2.15 Alarm Configuration ....................................................................................................... 7-22
7.2.16 Graphic Rack Layout...................................................................................................... 7-23
7.3 Printing Functional Logic Diagrams ........................................................... 7-25

7.3.1 Introduction..................................................................................................................... 7-25
7.3.2 Selecting FLDs for Printing ............................................................................................ 7-27
7.3.3 Setting the Printing Options ........................................................................................... 7-28
7.3.4 Setting the Page Options ............................................................................................... 7-29
7.3.5 Previewing the FLD Output ............................................................................................ 7-30
Software Manual
Section 7: Printing i
FIGURES
Figure 7-1 Print button with submenu........................................................................................... 7-1

Figure 7-2 Printing the project configuration: main menu............................................................. 7-2
Figure 7-3 Previewing printer output of the system configuration ................................................ 7-4
Figure 7-4 Print Setup dialog for the current printer ..................................................................... 7-6
Figure 7-5 First page with application information........................................................................ 7-7
Figure 7-6 Jumper settings (CP 1) ............................................................................................... 7-8
Figure 7-7 Installation descriptions (SYM1 and SYM2)................................................................ 7-9
Figure 7-8 Allocation of hardware modules (all Central Parts)................................................... 7-10
Figure 7-9 Allocation errors listing .............................................................................................. 7-11
Figure 7-10 I/O check list.............................................................................................................. 7-12
Figure 7-11 Tag number listing I/O module related: module layout ............................................. 7-13
Figure 7-12 Specifying the rack(s) the print.................................................................................. 7-14
Figure 7-13 Tag number allocations per rack............................................................................... 7-16
Figure 7-14 Tag number allocations per rack............................................................................... 7-17
Figure 7-15 Tag number listing alphabetical/loop number (all) (signal specification) .................. 7-19
Figure 7-16 Tag number listing alphabetical/loop number (all) (hardware information)............... 7-20
Figure 7-17 Communication configuration.................................................................................... 7-21
Figure 7-18 Alarm configuration listing ......................................................................................... 7-22
Figure 7-19 Graphic rack layout ................................................................................................... 7-23
Figure 7-20 Rack layout................................................................................................................ 7-24
Figure 7-21 Printing functional logic diagrams ............................................................................. 7-25
Figure 7-22 Example of printed functional logic diagram (FLD) ................................................... 7-26
Figure 7-23 Print Setup dialog for the current printer ................................................................... 7-29
Figure 7-24 Previewing FLD output.............................................................................................. 7-30
TABLES
Table 7-1 Additional functions in print preview window............................................................... 7-5

Table 7-2 Variable allocations ................................................................................................... 7-15
Table 7-3 FSC variable types .................................................................................................... 7-18
Table 7-4 Additional functions in print preview window............................................................. 7-31
Software Manual
ii Section 7: Printing
Section 7 – Printing
7.1 Introduction
Printing FSC Navigator allows you to create hardcopy of two main items:
• project configuration (data stored in the project database), and
• functional logic diagrams (FLDs).
Note:
The FSC system can also output reports and SER events to a
printer that is directly connected to the FSC system. For details
on this type of printing refer to Section 5 of this manual.
The 'Print' option of FSC Navigator will only be available if a project

has been opened. If no project is open, you must either create a new
project or open an existing one (for details refer to Section 3 of this
manual).
The 'Print' option can be called in three ways:

• Menu bar: File / Print
• Button bar: Print
• Navigation area: FSC Safety Compliance / Print
If you select the 'Print' option, a submenu will appear, which allows
you to choose between printing the project configuration (see
subsection 7.2) or functional logic diagrams (see subsection 7.3).
Figure 7-1 Print button with submenu
Software Manual
Section 7: Printing 7-1
7.2 Printing the Project Configuration
7.2.1 Introduction
Printing the project If you choose the 'Print \ Project Configuration' option of FSC
configuration Navigator, the following window will be displayed:
Figure 7-2 Printing the project configuration: main menu
This dialog has three main options:

• Page Setup (File / Page Setup or the button)
Choose this option to define the page size, orientation, etc.
• Print Preview (File / Print Preview or the button)
Choose this option to preview the selected output before actually
printing it.
• Print (File / Print or the button)
Choose this option to print the selected item.
Software Manual
7-2 Section 7: Printing
7.2.2 Selecting the Item for Printing
Selecting the item The Select print output box contains all items that can be printed.
for printing You can choose from the following printing items:
• Jumper settings
This allows you to print all jumper settings of the hardware modules
in the FSC system (see subsection 7.2.6).
• Installation description
This allows you to print the installation descriptions that you
entered using the 'System Configuration' option of FSC Navigator
(Install \ Description) (see subsection 7.2.7).
• Allocation of hardware modules
This allows you to print a list of the allocation of hardware modules
per Central Part (see subsection 7.2.8).
• Allocation errors listing
This allows you to print all I/O tag numbers that have not been
allocated correctly (see subsection 7.2.9).
• I/O check list
This allows you to print a checklist that contains all channels of the
I/O modules in the FSC cabinet. This checklist can be used during
testing of the system wiring (see subsection 7.2.10).
• Tag number listing I/O module related: module layout
This allows you to print a list of all tag numbers that are allocated to
I/O modules (see subsection 7.2.11).
• Tag number listing: rack layout
This allows you to print a list of all tag numbers that are allocated to
particular racks (see subsection 7.2.12).
• Tag numbers listing: alphabetical/loop number
This allows you to print a list of all tag numbers of all variable types
in the system, together with their operating parameters
• Communication configuration
This allows you to print the communication configuration of an
• Alarm configuration
This allows you to print the alarm configuration of an application
• Graphic rack layout
This allows you to print a graphical representation of the layout of
individual racks (see subsection 7.2.16).
Software Manual
7.2.3 Previewing the Printer Output
Previewing the You can have a look at the printer output before actually printing
printer output anything. To do that, either choose the Print Preview option from the
File menu, or click the button. This will open a print preview
window, which contains an exact representation of what the selected
print item will look like on paper (see Figure 7-3).
Figure 7-3 Previewing printer output of the system configuration
Software Manual
Options in print The print preview window has a number of options that allow you to
preview window further inspect the output before actually printing it.
Table 7-1 below lists the various options with their functions:
Table 7-1 Additional functions in print preview window

Button Function
Exit the print preview window and return to the Print

Project Configuration dialog.
Print the current print item as shown in the print

preview window.
Zoom to fit the entire current page in the window.
Zoom to 100% (= default view).
Zoom to fit the full page width in the window.
Set a specific percentage to scale the print preview

to (between 15% and 250%).
Go to the first page (if print item consists of more

than one page).
Go to the previous page (if print item consists of

more than one page).
Go to a specific page (if print item consists of more

than one page).
Go to the next page (if print item consists of more

than one page).
Go to the last page (if print item consists of more

than one page).
Software Manual
7.2.4 Setting the Page Options
Setting the To set the page options before actually printing anything, either
page options choose the Page Setup option from the File menu, or click the
button. This will open the Print Setup dialog for the current printer.
Figure 7-4 below shows an example of such a print setup dialog
Note:
The exact look and feel of the Print Setup dialog as well as the
available configuration options depend on the currently selected
printer.
Figure 7-4 Print Setup dialog for the current printer
In the Print Setup dialog as shown above, you can typically set the
paper size (A4 or US Letter) and orientation (portrait or landscape) as
well as other print parameters. (You may need to choose the
Properties button to be able to modify the printer settings.)
Software Manual
7.2.5 The First Page of All Printouts
First page The first page of every printout contains general information about
the application. The printout will look something like this:
Configuration documents of application: DEMO_1 Date: 08-31-2000 Time: 11:19 Page: 1
Requirement class : 5
FSC system type specification : Redundant
Tag number fault reset input : RESET

Tag number force enable input : ENABLE
Tag number clock sync. input : CLOCK-SYNC
CPU chip size : 512 KBit

COM chip size : Variable
Prim. SER channel configuration: Yes

Primary SER system number : 1
Primary SER central part number: 1
Primary SER com. module : 1
Primary SER channel : B
Primary SER base : 200
Primary SER maximum : 216
Sec. SER channel configuration : Not used
Process safety time : 3 seconds

Interval time between faults : 4320 minutes
FSC-FSC timeout : 1.20 seconds
Simulation mode : None

Memory type : FLASH
Power-on mode : Cold start
On-line modification wanted : Yes
Central part 1 Rack number : 1

Central part 2 Rack number : 2
Slots central part bus(es) : 12
Cabinet Rack Rack Rack Rack Rack Rack Rack Rack Rack
1 2 3 4 5 6 7 8 9
1 1 2 3 4 5 - - - -
2 11 12 13 - - - - - 19
Figure 7-5 First page with application information
Software Manual
7.2.6 Jumper Settings
Jumper settings You can print all jumper settings of the hardware modules in the FSC
system. The printout will look something like this:
Jumper settings (see module layouts in FSC Hardware Manual)
Central part: Central part: 1
Module Rack Position Module Rack Position
CPU 1 1 6 J1: 1 J2: 1 J3: 1 J4: 0 J5: 0 J6: 1 J7: 1 J8: 1

J9: 0
WD 1 1 14 J1: 0 J2: 0 J3: 0
VBD 1 1 16 J1: 1 J2: 0 J3: 0 J4: 0 J5: 1 J6: 0
VBD 2 1 15 J1: 0 J2: 1 J3: 0 J4: 0 J5: 1 J6: 0
DBM 1 17 J1: On
COM 1 1 12 J1: EPROM J2: 0 J3: 0 J4: 1 J5: 1 J6: EPROM J7: EPROM J8: 27020
J9: Other
COM 2 1 10 J1: EPROM J2: 1 J3: 0 J4: 1 J5: 1 J6: EPROM J7: EPROM J8: 27020
J9: Other
COM 3 1 8 J1: 0 J2: 1
Figure 7-6 Jumper settings (CP 1)
Note:
If the application is not compiled before using this option, not
all information is available (e.g. the size of the EPROM). In that
case the following message is printed:
Compile first; not all jumper settings are known before
compilation.
Software Manual
7.2.7 Installation Descriptions
Installation You can print the installation descriptions that you entered using the
descriptions 'System Configuration' option of FSC Navigator (Install \
Description). The printout will look something like this:
Installation Descriptions
Number Description
1 Customer :
2 Principal :
3 Plant :
4
5 Req/Ordernr :
6 Rev
7 Date
8 Description
9 Chk'd
10 By:
11 Drawing number:
12 Code
13
14
15 Honeywell SMS BV
16
17 Honeywell NL33
18 HSMS Product Marketing
19 Branderijstraat 6
20 5223 AS 's-Hertogenbosch
21
22 Serial
23 Project
24 Unit
25 Sheet
26 Cnt'd
27
28 Tel +31 73-6273273
29 Fax +31 73-6219125
30 P.O. Box 116
31 5201 AC
32 's-Hertogenbosch
Figure 7-7 Installation descriptions (SYM1 and SYM2)
Software Manual
7.2.8 Allocation of Hardware Modules
Allocation of You can print a list of all hardware modules in the system.
hardware modules The printout will look something like this:
Allocation of hardware modules
Cabinet: 1
Position Rack: 1 SR Tested Voting EFM Rack: 2 SR Tested Voting EFM Rack: 3 SR Tested Voting EFM Rack: 4 SR Tested Voting EFM
1 10101/1/1 Yes Yes 1oo2D N/A 10101/1/1 No Yes 1oo1D N/A
3 10101/1/1 Yes Yes 1oo2D N/A 10209/1/1 No No 1oo1 N/A
6 10020/1/1 Yes Yes 10020/1/1 Yes Yes 10102/1/2 Yes Yes 1oo2D N/A 10209/1/1 No No 1oo1 N/A
8 10008/2/U Yes Yes 10008/2/U Yes Yes 10105/2/1 Yes Yes 1oo2D N/A 10102/1/1 No Yes 1oo1D N/A
9 ********* *** *** ********* *** *** 10101/1/1 Yes Yes 1oo2D N/A 10209/1/1 No No 1oo1 N/A
10 10024/F/F Yes Yes 10024/./. Yes Yes 10101/1/1 Yes Yes 1oo2D N/A 10101/1/1 No Yes 1oo1D N/A
11 ********* *** *** ********* *** *** 10201/2/1 Yes Yes 2oo2D N/A 10205/1/1 No Yes 1oo1D N/A
12 10014/H/I Yes Yes 10014/H/. Yes Yes 10201/2/1 Yes Yes 2oo2D N/A 10215/1/1 No Yes 1oo1D N/A
13 ********* *** *** ********* *** *** 10209/1/1 No No 2oo2 N/A 10216/1/1 No Yes 1oo1D N/A
14 10005/1/1 Yes Yes 10005/1/1 Yes Yes 10209/1/1 No No 2oo2 N/A 10209/1/1 No No 1oo1 N/A
15 10001/R/1 Yes Yes 10001/R/1 Yes Yes 10209/1/1 No No 2oo2 N/A 10209/1/1 No No 1oo1 N/A
16 10001/R/1 Yes Yes 10001/R/1 Yes Yes 10209/1/1 No No 2oo2 N/A 10205/1/1 No Yes 1oo1D N/A
17 10006/2/1 Yes Yes 10006/2/1 Yes Yes 10209/1/1 No No 2oo2 N/A 10209/1/1 No No 1oo1 N/A
18 ********* *** *** ********* *** *** 10209/1/1 No No 2oo2 N/A 10302/1/1 No Yes
19 10303/1/1 Yes Yes 10303/1/1 Yes Yes
20 10300/1/1 Yes Yes 10300/1/1 Yes Yes 10100/2/1 Yes Yes
21 ********* *** *** ********* *** *** 10100/2/1 Yes Yes 10100/2/1 No Yes
********* = Reserved for the second position of the module on the previous position.
Figure 7-8 Allocation of hardware modules (all Central Parts)
Software Manual
7.2.9 Allocation Errors
Allocation errors You can print a list of all I/O tag numbers that have not been
allocated correctly. This means that:
• for variables with location 'FSC', the system number is invalid.
• for variables with location 'COM', the COM channel has not been
specified (CP, COM module channel).
• for variables with location 'ANN', the alarm group or the alarm type
has not been specified.
• for all other variables, the combination of rack, position, channel
has not been fully specified.
The printout will look something like this:
Allocation Errors listing
Type Tag number Service Qualification Rack Position Channel Sheet number Module type
O SEC.SWITCH-OFF 0 0 0 No sheet -
XI KE-576-D1 DATA SELECT 4 0 0 No sheet -
XO MULTIPLEX MUX 10 4 5 0 No sheet 10209/1/1
BO 57SD-7210 SELECT DISP-1 4 17 0 No sheet 10209/1/1
BI 53PT-920.H MAIN LINE = 110 BAR - - - 102 -
BI 53PT-920.L MAIN LINE = 75 BAR - - - 102 -
BI 53FT-700.H MAIN LINE = 75% - - - 102 -
BI 53FT-700.L MAIN LINE = 30% - - - 102 -
BI 53_PT_920.H MAIN LINE = 110 BAR - - - 104 -
BI 53PT-930.L MAIN LINE = 10 BAR - - - No sheet -
BI 53PT-930.H MAIN LINE = 50 BAR - - - No sheet -
BO INPUT-FAILURE INPUT ALARM - - - 103 -
BO MAINLINE DIAGNOSTIC STATUS - - - 103 -
O INPUT_FAILURE INPUT ALARM ALARM - - - No sheet -
O MAINLINE DIAGNOSTIC STATUS 1 = HEALTHY - - - 122 -
Figure 7-9 Allocation errors listing
Software Manual
7.2.10 I/O Checklist
I/O check list You can print a checklist that contains all channels of the I/O
modules in the FSC cabinet. This checklist can be used during testing
of the system wiring. The printout will look something like this:
I/O check list Test date: By:
Cabinet: 1 Rack: 3 Position: 1 Module type: Digital input 24 Vdc FS (10101/1/1) Safety-related: Yes Tested: Yes Voting: 1oo2D
Channel Tag number Tested Remark Retested

1 53HS-101 | | |
2 Test_pushButton | | |
3 Ack_PushButton | | |
4 RESET-ALARM | | |
5 EARTH-LEAKAGE | | |
6 PSU-2 | | |
7 PSU-1 | | |
8 LAMPTEST | | |
9 FIRSTUP-RESET | | |
10 SHUTDOWN | | |
11 SENSOR-CP2 | | |
12 SENSOR-CP1 | | |
13 SENSOR-B1 | | |
14 SENSOR-B3 | | |
15 ENABLE | | |
16 RESET | | |
Cabinet: 1 Rack: 3 Position: 3 Module type: Digital input 24 Vdc FS (10101/1/1) Safty-related: Yes Tested: Yes Voting: 1oo2D

1 Transm.-Value | | |
2 Transm.-Value | | |
3 Max-Discrepancy | | |
4 Max-Discrepancy | | |
5 SENSOR-B2 | | |
6 SENSOR-A2 | | |
7 SENSOR-A1 | | |
8 SENSOR2 | | |
9 SENSOR3 | | |
10 SENSOR1 | | |
11 SENSOR_2 | | |
12 SENSOR-1 | | |
13 RESET-PUSHBUTTON | | |
14 TEST-PUSHBUTTON | | |
15 ACK-PUSHBUTTON | | |
16 ALARM-2 | | |
Cabinet: 1 Rack: 3 Position: 5 Module type: Analog input FS (10102/1/2) Safety-relaed: Yes Tested: Yes Voting: 1oo2D

1 53PT-920 | | |
2 53TT-900 | | |
3 PRESSURE | | |
4 MAINLINE | | |
Figure 7-10 I/O check list
Software Manual
7.2.11 Tag Number Allocations: Per I/O Module
Tag numbers You can print a list of all tag numbers that are allocated to I/O
allocations per modules. An allocation error list is also printed on the last page(s).
I/O module The printout will look something like this:
Tag number listing I/O Module related: Module layout
Channel Tag number

1 53HS-101
2 Test_pushButton
3 Ack_PushButton
4 RESET-ALARM
5 EARTH-LEAKAGE
6 PSU-2
7 PSU-1
8 LAMPTEST
9 FIRSTUP-RESET
10 SHUTDOWN
11 SENSOR-CP2
12 SENSOR-CP1
13 SENSOR-B1
14 SENSOR-B3
15 ENABLE
16 RESET
Channel Tag number

1 53HS-101
2 Test_pushButton
3 Ack_PushButton
4 RESET-ALARM
5 EARTH-LEAKAGE
6 PSU-2
7 PSU-1
8 LAMPTEST
9 FIRSTUP-RESET
10 SHUTDOWN
11 SENSOR-CP2
12 SENSOR-CP1
13 SENSOR-B1
14 SENSOR-B3
15 ENABLE
16 RESET
Figure 7-11 Tag number listing I/O module related: module layout
Software Manual
7.2.12 Tag Number Allocations: Per Rack
Tag number You can print a list of all tag numbers that are allocated to particular
allocations per rack racks. If there are more than one rack, you will be asked to specify
the first and the last rack number you want to print (see Figure 7-12
below).
Figure 7-12 Specifying the rack(s) the print
The default 'First' rack number is the lowest rack number that exists.
The default 'Last' rack number is the highest rack number that exists.
You can only enter existing rack numbers.
Software Manual
Variable allocations Table 7-2 below lists the variable types that can be allocated to the
various module types.
Table 7-2 Variable allocations

Module type Variable types that can be allocated to it
Digital input modules I, BI, XI
Digital output modules BI (location 'MUX'), O, BO, XO
Analog input modules AI
Analog output modules AO
For modules other than the ones listed in Table 7-2, the following is
printed:
− the module type,
− the Central Part number, and
− the module number.
For HBDs and VBDs, the following is printed:

− the Central Part number,
− the VBD number, and
− the module number.
Software Manual
Tag number listing: Rack layout Cabinet: 1 Rack: 1

|----------------------------------------------------------------------------------------------------------------------------------------------|
|Channel | 1 | | 2 | | 3 | | 4 | | 5 | | 6 | 10002/1/2 | 7 | |
|----------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | | | | | | CPU 1. 1 | |
| 2 | | | | | | **************** | |
| 3 | | | | | | **************** | |
| 4 | | | | | | **************** | |
| 5 | | | | | | **************** | |
| 6 | | | | | | **************** | |
| 7 | | | | | | **************** | |
| 8 | | | | | | **************** | |
| 9 | | | | | | **************** | |
| 10 | | | | | | **************** | |
| 11 | | | | | | **************** | |
| 12 | | | | | | **************** | |
| 13 | | | | | | **************** | |
| 14 | | | | | | **************** | |
| 15 | | | | | | **************** | |
| 16 | | | | | | **************** | |
|----------------------------------------------------------------------------------------------------------------------------------------------|
|Channel | 8 | 10008/2/U | 9 | 10008/2/U | 10 | 10004/F/F | 11 | 10004/F/F | 12 | 10004/H/I | 13 | 10004/H/I | 14 | 10005/1/1 |
|----------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | COM 1. 3A | COM 1. 3B | COM 1. 2A | COM 1. 2B | COM 1. 1A | COM 1. 1B | WD 1. 1 |
| 2 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 3 | UCN | Undefined | Modbus RTU | Modbus RTU | FSC-FSC | Development sys. | **************** |
| 4 | 10008/U/1 | **************** | 10004/F/1 | 10004/F/1 | 10004/H/1 | 10004/I/1 | **************** |
| 5 | | **************** | (RS232 multidrop | (RS232 multidrop | (RS422 readback) | (RS485) No encod | RESET |
| 6 | **************** | **************** | 19K2,n,8,1,n | 19K2,n,8,1,n | 2M,n,8,1,n | 19K2,n,8,2,n | |
| 7 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 8 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 9 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 10 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 11 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 12 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 13 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 14 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 15 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 16 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
|----------------------------------------------------------------------------------------------------------------------------------------------|
|Channel | 15 | 10001/R/1 | 16 | 10001/R/1 | 17 | 10006/2/1 | 18 | 10006/2/1 | 19 | 10303/1/1 | 20 | 10300/1/1 | 21 | 10300/1/1 |
|----------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | VBD 1. 2 | VBD 1. 1 | DBM 1. 1 | DBM 1. 1 | PSD 1. 1 | PSU 1. 1 | PSU 1. 1 |
| 2 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 3 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 4 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 5 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 6 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 7 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 8 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 9 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 10 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 11 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 12 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 13 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 14 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 15 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
| 16 | **************** | **************** | **************** | **************** | **************** | **************** | **************** |
|----------------------------------------------------------------------------------------------------------------------------------------------|
**************** = This channel is not an I/O channel (only printed on positions which contain a module).
Figure 7-13 Tag number allocations per rack
Software Manual
7.2.13 Tag Number Allocations: Alphabetical/Loop Number
Tag number You can print a list of all tag numbers of all variable types in the
allocations: system, together with their operating parameters such as power-on
alphabetical / values, rack, position, channel (I/O tag numbers), etc. Please note that
loop number only existing tag numbers will be listed. This means that if, for
example, no analog inputs have been defined, no analog inputs will
be printed (and no page for analog inputs will be reserved).
You will first be prompted to specify which tag numbers should be
included in the list:
Figure 7-14 Tag number allocations per rack
There are three main options to choose from:

• All: To print all variables in the database.
• I/O: To print all digital inputs (DI), digital outputs (DO),
binary inputs (BI), binary outputs (BO), analog inputs
(AI), and analog outputs (AO).
• Specific: To print a specific type of variables (see next page).
Software Manual
'Specific' option The 'Specific' option can be used to print all tag numbers of a specific
variable type, together with their operating parameters such as
power-on values, rack, position, channel (I/O tag numbers), etc.
If no tag numbers of the selected type exist, no list will be created.
Variable type You need to specify the variable type you wish to print.
Choose the desired type from the drop-down list. Table 7-3 below lists
the variable types that are supported.
Table 7-3 FSC variable types

Type Description Type Description
A Alarm O Digital output
AI Analog input P PID control function
AO Analog output R Register
BI Binary input T Timer
BO Binary output XI Input multiplexer
C Counter XO Output multiplexer
I Digital input
M Marker
Depending on the variable type selected, you may need to specify

some other parameters:
• Search method,
• Text to search, and/or
• First part of tag number to search.
Search method If you selected 'I', 'AI', 'BI', 'XI', 'O', 'AO', 'BO', 'XO', 'P', or 'A' as the
variable type, you need to specify how the tag numbers will be
searched. You can choose to create the tag number list searched by
prefix, description, or loop number, which are all part of the tag
number. A tag number typically consists of three parts:
Tag number = <Prefix>'_'<Description>'_'<Loop number>
(e.g. AI_TRANSMITTER_01)
Choose the desired search method from the drop-down list:

• by prefix,
• by description, or
• by loop number.
Software Manual
Text to search for If you selected 'I', 'AI', 'BI', 'XI', 'O', 'AO', 'BO', 'XO', 'P', or 'A' as the
variable type, you also need to enter the text string that tag numbers
must match to be included in the list.
First part of tag number If you selected 'M', 'C', 'T', or 'R' as the variable type, you need to
to search specify the first part of the tag number to search. If you do not enter a
tag number, all tag numbers of the selected type will be included in
the list.
Input signal specification
Type Tag number Service Qualification Location Unit Subunit Sheet Safety Force En. Write En. SER En. SER seq. no.
I 53HS-101 LAMPTEST TEST MCP 102 Yes Yes No No -

I 53_HS_101 LAMPTEST "TEST" MCP 104 Yes Yes No No -
I 91XA-651A Door switch Close AH 5000 91UZ-650 0 Yes No No No -
I ACK-PUSHBUTTON PNL 107 Yes Yes No No -
I ACKNOWLEDGE DCS 106 Yes Yes No No -
I AF_Audible ANN 105 No No No No -
I AF_Common_Alarm ANN 105 No No No No -
I ALARM-1 ALARM STATUS DCS 107 Yes Yes No No -
I ALARM-2 ALARM STATUS DCS 107 Yes Yes No No -
I AUDIBLE ANN 107 No No No No -
I Ack_PushButton PNL 105 Yes Yes No No -
I CENTR.PART-FAULT System marker SYS 0 Yes No No No -
I CLOCK-SYNC FSC-CLOCK-SYNCHRON. CLOCK-SYNC SYS 0 No No No No -
I COMMON ANN 107 No No No No -
I DEVICE-COM.FLT System marker SYS 0 Yes No No No -
I EARTH-LEAKAGE EARTH LEAKAGE PSU'S NO FAILURE CAB 123 Yes Yes No No -
I ENABLE FORCE-ENABLE ENABLE SYS 0 Yes No No No -
I EXT.COMMUNIC.FLT System marker SYS 0 Yes No No No -
I FIRSTUP-ALARM-1 SUBLOCAION-FSC FIRSTUP FLAG DCS 107 Yes Yes No No -
I FIRSTUP-ALARM-2 SUBLOCATION-FSC FIRSTUP FLAG DCS 107 Yes Yes No No -
I FIRSTUP-RESET DCS 106 Yes Yes No No -
I FLASHER-0.5Hz System marker SYS 107 No No No No -
I FLASHER-1Hz System marker SYS 107 No No No No -
I FLASHER-2Hz System marker SYS 105 No No No No -
I FSC-SYSTEM-FAULT System marker SYS 123 Yes No No No -
I INPUT-FAILURE System marker SYS 122 Yes No No No -
I INT.COMMUNIC.FLT System marker SYS 0 Yes No No No -
I IO-COMPARE System marker SYS 120 Yes No No No -
I IO-FORCED System marker SYS 0 Yes No No No -
I LAMPTEST LAMPTEST TEST PNL 123 Yes Yes No No -
I OUTPUT-FAILURE System marker SYS 0 Yes No No No -
I PSU-1 PSU-1 24VDC NO FAILURE CAB 123 Yes Yes No No -
I PSU-2 PSU-2 24VDC NO FAILURE CAB 123 Yes Yes No No -
I RED.INPUT-FAULT System marker SYS 0 Yes No No No -
I RESET FSC-FAULT-RESET RESET SYS 121 Yes No No No -
I RESET-ALARM RESET ALARM RESET CAB 123 Yes Yes No No -
I RESET-PUSHBUTTON PNL 107 Yes Yes No No -
I SENSOR-1 109 Yes Yes No No -
I SENSOR-A1 111 Yes Yes No No -
I SENSOR-A2 111 Yes Yes No No -
I SENSOR-B1 112 Yes Yes No No -
I SENSOR-CP1 113 Yes Yes No No -
I SENSOR-CP2 113 Yes Yes No No -
I SENSOR1 110 Yes Yes No No -
I SENSOR_2 109 Yes Yes No No -
Figure 7-15 Tag number listing alphabetical/loop number (all)

(signal specification)
Software Manual
Input hardware information
Type Tag number Rack Pos Chan Sensor Sensconf Max. on. Max. discr. Rack2 Pos2 Chan2 Rack3 Pos3 Chan3 Bit no. Modbus PLC address
I 53HS-101 3 1 1 FS 8 - -
I 53_HS_101 3 9 3 FS 42 - -
I 91XA-651A 3 9 13 Red R 2O2 480 M 10 S 3 9 14 36 - 2002
I ACK-PUSHBUTTON 3 3 15 FS 22 - -
I ACKNOWLEDGE 3 9 11 FS 34 - -
I AF_Audible - - - - 5471 -
I AF_Common_Alarm - - - - 5468 -
I ALARM-1 3 9 9 FS 32 - 1020
I ALARM-2 3 3 16 FS 23 - -
I AUDIBLE - - - - 5551 -
I Ack_PushButton 3 1 3 Red R 2O2 480 M 10 S 3 9 12 10 - -
I CENTR.PART-FAULT - - - - 0 - -
I CLOCK-SYNC 3 9 15 FS 38 - -
I COMMON - - - - 5548 -
I DEVICE-COM.FLT - - - - 9 - -
I EARTH-LEAKAGE 3 1 5 FS 12 - -
I ENABLE 3 1 15 FS 6 - -
I EXT.COMMUNIC.FLT - - - - 13 - 3
I FIRSTUP-ALARM-1 3 9 10 FS 33 - -
I FIRSTUP-ALARM-2 3 9 8 FS 47 - -
I FIRSTUP-RESET 3 1 9 FS 0 - -
I FLASHER-0.5Hz - - - - 4 -
I FLASHER-1Hz - - - - 3 -
I FLASHER-2Hz - - - - 2 -
I FSC-SYSTEM-FAULT - - - - 15 - -
I INPUT-FAILURE - - - - 6 - -
I INT.COMMUNIC.FLT - - - - 11 - -
I IO-COMPARE - - - - 14 - -
I IO-FORCED - - - - 8 - -
I LAMPTEST 3 1 8 FS 15 - -
I OUTPUT-FAILURE - - - - 7 - -
I PSU-1 3 1 7 FS 14 - -
I PSU-2 3 1 6 FS 13 - -
I RED.INPUT-FAULT - - - - 10 - -
I RESET 3 1 16 FS 7 - 40
I RESET-ALARM 3 1 4 FS 11 - -
I RESET-PUSHBUTTON 3 3 13 FS 20 - -
I SENSOR-1 3 3 12 FS 19 - -
I SENSOR-A1 3 3 7 FS 30 - -
I SENSOR-A2 3 3 6 FS 29 - -
I SENSOR-B1 3 1 13 FS 4 - -
I SENSOR-B2 3 3 5 FS 28 - -
I SENSOR-B3 3 1 14 FS 5 - -
I SENSOR-CP1 3 1 12 FS 3 - -
I SENSOR-CP2 3 1 11 FS 2 - -
I SENSOR1 3 3 10 FS 17 - -
I SENSOR2 3 3 8 FS 31 - -
I SENSOR3 3 3 9 FS 16 - -
I SENSOR_2 3 3 11 FS 18 - -
Figure 7-16 Tag number listing alphabetical/loop number (all)

(hardware information)
The addresses in the rightmost column of the listing above can have
the following values:
<value>: Address value
'-' (dash): An address is possible but none has been assigned.
' ' (space): No address possible.
Software Manual
7.2.14 Communication Configuration
Communication You can print the communication configuration of an application. A

configuration list will then be created showing the configuration of all used
channels (i.e. channels that are not 'undefined'), as well as all
variables allocated to the communication channels.
Channel configuration of central part 1, module 2, channel A.
Protocol : Modbus RTU

Redundant : Yes
Network : Multidrop
Link status : Primary
Connected system : None
Timeout : 25 (100 ms)
Interface : 10004/F/1 (RS232 multidrop)
Baud rate : 19K2
Handshake : None
Number of stop bits : 1
Number of bits/char : 8
Parity : None
Communication address : 4
Link specification
Marker bytes : bit start address : 2256
Marker bytes : to FSC 1 from device: 200
Marker bytes : from FSC 1 to device: 200
Register bytes: byte start address : 2336

Register bytes: to FSC 1 from device: 200
Register bytes: from FSC 1 to device: 200
Channel configuration of central part 1, module 2 , channel A.
Link specification
Rel. bit no. Type Tag number Service Qualification Unit Subunit Sheet Safety SER En. SER seq. no. Power-on
1 I XK7F30A Gasleak test Start F3300 Burner 1 10 Yes Yes 1105 Off
Figure 7-17 Communication configuration
Software Manual
7.2.15 Alarm Configuration
Alarm You can print the alarm configuration of an application. A list will
configuration then be created showing all alarm groups and all allocated variables
of each alarm group.
Alarm configuration
Alarm group : A AF_AlarmPoint2

Alarm group number: 2
Alarm sequence : AF
Alarm group size : 16
Start address : 5456
Rel. bit no. Type Tag number Service Qualification Unit Subunit Sheet Safety SER En. SER seq. no. Alarm type
12 I AF_Common_Alarm 105 No No - Common alarm

15 I AF_Audible 105 No No - Audible
1 O AF_Acknowledge2 101 No No - Acknowledge
4 O AF_Flasher_1 105 No No - Flasher 1
Type Tag number Rack Pos Chan
O AF_AlarmPoint2 3 11 3
Figure 7-18 Alarm configuration listing
Software Manual
7.2.16 Graphic Rack Layout
Graphic rack You can print a graphical representation of the layout of individual
layout racks. If there are more than one rack, you will be asked to specify
the first and the last rack number you want to print (see Figure 7-19
below).
Figure 7-19 Graphic rack layout
The default 'First' rack number is the lowest rack number that exists.
The default 'Last' rack number is the highest rack number that exists.
You can only enter existing rack numbers.
The printout will include all modules that are placed in one rack.
Scale to fit on paper If you want the cabinet to be printed in such a way that it fits on the
selected paper size, make sure that the Scale to fit on paper
checkmark is selected ( ).
Software Manual
13 14 15 16 17 18 19 20 21
10201/1/1 10201/1/1 10201/1/1 10201/1/1
XI-2101-25 XI-2101-25 Count_out Count_out
System no. : 1
Cabinet : 1
Rack : 4
Figure 7-20 Rack layout
Software Manual
7.3 Printing Functional Logic Diagrams
7.3.1 Introduction
Printing FLDs If you choose the 'Print \ Functional Logic Diagrams' option of FSC
Navigator, the following window will be displayed:
Figure 7-21 Printing functional logic diagrams
This dialog has three main options:

• Page Setup (File / Page Setup or the button)
Choose this option to define the page size, orientation, etc.
• Print Preview (File / Print Preview or the button)
Choose this option to preview the selected output before actually
printing it.
• Print (File / Print or the button)
Choose this option to print the selected item.
Software Manual
Figure 7-22 below shows an example of a printed FLD.
M 53HS-101 3
C LAMPTEST 1
P "TEST" 1
C 53PT-920.H 1 40003
O MAIN LINE = 110 BAR 2 3 53PT-920.H M
M Signal type: W A >1
_ 11 HIGH ALARM C
> 1 5 "ALARM" P
53PT-920 3 A D 5 53PRA-920
5 1
MAIN LINE PRESSURE D A MAIN LINE PRESSURE
1 1
102 MAIN LINE PRESSURE

103 1 Signal type: F
3 53PT-920.L M
>1
_ 11 LOW ALARM C
> 1 6 "ALARM" P
C 53PT-920.L 1 40004
O MAIN LINE = 75 BAR 2
M Signal type: W A
3 A D 5
53TT-900 53TR-900
5 1
MAIN LINE TEMP D A MAIN LINE TEMP
2 2
102 MAIN LINE TEMP

103 Signal type: F
2
C 53FT-700.H 1 40001
O MAIN LINE = 75% 2 3 53FT-700.H M
S
M Signal type: W A 0 t >1
_ 11 HIGH ALARM C
> 1 1 "ALARM" P
t=30 S
R
MAIN LINE FLOW 101
Signal type: F 102 1
S 3 53FT-700.L M
0 t >1
_ 11 HIGH ALARM C
> 1 2 "ALARM" P
C 53FT-700.L 1 40002 t=30 S
O MAIN LINE = 30% 2 R
M Signal type: W A
E Customer : Honeywell NL33

FUNCTIONAL LOGIC DIAGRAMS
D Principal : HSMS Product Marketing
C UNIT 5300
Plant : Branderijstraat 6
B Tel +31 73-6273273 Date 30-5-1997 By: PM NL33
A 5223 AS 's-Hertogenbosch
Honeywell SMS BV Fax +31 73-6219125
P.O. Box 116
Drawing number:
O 30-5-1997 FIRST ISSUE Req/Ordernr : SPEC & TECH DEMO_1 102 103
5201 AC
Serial Unit
Rev Date Description Chk'd 's-Hertogenbosch Project Sheet Cnt'd
Code Code
Figure 7-22 Example of printed functional logic diagram (FLD)
Addresses in The printed FLDs include the Modbus addresses for all variables that
printed FLDs are allocated to communication modules. However, for all 10008/2/U
and 10018/2/U communication modules (FSC-SMM), DCS addresses
are shown rather than Modbus addresses.
Software Manual
7.3.2 Selecting FLDs for Printing
Selecting FLDs The dialog as shown in Figure 7-21 has two boxes. The box on the
for printing left ('Available sheets') lists all FLDs that are included in the current
application and are available for printing. The box on the right
('Selected sheets') lists the FLDs that have been selected for printing.
In the example shown in Figure 7-21, FLDs 109 and 112 are selected
for printing.
To select an FLD for printing, click on the appropriate FLD in the left
box, and choose the > button. The FLD will now be moved from the
left to the right box to indicate it has been selected for printing.
Similarly, to unselect an FLD for printing, click on the appropriate
FLD in the right box, and choose the < button.
Notes:
1. You can select multiple list items by holding down the
CTRL key while selecting them.
2. To select a group of items that are next to each other, hold
down the SHIFT key and click the first and last list item you
want to select.
3. To select or unselect all FLDs for printing, choose the >> or
<< button, respectively.
Software Manual
7.3.3 Setting the Printing Options
Printing options The dialog as shown in Figure 7-21 on page 7-25 provides a number
of options that allow you to define the printer settings for the
functional logic diagram(s) to be printed:
• Output destination,
• Blank printing paper,
• X-Translation, and
• Y-Translation.
Output destination You can choose to output the selected FLD(s) to paper or write them
to a plot file (HPGL).
• Graphical device: Outputs the drawings to paper (= default).
• File (HPGL): Writes the drawings to a plot file (*.PLT).
You can use this file to print to a plotter or
laser printer that can handle HPGL
instructions (or you must use an HPGL
interface or HPGL emulation program). The
file name will be <FLD no.>.PLT, located in
the project folder (e.g. 112.PLT).
Blank printing paper Here you specify whether you use blank paper or preprinted paper. If
you use preprinted paper, no title block and sheet borders will be
drawn. If you use blank paper, make sure the checkmark is selected
( ) (which is also the default).
X translation / You can enter two coordinates (X and Y) for positioning the selected
Y translation FLD(s) on the paper. This may be necessary for some graphical
devices in order to move the drawing into the printable area. The X
and the Y coordinate may be positive or negative. The value must be
entered as points (28 pts = approx. 1 cm; 72 pts = approx. 1 inch).
Software Manual
7.3.4 Setting the Page Options
Setting the To set the page options before actually printing anything, either
page options choose the Page Setup option from the File menu, or click the
button. This will open the Print Setup dialog for the current printer.
Figure 7-23 below shows an example of such a print setup dialog
Note:
The exact look and feel of the Print Setup dialog as well as the
available configuration options depend on the currently selected
printer.
Figure 7-23 Print Setup dialog for the current printer
In the Print Setup dialog as shown above, you can typically set the
paper size (A4 or US Letter) and orientation (portrait or landscape), as
well as other print parameters. (You may need to choose the
Properties button to be able to modify the printer settings.)
Software Manual
7.3.5 Previewing the FLD Output
Previewing the You can have a look at the FLD output before actually printing
FLD output anything. To do that, either choose the Print Preview option from the
File menu, or click the button. This will open a print preview
window, which contains an exact representation of what the selected
FLD(s) will look like on paper (see Figure 7-24).
Figure 7-24 Previewing FLD output
Software Manual
Options in print The print preview window has a number of options that allow you to
preview window further inspect the output before actually printing it.
Table 7-4 below lists the various options with their functions:
Table 7-4 Additional functions in print preview window

Button Function
Exit the print preview window and return to the Print

Project Configuration dialog.
Print the current FLD(s) as shown in the print

preview window.
Zoom to fit the entire current page in the window.
Zoom to 100% (= default view).
Zoom to fit the full page width in the window.
Set a specific percentage to scale the print preview

to (between 15% and 250%).
Go to the first page (if multiple FLDs are to be

printed).
Go to the previous page (if multiple FLDs are to be

printed).
Go to a specific page (if multiple FLDs are to be

printed).
Go to the next page (if multiple FLDs are to be

printed).
Go to the last page (if multiple FLDs are to be

printed).
Software Manual
Software Manual
Fail Safe Control
Section 8:
Translating an Application
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 8: Translating an Application
8.1 Introduction .................................................................................................... 8-1
8.2 Prerequisites .................................................................................................. 8-2
8.3 Compiler Operation........................................................................................ 8-3

8.3.1 Translation Process ......................................................................................................... 8-3
8.3.2 Output Files ...................................................................................................................... 8-4
8.3.3 Compiler Registers and Markers ..................................................................................... 8-6
8.3.4 Simulation Mode............................................................................................................... 8-6
8.4 Error Messages and Warnings ...................................................................... 8-8
Software Manual
Section 8: Translating an Application i
FIGURES
Figure 8-1 Warnings and messages screen................................................................................. 8-4
TABLES
Table 8-1 EPROM sizes .............................................................................................................. 8-7

Table 8-2 Digital I/O allocation error and secondary switch-off ................................................ 8-14
Software Manual
ii Section 8: Translating an Application
Section 8 – Translating an Application
8.1 Introduction
Translating After the FSC system has been configured and the functional logic
an application diagrams (FLDs) have been designed, the application must be
translated into code that can be used by the FSC processor(s). This
translation is done by the compiler. The compiler also checks if errors
were made during the configuration and design stage.
The 'Translate Application' option can be called in three ways:
• Menu bar: Project / Translate Application

• Buttons bar: Translate
• Navigation area: FSC Project Configuration / Translate
Application
Note:
An application can only be translated if the project folder
contains a number of files. If any of the files are not present or it
they are corrupted, an error message will be displayed, and the
translation process will be aborted.
Software Manual
Section 8: Translating an Application 8-1
8.2 Prerequisites
Prerequisites A number of conditions must be met for correct translation. They are
related to FLD numbering and function blocks.
FLD numbers The FLDs are translated by FLD number (in descending order). This
means that the FLD with the highest number is translated first and the
FLD with the lowest number last.
If an FLD was designed in FSC Navigator but is not present in the
project folder, it will be ignored. If one or more FLDs are missing, an
error is generated with the FLD number of the first FLD that is
detected missing.
Function blocks The following conditions must be met with regard to function blocks:
1. Function blocks must have higher FLD numbers than program
blocks and step blocks in order to ensure that they are translated
first.
2. The first function block must have an FLD number that is at least
2 higher than the program block (or step block) with the highest
FLD number.
3. The nesting of the function blocks must be such that the function
block which is nested deepest is translated first (i.e. has a higher
FLD number).
Software Manual
8-2 Section 8: Translating an Application
8.3 Compiler Operation
8.3.1 Translation Process
Translation The 'Translate Application' option of FSC Navigator translates all the
process functional logic diagrams (FLDs) that were designed using the FLD
design editor and that are present in the project folder.
Note:
Every time an application is translated, its version counter is
incremented by one. Please note that the version counter is also
incremented if the application is converted to a newer FSC
Navigator version.
Before a correct translation can be made, the FLDs must be

syntactically correct (for example, all required connections must have
been made). The application compiler checks whether the FLDs can
be translated, and will generate error messages if any errors are
detected. It will also give warnings when the syntax is correct, but
probably does not match the intention of the programming engineer
(e.g. if a function block input has not been connected). All messages
are written to a log file and displayed on screen.
The compiler will always try to find as many errors as possible, which
means that the translation of an FLD continues after an error has been
detected. This is the reason that some errors are reported more than
once (e.g. if more than one signal has been connected to the same
node). The compiler will also continue to translate all subsequent
FLDs.
After the translation has ended, the number of errors and warnings is
written to the log file. If severe errors occur, the translation is aborted
automatically and no additional data is reported.
On-screen The compiler displays on-screen status information during the

status information translation (see Figure 8-1). The colors of the warnings, messages and
errors depend on the color settings of FSC Navigator. For details refer
to Section 3 of this manual ("Using FSC Navigator").
Software Manual
Figure 8-1 Warnings and messages screen
Aborting the You can abort the translation process any time by pressing the <Esc>
translation process key. The compiler will then report a manual interrupt, and writes the
time and date of interruption to the log file.
8.3.2 Output Files
Output files If translation is successful, the compiler will generate one or more
output files from all FLDs that have been found to be syntactically
correct. The compiler may generate three types of files:
• A log file,
• Application code files, and
• Communication files (if COM modules are used).
Software Manual
Note:
If the compiler detects an error, no output files are generated
except the log file.
Log file The log file (<Application name>.LOG) contains all messages, errors
and warnings that were generated by the compiler. This file can be
printed or displayed on screen using the 'View Log' option of FSC
Navigator. For details on log files refer to Section 9 of this manual
("Log Files").
Application code files These files contain the FSC program code for the various processors
in the Central Part(s). They can be programmed into EPROMs or
loaded into flash memory.
One application code file (<Project name>.O<CP no.>1) will be
generated for the CPU of each Central Part. The first digit in the file
extension refers to the Central Part number; the second digit is always
'1'. For example, TEST_1.O21 is the file for Central Part 2.
Communication files These files are only generated if communication (COM) modules are
used. They contain the firmware for the COM module(s) in the
Central Part(s). The files can be programmed into EPROMs or loaded
into flash memory.
One communication file (<Application name>.C<number>) will be
generated for each COM module of each Central Part. The number in
the file extension refers to the Central Part number (first digit) and the
COM module sequence number (second digit). For example,
TEST_1.C13 is the communication file for Central Part 1, COM
module 3.
Default The compiler will also create a default SER format file if no
SER format file user-defined SER format file was found.
The default format file is identical to the default SER file which is
created if the SER format is specified for the first time using the 'SER
format' option of FSC Navigator.
For details on SER format files refer to Section 5 of this manual
("Editing Reports and SER Format").
Software Manual
8.3.3 Compiler Registers and Markers
Compiler registers During translation, compiler registers or markers may be introduced.

and markers These special registers and markers are needed to store intermediate
results or to store feedback results which are required in the next
program cycle.
The compiler markers and registers can be recognized by their tag
number, which always starts with the character 'C' (Compiler). The
different types of compiler markers and registers can be distinguished
visually by their service text.
There are various types of markers and registers:

• Compiler markers.
Compilers markers are used to store an intermediate boolean result.
• Compiler registers.
Compilers registers are used to store an intermediate binary result.
• Feedback markers.
Feedback markers are used to store a boolean feedback result.
• Feedback registers.
Feedback registers are used to store a binary feedback result.
If an FLD is changed and translated again, the compiler markers and

compiler registers that are no longer required are erased from the
variable database.
8.3.4 Simulation Mode
Simulation mode An application can be translated in simulation mode, which means

that the application variables can be forced or written regardless of
the force-enable status. This allows application software of large
systems to be tested on an FSC simulation unit.
The number of variables that can be forced or written regardless of the
force enable status depends on the configured EPROM size (see Table
8-1).
Software Manual
Table 8-1 EPROM sizes
Maximum number of
EPROM size
force/write variables
512 K 2,080
1M 8,192
2M 20,800
4M 44,800
If the number of variables of the same type in the original application

exceeds the maximum number, the remaining variables of that type
cannot be forced or written. The compiler will then give a warning.
The application software is stored in RAM which is located on the

memory boards on the Central Processing Unit (CPU).
Simulation The hardware configuration of the test systems is fixed. For details on
hardware the hardware contained in the simulation units refer to Appendix H of
this manual ("Simulation Mode").
COM channels in The communication (COM) channels of a simulated project can be

simulation mode assigned by the user. At least one channel must be a Development
System channel.
Addressing in To be able to reset the tested system, the Reset input is located on a
simulation mode default address, although it may be anywhere else in the original FSC
system. The default address of the reset input depends on the selected
simulation unit (see Appendix H of this manual for details).
The input and output modules will get the same address as in the
non-simulated system. This means that the inputs that have the same
address as the Force Enable and Reset inputs in the simulated system
cannot be debugged normally. Their location should be changed to
'COM'.
Software Manual
8.4 Error Messages and Warnings
Error messages FSC Navigator will create a translation log file which contains the
and warning following information:
1. All errors found in the FLDs and databases during translation.
2. All warnings that were generated during translation. (They refer to
instances where the code is syntactically correct but will probably
not perform the function intended by the design engineer.)
3. Some translation data (e.g. the number of markers used in the
application program).
Note:
If the compiler detects an error, no output files are generated
except the log file.
Node (x, y) Several error messages are followed by the expression 'Node (x, y)'.
These refer to the coordinates in an FLD where the item is located
that causes the error. It is the FLD position that is x grid points from
the left side of the FLD and y grid points from the FLD top.
The translation file will typically include the number of the affected
FLD. In the FLD editor, the node coordinates are displayed in the
bottom-right corner of the screen.
FLD number If a message contains an FLD number, the specified variable is

located in this FLD. If no FLD number is provided, this means that
the variable (tag number) is not used in any FLD.
Error messages Below you will find all error messages and warning that may be
and warnings included in the translation log file, in alphabetical order.
A functional logic diagram must contain at least one output

symbol.
Description: At least one output symbol (output, BO, off-sheet
reference, etc.) is required on each functional logic diagram.
Solution: Make sure that each FLD contains at least one output
symbol.
Software Manual
Alarm group number undefined: <type> <tag no.>
Description: The alarm group number of the specified variable
(with location 'ANN') has not been specified.
Solution: Use the 'System Configuration' option of FSC Navigator
(Hardware Specs option) to specify the alarm group number.
Alarm group size undefined: <type> <tag no.>

Description: The group size of the alarm group has not been
specified.
to specify the group size, or delete the variable.
Alarm type undefined: <type> <tag no.>

Description: The alarm type of the specified variable (with
location 'ANN') has not been specified.
(Hardware Specs option) to specify the alarm type.
Alarm variable declared more than once: <type> <tag no.>

Description: The alarm type of the variable (Location 'ANN') has
already been specified for this alarm group, but should be unique
for each alarm group.
Solution: Make sure that the alarm variable declaration is correct.
Alarm variable is allocated to hardware: <type> <tag no.>

Description: The specified variable should be allocated to a
communication channel, but is now configured as a hardware-
related variable.
to change the sub-allocation.
Alarm variable is not allocated to hardware: <type> <tag no.>

Description: The specified variable should be allocated to a digital
output module, but is now configured as a communication variable.
to change the sub-allocation.
Alarm variable not used on sheet: <type> <tag no.>

Description: The specified variable exists in the variable database,
but is not used in the application program.
Solution: Use the 'Design FLDs' option of FSC Navigator to
change the program, or delete the variable (if the variable is not
required for the alarm group).
Software Manual
Analog I/O allocation error: <type> <tag no.>
Description: The specified analog variable has not been properly
allocated to the hardware (rack, channel, position is not specified).
(Hardware Specs option) to allocate the variable. If the FLD
number of the variable is 0 (zero), the variable is not used in the
FLDs and may be deleted. You can use the 'Print' option of FSC
Navigator to print all variables in the variable database that were
not properly allocated.
Application too big to fit in 2 Megabit COM EPROMs. Use flash

memory boards instead.
Description: The file created for the communication module does
not fit in 2-Megabit communication EPROMs, which is the largest
size supported.
Solution: Do not use service and qualification for markers in the
SER messages.
Solution: Use COM modules with flash memory rather than
EPROMs (10014/x/x and 10018/x/x).
Average application time (ms): <time>

Description: After the translation is complete, the average
application time is listed in milliseconds.
BI/BO with DEC/BIN conversion must have BCD data

representation: <type> <tag no.>
Description: The specified variable is converted from/to BCD data
representation in the FLD, but the variable is specified as a binary
input or output.
to change the data representation to BCD, or replace the BCD input
or output symbol in the FLD with a binary input or output signal.
Called block is no or incorrect equation block: <equation block>

Description: The referenced diagram is not an equation block
diagram.
Called block is no function block: <function block>

Description: A call is made to an FLD which is not a function
block FLD.
Solution: Delete the call in the calling FLD.
Software Manual
Cascade PID not found: <type> <tag no.>
Description: The specified PID has been defined as a cascade PID,
but was not found in the database.
Description: Use the 'System Configuration' option of FSC
Navigator (Hardware specs) to change the cascade PID tag number,
or enter a new PID with this tag number.
Code file too large to fit on RAM set(s).

Description: The generated files will be too large for the current
configuration.
to change the application program to memory modules.
Compiler out of space: no more compiler sequence numbers.

Description: There is not enough space available to store more
compiler sequence numbers (on-line modification set to 'Yes').
(Rebuild option) to create new space.
Configured process safety time (s): <time>

Description: This is the process safety time as specified in the
database (in seconds).
Connected FSC application name not configured: <appl. no.>

Description: An FSC-FSC link has been defined for the specified
system, but no valid application name has been configured.
(Install / Configuration / FSC network) to define the name of the
application with the specified application number.
Converting sheets to new 'Design FLDs...' version.

Description: Before translation, all FLDs will be converted to the
correct compiler version.
Corrupted data: <type> <tag no.>

Description: The data of the specified variable is corrupted, but the
CRC is OK.
(Signal Specs option) to delete the variable, and enter the data for
the variable again.
Software Manual
Corrupted data detected.
Description: The current installation FLD contains a corrupted
record.
(Rebuild option) to regenerate the configuration.
Corrupted data detected in variable data file at record:

<record no.>
Description: The data file contains a corrupted record.
(Rebuild option) to rebuild the data file.
Corrupted file: <file name>

Description: A (temporary) file which was created by the compiler
is corrupted.
Solution: Use a disk utility to remove any bad sectors from your
disk and restart the translation.
Description: The report or SER format file is corrupted.
Solution: Use the 'SER Format' option of FSC Navigator to correct
the corrupted file(s).
Count-up or count-down not allowed for a float register.

Description: The count-up or count-down operation is only valid
for integer-type registers (byte, word or long).
modify the FLDs.
Counter allocation error: <type> <tag no.> Byte number:

<byte no.>
Description: The counter has an address <byte no.>, which is
already used by one or more other counters.
(Rebuild option) to check the addresses of all variables.
CRC-32 of application software in Central Part <CP no.>: <CRC>

Description: This is the checksum of the application software of
the specified Central Part. It is used to validate the verification.
Software Manual
Current application not linked in: <linked appl. name>
Description: The linked application was found, but no link has
been specified in this database to the current application (no
FSC-FSC link to the current application has been specified).
(Install/Modules/Central Parts/COM) to specify a link to the
current application name in the linked application. Remove the link
to the other application. For example, the current application is
TEST_1 and has a link to TEST_2. In application TEST_2, no
FSC-FSC link has been specified to application TEST_1.
Current application version: <version no.>

Description: If the translation is complete, the version of the
software is listed.
Data error in sheet.

Description: The currently translated FLD contains a corrupted
record.
Solution: Use the 'Design FLDs' option of FSC Navigator to see if
all symbols are still present and correct.
Data representation in sheet does not match variable data file.

Description: If input or output representation is of type BCD
(configured using the 'System Configuration' option of FSC
Navigator), there must be a conversion between input/output and
the other sheet symbols.
Solution: Make sure that the required conversion is carried out.
Database version mismatch detected in file: <file name>

Description: During the network check by the compiler, an attempt
was made to read data from an application with a different version
than the current application.
Solution: Use the 'Open Project' option of FSC Navigator to
convert the application to the current version.
Digital I/O allocation error: <type> <tag no.>

Description: The specified digital variable has not been properly
allocated to the hardware (rack, channel, position has not been
specified).
not properly allocated.
Software Manual
This error message (with "O SEC.SWITCH-OFF" as the type and
tag number) will also appear if the secondary switch-off has not
been allocated while it should. Whether or not this is required
depends on the requirement class (AK), the presence of 10216/./.
modules in the system, and the output voting scheme. Table 8-2
below shows when the secondary switch-off is mandatory and what
will be reported when it is not allocated.
Table 8-2 Digital I/O allocation error and secondary switch-off

AK5/6* AK1 to AK4
10216/./. No 10216/./. 10216/./. No 10216/./.
1oo2D 2oo2D 1oo2D 2oo2D
Mandatory Optional Optional Mandatory Optional Optional
(error) (warning) (warning) (error) (no error or (no error or
warning) warning)
* If 10002/x/x or 10012/x/x CPUs are used, secondary switch-off is mandatory for all AK6
applications (regardless of the 10216/x/x configuration). An error will otherwise be reported.
DISK READ ERROR: <file name>

Description: An unsuccessful attempt was made to read data from
the specified file.
DISK WRITE ERROR: <file name>

Description: An unsuccessful attempt was made to write data to
the specified file.
Disk full.
Description: There is insufficient disk space for the translation
process to continue.
Solution: This can be solved by removing unused files from your
disk or using a disk with a larger disk capacity.
Duplicate off-sheet reference on sheet: <FLD no.>

Description: An off-sheet reference with the specified tag number
has been placed on one FLD twice.
remove one reference.
Software Manual
Duplicate on-sheet reference on sheet: <FLD no.>
Description: An on-sheet reference with the specified tag number
has been placed on one FLD twice.
remove one reference.
Duplicate sheet transfer in index file: <tag no.>

Description: The index file is corrupted.
(Rebuild option) to rebuild the index file.
Duplicate tag number on sheet: <tag no.>

Description: A variable with the specified tag number has been
placed on one FLD twice.
remove one tag number.
Error in address allocation.

Description: A CRC error has occurred, which indicates there is an
error in the address allocation.
to verify the address allocation.
Error in the COM module specifications.

Description: A CRC error has occurred.
to verify the communication module specifications.
Error in link configuration to system: <system>

Description: A CRC error has occurred.
to verify the link specification to the specified system.
Error in sheet:
Description: The currently translated FLD contains a corrupted
record.
Solution: Use the 'Design FLDs' option of FSC Navigator to check
the FLD.
Error in the application description field: <field>

error in the specified field of the description fields.
to verify the specified rack application description field.
Software Manual
Error in the configuration definition.
error in the configuration definition.
to verify the configuration definition.
Error in the module in rack: <rack> at position: <pos.>

error in the module at the specified rack and position.
to verify the specified module.
Error in password definitions.

error in the password definitions.
to verify the password definitions.
Error in the rack definition of cabinet: <cabinet no.>

error in the rack definition of the cabinet.
to verify the specified rack definition of cabinet.
Error in the SER channel definition.

error in the SER channel definition.
to verify the SER channel definition.
Execution time too large.

Description: The total calculated maximum execution time
exceeds the maximum time (498 ms).
Solution: Change the timing of multiplexers and/or PIDs. Rebuild
the database without saving the addresses of the variables. Increase
the process safety time or split the application over two FSC
systems.
Fatal error. Translation aborted: <time> <date>

Description: This message is printed if for some reason the
translation process cannot continue. Possible reasons are disk full
or insufficient memory.
Software Manual
Description: The specified file could not be created. For example,
the disk may be full or the number of open files has been exceeded.
Solution: Clean your disk, i.e. delete unused files or save currently
unused files to a removable storage medium (e.g. a diskette), and
delete them from your hard disk.
Solution: Use a system with a larger disk capacity.

Description: An attempt was made to open the specified file, but it
was not found or could not be opened. If the file was the
<application name>.FMT, a default format file will be used by the
compiler and it will be reported that the default format file is used.
FLD contains different 'Design FLDs' version: <version>

Description: The FLD was drawn using an older version of the
FLD design editor.
Solution: Convert the FLD by editing the FLD in the current FLD
design editor.
FLD contains different symbol editor version: <version>

Description: The FLD was drawn with a symbol library that is
specified with an old symbol library editor.
Solution: Convert the FLD by editing the FLD in the current FLD
design editor.
FLD contains too many <symbol type>

Description: Too many symbols of the specified type have been
placed on an FLD.
Solution: Use the 'Design FLDs' of FSC Navigator to remove some
symbols.

Description: The specified FLD contains corrupted data.
Solution: Use the 'Design FLDs' option of FSC Navigator to load
the FLD, and then delete it.
FLD reference not found on FLD: <tag no.>

Description: The sheet reference with <tag no.> is found on one
FLD but not on a referenced FLD.
replace the reference.
Software Manual
FLD too big or nesting to deep. FLD time: <time>
Description: The execution time of the FLD is too large because
function blocks have been nested to deep or there are too many
time-consuming functions.
Solution: Use the 'Design FLDs' option of FSC Navigator and
change the FLDs so that fewer functions or other functions are
needed. Change the nesting of the function blocks, since too many
function block calls can cause the execution time to become too
large. Split the FLD into two or more FLDs. Particularly
time-consuming functions are square root and PID.
FLD transfer expected to be directly connected to I/O symbol.

<type> <tag no.>
Description: You defined a service text that is identical to the tag
number of an I/O symbol, but no direct connection exists.
change the service test or make a direct connection.
FSC system out of memory for this type of variable: <type>

<tag no.>
Description: The compiler cannot place a compiler register or
compiler marker in the variable database.
Solution: It is possible that new space will be created after the
translation is complete. Therefore, recompile the whole set. Erase
any unused variables (FLD number is 0). Change your design so as
to decrease the number of required markers and/or registers.
Function block input not connected. Function block input

sequence number: <seq. no.>
Description: An input of a function block has not been connected
to a signal in the FLD. This is allowed but a warning is
nevertheless given, because it might be not intended. The input
value will be zero during execution.
Function block sheet in program block area: <no.>

Description: The FLD number of a program block must be at least
two less than the FLD number of the first function block.
Solution: Use the 'Design FLDs' option of FSC Navigator
(renumber option) to shift down the program block or to shift up
the function block. Check all calls to this function block.
Software Manual
Function block sheet missing: <FLD no.>
Description: The function block which is called at the specified
FLD is not available in the project folder (file is not found).
Solution: Delete the function block on the calling FLD or restore
the function block sheet.
Function block sheet must contain at least one function block

output.
Description: A function block must have a function block output,
otherwise it is of no use in the functional logic diagrams.
Solution: Place a function block output or delete the FLD.
Description: Function block symbol corrupted.

Description: A function block symbol has been found to be
corrupted.
Solution: Use the 'Design FLDs' option of FSC Navigator to delete
and replace the corrupted function block.
Function change failed.

Description: The FLD contains too many variables of the specified
type (markers, counters, timers or registers).
Solution: Use the 'Design FLDs' option of FSC Navigator to edit
the FLD (e.g. split into more FLDs).
Identical source and destination sheet are not allowed.

Description: The source FLD and destination FLD for a sheet
transfer is identical, which is not allowed.
Solution: Make sure that the source and the destination FLD in a
sheet transfer are different.
Illegal address: <type> <tag no.>

Description: The specified variable in the database has an illegal
address.
(Rebuild option) to check the new addresses of all variables.
Illegal bit number: <bit no.>

Description: The bit number is corrupted.
Solution: Translate again.
Software Manual
Illegal connection: Node (x, y)
Description: A signal line has been connected to a symbol at a
point where it is not allowed, or the signal line is not a valid signal
type. Function blocks and registers have predefined input and
output positions.
Solution: Run the 'Design FLDs' option of FSC Navigator to
change the connection.
Illegal constant: <type> <tag no.>

Description: The value of the constant is not allowed (e.g. a
negative constant is loaded to a counter).
change the constant.
Illegal counter value: Node (x, y)

Description: The value which will be loaded into the counter is
illegal.
change the constant value or change the range of the counter.
Illegal function block call: <function block>

Description: The function block called has a higher or an equal
FLD number than the current FLD.
Solution: Remove the function block from the current FLD.
Renumber the function block to an FLD with a number higher than
the current FLD number. Place the function block again on the
current FLD.
Illegal function block input exchange.

Description: Two function block inputs have been exchanged
illegally.
Solution: Use the 'Design FLDs' option of FSC Navigator to place
the symbols as before.
Note:
Only active if on-line modification is set to Yes.
Software Manual
Illegal function block output exchange.
Description: Two function block outputs have been exchanged
illegally.
Solution: Use the 'Design FLDs' option of FSC Navigator to place
the symbols as before.
Note:
Only active if on-line modification is set to 'Yes'.
Illegal input signal type of function block: <function block>

Node (x, y)
Description: The signal type of the register on the FLD cannot be
converted to the signal type of the function block input. The calling
FLD long register cannot be connected to a word register.
Illegal modules used for multiplexer I/O.

Description: The multiplexer configuration contains I/O modules
which are not valid.
to change the allocation of the multiplexers.
Illegal name of application stored in database: <appl. name>

Description: The name of the current application has not been
specified for the current system number. For example, the current
application is TEST_1. The application name for system 1 in the
current database is, for example, DEMO. This will happen if an
application has been renamed "outside" FSC Navigator (e.g. using
Windows Explorer).
Solution: Use Windows Explorer to restore the original name of
the application.
Illegal printer reference: <file name>

Description: The printer specified in a report file or in the SER
format file is not known in the specified file.
Solution: Use the 'SER Format' option of FSC Navigator to install
another printer. The specified file might be an old version of the
file DEVICE.DRV.
Software Manual
Illegal protocol specified: <CP module> <COM no.> <chan.>
Description: The protocol specified in the database is not valid.
(Install option) to select a valid protocol.
Description: The channel has been specified as the SER channel,
but has an invalid protocol.
to specify the primary or secondary link, or define the channel as a
primary link.
Illegal record number: <no.> (<file name>)

Description: The compiler attempted to read a record which does
not exist.
to rebuild the index files.
Illegal record type: <type> <tag no.>

Description: The variable has been defined in a report, but cannot
be used as a condition to generate a report.
Solution: Use the 'SER Format' of FSC Navigator to remove the
variable from the condition of a report.
Illegal sec. link specified for COM chan. (CP, Mod): <CP no.>
<module> <chan.>
Description: The protocol of the secondary channel does not
match the protocol of the primary link.
to change the protocol or change the secondary link.
Illegal secondary SER channel specification.

Description: The secondary SER channel has been allocated to an
invalid channel.
to change the secondary SER channel specification.
Illegal SER printer specification (CP no., COM module, chan):

<CP no.> <module> <chan.>
Description: The SER channel has been configured in this system,
but the Central Part, COM module and channel have not been fully
specified.
to specify the SER channel.
Software Manual
Illegal SER printer specification (system number): <system no.>
Description: The SER printer has been configured to another
system, but no link with this system is available.
(Install/Configuration option) to specify the SER channel.
Illegal signal type(s): Node (x, y)

Description: The signal type is illegal for the symbol to which it is
connected. For example, a signal of type Long cannot be connected
to a counter or timer.
Description: The types of the signal coming from the FLD to an
internal off-sheet symbol (i.e. decimal marker) do not match and
conversion is not allowed for internal symbols.
change the signal type.
Illegal symbol for this block type: <block type>

Description: The FLD contains a symbol which should not be
present in an FLD with the specified block type.
the symbol.
Illegal timer base

Description: Base must be 100 ms, 1 second or 1 minute.
Solution: Use the 'Design FLDs' option of FSC Navigator (Change
option) to change the symbol.
Illegal value: <type> <tag no.>

Description: The value of the variable (timer or counter) is less
than or equal to zero, or greater than the maximum value (counter
maximum = 8191; timer maximum = 2047).
change the variable.
Illegal value specified in report condition.

Description: The value of the variable is not within the valid
range.
Solution: Use the 'SER Format' option of FSC Navigator to edit the
value of the report condition.
Software Manual
Illegal variable type specified for <type> <tag no.>
Description: The database contains a variable ('I' or 'O' with
location 'ANN') which is connected to this alarm with an illegal
alarm type.
to disconnect the illegal variable.
Impossible scan time: <type> <tag no.>

Description: A scan time was defined for the specified variable
which is not valid.
(Hardware Specs option) to change the scan time.
Inaccurate scaling specified for analog input:

Description: The difference between the bottom and top scale
value is too small.
to change the scaling values of the specified variable.
Incompatible version of file: <file name>

Description: The specified file is not compatible with the current
FSC Navigator version.
Solution: Use the 'SER Format' option of FSC Navigator to
convert the files or remove the file.
Index files are corrupted.

Description: The index files have been found to be corrupted.
(Rebuild option) to create new index files. If a timer or register
symbol was found on an FLD which is not found in the I/O data
file, the FLD design editor will first try to place this symbol in the
I/O data file. If this fails, the symbol is deleted from the FLD.
Index files will be rebuilt as soon as another FSC program is

started.
Description: A CRC error has occurred and the index files have
been removed from disk.
Solution: As soon as another main option of FSC Navigator is
started, the index files will automatically be rebuilt.
Infinite signal cycle: Node (x, y)

Description: A signal line has been connected to itself (perhaps via
several other FLDs), creating a loop.
the loop.
Software Manual
Input/output/PID already placed on sheet:
Description: An input, output or PID has been placed on different
FLDs twice.
remove the symbol on one of the FLDs.
Invalid data exchange with com. server system: <CP no.>

<Com no.> <chan.>
Description: The specified channel contains a number of markers
and/or registers to read and/or write to a communication server
channel.
to delete the number of bytes to read or write.
to change the communication server to a master channel.
Invalid fault reaction: <type> <tag no.>

Description: An invalid fault reaction setting has been encountered
for the specified variable type with the specified tag number.
to change the fault reaction for the specified variable.
Invalid I/O for diagnostic status.

Description: An invalid I/O has been detected for the diagnostic
status (e.g. allocation to a non fail-safe module).
Solution: Diagnostic input must be allocated to a fail-safe module.
Invalid library version. You need version <version>

Description: The library has a different version than the compiler,
but cannot be converted.
Solution: Use FSC user software of the specified version.
Invalid master channel configured (CP,COM,Ch): <CP no.>,

<COM module>, <channel>
Description: The channel specified has been configured as a
redundant master channel.
to change the master channel to a redundant slave channel or to a
single master channel.
Software Manual
Invalid math symbol found on FLD: node<x,y>
Description: The channel specified has been configured as a
redundant master channel.
to change the master channel to a redundant slave channel or to a
single master channel.
Invalid network configuration detected in appl:

Description: The configured network contains errors:
− The master of the current slave channel was not found.
− The current application has not been specified in the connected
slave systems.
− Invalid data was detected.
to correct the network configuration.
Invalid numeric order in equation table.

Description: The input value defined in the equation table is not in
ascending numerical order.
Solution: Make sure the input value is in ascending numerical
order.
Description: Invalid PID sample time configured. The sample time
of the PID is too small.
to change the PID sample time to a larger value (it should higher
than the application time).
Invalid redundancy type configured: <type> <tag no.>

Description: The specified input variable contains non fail-safe
sensors, but the redundancy type of the sensor has not been
specified (yet).
to change the sensor to fail-safe, or to specify the sensor
redundancy type.
Invalid redundant link definition (CP,COM,Ch): <CP no.>, <COM

module>, <channel>
Description: The specified channel has been configured as a
redundant link, but the configuration of both channels does not
match.
to change the redundant link to single, or redefine the redundant
link after a rebuild.
Software Manual
Invalid requirement class configured: <requirement class>
Description: The requirement class of the application is not valid.
to specify a valid requirement class.
Invalid safety relation configured at (rack, position): <rack>,

<position>
Description: The module at the specified location has a
'Safety-related' attribute that is set to 'Yes' and a 'Tested' attribute
that is set to 'No', which is an invalid combination.
to reset the 'Safety-related' attribute and 'Tested' attribute of the
specified module.
Invalid SER sequence number area specified.

Description: The SER sequence number area is too small or is not
in the valid range of SER sequence numbers.
(Install/Configuration/SER channel) to change the SER sequence
base and/or SER sequence maximum.
Invalid SER sequence number specified: <type> <tag no.>

Description: The SER sequence number specified for the specified
variable is out of the specified SER number range or is already in
use.
(Rebuild option) to change the SER sequence number.
Invalid sheet reference: <tag no.>

Description: The sheet reference with the specified tag number is
not correct (not found in the variable data file or found twice on
FLDs).
remove the reference.
Invalid software version. You need version <version>

Description: The database is of a different version than the
compiler, but cannot be converted.
Solution: Use FSC user software of the specified version.
Software Manual
Invalid system link configured at (CP,COM,Ch): <CP no.>,
Description: The specified channel contains systems that cannot be
used for FSC-FSC communication.
to remove the invalid systems, or specify the path for the invalid
systems in the complete network.
Invalid/unknown I/O module configured

Description: The I/O module configured is not supported by the
system.
to remove the invalid I/O module.
Invalid value in equation table.

Description: A value defined in the equation table is out of range.
Solution: Make sure the value is in the legal range (1E-38 to
1E+38).
I/O buffer full: <i,o,I,O>

Description: The buffer used for digital or analog I/O is full
(i = Analog input, o = analog output, I = digital input, O = digital
output).
to delete some I/O modules of the specified type.
I/O module address(es) have been changed.

Description: This warning will occur if the compiler detects
invalid addresses of I/O modules in the database. I/O variables
which are allocated to these modules will have other addresses.
Isolated symbol: Node (x,y)

Description: A symbol has been found without any direct or
indirect output connection to an off-sheet symbol.
connect the symbol or delete it.
Software Manual
Larger size of application EPROMs required: <EPROM size>
Description: A specific type of EPROM/RAM has been
configured for the application module (CPU only), but the
application does not fit in the configured type. The compiler shows
which type should be configured to make the application fit.
(Install/Configuration/Memory chip size) to select the suggested
EPROM type (or a larger type), or specify variable sizing. The
generated files can be used, but should be programmed with a
larger type of EPROM.
Larger size of communication EPROMs required: <EPROM size>

Description: A specific type of EPROM has been configured for
the communication module, but the application does not fit in the
configured type. The compiler shows which type should be
configured to make the communication file fit.
(Install\Configuration\Memory chip size) to select the suggested
EPROM type (or a larger type), or specify variable sizing. The
generated files can be used, but should be programmed with a
larger EPROM type.
Library corrupted: <library name>

Description: The specified library file is corrupted.
Solution: Reinstall FSC Navigator from the CD-ROM.
Library not found on disk: <library name>.SYM

Description: The library used to create the functional logic
diagrams cannot be found in the FSC Navigator application folder
(C:\FSC by default).
Solution: Make sure that the required library file is in the FSC
Navigator application folder, or use the Project/Properties menu
item of FSC Navigator to select another library and translate again.
Make sure that the library is compatible with the drawings.
Link area of connected appl. does not match: <linked appl. name>
Description: The number of bytes to read and/or write markers
and/or registers of the current application does not match the
number of bytes to read and/or write in the linked application.
to specify (or copy) the number of bytes used for external FSC-
FSC protocols.
Software Manual
Link specification contains errors.
Description: The compiler has detected an error for the link
specification of the COM channel specification.
to correct the error (Rebuild option).
Link appl. name of connected appl. not OK: <linked appl. name>
Description: The linked application is found, but in the database
the application name assigned to the current application number is
not the current application name.
(Install/Configuration) to specify the current application name in
the linked application. For example, the current application is
TEST_1 and has a link to TEST_2. In application TEST_2, the
application name for system number 1 is not TEST, but (for
example) TEST1.
Load and value must both be connected or not connected:

<type> <tag no.>
Description: If you have a load function, you need a value to be
loaded into the register. If you do not have a load function, no
value is needed.
Solution: Make sure a value is loaded into the register.
Logic sequence too complex: Node (x,y)

Description: The compiler has memory problems when translating
the sequence to the specified node point.
Solution: Use the 'Design FLDs' option of FSC Navigator to split
the functional logic diagrams into simpler or shorter sequences.
Marker allocation error: <type> <tag no.> Bit number: <bit no.>
Description: The variable in the marker area has the specified
address, which is already used by one or more other variables in the
marker area.
Software Manual
Maximum delay time on communication link (CP no., COM,
Chan.): <value> ms
Description: This message is given for each multidrop
communication channel in a communication server FSC
application. It shows the maximum response time (in ms) of that
channel. This information helps the user decide how to balance
overloaded communication channels.
Maximum number of report entries exceeded.

Description: The number of conditions used for report generation
is too large. The maximum number is 16,368.
Solution: Use the 'SER Format' option of FSC Navigator to reduce
the number of conditions or the number of reports.
Mismatch between data from FLD database and configuration

database: <tag no.>
Description: The information for the specified tag number
(typically used by a function block) contained in the FLD database
does not match the corresponding information in the FSC
configuration database.
remove the function block that uses the specified tag number from
the affected FLD and place it again.
Missing alarm variable(s) for <type> <tag no.> <alarm type>

Description: The alarm type mentioned is not specified with the
alarm group.
to append variables to this alarm group with the missing alarm
type.
Missing sheet: <appl. name>.<FLD no.>

Description: The file that contains the FLD cannot be found on
disk.
Solution: Copy the FLD file to the project folder. If the FLD is
really lost, run the 'Design FLDs' option of FSC Navigator. Enter
the FLD number of the lost FLD and answer 'Y' when asked
whether you want to erase the FLD from the database.
Missing signal or unconnected signal line: Node (x, y)

Description: A signal line which should be connected has not been
connected at node point (x, y).
connect or delete the line.
Software Manual
Missing slave system detected at (CP, COM, Ch): <CP no.>
<Com no.> <chan.>
Description: Not all systems connected have been configured at
the specified channel.
to add the system to the specified external application.
Missing variable data file : <filename>

Description: The variable data file is not found.
to create a new data file.
Module for which execution times are valid : <module type>

Description: The module type as specified using the 'System
Configuration' option of FSC Navigator.
More than one signal at a node: Node (x, y)

Description: Two independent signals may not be connected.
disconnect them.
Multiple I/O allocation error: <type> <tag no.>

Description: This means that a variable has not been properly
allocated to the hardware for all necessary I/O bits (rack, channel,
position has not been specified).
improperly allocated.
Multiplexer contains no variable: <type> <tag no.>

Description: The data bus of the multiplexer contains no variables.
In case of an XI, no BIs with the number of multiplexer XI exist.
In case of an XO, no BOs with mux number of the XO exist.
to delete the XI or XO, or append variables to this XI or XO.
Multiplexer RAM out of space.

Description: Too much RAM is required for all multiplexed I/O
(variables with location 'MUX') that have been configured.
Solution: Try to minimize the size of variables (bytes instead of
words or longs, words instead of longs), or change the location of
some variables.
Software Manual
Multiplexer tag number not defined: <type> <tag no.>
Description: The multiplexer tag number of the variable should be
specified to connect this variable to a XI or XO.
(Hardware Specs option) to specify the multiplexer tag number.
Network overload detected for (CP no., COM module, channel.):

<CP no.> <COM no.> <channel>
Description: This error message will typically appear if the
timeout configured for FSC-FSC configuration is too short for the
amount of data transferred within the network.
(Install/Configuration/FSC-FSC communication configuration) to
increase the FSC-FSC communication timeout.
No application connected for COM chan. (CP no., COM module,

chan.): <CP no.> <COM no.> <channel>
Description: The specified channel from the communication
module in the specified Central Part with the specified sequence
number has been defined as an external FSC-FSC protocol, but no
other application has been specified.
(Install/Central Part/COM) to specify the communication link.
No communication channel found to load application into RAM.

Description: The application is translated for test mode, but no
FSC user station (or printer) is available.
Solution: User the 'System Configuration' option of FSC Navigator
to set the memory type to 'EPROM', or specify a Development
System channel.
No conditions specified in report file.

Description: A report has been specified, but the report is never
printed.
Solution: Use the 'SER Format' option of FSC Navigator to edit the
conditions or frequency to generate the report, or to delete the
report.
Software Manual
No DBM module present, so real-time functions not available:
<type> <tag no.>
Description: The application program uses the specified system
variable, which can be used only if a DBM module has been
configured.
to specify a DBM module, or remove the real-time variables
(YEAR, DATE, DAY, MONTH, HOURS, MINUTES or
SECONDS) from the functional logic diagrams.
No hardware specified.
Description: The database has not been configured; no hardware
has been specified.
(Install option) to specify the hardware of the application.
No linked variable specified for: <type> <tag no.>

Description: The specified variable has been allocated to a
TFS_COM1 alarm group, and should be linked to another variable.
to specify a linked variable, allocate the variable to another alarm
group (with a different alarm group sequence), or change the alarm
type of the variable.
No load signal, so a count signal and clear signal must be

connected: <type> <tag no.>
Description: If you do not load a register, you must at least use a
count-up or a count-down in combination with a clear, otherwise
the register is of no use.
Solution: Make sure all conditions are met to use the register.
No master system detected for (CP,COM,Ch): <CP no.>,

Description: The slave channel specified does not communicate
with an external (master) system.
to add a master application to the specified channel.
No primary link specified for COM chan. (CP no., COM module,
chan.) : <CP no.> <COM> <chan.>
Description: The specified COM channel is a secondary channel,
but the primary link has not been fully specified.
to specify the primary link, or define the channel as a primary link.
Software Manual
No protocols specified for COM module (Central Part, COM
module): <CP no.> <seq.>
Description: The protocol of channel A and channel B from the
communication module in the specified Central Part with the
specified sequence number have not been set (Protocol =
undefined).
(Install/Central Part/COM option) to specify a protocol, or remove
this communication module.
Not enough disk space found. Required disk space: <MB>

Description: The compiler requires <MB> megabytes of hard disk
space.
Solution: Free disk space by deleting files that are no longer
needed.
Not enough memory to execute required translation function(s).

Description: The compiler needs more memory to execute the
translation process.
Solution: Free memory by closing any other applications that are
running.
Not enough register memory on COM modules: <no. of bytes>

Description: The number of bytes used on communication
modules exceeds its maximum limit.
Solution: Minimize the number of register bytes used for each
Not enough watchdog repeaters placed.

Description: The number of watchdog repeaters in the system is
too small. The number of watchdog repeaters should be at least the
number of PSUs (10300/1/1).
to add one or more watchdog repeaters (10302/1/1).
Not enough watchdog repeaters placed in single I/O part.

Description: At least one watchdog repeater should be placed in
the single I/O part of the system.
to add a watchdog repeater (10302/1/1).
Software Manual
Number of alarm groups without alarm type <alarm type>
connected: <number>
Description: The application database contains a number of alarm
groups with no alarm types of the specified type used.
Solution: Make sure the specified alarm types are present in the
application database.
Number of data memory bytes: <number>

Description: Total number of register bytes in the application
program.
Number of errors detected during safety calculation:

Description: Not implemented yet.
Number of I/O allocation errors: <number>

Description: Number of unallocated I/O, or I/O whose allocation is
not complete.
Number of markers: <number>

Description: Total number of markers used in the application
program.
Number of system allocation errors: <number>

Description: Number of registers, markers, counters or timers that
have been allocated more than once.
Number of warnings generated during safety calculation:

<number>
Description: Not implemented yet.
Numerical SER and ASCII SER specified on single channel:

Description: An SER channel in the FSC network is used as a
numerical SER channel, but it is also used as an ASCII SER
channel.
to change all SER channels to numerical SER or ASCII SER, or
select different channels for ASCII SER and numerical SER.
Numerical SER range overlap detected.

Description: The numerical SER ranges in the applications of the
network overlap.
to modify the numerical SER ranges in the various applications.
Software Manual
One or more sheets missing. First sheet: <number>
Description: Not all FLD files were found in the project folder,
although they are specified in the databases.
the FLDs from the database. The displayed FLD number is the first
FLD that is found missing and will be the FLD with the highest
number.
Original system contains too many <variable type>

Description: The application is translated in simulation mode, but
the original application contains more variables of the specified
type. You can use the generated files, but not all.
(Rebuild option) to change all addresses.
Output low clamp and output high clamp are identical:

<type> <tag no.>
Description: The output clamps of the PID are identical, which is
not allowed.
(Hardware Specs option) to specify the output clamp.
PID cascade in logics differs from cascade configuration:

P<tag no.> P<Cascade PID> P<tag no. of connected PID>
Description: There is a mismatch between the specified PID
cascade in the FLDs and the cascade configuration.
Solution: Make sure you also made a cascade connection at this
PID in the functional logic diagrams.
Cascade: – You did not configure a PID cascade tag number
using the 'System Configuration' option of FSC
Navigator but you connected the cascade setpoint
signal nevertheless.
– You configured a PID tag number using the 'System
Configuration' option of FSC Navigator but you did
not connect the cascade input signal, or you
connected it to the wrong PID or to another symbol.
PID register not found: <type> <tag no.>

Description: The specified register which should exist in the
database was not found.
to rebuild the index files, or delete the PID and insert it to create
the register again.
Software Manual
PID timer not found: <type> <tag no.>
Description: The specified timer which should exist in the
database was not found.
to rebuild the index files, or delete the PID and insert it to create
the timer again.
Power-on value out of range. <type> <tag no.>

Description: The power-on value of the variable is invalid. The
number of bits is too small to represent the power-on value.
to change the power-on value.
Press <Enter> to return to FSC main screen.

Description: The compiler waits until <Enter> is pressed, because
the compiler has generated errors or warnings.
Previous error may be caused by multiplexer scan time being too

high.
Description: This warning is generated when the compiler detects
errors.
Program aborted. Application configuration not defined.

Description: Before using the compiler, the FSC application
configuration should be known.
(Install option) to define the FSC application.
Program communication EPROMs.

Description: The application has been translated, but the COM
EPROMs should be programmed for the application to function
correctly.
Program interrupted manually.

Description: The translation process was interrupted because the
<Esc> key was pressed.
Protocol mismatch detected: <chan.>

Description: The specified channel contains a protocol definition
that does not match the protocol of connected systems.
to change the protocol of the specified channel.
Software Manual
Reference to non-existing FLD: <FLD no.>
Description: The specified FLD is undefined or cannot be found
on disk.
the reference.
Register allocation error: <type> <tag no.> Byte number:

<byte no.>
Description: The variable in the register area has the specified
address, which is already (partially) used by one or more other
variables in the register area.
to check the addresses of all variables.
Register type mismatch with current appl.: <type> <tag no.>

Description: The register type in the current application is
different from the register type in the connected external
application.
to copy the allocated variables or to change the register type of the
specified variable.
Report files configured, but no valid report communication

channel available.
Description: No communication channel has been configured
which may be used for report printing.
to specify a communication channel for report printing, or delete
the report file.
Reset signal must be connected: <type> <tag no.>

Description: A memorize timer must always have a reset signal
because you cannot get it low after you started it.
Solution: Make sure the memorize timer has a reset signal.
SER format file configured, but no valid communication channel

available.
Description: No communication channel has been configured
which may be used for SER printing.
to specify a communication channel for SER printing, or delete the
SER format file.
Software Manual
SER/report communication port must be set at 8 bits:
Description: The communication channel which is used for SER
and/or reports is configured at 7 bits/char, but the report and/or
SER file contain 8-bit characters.
to select 8 bits/char, or use the 'SER Format' option of FSC
Navigator to remove the 8-bit characters.
Serial number:
Description: The serial number of the FSC Navigator software.
Set and value signals must both be connected or not connected:

<type> <tag no.>
Description: If you have a set function, you need a value to be
loaded into the counter. If you do not have a set function, no value
is needed.
Solution: Make sure a value is loaded into the counter.
Set, count-up or count-down signal must be connected: <type>

<tag no.>
Description: You must connect one of these functions to the
counter for it to be of any use.
Solution: Make sure one of the specified functions is connected to
the counter. See the symbol description in Section 6 of this manual
Set signal must be connected.

Description: The set signal of a timer has not been connected.
Solution: Use the 'Design FLDs' option of FSC Navigator to create
a connection.
Setpoint low clamp and setpoint high clamp are identical:

<type> <tag no.>
Description: The setpoints of the PID are identical, which is not
allowed.
(Hardware Specs option) to specify the setpoint clamp.
Software Manual
Signal conversion not allowed (type mismatch): Node (x, y)
Description: The result of the calculation is not a float, but one of
the signals at the input side of the calculation symbol has a type
float. This means that a conversion from float to long would be
necessary. However, this conversion means a loss of information,
which is not allowed.
Solution: Use the 'Design FLDs' option of FSC Navigator and
change signal type(s).
Signal type does not match number of bits: <type> <tag no.>
Description: The signal type does not have the number of bits that
it should have.
(Hardware Specs option) and change signal type of the variable.
Signal type undefined. Signal cannot be saved or loaded:

<type> <tag no.>
Description: The signal type of the variable is undefined.
to specify the type of the variable.
Specified communication area(s) and/or alarm area(s) show

overlap.
Description: The compiler has detected an error in the database for
the reserved areas of alarm groups or communication channels.
(Rebuild option).
Single fault in single I/O part may cause system shutdown.

Description: The system contains a single I/O part. If a severe
error is detected, the possibility of a system trip exists.
Specified communication area(s) and/or alarm area(s) have illegal

range.
Description: The compiler has detected an error in the database for
the reserved area specification of alarm groups or COM channels.
(Rebuild option).
Specified SER format ignored, default format assumed.

Description: The configured SER format file is not allowed.
to specify a proper SER channel, or use the 'SER Format' option of
FSC Navigator to specify a proper printer configuration.
Software Manual
System contains too many <symbol type>
Description: Too many symbols of the specified type have been
used in the application.
remove some symbols.
Timeout inconsistency detected.

Description: This warning may be generated in case of FSC-FSC
communication on low baud rates. In order to guarantee correct
handling, the configured FSC-FSC communication timeout should
be identical for all applications in a network. Any mismatches are
reported as a warning, with the affected system(s) specified.
Solution: Make sure that the FSC-FSC communication timeout for
all connected systems in a network is identical.
Timer allocation error <type> <tag no.> Byte number: <byte no.>
Description: The timer has the specified address, which is already
used by one or more other timers.
Too many appl. connected for COM channel (Central Part, COM
module, Chan): <CP no.> <seq.> <chan.>
Description: The specified channel from the communication
module in the specified Central Part with the specified sequence
number has been specified as an external point-to-point FSC-FSC
protocol, but too many external applications have been specified.
to specify only one communication link, or change the point-to-
point link to a multidrop link (Install \ Central Part \ COM).
Too many linked variables specified for: <type> <tag no.>

Description: The specified variable has been allocated to a
TFS_COM1 alarm group and should have only one link variable.
to rebuild the database.
Too many links configured between two systems: <system no.>

Description: More than one physical path exists between the
current and the specified external application.
to remove links to the specified external application.
Software Manual
Too many masters specified for (CP,COM,Ch): <CP no.>,
Description: The specified communication channel has been
linked to several applications, but too many masters have been
specified.
to remove master applications from the specified channel.
Too many registers specified for on-line modification.

Description: The application is translated using on-line
modification, but the database contains too many register bytes.
to change on-line modification to 'No', or rebuild with address
reallocation.
Too many signal lines connected to one symbol: Node (x, y)

Description: The number of signal lines to one symbol is limited
by the compiler.
Solution: Change the functional logic diagrams by splitting the
symbol into two symbols.
Too much information to fit on EPROM set(s).

Description: The generated files will be too large for the current
configuration.
Top and bottom values are identical: <type> <tag no.>

Description: The range of the specified variable has not been
defined.
(Hardware Specs option) to specify the top and bottom value of the
variable.
Total number of warnings generated during translation:

<number>
Description: This is the total number of warnings that were
generated during translation.
Total number of errors detected during translation: <number>

Description: This is the total number of errors that were found
during translation.
Software Manual
'Translate application' program out of space.
Description: The number of mnemonics or the number of found
symbols in the FLD cannot be stored internally.
Solution: Try to optimize the FLD with regard to the number of
symbols needed for particular functions.
Try to change the partition of your total functional logics design in
such a way that fewer functions are needed per FLD.
Translating for simulation mode <simulation unit>

Description: This message is used to show that the application is
translated as a simulated application for the specified simulation
unit, which allows debugging of the application program. For
details on simulation units and the hardware contained in them
refer to Appendix H of this manual ("Simulation Mode").
Translation completed.
Description: The compiler has checked all FLDs and all data in the
databases without encountering serious errors.
Translation log file: <appl. name> <date> <time>

Description: Heading of log file.
Unable to create all dummy sheets. Number of unplaced dummy

sheets: <no. of FLDs>.
Description: In order to extend the total execution time to a certain
minimum, some delay sheets must be appended to the application
program. However, no space could be found between the program
blocks and the function blocks.
Solution: Move the function blocks to higher FLD numbers.
Renumber the first function block to create more unused sheet
numbers lower than the lowest function block number.
Undefined FLD reference: <type> <tag no.>

Description: A reference was found to FLD 0 or from FLD 0,
which has not been defined.
Solution: Use the 'Design FLDs' option of FSC Navigator to define
the sheet reference.
Unexpected I/O module at (rack, position, channel): (<rack>,

<pos.>, <chan.>) <type> <tag no.>
Description: The specified variable has been allocated to an
invalid module type (e.g. a digital input variable has been allocated
to an analog output module).
to reallocate the variable.
Software Manual
Unknown printer reference.
Description: The printer specified in a report file or in the SER
format file is not known by the compiler.
Solution: Use the 'SER Format' option of FSC Navigator to install
another printer.
Unnecessary signal conversion. Node (x,y)

Description: A signal conversion is performed but the source
signal is identical to the destination signal.
remove this signal conversion.
Value (or base) in sheet and variable data file are not equal:
<type> <tag no.>
Description: The value of the variable (timer or counter) has been
changed in the database but not in the FLD.
change the variable.
Value signal must be connected.

Description: A binary input for this type of timers must be
connected.
a connection.
Value signal must not be connected.

Description: A binary input for this type of timers may not be
connected.
remove the binary input.
Variable address is not assigned: <type> <tag no.>

Description: The database contains a variable that has not been
assigned to a communication channel and has an illegal address.
(Hardware Specs option) to assign the variables with location
'COM' or location 'FSC' to a communication channel.
Software Manual
Variable address mismatch with current appl.: <type> <tag no.>
(<linked appl. name>)
Description: The relative address of the variable specified does not
match the relative address in the current application. This will
occur if, for example, a digital input has a particular relative
address in the current application, but the corresponding digital
output does not have the same relative address in the application
specified.
(Hardware Specs option) to change the address, or use
Configuration\Module\Central Part\COM\Copy allocation to make
all addresses used in FSC networks identical.
Variable address not within communication area: <type> <tag

no.>
Description: The variable type tag number has an address which is
not within the range of the COM channel to which it has been
allocated.
(Hardware Specs or Rebuild option) to recover.
Variable data file too large. Try 'Rebuild' option to optimize file.
Description: The data file cannot be extended anymore.
(Hardware Specs or Rebuild option) to create some space.
Variable not found in variable data file: <type> <tag no.>

Description: The variable found in the FLD is not found in the
data file. The compiler will try to regenerate the variable. The
result of that action is logged.
(Symbol \ Change) to enter the required data. The variable will then
be placed in the database. If the variable is a repeated input, you
must first place the actual input. It is possible that the data was
deleted when using the 'System Configuration' option of FSC
Navigator. Use this option to (re-)enter the missing variable.
Variable is not SER enabled: <type> <tag no.>

Description: The specified variable is used for a report, but is not
SER-enabled.
to make the variable SER-enabled, or use the 'SER Format' option
of FSC Navigator to remove the variable from the condition of a
report.
Software Manual
Variable is SER enabled, but no DBM available: <type> <tag no.>
Description: The specified variable is SER-enabled, but this
requires a diagnostic and battery module (DBM), which has not
been defined in the system.
to define a DBM in the system, or reset the SER-enable status of
the specified variable.
Variable is SER enabled, but no valid SER communication

channel found: <type> <tag no.>
Description: The specified variable is SER-enabled, but this
requires a valid SER communication channel, which has not been
defined.
to specify the SER channel (Install\Configuration).
Variable not linked to current application: <type> <tag no.>

(<linked appl. name>)
Description: The specified variable in the other application
database does not exist, but is linked to another FSC system. For
example, TEST_1 in the current application is a digital input called
Link1, which is linked to TEST_2. There is a digital output Link1
in application TEST_2, but this variable is linked to system 3.
Solution: Correct the reference.
Wrong number of input signals: Node (x, y)

Description: The number of signals at the input side of the symbol
does not match the expected number of signals.
change the number. See the symbol description in Section 6 of this
manual ("Functional Logic Diagrams").
Wrong number of output signals: Node (x,y)

Description: The number of signals at the output side of the
symbol does not match the expected number of signals.
manual ("Functional Logic Diagrams").
Software Manual
Software Manual
Fail Safe Control
Section 9:
Log Files
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 9: Log Files
9.1 Introduction .................................................................................................... 9-1
9.2 Selecting a Log File........................................................................................ 9-3
9.3 Log File Viewer ............................................................................................... 9-4

9.3.1 Viewing a Log File ............................................................................................................ 9-4
9.3.2 Font Type and Size .......................................................................................................... 9-5
9.3.3 Printing a Log File ............................................................................................................ 9-7
9.3.4 Saving a Log File to Disk ................................................................................................. 9-8
Software Manual
Section 9: Log Files i
FIGURES
Figure 9-1 Button bar, with 'View Log' submenu .......................................................................... 9-3
Figure 9-2 Log file viewer with translation log file......................................................................... 9-4
Figure 9-3 Changing the font type and style................................................................................. 9-5
Figure 9-4 Font size spin button ................................................................................................... 9-6
Figure 9-5 Printing log files ........................................................................................................... 9-7
Figure 9-6 Saving a log file to disk ............................................................................................... 9-8
TABLES
Table 9-1 Log files ....................................................................................................................... 9-1
Software Manual
ii Section 9: Log Files
Section 9 – Log Files
9.1 Introduction
Log files FSC Navigator creates several log file to report the results of specific
functions. Table 9-1 below lists the log files that exist.
Table 9-1 Log files

Log file Description
Translation log file (∗.LOG): This file contains all messages, errors
and/or warnings that were generated
during translation of the application.
Safety Checker log file (∗.SAF): This file contains all messages, errors
by the Safety Checker feature of FSC
Navigator.
Verification log file (∗.VRF): This file contains all messages, errors
during verification of the application.
Append log file (∗.APP): This file contains all changes and/or
errors that were generated when two
or more projects are appended to the
currently open project. The append log
file is generated for the currently open
project.
Conversion log file (∗.FAD): This file contains information about

required changes and errors that were
detected during conversion of the
application to the current release.
Database integrity log file (∗.CRC): This file contains information about
CRC errors that are detected by FSC
Navigator, and is used to verify the
integrity of the FSC databases.
On-line rebuild log file (∗.OLR): This file contains all messages that
were generated during an on-line
rebuild.
Menu selection log file (CRC.LOG): This file lists any errors that occurred
(e.g. CRC errors) when the various
FSC Navigator application files were
called from the main screen.
Software Manual
Section 9: Log Files 9-1
All log files are project-related and are located in the corresponding
project folder. An exception is the menu selection log file
(CRC.LOG), which is project-independent and can be found in the
FSC Navigator application folder (C:\FSC by default).
The contents of the log files can be viewed, printed or saved to disk.
Viewing log files The 'View Log' option can be called in three ways:
• Menu bar: File / View Log

• Button bar: View Log
• Navigation area: FSC Safety Compliance / View Log
Software Manual
9-2 Section 9: Log Files
9.2 Selecting a Log File
Selecting If you select the 'View Log' option, a submenu will appear, which
a log file allows you to choose which log file you wish to view:
Figure 9-1 Button bar, with 'View Log' submenu
Only the log files that are actually available for viewing will be valid
menu options. The submenu as shown in Figure 9-1, for example,
shows the 'Verify Application' option disabled. This means that the
verification log file is not available for viewing, either because
verification has not yet taken place or because verification did take
place but no errors were found (and logged).
Note:
The log files will always relate to the project that is currently
open. If you wish to view the log files of a different project, you
must first close the current project and open the project whose
log files you wish to view.
Software Manual
9.3 Log File Viewer
9.3.1 Viewing a Log File
Log file viewer After a log file has been selected, the log file viewer will open and
show the requested log file. Figure 9-2 shows the log file viewer with
an example of the translation log file.
Figure 9-2 Log file viewer with translation log file
The log file viewer has a number of options that allow you to modify
the font settings (see subsection 9.3.2), as well as buttons for printing
or saving the log file (see subsections 9.3.3 and 9.3.4).
If the data contained in the log file does not fit in the viewer window,
horizontal and/or vertical scroll bars are provided which enable you to
view the entire log file.
Software Manual
Notes:
1. The log file viewer window is resizeable, which means that
you can use the mouse to "drag" the window edges to
change the window size.
2. The date and time format used in the log file viewer depends
on the Regional Settings in Control Panel.
9.3.2 Font Type and Size
Font type By default, the log files will be shown in the Courier New font with
and size font size 11 pt. If you want, you can modify these font settings.
FSC Navigator "remembers" the font settings, which means that the
log file viewer will always open with the font settings that were used
during the last session.
Changing To change the font type, choose the Font button in the upper left
the font type corner of the log file viewer. This will open the window as shown in
Figure 9-3 below. Here you can choose the font type and style that
you wish to use for viewing and printing the log files.
Figure 9-3 Changing the font type and style
Software Manual
Notes:
1. The font selection list only shows non-proportional fonts.
This means that all letters will have the same width,
regardless of their shape ('i' vs. 'm').
2. The font type and style that you choose will be used for both
on-screen viewing and printing.
Changing To change the font size, you can use the Size selection list in the Font
the font size window (see Figure 9-3), or you can use the Font Size spin button in
the log file viewer (see Figure 9-4).
Figure 9-4 Font size spin button
The default font size is 11 pt, but you can choose any value between
8 pt and 24 pt.
Please note that the font size that you choose will be used for both
on-screen viewing and printing.
Software Manual
9.3.3 Printing a Log File
Printing The Print button in the log file viewer allows you to print the log file
a log file currently being displayed to any printer configured in Windows. If
you choose the Print button, the standard Windows Print dialog will
open:
Figure 9-5 Printing log files
Note:
The Print dialog may look differently than shown in Figure 9-5,
depending on the selected printer and the exact Windows
version that you are running.
Paper size If you want to change the paper size and orientation (or any other
and orientation printing parameters) that should be used for the print job, you can use
the Properties button to modify the printer settings.
Note:
The Properties dialog that appears depends on the selected
printer and the exact printer driver that you are using.
Software Manual
9.3.4 Saving a Log File to Disk
Saving The Save As button in the log file viewer allows you to save the log
a log file file currently being displayed to disk. If you choose this button, the
following dialog will open:
Figure 9-6 Saving a log file to disk
To save the log file to disk, move to the folder you wish to save the
file to, and enter a valid file name in the File Name text box. The
default file extension is 'LOG'. This extension is assumed, which
means that you do not have to enter it. However, if you add a different
extension to your file name, this will be the extension that the file will
have. Thus, if you enter MYFILE as the file name, the log file will be
saved as MYFILE.LOG. If you enter MYFILE.TXT, it will be saved
as MYFILE.TXT.
Log files are saved to disk as plain ASCII files, which means that they
can be opened in any word processor or any other application that has
text-processing capabilities.
Software Manual
Fail Safe Control
Section 10:
Loading Software
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 10: Loading Software
10.1 Introduction .................................................................................................. 10-1
10.2 Loading Methods.......................................................................................... 10-3

10.2.1 Downloading vs. EPROMs............................................................................................. 10-3
10.2.2 Module Support .............................................................................................................. 10-3
10.3 Downloading to Memory.............................................................................. 10-5

10.3.1 Introduction..................................................................................................................... 10-5
10.3.2 Important Considerations for Downloading to Memory.................................................. 10-5
10.3.3 Basic Download Procedure............................................................................................ 10-7
10.3.4 Starting the Download Option ........................................................................................ 10-8
10.3.5 Selecting the Central Part for Downloading ................................................................. 10-10
10.3.6 Download Screen (RAM Mode) ................................................................................... 10-11
10.3.7 Download Screen (Flash Memory Mode) .................................................................... 10-12
10.3.8 Shutting Down the Central Part.................................................................................... 10-13
10.3.9 Download Menu ........................................................................................................... 10-15
10.3.10 Switching Between Central Parts................................................................................. 10-16
10.3.11 Download Matrix (Flash Memory Mode) ...................................................................... 10-17
10.3.12 Download Dependencies ............................................................................................. 10-21
10.3.13 Configured Hardware vs. Detected Hardware ............................................................. 10-21
10.3.14 Downloading to Flash Memory..................................................................................... 10-22
10.3.15 Downloading to RAM ................................................................................................... 10-24
10.3.16 After the Download....................................................................................................... 10-25
10.4 Programming EPROMs .............................................................................. 10-30

10.4.1 Introduction................................................................................................................... 10-30
10.4.2 Important Considerations for Programming EPROMs ................................................. 10-30
10.4.3 Starting the EPROM Programming Option .................................................................. 10-31
10.4.4 Main Menu.................................................................................................................... 10-33
10.4.5 Setting the Programming Options ................................................................................ 10-35
10.4.6 Programming EPROMs................................................................................................ 10-37
10.4.7 Reading EPROMs ........................................................................................................ 10-38
10.4.8 Blank-Checking EPROMs ............................................................................................ 10-39
10.4.9 Verifying EPROMs ....................................................................................................... 10-40
10.5 EPROM Programming Algorithms ............................................................ 10-41

10.5.1 Intel Intelligent Algorithm.............................................................................................. 10-41
10.5.2 Intel Quick Pulse Algorithm .......................................................................................... 10-41
10.5.3 Flash Algorithm ............................................................................................................ 10-42
10.6 Supported EPROMs ................................................................................... 10-43
10.7 Error Messages .......................................................................................... 10-44
Software Manual
Section 10: Loading Software i
FIGURES
Figure 10-1 Basic download process for redundant systems ...................................................... 10-7
Figure 10-2 Load Software button with Download option............................................................. 10-8
Figure 10-3 Selecting the Central Part for downloading............................................................. 10-10
Figure 10-4 Download screen (RAM) ......................................................................................... 10-11
Figure 10-5 Download screen (flash-memory mode) ................................................................. 10-12
Figure 10-6 Download in progress (flash-memory mode) .......................................................... 10-23
Figure 10-7 Download in progress (RAM mode) ........................................................................ 10-24
Figure 10-8 Extended diagnostics after download ..................................................................... 10-26
Figure 10-9 Download operation completed successfully .......................................................... 10-29
Figure 10-10 Setting the programmer's I/O address .................................................................... 10-32
Figure 10-11 Programming EPROMs: main menu....................................................................... 10-33
Figure 10-12 Specifying the programming configuration.............................................................. 10-35
Figure 10-13 Saving EPROM contents to file............................................................................... 10-39
Figure 10-14 Comparing data between EPROM and file ............................................................. 10-40
TABLES
Table 10-1 Loading software to CPU modules ........................................................................... 10-3

Table 10-2 Loading software to COM modules........................................................................... 10-4
Table 10-3 Information source for download matrix.................................................................. 10-21
Table 10-4 Extended diagnostics after a successful download ................................................ 10-28
Table 10-5 EPROMs supported by FSC Navigator................................................................... 10-43
Software Manual
ii Section 10: Loading Software
Section 10 – Loading Software
10.1 Introduction
Loading software The application logic that was created using the functional logic
diagrams (FLDs) and translated into machine code must be
transferred to the FSC system before it can be used in the safety
application.
Modules All required software is contained in non-volatile memory on two

module types in the FSC cabinet (all located in the Central Parts):
• Central Processing Units (CPU)
CPU modules are identified by type numbers 10002/1/2,
10012/1/2, or 10020/1/1.
• Communication modules (COM)
Communication modules are identified by type numbers
10004/x/x, 10008/x/x, 10014/x/x, 10018/x/x, or 10024/x/x.
Software All CPU and COM modules contain three types of software:
• Boot program
This is firmware that defines the hardware of the module (type of
module, channel usage, etc.). This software is preprogrammed,
and will normally never have to be updated.
• System software
This piece of software defines the functionality of the module at a
system level, e.g. ability to handle communication requests. The
system software will usually only need to be updated after you
have upgraded to a newer FSC Navigator version.
• Application program
For CPU modules, this piece of software is the actual safety
application program that was defined using the Functional Logic
Diagrams (FLDs).
For COM modules, it is the firmware that is used to handle all
information exchange between the FSC system and other
computer equipment.
The CPU and COM application programs need to be updated
each time your safety application is modified (and translated).
Software Manual
Section 10: Loading Software 10-1
Important!
1. It is strongly recommended that you carefully read all
appropriate subsections before carrying out any software
transfer to the FSC system.
2. On-line software downloading should be carried out with the
utmost care, and by authorized and qualified persons only.
In case of problems during the on-line software download,
the FSC system can go to a safe state resulting in a process
shutdown.
3. After you have made any modifications to an existing
application, make sure that you translate the application
before transferring it to the FSC system. If you do not
translate first, you may load an old version. For details on
translating an application refer to Section 8 of this manual.
4. It is essential that you upgrade the firmware of 10008/2/U
modules with firmware R420 to the latest firmware version
prior to downloading any software.
Software Manual
10-2 Section 10: Loading Software
10.2 Loading Methods
10.2.1 Downloading vs. EPROMs
Loading methods There are basically two ways to transfer the software to the FSC
system:
• Downloading it directly to random access memory (RAM) or flash
memory on the CPU and/or COM module(s) in the FSC cabinet.
This method does not require the modules to be removed from the
rack. For details refer to subsection 10.3.
• Programming EPROMs, which are subsequently placed on the
CPU and/or COM module(s) in the FSC cabinet. This method
requires the modules to be removed from the rack and re-installed.
10.2.2 Module Support
Module support The loading method that can be used depends on the CPU and COM
module types in the FSC system. Not all module types support
downloading to (flash) memory. Some require EPROMs to be used.
Table 10-1 and Table 10-2 below provide an overview of which
module types support which software downloads.
Note:
To be able to load software correctly, you must make sure that
the operating mode ("memory type") of your application is set
correctly. For details refer to Section 4 of this manual.
Table 10-1 Loading software to CPU modules

Software is loaded to...
CPU module type Boot program System software Application software
10002/1/2 (CPU) EPROMs EPROMs RAM
10012/1/2 (CPU) Flash memory Flash memory Flash memory
10020/1/1 (QPM) Flash memory Flash memory Flash memory
Software Manual
Table 10-2 Loading software to COM modules
Software is loaded to...
COM module type Boot program System software Application software
10004/x/x (COM) EPROMs EPROMs EPROMs

1) 2)
10008/2/U (SMM) EPROMs EPROMs N/A
2)
10008/3/P (P-Bus) EPROMs EPROMs N/A
10014/x/x (COM) Flash memory Flash memory Flash memory

3) 2)
10018/2/U (SMM) Flash memory Flash memory N/A
2)
10018/E/x (PlantScape) Flash memory Flash memory N/A
10024/x/x (ECM) Flash memory Flash memory Flash memory

or or or
EPROMs EPROMs EPROMs
1) EPROMs should be used for the communication firmware. The personality image
X
(PI) is loaded from the TPS operator station (US, U S, GUS).
2) The module receives its application software from the CPU module.
3) Only the communication firmware can be downloaded. The personality image (PI)
X
is loaded from the TPS operator station (US, U S, GUS).
Important!
Communication software larger than 2 Mb cannot be loaded into
EPROMs. They must be loaded to flash memory (FLASH).
Software Manual
10.3 Downloading to Memory
10.3.1 Introduction
Downloading The easiest way to transfer software to the FSC system is by

software downloading it directly to (flash) memory on the appropriate modules
in the system cabinet. This means that no modules need to be
removed from the FSC cabinet and re-installed.
Communication The communication protocol used for downloading software into the
protocol FSC system is the FSC Development System (FSC-DS) protocol.
FSC Navigator automatically determines which baud rate can be used.
If communication cannot be established using the highest baud rate
possible, it will automatically switch to a lower baud rate. If no
communication can be established at the lowest baud rate, an error
message is displayed on screen.
Note:
For details on the FSC-DS communication protocol refer to
10.3.2 Important Considerations for Downloading to Memory
Considerations The following important considerations apply to downloading to

memory:
Prerequisites Downloading can only be done if there is a communication link

for download between the FSC user station and the FSC system.
07177 If the 07177/1/x serial interface module is used to communicate with

interface module the FSC system (i.e. the communication port has been set to '07177'),
it must be installed correctly for downloading to be possible. Also,
the special communication driver must be installed correctly. For
details on installing the 07177/1/x interface module and the
communication driver refer to Section 2 of this manual ("Installation
Guide").
Software Manual
Hardware Downloading can only be done if the hardware modules in the FSC
system support this feature (see subsection 10.2.2).
Password If the password for loading software is active, you must first enter the
correct password to be able to download software. For more
information on passwords, refer to Section 3 of this manual ("Using
FSC Navigator").
Memory type To use the download option, the memory type used must be 'RAM' or
'FLASH', or the application must be in simulation mode. To
configure the memory type or simulation mode, use the 'System
Configuration' option of FSC Navigator (see Section 4 of this
manual).
Modem connection The download features will be disabled if the connection with the
FSC system has been established via modem.
FSC-SMM If your system contains an FSC Safety Manager Module

(FSC-SMM), make sure that you always reload the Personality Image
(PI) after completing a download of a new application version (on-
line modification). For details refer to Appendix D of this manual
("On-Line Modification").
If a firmware download is to be performed for a 10018/2/U Safety

Manager Module (SMM), make sure that you shut down the module
from the TPS operator station (US, UXS, GUS) before starting the
download. If you do not, the download will start but cannot be
completed successfully, and a "module faulty" message will be
displayed. If this does not work, pull the module from the rack,
reinstall it, and restart the download (typing 'Y' when asked whether
the 10018/x/x modules should be shut down and downloaded as well).
Network If a new system is added to an existing network of FSC systems, the

software for the new system must be downloaded using a direct DS
link.
PlantScape When a new FSC application has been downloaded into the system
interface module (e.g. during an on-line modification) and a Central Part is started up,
any 10018/E/x Ethernet interface module will automatically restart to
reinitialize itself. During this restart, the status LED of the 10018/E/x
module will light up red while the eight other (red) LEDs will be
activated one by one.
After completion of the restart, the status LED will light up green
again while the other LEDs will display their normal functions.
This is normal behavior.
Software Manual
10.3.3 Basic Download Procedure
Download Figure 10-1 below outlines the basic download procedure for
procedure redundant systems:
Before any downloading to memory can take place, the Central Part
whose software will be downloaded must be shut down. After
downloading, the Central Part is restarted and brought back on-line.
In redundant systems, the software for both Central Parts must be
downloaded. The download procedure as shown in Figure 10-1 is
described in the following subsections.
Note:
Appendix D of this manual ("On-Line Modification") contains
detailed, step-by-step procedures for downloading to flash
memory and RAM as part of on-line modification (OLM).
System Central Part 1 Switch Central Part 2 System

running running Central Part running running
Shut down Start up Shut down Start up

Central Part 1 Central Part 1 Central Part 2 Central Part 2
Ready for Download Ready for Download

download successful download successful
Download Download
software software
(Central Part 1) (Central Part 2)
Figure 10-1 Basic download process for redundant systems
Software Manual
10.3.4 Starting the Download Option
Calling the
download option The download option of FSC Navigator can be called in two ways:
• Menu bar: Project / Download

• Navigation area: FSC Project Configuration / Load Software /
Download (see Figure 10-2)
Figure 10-2 Load Software button with Download option
Communication If your project has been configured in RAM mode (i.e. the memory
EPROMs type is set to 'RAM'), the following warning will be displayed when
you start the download option:
Make sure the communication EPROMs have been
programmed. Continue? (Y/N)
This warning is displayed to remind you that you should not forget to
program new communication EPROMs before continuing with the
download. In RAM mode, the CPU software is downloaded, but
EPROMs are still required for the communication modules. If you do
not make new EPROMs, you may load the new CPU software, while
the COM software is not updated.
If you answer 'No', you will exit the download option.
If you answer 'Yes', you will continue.
Changes detected If FSC Navigator detects that any changes were made to the FSC
configuration database since the project was last translated, the
following warning will be displayed:
Changes detected since the last translation. Continue
anyway? (Y/N)
This warning is displayed to remind you that you should not forget to
translate a project after you have made any changes to it. Only then
can you be sure that the latest version is downloaded.
If you answer 'No', you will exit the download option.
If you answer 'Yes', you will continue. (This may be useful if you
want to reload an existing version of the software.)
Software Manual
07177 module If you use the 07177/1/x serial interface module to communicate with
the FSC system (i.e. the communication port has been set to '07177'),
it should be properly configured before you can download any
software. Also, you need to install a special software communication
driver onto the FSC user station.
If the module has not been connected properly or the communication
driver has not been (correctly) installed, FSC Navigator cannot detect
the module, and the following message will be displayed on screen:
The 07177 module cannot be reached:
FSC 07177 module driver has not started or has not been
installed.
After you press <Esc>, you will exit the download option.
For details on the 07177 interface module and the communication
driver refer to sections 2.2 and 2.3 of this manual. ("Installation
Guide").
Software Manual
10.3.5 Selecting the Central Part for Downloading
Selecting the If the FSC system is redundant (i.e. contains two Central Parts), you
Central Part must first select the Central Part whose software you wish to
download (see Figure 10-3 below). You will normally want to start
with Central Part 1. If your system is non-redundant ('single'), you do
not need to specify a Central Part.
Press <Space> to toggle the Central Part number, and <Enter> to

confirm. You can also press <?> to choose from a list of available
options. If you press <Esc>, you will return to the FSC Navigator
main screen.
Note:
In redundant configurations, make sure that you download the
software for both Central Parts. If you do not, the system will
not be able to start up.
Figure 10-3 Selecting the Central Part for downloading
Software Manual
10.3.6 Download Screen (RAM Mode)
Download screen After you have selected a Central Part (if required), the download
screen will appear.
RAM If FSC Navigator has detected that a 10002/1/2 CPU module (RAM)
has been configured in the FSC system, the screen as shown in Figure
10-4 will appear. The number of the selected Central Part and the
name of the application are shown at the bottom of the screen. If the
system has been configured for simulation mode, the words
'Simulation mode' are displayed in the top right corner of the screen.
Figure 10-4 Download screen (RAM)
The menu that is shown depends on the operational status of the

selected Central Part. For details refer to subsection 10.3.9 on page
10-15.
Software Manual
10.3.7 Download Screen (Flash Memory Mode)
Download screen After you have selected a Central Part (if required), the download
screen will appear.
Flash memory If FSC Navigator has detected modules in the FSC system
configuration that support downloading to flash memory (10012/1/2,
10020/1/1, 10014/x/x, 10018/x/x, or 10024/x/x), the screen as shown
in Figure 10-5 will appear. The number of the selected Central Part
and the name of the application are shown at the bottom of the screen.
If the system has been configured for simulation mode, the words
'Simulation mode' are displayed in the top right corner of the screen.
Figure 10-5 Download screen (flash-memory mode)
The download screen shows a matrix that lists the CPU module and
any COM modules that have been found in the selected Central Part,
together with their download status. The CPU module will always be
on the first line. For details on the download matrix refer to subsection
10.3.11 on page 10-17.
Software Manual
The menu that is shown depends on the operational status of the
selected Central Part. For details refer to subsection 10.3.9 on page
10-15.
10.3.8 Shutting Down the Central Part
Shutting down The selected Central Part needs to be shut down before any
the Central Part downloading can take place. How to do that depends on the CPU
module that is contained in the Central Part:
• 10020/1/1, or
• 10002/1/2 or 10012/1/2.
10020/1/1 If the FSC system contains a 10020/1/1 Quad Processor Module

(QPM), the module's key switch needs to be set to IDLE (=
horizontal position) before downloading can take place.
Key switch = RUN If the key switch is in the RUN position and the Central Part is
and CP is running running, the following message is displayed in the message bar of the
download screen:
System is running. Set processor module key to IDLE to
stop central part.
Key switch = RUN If the key switch is in the RUN position and the Central Part has been
and CP is shut down shut down, the following message is displayed in the message bar of
the download screen:
Load cannot start. Set processor module key to IDLE to
continue.
Make sure that the key switch is in the IDLE position. The download
menu will then appear (see subsection 10.3.9). Also, the words
'Central part stopped' are shown in the bottom right corner of the
screen to indicate that the selected Central Part has shut down.
Important!
When you set the key switch to the IDLE position, some
communication errors may be reported (e.g. 'communication
with too many retries'). This is normal behavior.
Software Manual
10002/1/2 or If the FSC system contains a 10002/1/2 or 10012/1/2 CPU module
10012/1/2 and the selected Central Part has not been shut down yet, the
download menu will contain an option called 'sTop central part'.
Choose this option to shut down the selected Central Part and bring it
to the state that allows downloading. Before the Central Part will
actually be shut down, you are first asked to confirm the operation:
System is running. Stop execution? (Y/N)
If you type 'N', you will return to the main download menu without
shutting down the Central Part. Please note that you must shut down
the Central Part before any downloading can take place.
If you type 'Y', the selected Central Part will be shut down, and you
will return to the main download menu. The 'sTop central part' option
has now disappeared, and has been replaced with the 'Start' option.
Also, the words 'Central part stopped' are shown in the bottom right
corner of the screen to indicate that the selected Central Part has shut
down.
Important!
1. You can only shut down the Central Part if the Force Enable
key switch is present and has been activated. Otherwise an
error message will be displayed.
2. After you have shut down the Central Part and you decide not
to download any software (by choosing 'eXit' rather than
'Start'), the only way to restart the Central Part is by starting
the download option of FSC Navigator again, and choosing
the 'Start' option from the menu.
3. As long as you are in FSC Navigator's download
environment, you can only choose the 'sTop central part'
option once. This means that if you shut down a Central Part
and switch to the other Central Part, no 'sTop central part'
option will be available in the menu. This prevents you from
accidentally shutting down both Central Parts in the system.
'OK' status If the selected Central Part is still running, the download matrix may
display nothing but 'OK', even though the software components may
need updating. The 'OK' status is a system status, which does not say
anything about the software download status. After you shut down
the Central Part, the download matrix is updated to report the actual
download status of the software components.
Software Manual
10.3.9 Download Menu
Menu commands The available options in the download menu depend on the
operational status of the selected Central Part and the CPU module
type that has been detected:
• sTop central part, Other central part, eXit.
• Start, Other central part, eXit.
• Other central part, eXit.
Please note that the 'Other central part' option is only available in
redundant systems.
sTop central part, This menu will be displayed if the FSC system contains a 10002/1/2
Other central part, eXit or 10012/1/2 CPU module and the selected Central Part has not been
shut down yet, which means that no software can be downloaded.
Choose the 'sTop central part' option to shut down the Central Part
(see subsection 10.3.8) and bring it to the state that allows
downloading.
Choose the 'Other central part' option to switch to the other Central
Part in a redundant system (see subsection 10.3.10).
Choose the 'eXit' option to return to the FSC Navigator main screen
without loading anything.
After you have successfully shut down the selected Central Part, the
'sTop central part' option from the menu will be replaced with the
'Start' option, which allows you to start the actual download procedure
(see subsections 10.3.14 to 10.3.16).
Start, This menu will be displayed if the selected Central Part has shut
Other central part, eXit down correctly, and software can be downloaded.
Choose the 'Start' option to start the download process (see
subsections 10.3.14 to 10.3.16).
Choose the 'eXit' option to return to the FSC Navigator main screen
without loading anything.
Note:
If this menu is displayed and you choose the 'eXit' option, the
only way to restart the Central Part is by starting the download
option of FSC Navigator again, and choosing the 'Start' option
from the menu.
Software Manual
Other central part, eXit This menu will be displayed in two cases:
• All software for the selected Central Part has been downloaded
correctly and the Central Part has successfully restarted.
• The selected Central Part has shut down correctly, but no software
can be downloaded (e.g. due to a download status error).
Choose the 'eXit' option to return to the FSC Navigator main screen.
10.3.10 Switching Between Central Parts
Switching between The download screen will always relate to one Central Part at a time.
Central Parts The number of the currently selected Central Part is indicated in the
bottom left corner of the screen.
In a redundant system, you can easily switch between Central Parts by
choosing the 'Other central part' option from the menu.
Alternatively, you can also press Alt + <C>. This will move the cursor
to the 'Central Part' field in the bottom left corner. You can now use
<Space> to toggle between Central Parts. Press <Enter> to confirm.
FSC Navigator will now establish communication with the new

Central Part. The 'Central part' field will show the number of the new
Central Part to indicate that it has now been selected. The download
matrix (see subsection 10.3.11), if displayed, will be updated to reflect
the new selected Central Part. The menu will also be updated, if
required (see subsection 10.3.9).
Important!
1. In redundant configurations, after the software download for
Central Part 1, the download matrix will not automatically
switch to Central Part 2. You need to do that manually using
the 'Other central part' menu option or the Alt + <C> key
combination.
2. As long as you are in FSC Navigator's download
environment, you can only choose the 'sTop central part'
option once. This means that if you shut down a Central Part
and switch to the other Central Part, no 'sTop central part'
option will be available in the menu. This prevents you from
accidentally shutting down both Central Parts in the system.
Software Manual
10020/1/1 If the Central Part you switch to contains a 10020/1/1 CPU module,
key switch the key switch of that module may be in the RUN position while the
Central Part has been shut down. This will typically happen during an
on-line modification. In that case, the following message is displayed
in the message bar of the download screen:
Load cannot start. Set processor module key to IDLE to
continue.
Make sure that the key switch is in the IDLE position. The download
menu (see subsection 10.3.9) will then appear and the download
matrix is updated to report the actual download status of the software
components.
10.3.11 Download Matrix (Flash Memory Mode)
Download matrix If FSC Navigator has detected modules in the FSC system that
support downloading to flash memory (10012/1/2, 10020/1/1,
10014/x/x, 10018/x/x, or 10024/x/x), the download screen will include
a matrix that lists the CPU module and any COM modules that have
been found in the configuration database. The download matrix
provides the following information for each detected CPU and COM
module:
• the module designation (CPU, COM 1, COM 2, etc.),
• the module type (e.g. 10020/1/1, 10018/2/U, 10024/H/F),
• the module location in the FSC cabinet (rack number and position),
and
• the download status for the various software components
(see below).
Note:
If the communication module type includes a question mark
('?'), this means that there is a discrepancy between the
configured interface and the detected interface. For details refer
to subsection 10.3.13.
Software Manual
Download The matrix in the download screen (see Figure 10-5) shows the
status download status for each software component in each of the modules
that were detected in the Central Part. The download status will be
any of the following:
− Alive − Loaded − No file − Offnet
− Failed − Loading... − Not cfg'd − OK
− Idle − N/A − Not placed − Unknown
Alive This status will normally indicate the following situation:

• the Central Part has shut down correctly, and
• it has been determined that software needs to be updated
(i.e. the versions of the software in the module and on the FSC user
station are not identical), and
• the software is ready to be downloaded.
This is the state that allows downloading (see Figure 10-1).
Note:
The 'Alive' status will also be reported if the module reports a
download error due to a hardware fault or CRC error. The status
of all software components for the affected module may then
change to 'Alive'. This means that all software components need
to be reloaded.
Failed This status indicates that the download procedure was not completed
successfully (e.g. due to hardware problems). It will normally only be
visible for a short time, after which the status will change to 'Alive'.
Idle This status indicates that the download procedure has been completed
successfully, but the Central Part has not been put back on-line yet
(see Figure 10-1). After a successful download, you need to cycle the
WD Reset key switch to bring the Central Part back on-line ('OK'
state). The download matrix is then updated to report the 'OK' status
(indicating that the selected Central Part is back on-line and running).
Loaded This status indicates that the software component is up to date

(i.e. identical to the software files found on the FSC user station),
and does not need to be updated.
Software Manual
Loading... This status indicates that the download process is in progress and that
software is being transferred to the specified module.
N/A This status indicates either of the following situations:

• The specified software component does not exist (e.g. application
program for 10018/2/U module).
• The specified software component does exist, but downloading of
this software is not supported (e.g. system software of 10008/2/U
module).
See also Table 10-1 and Table 10-2 on page 10-3.
No file This status indicates that the file required to perform the download
for the specified piece of software cannot be located on the FSC user
station. If this status is reported for any software component, the
download cannot be started (the menu will not contain a 'Start'
option).
Not cfg'd This status indicates that the specified module has been detected in
the FSC cabinet, but it has not been configured (i.e. it does not exist
in the configuration database). See also 10.3.13 on page 10-21.
If this status is reported for any software component, the download
cannot be started (the menu will not contain a 'Start' option).
Not placed This status indicates either of the following situations:

• The specified module has been configured in the system (i.e. it
exists in the configuration database), but a different module was
detected at its allocated position in the FSC cabinet.
• The specified module has been configured in the system (i.e. it
exists in the configuration database), but no module could be found
at all at its allocated position in the FSC cabinet.
See also 10.3.13 on page 10-21. If this status is reported for any
software component, the download cannot be started (the menu will
not contain a 'Start' option).
Note:
Older 10008/2/U modules (with firmware release 420) do not
report their presence or version to the CPU module. That is why
they will be reported as being 'not placed', even though they are.
It is essential that you upgrade their firmware to the latest
version prior to downloading any software.
Software Manual
Offnet This status indicates that no communication could be established with
the FSC system.
OK This is a system status. It does not say anything about the download
status of the software components. This status indicates that the
Central Part is on-line and running without any faults, either before or
after a download.
If you see the 'OK' status before a download, it does not necessarily
mean that no software needs to be updated. If the Central Part is still
running, the download matrix may report nothing but 'OK', even
though the software components may need updating. The selected
Central Part must be shut down before any downloading can take
place (see subsection 10.3.8 on page 10-13). After the Central Part has
been shut down successfully, the download matrix is updated to report
the actual download status of the software components. Also, the
'sTop central part' option from the menu has been replaced with the
'Start' option, which allows you to start the actual download
procedure.
If the download matrix contains nothing but 'OK' after a download,
the download procedure has been completed successfully and the
Central Part is back on-line and running. In redundant configurations,
you can then proceed with downloading the software for the other
Central Part.
Unknown This status indicates that the version of the specified piece of
software could not be determined. This will typically be the case for
the boot program and system software of the 10018/2/U FSC-SMM
or 10018/E/x PlantScape interface module.
Software Manual
10.3.12 Download Dependencies
Download Sometimes the download matrix will indicate that a particular piece
dependencies of software needs to be updated, even though, strictly speaking, there
may not be any need for that. This is because downloading of certain
software components is automatically "linked" to the status of other
components:
• Both CPU and COM modules:
If the boot program is not up to date, then the system software and
application program must also be downloaded. This means that you
will never see the status line 'Alive, Loaded, Loaded' for any
module.
• COM modules only:
If the system software is not up to date, then the application
program must also be downloaded. This means that you will never
see the status line 'Loaded, Alive, Loaded' for any COM module.
10.3.13 Configured Hardware vs. Detected Hardware
Information For flash-memory modules, all information in the download matrix is

source retrieved from the FSC configuration database, which is stored on the
FSC user station. The system configuration as laid down in the FSC
database is compared to the hardware that is actually detected in the
FSC cabinet. Table 10-3 below lists what happens if any
discrepancies are found.
Table 10-3 Information source for download matrix

If ... found in and ... detected in then ... reported in
FSC database FSC cabinet download matrix
Module X Module X Idle / Alive / Loaded, etc.
Module X Module Y Module X not placed
Module X nothing Module X not placed
nothing Module Y Module Y not cfg'd
Module X (COM a) Module X (COM b) Module X not placed
(= incorrect jumper settings) Module X not cfg'd
Software Manual
Notes:
1. If the status Not placed and Not cfg'd are reported for the
same module, this is typically caused by incorrect jumper
settings.
2. Older 10008/x/x modules (with firmware release 420) do not
report their presence or version to the CPU module. That is
why they will be reported as being 'not placed', even though
they are.
Communication Please note that communication modules with different interfaces are
interfaces not considered to be identical. (For example, a 10014/H/F and
10014/I/F are not the same module.)
If a discrepancy is found between configured and detected
communication interfaces, the download matrix will display a
question mark ('?') for the affected interface. If, for example, the
matrix displays '10014/?/F', this means that the configured hardware
is, say, 10014/H/F, whereas the detected hardware may be 10014/I/F.
This does not prevent you from downloading, but a warning will be
displayed prior to downloading.
10.3.14 Downloading to Flash Memory
Starting Choose the 'Start' option from the menu to start downloading the
the download software components in accordance with their download status as
shown in the download matrix.
If a 10018/x/x communication module (FSC-SMM or PlantScape) has

been detected in the FSC system, you will first be asked whether the
software for this module should be downloaded or not:
Shutdown and download 10018/./. module also? (Y/N)
Please note that downloading is only required if the firmware has
changed, which may (but does not need to) be the case if you upgrade
to a new FSC release. This means that normally you do not need to
download the module software for the 10018/2/U FSC-SMM or
10018/E/x PlantScape interface module.
If no firmware upgrade is required, make sure that you always type 'N'
to start the download process without downloading the 10018/x/x
module software. Type 'Y' to start the download process including the
10018/x/x module software. (Please note that the module's 'Unknown'
status will then change to 'Alive'.)
Software Manual
You can press <Esc> at any time to interrupt the download. During
the download process, the screen will look something like Figure 10-6
below.
Figure 10-6 Download in progress (flash-memory mode)
A percentage bar is displayed to show the progress of each software

component download. The download process may take some time,
depending on the amount of software to be downloaded and the
communication baud rate used. During downloading, the time
indication at the Diagnostic and Battery Module (DBM) is frozen or
blank.
The download matrix will always be processed from top to bottom,

from left to right. This means that downloading will start with the boot
program of the CPU module (if required) and end with the application
program of the last COM module.
Any error messages are displayed in a maximum of four lines below

the progress bar. Their color depends on the color settings of FSC
Navigator. The default color is red. For details refer to Section 3 of
this manual ("Using FSC Navigator").
Software Manual
The top message is always the most recent one. If there are more than
four messages, the oldest one (i.e. the bottom line) will disappear.
Refer to subsection 10.7 for a list of error messages that may appear
during downloading.
10.3.15 Downloading to RAM
Starting Choose the 'Start' option from the menu to start downloading the
the download application software to the 10002/1/2 CPU module (after an
acknowledgment from the FSC system). During the download
process, the screen will look something like Figure 10-7 below.
Figure 10-7 Download in progress (RAM mode)
You can press <Esc> at any time to interrupt the download.

A percentage bar is displayed to show how much of the CPU
application program has been downloaded. The size and name of the
file being downloaded are also shown.
Software Manual
The download process may take some time, depending on the size of
the CPU application program to be downloaded and the
communication baud rate used. During downloading, the time
indication at the Diagnostic and Battery Module (DBM) is frozen or
blank.
Any error messages are displayed on screen. Refer to subsection 10.7

for a list of error messages that may appear during downloading.
10.3.16 After the Download
After the download After all software has been downloaded, a 20-second timeout is
initiated (indicated by a progress bar), which allows the FSC system
to re-initialize. After that, FSC Navigator will automatically retrieve
the extended diagnostics from the system and display them on screen
(see Figure 10-8).
Note:
Old diagnostics messages, if any, are not cleared. You should
therefore pay close attention to the exact timestamp of reported
messages.
On-line If the downloaded application is being activated while the FSC

modification system is running (typically during on-line modification), the system
will first check the application of the Central Part and the FSC-FSC
communication. This may take some time, depending on the size of
the application. During this check, the following message is displayed
on screen:
Waiting for OLM check and FSC-FSC COM check...
After completing the OLM check and the FSC-FSC communication
check, the diagnostics of the FSC system are retrieved and displayed.
Software Manual
Figure 10-8 Extended diagnostics after download
Message bar The message bar in the Extended Diagnostics screen will show a
message, depending on the CPU module type and the success of the
download:
• Load successful. Set processor module key to RUN and cycle
RESET key to start.
This message is only applicable if the FSC system contains a
10020/1/1 CPU module. It will appear if the download and all
subsequent checks were successful. You must set the key switch of
the 10020/1/1 CPU module to the RUN position and cycle the WD
Reset key switch to restart the selected Central Part and start the
downloaded application. The message 'Central part stopped' will
now disappear. You can then switch to the other Central Part in a
redundant system to download the software for that Central Part
(see subsection 10.3.10 on page 10-16).
• Load successful. Cycle RESET key switch to start.
This message will appear if the download and all subsequent checks
were successful. You must cycle the WD Reset key switch to restart
the selected Central Part and start the downloaded application. The
Software Manual
message 'Central part stopped' will now disappear. You can then
switch to the other Central Part in a redundant system to download
the software for that Central Part (see subsection 10.3.10 on page
10-16).
• Load successful. Please VERIFY extended diagnostics.
This message will appear if the download has been completed
successfully and the Central Part was not running (off-line). If any
system faults were detected, the appropriate extended diagnostic
messages will be displayed (see below). Make sure that you correct
any reported errors before attempting to put the system back
on-line. For details on the extended diagnostic messages refer to
Section 12 of this manual ("On-Line Environment").
• Load NOT successful. Press any key.
This message will appear if the download operation was not
completed successfully. The extended diagnostics screen will list
the appropriate error messages. Correct the errors and reload the
software.
Diagnostic Not all messages that may appear in the Extended Diagnostics screen
messages are necessarily serious and cause for concern. A number of them are
only for information purposes or indicate minor issues. The following
diagnostic messages are part of the normal download process:
• No faults detected.
• No differences detected in application program.
• Difference found at FLD(s)
(followed by all FLDs that have changed).
• Processor module key in IDLE position
(10020/1/1 CPU module only).
Table 10-4 on the next page explains when the first three of the above
messages are displayed.
Make sure that you carefully read all messages in the Extended
Diagnostics screen, and that you correct any reported errors before
continuing. For details on extended diagnostic messages refer to
Software Manual
Table 10-4 Extended diagnostics after a successful download
Message displayed Single / Other CP Version of Application
redundant running? application in program
configuration other CP different? changed?
No faults detected. Single n/a n/a n/a
No faults detected. Redundant No n/a n/a
No faults detected. Redundant Yes No n/a
No differences detected in Redundant Yes Yes No

application program.
Differences found at FLD(s)* Redundant Yes Yes Yes
* This message is always followed by all FLDs that have changed.
Finalizing After everything has been completed successfully, you will return to
the download the download screen (see Figure 10-4 or Figure 10-5). The download
matrix (flash-memory mode only) will now display the 'OK' status for
all modules, and the menu bar will present the menu options 'Other
central part' and 'eXit' (see Figure 10-9 on the next page).
Important!
1. If the system cannot go to the 'OK' state (e.g. because you
pressed <Esc> in the extended diagnostics screen without
cycling the WD Reset key switch), the download matrix will
report the 'Idle' status for all modules. This means that the
download was successful, but the Central Part has not been
put back on-line yet. You must cycle the WD Reset key
switch to bring the Central Part back on-line.
2. In redundant configurations, make sure that you download
the software for both Central Parts. If you do not, the system
cannot restart and operate correctly.
Software Manual
Figure 10-9 Download operation completed successfully
Software Manual
10.4 Programming EPROMs
10.4.1 Introduction
Programming Some modules do not support downloading of software. Their

EPROMs software must be made available by programming it into EPROMs
and installing those on the modules in the FSC system cabinet.
Two types of EPROMs can be programmed:

• FSC application EPROMs for the CPU and COM modules, and
• the CPU system program EPROMs.
EPROMs must be programmed for the following CPU and COM

modules: 10002/1/2, 10004/x/x and 10008/x/x (see also Table 10-1 and
Table 10-2 on page 10-4).
EPROMs may be programmed for the 10024/x/x communication
modules. (They also support downloading to flash memory.)
10.4.2 Important Considerations for Programming EPROMs
Considerations The following important considerations apply to programming

EPROMs:
07177 You can only program EPROMs if the FSC user station contains a
interface module 07177 serial interface module that the EPROM programmer can be
connected to. For details refer to section 2.2 of this manual.
07177 You can only program EPROMs if the 07177 communication driver
communication driver has been properly installed on the FSC user station. For details refer
to section 2.3 of this manual.
07170 You can only program EPROMs if the 07170 EPROM programmer
EPROM programmer has been properly connected to the FSC user station.
10012/M/1 or 10014/M/1 Do not attempt to program 10012/M/1 or 10014/M/1 memory boards

memory boards on the EPROM programmer. This will irreparably damage the
memory boards!
Software Manual
LEDs on EPROM The EPROM programmer has two LEDs for each EPROM position: a
programmer green one and a red one. They are located immediately behind each
position on the programmer. If any errors occur during programming,
an error message is reported on screen. At the same time, the red
LED(s) for the EPROM(s) that the error message applies to will start
to blink.
10002/A/2 10002/A/2 memory boards are mounted on the CPU module. These
memory board boards use flash memory to store the system program rather than
surface-mounted EPROMs (which are used on 10002/A/1 boards).
Programming 10002/A/2 flash-memory boards will normally take
approximately one minute. However, if you use an old model
07170/1/1 EPROM programmer, programming is slowed down
considerably, and can take up to 20 minutes. Old model programmers
can be identified as follows:
• they have no serial number at all (year: 1988), or
• their serial number is one of the following:
− 1489909001 to 1489909015 (year: 1989)
− 4489109000 to 4489109026 (year: 1989)
− 2190100001 to 2190100050 (year: 1990)
10.4.3 Starting the EPROM Programming Option
Starting The 'Program EPROMs' option of FSC Navigator can be called in

two ways:
• Menu bar: Project / Program EPROMs

• Navigation area: FSC Project Configuration / Load Software /
Program EPROMs (see Figure 10-2)
Note:
The 'Program EPROMs' option will not be available if any of
the following files are corrupt or missing in the FSC Navigator
application folder (C:\FSC by default): COMxxx.BIN (where
'xxx' is the FSC software release number), CTV.BIN and
MTV.BIN.
Software Manual
Checks on If the 'Program EPROMs' option is called, FSC Navigator will first
start-up check whether it can access the 07177 interface module, which the
07170 EPROM programmer is connected to. If this is not the case,
the following error message is displayed on screen:
Figure 10-10 Setting the programmer's I/O address
The 07177 interface module can only be used if a special

communication driver has been installed on the FSC user station.
For details on installing and configuring this driver refer to section 2.3
of this manual.
Note:
Do not place the EPROMs until the 'Program EPROMs' option
of FSC Navigator has completed its startup routine.
Software Manual
10.4.4 Main Menu
Main menu The 'Program EPROMs' option of FSC Navigator can only be used if
the EPROM programmer has been properly connected. If that is the
case, the main menu will be displayed on screen, which allows you to
program, read, copy and blank-check EPROMs:
Figure 10-11 Programming EPROMs: main menu
Menu options The main menu has seven options:
Configuration This option allows you to modify the configuration that is used to
program the application logic into the EPROMs. (For details refer to
subsection 10.4.5.)
Program This option allows you to program or copy the application into one or
more EPROMs. It can only be selected if the EPROM type specified
matches the size of the file to be programmed. (For details refer to
subsection 10.4.6.)
Software Manual
Read This option allows you to read one or more EPROMs and write their
contents to a file. (For details refer to subsection 10.4.7.)
Blank check This option allows you to check whether one or more EPROMs are
empty. (For details refer to subsection 10.4.8.)
Verify This option allows you to check whether one or more EPROMs
contain the same data as a given file. It can only be selected if the
EPROM type specified matches the size of the file to be programmed.
(For details refer to subsection 10.4.9.)
Install This option allows you to calibrate the 07170/1/1 module.

For details on calibrating the 07170/1/1 module refer to the module's
data sheet in the FSC Hardware Manual.
eXit This option returns you to the main screen of FSC Navigator.
You can always return to the main menu from anywhere in the
program by (repeatedly) pressing <Esc>.
Software Manual
10.4.5 Setting the Programming Options
Programming The 'Configuration' option in the main menu allows you to modify
options the configuration that is used to program the application logic into the
EPROMs. The screen as shown in Figure 10-12 will be displayed:
Figure 10-12 Specifying the programming configuration
The following fields are available:
FSC module This field specifies the type of EPROMs that will be programmed:
− Application: Create application software EPROMs which are
located on the CPU module (location = CPU).
− Communication: Create communication EPROMs for the
application.
− CPU system: Create CPU system software EPROMs.
− FSMM firmware: Create FSC-SMM firmware EPROMs.
− P-Bus: Create EPROMs for the Hartmann & Braun P-bus.
Software Manual
Notes:
1. Not all of the above options may be available, depending on the
FSC Navigator package that was purchased.
2. The application software, communication EPROMs and CPU
system software always require four EPROMs of 512 Kb, 1 Mb or
2 Mb.
3. FSC-SMM firmware requires one EPROM of 4 Mb, which must
be placed on position 1 of the EPROM programmer.
4. CPU and COM can only be selected if valid files exist for these
modules.
EPROM type This field specifies the size of the EPROMs used. FSC Navigator
supports four different sizes: 512 Kb, 1 Mb, 2 Mb and 4 Mb.
Programming This field specifies the algorithm that is used to program the
algorithm EPROMs. There are three options:
− Intel Intelligent,
− Intel Quick Pulse, and
− Flash.
(For details refer to subsection 10.5).
Programming This field specifies how the programming procedure will take place.
method There are three options:
Program: Use this option to program an EPROM.
Program, Verify: Use this option to program an EPROM and verify
its contents after programming.
(This option is only available if the programming
algorithm is set to 'Flash'.)
Blank, Prog., Vrf: Use this option to blank-check an EPROM before
programming, program it, and verify its contents
after programming.
(This option is not available if the programming
algorithm is set to 'Flash'.)
The program prevents you from creating an invalid configuration. If

you alter one of the options, the other options are automatically
updated to show only valid configurations. It may also be that some of
the options are blocked once a certain configuration has been selected.
You should therefore always start at the top if you want to modify the
current configuration.
Software Manual
10.4.6 Programming EPROMs
Programming To program or copy the application into one or more EPROMs,

EPROMs choose the 'Program' option in the main menu. It can only be selected
if the EPROM type specified matches the size of the file to be
programmed.
If the FSC module type has been set to 'Communication' or

'Application', FSC Navigator will search for all possible files to
select. If more than one file is available, you will be prompted to
toggle the Central Part number and/or the module sequence number
(e.g. COM1, COM2, CPU1, etc.).
If the FSC module type has been set to 'CPU system' and FSC
Navigator detects a 10002/A/2 flash memory board on the EPROM
programmer, it will automatically change the programming algorithm
to 'Flash' and the programming method to 'Program, verify'.
If the FSC module type has been set to 'CPU system' and FSC
Navigator detects regular 1-Mbit EPROMs on the EPROM
programmer, it will automatically change the programming algorithm
to 'Quick' and the programming method to 'Blank, Prog., Vrf'.
Checks prior to Before the programming or verification procedure is started, the

programming checksum (CRC) of the file is calculated and verified to detect any
data corruption.
Before FSC Navigator starts the actual programming of the EPROMs,

it performs a check to verify whether the EPROMs have been
correctly inserted and whether they are of the correct type and
manufacturer. You must insert the EPROMs correctly before you can
start programming (green LEDs on). If the EPROMs are not of the
correct type or manufacturer, a message is displayed on screen. (For a
list of supported EPROM types refer to subsection 10.6.)
Software Manual
Programming During programming, the screen will show the address currently
procedure being programmed. This will give you an idea how many bytes have
been programmed. Programming can stop in three ways:
1. Programming was successful.
2. Programming crashed.
3. You pressed <Esc> during programming.
The way in which programming stopped will be displayed on screen.

If programming crashed (i.e. unable to program the desired data ), the
address where the programming crashed is also displayed. If your file
format is 'FSC' and programming was successful, the address of the
last bytes which were programmed in your last EPROM set is also
given.
Note:
Programming the memory boards will normally take
approximately one minute. However, if you use an old model
07170/1/1 EPROM programmer, programming is slowed down
considerably, and can take up to 20 minutes. Old model
programmers can be recognized as follows:
• they have no serial number at all (year: 1988), or
• their serial number is one of the following:
– 1489909001 to 1489909015 (year: 1989)
– 4489109000 to 4489109026 (year: 1989)
– 2190100001 to 2190100050 (year: 1990)
10.4.7 Reading EPROMs
Reading The 'Read' option in the main menu allows you to read a set of
EPROMs EPROMs and write their contents to a file.
Before FSC Navigator starts reading the EPROMs, it performs a

check to verify whether the EPROMs have been correctly inserted and
whether they are of the correct type and manufacturer. You must
insert the EPROMs correctly before you can start the reading process
(green LEDs on). If the EPROMs are not of the correct type or
manufacturer, a message is displayed on screen. (For a list of
supported EPROM types refer to subsection 10.6.)
Software Manual
You also need to provide a valid file name before FSC Navigator can
start writing the EPROM contents to a file (see Figure 10-13).
Figure 10-13 Saving EPROM contents to file
10.4.8 Blank-Checking EPROMs
Blank-checking The 'Blank check' option in the main menu allows you to perform a
EPROMs test to check whether the EPROMs are empty. If an error occurs, FSC
Navigator will tell you in which EPROM the error occurred and at
what address.
Software Manual
10.4.9 Verifying EPROMs
Verifying The 'Verify' option in the main menu allows you to check whether the
EPROMs data in the EPROMs is the same as the data in a file. Before
verification starts, you must first enter a file name. The data
contained in the EPROMs is subsequently compared with the data in
that file. If any differences are found, they will be displayed on screen
(see Figure 10-14). The following is shown:
• the address in the EPROM,
• the data contained in the EPROM, and
• the data in the file.
Figure 10-14 Comparing data between EPROM and file
Software Manual
10.5 EPROM Programming Algorithms
Algorithms There are three available algorithms for programming the EPROMs:
• Intel Intelligent (see subsection 10.5.1),
• Intel Quick Pulse (see subsection 10.5.2), and
• Flash (see subsection 10.5.3).
10.5.1 Intel Intelligent Algorithm
Intel Intelligent The duration of an intelligent programming pulse is 1.0 ms. This will
algorithm be repeated until the desired data is settled in the EPROM. After this,
an "overprogram" pulse will follow. The number of these pulses is
three times the number of program pulses needed. For example, if
two pulses were needed before a byte was settled, the algorithm will
give an overpulse of 3 x 2 = 6 ms.
Note:
FSC Navigator does not execute the Intel Intelligent algorithm
exactly as described above. The overprogram pulse of the Intel
Intelligent algorithm is replaced by a fixed number of three
(separate) pulses of 1 ms.
10.5.2 Intel Quick Pulse Algorithm
Intel Quick Pulse The Intel Quick Pulse algorithm differs from the Intel Intelligent
algorithm algorithm in two ways:
• the duration of the programming pulse is not 1.0 ms but 0.1 ms, and
• there is no overprogram pulse.
Note:
FSC Navigator does not execute the Intel Quick Pulse algorithm
exactly as described above. The Intel Quick Pulse algorithm
uses no overprogram pulse. FSC Navigator will, however,
nevertheless give three overprogram pulses of 0.1 ms each.
Software Manual
10.5.3 Flash Algorithm
Flash algorithm The Flash programming algorithm allows the CPU system software
to be programmed into 10002/A/2 flash memory boards, which are
used in conjunction with the 10002/1/2 CPU module. Flash memory
has two main advantages:
• Flash memory is software-erasable using the EPROM programmer.
You no longer need a UV eraser to erase EPROMs.
• Flash memory has improved EMC properties compared to
EPROMs, which means that the programming failure rate will be
lower.
Notes:
1. The 10002/A/2 memory boards are not suitable for
downloading software to flash memory (as described in
subsection 10.3).
2. The Flash programming algorithm can only be used for CPU
system software in conjunction with the 10002/A/2 flash
memory board. This board can be placed on the EPROM
programmer using the 07170/A/. adapter.
3. The 10002/A/2 flash memory board is fully compatible with
the 10002/A/1 board. No jumper settings need to be
changed.
If the specified FSC module type is 'CPU system' and FSC Navigator
detects a 10002/A/2 flash memory board on the EPROM programmer,
it will automatically change the programming algorithm to 'Flash'.
Erasing The flash memory will always automatically be erased prior to

flash memory programming. There is no separate erase option in FSC Navigator. If
you only need to erase the flash memory, you should press the <Esc>
key during the automatic erase process before programming.
Erasing will usually take a few seconds. If the flash memory has not
been successfully erased within ten seconds, an error message will be
displayed. If erasing the flash memory was successful, programming
will start automatically.
Software Manual
10.6 Supported EPROMs
Table 10-5 below lists the EPROMs that are supported by the
'Program EPROMs' option of FSC Navigator.
Table 10-5 EPROMs supported by FSC Navigator

Manufacturer Type Size Remarks
27512 512 Kb
Intel
27010 1 Mb
27C512 512 Kb
27C1001 1 Mb
27C2001 2 Mb Only programmable with Intel Quick Pulse.

NEC
Only for programmers produced after June
1, 1990. FSC Navigator detects if this
27C4001 4 Mb EPROM type can be programmed with the
programmer used. Only programmable with
Intel Quick Pulse.
27512 512 Kb
27C010 1 Mb
AMD 27C020 2 Mb
27C040 4 Mb
571000D 1 Mb
Only for programmers produced after June

1, 1990. FSC Navigator detects if this
Toshiba 574000D 4 Mb EPROM type can be programmed with the
programmer used. Only programmable with
Intel Quick Pulse.
WSI 27010 1 Mb Only programmable with intelligent mode.
SGS-Thompson M27C2001 2 Mb
Honeywell Safety 27C010 on 1 Mb Only programmable with 07170/A/1 adapter

Management 10002/A/1 module module and Intel Intelligent programming
Systems B.V. mode.
Honeywell Safety 29F010 on 1 Mb Only programmable with 07170/A/1 adapter

Management 10002/A/2 module module and Flash programming mode.
Systems B.V.
Software Manual
10.7 Error Messages
Messages The following error messages may appear during downloading or

EPROM programming:
Application files not translated for download.

Change the operating mode of the application to RAM mode or
simulation mode, and translate again.
Application name of connected system not correct.

You attempted to stop a Central Part while the application name in
the FSC system does not match the name of the current application
in FSC Navigator. Please note that this message will not be
displayed if the connected system is in simulation mode.
Application versions in database and FSC system do not match.

You have translated your application without loading it to the FSC
system. The application in the database may differ from the
application in the FSC system.
Command not allowed.

You have entered a force command, but the FSC system does not
accept it because it is not allowed.
Communication: <error message>

Description: This message indicates that a communication error
has occurred. The error message further specifies the error. These
error messages are explained in more detail in Section 12 of this
manual ("On-Line Environment").
Communication with too many retries.

a) Check if the communication cable is terminated correctly, has
no broken wires, etc.
b) Decrease the communication speed as the length of the
communication cable may be too long for the selected
communication speed.
Corrupt extended diagnostic data file(s).

Delete the diagnostic index files (.EXR and .EXT).
Software Manual
Error in communication between user station and FSC system.
a) Check if the cable has been plugged into the correct
communication port of the FSC user station and/or the FSC
system.
b) Check if the FSC COM port has been set correctly.
c) Check if the EPROMs on the COM module have been placed
correctly. If they are, verify the EPROMs.
d) Check all modules on the system bus for correct EPROMs and
jumper settings.
e) Decrease the communication speed (the length of the
communication cable may be too long for the communication
speed).
Error updating extended diagnostic data file(s).

Delete <application name>.EXT in the application folder. The
database will be rebuilt.
File I/O error

Description: This message appears if FSC Navigator cannot
perform a required file operation (open a file, close a file, read a
file, write to a file).
File not found: <filename>

Description: This message appears if FSC Navigator cannot find
any of the files that are required for downloading.
Force enable input not activated.

You attempted to force a variable, but the Force Enable key switch
has not been activated, which means that no force commands are
accepted. Forces are only allowed when this key switch is
activated.
Invalid destination address or system number not correct.

You tried to communicate with an FSC system that is loaded with a
different application and/or system number.
Load NOT successful. Press any key.

Downloading of the FSC program was not successfully completed
due to a communication error. Try again.
Load aborted due to disk file error. Press any key.

Check the surface of your hard disk and translate again.
Software Manual
Manual interrupt
Description: This message appears if the user has aborted the
download process by pressing the <Esc> key on the keyboard.
MEM - COM incompatible versions

You tried to download a file from a different application than the
CPU EPROMs/RAM, or the COM EPROMs are from another
application.
Module faulty <module>: <error code>

Description: This message appears if something went wrong with
the data transfer to the FSC system. This normally indicates a
faulty module. <Module> specifies the affected module (e.g.
CPU, COM1). <Error code> is a number that helps HSMS
engineers determine the exact nature of the fault.
No application files found. Translate first before choosing this

option.
You tried to run the download program, but no application files
(e.g. <Application name>.O11) were found on disk.
No Development System communication port configured for

<PC interface>
You tried to communicate via a communication port in the FSC
user station that has not been configured in the FSC system. For
example, the FSC user station uses RS-485, and FSC only has an
RS232 port, or vice versa.
No EPROMs programmed yet for COM module.

You tried to communicate with an FSC system for which no
communication EPROMs have been programmed yet.
No response from FSC system.

a) Check if the cable is plugged into the correct communication
port of the FSC user station and/or the FSC system.
b) Check if the EPROMs on the COM module have been placed
correctly. If that is the case, verify the EPROMs.
c) Check all modules on the system bus for correct EPROMs and
jumper settings.
Out of memory
Description: This message appears if FSC Navigator cannot
perform the download operation because the required memory is
not available.
Software Manual
Power-on modes in database and FSC system do not match.
Check if the power-on mode in the database is the same as in the
FSC system (RAM or EPROM mode).
Program communication EPROMs or wrong application files on

disk.
The communication EPROMs in the FSC system do not match the
application that you attempt to download. This will typically
happen in RAM mode if you have implemented modifications that
require the EPROMs to be reprogrammed, but you have not done
that. Make sure that you reprogram the communication EPROMs
before continuing.

installed.
If you use the 07177 interface modules to communicate with the
FSC system, a special communication driver needs to be installed
on the FSC user station. This driver has either not been installed, or
it has not been configured correctly (e.g. incorrect module address).
For details on the 07177 communication driver refer to section 2.3
of this manual.
Unable to start download

Description: This message appears if the download process cannot
be started. This will typically happen when the download matrix
contains any of the following states: No file, Not cfg'd, and Not
placed. With any software component in any of these states, the
FSC system would never be able to start up after a download, and
that is why no download is allowed. (The menu will not contain the
'Start' option.)
Software Manual
Software Manual
Fail Safe Control
Section 11:
Verifying an Application
Release 531
Revision 01 (03/2001)
© 2001– Honeywell Safety Management Systems B.V.
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 11: Verifying an Application
11.1 Introduction .................................................................................................. 11-1
11.2 Verification Process ..................................................................................... 11-3
11.3 Verification of FSC Application Using the FSC Database ......................... 11-5
11.4 Verification of FSC Application Software Using the Functional

Logic Diagrams ............................................................................................ 11-7
11.6 Error Messages .......................................................................................... 11-10

11.6.1 Introduction................................................................................................................... 11-10
11.6.2 Common Error Messages ............................................................................................ 11-10
11.6.3 Error Messages for Verification Using the FSC Database........................................... 11-13
11.6.4 Error Messages for Verification Using FLDs................................................................ 11-14
Software Manual
Section 11: Verifying an Application i
FIGURES
Figure 11-1 Example of verification output to screen ................................................................... 11-4

Figure 11-2 Verifying an application during OLM ......................................................................... 11-9
Software Manual
ii Section 11: Verifying an Application
Section 11 – Verifying an Application
11.1 Introduction
Verifying The 'Verify Application' option of FSC Navigator verifies if the FSC
an application application software as present in the FSC system is consistent with
the FSC database and the functional logic diagrams (FLDs) as stored
on the FSC user station.
The 'Verify Application' option can be called in three ways:
• Menu bar: On-Line / Verify Application

• Button bar: Verify
• Navigation area: FSC Safety Compliance / Verify Application
Differences between the application at the FSC user station and the
application software in the FSC system may be the result of:
1. changes made to the application at the FSC user station without
transferring the new application to the FSC system,
2. corruption of the FSC database or the functional logic diagrams
(FLDs), or
3. errors occurring in the complete path from configuring the
application to programming the FSC system EPROMs or
downloading the application.
Using the The 'Verify Application' option of FSC Navigator can be used in
verification option two ways:
• as a project verification tool, or
• as a Management Of Change (MOC) tool.
Project verification If used as a project verification tool, the verification option will
confirm that no translation or transfer faults have occurred to the FSC
application program. FSC Navigator will then compare the translated
application program as it is present in the FSC system with the FSC
databases and functional logic diagrams (FLDs) that are stored on the
FSC user station. This allows the user to verify that the defined
application program has been loaded correctly. This verification
process is part of the safety lifecycle as laid down in IEC 61508 and
ISA S84.01.
Software Manual
Section 11: Verifying an Application 11-1
Revision control As a Management Of Change (MOC) tool, the verification option is
used to compare different versions of the application programs in the
FSC system and the FSC user station (revision control). This option
is typically used to list all the differences (modifications) between the
'old' version, which is stored in the FSC system, and the 'new'
version, which is stored on the FSC user station. This method can be
used to check if all modifications have been implemented correctly.
Log file All differences found during the verification process are reported and
stored in a log file for later reference. The verification log file is
called <Application name>.VRF, and is located in the project folder.
It contains all messages and errors that were generated during the
verification process.
The verification log file can be viewed and printed using the 'View
Log' option of FSC Navigator (see Section 9 for details).
Conditions for The FSC application software can only be verified if the following
verification conditions are met:
• All functional logic diagrams of your application must have been
translated, i.e. the 'Translate Application' option of the FSC
Navigator must have been performed successfully.
• The FSC user station must be able to communicate with the FSC
system.
• An application must be present in the FSC system (programmed in
EPROMs or loaded into memory).
• The memory type of the FSC system and of the application at the
FSC user station must either be 'EPROM' or 'RAM'. Simulation
modes are not supported.
• The configuration of the FSC system must match the FSC
configuration as defined in the FSC database. In other words, you
cannot use a single (i.e. non-redundant) application to verify a
redundant FSC system and vice versa.
• There must be sufficient free disk space to store intermediate results
of the verification process. The required amount of disk space is
approximately the disk space needed to store the compiler output
(.Oxx and .Cxx files).
• The version of the application on the CPU module must match that
of the application on the COM module, i.e. the EPROMs of the
COM module must have been programmed at all times.
Software Manual
11-2 Section 11: Verifying an Application
11.2 Verification Process
Uploading the FSC To verify an application, the FSC application software as present in
application software the FSC system is first uploaded to the FSC user station. The FSC
to FSC user station application software is temporarily stored in the project folder, and
will be deleted when it is no longer needed.
The time required to upload the FSC application software depends on
the configuration, the size of the application and the baud rate of the
configured Development System communication protocol.
During communication, an asterisk (∗) is displayed in the upper right
corner of the screen. The progress of the upload function is visualized
by displaying a percentage counter for each file that is being uploaded
to the FSC user station.
Verification As soon as all FSC application software has been uploaded

process successfully, FSC Navigator will start verifying the application.
Verification of an application is divided into two steps:
1. Verification of the FSC application software with regard to the
information in the FSC database (see subsection 11.3).
2. Verification of the FSC application software with regard to the
functional logic diagrams (FLDs) (see subsection 11.4).
All differences that are found between the application stored at the
FSC user station and the FSC application software are reported and
logged in a verification log file.
Verification of an application can be terminated at any time by

pressing <Esc>. FSC Navigator will then report a manual interrupt,
and will write the time and date of interruption to the log file. If one or
more differences were found or if an error occurs that does not allow
further program execution, you are asked to press <Enter> to return to
the FSC Navigator main screen. If no differences were found, you will
automatically return to the FSC Navigator main screen.
Figure 11-1 below shows an example of the screen output during

verification of the FSC database. In the example shown, a difference
was found in the numerical SER configuration.
Software Manual
Figure 11-1 Example of verification output to screen
Note:
If you perform an on-line upgrade to FSC Release 530 from a
release prior to 510, sheet differences will be reported for all
functional logic diagrams (FLDs) that contain mathematical
routines, PIDs and/or equation blocks, even though no
modifications were implemented. This is normal behavior.
FSC R510 and higher use a different internal addressing scheme
than earlier releases, which causes the above sheet differences to
be reported.
Software Manual
11.3 Verification of FSC Application Using the FSC Database
Verification using This part of the verification process verifies the information in the
FSC database FSC database against the application software in the FSC system.
Verification of the FSC database is performed once for every Central
Part of the FSC configuration.
Any differences between the FSC database and the FSC application
software are logged in the log file and reported on screen (see Figure
11-1). Error messages are preceded by the word 'ERROR:', and they
explain the differences. They are shown in the color that has been set
for error text (red by default).The actual difference is displayed
highlighted (blue by default). The colors used depend on the color
settings of FSC Navigator. For details refer to Section 3 of this manual
("Using FSC Navigator").
If a difference is detected in a field that affects related information,

only this field is reported. For this reason, when you decide to correct
the difference and verify the application for the second time,
additional differences may be reported.
For example, if differences are detected in the characteristics of a
specific communication channel (protocol, interface, baud rate, etc.),
then only the protocol is reported. If the protocol is subsequently made
identical to the protocol as defined within the FSC system, the
interface and baud rate may be reported after a second verification.
Restrictions A number of items in the FSC databases are not verified.
Application database The following items in the application database are not verified:
1. If the interface of a communication channel is RS-485, the
program does not verify the network configuration in the FSC
database, which can be 'multidrop' or 'point-to-point.'
2. The program does not distinguish between the Development
System communication protocol and the Modem protocol.
3. The program does not verify which rack numbers are controlled
by which HBD.
4. The program does not verify any information regarding PSU or
PSD modules.
5. The program does not verify user-defined rack numbers.
6. The program does not verify the descriptive installation texts.
7. The program does not verify the maximum number of cabinets
and racks.
8. The program does not verify the number of slots on the Central
Part bus.
Software Manual
9. The program does not verify CPU and communication EPROM
types.
10. The program does not verify the maximum numerical SER
number.
11. The program does not verify the minimum and maximum FLD
execution times.
12. The program does not verify application names of the other FSC
systems connected to a network.
Note:
If a communication channel has been configured as a master
channel but no data is exchanged with its slave systems (which
means that the system actually serves as a communication
server), the program will report this as a difference.
Variables database The following items in the variables database are not verified:
1. The program does not verify service fields of register variables
(R), multiplexer variables (XI/XO) and binary input and output
variables (BI and BO).
2. The program will only verify the service and qualification fields
of input and output variables and marker variables if the
appropriate information is present in the FSC application
software.
3. The program does not verify any user-defined locations of
variables (non-reserved).
4. The program does not verify the signal type of variable types BI
and BO (BCD or normal).
5. The program does not verify the signal type of analog input
variables (AI).
6. The program does not verify strings that specify the engineering
units of several parameters.
7. The program does not verify top and bottom values of PID
variables.
Note:
The 'On-Line Environment' option of FSC Navigator can be
used to change the parameters of PID variables, the power-up
value of variables with location COM, etc. These new values are
stored in the FSC database. As long as the new values are not
transferred to the FSC system, the differences will be reported
by the 'Verify Application' option of FSC Navigator.
Software Manual
11.4 Verification of FSC Application Software Using the
Functional Logic Diagrams
Verification using After the contents of the FSC database have been verified, the
FLDs functional logic diagrams (FLDs) are verified.
All differences between the FLDs and the FSC application software
are displayed in red. If the connections on a functional logic diagram
do not match, the connection is further specified by a highlighted
description (blue by default). Any differences found will be output to
the screen and to the log file.
Restrictions The following items in the variable database are not verified:
1. The program does not verify the signal type of binary signals
(byte, word, long, or float).
Software Manual
11.5 Revision Control
Revision control The 'Verify Application' option of FSC Navigator is very useful as a
revision control tool to register the differences between various
versions of an application during application development or in case
of subsequent application updates.
This feature is available for both single-channel configurations and

redundant configurations.
Verifying changes If application software for use on any FSC system configuration is
modified, the 'Verify Application' option of FSC Navigator can be
used to register and verify the changes that were made. This is
accomplished by running the 'Verify Application' option of FSC
Navigator while the previous version of the application software is
still present in the FSC system.
FSC Navigator will then list all the differences (modifications)
between the 'old' version, which is stored in the FSC system, and the
'new' version, which is stored on the FSC user station.
On-line For redundant configurations, additional benefits are achieved when

modification the 'Verify Application' option of FSC Navigator is used during
on-line modification (OLM). During OLM, running the program only
once is sufficient to both verify the new application in one Central
Part and to register the differences with respect to the previous
version of the application.
When Central Part 1 has been loaded with a new version of the
application software while Central Part 2 is still running on the
previous version, the 'Verify Application' option of FSC Navigator
will perform the following two functions (see Figure 11-2 below):
• The program will verify that there are no differences between the
application software at the FSC user station and the application
software in Central Part 1. This is basically a verification of the
application software in Central Part 1. The sections in the log file
that refer to Central Part 1 should contain no differences, except for
the differences that pertain to the test data, which is used for
integrity purposes. (For details on test data, refer to the FSC Safety
Manual).
Software Manual
• The program will register the differences between the latest version
of the application software at the FSC user station and the previous
version of the software in Central Part 2. Therefore, for Central Part
2, the program operates as a revision control tool to register
differences between two versions of the application software. The
sections in the log file that refer to Central Part 2 should contain all
changes that were made with respect to the previous version of the
application software.
FSC
FSC user station
CP1
Appl. Version 2
CP2
Appl. Version 1
Verify Application
CP1 'No differences'
CP2
'Difference list'
Appl. Version 1 vs.
Appl. Version 2
Figure 11-2 Verifying an application during OLM
Software Manual
11.6 Error Messages
11.6.1 Introduction
Error messages This section lists the error messages that may be reported during the
verification process. All messages are preceded by the word
'ERROR:', except for the manual interrupt message.
No differences should be reported except for the differences as listed

in the FSC Safety Manual, unless the 'Verify Application' option of
FSC Navigator is used as a revision control tool (see subsection 11.5).
If any differences are reported, the application in the FSC system is
not consistent with the application at the FSC user station. In that case,
it is necessary to correct the differences at the FSC user station,
translate the application again, and reload it into the FSC system. The
'Verify Application' option should then report the proper differences
(see FSC Safety Manual).
11.6.2 Common Error Messages
Common error The following common error messages may be reported during the
messages verification process:
Application not translated. Translate application.

Description: The application must have been translated correctly
before it can be verified.
Corrupted data detected. Translate application.

Description: The FSC application software in the FSC system
contains data that does not allow further program execution.
Could not write to file <file name>

the specified file.
Software Manual
Could not create file <file name>
Description: An unsuccessful attempt was made to create the
specified file.
Could not open file <file name>

Description: An unsuccessful attempt was made to open the
specified file.
Could not read from file <file name>

the specified file.
Could not close file <file name>

Description: An unsuccessful attempt was made to close the
specified file.
Could not open log file.

Description: An unsuccessful attempt was made to open the log
file.
Could not write to log file.

the log file.
Could not close log file.

Description: An unsuccessful attempt was made to close the log
file.
CRC error in file <file name>

Description: An attempt was made to read from the specified file,
but the file was found to be corrupted.
Fatal error occurred during communication.

Description: Communication with FSC system is not possible.
Try again.
Note:
All errors that may be reported during the communication with
the FSC system are specified in Section 12 of this manual
("On-Line Environment").
File of illegal format: <file name>

Description: An attempt was made to read data from the specified
file, but the format of the file was not correct.
Software Manual
File of incorrect version: <file name>
Description: The program cannot continue since the version of the
specified file is not the same as the current program version.
FSC configuration in database and FSC system do not match.

Description: It is not possible to verify an application in an FSC
system whose configuration is not compatible with the database as
stored on the FSC user station.
Incorrect version of application software on CP, CPU :

<Central Part>, <CPU module>.
Description: The version of the FSC Navigator software that was
used to generate the FSC application software does not match the
current program version.
Incorrect version of communication EPROMs belonging to CP,

COM : <Central Part>, <COM module>.
Description: The version of the FSC Navigator software that was
used to generate and program the communication EPROMs does
not match the current program version.
No application present in FSC system.

Description: Verification of the application is not possible. The
application has not been downloaded yet.
Not enough disk space. Required additional space : <###> kB.

Description: There is not enough hard disk space to store the
temporary files that are required to successfully complete the
verification process.
Not enough memory.

Description: The program does not have enough memory to
proceed.
Program interrupted manually.

Description: You have interrupted the verification process by
pressing the <Esc> key.
Simulation mode not supported or illegal power-on mode.

Description: The application in the FSC system or the application
at the FSC user station has been configured for simulation mode, or
the power-on mode of the FSC system or the FSC user station is set
to an invalid value.
Software Manual
Variable not found in variables database: <variable>.
Description: A variable that was expected to be present in the
variables database could not be found.
11.6.3 Error Messages for Verification Using the FSC Database
Verification using The following error messages may be reported during the verification
FSC database process using the FSC database (in alphabetical order):
Application database contains <number> additional block

definition record(s).
Description: The application database contains more block
definition records than could be generated from the FSC
application software in the FSC system.
Application database record(s) that were not regenerated for CP

<CP no.>
Description: The application database contains more records than
could be generated from the FSC application software in the FSC
system. The lines that follow provide a list of application database
records that were not generated.
Illegal record number found in FSC application software.

Description: The generated record cannot be compared, since the
record number is out of range (the record is not present in the FSC
database).
Mismatching field(s) in block definition records:

Description: Differences were found between the RKE block
definition records in the application database and the FSC system.
The lines that follow specify where the differences were found, and
will contain the mismatching values.
Mismatching field(s) in regenerated application database:

Description: Differences were found between the application
database and the FSC system. The lines that follow specify which
differences were detected, and will contain the mismatching values.
Software Manual
Mismatching field(s) in regenerated variables database:
Description: Differences were found between the variables
database and the FSC system. The lines that follow specify where
the differences were found, and will contain the mismatching
values.
Missing block definition record in application database.

Description: Use the 'System Configuration' option of FSC
Navigator to modify the application or rebuild your databases (see
Section 4 of this manual).
Missing RKE block definition table.

Description: The records belonging to an RKE communication
channel cannot be regenerated since the specified table is not
present in the FSC application software.
Variables database record(s) that were not regenerated for CP

<CP no.>
Description: The variables database contains more records than
could be generated from the FSC application software in the FSC
system. The lines that follow provide a list of variables database
records that were not generated.
11.6.4 Error Messages for Verification Using FLDs
Verification using The following error messages may be reported during the verification
FLDs process using the FLDs (in alphabetical order):
Connection between symbols not found on FLD <FLD no.>:

From : <symbol>, output <#>
To : <symbol>, input <#>
Description: The specified connection generated from the FSC
application software is not present on the specified FLD.
Connection between symbols on FLD <FLD no.> has not been

regenerated:
From : <symbol>, output <#>
To : <symbol>, input <#>
Description: The specified connection on the specified FLD was
not generated from the FSC application software.
Software Manual
CRC error in FLD <FLD no.>
Description: The specified FLD in the project folder is corrupted.
Expected symbol not found. FLD number: <FLD no.>

Description: Internal storage error. This error should never occur.
FLD in application directory has not been regenerated. FLD

number: <FLD no.>
Description: The project folder contains more FLDs than could be
regenerated from the FSC application software in the FSC system.
Function block I/O data not found on original FLD <FLD no.>
Description: The original FLD is corrupted. Use the 'Design FLDs'
option of FSC Navigator to remedy the problem.
Function block I/O data not found on regenerated FLD <FLD no.>
Description: Internal storage error. This error should never occur.
Incorrect initialization of function block <FB> on FLD: <FLD

no.>
Description: The FSC application software to initialize the
specified function block, which is called on the specified FLD, is
missing, incomplete or incorrect.
Illegal instruction detected. FLD: <FLD no.>

Description: The FSC application software in the specified FLD
contains an illegal 68000 instruction.
Illegal bit number detected. FLD: <FLD no.>

Description: The bit address of a variable in the FSC application
software is illegal.
Illegal constant value detected. FLD: <FLD no.>

Description: A constant value in the specified FLD of the FSC
application software is out of range.
Illegal displacement detected. FLD: <FLD no.>

Description: The address of a variable in specified FLD of the
FSC application software is out of range.
Illegal equation table address detected: <FLD no.>

Description: The absolute address in the equation block in the
specified FLD of the FSC application software does not point to an
equation block table, or the format of the equation table is not
correct.
Software Manual
Illegal 32-bit address detected. FLD: <FLD no.>
Description: The absolute address of a variable in the specified
FLD of the FSC application software is out of range.
Illegal timer value detected. FLD: <FLD no.>

Description: The value of a timer variable in the specified FLD of
the FSC application software is out of range.
Illegal counter value detected. FLD: <FLD no.>

Description: The value of a counter variable in the specified FLD
of the FSC application software is out of range.
Illegal LPEC detected. FLD: <FLD no.>

Description: An illegal program execution in the FSC application
software has been detected in the specified FLD.
Incorrect type(s) of I/O to and from symbol <symbol>

Description: The signal types of the connections of a symbol do
not match. In most cases, the symbol will be a function block
symbol.
Mismatching equation table entries on FLD: <FLD no.>

Description: The specified equation table FLD as found in the
project folder contains entries that are different from the equation
table in the FSC application software in the FSC system.
Missing logic sequence at start of FLD: <FLD no.>

Description: The specified FLD does not start with the expected
program code.
Number of entries in equation table does not match for FLD:

<FLD no.>
Description: The specified equation table FLD as found in the
project folder does not contain the same number of entries as the
equation table in the FSC application software in the FSC system.
Regenerated FLD not found in application directory. FLD

number: <FLD no.>
Description: The project folder does not contain the FLD that was
regenerated from the FSC application software in the FSC system.
Regenerated symbol <symbol> not found on FLD <FLD no.>

Description: The specified symbol generated from the FSC
application software is not present on the specified FLD. (See note
below.)
Software Manual
Symbol <symbol> on FLD <FLD no.> has not been regenerated
Description: The specified symbol on the specified FLD was not
generated from the FSC application software. (See note below.)
Note:
The preceding two messages are usually reported
simultaneously as a result of only one difference. If, for
example, a constant value symbol with value 10 is generated for
FLD 100 while the value of the constant on the FLD is 20, the
following two messages will be reported:
− ERROR: Regenerated symbol CONSTANT VALUE 10 not
found on FLD 100.
− ERROR: Symbol CONSTANT VALUE 20 on FLD 100 has not
been regenerated.
This pair of messages will sometimes also be reported in
addition to other changes on that same FLD. Consider, for
example, an AND gate on FLD 39 that has two digital input
signals and one digital output signal. If, in the new application,
something changes about the inputs or outputs (e.g. one of the
inputs is removed), FSC Navigator may consider the AND gate
to be different (even though this is not true). This will then result
in the following two error messages (in addition to the messages
that specify the digital input and output symbol differences):
− ERROR: Symbol AND GATE on FLD 39 has not been
regenerated.
− ERROR: Regenerated symbol AND GATE not found on FLD
39.
Signal type of connection on FLD <FLD no.> does not match:

From :<symbol>, output <#>
To :<symbol>, input <#>
Description: The specified connection on the FLD is binary while
the connection generated from the FSC application software is
digital, or vice versa.
Software Manual
Type of symbol could not be determined. FLD number: <FLD
no.>
Description: 68000 code in FSC system cannot be converted to a
logic sequence of symbols.
This message means that there is a problem with the application
loaded into the FSC system. The specified FLD in the project
folder is most likely corrupted. This situation may occur if you
copy an FLD "outside" FSC Navigator (e.g. using Windows
Explorer) instead of using the 'Copy' command in the functional
logic editor (the 'Design FLDs' option of FSC Navigator). To solve
this problem, delete the FLD and redraw it from scratch, or use the
correct copy command.
Unexpected mnemonic found. FLD: <FLD no.>

Description: The program code of the specified FLD contains an
unexpected sequence of 68000 code.
Untranslatable code detected. FLD: <FLD no.>

Description: The FSC application software contains a sequence of
code that cannot be translated.
Symbol attributes The following differences and error messages address the attributes
of the different types of symbols (in alphabetical order). The
messages speak for themselves.
Counter value of symbol <symbol> does not match.
Incorrect number of inputs to symbol <symbol>
Incorrect number of outputs from symbol <symbol>
Regenerated symbol <symbol> on FLD <FLD no.> has no output

signals.
Regenerated symbol <symbol> on FLD <FLD no.> has no input

signals.
Register type of symbol <symbol> does not match.
Signal conversion of symbol <symbol> does not match.
Signal type of symbol <symbol> does not match.
Symbol <symbol> on FLD <FLD no.> has no output signals.
Software Manual
Symbol <symbol> on FLD <FLD no.> has no input signals.
Timer base of symbol <symbol> does not match.
Timer value of symbol <symbol> does not match.
Note:
If the specified symbol in one of the preceding messages is
followed by (FB <FLD no.> <sequence>), the symbol is an
internal variable belonging to function block <FLD no.> which
is used to initialize the function block.
Software Manual
Software Manual
Fail Safe Control
Section 12:
On-Line Environment
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 12: On-Line Environment

12.1 Introduction .................................................................................................. 12-1
12.1.1 Overview ........................................................................................................................ 12-1
12.1.3 On-Line vs. Off-Line Menu ............................................................................................. 12-3
12.1.4 Date and Time Format ................................................................................................... 12-4
12.2 Off-Line Menu ............................................................................................... 12-5
12.3 On-Line Menu ............................................................................................... 12-7
12.4 'FSC System' Menu .................................................................................... 12-11

12.4.1 Introduction................................................................................................................... 12-11
12.4.2 'Sys Info' Submenu....................................................................................................... 12-12
12.4.3 'Inputs' Submenu.......................................................................................................... 12-14
12.4.4 'Outputs' Submenu ....................................................................................................... 12-16
12.4.5 'Diag to Disk' Submenu ................................................................................................ 12-17
12.5 'Process Status' Menu ............................................................................... 12-19

12.5.1 Introduction................................................................................................................... 12-19
12.5.2 'FLD' Submenu............................................................................................................. 12-20
12.5.3 'Var Status' Submenu................................................................................................... 12-21
12.6 Selecting an Application to Monitor.......................................................... 12-23
12.7 Retrieving FSC System Information.......................................................... 12-24

12.7.1 Introduction................................................................................................................... 12-24
12.7.2 Viewing Configuration Parameters .............................................................................. 12-24
12.7.3 Viewing Software Version Information ......................................................................... 12-25
12.7.4 Reading the DBM Status.............................................................................................. 12-27
12.7.5 Setting the Real-Time Clock ........................................................................................ 12-29
12.7.6 Viewing Communication Statistics ............................................................................... 12-30
12.8 Monitoring the I/O Status........................................................................... 12-32

12.8.1 Introduction................................................................................................................... 12-32
12.8.2 Monitoring Individual Inputs and Outputs..................................................................... 12-32
12.8.3 Selecting an Input/Output by Position or Tag Number ................................................ 12-36
12.8.4 Viewing 'High' or 'Low' Inputs....................................................................................... 12-38
12.8.5 Monitoring Inputs for Status Changes.......................................................................... 12-39
12.9 Monitoring the Process and Variable Status ............................................ 12-40

12.9.1 Introduction................................................................................................................... 12-40
12.9.2 Monitoring the Status of FLDs...................................................................................... 12-41
12.9.3 Monitoring the Status of All Variables in an FLD ......................................................... 12-45
12.9.4 Monitoring the Status of Selected Variables ................................................................ 12-47
12.9.5 Monitoring the Status of Variables by Type ................................................................. 12-49
12.9.6 Working with Variable Status Screens ......................................................................... 12-50
12.9.7 Rebuilding the Screen File ........................................................................................... 12-51
Software Manual
Section 12: On-Line Environment i
12.10 Viewing the I/O Loop Status ...................................................................... 12-53

12.10.1 Loop Status for the Entire Application.......................................................................... 12-53
12.10.2 Loop Status for the Selected Central Part.................................................................... 12-55
12.11 Forcing Inputs and Outputs....................................................................... 12-57

12.11.1 Introduction................................................................................................................... 12-57
12.11.2 Setting a Force ............................................................................................................. 12-57
12.11.3 Clearing Individual Forces............................................................................................ 12-60
12.11.4 Clearing All Forces ....................................................................................................... 12-62
12.11.5 Listing the Forced Variables......................................................................................... 12-62
12.12 Writing to Inputs and Outputs ................................................................... 12-64
12.13 Calibrating Analog Inputs and Outputs .................................................... 12-66

12.13.1 Calibrating Analog Inputs ............................................................................................. 12-66
12.13.2 Calibrating Analog Outputs .......................................................................................... 12-70
12.14 Working with PIDs ...................................................................................... 12-72

12.14.1 Viewing the PID Status................................................................................................. 12-72
12.14.2 Adjusting PIDs.............................................................................................................. 12-75
12.15 Working with System Diagnostics ............................................................ 12-78

12.15.1 Introduction................................................................................................................... 12-78
12.15.2 Retrieving Diagnostics from the FSC System .............................................................. 12-79
12.15.3 Selecting the FSC System(s) for Diagnostics Retrieval............................................... 12-81
12.15.4 Retrieving Diagnostics Continuously............................................................................ 12-82
12.15.5 Reading Diagnostic Information from Hard Disk.......................................................... 12-83
12.15.6 Backing Up the Diagnostics Message File................................................................... 12-84
12.16 Extended Diagnostic Messages ................................................................ 12-86

12.16.1 Introduction................................................................................................................... 12-86
12.16.2 Messages Not Related to Specific Hardware Modules................................................ 12-87
12.16.3 Vertical Bus Drivers (10001/1/1, 10001/R/1)................................................................ 12-91
12.16.4 Central Processing Units (10002/1/2, 10012/1/2, 10020/1/1) ...................................... 12-92
12.16.5 Communication Modules (10004/./., 10014/./., 10024/./., 10008/2/U,
10008/3/P, 10018/2/U) ................................................................................................. 12-94
12.16.6 PlantScape Interface Modules (10018/E/E, 10018/E/1) .............................................. 12-97
12.16.7 Watchdog Modules (10005/1/1) ................................................................................... 12-98
12.16.8 Diagnostic and Battery Modules (10006/./.) ................................................................. 12-99
12.16.9 Single Bus Drivers (10007/1/1) .................................................................................... 12-99
12.16.10 Horizontal Bus Drivers (10100/./.) .............................................................................. 12-100
12.16.11 Digital Input Modules 10101/./.................................................................................... 12-100
12.16.12 Analog Input Modules 10102/./. ................................................................................. 12-101
12.16.13 Analog Input Module 10105/2/1 ................................................................................. 12-101
12.16.14 Digital Input Module 10106/2/1 .................................................................................. 12-102
12.16.17 Analog Output Modules 10205/./................................................................................ 12-104
Software Manual
ii Section 12: On-Line Environment
12.16 Extended Diagnostic Messages (continued)

12.16.23 Watchdog Repeater Modules (10302/./.) ................................................................... 12-108
12.17 Error Messages ........................................................................................ 12-109
Software Manual
Section 12: On-Line Environment iii
FIGURES
Figure 12-1 FSC On-Line Environment screen ............................................................................ 12-2

Figure 12-2 Button in FSC On-Line Environment screen (with submenu) ................................... 12-3
Figure 12-3 Current date and time in on-line screen.................................................................... 12-4
Figure 12-4 Date format setting in Control Panel ......................................................................... 12-4
Figure 12-5 Off-line menu............................................................................................................. 12-5
Figure 12-6 On-line menu: main menu......................................................................................... 12-7
Figure 12-7 On-line environment menu structure (part 1) ............................................................ 12-8
Figure 12-8 On-line environment menu structure (part 2) ............................................................ 12-9
Figure 12-9 On-line menu: FSC system ..................................................................................... 12-11
Figure 12-10 On-line menu: system information .......................................................................... 12-12
Figure 12-11 Diagnostics button with System Information option ................................................ 12-12
Figure 12-12 On-line menu: inputs ............................................................................................... 12-14
Figure 12-13 I/O Signal Status button with Inputs option ............................................................. 12-14
Figure 12-14 On-line menu: sequential inputs.............................................................................. 12-15
Figure 12-15 On-line menu: all inputs .......................................................................................... 12-15
Figure 12-16 On-line menu: outputs............................................................................................. 12-16
Figure 12-17 I/O Signal Status button with Input option............................................................... 12-16
Figure 12-18 On-line menu: sequential outputs ........................................................................... 12-17
Figure 12-19 On-line menu: diagnostics to disk ........................................................................... 12-17
Figure 12-20 Diagnostics button with Diagnostics To Disk option ............................................... 12-18
Figure 12-21 On-line menu: process status ................................................................................. 12-19
Figure 12-22 On-line menu: FLD status ....................................................................................... 12-20
Figure 12-23 Process Status Monitoring button with Monitor FLDs option .................................. 12-20
Figure 12-24 On-line menu: variable status ................................................................................. 12-21
Figure 12-25 Process Status Monitoring button with Variable Status option ............................... 12-21
Figure 12-26 Selecting an application .......................................................................................... 12-23
Figure 12-27 Viewing the system parameters .............................................................................. 12-25
Figure 12-28 Viewing software version information ..................................................................... 12-26
Figure 12-29 Status of diagnostic and battery module (DBM) ..................................................... 12-28
Figure 12-30 Viewing the FSC-FSC communication statistics..................................................... 12-30
Figure 12-31 I/O Signal Status button with Inputs option ............................................................. 12-32
Figure 12-32 Selecting an input or output for monitoring ............................................................. 12-33
Figure 12-33 Example of I/O status screen .................................................................................. 12-34
Figure 12-34 Selecting an input or output by position .................................................................. 12-36
Figure 12-35 Selecting an input or output by tag number ............................................................ 12-37
Figure 12-36 Listing all high inputs............................................................................................... 12-39
Figure 12-37 Process Status Monitoring button with Monitor FLDs option .................................. 12-41
Figure 12-38 Monitoring the status of an FLD .............................................................................. 12-42
Figure 12-39 Process Status Monitoring button with Variable Status option ............................... 12-45
Figure 12-40 Monitoring the status of all variables in an FLD ...................................................... 12-46
Figure 12-41 Monitoring the status of variables in a user-defined screen ................................... 12-47
Figure 12-42 Monitoring the status of variables by type............................................................... 12-49
Figure 12-43 Editing a status screen............................................................................................ 12-50
Figure 12-44 Diagnostics button with I/O Loop Diagnostics option.............................................. 12-53
Figure 12-45 Viewing the I/O loop status ..................................................................................... 12-54
Figure 12-46 Forcing an analog input........................................................................................... 12-59
Figure 12-47 Display of a forced variable in the I/O status screen............................................... 12-59
Figure 12-48 Display of a forced variable in a 'live' FLD .............................................................. 12-60
Figure 12-49 Display of a forced variable in a variables status screen........................................ 12-60
Figure 12-50 Process Status Monitoring button with List Forces option ...................................... 12-62
Software Manual
iv Section 12: On-Line Environment
FIGURES (continued)
Figure 12-51 Listing all forces in the system ................................................................................ 12-63

Figure 12-52 Calibrating analog inputs (zero + span) .................................................................. 12-67
Figure 12-53 Location of potentiometers on the 10102/./. module............................................... 12-67
Figure 12-54 Calibrating analog inputs (test value)...................................................................... 12-69
Figure 12-55 Location of potentiometers on the 10205/1/1 module............................................. 12-71
Figure 12-56 Viewing and editing a PID ....................................................................................... 12-72
Figure 12-57 Adjusting PID parameters ....................................................................................... 12-76
Figure 12-58 Diagnostics button with Extended Diagnostics option ............................................ 12-79
Figure 12-59 Viewing the extended diagnostic information ......................................................... 12-80
Figure 12-60 Selecting the FSC system(s) for diagnostics retrieval ............................................ 12-81
TABLES
Table 12-1 Loop status errors (entire application) .................................................................... 12-54

Table 12-2 Loop status errors (for selected Central Part)......................................................... 12-56
Software Manual
Section 12: On-Line Environment v
Software Manual
vi Section 12: On-Line Environment
Section 12 – On-Line Environment
12.1 Introduction
12.1.1 Overview
On-line The 'On-Line Environment' option of FSC Navigator is a powerful

environment tool for interaction between the FSC user station and the FSC system.
It allows you to obtain valuable information on the status of your
process and the FSC system. It is also a useful tool in case of
problems. You can do any of the following:
• retrieve status information from the FSC system (see subsection
12.7 on page 12-24),
• monitor the status of inputs and outputs (see subsection 12.8 on
page 12-32),
• monitoring the status of the process and variables (see subsection
12.9 on page 12-40),
• viewing the status of I/O loops (see subsection 12.10 on page
12-53),
• forcing inputs and outputs (see subsection 12.11 on page 12-57),
• writing to inputs and outputs (see subsection 12.12 on page 12-64),
• calibrating analog inputs and outputs (see subsection 12.13 on page
12-66),
• viewing the status of PIDs and modify their parameters (see
subsection 12.14 on page 12-72), and
• display and store system diagnostics (see subsections 12.15 and
12.16 on pages 12-78 and 12-86, respectively).
The on-line environment main menu of FSC Navigator can be called

in three ways:
• Menu bar: On-Line / Monitor System

• Button bar: Monitor
• Navigation area: FSC On-Line Environment screen
(see Figure 12-1)
Software Manual
Section 12: On-Line Environment 12-1
12.1.2 FSC On-Line Environment Screen
On-line The FSC On-Line Environment screen (see Figure 12-1 below)
environment provides a number of shortcuts to specific functions.
Figure 12-1 FSC On-Line Environment screen
• Process Status Monitoring / Monitor FLDs

Use this option to view the on-line status of the variables in the
FLDs of the current FSC project (see subsection 12.9.2).
• Process Status Monitoring / Variable Status
Use this option to view the on-line status of the variables used in the
FSC system (see subsection 12.9.3).
• Process Status Monitoring / List Forces
Use this option to view a list of all forced variables in the FSC
system (see subsection 12.11.5).
Software Manual
12-2 Section 12: On-Line Environment
• I/O Signal Status
Use this option to view the status of the input/output loops. This
menu option has a submenu which allows you to choose which
loops you wish to view (see subsection 12.8).
• Diagnostics / Extended Diagnostics
Part(s) in the FSC system (see subsection 12.15).
• Diagnostics / Diagnostics to Disk
Use this option to back up the extended diagnostic database to hard
disk or retrieve a previously stored database (see subsection 12.15).
• Diagnostics / I/O Loop Diagnostics
Use this option to view all diagnostics of the I/O loops in the FSC
system (see subsection 12.10).
• Diagnostics / System Information
Use this option to view important system parameters of the FSC
system (see subsection 12.7).
Figure 12-2 Button in FSC On-Line Environment screen

(with submenu)
12.1.3 On-Line vs. Off-Line Menu
Communication As soon as any of the on-line functions of FSC Navigator is called,

FSC Navigator will read all required data files from your hard disk
and try to establish a communication link with the FSC system.
If a communication link was established successfully, you will see the
on-line menu (see subsection 12.3). If setting up a communication link
failed, the off-line menu will appear (see subsection 12.2).
Software Manual
12.1.4 Date and Time Format
Date and Several on-line screens show the current date and time in the top
time format right-hand corner (see Figure 12-3). The date and time format used
depends on the Regional Settings as laid down in the Windows
NT/2000 Control Panel (see Figure 12-4).
Figure 12-3 Current date and time in on-line screen
Figure 12-4 Date format setting in Control Panel
Note:
FSC Navigator will always display the century indicator, even if
you do not specify it in Regional Settings. This means that if
you set the year to 'yy' (i.e. without century indicator), the date
will still show '2000' rather than '00'.
Software Manual
12.2 Off-Line Menu
Off-line menu If no communication link could be successfully established with the

FSC system, the following message will be displayed:
Check connection with FSC system. Press <Enter> for
communication retry or 'C' to enter the off-line menu.
If you press <Enter>, FSC Navigator will try to establish
communication again. If you press <C>, the off-line menu will appear
(see Figure 12-5). The options in this menu allow you to perform a
number of off-line tasks.
MAIN
Retrieve diag Edit screen rebuild Screenfile eXit
Figure 12-5 Off-line menu
Common causes for unsuccessful communication are:

• The communication cables are not properly connected.
• The incorrect COM port has been selected. (To change the COM
port, choose the Communication Port option from the On-Line
menu in FSC Navigator's main screen.)
• The application in the FSC system is not the same as the project that
is currently open in FSC Navigator.
• The communication channel has not been configured properly
(e.g. incorrect protocol).
Retrieve diag This option allows you to retrieve and display extended diagnostic
data that is stored on disk. For details refer to subsection 12.17.5.
Edit screen This option allows you to edit the status screens that were defined
earlier. Screens can contain up to 32 FSC variables or 8 PID
controllers whose values are continuously updated on screen. For
details refer to subsection 12.9.6.
Software Manual
rebuild Screenfile This option allows you to rebuild your screen file according to the
current database in case it has changed. For details refer to subsection
12.9.7.
eXit Choose this option to return to the main FSC Navigator screen.
Software Manual
12.3 On-Line Menu
On-line If the communication link with the FSC system was established
main menu successfully, the on-line main menu will appear, which has the
MAIN
Fsc system Process status select Application Modem eXit
Figure 12-6 On-line menu: main menu
Several menu options have submenus. Figure 12-7 and Figure 12-8
show the entire menu structure of FSC Navigator's on-line
environment.
Fsc system If you choose 'Fsc system' in the on-line main menu, a new menu will
open that allows you to retrieve status information on the FSC
system. For details refer to subsection 12.4.
Process status If you choose 'Process status' in the on-line main menu, a new menu
will open that allows you to retrieve status information on the process
that the FSC system is controlling. You can also change the status of
the variables by performing force or write commands to the variables.
select Application If you choose 'select Application' in the on-line main menu, you can
switch to another FSC system that is also a part of the configured
FSC network. This allows you to select another application to
communicate with, without leaving the on-line environment of FSC
Navigator. For details refer to subsection 12.6.
Modem If you choose 'Modem' in the on-line main menu, you can establish a
connection with the FSC system via a modem. For details refer to
section F.10 of this manual. Please note that this option will only be
available if a modem channel has been defined in the application.
eXit If you choose this option, you will return to the main FSC Navigator
screen.
Software Manual
On-line menu
Fsc system Sys info Parameters
Process status Versions
select Application Read DBM status
Modem Set real time
eXit COM statistics
Main
Inputs Sequential Force
Calibration Position
Tag number
Clr force
Main
All High input
Loop status Low input
Main Test changes
Main
Outputs Sequential Force
Extended diag Calibration Position
Loop status Tag number
Main Clr force
Diag to disk Backup Main
Main cOnfig
Continuous
Retrieve
Main
Figure 12-7 On-line environment menu structure (part 1)

Software Manual
On-line menu
Fsc system
Process status FLD New FLD
Tag number
Force
Clear
Write
Zoom
Main
select Application Var status FLD
lIst forces sCreen
Clr all forces Var type
Loop status Edit pid
Main Adjust pid
Modem Rebuild scrnfile
eXit Main
Figure 12-8 On-line environment menu structure (part 2)
Software Manual
are meaningful. For example, the menu option Fsc system \ Sys info \
Read DBM status will only be only available if a Diagnostic and
Battery Module (DBM) has been placed in the FSC system.
Activating The on-line environment of FSC Navigator is entirely menu-driven.

menu options The menus are placed on the bottom line of the screen. The menus
can be accessed using the keyboard. Menu options can be activated in
two ways:
• Press the highlighted letter of the menu option. For example, to
activate the 'select Application' command, you should press the
<A> key.
If you press <Esc> at any time, you will go back to the menu of the
next highest level.
Software Manual
12.4 'FSC System' Menu
12.4.1 Introduction
'Fsc system' If you choose 'Fsc system' in the on-line main menu, a new menu will
menu open that allows you to retrieve on-line status information about the
FSC system. It has the following menu items:
MAIN
Fsc system
Sys info Inputs Outputs Extended diag Diag to disk Main
Figure 12-9 On-line menu: FSC system
Sys info If you choose this option, a new menu will open that allows you to
perform a number of on-line system tasks. For details refer to
subsection 12.4.2.
Inputs If you choose this option, a new menu will open that allows you to
monitor one or more hardware inputs. For details refer to subsection
12.4.3.
Outputs If you choose this option, a new menu will open that allows you to
monitor one or more hardware outputs. For details refer to subsection
12.4.4.
Extended diag Choose this option to view on-line diagnostics that are generated in
the running FSC system (see subsection 12.15.2).
Diag to disk If you choose this option, a new menu will open that allows you to
work with diagnostics on your hard disk. For details refer to
subsection 12.4.5.
Main Choose this option to go back to the main menu.
Software Manual
12.4.2 'Sys Info' Submenu
'Sys info' The Sys info submenu provides a number of options that allow you to
submenu retrieve basic system information and view it on screen. This
submenu has the following menu items:
Fsc system
Sys info
Parameters Versions Read DBM status Set real time COM statistics Main
Figure 12-10 On-line menu: system information
There is a shortcut to the 'Sys Info' menu. In the FSC On-Line

Environment screen, choose the Diagnostics button and then the
System Information option (see Figure 12-11).
Figure 12-11 Diagnostics button with System Information option
Parameters Choose this option to view the configuration parameters of the

running FSC system (see subsection 12.7.2).
Version Choose this option to view the versions of the embedded software in
the FSC system components (see subsection 12.7.3).
Read DBM status Choose this option to read the current status of the diagnostic and
battery module (DBM) (see subsection 12.7.4).
Set real time Choose this option to set the real-time clock of the FSC system
Software Manual
COM statistics Choose this option to view the statistics of the communication
channels in the selected Central Part (see subsection 12.7.6).
Software Manual
12.4.3 'Inputs' Submenu
'Inputs' The Inputs submenu provides a number of options that allow you to
submenu retrieve on-line information on digital and analog inputs and view it
on screen. This submenu has the following menu items:
Fsc system
Inputs
Sequential Calibration All Loop status Main
Figure 12-12 On-line menu: inputs
There is a shortcut to the 'Inputs' menu. In the FSC On-Line

Environment screen, choose the I/O Signal Status button and then
the Inputs option (see Figure 12-13).
Figure 12-13 I/O Signal Status button with Inputs option
Sequential Choose this option to display on-line status information about a

specific hardware input (see subsection 12.8).
Calibration Choose this option to calibrate an analog input (see subsection 12.13).
All Choose this option to display on-line information about a group of

hardware inputs that meet certain selection criteria (see subsection
12.8).
Loop status Choose this option to view the loop status of all inputs in the selected
Central Part (see subsection 12.10.2).
Software Manual
'Sequential' The Sequential submenu provides a number of options that allow
submenu you to display on-line status information about a specific hardware
input. This submenu has the following menu items:
Sequential
Force Position Tag number Clr force Main
Figure 12-14 On-line menu: sequential inputs
Force Choose this option to force the selected input variable to a certain
value (see subsection 12.11.2).
Position Choose this option to select an input variable based on its rack
position (see subsection 12.8.3).
Tag number Choose this option to select an input variable based on its tag number
Clr force Choose this option to clear the forced status of the selected input
variable (see subsection 12.11.3).
'All' submenu The All submenu provides a number of options that allow you to
display on-screen status information about a group of hardware input
that meet certain selection criteria. This submenu has the following
menu items:
All
High input Low input Test changes Main
Figure 12-15 On-line menu: all inputs
High input Choose this option to display on-line status information for all
variable whose status is 'not low' (see subsection 12.8.4).
Low input Choose this option to display on-line status information for all
variable whose is status 'low' (see subsection 12.8.4).
Test changes Choose this option to display on-line status information of variables
as soon as their status changes (see subsection 12.8.5).
Software Manual
12.4.4 'Outputs' Submenu
'Outputs' The Outputs submenu provides a number of options that allow you
submenu to retrieve on-line information on digital and analog outputs. This
submenu has the following menu items:
Fsc system
Outputs
Sequential Calibration Loop status Main
Figure 12-16 On-line menu: outputs
There is a shortcut to the 'Outputs' menu. In the FSC On-Line

Environment screen, choose the I/O Signal Status button and then
the Outputs option (see Figure 12-13).
Figure 12-17 I/O Signal Status button with Input option
Sequential Choose this option to display on-line information about a specific

hardware output (see subsection 12.8).
Calibration Choose this option to calibrate an analog output (see subsection

12.13).
Loop status Choose this option to view the loop status of all outputs in the
selected Central Part (see subsection 12.10.2).
Software Manual
'Sequential' The Sequential submenu provides a number of options that allow
submenu you to display on-line information about a specific hardware input.
This submenu has the following menu items:
Sequential
Force Position Tag number Clr force Main
Figure 12-18 On-line menu: sequential outputs
Force Choose this option to force the selected output variable to a certain
Position Choose this option to select an output variable based on its rack
position (see subsection 12.8.3).
Tag number Choose this option to select an output variable based on its tag
number (see subsection 12.8.3).
Clr force Choose this option to clear the forced status of the selected output
variable (see subsection 12.11.3).
12.4.5 'Diag to Disk' Submenu
Diag to Disk The Diag to disk submenu provides a number of options that allows
submenu you to work with diagnostics on your hard disk. This submenu has
the following menu items:
Fsc system
Diag to disk
Backup cOnfig Continuous Retrieve Main
Figure 12-19 On-line menu: diagnostics to disk
Software Manual
The 'Diag to disk' submenu has two shortcuts:
• Menu bar: On-Line / Diagnostics To Disk

• Navigation area: FSC On-Line Environment / Diagnostics /
Diagnostics To Disk (see Figure 12-20)
Figure 12-20 Diagnostics button with Diagnostics To Disk option
Backup Choose this option to back up stored extended diagnostic data (see
subsection 12.15.6).
cOnfig Choose this option to select the FSC system(s) that should be polled
for diagnostic data (see subsection 12.15.3).
Continuous Choose this option to continuously poll the selected FSC system(s)
for diagnostic data and write the data to hard disk (see subsection
12.15.4).
Retrieve Choose this option to retrieve and display extended diagnostic data
that is stored on your hard disk (see subsection 12.15.5).
Software Manual
12.5 'Process Status' Menu
12.5.1 Introduction
'Process status' If you choose 'Process status' in the on-line main menu, a new menu
menu will open that allows you to retrieve status information on the process
that the FSC system is controlling. You can also change the status of
the variables by performing force or write commands to the variables.
The 'Process status' menu has the following menu items:
MAIN
Process status
Fld Var status lIst forces Cir all forces Loop status Main
Figure 12-21 On-line menu: process status
FLD If you choose this option, a new menu will open that allows you to
monitor signals on functional logic diagrams (FLDs). For details refer
to subsection 12.5.2.
Var status If you choose this option, a new menu will open that allows you to
display the status of variables used in the FSC system. For details
refer to subsection 12.5.3.
lIst forces Choose this option to display an overview of all variables in the FSC
system that have been forced (see subsection 12.11.5).
Clr all forces Choose this option to remove the forced status of all variables in the
FSC system that have been forced (see subsection 12.11.4).
Loop status Choose this option to display the status of I/O loops in the entire
Software Manual
12.5.2 'FLD' Submenu
'FLD' The FLD submenu provides a number of options that allow you to
submenu monitor the status of all signals present on a selected functional logic
diagram. This submenu has the following menu items:
Process status
FLD
New Fld Tag number Force Clear Write Zoom Main
Figure 12-22 On-line menu: FLD status
The 'FLD' submenu has two shortcuts:
• Menu bar: On-Line / Monitor FLDs

• Navigation area: FSC On-Line Environment / Process Status
Monitoring / Monitor FLDs (see Figure 12-23)
Figure 12-23 Process Status Monitoring button with

Monitor FLDs option
New FLD Choose this option to select a new FLD whose signals you wish to
monitor (see subsection 12.9.2).
Tag number Choose this option to select a signal to be monitored based on its tag
number (see subsection 12.9.2).
Force Choose this option to force a signal on the monitored FLD to a fixed
Software Manual
Clear Choose this option to clear the force of a signal on the monitored
FLD (see subsection 12.11.3).
Write Choose this option to write to a specific signal in the monitored FLD
(see subsection 12.12).
Zoom Choose this option to scale the current FLD in such a way that it can
be displayed on your screen. Please note that this option is only active
if the size of the FLD is too big to be displayed on your screen
(depending on the symbol library used) (see subsection 12.9.2).
12.5.3 'Var Status' Submenu
Variable status The Var status submenu provides a number of options that allow you
submenu to display the status of specific FSC variables. This submenu has the
Process status
Var status
Fld sCreen Var type Edit pid Adjust pid Rebuild scrnfile Main
Figure 12-24 On-line menu: variable status
There is a shortcut to the 'Var status' option. In the FSC On-Line

Environment screen, choose the Process Status Monitoring button
and then the Variable Status option (see Figure 12-25).

Variable Status option
Software Manual
FLD Choose this option to open a status screen that shows the status of all
variables in an FLD (see subsection 12.9.3).
sCreen Choose this option to open a status screen that shows the status of a
user-defined group of FSC variables (see subsection 12.9.4).
Var type Choose this option to open a status screen that shows the status of
variables of a particular type (see subsection 12.9.5).
Edit pid Choose this option to view or edit the PID control parameters in the
FSC system (see subsection 12.14.1).
Adjust pid Choose this option to adjust the PID values in the FSC system (see
subsection 12.14.2).
Rebuild screenfile Choose this option to rebuild the screen file in accordance with the
current FSC database (see subsection 12.9.7).
Software Manual
12.6 Selecting an Application to Monitor
Selecting an If you enter the on-line environment of FSC Navigator, the program
application will use the current application. You can use the 'select Application'
option from the on-line main menu to switch communication to
another FSC system that is also part of the configured FSC system or
network. This allows you to switch between FSC systems without
having to leave the on-line environment.
If you choose this option, FSC Navigator will display a popup window
containing a list of all the applications that are present on your hard
disk. The screen will look something like this:
Figure 12-26 Selecting an application
To select an application, use the arrow keys to move the cursor bar to
the application you wish to communicate with, and press <Enter> to
confirm. FSC Navigator will now try to establish communication with
the selected system.
Software Manual
12.7 Retrieving FSC System Information
12.7.1 Introduction
FSC system FSC Navigator offers a number of options to retrieve system

information information on the running FSC system. You can do the following:
• View configuration parameters (see subsection 12.7.2),
• View the versions of the embedded software components (see
subsection 12.7.3),
• Read the status of the diagnostic and battery module (DBM) (see
subsection 12.7.4), and
• Set the system's real-time clock (see subsection 12.7.5).
Each of these options is discussed in more detail below.
12.7.2 Viewing Configuration Parameters
FSC configuration To view the configuration parameters of the running FSC system,
parameters choose the following menu options:
Fsc system Sys info Parameters
The screen as shown in Figure 12-27 will appear. It shows a number

of important configuration parameters of the running system,
including the requirement class, Central Part configuration, process
safety time, and the power-on mode. You cannot edit anything in this
screen; it is for information purposes only.
Software Manual
Figure 12-27 Viewing the system parameters
12.7.3 Viewing Software Version Information
Software version To view version information for the running FSC system, choose the
information following menu options:
Fsc system Sys info Versions
The screen as shown in Figure 12-28 will appear. You cannot edit
anything in this screen; it is for information purposes only.
Note:
If you want to view version information of the FSC Navigator
software components, you should choose the About option from
the Help menu in the main FSC Navigator screen.
Software Manual
Figure 12-28 Viewing software version information
This screen provides version information for each CPU module and
COM module in the system. The following information is provided:
System software This field shows the version of the module's system software, which
version defines the functionality of the module at a system level, e.g. ability
to handle communication requests.
Current application This field shows the version of the actual safety application program
version that is currently present in the FSC system. The version number refers
to the number of times that the application has been translated. Please
note that the version counter is also incremented by one when an
application is converted from a previous FSC release.
CRC-32 of application This field shows the checksum of the application program, which is
program used to guarantee the integrity of the program.
Channel A / Channel B These fields show the communication protocol that is used for each
channel of a COM module, as well as its driver version.
Software Manual
Note:
The version of the FSC Safety Manager Module (FSC-SMM,
100x8/2/U) is only displayed if the Safety Manager firmware is
v2.1 or higher. If the firmware version is older, the window will
show that an FSC Safety Manager Module is present, but will
not indicate its firmware version. The FSC-SMM firmware
version can also be retrieved from the TPS Universal Station (at
the VERS/REV detail display).
12.7.4 Reading the DBM Status
DBM status To read the status of the diagnostic and battery module (DBM),
Fsc system Sys info Read DBM status
Notes:
1. This menu option is only available if a Diagnostic and
Battery Module (10006/./.) has been placed in the FSC
system.
2. For technical details on the DBMs refer to their data sheets.
The screen as shown in Figure 12-29 will appear. You cannot edit
anything in this screen; it is for information purposes only. The
following information is displayed in the screen, which is updated
continuously:
Current date and time The date and time format used on the DBM status display depends on
the Regional Settings as laid down in the Windows NT/2000 Control
Panel.
Battery voltage S-xx bus This is the voltage level of the bus that the DBM is connected to.
Battery voltage of DBM This is the charge voltage level of the backup batteries on the DBM.
Supply voltage This is the actual voltage level that comes directly from the 5 Vdc
power supply (10300/1/1).
Temperature 1 This is the temperature that is measured inside the Central Part by the
first sensor on the DBM.
Software Manual
Figure 12-29 Status of diagnostic and battery module (DBM)
Temperature 2 This is the temperature that is measured inside the Central Part by the
second sensor on the DBM.
FSC operational time The FSC operational time is the time that the FSC system has been
controlling and safeguarding your process without a shutdown.
Note:
After each power-up of the FSC system, the time setting should
be checked and corrected, if necessary.
Software Manual
12.7.5 Setting the Real-Time Clock
Setting the
real-time clock You can set the real-time clock of the FSC system in two ways:
• By pressing <S> in the DBM status screen (see Figure 12-29), or
• By choosing the following menu options:
Fsc system Sys info Set real time
This will open a screen in which you can enter the new date and time.
After you have adjusted the time and date, you will automatically go
(back) to the DBM status screen (see Figure 12-29)
Notes:
1. You can only set the real-time clock if the FSC user station
can issue time synchronization commands. If any time
synchronization sources of a higher hierarchy level are
available (e.g. DCF-77 or a DCS), you can change the time
settings, but they will not take effect. For details on time
synchronization refer to Appendix F of this manual
("Communication").
2. After each power-up of the FSC system, the time setting
should be checked and corrected, if necessary.
Software Manual
12.7.6 Viewing Communication Statistics
Communication You can view communication statistics of all communication

statistics channels in the selected Central Part, which is a helpful tool for
maintenance and troubleshooting purposes.
To view the statistics, choose the following menu options:
Fsc system Sys info COM statistics
The screen as shown in Figure 12-30 below will appear.
Important!
Non-zero values in this screen do not necessarily indicate
problems! The numbers merely provide information on certain
communication parameters.
It is normal behavior for the counters to increment at a rate of up
to 3 per hour.
Figure 12-30 Viewing the FSC-FSC communication statistics
Software Manual
You cannot edit anything in this screen as it is for information
purposes only. The screen shows all communication channels in the
selected Central Part, together with their communication statistics.
The screen is updated continuously.
Statistics shown The following information is displayed in the screen:
Chan This is the communication channel of the selected Central Part that is
being monitored. Each channel is identified by the number of the
communication module and the channel letter. For example, '1,A'
refers to channel A of communication module 1 in the selected
Central Part.
Protocol This is the communication protocol that is used for the specified
channel.
DE This specifies the number of data errors.
RCP This specifies the number of reception timeout errors.
RSP This specifies the number of response timeout errors.
RD This specifies the number of receiver disturbance errors.
RS This specifies the number of retries sent.
HLR This specifies the number of high-level retries sent.
NC This specifies the number of network collisions.
PE This specifies the number of procedural errors.
VE This specifies the number of version errors.
CE This specifies the number of command errors.
AE This specifies the number of address errors.
Software Manual
12.8 Monitoring the I/O Status
12.8.1 Introduction
Monitoring FSC Navigator offers various features that allow you to view the
variables on-line status of the FSC system. You can view any of the following:
• the current status of individual inputs and outputs (selectable by
position or tag number) (see subsections 12.8.2 and 12.8.3), and
• an overview of all inputs and outputs whose status is 'high' or 'low'
You can also force the value of an input or output to a certain fixed
state (see subsection 12.11) and calibrate analog inputs and outputs
There is a shortcut to the I/O signal status feature of FSC Navigator.

In the FSC On-Line Environment screen, choose the I/O Signal
Status button and then the Inputs or Outputs option (see Figure
12-13).
Figure 12-31 I/O Signal Status button with Inputs option
12.8.2 Monitoring Individual Inputs and Outputs
Monitoring To view the status of a specific input, choose the following menu
individual I/O options:
Fsc system Inputs Sequential
To view the status of a specific output, choose the following menu

options:
Fsc system Outputs Sequential
Software Manual
This will open the following screen:
Figure 12-32 Selecting an input or output for monitoring
You can use the <PgUp> and <PgDn> keys to browse through the list
of inputs or outputs. If the current channel is the last channel and you
press <PgDn>, the first configured hardware channel will be
displayed. If the current channel is the first channel and you press
<PgUp>, the last configured hardware channel will be displayed.
If the application has a redundant configuration and the next or
previous channel of a module is controlled by the other Central Part,
the Central Part will be switched. If the other Central Part is in
shutdown, all channels of that module will be ignored.
In addition to using <PgUp> and <PgDn>, you can also select a

specific input or output by specifying its position or tag number (see
subsection 12.8.3).
Forcing a variable If the value of the displayed input or output can be forced, the menu
bar will include a 'Force' option. For details on forcing variables refer
to subsection 12.11.
Software Manual
Information Figure 12-33 below shows an example of an I/O status screen. The
on screen information that is presented on screen depends on the I/O type.
Figure 12-33 Example of I/O status screen
The following fields may be displayed: (depending on the variable

type):
Appl. This field specifies the name of the application (at bottom line).
Central Part This field specifies the number of the Central Part (only in case of a
redundant Central Part configuration) (at bottom line).
Rack This field specifies the rack which houses the module that the input or
output has been allocated to.
Position This field specifies the position of the module in the rack that the
input or output has been allocated to.
Channel This field specifies the module channel that the input or output has
been allocated to.
Software Manual
Tag number This field specifies the tag number that has been assigned to the input
or output.
Service This field provides the specified description of the tag number.
Qualification This field specifies the status of the signal (only for digital inputs and
outputs).
Location This field specifies the location of the tag number.
Unit This field specifies the name of the unit which the input or output is
used for in the application program.
Subunit This field specifies the name of the subunit which the input or output
is used for in the application program.
Safety-related This field specifies whether the input or output is safety-related or

not.
Bottom scale This field specifies the lowest possible value that the signal can take
(only for analog inputs and outputs).
Top scale This field specifies the highest possible value that the signal can take
(only for analog inputs and outputs).
Signal type This field specifies the type of the signal (only for analog inputs and
outputs).
Scan value This field specifies the current value of the input or output signal (in
engineering units).
Application value This field specifies the value of the signal as used by the system for
the application calculations (i.e. scan value, diagnostic status, and
force status).
Input current This field specifies the currently detected current or voltage (only for
analog inputs or outputs).
Loop status This field specifies the loop status (only for analog inputs or outputs).
Diagnostic data This field specifies the diagnostic status of the input or output
channel. If the channel is valid, the field value will either be 'OK' or
'Defect'.
Software Manual
12.8.3 Selecting an Input/Output by Position or Tag Number
Selecting an In addition to simply browsing through the I/O database (see

input/output subsection 12.8.2), you can also select a specific input or output to
monitor by entering its position or tag number.
Position To select an input by position, choose the following menu options:

Fsc system Inputs Sequential Position
To select an output by position, choose the following menu options:

Fsc system Outputs Sequential Position
After selecting the 'Position' option, you can enter a hardware location
of an input. You must enter the rack, position number (1 to 18) and
channel number at the bottom left corner of the screen (see Figure
12-34).
Figure 12-34 Selecting an input or output by position
Software Manual
If the application has a redundant configuration and a channel is
selected that is controlled by a Central Part in shutdown, the
corresponding channel of the other Central Part is displayed.
Tag number To select an input by tag number, choose the following menu options:
Fsc system Inputs Sequential Tag number
To select an output by tag number, choose the following menu

options:
Fsc system Outputs Sequential Tag number
If you choose this option, you can select a specific input or output by
entering its variable type (I, AI, O, AO) and tag number, as shown in
Figure 12-35. Enter the variable type and tag number, or press <?> to
select from a list of available options.
Figure 12-35 Selecting an input or output by tag number
Software Manual
12.8.4 Viewing 'High' or 'Low' Inputs
Monitoring groups In addition to displaying the status of individual inputs and outputs,
of variables you can also display a list of all inputs whose status is 'low' or 'high'
(i.e. 'not low').
High inputs To display on screen all inputs whose status is 'high' (i.e. 'not low'),
Fsc system Inputs All High input
After you choose the 'All' option, a warning is displayed on screen:

WARNING: For I/O test purposes. Continue? (Y/N)
Use <Space> to toggle the field to 'Yes' and press <Enter> to confirm.
You can now choose the 'High input' option.
If you select this option, you must first specify whether you wish to
see analog inputs or digital inputs. Subsequently, all inputs of the
selected type with status 'high' (i.e. 'not low') are displayed on screen
(see Figure 12-36). They are represented by their rack, position,
channel and tag number (if available). This option can be used to test
if all inputs can be set high independently (for wiring check).
Low inputs To display on screen all inputs with status 'low', choose the following
menu options:
Fsc system Inputs All Low input

You can now choose the 'Low input' option.
If you select this option, you must first specify whether you wish to
see analog inputs or digital inputs. Subsequently, all inputs of the
selected type with status 'low' are displayed on screen. They are
represented by their rack, position, channel and tag number (if
available). This option can be used to test if all inputs can be set low
independently (for wiring check).
Software Manual
Figure 12-36 Listing all high inputs
12.8.5 Monitoring Inputs for Status Changes
Changes To display analog or digital inputs on screen as soon as their status

changes, choose the following menu options:
Fsc system Inputs All Test changes

You can now choose the 'Test changes' option.
If you choose this option, you must first specify whether you wish to
see analog inputs or digital inputs. Subsequently, inputs of the selected
type are displayed on screen as soon as their status changes. The
screen is updated continuously. The inputs are represented by their
rack, position, channel and tag number (if available). This option is
particularly useful for testing field loops.
Software Manual
12.9 Monitoring the Process and Variable Status
12.9.1 Introduction
Monitoring the FSC Navigator offers various features that allow you to view the
process status on-line status of the safeguarded process. You can view any of the
following:
• the on-line status of all signals in a functional logic diagram (FLD)
(see subsection 12.9.2),
• the on-line status of all FSC variables used in a functional logic
diagram (see subsection 12.9.3),
• the on-line status of freely selectable FSC variables in user-defined
screens (see subsection 12.9.4), and
• the on-line status of FSC variables by type (see subsection 12.9.5).
In addition, you can do the following:

• force the value of a variable to a certain fixed state (see subsection
12.1112.11), and
• write to a variable (see subsection 12.12).
Status screens All on-line status viewing of FSC variables (subsections 12.9.3 and
12.9.4) is done using screens. There are basically three kinds of
screens:
• FLD status screens.
FLD status screens are automatically generated for each FLD in the
application whenever you enter FSC Navigator's on-line
environment. They are predefined status screens that contain all the
variables used on the FLD (see subsection 12.9.3). They are not
fixed; you can delete or add variables.
• User-defined status screen.
In addition to the predefined FLD status screens, you can also
define your own screens, each of which can contain up to 32 FSC
variables whose status you wish to monitor (see subsection 12.9.4).
• PID screens.
PID screens allow you to view the on-line status of PIDs, and to edit
their characteristics (see subsection 12.14).
Software Manual
All screens (both automatically generated FLD screens and user-
defined screens) are stored in the screen file (<application>.SCR),
which is located in the application folder.
12.9.2 Monitoring the Status of FLDs
Monitoring the To monitor the on-line status of all signals in a functional logic
status of FLDs diagram (FLD), choose the following menu options:
Process status FLD
This option has two shortcuts:
• Menu bar: On-Line / Monitor FLDs

• Navigation area: FSC On-Line Environment / Process Status
Monitoring / Monitor FLDs (see Figure 12-37)

Monitor FLDs option
If you choose this option, you are prompted to specify the FLD whose
status you wish to monitor 'live'. You can enter the FLD number, or
you can press <?> to choose from a list of available FLDs. After you
have specified an FLD, a screen as shown in Figure 12-38 is displayed
which shows the status of all signals present on the FLD.
The screen is a graphical representation of the FLD as it is shown in
the FLD design editor (see Section 6 of this manual), and it is updated
continuously. The number of the FLD currently being monitored is
shown in the bottom left corner of the screen.
You can use <PgDn> or <PgUp> to display the next or previous FLD
of the current application.
Software Manual
Figure 12-38 Monitoring the status of an FLD
Note:
If the FSC system is part of an FSC network and it is not
directly connected to the FSC user station, communication will
take more time. In that case mouse response may be slower
when selecting variables or menu options. Keep the mouse
button pressed until the option has been selected.
Forcing a variable The 'Force' option in the menu allows you to force the value of a
variable in the displayed FLD (providing all prerequisites have been
met). For details on forcing variables refer to subsection 12.11.
Writing to a variable The 'Write' option in the menu allows you to write a value to a
variable in the displayed FLD (providing all prerequisites have been
met). For details on writing to variables refer to subsection 12.12.
Software Manual
Signal value
representation Signal values are represented as follows:
• Digital (boolean) signals (I, O):
A straight line () indicates that the signal is high (logic '1').
A dotted line (− − − −) indicates that the signal is low (logic '0').
• Binary signals (BI, BO) and analog signals (AI, AO):
The values are displayed across the double lines (for AI/AO in
engineering units). Please note that if the length of a binary value
exceeds the width of the double line, no value will be displayed.
The only solution then is to change the size of the double line in
your functional logic diagram.
• Timer, counter and register values (T, C, R):
The current value is displayed in the symbol.
• Annunciator outputs:
The current status of the annunciator output is indicated between the
two vertical lines before the output. If this output is high, this is
indicated by 'A', otherwise no indication is displayed.
Please note that if the annunciator output is flashing, the indication
might not be consistent in frequency with the current output, due to
the refresh time of the screen display.
Selecting There are three ways in which you can change the FLD that is
an FLD monitored:
• Using the <PgUp> and <PgDn> keys,
• Using the 'New Fld' option in the menu, or
• Using the 'Tag number' option in the menu.
<PgUp> and <PgDn> You can use <PgDn> or <PgUp> to display the next or previous FLD
of the current application. This allows you to browse through all
FLDs in an application.
New FLD Choose this option to specify another functional logic diagram whose
status you wish to monitor. You can enter the FLD number, or you
can press <?> to choose from a list of available FLDs.
Tag number Choose this option to specify a variable type and tag number to
monitor the status of the corresponding functional logic diagram. You
can enter the variable type and tag number, or you can press <?> to
choose from a list of available options.
Software Manual
Zoom mode If you used the SYM2, SYM3 or SYM4 symbol library for drawing
and view mode the functional logic diagrams, the FLD consists of more than one
display. In that case a number of additional options may be available
in the FLD menu:
• View,
• Zoom,
• Up, and
• Down.
View Choose this option to display the entire sheet on screen. This means
that the sheet is compressed and some text may no longer be readable
(depending on the graphic capabilities of the PC). This option is
useful to obtain an overview of the entire functional logic diagram.
The 'View' option is only available in zoom mode.
Zoom Choose this option to go back to the normal display when you are in
view mode. The 'Zoom' option is only available in view mode.
Up Choose this option to scroll the FLD half a screen upward.

The 'Up' option is only available in zoom mode.
Down Choose this option to scroll the FLD half a screen downward.
The 'Down' option is only available in zoom mode.
Software Manual
12.9.3 Monitoring the Status of All Variables in an FLD
Monitoring the To monitor the on-line status of all FSC variables used in a functional
status of variables logic diagram (FLD), choose the following menu options:
Process status Var status FLD
There is a shortcut to this option. In the FSC On-Line Environment

screen, choose the Process Status Monitoring button and then the
Variable Status option (see Figure 12-39).

Variable Status option
If you choose this option, you are prompted to specify the FLD whose
variables you wish to monitor. Enter the appropriate FLD number
(S1 to S999). Make sure that you precede the number with the letter
'S', otherwise FSC Navigator will interpret it as a user-defined status
screen number (see subsection 12.9.4). If you enter the number of a
non-existing FLD screen or status screen, the following message will
be displayed:
Screen has NOT been selected for display.
After you have specified a valid FLD number (Sxxx), a screen as
shown in Figure 12-40 is displayed which shows the on-line status of
all FSC variables used in the selected FLD. The screen is updated
continuously. The number of the FLD currently being monitored is
shown in the top right corner of the screen.
You can use <PgDn> or <PgUp> to browse through the list of FLDs
(see subsection 12.9.2) and status screens. You can also press <S>
(Search screen) to select another FLD.
If a variable is followed by the letter 'F', it means that it is forced.

If a variable is following by the letter 'D', it is regarded faulty.
Software Manual
Figure 12-40 Monitoring the status of all variables in an FLD
variable in the displayed status screen (providing all prerequisites
have been met). For details on forcing variables refer to subsection
12.11.
have been met). For details on writing to variables refer to subsection
12.13.
Editing an FLD Even though FLD status screens are generated automatically, they
status screen can be modified. For details refer to subsection 12.9.6.
Software Manual
12.9.4 Monitoring the Status of Selected Variables
Selecting You can define your own status screens that contain a maximum of
a status screen 32 variables whose status is monitored and continuously updated.
These variables can, for example, be all the inputs and outputs of a
process unit. To select a status screen and display it on screen, choose
Process status Var status sCreen
If you choose this option, you are prompted to specify a screen

number. Enter the appropriate screen number (1 to 99). If you enter a
status screen number that does not exist, an empty status screen will
open in edit mode (see subsection 12.9.6). If the status screen does
exist, it will be displayed. Figure 12-41 below shows an example of a
user-defined status screen.
Figure 12-41 Monitoring the status of variables in a

user-defined screen
Software Manual
The status screen shows the on-line status of a user-defined group of
variables. The screen is updated continuously. The number of the
current screen file is shown in the top right corner of the screen.
You can use <PgDn> or <PgUp> to browse through the list of status
screens and FLD screens (see subsection 12.9.2). You can also press
<S> (Search screen) to select another status screen.
If a variable is followed by the letter 'F', it means that it is forced.

If a variable is following by the letter 'D', it is regarded faulty.
have been met). For details on forcing variables refer to subsection
12.11.
have been met). For details on writing to variables refer to subsection
12.12.
Software Manual
12.9.5 Monitoring the Status of Variables by Type
Variable type You can display a status list of all the variables of a certain type and
and tag number (part of a) tag number. To display such a list of variables, choose the
Process status Var status Var type
If you choose this option, you are asked to enter an FSC variable (type
and tag number). Enter the variable type and tag number, or press <?>
to select from a list of available options. If you enter a full tag number,
the status of the selected FSC variable is displayed and continuously
updated. If you enter an incomplete tag number, all FSC variables
whose tag number starts with the text you entered are displayed and
updated. This means you can easily display all variables of a particular
type by keeping the 'Tag number' field empty. The maximum number
of FSC variables displayed is 32. Figure 12-42 below shows an
example of what the screen might look like:
Figure 12-42 Monitoring the status of variables by type
Software Manual
12.9.6 Working with Variable Status Screens
Editing a All status screens can be edited (even the standard FLD screens,
status screen which are generated automatically). To edit a status screen, choose
the 'Edit' option from the menu line in an FLD screen (see subsection
12.9.3) or user-defined status screen (see subsection 12.9.4). This will
open the current status screen in edit mode, as shown in Figure 12-43.
A status screen consists of a maximum of 32 FSC variables (type and
tag number) or 8 PID controllers. Each screen has its own number (1
to 99). You can delete or add variables whose status should be
monitored. Enter the variable type and tag number, or press <?> to
select from a list of available options.
Note:
For details on PIDs refer to Appendix E of this manual ("PID
Controllers").
Figure 12-43 Editing a status screen
Software Manual
If you are done editing, press <Esc> to save the status screen to disk.
If you were editing an FLD screen, the updated screen is displayed on
screen immediately. To display the updated user-defined status screen,
to need to press <Esc> once more.
Deleting a screen To delete the current screen, choose the 'Delete' option from the menu
line. Before the screen will actually be deleted, you are asked to
confirm the operation.
Opening another To open another status screen, choose the 'Search screen' option from
screen the menu line. If you choose this option, you are prompted to specify
a screen number. Enter the appropriate screen number (1 to 99, or S1
to S999). If you enter a status screen number that does not exist, an
empty status screen will open in edit mode. If the status screen does
exist, it will be displayed.
Note:
If your system contains a PID, you will be asked whether a new
screen should be a status screen or PID screen.
12.9.7 Rebuilding the Screen File
Rebuilding the All screens (both automatically generated FLD screens and user-
screen file defined screens) are stored in the screen file (<application>.SCR),
which is located in the application folder. Sometimes you may want
to rebuild the screen file (e.g. after an FSC database rebuild or if the
screen file has become corrupted). To rebuild the screen file, choose
Process status Var status Rebuild screenfile
The screen file is then updated according to the current FSC database.
If you choose the 'Rebuild screenfile' option, you will be asked
whether the present screen file must be saved or deleted. Just press
<Space> to select 'Yes' or 'No', and press <Enter> to confirm. If you
select 'Yes', the extension of the current screen file will be changed to
OLD. Should you wish to reuse your old screen file, all you need to is
change the extension OLD into SCR (e.g. using Windows Explorer).
Software Manual
Rebuilding the screen file may take some time, depending on the size
of the current database.
If you rebuild the screen file, all standard FLD screens are generated
again, which means that any changes you made to them are lost. The
user-defined status screens remain available after a screen file rebuild.
Software Manual
12.10 Viewing the I/O Loop Status
12.10.1 Loop Status for the Entire Application
Loop status for To view the I/O loop diagnostics for the entire application (i.e. both
entire application Central Parts in a redundant system), choose the following menu
options:
Process status Loop status
There is a shortcut to the 'Loop Status' option. In the FSC On-Line

Environment screen, choose the Diagnostics button and then the I/O
Loop Diagnostics option (see Figure 12-44).
Figure 12-44 Diagnostics button with I/O Loop Diagnostics option
Note:
This option will check both Central Parts in a redundant
configuration. To view the I/O loop status errors for one Central
Part refer to subsection 12.10.2.
If you choose this option, a screen will open which displays the
following:
• the specification (type, tag number, location) of all analog input
channels whose values are out of their defined range,
• all output variables allocated to a 10214/1/2 or 10216/x/x module
that have an open loop or short circuit, and
• all variables allocated to a 10106/2/1 module whose loop status is
not OK.
For technical details on the above modules refer to the FSC Hardware
Manual.
Software Manual
Figure 12-45 below shows an example of what the screen might look
like. If the list does not fit on the screen, you can use the ↑ and ↓
arrow keys on the keyboard to scroll through the list.
Figure 12-45 Viewing the I/O loop status
Error reporting Not all loop status errors are displayed. Table 12-1 below shows what
is reported in the loop status screen for the entire application.
Table 12-1 Loop status errors (entire application)

In case of the following loop status error… Then the following is displayed:
Input loop status error in Central Part 1 only. Error is not reported.
Input loop status error in Central Part 2 only. Error is not reported.
Input loop status error in both Central Part 1
Error is reported for Central Part 1 only.
and Central Part 2.
Output loop status error in Central Part 1 only. Error is reported for Central Part 1.
Output loop status error in Central Part 2 only. Error is reported for Central Part 1.
Output loop status error in both Central Part 1
Error is reported for Central Part 1 only.
and Central Part 2.
Software Manual
12.10.2 Loop Status for the Selected Central Part
Loop status for To view the input loop diagnostics for the selected Central Part
selected CP (shown in the bottom left corner of the screen), choose the following
menu options:
Fsc system Inputs Loop status
To view the output loop diagnostics for the selected Central Part
(shown in the bottom left corner of the screen), choose the following
menu options:
Fsc system Outputs Loop status
If you choose either of these options, a screen will open which

basically shows the same as the loop status screen for the entire
application (see subsection 12.10.1). The main differences are the
following:
• The loop status screen for the selected Central Part will only show
the loop status for one Central Part, whereas the loop status screen
for the entire application (see subsection 12.10.1) shows both
Central Parts.
• The loop status screen for the selected Central Part will only show
inputs or outputs (depending on the selected menu option), whereas
the loop status screen for the entire application (see subsection
12.10.1) shows both inputs and outputs.
• The error visibility is not entirely the same. Table 12-1 on page
12-54 lists what is reported for the entire application, and Table
12-2 on the next page for selected Central Parts.
Software Manual
Error reporting Table 12-2 below show what is reported in the loop status screen for
the selected Central Part.
Table 12-2 Loop status errors (for selected Central Part)

In case of the following loop status Then the following is displayed:
error…
Central Part 1 selected Central Part 2 selected
Input loop status error in Central Part 1. Error is reported. Error is not reported.
Input loop status error in Central Part 2. Error is not reported. Error is reported.
Output loop status error in Central Error is reported. Error is not reported.
Part 1.
Output loop status error in Central Error is not reported. Error is reported.
Part 2.
Note:
This option will only check the selected Central Part. This
means that if loop status errors are present in both Central Parts,
only the ones for the selected Central Part will be reported. To
view the I/O loop status errors in both Central Parts refer to
subsection 12.10.1.
Software Manual
12.11 Forcing Inputs and Outputs
12.11.1 Introduction
Forcing inputs For maintenance reasons, it may be desirable to force an input or

and outputs output to a certain fixed state, e.g. when exchanging a defective input
sensor. This allows the sensor to be exchanged without affecting the
process continuity. During the exchange, the applicable input or
output is forced to its normal operational state. All forcing actions are
included in the FSC event reports for traceability purposes.
Forcing operations can be performed in any of the following screens:
• the I/O status screen (see subsection 12.8),
• the graphical FLD status screen (see subsection 12.9.2),
• the FLD variables status screen (see subsection 12.9.3), and
• the user-defined variables status screen (see subsection 12.9.4).

1. Forcing is only possible if the Force Enable key switch has been
activated (which means that the Force-Enable system input is
high).
2. Inputs and outputs can only be forced if their force-enable
attribute has been set to 'Yes' (see Section 4 of this manual).
3. If the password for forcing variables is active, you must enter the
correct password to be able to perform any forcing operation.
12.11.2 Setting a Force
I/O status screen To force an input in the I/O status screen (see subsection 12.8),
Fsc system Inputs Sequential Force
To force an output in the I/O status screen (see subsection 12.8),

Fsc system Outputs Sequential Force
Software Manual
Please note that the menu bar will only contain the 'Force' option if the
currently displayed variable can be forced.
If forcing is allowed for the current input or output, you can now set
the forced value (see below).
FLD status screen To force an input or output signal in the 'live' FLD status screen (see
subsection 12.9.2), choose the following menu options:
Process status FLD Force
You can now force an input or output signal in the current FLD. To do
that, select a signal by moving the cursor to its symbol, and press
<Enter> or click the left mouse button. You can now set the forced
value (see below).
Variables To force an input or output variable in an FLD variables status screen

status screen (see subsection 12.9.3), choose the following menu options:
Process status Var status FLD Force
To force an input or output variable in a user-defined variables status

screen (see subsection 12.9.4), choose the following menu options:
Process status Var status sCreen Force
Please note that the 'Force' option will only be available if the status
screen contains variables that can be forced. To force a variable, select
the appropriate variable by moving the cursor bar to its line, and press
<Enter>. You can now set the forced value (see below).
Setting the If the input or output is digital, you can use <Space> to toggle the I/O
forced value status and press <Enter> to confirm the forced value.
If the input or output is analog or binary, you must enter the desired
forced value using the keyboard and press <Enter> to confirm. This
value must be between the bottom scale and the top scale, both of
which are presented on screen. Figure 12-46 below shows an example
of forcing an analog input in the I/O status screen (see subsection
12.8). Please note that the status/value shown is the actual
status/value.
Software Manual
Figure 12-46 Forcing an analog input
Force
representation The way that a forced variable is represented depends on the screen:
• In the I/O status screen (see subsection 12.8):
If an input or output is forced, its application value is followed by
the letter 'F' (see Figure 12-47).
Figure 12-47 Display of a forced variable in the I/O status screen
Software Manual
• In a 'live' FLD status screen (see subsection 12.9.2):
If an input is forced, the current scan value will be displayed
between the two vertical lines behind this input (see Figure 12-48).
If an output is forced, the force value will be displayed between the
two vertical lines in front of the output.
Figure 12-48 Display of a forced variable in a 'live' FLD
• In a variables status screen (see subsections 12.10.3 + 12.10.4):

If a variable is forced, its application value is followed by the letter
'F' (see Figure 12-49).
Figure 12-49 Display of a forced variable in a variables status screen
12.11.3 Clearing Individual Forces
I/O status screen To clear the forced status of an input in the I/O status screen (see
subsection 12.8), choose the following menu options:
Fsc system Inputs Sequential Clr force
To clear the forced status of an output in the I/O status screen (see
subsection 12.8), choose the following menu options:
Fsc system Outputs Sequential Clr force
Software Manual
If the password for forcing variables is active, you must first enter the
correct password to start this option. After you have done that, the
forced status of the input or output that is displayed on screen is
cleared, and the input or output gets its current process status.
FLD status screen To clear the forced status of an input or output signal in the 'live' FLD
status screen (see subsection 12.9.2), choose the following menu
options:
Process status FLD Clear
You can now clear the forced status of an input or output signal in the
current FLD. To do that, select the signal by moving the cursor to its
symbol, and press <Enter> or click the left mouse button to clear the
force. The signal will get its current process status.
Variables To clear the forced status of an input or output variable in an FLD

status screen variables status screen (see subsection 12.9.3), choose the following
menu options:
Process status Var status FLD Clear force
To force an input or output variable in a user-defined variables status

Process status Var status sCreen Clear force
To clear the forced status of a variable, select the appropriate variable

by moving the cursor bar to its line, and press <Enter>. The variable
will get its current process status.
Software Manual
12.11.4 Clearing All Forces
Clearing all forces To remove all the forces that have been set in the FSC system, choose
Process status Clr all forces
If the password for forcing variables is active, you must first enter the
correct password to start this option. After you have done that, you are
asked whether all forced FSC variables should indeed be cleared.
After you confirm, all forces are removed and the FSC variables will
get their current status.
12.11.5 Listing the Forced Variables
Listing all forces To see a list of all the variables in the FSC system that are currently
forced (analog/digital inputs, analog/digital outputs, and markers),
Process status lIst forces
There is a shortcut to the 'List Forces' option. In the FSC On-Line

Environment screen, choose the Process Status Monitoring button
and then the List Forces option (see Figure 12-50).

List Forces option
If you choose the 'List Forces' option, a screen will open which
contains all variables in the FSC system that are currently forced (see
Figure 12-51). The variables are represented by their rack, position,
channel, type and tag number. If no variables are forced, a message
will be displayed. If the list does not fit on the screen, you can use the
arrow keys on the keyboard to scroll through the list.
Software Manual
Figure 12-51 Listing all forces in the system
Software Manual
12.12 Writing to Inputs and Outputs
Writing a value You can write a specific value to certain variables, providing the
to a variable write-enable attribute of that variable has been set to 'Yes' (see
Section 4 of this manual). The new value will remain valid until it is
overwritten, e.g. due to a status change.
You can only write to variables of the following types:
• digital inputs (I) with location 'COM',
• binary inputs (BI) with location 'COM',
• markers (M) (not for on/off-sheet references),
• registers (R) (not for off-sheet references),
• counters (C), and
• timers (T) (providing they are running).
I/O status screen To write a value to an input in the I/O status screen (see subsection
12.8), choose the following menu options:
Fsc system Inputs Sequential Write
To write a value to an output in the I/O status screen (see subsection

12.8), choose the following menu options:
Fsc system Outputs Sequential Write
If writing is allowed for the current input or output, you can now set
the write value (see below).
FLD status screen To write a value to an input or output signal in the 'live' FLD status
Process status FLD Write
You can now write a value to an input or output signal in the current
FLD. To do that, select a signal by moving the cursor to its symbol,
and press <Enter> or click the left mouse button. You can now set the
write value (see below).
Software Manual
Variables To write a value to an input or output variable in an FLD variables
status screen status screen (see subsection 12.9.3), choose the following menu
options:
Process status Var status FLD Write
To write a value to an input or output variable in a user-defined

variables status screen (see subsection 12.9.4), choose the following
menu options:
Process status Var status sCreen Write
Please note that the 'Write' option will only be available if the status
screen contains variables that can be written to. To write a value to a
variable, select the appropriate variable by moving the cursor bar to its
line, and press <Enter>. You can now set the write value (see below).
Setting the If the input or output is digital, you can use <Space> to toggle the I/O
write value status and press <Enter> to confirm the write value.
If the input or output is analog, you must enter the desired write value
using the keyboard and press <Enter> to confirm. This value must be
between the bottom scale and the top scale, both of which are
presented on screen.
Software Manual
12.13 Calibrating Analog Inputs and Outputs
12.13.1 Calibrating Analog Inputs
Calibration FSC Navigator offers a feature that allows you to calibrate the analog
input channels in the FSC system (10102/./. modules). To do this,
Fsc system Inputs Calibrate
Note:
If the password for forcing variables is active, you must first
enter the correct password to start this option.
If you want to calibrate an analog input, you must first specify the
rack location of the analog input module to calibrate. The 'Rack' and
'Position' fields default to the position of the first valid 10102/./.
analog input module. If you enter a location that does not contain a
10102/./. module, the following error message is displayed on screen:
Selected module does not support the calibrate function.
After you have specified a valid rack location, you must enter the
calibration value for channel 1 (Span). There are six standard
calibration values: 4, 8, 10, 12, 16, and 20 mA. Press <Space> to
select a value, and press <Enter> to confirm.
Connect a mA source to channel 1 (volt source for redundant

configurations). Place the 10102/./. module in the extender card and
connect the flatcable to the horizontal bus via the extender flatcable.
Press <Space> to select a value, and press <Enter> to confirm.
Notes:
1. After this, the calibration value of channel 2 (Zero) is set to
0 mA.
2. Short-circuit the input terminals for channel 2 (d22 and z22
on the 10102/1/. connector).
3. In redundant configurations, the calibration is preferably
performed with only one Central Part running.
The screen will now look something like Figure 12-52.
Software Manual
Figure 12-52 Calibrating analog inputs (zero + span)
This screen provides information about how you should manipulate

the potentiometers at the module to achieve the appropriate
calibration. Figure 12-53 below shows the location of the
potentiometers at the 10102/./. modules.
10102/1/. module 10102/2/. module

Figure 12-53 Location of potentiometers on the 10102/./. module
Software Manual
Note:
During calibration, the diagnostics will be continuously updated
at the bottom of the screen.
Adjusting the Zero You must first calibrate the zero. This is done by adjusting
potentiometer P4 on the module (see Figure 12-53). The action to
take depends on the value of the Zero field:
DOWN Turn potentiometer P4 (see Figure 12-53) counter-clockwise.
UP Turn potentiometer P4 (see Figure 12-53) clockwise.
HOLD Potentiometer P4 (see Figure 12-53) is in the correct position.

Hold it for stabilization.
CORRECT Potentiometer P4 (see Figure 12-53) is set correctly.
The zero value must constantly change between 0 mA and 0.006 mA

(a steady 0 mA means that the zero is too low).
Adjusting the Span If the Zero field indicates 'CORRECT', you must calibrate the Span.
This is done by adjusting potentiometer P1 on the module (see Figure
12-53). The action to take depends on the value of the Span field:

Note:
When you adjust the Span, the Zero result may change. Correct
this by adjusting potentiometer P4 (see Figure 12-53). Keep
adjusting potentiometers P1 and P4 until both Span and Zero are
'CORRECT'.
When both Span and Zero are 'CORRECT', the test value calibration
will be performed. The screen will now look something like Figure
12-54.
Software Manual
Figure 12-54 Calibrating analog inputs (test value)
Adjusting the Span You must first roughly calibrate the Span. This is done by adjusting
(test value) potentiometer P2 on the module (see Figure 12-53). The action to
take depends on the value of the Span field:

The Span is roughly calibrated when the result is 'HOLD', or switches

between 'UP' and 'DOWN'.
Software Manual
Adjusting the Zero After you have calibrated the Span, you must calibrate the Zero. This
(test value) is done by adjusting potentiometer P5 on the module (see Figure
12-53). The action to take depends on the value of the Zero field:

If the Zero result is 'CORRECT', the Span must be calibrated again.

This is done by adjusting potentiometer P2 (see Figure 12-53) as
described above, until the Span result is 'CORRECT'.
Note:
When you adjust the Span of the test value calibration, the Zero
result may change. Correct this by adjusting potentiometer P5
(see Figure 12-53). If both values are 'HOLD' or 'CORRECT',
cycle the Fault Reset key switch to reset the diagnostics. Keep
adjusting the potentiometers (P2 and P5) until both Zero and
Span are 'CORRECT'.
12.13.2 Calibrating Analog Outputs
Calibration FSC Navigator offers a feature that allows you to calibrate the analog
output channels in the FSC system (10205/./. modules). To do this,
Fsc system Outputs Calibrate
Note:
If the password for forcing variables is active, you must first
enter the correct password to start this option.
If you want to calibrate an analog output, you must first specify the
rack location of the analog input module to calibrate. The 'Rack' and
'Position' fields default to the position of the first valid 10205/./.
Software Manual
analog output module. If you enter a location that does not contain a
10205/./. module, the following error message is displayed on screen:
Selected module does not support the calibrate function.
After you have specified a valid rack location, you must enter the
calibration value for channel 1 (Span). There are seven standard
calibration values: 4, 8, 10, 12, 16, 20, and 24 mA. Press <Space> to
select a value, and press <Enter> to confirm.
The output current can now be measured using, for example, a

multimeter. The Span can be adjusted with the potentiometer for the
channel specified. The output has been correctly calibrated if the
meter indicates the value set.
Note:
The diagnostics of the module are continuously updated in the
screen. If any faults are mentioned, you must give a fault reset in
order to retest the channel(s).
You can press <Esc> at any time to stop the calibration procedure. A
menu will then appear which allows you to select another module,
change the calibration value, or return to the main menu. Use <PgDn>
or <PgUp> to select the next or previous channel.
Figure 12-55 Location of potentiometers on the 10205/./1 module
Software Manual
12.14 Working with PIDs
12.14.1 Viewing the PID Status
Edit PID If your system configuration includes a PID, you can view (and edit)
its control parameters. To view (or edit) a PID, choose the following
menu options:
Process status Var status Edit pid
Please note that the 'Edit pid' option will only be available if a PID has
been configured for your system. If you choose this option, you will
be asked to enter the tag number of the PID controller you wish to see
or edit. If the tag number you entered is found in the database, the
following screen will appear:
Figure 12-56 Viewing and editing a PID
Software Manual
The following information is displayed on screen:
Tag number This field specifies the tag number of the PID that is displayed on
screen. It cannot be modified.
Unit This field specifies the process unit of the PID that is displayed on
Subunit This field specifies the process subunit of the PID that is displayed on
Sample time This field specifies the sample time of the PID controller. Since this
is a digital PID controller, it is the time between two samples. The
range is 0.1 to 204.7 seconds.
Proportional band This field specifies the percentage change in the error (setpoint input)
100/K for doubling the output. This is a measure for the gain of the PID
controller. The lower the proportional band, the higher the gain. For
example, 50% means an amplifier factor of 2. It can be modified over
the full range, but it cannot be 0.
1/Reset time This field specifies the number of times per minute that the
integration is calculated. For example, if 1/Reset Time is 2 rep/min,
the time is integrated in 0.5 minute (1/2). This field can be modified
over the full positive range. If it is 0 (zero), the integrating part is out
of the controller.
Rate time This field specifies the time period in which the differentiations are
made discrete. The range is 0.0 to 3276.7 seconds. If it is 0 (zero), the
differentiating part is out of the controller.
Deviation limit This field specifies the high clamp for the error (setpoint – input).
Please note that if this parameter is 0 (zero), there will be no correct
controlling. Any value in engineering input units can be assigned to
this parameter.
Setpoint low clamp This field specifies is the low clamp for the setpoint. The setpoint will
never become smaller than this value. Any value in engineering units
can be assigned to this parameter.
Setpoint low clamp This field specifies the high clamp for the setpoint. The setpoint will
never exceed this value. Any value in engineering units can be
assigned to this parameter.
Software Manual
Setpoint The setpoint cannot be specified in Auto mode (in this mode, it is
generated by the application program from, for example, BCD
switches or a constant.). In test mode, a test setpoint may be
specified. If you then enter a test input as well, you can simulate a
process. Any value in engineering units can be assigned to this
parameter.
Output low clamp This field specifies the low clamp for the output. The output will
never become smaller than this value. Any value in engineering units
can be assigned to this parameter.
Output high clamp This field specifies the high clamp for the output. The output will
never exceed this value. Any value in engineering units can be
assigned to this parameter.
Mode If the password for writing variables is active, you must first enter the
correct password to start this option. The input, output and setpoint
are only continuously updated if the cursor is positioned at this field.
The other parameters are less frequently updated. The following
operating modes are supported:
• Auto:
This is the automatic mode. The output is calculated each sample
timeout of the error, based on the input, setpoint and the configured
parameters. The input is an FSC input, the setpoint is generated by
the application program and the output is calculated, so the setpoint
and the output cannot be changed.
• Cascade:
The PID acts as a slave which is controlled by a master. You can
only switch to this mode if the master is in Auto mode. The output
of the master will control the (cascade) setpoint of this PID.
• Manual:
In this mode, the output can be entered. This output is directly
copied to an FSC output and is not calculated.
• Test:
In this mode, the input (a virtual input) and the setpoint (a virtual
setpoint) can be entered. The output is calculated using these values.
This allows the PID function to be simulated.
Output This is the FSC output, which is updated if the cursor position is in
the 'Mode' field. In Manual mode, this value can be modified.
Input In Auto and Manual mode, this is the FSC input, which is updated if
the cursor position is in the 'Mode' field. In Test mode, this value is a
virtual test input.
Software Manual
Key commands In addition to the arrow keys and <Enter> (which are used to move
around the screen), the following key command are available:
<Esc> If you press this key, you will exit the PID edit screen without saving
any changes you made.
<PgDn> If you press this key, FSC Navigator will check whether all inputs are
in the correct range. It will then save the current PID and open next
PID in the database for editing.
<PgUp> If you press this key, FSC Navigator will check whether all inputs are
in the correct range. It will then save the current PID and open
previous PID in the database for editing.
12.14.2 Adjusting PIDs
Adjusting PIDs If your system configuration includes a PID, you can adjust it. To
adjust a PID, choose the following menu options:
Process status Var status Adjust pid
Please note that the 'Adjust pid' option will only be available if a PID
has been configured for your system. If the password for writing
variables is active, you must first enter the correct password before
you can adjust a PID. If you choose the 'Adjust pid' option, you will
be asked to enter the tag number of the PID controller you wish to
adjust. If the tag number you entered is found in the database, the
screen as shown in Figure 12-57 will open. It shows a graphical
representation of one PID. You can change the PID's operating mode.
In test mode, you can modify the (test) setpoint and (test) input. In
manual mode, you can modify the output.
The PID screen contains three bars. The left bar (PV) represents the
setpoint, the middle (Pv) the input and the right (Out) the output.
These bars are filled proportionally between their bottom and top
scaling. For example, a fully filled bar means the value is at its
maximum, whereas a half-filled bar denotes a value halfway between
the bottom and top scaling. The value in engineering units is placed
under each bar.
Software Manual
Figure 12-57 Adjusting PID parameters
At the right of the picture, the parameters of the PID are displayed.
These values cannot be changed here. The bars and values are
continuously updated. The following key commands are available:
Menu options Depending on the PID's operating mode, a menu will be displayed on
screen:
• Auto:
Menu: to Manual mode, to Test mode, (Cascade mode)
• Manual:
Menu: to Auto mode, to Test mode, set Output
• Test:
Menu: to Auto mode, to Manual mode, set Setpoint, set Input
• Cascade:
Menu: to Auto mode, to Manual mode, to Test mode
to Auto mode Use this option to switch to Auto mode. The screen will be updated.
to Manual mode Use this option to switch to Manual mode. The screen will be
updated.
to Test mode Use this option to switch to Test mode. The screen will be updated.
Software Manual
to Cascade mode Use this option to switch to Cascade mode. The screen will be
updated.
set Output Use this option to set the output to a certain value. You will be asked
to enter the value. The screen will be updated.
set Input Use this option to set the input to a certain value. You will be asked
to enter the value. The screen will be updated.
set Setpoint Use this option to set the setpoint to a certain value. You will be
asked to enter the value. The screen will be updated.
Key commands The following key command are available:
<Esc> If you press this key, you will exit this screen and return to the PID
menu.
<PgDn> If you press this key, the next PID in the database will be displayed.
<PgUp> If you press this key, the previous PID in the database will be
displayed.
Software Manual
12.15 Working with System Diagnostics
Extended The FSC system continuously performs self-tests which enable it to

diagnostics collect valuable information on the diagnostic status of its own
hardware and the field equipment. You can retrieve this diagnostic
information from the system and view it on screen. This allows you
to monitor the system status, and locate and resolve problems
effectively, thus reducing the Mean Time To Repair (MTTR) and
minimizing the risk of a plant trip.
Note:
If the FSC system is integrated into the TPS system, the FSC
diagnostics are also available at the TPS operator stations (US,
UXS, GUS).
In addition to viewing the diagnostics from the current application on

screen (see subsection 12.15.2), you can also perform the following
tasks:
• Select the FSC system(s) that FSC Navigator should interrogate to
retrieve the extended diagnostics (see subsection 12.15.3),
• Let FSC Navigator interrogate the selected FSC system(s)
continuously and write the extended diagnostics to the database
(see subsection 12.15.4),
• Display the contents of the diagnostics database currently stored on
your hard disk (see subsection 12.15.5), and
• Back up the extended diagnostics database, e.g. for further analysis
Important!
Always read diagnostic data prior to a system fault reset.
Otherwise the diagnostic information will be lost.
Software Manual
12.15.2 Retrieving Diagnostics from the FSC System
Viewing the To view all the on-line diagnostic information from the current
diagnostics application, choose the following menu options:
Fsc system Extended diag
This option has three shortcuts:
• Menu bar: On-Line / Extended Diagnostics

• Button bar: Diagnostics
• Navigation area: FSC On-Line Environment screen /
Diagnostics / Extended Diagnostics
(see Figure 12-58)
Figure 12-58 Diagnostics button with Extended Diagnostics option
If you choose the 'Extended Diagnostics' option, FSC Navigator

retrieves all diagnostic messages from the current application and
displays them on screen (see Figure 12-59). All diagnostic data that is
retrieved from the FSC system is stored in a database file on your hard
disk. The following information is displayed on screen:
• module name,
• short description of the event,
• rack and position of hardware modules, and
• time and date of event.
The retrieved diagnostic information is presented in ascending

chronological order, i.e. the most recent event is shown on the last
line.
Notes:
1. Refer to subsection 12.16 on page 12-86 for a full list of
extended diagnostic messages for the various module types.
2. You can also retrieve diagnostics from the selected
application(s) continuously. For details refer to subsection
12.15.4.
Software Manual
Figure 12-59 Viewing the extended diagnostic information
All diagnostic information that is retrieved from the application is

stored in the extended diagnostics database. If the FSC system has a
redundant configuration, FSC Navigator retrieves and stores the
diagnostic information from all Central Parts. The diagnostic
information of the application's selected Central Part is displayed.
If the list of diagnostic messages does not fit on one screen, you can
use the up and down arrow keys (↑ and ↓) or <PgUp> and <PgDn> to
browse through the list.
You can quickly switch between Central Parts by pressing <Alt>+C.
Software Manual
12.15.3 Selecting the FSC System(s) for Diagnostics Retrieval
Selecting an To select the FSC system(s) whose diagnostics should be retrieved,

FSC system choose the following menu options:
Diag to disk cOnfig
If you select this option, a popup window will appear which lists all
FSC systems that FSC Navigator can communicate with. It also shows
the maximum size of the extended diagnostics database (see Figure
12-60).
Figure 12-60 Selecting the FSC system(s) for diagnostics retrieval
All applications which must be continuously interrogated can be

(de)selected. After you have finished (de)selecting applications, the
size of the extended database must be specified. This information is
stored in the file DIAGEXT.CFG.
Software Manual
Selecting If you choose the 'cOnfig' option, a popup window will appear which
applications lists all FSC systems that FSC Navigator can communicate with. Use
the arrow keys on your keyboard to move between applications. Press
<S> to select an application, and <D> to deselect an application.
The selected applications are highlighted. If an application name
consists of more than one system number, a separate window appears
that contains all the valid system numbers.
If you choose the 'cOnfig' option for the first time, the current
application is selected by default. If you have used this option before,
the information from the last time you used it is retrieved from the
configuration file and presented on screen.
Setting maximum If you press <Enter> in the application selection window, you can set
database size the maximum size of the extended diagnostics database file. The
default size is 500 Kbytes. The minimum size is 100 Kbytes or, if the
current size is greater than 100 Kbytes, 110% of the current size. The
maximum size is 30 Mbytes, or the remaining disk space plus the
current size of the extended diagnostic data file (whichever of the two
is smaller).
12.15.4 Retrieving Diagnostics Continuously
Retrieving
diagnostics To retrieve diagnostics from the select FSC system(s) continuously,
continuously choose the following menu options:
Diag to disk Continuous
If you choose this option, FSC Navigator will establish

communication with the selected application(s) and will continuously
interrogate them to retrieve their diagnostics. The diagnostic
information from all applications is stored in the diagnostic database.
The following message is displayed on screen as long as continuous
diagnostics retrieval is active:
Writing extended diagnostic data to disk...
The bottom line of the screen shows the application that is being
interrogated.
Software Manual
Before any extended diagnostics data of a Central Part is stored, FSC
Navigator checks the size of the extended diagnostic database. If the
size exceeds 90% of the maximum size, a message will be displayed
to indicate that the database is almost full. You can then decide to
interrupt the retrieval process and back up (part of) the database before
proceeding. If the database size exceeds 95% of the maximum size,
FSC Navigator will automatically reduce it to 85% of the maximum
by deleting the oldest information stored in the database. This is done
to create more space for new data. A message will be displayed to
indicate that data is being deleted. After diagnostic data has been
deleted, the database will be rebuilt. This may take some time,
depending on the size of the database file.
Important!
Once extended diagnostic data has been deleted from the
database, it can never be recovered.
Stopping the You can press <Esc> at any time to stop continuous diagnostics
retrieval process retrieval. If you do, the communication with all the applications is
terminated, and the retrieved data is stored in the extended
diagnostics database.
Note:
If, during continuous diagnostics retrieval, the time of the FSC
system is changed, the event records that are stored in the
diagnostics database will be timestamped according to the new
settings. This means there may then be chronological
inconsistencies between the event records in the diagnostics
database.
12.15.5 Reading Diagnostic Information from Hard Disk
Reading
diagnostics To read the contents of the diagnostics database currently stored on
from hard disk your hard disk, choose the following menu options:
Diag to disk Retrieve
If you choose this option, you are asked to specify the name of the file
that should be retrieved. The name must have the following format:
<Disk>:\<Path>\<Filename> (e.g. 'C:\BACKUP\DIAGS').
Software Manual
The extension '.EXD' is assumed and should not be specified. The
default name is the diagnostic database of the current application.
If the stored data was retrieved from an application that can

communicate with the current application, then the data will be
displayed. Otherwise a message appears to indicate that the diagnostic
data cannot be displayed. The retrieved diagnostic information is
presented in ascending chronological order, i.e. the most recent event
is shown on the last line.
If the list of diagnostic messages does not fit on one screen, you can
use the up and down arrow keys (↑ and ↓) or <PgUp> and <PgDn> to
browse through the list.
Defining The first time you choose the 'Retrieve' option, the entire list of
a range diagnostics messages will be displayed. Once this list is on the
screen, you can press <Esc> to search for specific diagnostic data by
entering a timestamp filter (date and time). You must use the
following date and time format: DD-MM-YY,HH.MM.SS (e.g. '17-
02-99,10:00:00'). Please note that a 24-hour clock should be used.
The screen will then show the first diagnostic event that occurred
after the specified date and time (and all others after that). If no
events meet the defined date and time criteria, a message will be
displayed.
Note:
The default timestamp suggestion is the date and time that the
top diagnostic message in the displayed screen was retrieved
from the FSC system.
12.15.6 Backing Up the Diagnostics Message File
Backing up To store the extended diagnostic database (or part of it) into another
the diagnostics database file, choose the following menu options:
Diag to disk Backup
If you choose this option, you are asked to specify the name of the
backup file. The name must have the following format:
<Disk>:\<Path>\<Filename> (e.g. 'C:\BACKUP\DIAGS').
Software Manual
Notes:
1. The extension '.EXD' is assumed and should not be
specified.
2. You cannot use long file names.
3. The current application name can never be used as a backup
file name.
If the file you specified already exists, you will be asked whether this
file should be overwritten. If you choose to overwrite, the existing
backup file is overwritten by the new one. If you do not want the
existing backup file to be overwritten, you should choose a different
file name and/or location.
Defining After specifying the file name, you need to define the range of the
the range diagnostic messages that should be stored in the backup file. This is
done by specifying the date/time range that the event records must
meet to be backed up. You must enter the first and last date/time of
the event records. You must use the following format:
DD-MM-YY,HH.MM.SS (e.g. '17-02-99,10:00:00'). Please note that
a 24-hour clock should be used. By default, the first time is set to the
time of the first event record stored in the database. The default last
time will always be the same as the first time.
Note:
Incomplete time stamps are allowed. For example, '27-09-00,15'
means the first extended diagnostic data block stored from
September 27, 2000, 3 p.m.
Before records are stored in the backup file, you are asked whether the
records from the current extended diagnostic database should be
deleted. If you confirm, the extended diagnostic database will be
rebuilt after all selected records have been stored in the backup file.
This may take some time, depending on the size of the diagnostic
database.
Software Manual
12.16 Extended Diagnostic Messages
Extended This section lists the diagnostic messages per module type. As a
diagnostics reference, error codes are listed as well as the type of message:
• E: Error which caused the FSC system to shut down or prevent
its start-up.
• W: Warning, which indicates that a problem has been detected
that allows the FSC system to continue operation (for a limited
time period).
• M: Message, which provides information on the status of the FSC
system.
Each diagnostic error message includes a description that provides

information about the cause of the problem and how to remedy it. If
this does not work for hardware-related problems, try to resolve the
problem by exchanging modules in the circuitry. If a problem report is
related to a Central Part module, replace the modules of the Central
Part. If a problem is related to I/O modules, check the VBD, vertical
bus, HBD and horizontal bus connections, as well as the power supply
and watchdog wiring.
Diagnostic messages other than those listed below are possible. If

these occur, document the message, the message number and
circumstances as completely as possible, and contact Honeywell
Safety Management Systems B.V. in the Netherlands
(sms-technical-support@honeywell.com).
Software Manual
12.16.2 Messages Not Related to Specific Hardware Modules
Analog output scaling error. (E-88)

A calculation overflow occurred in scaling the value from
engineering units to the 12-bit value for the A/D converter. Check
the calculation of the analog output value in the functional logic
diagrams.
Analog input sensor break alarm. (W-24)

An analog input value is out of its specified range. Use the 'Loop
status' option to determine the tag number (see subsection 12.10).
Check the field wiring and transmitter output.

The CRC retrieved from the FSC system does not match the CRC
of the current project. There is a mismatch between the FSC.INI
configuration file and the connected system and application.
Update the FSC.INI file, or create new COM EPROMs.
Application not yet loaded into RAM. (M-45)

The FSC system does not have an application program loaded yet
and is waiting for the download. Use the download option of FSC
Navigator (see Section 10 of this manual).
Calculation overflow (E-70)

Check the calculation in the functional logic diagrams at the
specified FLD.
Command status buffer overflow. (E-51)

Check that the COM module functions correctly, and if required,
replace it.
Communication failure during OLM (CPU). (E-149)

A communication error has occurred during the on-line
modification check between the Central Parts. Check the
communication cable between the Central Parts.
Corrupted installation file. (E-117)

Rebuild the application files, check the hardware configuration,
translate the application again and reload it.
CPU module failure. (E-30, E-31)

The 10-ms time base is faulty. Replace the CPU module.
Software Manual
Cycle CPU STOP-RUN key switch. (E-27)
This message will always be displayed in combination with an
external communication failure message (E-27).
Device communication error. (W-38)

An external device (SER PC, DCS printer or MMI PC) has stopped
communicating with the FSC system. Check the external device
and the communication table.
Diagnostic data invalid.

This error message appears if any diagnostic data received from the
FSC system is invalid or corrupt, e.g. an illegal time or date format.
Divide by zero (E-71)

Check the calculations in the functional logic diagrams at the
specified FLD.

a) Check if the cable has been plugged in the correct
system.
jumper settings.
speed).
External communication error (E-27)

The communication between the system and the specified FSC
system (system no., COM module, channel) is not correct. Check
the connections of the cable between the systems.
External communication failure. (E-27)

An error was detected in the FSC network check. The on-line
modification check between FSC systems in an FSC network was
not successful.
Illegal argument, e.g. square root of -1 (E-72)

specified FLD.
Software Manual
Illegal counter value (0 .. 8191). (E-74)
specified FLD.
Illegally placed COM module. (E-104...E-107)

The number of communication modules is incorrect, or the jumpers
on one or more communication modules have not been set correctly
(see the FSC Hardware Manual).
Illegally placed VBD module. (E-116, E-118...E-131)

The number of VBD modules is incorrect, or the jumpers on one or
more VBD modules have not been set correctly (see the FSC
Hardware Manual).
Illegal timer value (0 .. 2047) (E-73)

specified FLD.
Incorrect version of 'System Configuration...'. (E-134)

Use the correct version of the 'System Configuration' option of FSC
Navigator (FSC_IO).
Incorrect version of 'Design FLDs…'. (E-135)

Use the correct version of the 'Design FLDs' option of FSC
Navigator (FSCAD).
Incorrect version of 'Translate application.'. (E-137)

Use the correct version of the 'Translate Application' option of FSC
Navigator (FSCCODE, FSCTABLE).
Internal communication failure. (E-26, E-150...E-155,

E-158...E-164, E-167...E-169, E-171)
One Central Part has shut down. If the Central Part does not start
up after several retries, check the following:
− the communication cable has been properly connected.
− there is lead breakage in the communication cable.
− EPROMs on the COM or CPU module of the Central Part that
do not start up.
Jumper setting COM module on system bus not correct. (E-245)

Check the jumper settings on the system bus and communication
module, and put them in the correct positions (see the FSC
Hardware Manual).
Software Manual
Maximum number of I/O faults exceeded. (E-200)
There are too many I/O faults which cause the FSC system to
overload and shut down. This situation may, for example, occur if
there are serious problems with a horizontal bus or if the power
supply to all modules in a rack is lost.
No differences detected in application program. (M-37)

A new application version has been loaded, but no differences in
the functional logic diagrams and hardware configuration were
detected.
Processor module key in IDLE position (M-54)

Software has just been successfully downloaded to the Central Part,
but the key switch on the 10020/1/1 CPU module is still in the
IDLE position. You need to set it to the RUN position before the
Central Part can start up.
Redundant input fault. (E-25)

The maximum on time or the maximum discrepancy time of the
displayed redundant inputs has expired.
Second fault timer expired. (M-21)

The fault that caused the start of the second fault timer has not been
repaired within the interval time between faults. This resulted in the
system shutdown.
Second fault timer started. (W-28)

An error has occurred and the second fault timer has been started.
Repair the error before this timer expires (otherwise a shutdown of
the Central Part will take place).
Shutdown due to I/O error on single I/O section. (E-156, E-157)

An I/O module has been detected faulty by the other Central Part in
the single I/O section, which has resulted in a shutdown of both
Central Parts.
Shutdown due to on-line modification. (M-35)

The Central Part that is running the unmodified software has shut
down due to exchange of software in the other Central Part, which
runs the modified software.
Software Manual
Software shutdown. (M-8)
This message is always reported if the system shuts down as a
result of a severe error detected during the self-test. The reported
error listed above this one in the extended diagnostics is the actual
cause.
Spurious watchdog interrupt. (E-9)

This shutdown can be caused by:
− memory error
− 5 Vdc out of range
− deactivation of ESD input (removed watchdog flat cable)
− program runtime error
The watchdog status is displayed automatically.
System stopped via FSC Navigator. (M-99)

A system stop command was given in FSC Navigator's on-line
environment.
Temperature alarm. (W-23)

The temperature in the FSC system exceeds the configured range.
12.16.3 Vertical Bus Drivers (10001/1/1, 10001/R/1)
Address CP not set correctly (J5/J6 on VBD/SBD). (E-146)

The jumpers for addressing the Central Part are not set correctly.
Check and set the jumpers in the correct position for the specified
Central Part (see the FSC Hardware Manual).
Configuration error. (E-117)

The module has been configured but could not be detected in the
FSC system.
CP address not set correctly (J5/6 on VBD/SBD) or module faulty

(E-145)
The logic on the VBD module cannot be activated. This can be
caused by incorrect jumper setting or due to a faulty module.
Illegal VBD function. (E-22)

Check that the EPROMs have been placed correctly, or translate
and load the application program again.
Software Manual
Module faulty. (E-0...E-53, E-58...E-144)
Check the vertical bus flatcable and the vertical bus terminator. If
the problem persists, replace the VBD module.
VBD correlation test. (E-13)

Check the HBDs, the vertical bus flatcable and the vertical bus
terminator. If the problem persists, replace the VBD module.
VBD, vertical bus or HBD faulty. (E-54...E-57)

Check the HBDs, the vertical bus flatcable and the vertical bus
terminator. If the problem persists, replace the VBD module.
12.16.4 Central Processing Units (10002/1/2, 10012/1/2, 10020/1/1)
Application program corrupted. (E-41, E-44)

A CRC error was detected in the application program during the
start-up check.
EPROM mode: Replace the CPU application EPROMs or the CPU
module.
RAM mode: Download the application. If the fault persists after
download, replace the RAM chips or the CPU
module.
FLASH mode: Download the Central Part software. If the fault
persists after download, replace the CPU module.
Bus error (E-240)

The CPU module tried to access the module indicated above, but it
did not get access. Replace the indicated module above or the CPU
module. If the problem persists, contact Honeywell Safety
Management Systems in The Netherlands.
Communication failure during OLM (COM). (E-2)

Check the communication cable between the Central Parts.
Configuration coprocessor. (E-133)

The coprocessor has been placed and not configured, or it has not
been placed and configured.
CPU address setting (J1,2,3). (E-12)

Set the address of the CPU (10002/1/2) correctly (see the FSC
Hardware Manual).
Software Manual
CPU or COM RAMs/EPROMs faulty. (E-39)
Check the contents of the EPROMs and make sure that all
EPROMs and RAMs on the CPU and COM modules have been
inserted correctly.
CPU module error. (E-230, E-231)

Replace the CPU module.
CPU test error. (E-247...E-255)

The microprocessor is faulty. Replace the CPU module.
Difference found at FLD(s): (M-3)

The system found differences at the specified FLDs during the
on-line modification check. Check that the FLD numbers
correspond with the changes you made.
Error in hardware comparator test. (E-1)

Replace the CPU module.
Memory error. (E-10, E-14...E-19)

Replace the EPROMs on the specified module. If the problem
persists, replace the module.
Module error. (E-241)

No access is possible to the system bus. Replace the CPU module.
No start-up due to different application. (E-5)

Central Parts have different application programs. Reload the
Central Part that has the incorrect application program.
Processor module key in IDLE position. (W-54)

The key switch of the 10020/1/1 Quadruple Processor Module is in
the IDLE position. It needs to be set to the RUN position before the
Central Part can restart.
Shutdown due to faulty temperature sensors. (E-60)

Both temperature sensors on the DBM module are regarded faulty.
Exchange the DBM module.
Start-up not possible. Modify off-line. (M-4)

Changes have been made in the application software, which cannot
be modified on-line (only off-line).
Software Manual
System program corrupted. (E-40, E-53)
A CRC error was detected in the system program during the
start-up check.
EPROM mode: Replace the CPU 10002/A/x memory boards or the
CPU module.
RAM mode: Replace the CPU 10002/A/x memory boards or the
CPU module.
persists after download, replace the CPU module.
12.16.5 Communication Modules (10004/./., 10014/./., 10024/./.,

10008/2/U, 10008/3/P, 10018/2/U)
Application program corrupted. (E-19)

A CRC error was detected in the application program during the
start-up check.
EPROM mode: Replace the communication EPROMs or the COM
module.
RAM mode: Replace the communication EPROMs or the COM
module.
persists after download, replace the COM module.
Bad EPROM checksum (E-3)

The firmware of the FSC-SMM (10008/2/U or 10018/2/U) is
corrupt. Reprogram the EPROMs or download the firmware.
COM module not responding. (E-59)

The FSC-SMM (10008/2/U or 10018/2/U) does not respond to
initialization commands. Check the jumpers and the EPROMs.
Communication failure during configuration check. (E-45)

A timeout occurred during the configuration check between FSC
systems. Check the system cables.
Communication failure during OLM check. (E-45)

A timeout occurred during the on-line modification check between
FSC systems. Check the system cables.
Software Manual
Communication overrun (E-58)
Too many digital input variables (I) and/or binary input variables
(BI) are being sent, or were sent, to the FSC system during a period
of time. The maximum is 100 per second.
Make sure that the number of I and BI variables sent to the FSC
system does not exceed 100 per second.
Communication program corrupted. (E-42)

Replace the EPROMs on the COM modules of the Central Part that
reports the faults, or check for bent EPROMs pins.
COM software version mismatch. (E-20)

Translate and load the application program again.
Error in self-test COM module. (E-220)

Replace the specified COM module. In case of a 10014/./. or
10018/./. module, make sure that you also reload the software into
flash memory.
Exception test failed or illegal exception (E-4)

Replace the module. In case of a 10014/./. or 10018/./. module,
make sure that you also reload the software into flash memory.
If the problem persists, contact HSMS.
Firmware communication error (E-8)

Check the connections with the UCN and the communication
statistics of the UCN. If this is not the source of the problem,
replace the module. In case of a 10014/./., 10018/./., or 10024/./.
module, make sure that you also reload the software into flash
memory.
Hardware comparator failure. (E-1)

Replace the specified COM module. In case of a 10014/./.,
10018/./., or 10024/./. module, make sure that you also reload the
software into flash memory.
Incompatible FSC-FSC configuration. (E-44)

The FSC-FSC communication block sizes for two FSC systems are
not identical. Translate and load the application program again, or
modify off-line.
Incompatible FSC-FSC variable allocation. (E-44)

Tag numbers have changed during the last modification of the
application software. You can only add or delete tags during on-
line modification.
Software Manual
Incompatible variable allocation. (E-44)
Tag numbers have changed during the last modification of the
application software. You can only add or delete tags during on-
line modification.
MEM - COM incompatible Central Part number. (E-6)

The Central Part numbers in the CPU application and COM
application do not match. Make sure that all EPROMs have been
placed in the correct Central Part.
MEM - COM incompatible run mode. (E-6)

EPROMs on the CPU and COM module are not compatible with
regard to the power-on mode. Translate the application again, and
replace all EPROMs on the CPU module and the COM modules.
MEM - COM incompatible system number. (E-6)

EPROMs on the CPU and COM module contain different system
numbers. Make sure that the correct EPROMs have been placed on
the modules.
Missing OS-9 entry point (E-27)

Recover the module and reload the Personality Image (PI). If the
problem persists, replace the module. In case of a 10014/./.,
Module faulty. (E-11, E-13)

Replace the COM module In case of a 10014/./., 10018/./., or
flash memory.
Parity error (E-29)

Recover the module and reload the Personality Image (PI). If the
problem persists, replace the module. In case of a 10014/./.,
Program communication EPROMs or wrong application files on

disk.
The communication EPROM files do not match the application
files on your hard disk. This will typically happen in RAM mode if
you have implemented modifications that require the EPROMs to
be reprogrammed, but you have not done that. Make sure that you
program the communication EPROMs before continuing.
Software Manual
RAM error. (E-25, E-27)
Replace the COM module. In case of a 10014/./., 10018/./., or
flash memory.
Selftest failure. Test ID: <##> (E-1)

The FSC-SMM (10008/2/U or 10018/2/U) has detected a problem
while performing its power-up self-tests. Replace the module. In
case of a 10014/./., 10018/./., or 10024/./. module, make sure that
you also reload the software into flash memory.
Software assertion. Crashcode: <###> (E-11)

Contact HSMS. Call up the MAINT SUPPORT detail display on
the Universal Station for additional information.
System program corrupted. (E-18)

A CRC error was detected in the system program during the
start-up check.
EPROM mode: Replace the communication EPROMs or the COM
module.
RAM mode: Replace the communication EPROMs or the COM
module.
persists after download, replace the COM module.
Wrong EPROMs or jumpers (J2, J3) on COM module set

incorrectly. (E-6)
The EPROM size and jumper setting do not match (see the FSC
Hardware Manual for jumper settings).
12.16.6 PlantScape Interface Modules (10018/E/E, 10018/E/1)
COM software version mismatch (E-18)

Contact HSMS if this problem occurs.
Configuration error (E-19)

The configured number of DCS addresses has exceeded the
maximum (12,000). Reduce the number of configured DCS
addresses.
Software Manual
Configuration error (E-20)
The IP address for channel A has not been specified or it has been
set to 0.0.0.0 (which is an illegal value). Make sure that you
configure a valid IP address for channel A.
Communication overrun (E-58)

Too many digital input variables (I) and/or binary input variables
(BI) are being sent, or were sent, to the FSC system during a period
of time. The maximum is 100 per second.
Make sure that the number of I and BI variables sent to the FSC
system does not exceed 100 per second.
External communication failure (E-142, E-143)

The communication protocol could not recognize a received
message. If the problem persists, contact HSMS.
Program execution assertion (E-0…E-17, E-21…E-141,

E-144…E-218, E-220…E-255)
Contact HSMS if this problem occurs.
Too many SER-enabled variables configured (E-219)

Processing the SER events takes longer than the configured FSC
application cycle time. Reduce the number of SER-enabled
variables until the error does not appear again.
12.16.7 Watchdog Modules (10005/1/1)
Illegally placed watchdog module. (E-108...E-115)

The number of watchdog modules is incorrect, or the jumpers on
one or more watchdog modules have not been set correctly (see the
FSC Hardware Manual).
Maximum runtime test failed. (E-49)

Replace the watchdog module.
Minimum runtime test failed. (E-48)

Module faulty (E-0...E-38)

Software Manual
12.16.8 Diagnostic and Battery Modules (10006/./.)

FSC system.
Error in temperature sensor. (E-4...E-7)

The specified temperature sensor is regarded faulty. Replace the
DBM module.
Error in voltage reference check. (E-1...E-3)

The reference voltage to check the functionality of the A/D
converter for the temperature sensors is faulty.
Illegally placed DBM module. (E-132)

The number of DBM modules is incorrect, or the jumpers on one or
more DBM modules have not been set correctly (see the FSC
Hardware Manual).
Jumper set incorrectly or fuse blown. (W-8)

The battery voltage is not correct. Make sure that the jumper is set
to the 'battery on' position, and check the fuse.
Sensor temperature difference out of range. (E-9, E-10)

The temperature difference between the two sensors exceeds 5°C
(9°F). Replace the DBM module.
Temperature out of range. (M-20)

Check the ambient temperature of the Central Part. If the
temperature is within the range, replace the DBM module.
12.16.9 Single Bus Drivers (10007/1/1)
Address CP not set correctly (J5/J6 on VBD/SBD). (E-146)

The jumpers for addressing the Central Part are not set correctly.
Check and set the jumpers in the correct position for the specified
Central Part (see the FSC Hardware Manual).
Address CP not set correctly (J5/6 on VBD/SBD) or module

faulty. (E-145)
The logic on the SBD module cannot be activated. This can be
caused by incorrect jumper settings or a faulty module.
Software Manual
FSC system.
Illegally placed SBD module. (E-116, E-118...E-131)

The number of SBD modules is incorrect, or the jumpers on one or
more SBD modules have not been set correctly (see the FSC
Hardware Manual).
Module faulty. (E-0...E-49)

Replace the SBD module.
12.16.10 Horizontal Bus Drivers (10100/./.)
HBD addressing error. (E-98)

Check the address setting on the HBD connectors of all HBD
modules. Make sure that the vertical bus flatcable in the VBD and
HBDs has been inserted correctly.
HBD addressing error or other HBD fault. (E-99)

Check the address setting on the HBD connectors of all HBD
modules. Make sure that the vertical bus flatcable in the VBD,
HBDs and bus terminator has been inserted correctly. If the
problem persists, replace the HBD module.

Replace the electronic part of the HBD module.
12.16.11 Digital Input Modules 10101/./.
Input compare error. (E/W-99)

A discrepancy was detected between the inputs scanned via Central
Part 1 and Central Part 2. Check the input signal for fast transients,
or replace both modules.
Module faulty. (E/W-0...21)

One or more channels of the input module are faulty. Replace the
module.
Software Manual
12.16.12 Analog Input Modules 10102/./.
Calibration error. (E/W-4...20)

Calibrate the analog input module using the calibration feature of
FSC Navigator (see subsection 12.13).
Capacitor test. (E/W-0...3)

The leakage current of the input circuitry is too high. Replace the
module.
Input compare error. (E/W-99)

A discrepancy was detected between the inputs scanned via Central
Part 1 and Central Part 2. Check the input signal on fast transients,
or replace both modules.
Module faulty. (E-21...E-23, E-28)

Check the calibration. If it is not possible to calibrate, then replace
the 10102/1/1 or 10102/1/2 module.
Voltage output short circuit or module faulty. (E/W-24...27)

Make sure that the 26 Vdc output actually provides approx. 26 V. If
it does not, check for short-circuiting, or replace the 10102/1/1 or
10102/1/2 module. If the transmitter current is > 25 mA, change the
maximum current setting to < 25 mA.
12.16.13 Analog Input Module 10105/2/1
Communication overrun. (E-58)

Too many I/BI variables with location 'COM' have been written to
the CPU during one application cycle. The maximum number of
variables that can be written is 50.
Internal power-down. (E-1, E-4, E-5, E-9, E-10, E-12, E-56,

E-59...E-61, E-88, E-91...E-93, E-136)
There is no internal voltage. Check the power supply to the
module. If no problem can be found, replace the module.
Module faulty, voltage monitoring channel. (E-196)

There is no external voltage.
Software Manual
Module faulty. (all other codes)
The hardware is defective. Replace the module.
12.16.14 Digital Input Module 10106/2/1
Earth fault detected. (E-238)

Check the field wiring for earth faults. If no problem can be found,
replace the module.
Internal power-down. (E-5, E-97, E-98, E-123, E-243)

There is no internal voltage. Check the power supply to the
module. If no problem can be found, replace the module.
Lead breakage. (E-45...E-60)

Check the field wiring for lead breakage. If no problem can be
found, replace the module.
Note:
The number of reported lead breakage messages for
10106/2/1 modules is limited to three per application cycle.
This means that if there are multiple lead breakages for one
module, only the first three affected channels will be reported.
If multiple lead breakages occur at multiple 10106/2/1
modules, the first three of each module will be reported
(assuming the lead breakages do not occur in the same
application cycle). After a system reset, only the first three
affected channels of the first 10106/2/1 module will then be
reported.
Short-circuit. (E-61...E-76)
Check the sensor and field wiring for short-circuiting. If no
problem can be found, replace the module.
Module faulty. (all other codes)

The hardware is defective. Replace the module.
Software Manual
12.16.15 Digital Output Modules 10201/./.
External power-down complete module. (W-17)

Check the fuses or circuit breakers for the external power supply,
or check the watchdog signal.
External power-down channels 1, 2, 3, 4. (W-15)

Check the fuses or circuit breakers for the external power supply to
channels 1 to 4, or check the watchdog signal.
External power-down channels 5, 6, 7, 8. (W-16)

Mismatch between expected and actual output value. (E/W-13)

The actual output status is not identical to the expected value that
was calculated by the application program. Replace the module.
Module faulty. (E/W-0...4)

A fault was detected in the common part of the output module.
Replace the module.
Output channel cannot be switched off. (E/W-5...12)

Replace the module.
Output short circuit. (W-14)

Check the actuator and field wiring for short-circuiting.
SEC. SWITCH-OFF channel defective. (W-18)

The output channel used for the secondary switch-off cannot be
switched on. Replace the module.
Software Manual
12.16.16 Digital Output Module 10203/1/2
External power-down complete module. (W-15)



Replace the module.

Replace the module.

Check the actuator and field wiring for short-circuiting. If no
12.16.17 Analog Output Modules 10205/./.
Mismatch between expected and actual output value. (E/W-10,

E/W-11)
Check for open loop on the analog output. Check the calibration, or
replace the module.

Replace the module.
Software Manual
External powerdown channels 1, 2, 3, 4. (W-15)

Mismatch between expected and actual output. (E/W-13)


Replace the module.

Replace the module.

Check the actuator and field wiring for short-circuiting.
External power-down. (E-8)


Module faulty. (W-0...W-2)

Replace the module.

Replace the module.

Software Manual
Current detected in output loop. (E-10)

Current was detected in an output loop, even though the channel is
switched off. Check for short-circuiting between the channels in the
field.
External power-down. (E-11)

Line-monitor circuit faulty. (E-7...E-9)

The circuitry that senses the output loop current is faulty. Replace
the module.

Replace the module.
Open loop or line monitor circuit faulty. (W-13)

Check the field wiring for lead breakage, or check the lead
breakage current setting (see the FSC Hardware Manual). If no

Replace the module.

Output short circuit or output cannot be switched on. (W-6)

Software Manual
External power-down. (W-12)

External power-down channels 1, 2. (W-10)

channels 1 and 2, or check the watchdog signal.
External power-down channels 3, 4. (W-11)

channels 3 and 4, or check the watchdog signal.


Replace the module.

Replace the module.

Correlation between channels. (E-3, E-4, E-30)

The output channel cannot be switched on or off independently of
the other channel(s). Replace the module.
Current detected in output loop. (W-5, E-6, E-29, E-31, E-33,

E-34)
Current was detected in an output loop, even though the channel is
switched off. Check for short-circuiting between the channels in the
field.
Software Manual
External power-down complete module. (W-23, W-24)
Line-monitor circuit faulty. (E-8, W-17...W-19)

The circuitry that senses the output loop current is faulty. Replace
the module.
Module faulty. (E-1, E-2, E-10, E-11, E-12, E-25)

Replace the module.
Open loop or line-monitor circuit faulty. (W-20...W-22, W-26)

Check the field wiring for lead breakage, or check the lead
breakage current setting (see the FSC Hardware Manual). If no
Output channel cannot be switched on. (E-14)

The output is de-energized and cannot be energized, if required.
Replace the module.
Output channel cannot be switched off. (E-13)

The output is energized and cannot be de-energized, if required.
Replace the module.
Output is incorrectly switched on. (E-7)

The actual output status is 'On', although it should be 'Off'
according to the application program. Replace the module.
Output short circuit. (W-9, W-15, W-16)

12.16.23 Watchdog Repeater Modules (10302/./.)

Check the 24 Vdc supply, 5 Vdc supply, and the incoming
watchdog. If no problem can be found, replace the module.
Software Manual
12.17 Error Messages
Address allocation of I/O variables not correct.

You have added new I/O, but the application has not been
translated. Translate the application again and load it, or perform an
on-line rebuild.

The CRC retrieved from the FSC system does not match the CRC
of the current project. There is a mismatch between the FSC.INI
configuration file and the connected system and application.
Update the FSC.INI file, or create new COM EPROMs.
Application versions in database and FSC system do not match.

You have translated your application without loading it to the FSC
system. The application in the database may differ from the
application in the FSC system.
Cannot be forced.
You want to force a variable that is not force-enabled according to
the database.
Cannot be written.
You want to write to a variable that is not write-enable according to
the database.
Cannot find tag number.

You have entered a valid variable type, but the tag number is not
found in the database. Enter a correct and existing tag number.
Please note that tag numbers are case-sensitive, which means that
'Tag' is not the same as 'TAG'.
Cannot receive PID update values.

This happens if the communication with the FSC system was not
successful. Correct this by trying it again, or check the hardware of
the connection between the FSC system and the user station.
Cannot update diagnostic configuration file.

The DIAGEXT.CFG file could not be created or written to. Check
the available disk space and file attributes (read-only?).
Software Manual
Command not allowed.
You have entered a force command, but the FSC system does not
accept it because it is not allowed.
Communication with too many retries.

a) Check if the communication cable is terminated correctly, has
no broken wires, etc.
b) Decrease the communication speed as the length of the
communication cable may be too long for the selected
communication speed.
Corrupt extended diagnostic data file(s).

Delete the diagnostic index files (.EXR and .EXT).

a) Check if the cable has been plugged into the correct
system.
correctly. If they are, verify the EPROMs.
jumper settings.
speed).
Error updating extended diagnostic data file(s).

Delete <application name>.EXT in the application folder. The
database will be rebuilt.
Force enable input not activated.

You attempted to force a variable, but the Force Enable key switch
has not been activated, which means that no force commands are
accepted. Forces are only allowed when this key switch is
activated.
FSCVIEW.MSG missing
The message file FSCVIEW.MSG is not present in the FSC
Navigator installation folder. Re-install FSC Navigator.
Illegal variable type.

You have entered an invalid variable type. Valid variable types are:
I, O, AI, AO, BI, BO, C, T, M, R.
Software Manual
Invalid destination address or system number not correct.
You tried to communicate with an FSC system that is loaded with a
different application and/or system number.
Maximum output clamp must be higher than minimum output

clamp.
While editing PID parameters, you attempted to specify an output
high clamp that is smaller than the output low clamp. Correct this
by entering a smaller output low clamp or a larger output high
clamp.
No Development System communication port configured for

<PC interface>
You tried to communicate via a communication port in the FSC
user station that has not been configured in the FSC system. For
example, the FSC user station uses RS-485, and FSC only has an
RS232 port, or vice versa.
No EPROMs programmed yet for COM module.

You tried to communicate with an FSC system for which no
communication EPROMs have been programmed yet.
NO INPUT CHANNEL
The selected rack and position contains no input module. Make
sure that you enter correct values for rack location.
NO OUTPUT CHANNEL
The selected rack and position contains no output module. Make
sure that you enter correct values for rack location.
No PID screens have been created.

You tried to enter the graphic PID status screen, but no PIDs have
been created yet. Correct this creating a PID screen, and select at
least one PID.
No records of this type in database.

You have entered a valid variable type, but no FSC variables of
that type were found in the current database.
Software Manual
No response from FSC system.
a) Check if the cable is plugged into the correct communication
port of the FSC user station and/or the FSC system.
b) Check if the EPROMs on the COM module have been placed
c) Check all modules on the system bus for correct EPROMs and
jumper settings.
Power-on modes in database and FSC system do not match.

Check if the power-on mode in the database is the same as in the
FSC system (RAM or EPROM mode).
Proportional band NOT in the range.

While editing PID parameters, you attempted to specify a
proportional band which is not in range (–327.67 to 327.67).
Correct this by entering a value in the correct range.
Rate time NOT in the range.

While editing PID parameters, you attempted to specify a rate time
which is not in range (0.0 to 3276.7). Correct this by entering a
value in the correct range.
Reset time NOT in the range.

While editing PID parameters, you attempted to specify a reset
time which is not in range (0.00 .. 327.67). Correct this by entering
a value in the correct range.
Sample time NOT in the range.

While editing PID parameters, you attempted to specify a sample
time which is not in range (0.1 .. 3276.7). Correct this by entering a
value in the correct range.
Screen cannot be selected for PID overview.

You have entered a sheet number in the range to S1-S999, but these
sheets cannot be selected for PIDs (these screens are assigned to
FLD status sheets). Please enter a screen number in the range of
1-99.
Screen has NOT been selected for PID display.

You have entered a screen number which is not defined as a PID
screen. Correct this by entering a defined PID screen number or
select this number for a PID screen. To do this, choose the 'Edit
screen' option in the status main menu. Enter the desired screen
number and create a PID screen.
Software Manual
Screen has NOT been selected for status display.
You have entered a screen number which was not defined as a
status screen. The selected screen is a PID screen or it has not been
defined at all.
Setpoint Low must be smaller than setpoint High.

While editing PID parameters, you attempted to specify an setpoint
high clamp that is smaller than the setpoint low clamp. Correct this
by entering a smaller setpoint low clamp or a larger setpoint high
clamp.

installed.
If you use the 07177 interface modules to communicate with the
FSC system, a special communication driver needs to be installed
on the FSC user station. This driver has either not been installed, or
it has not been configured correctly (e.g. incorrect module address).
For details on the 07177 communication driver refer to section 2.3
of this manual.
Version of message file and program do not match.

The message file FSCVIEW.MSG is present in the FSC Navigator
installation folder, but its version does not match the version of
FSC Navigator.
Software Manual
Software Manual
Fail Safe Control
Section 13:
Safety Checker
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Section 13: Safety Checker
13.1 Introduction .................................................................................................. 13-1
13.2 Safety Checker Operation............................................................................ 13-3
13.3 Reviewing Safety Inconsistencies .............................................................. 13-6
13.4 Log File ......................................................................................................... 13-7
13.5 Safety Relation of FLD Symbols.................................................................. 13-8

13.5.2 Compare Functions ...................................................................................................... 13-10
13.5.3 Calculation Functions ................................................................................................... 13-12
13.5.4 Mathematical Functions ............................................................................................... 13-13
13.5.5 Counters and Registers ............................................................................................... 13-14
13.5.6 Constants and Signal Conversions .............................................................................. 13-15
13.5.7 Function Blocks ............................................................................................................ 13-15
13.5.8 Equation Blocks ........................................................................................................... 13-16
13.5.9 PIDs.............................................................................................................................. 13-16
13.5.10 Timers .......................................................................................................................... 13-16
13.5.11 I/O Symbols.................................................................................................................. 13-18
13.5.12 Flip-Flops...................................................................................................................... 13-19
13.6 Error Messages .......................................................................................... 13-20
Software Manual
Section 13: Safety Checker i
FIGURES
Figure 13-1 Project menu with Safety Checker option ................................................................. 13-2
Figure 13-2 Calculating the safety relation of FLDs ..................................................................... 13-3
Figure 13-3 FLD with safety relations displayed .......................................................................... 13-6
Figure 13-4 Safety relation inconsistency warning....................................................................... 13-6
TABLES
Table 13-1 Logical functions ....................................................................................................... 13-8

Table 13-2 Compare functions .................................................................................................. 13-10
Table 13-3 Calculation functions ............................................................................................... 13-12
Table 13-4 Mathematical functions ........................................................................................... 13-13
Software Manual
ii Section 13: Safety Checker
Section 13 – Safety Checker
13.1 Introduction
Safety Checker The Safety Checker is a static analysis tool that helps engineers verify
the safety consistency of an FSC application. If the Safety Checker
detects any inconsistencies in the application that affect its safety
integrity, it will report them on screen and store them in a log file (see
subsection 13.4). This allows engineers to correct any safety-related
design errors at an early stage, and verify that the safety application
suits its projected purpose. The Safety Checker supports the
verification process that is part of the safety lifecycle as laid down in
IEC 61508 and ANSI/ISA S84.01.
An FSC control application can only be considered safe if all its

outputs are safety-related and the entire logic path leading to the
outputs is safety-related as well. An inconsistent configuration can
lead to hazardous situations. The Safety Checker will alert the
programmer to these inconsistencies. If, for example, an analog input
for a pressure trip has not been configured as safety-related, but the
output that drives the shutdown valve has been configured safety-
related, an inconsistency is detected in the loop and the programmer is
alerted. Conversely, an output that drives a non safety-critical function
but is configured as being safety-related, could display unwanted
behavior if a fault is detected in the output channel.
The Safety Checker will highlight the safety-critical functions in an
FSC application.
An additional function of the Safety Checker reports any off-sheet

references to a destination FLD with a lower number than the source
FLD, which might be design errors.
The Safety Checker helps you design the safety application in such a
way that it suits its projected purpose.
Software Manual
Section 13: Safety Checker 13-1
Definitions The following definitions are important for the Safety Checker:
Safety-related A design property of an item in which the specified failure mode is

(SR) predominantly in a safe direction. FSC I/O variables may be
safety-related, depending on their type and their safety relation setting
(see Section 4 of this manual).
Non safety-related A design property of an item in which the specified failure mode is
(NSR) not predominantly in a safe direction. Any input from any DCS
system is by definition non safety-related.
Inverted safety-related Safety-related signals that are inverted in the FLD (using the inverter
(ISR) symbol) are regarded 'inverted safety-related' (ISR).
Starting the Important!

Safety Checker Make sure that you always translate the application before
starting the Safety Checker. If you do not, the Safety Checker
may not be able to perform a correct analysis of the application
FLDs. If any errors are reported during translation, make sure
that you correct them before starting the Safety Checker.
For details on translating an application refer to Section 8 of
this manual ("Translating an Application").
The Safety Checker option of FSC Navigator can be called in two

ways:
• Menu bar: Project / Safety Checker (see Figure 13-1)

• Navigation area: FSC Safety Compliance / Safety Checker
Figure 13-1 Project menu with Safety Checker option
Software Manual
13-2 Section 13: Safety Checker
13.2 Safety Checker Operation
Operation After you start the Safety Checker, it will process all FLDs in the
application in ascending order (i.e. from FLD with the lowest number
to the FLD with the highest number). The safety-checking process
may take some time, depending on the number and complexity of the
FLDs in the application. During the process, the message bar will
indicate which FLD is being checked.
Figure 13-2 Calculating the safety relation of FLDs
Process steps The safety checking process for an FLD consists of three steps, which
are repeated for each FLD in the application:
1. Initialization of the FLD to be checked.
2. Actual analysis of the FLD.
3. Logging of any errors and warnings.
Each of these steps is discussed in more detail below.
Software Manual
FLD initialization Before an FLD can be analyzed, it needs to be properly initialized.
All the symbols on the FLD are processed, as well as its sheet
transfers. The safety relation of all inputs and outputs on the FLD are
retrieved, their connection lines are identified, and the general FLD
syntax is checked.
If the FLD initialization has been completed successfully, the Safety
Checker will proceed with the actual safety analysis.
If any syntax errors are detected in an FLD, they are stored in the log
file, and the FLD will not be analyzed. The Safety Checker will then
move on to the next FLD, except in case of the following error
messages:
− Application not translated correctly.
− Attempting to write 'Undef' value to I/O datafile.
− FLD is corrupted: <FLD number>.
− Forcing symbols to non safety-related status failed.
− Illegal symbol for this block type.
− Project not entirely calculated.
− Undefined symbol found.
If any of these errors are detected, the safety checking process will be
aborted altogether, and you will return to the FSC Navigator main
screen.
Notes:
Even though the Safety Checker will detect a number of FLD
syntax errors, it is strongly recommended that you always
translate an application before starting the Safety Checker. Any
errors reported during the translation should be corrected before
proceeding with the Safety Checker.
For details on translating an application refer to Section 8 of this
manual ("Translating an Application").
Software Manual
FLD analysis The Safety Checker checks the following two things:
1. Safety inconsistencies in the logic path leading to each output in
the FLD. An error will be reported if a safety-related (SR) output
is only controlled by non safety-related (NSR) signals, which is
unacceptable from a safety point of view. A warning will be
reported if an inverted safety-related (ISR) signal connects to a
safety-related output, which may be wanted behavior, but might
also be a design error.
2. Off-sheet references to a destination FLD with a lower number
than the source FLD. Even though such off-sheet references need
not be errors, a warning is reported to draw your attention to
them. They may be wanted behavior, but might also be design
errors.
Error logging All problems found during the safety check are reported and stored in
a log file, which can be retrieved and printed for later use (see
subsection 13.4).
Software Manual
13.3 Reviewing Safety Inconsistencies
Reviewing safety After you performed a safety check, you can start the FLD design
inconsistencies editor and open an FLD of the application that was checked. All
safety-related paths leading to an output will be shown in the color
that has been set for safety-related items (red by default).
Non safety-related paths are shown in the normal color (black by
default). Any safety inconsistencies are immediately clear, since some
of the lines leading to the safety-related output will have a different
color than the output itself (see bottom I/O connection in Figure 13-3
below).
Figure 13-3 FLD with safety relations displayed
Please note that in case of an inverted safety-related (ISR) path, only a

warning is generated because it may be wanted behavior, but might
also be a design error (see Figure 13-4).
Red
Red Black
=1 SR output
ISR
Figure 13-4 Safety relation inconsistency warning
Software Manual
13.4 Log File
Log file All problems found during the safety check are reported and stored in
a log file for later reference. The Safety Checker log file is called
<Application name>.SAF, and is located in the project folder. It
contains all messages and errors that were generated during the safety
checking process. The log file can be viewed and printed using the
'View Log' option of FSC Navigator (see Section 9 for details).
The Safety Checker log file may look something like this:
Safety Checker log file: E:\FSC\DEMO_1 Date: 24-8-2000 Time: 16:12
ERROR FLD number: 102. Safety relation inconsistency: O 53PT-920.H

ERROR FLD number: 102. Safety relation inconsistency: O 53PT-920.L
ERROR FLD number: 102. Safety relation inconsistency: O 53FT-700.H
ERROR FLD number: 102. Safety relation inconsistency: O 53FT-700.L
WARNING FLD number: 104. FLD reference detected to a lower FLD number : R 104_103_2
WARNING FLD number: 108. FLD reference detected to a lower FLD number : M 108_103_1
ERROR FLD number: 121. Safety relation inconsistency: O UNIT1
MESSAGE Number of warnings generated during safety calculation : 8
MESSAGE Number of errors detected during safety calculation : 5
For details on the error messages refer to subsection 13.6.
Software Manual
13.5 Safety Relation of FLD Symbols
Safety relation This section describes the safety relation of all symbols that can be
used in the functional logic diagrams (FLDs). For most symbols, the
safety relation of the output parameters depends on the safety relation
of the input parameters. A table has therefore been included for each
symbol which defines the dependencies between the safety relation of
the output parameters and that of the input parameters.
The abbreviations in the tables have the following meaning:

– SR = safety-related
– NSR = non safety-related
– ISR = inverted safety-related
– X = does not matter
13.5.1 Logical Functions
Logical functions This section describes the safety relation of the logical functions that
are available in FLDs.
Table 13-1 Logical functions

AND functions OR functions Inverter functions
AND gate OR gate INVERTER
AND filter XOR gate
NAND gate NOR gate
XNOR gate
Software Manual
AND gate The safety relation of the AND gate is as follows:
a n d
a
SR X SR
. & d NSR NSR NSR
ISR NSR NSR
n
ISR ISR ISR
AND filter The safety relation of the AND filter is as follows:
d a n e
d
SR X X SR
a
& e X SR X SR
. else NSR
n
NAND gate The safety relation of the NAND gate is as follows:
a n d
a
SR X ISR
. & d ISR ISR SR
ISR NSR NSR
n
NSR NSR NSR
OR gate The safety relation of the OR gate is as follows:
a n d
a
SR NSR NSR
. >1 d ISR X ISR
NSR NSR NSR
n
SR SR SR
XOR gate The safety relation of the XOR gate is as follows:
a b c
a
SR SR SR
=1 c ISR ISR SR
SR ISR ISR
b
NSR X NSR
Software Manual
NOR gate The safety relation of the NOR gate is as follows:
a n d
a
SR NSR NSR
. >1 d ISR X SR
NSR NSR NSR
n
SR SR ISR
XNOR gate The safety relation of the XNOR gate is as follows:
a b c
a
SR SR ISR
=1 c ISR ISR ISR
SR ISR SR
b
NSR X NSR
INVERTER The safety relation of the INVERTER is as follows:
a b
a 1 b SR ISR
ISR SR
NSR NSR
13.5.2 Compare Functions
Compare functions This section describes the safety relation of the compare functions
that are available in FLDs.
Table 13-2 Compare functions

Equal functions Greater than functions Smaller than functions
EQUAL gate GREATER THAN gate LESS THAN gate
GREATER THAN OR LESS THAN OR

EQUAL gate EQUAL gate
Software Manual
EQUAL gate (EQ) The safety relation of the EQUAL gate (EQ) is as follows:
a b c
a
SR SR SR
= c X NSR NSR
GREATER THAN
gate (GT) The safety relation of the GREATER THAN gate (GT) is as follows:
a b c
a
SR SR SR
> c X NSR NSR
GREATER THAN OR The safety relation of the GREATER THAN OR EQUAL gate (GTE)
EQUAL gate (GTE) is as follows:
a b c
a
SR SR SR
> c X NSR NSR
LESS THAN gate

(LT) The safety relation of the LESS THAN gate (LT) is as follows:
a b c
a
SR SR SR
< c X NSR NSR
LESS THAN OR The safety relation of the LESS THAN OR EQUAL gate (LTE) is as
EQUAL gate (LTE) follows:
a b c
a
SR SR SR
< c X NSR NSR
Software Manual
13.5.3 Calculation Functions
Calculation This section describes the safety relation of the calculation functions
functions that are available in FLDs.
Table 13-3 Calculation functions

ADDITION MULTIPLY
SUBTRACT DIVIDE
ADDITION gate
(ADD) The safety relation of the ADDITION gate (ADD) is as follows:
a n d
a
SR SR SR
. + d X NSR NSR
SUBTRACT gate
(SUB) The safety relation of the SUBTRACT gate (SUB) is as follows:
a b c
a
SR SR SR
- c X NSR NSR
MULTIPLY gate
(MUL) The safety relation of the MULTIPLY gate (MUL) is as follows:
a b c
a
SR SR SR
X c NSR X NSR
Software Manual
DIVIDE gate (DIV) The safety relation of the DIVIDE (DIV) is as follows:
a b c
a
SR SR SR
_.
. c NSR X NSR
13.5.4 Mathematical Functions
Mathematical This section describes the safety relation of the calculation functions
functions that are available in FLDs.
Table 13-4 Mathematical functions

SQUARE ROOT NATURAL LOGARITHM
SQUARE EXPONENT
SQUARE ROOT The safety relation of the SQUARE ROOT gate (SQRT) is as
gate (SQRT) follows:
a b
a X b SR SR
NSR NSR
SQUARE gate (SQR) The safety relation of the SQUARE gate (SQR) is as follows:
a b
2
a X b SR SR
NSR NSR
EXPONENT gate
(EXP) The safety relation of the EXPONENT gate (EXP) is as follows:
a b
X SR SR
a e b
NSR NSR
Software Manual
NATURAL
LOGARITHM gate The safety relation of the NATURAL LOGARITHM gate (LN) is as
(LN) follows:
a b
a ln(x) b SR SR
NSR NSR
13.5.5 Counters and Registers
Counters and This section describes the safety relation of the counters and registers
registers in FLDs.
Counters The safety relation of counters is as follows:
a CU a b c d e f g h
=Max f
b
CD X X X X ISR SR SR ISR
c S
g X X ISR SR SR NSR SR NSR
Counter X X ISR SR NSR NSR SR NSR
d 0 h
e R else NSR NSR NSR
Inputs that are not connected are considered safety-related.
Registers The safety relation of registers is as follows:

a CU
a b c d e f
b
CD
f
X X X X ISR SR
c L
X X ISR SR X SR
d Register
else NSR
e C T
Software Manual
13.5.6 Constants and Signal Conversions
Constants and This section describes the safety relation of constants and signal
signal conversions conversions in FLDs.
Constant value The safety relation of constant values is as follows:
value b
T Value
b X SR
Constant boolean The safety relation of constant booleans is as follows:
value b
1
X ISR
Signal conversion The safety relation of signal conversions is as follows:
S T
S SR SR
T NSR NSR
Function blocks The contents of the function block and the safety relation of all inputs
leading to that function block define de safety relation of a function
block output. Each function block is recalculated with the appropriate
input specifications. All inputs that are not connected are regarded
safety-related.
Software Manual
Equation blocks The safety relation of equation blocks is as follows:
A B
SR SR
A EB B
NSR NSR
13.5.9 PIDs
PIDs The safety relation of PIDs is as follows:
a I a b c d e f
PID X X X X X NSR
b
S
O f
c CS The output of a PID is always regarded non safety-related.
d M PID controllers may not be used for fail-safe functions.
e OM
13.5.10 Timers
Timers This section describes the safety relation of timers in FLDs.
Cycle timers The safety relation of cycle timers is as follows:
a b
a b
SR SR
ISR SR
NSR NSR
Software Manual
Pulse timers The safety relation of pulse timers is as follows:
S N S R Q u
Q
SR X SR NSR
R t= u
X ISR SR NSR
else NSR NSR
S N Q
a The 'u' output of the timer is regarded non safety-related as it is
R Base u
used for indication purposes only.
Pulse retriggerable The safety relation of pulse retriggerable timers is as follows:

timers
S R S R Q u
Q
SR X SR NSR
R t= u
X ISR SR NSR
else NSR NSR
S R Q
R Base u
used for indication purposes only.
Delayed-on timers The safety relation of delayed-on timers is as follows:
S t 0 S R Q u
Q
SR X SR NSR
R t= u
X ISR SR NSR
else NSR NSR
S t 0 Q
R Base u used for indication purposes only.
Software Manual
Delayed-on
memorize timers The safety relation of delayed-on memorize timers is as follows:
S
M S R Q u
t 0 Q
X ISR SR NSR
R u
t= else NSR NSR
S
M The 'u' output of the timer is regarded non safety-related as it is
t 0 Q
a used for indication purposes only.
R u
t=
Delayed-off timers The safety relation of delayed-off timers is as follows:
S 0 t S R Q u
Q
X ISR SR NSR
R t= u
else NSR NSR
S 0 t
The 'u' output of the timer is regarded non safety-related as it is
Q
a used for indication purposes only.
R Base u
13.5.11 I/O Symbols
I/O symbols The safety relation of most I/O symbols is defined using the 'System
Configuration' option of FSC Navigator ('safety relation' field).
However, there are a number of exceptions (some of which have a
predefined safety relation):
– Diagnostic inputs: safety-related
– FSC alarm markers: safety-related
– Watchdog inputs: safety-related
– Flashers: non safety-related
– Date/time constants: non safety-related
– Clock synchronization input (CLOCK-SYNC): non safety-related
– System reset input (RESET): safety relation configurable
– Force-enable input (ENABLE): safety relation configurable
– Secondary switch-off (SEC.SWITCH OFF): non safety-related
– Annunciation inputs and outputs (e.g. audible): non safety-related
– VM_ (volt-monitoring input of 10105/2/1): safety-related
– EL_: non safety-related
Software Manual
13.5.12 Flip-Flops
Flip-flops This section describes the safety relation of flip-flops in FLDs.
S-R flip-flop The safety relation of S-R flip-flops is as follows:
S R Q not Q
S S Q
ISR X ISR SR
R R Q else NSR NSR
R-S flip-flop The safety relation of R-S flip-flops is as follows:

S R Q not Q
S S Q
X ISR SR ISR
R R Q else NSR NSR
Software Manual
13.6 Error Messages
Error messages This section lists the error messages and warnings that may be
reported by the Safety Checker. All messages are stored in the log file
Application not translated correctly.

Description: This message will typically appear if you modified
the project in any way (using the FLD design editor or the System
Configuration option), and you did not translate the project before
starting the Safety Checker. The safety checking process will be
aborted and you will return to the FSC Navigator main screen.
Solution: Translate the project before starting the Safety Checker.
Attempting to write 'Undef' value to I/O datafile:

<type> <tag no.>
Description: An undefined safety relation ('Undef') for a symbol
was found which did have a valid value other than 'Undef' (SR,
NSR or ISR) at a previous calculation loop. This only applies to
symbols that have a sequence number (i.e. timers, registers,
counters, PIDs, cycle pulses, flip-flops, and off-sheet transfers).
The safety checking process will be aborted and you will return to
the FSC Navigator main screen.
Calculation of symbols with forced NSR inputs failed.

Description: After the safety relation of all symbol outputs on an
FLD have been calculated (based on the symbol inputs), there may
still be symbol outputs whose safety relation is not known (i.e.
undefined). If that happens, the Safety Checker will force the inputs
of these symbols to non safety-related, and will then recalculate
them to see if the symbol outputs can now be determined. If the
safety relation of these symbols remains undefined even after the
recalculation, this message will appear. The safety checking
process will be aborted and you will return to the FSC Navigator
main screen.
Solution: Make sure that all inputs and outputs on an FLD have a
valid safety relation (other than 'Undef') before starting the Safety
Checker.
Software Manual
Count-up or count-down not allowed for a float register.
Description: The count-up or count-down operation is only valid
for integer-type registers (byte, word or long).
modify the FLDs. Translate the application again, and then restart
the Safety Checker.
DISK READ ERROR: <file name>

the specified file.
disk and restart the Safety Checker.
DISK WRITE ERROR: <file name>

the specified file.
disk and restart the Safety Checker.

Description: The specified FLD contains corrupted data. The
safety checking process will be aborted and you will return to the
FSC Navigator main screen.
Solution: Use the 'Design FLDs' option of FSC Navigator to load
the FLD, and then delete it. Translate the application again, and
then restart the Safety Checker.

Description: The specified file could not be created. For example,
the disk may be full or the number of open files has been exceeded.
Solution: Clean your disk, i.e. delete unused files or save currently
unused files to a removable storage medium (e.g. a diskette), and
delete them from your hard disk.
Solution: Use a system with a larger disk capacity.

Description: An attempt was made to open the specified file, but it
was not found or could not be opened. If the file was the
<application name>.FMT, a default format file will be used by the
Safety Checker and it will be reported that the default format file is
used.
Software Manual
FLD reference detected to a lower FLD number: <symbol type>
<source FLD>_<destination FLD>_<seq. no.>
Description: An off-sheet symbol is referencing an FLD with a
lower FLD number.
Solution: This is a warning which reminds you that the logical
flow of some FLDs depends on FLDs with a higher FLD number,
which, in itself, is not a cause of errors. It may be wanted behavior,
but might also be a design error. There are basically two main
considerations that should be taken into account here:
1. During on-line modification (OLM), the value of the specified
variable on the specified source FLD is initialized to '0' (zero).
2. The response time of the functions related to the specified sheet
transfer is one program cycle longer. It may even be several
program cycles longer if the reference to lower FLD numbers is
repeated from one destination FLD to the next (e.g. from 880 to
870 to 860, etc.).
FLD transfer expected to be directly connected to I/O symbol.

<type> <tag no.>
Description: You defined a service text that is identical to the tag
number of an I/O symbol, but no direct connection exists.
change the service test or make a direct connection. Translate the
application again, and then restart the Safety Checker.
Illegal symbol for this block type: <block type>

Description: The FLD contains a symbol which should not be
present in an FLD with the specified block type. The safety
checking process will be aborted and you will return to the FSC
the symbol. Translate the application again, and then restart the
Safety Checker.
Inverted safety-related signal connected to safety-related output:

<type> <tag no.>
Description: An inverted safety-related (ISR) signal has been
connected to a safety-related (SR) output symbol.
Solution: This is a warning that is merely reported to draw your
attention. It may be wanted behavior, but might also be a design
error.
Software Manual
I/O with undefined safety relation: <type> <tag no.>
Description: No safety relation has been defined for the specified
I/O symbol.
to set the safety relation (safety-related or non safety-related).
Translate the application again, and then restart the Safety Checker.
Isolated symbol: Node (x,y)

Description: A symbol has been found without any direct or
indirect output connection to an off-sheet symbol.
connect the symbol or delete it. Translate the application again, and
then restart the Safety Checker.
Illegal connection: Node (x, y)

Description: A signal line has been connected to a symbol at a
point where it is not allowed, or the signal line is not a valid signal
type. Function blocks and registers have predefined input and
output positions.
change the connection. Translate the application again, and then
restart the Safety Checker.
Illegal signal type(s): Node (x, y)

Description: The signal type is illegal for the symbol to which it is
connected. For example, a signal of type Long cannot be connected
to a counter or timer.
Description: The types of the signal coming from the FLD to an
internal off-sheet symbol (i.e. decimal marker) do not match and
conversion is not allowed for internal symbols.
change the signal type. Translate the application again, and then
Load and value must both be connected or not connected:

<type> <tag no.>
Description: If you have a load function, you need a value to be
loaded into the register. If you do not have a load function, no
value is needed.
Solution: Make sure a value is loaded into the register. Translate
the application again, and then restart the Safety Checker.
Software Manual
Logic sequence too complex: Node (x,y)
Description: The Safety Checker has memory problems when
analyzing the sequence to the specified node point.
Solution: Use the 'Design FLDs' option of FSC Navigator to split
the functional logic diagrams into simpler or shorter sequences.
Mismatch between data from FLD database and configuration

database: <tag no.>
Description: The information for the specified tag number
(typically used by a function block) contained in the FLD database
does not match the corresponding information in the FSC
configuration database.
remove the function block that uses the specified tag number from
the affected FLD and place it again.
Missing signal or unconnected signal line: Node (x, y)

Description: A signal line which should be connected has not been
connected at node point (x, y).
connect or delete the line. Translate the application again, and then
More than one signal at a node: Node (x, y)

Description: Two independent signals may not be connected.
disconnect them. Translate the application again, and then restart
the Safety Checker.
No load signal, so a count signal and clear signal must be

connected: <type> <tag no.>
Description: If you do not load a register, you must at least use a
count-up or a count-down in combination with a clear, otherwise
the register is of no use.
Solution: Make sure all conditions are met to use the register.
Not enough memory to execute required Safety Checker

function(s).
Description: The Safety Checker needs more memory to execute.
Solution: Free up memory by exiting any applications that are
loaded in the computer's random-access memory (RAM).
Software Manual
Number of errors detected during safety calculation: <number>
Number of warnings generated during safety calculation:

<number>
Program aborted. Application configuration not defined.

Description: Before using the Safety Checker, the FSC application
configuration should be known.
(Install option) to define the FSC application. Translate the
application again, and then restart the Safety Checker.
Project not entirely calculated.

Description: The project analysis could not be completed
successfully, even after symbol inputs were forced to
non safety-related. This will typically be caused by the project
being too complex. The safety checking process will be aborted
and you will return to the FSC Navigator main screen.
Reset signal must be connected: <type> <tag no.>

Description: A memorize timer must always have a reset signal
because you cannot get it low after you started it.
Solution: Make sure the memorize timer has a reset signal.
'Safety Checker' program out of space.

Description: The number of mnemonics or the number of found
symbols in the FLD cannot be stored internally.
Solution: Try to optimize the FLD with regard to the number of
symbols needed for particular functions. Translate the application
again, and then restart the Safety Checker.
Solution: Try to change the partition of your total functional logics
design in such a way that fewer functions are needed per FLD.
Safety relation inconsistency: <type> <tag no.>

Description: A non safety-related line has been connected to a
safety-related output, or a non safety-related marker input has been
connected to a safety-related marker output.
correct or delete the connections.
Software Manual
Set and value signals must both be connected or not connected:
<type> <tag no.>
Description: If you have a set function, you need a value to be
loaded into the counter. If you do not have a set function, no value
is needed.
Solution: Make sure a value is loaded into the counter. Translate
the application again, and then restart the Safety Checker.
Set, count-up or count-down signal must be connected: <type>

<tag no.>
Description: You must connect one of these functions to the
counter for it to be of any use.
Solution: Make sure one of the specified functions is connected to
the counter. See the symbol description in Section 6 of this manual
("Functional Logic Diagrams"). Translate the application again,
and then restart the Safety Checker.
Set signal must be connected.

Description: The set signal of a timer has not been connected.
a connection. Translate the application again, and then restart the
Safety Checker.
Undefined FLD reference: <type> <tag no.>

Description: A reference was found to FLD 0 or from FLD 0,
which has not been defined.
Solution: Use the 'Design FLDs' option of FSC Navigator to define
the sheet reference. Translate the application again, and then restart
the Safety Checker.
Undefined symbol found.

Description: A symbol on an FLD was found which could not be
identified. The symbol is not valid in the symbol set used by FSC
Navigator. The FLD may be corrupted. The safety checking
process will be aborted and you will return to the FSC Navigator
main screen.
Value signal must be connected.

Description: A binary input for this type of timers must be
connected.
a connection. Translate the application again, and then restart the
Safety Checker.
Software Manual
Value signal must not be connected.
Description: A binary input for this type of timers may not be
connected.
remove the binary input. Translate the application again, and then
Variable not found in variable data file: <type> <tag no.>

Description: The variable found in the FLD is not found in the
data file. The Safety Checker will try to regenerate the variable.
The result of that action is logged.
(Symbol \ Change) to enter the required data. The variable will then
be placed in the database. If the variable is a repeated input, you
must first place the actual input. It is possible that the data was
deleted when using the 'System Configuration' option of FSC
Navigator. Use this option to (re-)enter the missing variable.
Wrong number of input signals: Node (x, y)

Description: The number of signals at the input side of the symbol
does not match the expected number of signals.
manual ("Functional Logic Diagrams"). Translate the application
Wrong number of output signals: Node (x,y)

Description: The number of signals at the output side of the
symbol does not match the expected number of signals.
manual ("Functional Logic Diagrams"). Translate the application
Software Manual
Software Manual
Fail Safe Control
Appendix A:
Alarm Functions
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix A: Alarm Functions
A.1 Introduction ....................................................................................................A-1
A.2 Alarm Types....................................................................................................A-3
A.3 Alarm Sequences ...........................................................................................A-6

A.3.1 Alarm Symbols .................................................................................................................A-6
A.3.2 Alarm Sequence AF: Basic Flashing................................................................................A-7
A.3.3 Alarm Sequence AM: Manual Lamp Reset......................................................................A-7
A.3.4 Alarm Sequence FR: Flasher Reset ................................................................................A-8
A.3.5 Alarm Sequence FRM: Flasher/Lamp Reset ...................................................................A-9
A.3.6 Alarm Sequence AR: Ringback........................................................................................A-9
A.3.7 Alarm Sequence ARR: Double Audible Ringback .........................................................A-10
A.3.8 Alarm Sequences TFS, TFS_COM1, and TFS_COM2: First Up Indication ..................A-11
A.4 Alarm Configuration Examples ...................................................................A-13

A.4.1 AF Alarm Configuration..................................................................................................A-13
A.4.2 First Up Alarm Configuration Via Communication Links ................................................A-18
A.4.3 Flasher for Alarm Functions ...........................................................................................A-21
Software Manual
Appendix A: Alarm Functions i
FIGURES
Figure A-1 Alarm functions ...........................................................................................................A-1

Figure A-2 Symbols used in description of alarm sequences.......................................................A-6
Figure A-3 Basic flashing ..............................................................................................................A-7
Figure A-4 Manual lamp reset.......................................................................................................A-7
Figure A-5 Flasher reset ...............................................................................................................A-8
Figure A-6 Flasher/lamp reset ......................................................................................................A-9
Figure A-7 Ringback .....................................................................................................................A-9
Figure A-8 Double audible ringback............................................................................................A-10
Figure A-9 First up indication (fast flash, slow flash) ..................................................................A-11
Figure A-10 First up indication (single flash frequency)................................................................A-11
Figure A-11 Adding an alarm group..............................................................................................A-13
Figure A-12 AF alarm configuration ..............................................................................................A-14
Figure A-13 AF audible .................................................................................................................A-15
Figure A-14 Allocation of alarm point to alarm lamp driver...........................................................A-16
Figure A-15 Alarm function included in application program ........................................................A-17
Figure A-16 Example of alarm sequence......................................................................................A-18
Figure A-17 Functional logic for alarm sequence .........................................................................A-19
Figure A-18 Functional logic for alarm sequence .........................................................................A-20
Figure A-19 Flasher for alarm functions........................................................................................A-21
TABLES
Table A-1 Inputs and outputs per alarm sequence......................................................................A-3
Software Manual
ii Appendix A: Alarm Functions
Appendix A – Alarm Functions
A.1 Introduction
Alarm functions The FSC system software has several standard alarm functions, which
can easily be configured by the user. An alarm function group is
defined by the variable type 'A'. They are added to the application
using the System Configuration option of FSC Navigator ('Signal
specs' menu item). A predefined standard sequence and the number of
alarm points can be configured for an alarm group.
Once this has been done, the alarm function is included in the
application program via inputs and outputs with location 'ANN'
(annunciation), which are allocated to the alarm function. The
function of the alarm sequence of each input and output is defined by
the alarm signal type.
The inputs with location 'ANN' are virtual inputs for the application.
The status of these inputs is generated by the standard alarm sequence
function in the system software.
The outputs with location 'ANN' are virtual outputs for the
application. The status of these outputs is used as input in the standard
alarm sequence function in the system software (see Figure A-1).
Figure A-1 Alarm functions
Software Manual
Appendix A: Alarm Functions A-1
Allocation of Variables are allocated to an alarm group by specifying the alarm
variables group tag number. This tag number must already be defined as a
variable with type 'A'. The number of variables with alarm type
'Alarm' are specified by the user. This number should be a multiple of
8. All alarm types of a specific group must be configured, except for
alarm type 'Lamp test' and alarm type 'Common'.
Software Manual
A-2 Appendix A: Alarm Functions
A.2 Alarm Types
Alarm types Table A-1 shows the inputs and outputs used for each alarm
sequence. (For details on alarm sequences refer to subsection A.3.)
Table A-1 Inputs and outputs per alarm sequence

Alarm sequence
Type Alarm type AF AM FR FRM AR ARR TFS TFS TFS

COM1 COM2
O alarm(s) = = = = = = = = =
O acknowledge = = = = = = = = =
O flasher 1 2 Hz 2 Hz 2 Hz 2 Hz 0.5 Hz 0.5 Hz 0.5 Hz 0.5 Hz
O flasher 2 2 Hz 2 Hz 2 Hz 2 Hz
O lamp test = = = = = = = =
O lamp reset = =
O reset = =
O flasher reset = =
O first up reset = = =
O first up status =
I audible = = = = = = =
I common = = = = = = = = =
I audible reset =
I audible set =
Software Manual
The alarm types of an alarm function group are the following:
Acknowledge The acknowledge signal (output variable) is used to confirm the

alarm, e.g. by the system operator.
Alarm(s) This is an output variable which is used to activate the alert function
of the alarm group. The variable should be allocated to a digital
output module, which contains the current status of the specific
alarm. The number of alarm variables of an alarm group are specified
within the alarm function group variable ('A' <tag number>).
At least one output variable with alarm type 'Alarm' should be
allocated to each alarm group.
Alarm sequences The alarm sequences supported by FSC are a subset of the
Audible Audible (input variable) is the audible result of the alarm group.
The signal is set when an alarm is detected or when the state of the
alarm changes. The signal is reset by the acknowledge signal or by the
reset signal of the alarm group.
Audible reset Audible reset (input variable) is the audible result of the alarm group.
The signal is set when an alarm returns to the normal state. The signal
is reset by the reset signal of the alarm group.
Audible set Audible set (input variable) is the audible result of the alarm group.
The signal is set when an alarm is detected. The signal is reset by the
acknowledge signal of the alarm group.
Common This input variable is high if any of the alarm types 'Alarm' of the
alarm group is in the alarm state. The configuration of this variable is
optional.
First up reset First up reset (output variable) is used to reset the alarm type 'Alarm'
to the steady (high) state. This signal is only accepted when the alarm
was already confirmed by an acknowledge.
First up status This represents the status of the first up reset in the receiver alarm
status. This output must be linked to the output of type alarm of the
same alarm group which it belongs to.
Flasher reset Flasher reset (output variable) is used to reset the alarm type 'Alarm'
to the steady (high) state. This signal is only accepted if the alarm
was already confirmed by an acknowledge.
Software Manual
Flasher 1 Flasher 1 (output variable) is the signal which is used for the flash
functions of the alarm type 'Alarm'.
In case two flashers are needed for the alarm type, this flasher is used
for the slow flash function. Table A-1 indicates the standard frequency
for the flash functions for each alarm function.
Flasher 2 Flasher 2 (output variable) is only used if two flash functions are
needed for the alarm type 'Alarm'.
Flasher 2 is used for the fast flash function. Table A-1 indicates the
standard frequency for the flash test functions for each alarm function.
Lamp test Lamp test (output variable) is used to check the hardware of the
digital output modules which are used by an alarm type 'Alarm' and
the alarm indicator. The configuration of this variable is optional.
Lamp reset Lamp reset (output variable) is used to reset the alarm type 'Alarm' to
the normal (low) state when the condition of the 'alarm' has returned
to normal.
Reset Reset (output variable) is used to reset the alarm type 'Alarm' to the
normal (low) state and to reset the audible signal when the condition
of the 'alarm' has returned to normal.
Software Manual
A.3 Alarm Sequences
Alarm sequences The alarm sequences supported by FSC are a subset of the
The following alarm sequences are supported:
• AF: basic flashing
• AM: manual lamp reset
• FR: flasher reset
• FRM: flasher/lamp reset
• AR: ringback
• ARR: double audible ringback
• TFS, TFS_COM1, TFS_COM2: first up indication.
A.3.1 Alarm Symbols
Alarm symbols Figure A-2 below shows the symbols that are used to describe the
alarm sequences. They are all in accordance with DIN 19235
(October 1980).
Visual symbols Audible symbols

Figure A-2 Symbols used in description of alarm sequences
Software Manual
A.3.2 Alarm Sequence AF: Basic Flashing
Figure A-3 shows the annunciator sequence diagram for alarm

sequence AF (basic flashing).
Figure A-3 Basic flashing
When an alarm becomes active, the output of the alarm flashes, and
the audible is set. When 'Acknowledge' becomes high, the output of
the alarm is steady, and the audible is reset. The output will be cleared
when the alarm returns to its normal (high) state. 'Common' will be
high when one or more alarms of the alarm group are in the active
state.
A.3.3 Alarm Sequence AM: Manual Lamp Reset

sequence AM (manual lamp reset).
Figure A-4 Manual lamp reset
Software Manual
the audible is set. When 'Acknowledge' becomes high, the output of
the alarm is steady, and the audible is reset. The output continues
steadily when the alarm returns to its normal (high) state. The output
will be cleared when 'Lamp reset' is set. 'Common' will be high when
one or more alarms of the alarm group are in the active state.
A.3.4 Alarm Sequence FR: Flasher Reset

sequence FR (flasher reset).
Figure A-5 Flasher reset
the audible is set. When 'Acknowledge' becomes high, the audible is
reset. The output becomes steady when 'Flasher reset' is set. The
output will be cleared when the alarm returns to its normal (high)
state. 'Common' will be high when one or more alarms of the alarm
group are in the active state.
Software Manual
A.3.5 Alarm Sequence FRM: Flasher/Lamp Reset

sequence FRM (flasher/lamp reset).
Figure A-6 Flasher/lamp reset
the audible is set. When 'Acknowledge' becomes high, the audible is
reset. The output will be steady when 'Flasher reset' is high. The
output will be cleared when the alarm returns to its normal (high)
state. 'Common' will be high when one or more alarms of the alarm
group are in the active state.
A.3.6 Alarm Sequence AR: Ringback

sequence AR (ringback).
Figure A-7 Ringback
Software Manual
When an alarm becomes active, the output of the alarm flashes fast,
and the audible is set. When 'Acknowledge' becomes high, the output
of the alarm is steady, and the audible is reset. The output will flash
slowly when the alarm returns to its normal (high) state. The output
will be cleared if 'Lamp reset' is set. 'Common' will be high when one
or more alarms of the alarm group are in the active state.
A.3.7 Alarm Sequence ARR: Double Audible Ringback

sequence ARR (double audible ringback).
Figure A-8 Double audible ringback
When an alarm becomes active, the output of the alarm flashes fast,
and 'Audible set' is set. When 'Acknowledge' becomes high, the output
of the alarm is steady, and 'Audible set' is reset. When the alarm
returns to its normal (high) state, the output will flash slowly, and
'Audible reset' is set. When 'Reset' is set, the output will be cleared
and 'Audible reset' is reset. 'Common' will be high when one or more
alarms of the alarm group are in the active state.
Software Manual
A.3.8 Alarm Sequences TFS, TFS_COM1, and TFS_COM2:
First Up Indication
Figure A-9 and Figure A-10 show the annunciator sequence diagrams
for alarm sequence TFS, TFS_COM1, and TFS_COM2 (first up
indication).
Figure A-9 First up indication (fast flash, slow flash)
When the first alarm becomes active, the output of this alarm has an
intermittent flash, and the audible is set. When other alarms become
active, the output of these alarms have steady fast flashes, and the
audible is set. When 'Acknowledge' becomes high, the output of the
first alarm flashes slowly, the output of the other active alarms will
become steady, and the audible is cleared. The output of the first
alarm will be steady when 'First up reset' is set. The outputs will be
cleared when the alarm returns to its normal (high) state. 'Common'
will be high when one or more alarms of the alarm group are in the
active state.
Figure A-10 First up indication (single flash frequency)
Software Manual
When the first alarm becomes active, the output of this alarm has a
steady fast flash, and the audible is set. When other alarms become
active, the output of these alarms also have fast flashes, and the
audible is set. When 'Acknowledge' becomes high, the output of the
first alarm remains flashing, the output of the other active alarms will
become steady, and the audible is cleared. The output of the first
alarm will be steady when 'First up reset' is set. When the alarm
returns to its normal (high) state, the outputs will be cleared.
'Common' will be high when one or more alarms of the alarm group
are in the active state.
Software Manual
A.4 Alarm Configuration Examples
Alarm configuration This section discusses two examples of how alarm functions can be
used. The first example shows the basic flashing sequence (AF). The
second example discusses the configuration of the first up alarm
sequence with separate alarm detection and indication which can be
used in communication networks.
A.4.1 AF Alarm Configuration
Configuring an
AF alarm To configure an AF alarm, do the following:
1. Start the 'System Configuration' option of FSC Navigator.
2. Choose the 'Signal specs' main menu option to add an alarm
group. The type of an alarm group is always 'A'.
Figure A-11 Adding an alarm group
Software Manual
3. Choose the 'Hardware specs' main menu option to assign this
variable to an alarm sequence and to define the maximum number
of alarm points for this group, e.g. 16 points for the alarm
sequence AF as shown in Figure A-12.
Figure A-12 AF alarm configuration
Software Manual
4. You can now assign variables with location 'ANN' to this alarm
group in accordance with Table A-1 on page A-3. For the alarm
sequence AF, you can assign inputs to the signal type 'Common'
and 'Audible' (see Figure A-13).
Figure A-13 AF audible
Software Manual
5. The alarm types 'Flasher 1', 'Lamp test' and 'Acknowledge' (for
outputs) can be allocated in the same way. The actual alarm points
can be allocated to an alarm lamp driver (output module) (see
Figure A-14).
Figure A-14 Allocation of alarm point to alarm lamp driver
Software Manual
Functional logic The alarm function can now be included in the application program
diagrams as shown in Figure A-15.
F 10
High level alarm 3 AF_AlarmPoint1 A
> 11 N
F 3 A 4 "alarmtype= ALARM" N
PRESSURE
L 5
D 3 D
Low level alarm 3 AF_AlarmPoint2 A

> 11 N
3 "alarmtype= ALARM" N
F 5
Alarm status
P Ack_PushButton 3 AF_Acknowledge A
N 1 N
L 3 N
Alarm Sequence AF
F Test_pushButton 3 3 AF_LampTest A
L 1 15 N
D 2 5 N
S FLASHER-2Hz AF_Flasher_1 A
Y System marker N
S N
In alarm function
Out alarm function

A AF_Audible 3 Horn F
N 15 L
N 7 D
A AF_Common_Alarm 3 Com._alarm_lamp F
N 15 L
N 8 D

D Principal : HSMS Product Marketing
C
Plant : Branderijstraat 6
B Tel +31 73-6273273 Date 11-6-1997 By: RK NL33
A 5223 AS 's-Hertogenbosch
Honeywell SMS BV Fax +31 73-6219125
P.O. Box 116
Drawing number:
O 11-6-1997 FIRST ISSUE Req/Ordernr :

5201 AC
DEMO_1 105 106
Serial Unit
Rev Date Description Chk'd 's-Hertogenbosch Project Sheet Cnt'd
Code Code
Figure A-15 Alarm function included in application program
A high and low level pressure alarm will bring up alarms called
'AF_AlarmPoint1' and 'AF_AlarmPoint2'.
A horn and a common alarm lamp are driven by the inputs
'AF_Audible' and 'AF_Common_Alarm'.
The 2 Hz system flasher controls the flashing speed of this group. The
acknowledge of the alarm sequence is realized via an input button
which is connected to 'AF_Acknowledge'. The lamp test button is
connected to 'AF_Lamptest'.
Software Manual
A.4.2 First Up Alarm Configuration Via Communication Links
First up Alarm groups of the sequence TFS COM_1 and TFS COM_2 are
alarm groups related. Their sequence is nearly the same as TFS. The alarm
detection and the visual display and manipulation of the alarm
sequence is done in different FSC systems or an FSC system in
cooperation with a Distributed Control System (DCS). An example of
these sequences is given in Figure A-16.
Figure A-16 Example of alarm sequence
As shown in Figure A-16, an alarm group with sequence 'TFS_COM1'

has been configured in FSC system 20. FSC system 14 has an alarm
group with sequence 'TFS_COM2'. The actual alarm is detected in
FSC system 20. Since it is a TFS sequence and the first in the alarm
group must be detected, two signals for each alarm point are
transferred to the other device (here FSC system 14). The signals are
the alarm status and information whether it was the first alarm in the
group or not (the first up status). In FSC 14, these alarms are
displayed and can be acknowledged. The acknowledge signal is
transferred back to FSC 20. If the alarm must be reset, this is initiated
in FSC 14 and copied to FSC 20.
Software Manual
Functional The functional logic diagrams (FLDs) that are required to include
logic diagrams these alarm sequences in the application program are shown in Figure
A-17 and Figure A-18.
F 10 High level alarm

2 FIRSTUP-ALARM-1 A
> 2 N
"FIRSTUP-FLAG" N
3 ALARM-1 F
F 1 A 2 S
PRESSURE
L 3 "ALARM STATUS" C
D 1 D
Low level alarm 4 ALARM-2 F

> 2 S
"ALARM STATUS" C
F 5
1 FIRSTUP-ALARM-2 A
2 N
"FIRSTUP-FLAG" N
ALARM SIGNALS
---------------------------------------------------- COMMON SIGNALS
F ACKNOWLEDGE 1 ACKNOWLEDGE A
S 2 N
C N
F FIRSTUP-RESET 0 FIRSTUP-RESET A
S 2 N
C N
FSC 20
ALARM SEQUENCE TFSCOM1
Customer :
Principal :
Plant 1 :
Tel +73-6273273 Date 3-11-1998 By:
Plant 2 :
Honeywell SMS BV Fax +73-6219125
P.O.Box 116
Drawing number:
O 3-11-1998 FIRST ISSUE Req/Order no: TFSCM1_1 1 -

5201 AC
Serial Unit
Rev Date Description Chk'd DEN BOSCH (NL) Project FLD Cnt'd
Code Code
Figure A-17 Functional logic for alarm sequence
A high-level alarm is detected in FSC 20 and connected to two signals

ALARM-1 and FIRSTUP-ALARM-1. FIRSTUP-ALARM-1 has
location 'ANN' and is used to detect whether it was the first alarm in
the group. The other signal ALARM-1 contains the status of the alarm
and must only be sent to the display unit. This signal has location
'FSC', but if a DCS system is used as the alarm display driver, the
(sub)location is 'COM'.
These signals arrive in FSC 14 as inputs (see Figure A-18) (location

FSC), and are directly connected to the alarm group 'FSC_COM_2'
via outputs with location 'ANN' ALARM-1 and FIRSTUP-ALARM_1
(signal type 'Alarm' and 'First up status'). If FSC 14 receives an active
alarm status, the alarm group will activate the inputs COMMON and
AUDIBLE. In the functional logic diagrams, these are connected to
outputs which drive the common alarm lamp and horn.
Software Manual
F FIRSTUP-ALARM-1 2 FIRSTUP-ALARM-1 A
S 1 N
C "FIRSTUP-FLAG" "FIRSTUP-FLAG" N
F ALARM-1 3 1 ALARM-1 A
S 1 8 N
C "ALARM STATUS" 1 N
F FIRSTUP-ALARM-2 1 FIRSTUP-ALARM-2 A
S 1 N
C "FIRSTUP-FLAG" "FIRSTUP-FLAG" N
F ALARM-2 4 1 ALARM-2 A
S 1 8 N
C "ALARM STATUS" ALARM SIGNALS 2 N
---------------------------------------------------
F TEST-PUSHBUTTON 1 COMMON SIGNALS LAMPTEST A
L 1 N
D 3 N
A COMMON 1 COM.ALARM-LAMP F
N 6 L
N 2 D
A AUDIBLE 1 HORN F
N 6 L
N 1 D
S FLASHER-0.5Hz
Y System marker
ALARM SEQUENCE TFSCOM2 FLASHER-1 A
N
S N
S FLASHER-1Hz
FSC14 FLASHER-2 A
Y System marker N
S N
P RESET-PUSHBUTTON 1 -1 FIRSTUP-RESET-2 A
N 1 N
L 2 N
0 FIRSTUP-RESET F
1 S
C
1 ACKNOWLEDGE F
1 S
C
P ACK-PUSHBUTTON 1 -1 ACKNOWLEDGE_2 A
N 1 N
L 1 N
Customer :
Principal :
Plant 1 :
Tel +73-6273273 Date 3-12-1998 By:
Plant 2 :
Honeywell SMS BV Fax +73-6219125
P.O.Box 116
Drawing number:
O 3-12-1998 FIRST ISSUE Req/Order no: TFSCM2_2 4 -

5201 AC
Serial Unit
Rev Date Description Chk'd DEN BOSCH (NL) Project FLD Cnt'd
Code Code
Figure A-18 Functional logic for alarm sequence
Two flashers control the flashing sequence in FSC 14.
The input ACK-PUSHBUTTON in FSC 14 is hardwired. The FLDs

connect these inputs to outputs ACKNOWLEDGE (location ANN)
and ACKNOWLEDGE-2 (location FSC). ACKNOWLEDGE is used
for 'TFS_COM2' and ACKNOWLEDGE-2 for 'TFS_COM1'. Since
'TFS_COM1' is in another system, the signal must first be sent to FSC
20 using FSC-FSC communication.
The hardwired input to reset the alarm group RESET-PUSHBUTTON

works in the same way.
Another hardwired input is used to activate a lamp test. This input is
called TEST-PUSHBUTTON and is connected to the output
LAMPTEST in FSC14.
Software Manual
A.4.3 Flasher for Alarm Functions
Flashers The FSC system supports built-in alarm functions.

These alarm functions include flashing of the alarm lights. The flasher
frequency for the alarm lights can be generated from the FSC system
flashers (based on the real-time clock data) or built up using the cycle
pulse function (output coupled to the input via an inverter with
optional divider created via counter). The use of FSC system flashers
result in variations of the on/off time of the flashing lights. The
flashers based on the cycle time of the application program do not
have this drawbacks (the on/off time of the flashing lights is constant).
Figure A-19 shows an example of flashers based on the cycle time.
108 FAST_FLASHER
CU =1
103
1
CD
COUNTER
R 0
108 SLOW_FLASHER
CU =1
103
2
CD
COUNTER
R 0
Figure A-19 Flasher for alarm functions
Software Manual
Software Manual
Fail Safe Control
Appendix B:
Sequence-of-Event Recording
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix B: Sequence-of-Event Recording
B.1 Introduction ....................................................................................................B-1
B.2 Sequence-of-Event Recording to FSCSOE...................................................B-3

B.2.1 Introduction.......................................................................................................................B-3
B.3 Sequence-of-Event Recording to PlantScape ..............................................B-6

B.3.1 Introduction.......................................................................................................................B-6
B.4 Sequence-of-Event Recording to a Modbus Device ....................................B-9

B.4.1 Introduction.......................................................................................................................B-9
B.4.3 Reading the SER Event Records...................................................................................B-10
B.5 Sequence-of-Event Recording to a Printer .................................................B-13

B.5.1 Introduction.....................................................................................................................B-13
B.5.2 Configuration ..................................................................................................................B-13
B.6 Numerical SER..............................................................................................B-15

B.6.1 Introduction.....................................................................................................................B-15
B.6.3 Setting the SER Range ..................................................................................................B-18
B.7 Text SER .......................................................................................................B-21

B.7.1 Introduction.....................................................................................................................B-21
B.7.3 Specifying the Printer Type ............................................................................................B-22
B.8 Event Specification ......................................................................................B-26

B.8.1 Variable Events ..............................................................................................................B-26
B.8.2 Force Events ..................................................................................................................B-29
B.8.3 Fault Events ...................................................................................................................B-29
B.9 SER Characteristics .....................................................................................B-30

B.9.1 SER Resolution ..............................................................................................................B-30
B.9.2 SER Buffer Capacity ......................................................................................................B-30
B.9.3 SER Format....................................................................................................................B-31
B.10 SER Channel Specification..........................................................................B-32

B.10.1 SER Channels in Communication Networks..................................................................B-32
B.10.2 Single SER Channel ......................................................................................................B-35
B.10.3 Redundant SER Channels .............................................................................................B-35
B.10.4 Dual SER Channels .......................................................................................................B-36
B.10.5 SER Channel Availability ...............................................................................................B-36
Software Manual
Appendix B: Sequence-of-Event Recording i
FIGURES
Figure B-1 FSCSOE, the event historian ......................................................................................B-3

Figure B-2 FSC sequence-of-event data on PlantScape display .................................................B-6
Figure B-3 Configuring the SER channel and SER range ..........................................................B-17
Figure B-4 SER-enabling FSC variables using FSC Navigator ..................................................B-19
Figure B-5 SER printer configuration screen ..............................................................................B-22
Figure B-6 FSCSER format ........................................................................................................B-24
Figure B-7 Event definition for variable types AI and AO ...........................................................B-27
Figure B-8 'Local' event collection in SER communication network ...........................................B-32
Figure B-9 'Global' event collection in SER communication network .........................................B-33
Figure B-10 'Global' and 'local' event collection in SER communication network ........................B-33
Figure B-11 Primary and secondary SER channel .......................................................................B-34
Figure B-12 Single SER channel layout........................................................................................B-35
Figure B-13 Redundant SER communication channel .................................................................B-35
Figure B-14 Dual, redundant SER channels.................................................................................B-36
TABLES
Table B-1 Event record structure (Modbus) ..............................................................................B-11

Table B-2 SER system messages (Modbus).............................................................................B-12
Table B-3 Supported SER printers ............................................................................................B-23
Software Manual
ii Appendix B: Sequence-of-Event Recording
Appendix B – Sequence-of-Event Recording
B.1 Introduction
Sequence-of-event The FSC system contains an integrated sequence-of-event recording

recording (SER) function, which allows the system to detect and record events
that indicate or may cause deviations from normal process operation.
Examples of such events are:
• change of state of a valve limit switch,
• steam pressure becoming too high,
• maintenance override effected by a maintenance engineer,
• faults in the field (e.g. open transmitter loop), and
• faults in FSC input/output interfaces.
Once per program scan, the FSC system inspects all defined process
quantities, both digital and analog, for a change of state, in line with
the execution of the control program. An event is logged for any
changed process quantity, in an event buffer that resides within the
system. Events that result from operator interaction or from detected
faults are logged as soon as they are handled by the system. The
integrated list of the detected exceptions thus provides excellent
information for post-mortem analysis of abnormal process behavior,
in line with the 'traceability requirements' of IEC 61508 and
ANSI/ISA S84.01.
SER output The logged events are reported to event management systems through
the FSC system's communication interfaces. Events may be reported
to:
• a personal computer running Honeywell's dedicated FSCSOE event
historian, which allows users to view and analyze (anomalous)
process events (see subsection B.2),
• a distributed control system (DCS) (PlantScape, TPS, or third-party
system) for incorporation of the events into an overall event journal,
(see subsections B.3 and B.4), or
• a line printer or matrix printer for direct reporting on paper
(see subsection B.5).
Software Manual
Appendix B: Sequence-of-Event Recording B-1
Advanced features of the FSC sequence-of-event recording function
include:
• centralized event reporting in distributed safety networks, and
• event reporting to redundant event management systems.
Event reporting The sequence-of-event recording (SER) function of the FSC system
logs (anomalous) process events, and outputs them to FSCSOE, a
DCS, or a printer. This allows you to evaluate any abnormal
situations that have occurred. The SER function reports events if:
• an event occurs for a process variable which is SER-enabled, or
• a process variable is forced (maintenance override), or
• an active force on a process variable is removed, or
• a fault is detected in the FSC system.
Numerical SER vs. SER data can be sent from the FSC system to the SER data
text SER processing device (e.g. FSCSOE, PlantScape, or a printer) in two
ways:
• numerical SER, and
• text SER.
Numerical SER Numerical SER allows event recording with minimal communication
overhead. It is used for event recording to FSCSOE (the event
historian of the FSC product portfolio), PlantScape, or a Modbus
device (e.g. a DCS).
If numerical SER is used, a unique sequence number is assigned to all
For details on numerical SER refer to subsection B.6.
Text SER Text SER is only used for event recording to printers that are directly
connected to the FSC system. Full text strings containing all event
information are sent to the printer, which output this information on
paper. This type of event recording requires much more
communication resources than numerical SER.
For details on text SER refer to subsection B.7.
Software Manual
B-2 Appendix B: Sequence-of-Event Recording
B.2 Sequence-of-Event Recording to FSCSOE
B.2.1 Introduction
FSCSOE FSC Sequence of Events (FSCSOE) is the safety historian for

Honeywell's Fail Safe Control (FSC) product line. This Windows
software package records and logs process events, alarm events and
diagnostic events that are detected by the connected FSC system(s),
and stores them in its event database including detailed time-stamp
information. These events can be displayed, analyzed, printed and
exported based on user-definable selection criteria (filters).
Figure B-1 FSCSOE, the event historian
FSCSOE enables users to analyze and monitor (abnormal) process

behavior. Any anomalies in a process may upset the process as a
whole. In order to understand why they occurred and to find the first
event that caused the process upset, accurately time-stamped and
Software Manual
archived information is essential. Equally important is the ability to
retrieve and analyze the logged information. This enables any process
anomaly to be reported rapidly and remedied effectively. This helps
the user keep the process on-line and maximize the plant profitability.
FSCSOE allows on-line modification of the network/variable

configuration while event recording continues. It can also send event
data to, or receive data from, various Distributed Control Systems
(DCSs).
Note:
For details on sequence-of-event recording using FSCSOE refer
to the FSCSOE manuals.
B.2.2 Configuration
Configuration If you wish to use the SER function and send the event data to
requirements FSCSOE, the FSC configuration must contain the following:
1. a DBM module (except for the FSC slaves), and
2. a communication channel that has been configured for SER
reporting, using the Development System (DS) protocol.
Note:
If the SER channel configuration is modified, any SER data
If these requirements are not met, you will not be able to set any
variable to 'SER-enabled' and translate successfully.
Setting up SER Setting up sequence-of-event recording to FSCSOE consists of the

to FSCSOE following steps:
1. Configuring the SER channel (see subsection B.6.2),
2. Defining the SER range (see subsection B.6.3), and
3. Setting the 'SER-enabled' status of variables (including allocating
SER sequence numbers to them) (see subsection B.6.4).
Software Manual
Supported events The following FSC event types are recorded and stored by FSCSOE:
• FSC events of process variables of types I, O, AI, and AO
(process variable events),
• FSC force events of variable of types I, O, AI, and AO
(force events),
• FSC variable value reports of variables of type BO-SER
(report events),
• FSC diagnostic events, and
• FSC system events:
− FSC system faults,
− SOE buffer full events,
− All forces cleared event,
− Unknown force change (forced variable without a sequence
number).
For a more detailed specification of the event types refer to subsection

B.8 on page B-26.
Software Manual
B.3 Sequence-of-Event Recording to PlantScape
B.3.1 Introduction
PlantScape Sequence-of-event (SOE) features as supported by the FSC controller

are integrated into the PlantScape system. Each tag name that has
been "SOE-enabled" is time-stamped by the FSC controller and
reported to the PlantScape server, where it is incorporated into the
standard PlantScape SOE table. Standard SOE displays are available
to view the events as they are reported.
Figure B-2 FSC sequence-of-event data on PlantScape display
Note:
The FSC system events are only logged by PlantScape if points
have been assigned to an SOE-only point controller. For
configuration details refer to the PlantScape manuals.
Software Manual
B.3.2 Configuration
Configuration If you wish to use the SER function and send the event data to
requirements PlantScape, the FSC configuration must contain the following:
1. a DBM module (except for the FSC slaves),
2. one or more 10018/E/x PlantScape communication modules, and
reporting, using the PlantScape communication protocol.
Notes:
1. If the SER channel configuration is modified, any SER data
2. The FSC system events are only logged by PlantScape if
points have been assigned to an SOE-only point controller.
For configuration details refer to the PlantScape manuals.
Setting up SER Setting up sequence-of-event recording to PlantScape consists of the

to PlantScape following steps:
Supported events The following FSC event types are recorded and stored by
PlantScape:
(force events),
(report events),
Software Manual
number).

B.8 on page B-26.
Software Manual
B.4 Sequence-of-Event Recording to a Modbus Device
B.4.1 Introduction
Modbus Sequence-of-event data can be sent to a Modbus device (e.g. a

distributed control system, DCS).
B.4.2 Configuration
Configuration If you wish to use the SER function and send the event data to a
requirements Modbus device, the FSC configuration must contain the following:
1. a DBM module (except for the FSC slaves), and
reporting, using the Modbus communication protocol (either RTU
or H&B).
Note:
Setting up SER Setting up sequence-of-event recording to a Modbus device consists

to Modbus device of the following steps:
Software Manual
Supported events The following FSC event types are recorded and stored by the
Modbus device:
(force events),
• FSC diagnostic events,
• FSC events related to markers (M), timers (T), and counters (C),
number).

B.8 on page B-26.
B.4.3 Reading the SER Event Records
Reading the SER Modbus function code 3 is used to read the contents of the FSC event
event records buffer. At each request, the FSC system sends a response message
that contains 16 events. If the FSC event buffer holds fewer than 16
events, the remaining entries in the response message will be filled
with an SER buffer empty event.
Each event contains 8 bytes as specified in Table B-1 on the next
page.
When reading FSC event data, the DCS must use the register
addresses 49994 and 49995 alternately. The FSC system uses the
constant switchover as a mechanism to confirm the event response
message that was sent last. As long as the FSC system receives
alternating register addresses, the FSC system sends the next events in
sequence. If, however, the same address is received twice (which
means that something went wrong), the FSC system will resend the
last event message.
The event data read option is only valid if numerical SER is used (see
subsection B.6 on page B-15).
Software Manual
Table B-1 Event record structure (Modbus)
Byte No. Description Range
1, 2 Seq. No. High, Low 0 to FFFEh
3 Event status 0, 0Fh, FFh (see 'Event status' below)
4 Milliseconds 0 to 63h (= 0 to 99) (only last two digits)
5 Tenths of seconds 0 to 9h
6 Seconds 0 to 3Bh (= 0 to 59)
7 Minutes 0 to 3Bh (= 0 to 59)
8 Hours (bits 0-6) 0 to 17h (= 0 to 23)
SZ (bit 7) 0 = winter time
1 = daylight saving time
Notes:
1. The SZ bit only serves as a flag to indicate whether daylight
saving time is active or not. The hour values that are sent
have already been compensated.
2. The 24-hour clock is used, which means that 2:05 pm is
represented as 14:05.
3. For example, 1.234 seconds is represented as follows:
seconds = 1, tenths of seconds = 2, milliseconds = 34.
4. Summer/winter time only available if the 10006/2/2
diagnostic and battery module (DBM) is used.
5. For correct operation of the Modbus protocol, the number of
registers in the event request must be 64.
Event status The value of the event status byte depends on the type of event:
System messages For system messages, the event status field specifies if the event has
occurred or if the system has recovered from the event:
0 occurrence of event
FFh recovery from event
The sequence number of the system messages are calculated by the

FSC system, based on the configured base sequence number. Table
B-2 on the next page shows which system messages have been
defined.
Software Manual
Table B-2 SER system messages (Modbus)
Message Sequence number
All forces cleared 00h
FSC system fault 01h
SER buffer full 02h
SER buffer empty Base + 3
Force event 05h
Variable events For variable events, the event status field specifies the current status
of the variable.
Variable type I, O, M For variables of type I, O and M, the event status field indicates the
current status of the variable:
0 variable status is low
FFh variable status is high
Variable types T, C For all timer events and counter events, the event status has no
meaning. The field value is always 0.
Variable types AI, AO For the variable types AI and AO, the event status field indicates in
what range the analog value currently is:
02h value is larger than SER high value as configured
06h value is less than SER low value as configured
04h value within healthy range
Force events For variable force events, the event status field specifies if a force
was activated or deactivated:
0 force activated
FFh force deactivated
Software Manual
B.5 Sequence-of-Event Recording to a Printer
B.5.1 Introduction
Printer Sequence-of-event data can be sent to a printer that is directly

connected to the FSC system. Text SER is used for this purpose.
Text SER means that full text strings containing all event information
are sent to the printer, which output this information on paper. This
type of event recording requires much more communication resources
than numerical SER.
B.5.2 Configuration
Configuration If you wish to use the SER function and send the event data to a
requirements printer, the FSC configuration must contain the following:
1. a DBM module (except for the FSC slaves),
reporting, using the Printer communication protocol.
Note:
Setting up SER Setting up sequence-of-event recording to a printer consists of the

to a printer following steps:
2. Specifying the printer type (see subsection B.7.3), and
Software Manual
Supported events The following FSC event types are printed:
(force events),
(report events),
number).

B.8 on page B-26.
Software Manual
B.6 Numerical SER
B.6.1 Introduction
Numerical SER Numerical SER allows event recording with minimal communication
overhead. It is used for event recording to FSCSOE (the event
historian of the FSC product portfolio), PlantScape, or a Modbus
device (e.g. a DCS)
If numerical SER is used, a unique sequence number is assigned to all
Note:
Although in principle numerical SER can also be configured for
printers, this is not very practical. After all, the only thing
printed would be a constant string of meaningless hexadecimal
codes.
Supported events The following FSC event types are recorded using numerical SER:
(force events),
(report events) (not used by Modbus device),
(not used by FSCSOE or PlantScape)
• FSC diagnostic events (not used by Modbus device), and
number).
Software Manual
Setting up Setting up numerical SER to FSCSOE, PlantScape or a Modbus
numerical SER device consists of the following steps:
B.6.2 Configuring the SER Channel
Configuring Before sequence-of-event recording to FSCSOE, PlantScape or a

the SER channel Modbus device can be used, one of the available communication
channels needs to be defined as the "SER channel" (i.e. it is used to
request sequence-of-event data). The SER communication channel
must use one of the following communication protocols:
• Development System (DS) (for SER to FSCSOE),
• PlantScape (for SER to PlantScape), or
• Modbus (either RTU or H&B) (for SER to Modbus device).
Important!
To configure an SER channel and define its SER range, follow the
procedure below. (For further details on configuring an SER channel
refer to subsection 4.5.4 of this manual.)
1. In FSC Navigator, choose the System Configuration option.
2. Choose the Install option.
3. Choose the Configuration option. The system configuration
screen will appear.
4. Move the cursor to the SER channel specification field, and
press the <E> key on your keyboard to specify the SER channel
parameters. Please note that this field will only be available if you
have installed a communication module in your system.
The window as shown in Figure B-3 on the next page will appear.
Software Manual
Figure B-3 Configuring the SER channel and SER range
5. To allocate a communication channel to sequence-of-event

recording, move the cursor to the Primary SER channel field,
and make sure it is set to 'Yes'. Use <Space> to toggle between
'Yes' and 'No'.
Note:
You may also decide to leave the Primary SER channel field
to 'No' and proceed with defining the SER range. This allows
you to provide FSC variables with sequence numbers, and
actually activate the SER channel later.
6. Configure the SER channel (i.e. the communication channel that

is used to request sequence-of-event data) using the System
number, Central part, COM module and COM channel fields.
The SER channel may be defined in the current FSC system, but
also in another system in an FSC network.
Make sure that you refer to the correct communication channel
running the correct communication protocol for the SER output
device (FSCSOE, PlantScape, Modbus device, or a printer).
Software Manual
7. If you wish to define a redundant SER channel, also set the
Secondary SER channel field to 'Yes', and configure that SER
channel. (For details on SER channel redundancy refer to
subsection B.10.3 on page B-35.)
Note:
For further details on the SER channel specification refer to
subsection B.10 on page B-32.
B.6.3 Setting the SER Range
Setting the The SER range specifies the maximum number of FSC variables that
SER range are available for sequence-of-event recording (they are
"SER-enabled").The SER range is defined by the SER base and SER
maximum. To define the SER range, do the following:
1. In the SER channel configuration screen (see Figure B-3 on page
B-17), move the cursor to the SER base field. You may enter any
value between 1 and 65518 (see the note below).
2. Move the cursor to the SER maximum field. You may enter any
value between 17 and 65534 (see the note below). The SER
maximum must be higher than the SER base.
3. If you defined a redundant SER channel, make sure that you also
define the SER range for the secondary channel.
Note:
FSC will always reserve space for 16 system markers, which
means you should make the range at least 16 larger than the
number of variables you wish to SER-enable. The sequence
numbers of the SER-enabled FSC variables will all be in the
range specified.
In the example shown in Figure B-3 on the previous page, the
first available sequence number is 200 and the last 1216. This
means that a total of 1017 sequence numbers are available, but
since 16 of them are reserved for system markers, a maximum
of 1001 FSC variables can be SER-enabled. (If you attempt to
SER-enable more, an error message will be displayed saying
you should increase the SER range.)
As soon as you specify a non-zero value for the SER base or SER
maximum, numerical SER is assumed.
Software Manual
B.6.4 SER-Enabling of FSC Variables
SER-enabling FSC variables need to be prepared for sequence-of-event recording;

FSC variables in other words, they must be "SER-enabled". Also, they must be
provided with a sequence number. The device that receives the SER
data uses the sequence numbers to uniquely identify FSC variables.
To make FSC variables SER-enabled, do the following:
1. In FSC Navigator, choose the System Configuration option.
2. Choose the Hardware Specs option. A variable selection window
will appear. Use the Variable type and Tag number fields to
select the FSC variable you wish to make 'SER-enabled'. You can
press the <?> key to select from a list of available items.
3. After you have made your selection, the variable properties
window will appear which shows the properties of the selected
FSC variable (see Figure B-4 below). Once you are in the variable
properties window, you can use the PgUp and PgDn keys on your
keyboard to browse through all FSC variables in the configuration
database.
Figure B-4 SER-enabling FSC variables using FSC Navigator
Software Manual
4. Move the cursor to the SER enable (sequence) field. (This field
will be inaccessible if it is not available, e.g. because the FSC
variable cannot be SER-enabled.) Make sure this field contains
the value 'Yes'. You can use <Space> to toggle between 'Yes' and
'No'.
5. If you now press the down arrow key (↓) to move to the next
field, a sequence number will be automatically generated for the
FSC variable (see also the note below). This sequence number
will be used by FSCSOE, PlantScape or the Modbus device to
uniquely identify the variable.
6. Repeat the above steps until you have SER-enabled all the FSC
variables that you wish to use for sequence-of-event recording.
Note:
With the cursor in the SER enable (sequence) field you can
also press the right arrow key (→) on your keyboard. A
sequence number will then be generated automatically, and
you will move to the (editable) sequence number field.
If you press <F2> at this point, a window will appear that lists
which SER sequence numbers have been allocated to which
variables in the system. For details refer to Section 4 of the
FSC Software Manual.
Software Manual
B.7 Text SER
B.7.1 Introduction
Text SER Text SER is only used for event recording to printers that are directly
connected to the FSC system. Full text strings containing all event
information are sent to the printer, which output this information on
paper. This type of event recording requires much more
communication resources than numerical SER.
Setting up Setting up text SER to a printer that is directly connected to the FSC
text SER system consists of the following steps:
2. Specifying the printer type (see subsection B.7.3), and
B.7.2 Configuring the SER Channel
Configuring Before sequence-of-event recording to a printer can be used, one of

the SER channel the available communication channels needs to be defined as the
"SER channel" (i.e. it is used to request SER data). The SER
communication channel must use the Printer protocol.
The procedure for configuring the SER channel is the same as for
numerical SER (see page B-16).
Software Manual
B.7.3 Specifying the Printer Type
Specifying If event recording is to take place to a printer that is directly

the printer type connected to the FSC system, you need to specify the correct printer
type. To do that, follow the procedure below:
1. In FSC Navigator, choose the SER Formats option from the
Project menu.
2. Choose the SER format file option from the main menu.
(If this option is not available, numerical SER has been defined.
For details refer to subsection B.6 on page B-15.)
3. Choose the Printer config. option. The window as shown in
Figure B-5 on the next page will appear. Move to the Printer type
field, and press <Space> to toggle between the available printers.
You can also use the <?> command to choose from a list. Table
B-3 on the next page lists the available printers.
Figure B-5 SER printer configuration screen
Software Manual
Table B-3 Supported SER printers
NEC P7 Plus EPSON FX80+ FSC SER format
EPSON FX1000
EPSON RX80
There are two special printer types:

• Dummy printer
If you select this printer, all attributes specified in the report text
will be ignored.
• FSC SER format
If the FSC SER format has been selected, the marker service and
marker qualification may be available in the SER. To specify
marker services in the SER, use <Space> to toggle the 'Marker
service in EPROM' field to 'Yes'. To specify the marker
qualification in the SER, use <Space> to toggle the 'Marker
qualification in EPROM' field to 'Yes (see Figure B-6 on the next
page).
Printer parameters A number of extra printer parameters need to specified:

• page length,
• header margin,
• footer margin, and
• characters on line.
Software Manual
Figure B-6 FSCSER format
page before the footer is printed. The valid header margin range
Software Manual
B.7.4 SER-Enabling of FSC Variables
SER-enabling FSC variables need to be prepared for sequence-of-event recording;

FSC variables in other words, they must be "SER-enabled".
The procedure for SER-enabling FSC variables is the basically the
same as for numerical SER (see page B-19), except that no sequence
numbers need to be specified.
Software Manual
B.8 Event Specification
Overview The SER function of the FSC system records three types of events:
• Variable events (see subsection B.8.1),
• Force events (see subsection B.8.2), and
• Fault events (see subsection B.8.3).
Each of these event types is explained in more detail below.
B.8.1 Variable Events
Variable events A variable event is recorded if an event occurs for a process variable
which is SER-enabled. Variables can be enabled for sequence-of-
event recording using the 'System Configuration' option of FSC
Navigator.
Digital inputs (I) For variable type I, an event occurs if the application value of the
variable as applied to the application logic changes, i.e. Low → High
or High → Low.
The event report will contain the variable identification, the current
variable value and the date and time that the event occurred.
Digital outputs (O) For variable type O, an event occurs if the scan value of the variable
as applied to the process changes, i.e. Low → High or High → Low.
Analog inputs and For event recording of variable types AI and AO, three operational
outputs (AI, AO) areas are defined (Figure B-7):
1. the normal operational area, between the SER setpoint Low and
the SER setpoint High,
2. the low-level alarm area, below the SER setpoint Low, and
3. the high-level alarm area, above the SER setpoint High.
Software Manual
Setpoint Low Hysteresis
Maximum
Healthy
Minimum
Hysteresis Setpoint High
Figure B-7 Event definition for variable types AI and AO
Analog inputs (AI) For variable type AI, an event occurs if the variable application value
as applied to the application logic:
• becomes less than the SER setpoint Low (minimum event),
• exceeds the SER setpoint High (maximum event), or
• re-enters the normal operational area, between the SER setpoint
Low and SER setpoint High, compensated with a hysteresis
(healthy event).
operational area (high, low, healthy), and the date and time that the
event occurred.
Analog outputs For variable type AO, an event occurs if the variable scan value as
(AO) applied to the process:
• becomes less than the SER setpoint Low (minimum event),
• exceeds the SER setpoint High (maximum event), or
• re-enters the normal operational area, between the SER setpoint
Low and SER setpoint High, compensated with a hysteresis
(healthy event).
The event report will contain the variable identification and the date
and time that the event occurred.
Hysteresis The hysteresis (i.e. "lag") is 0.5% of the full scale of the analog value.
The absolute value depends on the configuration of the variable and
can be calculated as shown in the equation below.
Software Manual
For channels with range 0-20 mA, 0-5 V or 0-10 V, the following
equation is used:
10 ∗ ( top − bottom)
hysteresis = [engineering units]
1638
For channels with range 4-20 mA, 1-5 V or 2-10 V, the following
equation is used:
20 ∗ ( top − bottom)
hysteresis = [engineering units]
2621
Markers (M) For variable type M, an event occurs if the value of the variable
changes, i.e. Low → High or High → Low.
Timers (T) For variable type T, an event occurs if a running timer expires.
Counters (C) For variable type C, an event occurs if the counter value changes
from non-zero to zero.
Binary outputs For variable type BO, an event occurs if a trigger output that is
(BO) associated with the BO changes from Low to High.
The BO event can be regarded as the ability to sample the value of the
BO variable at user-definable criteria. The event report will contain
the variable identification, the current value of the BO variable and the
date and time that the event occurred. The BO must be allocated to the
channel where the SER is sent to.
The associated trigger output is automatically generated when a BO is
enabled for SER. The tag number of the trigger output will be equal to
the tag number of the BO variable. The location of the trigger output
is 'SYS'. Thus, it can be included in the application logic to generate
the event, and needs no further allocation to hardware.
Only BO variables with location 'COM' or 'FSC' can be SER-enabled.
Software Manual
B.8.2 Force Events
Force events A force event occurs if a process variable is forced or a force is

removed. The event report will contain the variable identification (tag
number), an indication if the force was activated or removed, and the
date and time that the event occurred.
If numerical SER has been configured and the forced variable is

SER-enabled, the variable is identified by its numerical sequence
number. If the forced variable is not SER-enabled, a generic
(non-specific) force event message is used.
If the force concerns a variable that is SER-enabled, a variable event
may occur as well.
An exceptional force event is generated if all forces are removed

simultaneously. The event report will then contain the 'All forces
cleared' event specification and the date and time that the event
occurred.
B.8.3 Fault Events
Fault events A fault event occurs if a fault is detected by the self-diagnostics of the
FSC system. The event report will contain the system number, rack
and position of the module the fault was detected at, and the date and
time that the event occurred.
If the fault affects a variable that is SER-enabled, a variable event may

occur as well.
Software Manual
B.9 SER Characteristics
This section discusses three SER characteristics:

• SER resolution (see subsection B.9.1),
• SER buffer capacity (see subsection B.9.2), and
• SER format (see subsection B.9.3).
B.9.1 SER Resolution
SER resolution The resolution of the SER channel is equal to the execution time of
the application. The application execution time is reported in the
translation log file, which can be viewed using the 'View Log' option
of FSC Navigator (see Section 9 of this manual, "Log Files").
The time stamping of the events has a resolution of 10 ms.
B.9.2 SER Buffer Capacity
SER buffer Until events have been successfully reported (via the SER
capacity communication channel), the FSC system stores the logged events in
its internal SER event buffer. The exact size of the SER buffer
depends on the system configuration, but the buffer can hold at least
448 events.
If the number of detected events exceeds the buffer capacity, all
subsequent events are ignored. This will ensure that the start of a plant
upset is preserved for post-mortem analysis. If the FSC event buffer
overflows as a result of communication failures with the event
management system, the FSC system will start overwriting events
older than four hours.
If a buffer overflow occurs, a specific event report is generated which

specifies the 'SER buffer full' event. This event contains the date and
time that the event occurred.
Software Manual
B.9.3 SER Format
SER format The layout of SER reports can be customized using the 'SER format'
option of FSC Navigator. SER report layouts are stored in the SER
format file.
For details on modifying the SER format refer to Section 5 of this
manual ("Editing Reports and SER Format").
If the SER function is used in combination with the FSCSOE

application, the standard "numerical SER" format must be configured.
Any custom SER format will be ignored.
In FSC networks, the SER format file is used of the application that
contains the SER communication part, e.g. the printer or user station
port.
Software Manual
B.10 SER Channel Specification
SER channel The SER channel specifies the communication channel which is used
specification to report events to the outside world. It is configured using the
'System Configuration' option of FSC Navigator (Install \
Configuration \ SER channel specification) (see Figure B-11).
In FSC communication networks, the SER channel may be located in

another system. This allows events of multiple systems to be reported
at one central point in the network.
B.10.1 SER Channels in Communication Networks
Communication There are two basic SER channel configurations in an SER

networks communication network:
• local, and
• global.
Each of these configurations is explained below.
Local SER In this configuration, each system has its own local SER channel that
is used by the SER PC to poll the FSC system.
FSC1 FSC2 FSC3
SER Printer
PC
Figure B-8 'Local' event collection in SER communication network
Software Manual
Global SER In this configuration, there is one global SER channel that is used by
the SER PC to poll all connected FSC systems. In the example below,
all connected FSC systems send their event data to FSC1, which is
polled by the SER PC.
FSC1 SER Printer

PC
FSC2 FSC3
FSC4 FSC5 FSC6
Figure B-9 'Global' event collection in SER communication network
Global and An SER communication network can also use both global and local
local SER event collection. In the example below, FSC2 sends its data to FSC1,
which is polled by SER PC 1 (global event collection). At the same
time, FSC2 is polled by SER PC 2 (local event collection).
Global SER
SER
FSC1 Printer
PC 1
SER FSC2 FSC3

PC 2
Local SER
Figure B-10 'Global' and 'local' event collection in SER

communication network
Software Manual
If both local SER and global SER are used, the primary SER must be
global and the secondary SER local. This means that the secondary
SER can never be global. In the example shown in Figure B-10, the
primary SER channel of FSC2 must be allocated to system number 1,
and the secondary SER channel to system number 2 (see Figure B-11).
Figure B-11 Primary and secondary SER channel
Also, the global and local SER must be of the same type (i.e. both
numerical or both text).
Software Manual
B.10.2 Single SER Channel
Single The basic SER channel layout is shown in Figure B-12. If Central
SER channel Part 1 shuts down, SER communication will continue. If, however,
Central Part 1 stops, SER communication will halt, and events are no
longer recorded.
CP1
SER
Printer
PC
CP2
Figure B-12 Single SER channel layout
B.10.3 Redundant SER Channels
Redundant To improve availability of the SER function, the SER channel may be
SER channels configured for redundant communication (see Figure B-13).
SER events are reported as long as one of the redundant
communication channels is operational. Refer to Appendix F of this
manual ("Communication") for further details on redundant
communication.
CP1
SER
Printer
PC
CP2
Figure B-13 Redundant SER communication channel
Software Manual
B.10.4 Dual SER Channels
Dual For optimum availability of the SER function, two SER channels may
SER channels be used (see Figure B-14).
As long as both channels are operational, all events are reported at
both channels. If one of the channels fails, events will continue to be
reported by the channel that is still operational.
CP1
SER Printer
PC
SER
CP2 Printer
PC
Figure B-14 Dual, redundant SER channels
B.10.5 SER Channel Availability
Diagnostics The operation of the SER channel is monitored by the FSC system.
If the channel is not able to report any events for a period of one
minute (e.g. because the SER collecting device is switched off), a
device communication error will be reported for that channel. This
error will persist until the channel is able to report events again.
If an SER configuration has a primary and secondary SER channel,

and one of the channels goes off-line, no events will be reported to the
event collector (e.g. FSCSOE) for a maximum of five minutes. Event
retrieval is not halted. Any incoming events retrieved by the healthy
channel are stored in the event buffer.
If the off-line SER channel becomes healthy again within five
minutes, the buffered events will be reported to the event collector,
and event retrieval and reporting will resume as normal for both
channels.
If the off-line SER channel does not recover within five minutes, all
buffered events are reported to the event collector, and the healthy
SER channel will resume event retrieval and reporting, despite the
off-line status of the other channel. When the off-line channel
Software Manual
becomes healthy again, it may have "missed" certain events which
were reported by the healthy SER channel, depending on the number
of incoming events.
Please note that no events will be lost.
Software Manual
Software Manual
Fail Safe Control
Appendix C:
Safety-Related Inputs with Non Fail-Safe
Sensors
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix C: Safety-Related Inputs with Non Fail-Safe Sensors
C.1 Introduction ....................................................................................................C-1
C.2 Safety-Related Digital Inputs with Non Fail-Safe Sensors...........................C-3

C.2.1 FSC Systems with Single Central Part.............................................................................C-3
C.2.2 FSC Systems with Redundant Central Parts ...................................................................C-5
C.3 Safety-Related Analog Inputs with Non Fail-Safe Transmitters ..................C-8

C.3.1 FSC Systems with Single Central Part.............................................................................C-8
C.3.2 FSC Systems with Redundant Central Parts .................................................................C-11
C.4 Function Blocks ...........................................................................................C-14
Software Manual
Appendix C: Safety-Related Inputs with Non Fail-Safe Sensors i
FIGURES
Figure C-1 Example of a safety-related input function with dual sensors.................................... C-2
Figure C-2 Redundancy type 201 for digital inputs...................................................................... C-3
Figure C-3 Redundancy type 201 for FSC systems with single CP ............................................ C-4
Figure C-7 Redundancy type 202 for FSC systems with redundant Central Parts ..................... C-6
Figure C-9 Redundancy type 302 for FSC systems with redundant Central Parts ..................... C-7
Figure C-10 Redundancy type 201 for analog inputs .................................................................... C-9
Figure C-12 Redundancy type 301 for analog inputs .................................................................... C-9
Figure C-13 Redundancy type 301 for FSC systems with single CP .......................................... C-10
Figure C-14 Redundancy type 202 for analog inputs .................................................................. C-11
Figure C-15 Redundancy type 202 for FSC systems with redundant Central Parts ................... C-12
Figure C-16 Redundancy type 302 for analog inputs .................................................................. C-12
Figure C-17 Redundancy type 302 for FSC systems with redundant Central Parts ................... C-13
Figure C-18 Function block FB-900 (2-out-of-3 function) ............................................................ C-14
Figure C-19 Function block FB-905 (2-out-of-3 function) ............................................................ C-14
Figure C-20 Function block FB-906 (mean function) ................................................................... C-15
Figure C-21 Function block FB-907 (part of FB-905)................................................................... C-15
TABLES
Table C-1 Possible redundancy types for various VBD functions .............................................. C-1
Software Manual
ii Appendix C: Safety-Related Inputs with Non Fail-Safe Sensors
Appendix C – Safety-Related Inputs with
Non Fail-Safe Sensors
C.1 Introduction
Safety-related Safety-related inputs require the use of fail-safe input modules, e.g.
inputs 10101/1/1, 10101/1/2 or 10101/1/3 for digital inputs, and 10102/1/1,
10102/1/2 or 10105/2/1 for analog inputs. It is also required that
fail-safe input devices (e.g. sensors, switches and transmitters) are
used.
Redundancy If the input device is not fail-safe, then redundant sensors

(transmitters) are required which are each connected to their own
FSC input channel. The sensor configuration depends on the number
of sensors and the function of the vertical bus driver (VBD) that
controls the rack which the input is connected to. The various
redundancy types are shown in Table C-1.
Table C-1 Possible redundancy types for various VBD functions

VBD function Redundancy types Description
Two input sensors, each connected to one input

201
channel (2-out-of-2 function).
Single
Three input sensors, each connected to one input
301
channel (2-out-of-3 function).
Two input sensors, two input channels per Central

202
Part (2-out-of-2 function per Central Part).
Redundant Three input sensors, each connected to one input
302
channel per Central Part (2-out-of-3 function per
Central Part).
Number of inputs per sensor

Number of sensors
The redundancy type can be selected using the 'System Configuration'

option of FSC Navigator.
Depending on the redundancy type, extra inputs may need to be
allocated. Extra inputs can only be allocated if the previous inputs
have been allocated correctly. If the allocation of the main input is
changed, the redundant inputs must be reallocated as well. The
Software Manual
Appendix C: Safety-Related Inputs with Non Fail-Safe Sensors C-1
redundant inputs must be allocated at an input module which is
controlled by the same VBD as the input module that the main input is
allocated to.
Figure C-1 shows an example of redundancy type 201 for digital

inputs which can be used for VBD functions with single I/O.
SENSOR-1 3
3
12
&
SENSOR_2 3 4 SENSOR-
3 S & 15 STATUS
11 t 0 6
t=6 min
R
Maximum On time
4 SENSOR_
S >1
_ 15 FAULT
t 0 5 "NO FAULT"
=1
t=10 s
R
Maximum discrepancy time
Figure C-1 Example of a safety-related input function with

dual sensors
Timers To check the safety of the digital sensors, they must switch in a
certain time interval. Also, the maximum on time is monitored,
which can be set in the range between 100 milliseconds and 2047
minutes (deactivation of the maximum on time is also possible). If the
maximum on time is exceeded, the resulting sensor status is switched
off. To detect if all inputs execute the switch function, an extra timer
is added: the maximum discrepancy timer (range: 100 milliseconds
to 2047 minutes). If the maximum on timer or the maximum
discrepancy timer expires, a redundant input fault and a sensor fault
are generated.
Note:
The maximum on time may also be deactivated. In that case, an
organizational procedure must exist which ensures periodical
testing of the sensors.
Software Manual
C-2 Appendix C: Safety-Related Inputs with Non Fail-Safe Sensors
C.2 Safety-Related Digital Inputs with Non Fail-Safe Sensors
Digital inputs The sensor configuration required for safety-related digital inputs
with non fail-safe sensors depends on the Central Part configuration
of the FSC system:
• single Central Part (see subsection C.2.1), or
• redundant Central Parts (see subsection C.2.2).
C.2.1 FSC Systems with Single Central Part
Single-channel Single-channel FSC configurations require the use of two or three

FSC configurations input sensors connected to a fail-safe digital input module.
If two input sensors are used, the redundancy type is 201.
If three input sensors are used, the redundancy type is 301.
2 sensors Both input sensors are connected to the FSC system (see Figure C-2).
(redundancy type 201) This may be to the same input module or to different input modules.
In the system software, an AND function is performed to determine
the resulting sensor status.
Figure C-2 Redundancy type 201 for digital inputs
Figure C-3 below shows an FLD example of redundancy type 201 for
FSC systems with a single Central Part.
Software Manual
SENSOR-1 3
3
12
&
SENSOR_2 3 4 SENSOR-
3 S & 15 STATUS
11 t 0 6
t=6 min
R
Maximum On time
4 SENSOR_
S >1
_ 15 FAULT
t 0 5 "NO FAULT"
=1
t=10 s
R
Figure C-3 Redundancy type 201 for FSC systems with single CP
3 sensors All three input sensors are connected to the FSC system (see Figure
(redundancy type 301) C-4). This may be to the same input module or to different input
modules. In the system software, a 2-out-of-3 function is performed
to determine the resulting sensor status.
SENSOR1 3
3
10 4 SENSOR
A D 15 STATUS
SENSOR2 3
3 B
FB 4
8 900 4 SENSOR.
C E 15 FAULT
SENSOR3 3 3 "NO FAULT"
3
9
Function block FB-900 (2-out-of-3 function) is shown in Figure C-18.
Software Manual
C.2.2 FSC Systems with Redundant Central Parts
Redundant For redundant FSC system configurations, the same sensor

FSC configurations configurations apply as for single-channel configurations, since one
part of the redundant system must be able to control the process.
These configurations, too, require the use of two or three input
sensors.
2 sensors Both input sensors are connected to both Central Parts of the FSC
(redundancy type 202) system (see Figure C-6). In the system software, an OR function is
performed for the synchronization in cases where faults can be
located, and an AND function in all other cases.
FSC systems with redundant Central Parts.
The status of the inputs is exchanged during the communication. The

input synchronization function for redundant systems is the OR
function in cases where faults can be located, and an AND function in
all other cases.
Software Manual
Central part 1
& 4 SENSOR-Cp1
S & 15 STATUS
t 0 2
t=6 min
R
Input Maximum On time
Synchronisation
4 SENSOR_Cp1
>1
_ S >1
_ 15 FAULT
t 0 1 "NO FAULT"
=1
t=10 s
>1 R
_
SENSOR-A1 3
3
7
Communication
Central part 2
SENSOR-A2 3 &
3 4 SENSOR-Cp2
6 S & 14 STATUS
t 0 16
t=6 min
R
Maximum On time
4 SENSOR_Cp2
>1
_ S >1
_ 14 FAULT
t 0 11 "NO FAULT"
=1
t=10 s
>1 R
_
Input Synchronisation
E C t H ll NL33
Figure C-7 Redundancy type 202 for FSC systems with

redundant Central Parts
3 sensors All three input sensor are connected to both Central Parts of the FSC
(redundancy type 302) system (see Figure C-8). For the synchronization in the system
software, an OR function is performed in cases where faults can be
located, and an AND function in all other cases. A 2-out-of-3
function is performed to determine the resulting sensor status.
Software Manual
Input Synchronisation Central part 1
>1
_
4 SENSOR-CP1
A D 14 STATUS
>1
_ B
FB 14
900 4 SENSOR_CP1
C E 14 FAULT
13 "NO FAULT"
>1
_
SENSOR-B1 3
1
13
SENSOR-B2 3
Communication
3
5
SENSOR-B3 3
1 Central part 2
14
Sensors connected
to both central
parts
>1
_
4 SENSOR-CP2
A D 14 STATUS
>1
_ B
FB 12
900 4 SENSOR_CP2
C E 14 FAULT
15 "NO FAULT"
>1
_


input synchronization function for redundant systems is the OR
function in cases where faults can be located, and an AND function in
all other cases.
Software Manual
C.3 Safety-Related Analog Inputs with Non Fail-Safe
Transmitters
Analog inputs The sensor configuration required for safety-related analog inputs
with non fail-safe sensors depends on the Central Part configuration
of the FSC system:
• single Central Part (see subsection C.3.1), or
• redundant Central Parts (see subsection C.3.2).
Maximum To check the functioning of redundant transmitters, they must be

discrepancy value within a certain bandwidth: the "maximum discrepancy value".
This maximum value is monitored, and can be set during the
configuration stage. If the maximum discrepancy value is exceeded,
the resulting transmitter status is switched to the bottom scale of the
analog input. If the maximum discrepancy value is exceeded, a
redundant input fault and a transmitter fault are generated.
C.3.1 FSC Systems with Single Central Part
Single-channel Single-channel FSC configurations require the use of two or three

FSC configurations transmitters connected to a fail-safe analog input module.
If two transmitters are used, the redundancy type is 201.
If three transmitters are used, the redundancy type is 301.
2 sensors Both input transmitters are connected to the FSC system (see Figure
(redundancy type 201) C-10). This may be to the same 10102/1/· input module or to different
10102/1/· input modules. In the system software, a mean function is
performed to determine the resulting transmitter status.
Software Manual
Figure C-10 Redundancy type 201 for analog inputs
Function block FB-906 (mean function) is shown in Figure C-20.
3 sensors All three input transmitters are connected to the FSC system (see
(redundancy type 301) Figure C-12). This may be to the same 10102/1/· input module or to
different 10102/1/· input modules.
Software Manual
The system software calculates the resulting transmitter status using
the following algorithm:
1. If the difference between the values of each pair of transmitters
(1-2, 1-3 and 2-3) is less than the maximum discrepancy value,
the resulting transmitter status is the mean value of the three
transmitters.
2. If the difference between the values of only two transmitters is
less than the maximum discrepancy value, the resulting
transmitter status is the mean value of these two transmitters. The
third transmitter is regarded faulty. Its value is ignored.
3. If the difference between the value of one transmitter (e.g.
transmitter 1) and both other transmitters (2 and 3) is less than the
discrepancy value, and
if the difference between the values of transmitters 2 and 3 is
more than the discrepancy value,
then two calculation algorithms are possible:
− If the differences between 1 and 2 and the difference between 1
and 3 are identical, the resulting transmitter status is the mean
value of the three transmitters.
− If the differences between 1-2 and 1-3 are not identical, the
resulting transmitter status is the mean value of the two
transmitters with the smallest difference. The third transmitter is
regarded faulty. Its value is ignored.
Figure C-13 below shows an FLD example of redundancy type 301

for FSC systems with a single Central Part.
Transmitter-1 A
D Transmitter_
A D status
Transmitter-2 A
B
FB Signal type: W
D 905 Transmitter-
C E fault
transmitter-3 A "No fault"
D
Software Manual
C.3.2 FSC Systems with Redundant Central Parts
Redundant For redundant FSC system configurations, the same transmitter

FSC configurations configurations apply as for single-channel configurations, since one
part of the redundant system must be able to control the process.
These configurations, too, require the use of two or three transmitters.
2 sensors Both transmitters are connected to both Central Parts of the FSC
(redundancy type 202) system (see Figure C-14). In the system software, a mean function is
performed to determine the resulting transmitter status.

input synchronization function for redundant systems is the mean
function (see Figure C-20).
Software Manual
TRANSMITTER-1 A
W 2
TRANSMITTER-CP1
A D STATUS
FB E
Signal type: W
906 TRANSMITTER_CP1
B C FAULT
"NO FAULT"
Transmitters W 2
Connected to both
central parts
Communication
Central part 2
W 2
TRANSMITTER-CP2
A D STATUS
FB E
Signal type: W
906 TRANSMITTER_CP2
B C FAULT
TRANSMITTER-2 A "NO FAULT"
D
W 2

Function block FB-906 (mean function) is shown in Figure C-20.
3 sensors All three transmitters are connected to both Central Parts of the FSC
(redundancy type 302) system (see Figure C-16). The system software calculates the
resulting transmitter status. The algorithm used is described in
subsection C.3.1.
Software Manual
Figure C-17 below shows an FLD example of redundancy type 302
for FSC systems with redundant Central Parts.
F 2
Transmitter-CP1
A D status
B
FB Signal type: W
905 Transmitter_CP1
F 2 C E fault
"no fault"
Transmitters
connected to both F 2
central parts
Communication
Central part 2
transmitter_1 A
F 2
transmitter_2 A
Transmitter-CP2
D A D status
B
FB Signal type: W
905 Transmitter_CP2
F 2 C E fault
transmitter_3 A "no fault"
D
F 2


input synchronization function for redundant systems is the mean
function (see Figure C-20).
Software Manual
C.4 Function Blocks
Function blocks Figure C-18 to Figure C-24 show the function blocks mentioned in
this appendix.
FB-900
Sensor-1 A
&
Sensor-2 B
& >1
_
S & D Sensor Status

t 0
Sensor-3 C t=6 min

R
&
Maximum On time
&
S >1
_ E fault Status
t 0
>1
_
t=10 s
R
>1
_ Maximum discrepancy time
Figure C-18 Function block FB-900 (2-out-of-3 function)
Transmitter 1
A E
Signal type: W
Transmitter 2 F
B
Signal type: W
G
Transmitter 3
C D
FB H D
Transmitter Status
Signal type: W Signal type: W
910
FB-905 C
A D
FB E E
906
B C F
G
A D FB
FB E
A
908
H
906 B
B C
C
A D D
FB E
906 F I
B C
G
A D C
FB J
909
E D
F E
B
FB G A
907
H L K
C J
E No fault
Figure C-19 Function block FB-905 (2-out-of-3 function)
Software Manual
FB-906
Transmitter1
A
Signal type: W
Transmitter2
Signal type: W B Transmitter Status
& D
Signal type: W
F 2
>
& Difference
E
Signal type: W
&
< C No fault
&
&
Max-Discrepancy
Transmitters
Signal type: W
Figure C-20 Function block FB-906 (mean function)
No fault 1 A FB-907
No fault 2 B & D Divide 3
No fault 3 C
& E Divide 2 or 3 "1"
& F Divide 2 or 3 "2"
& G Divide 2 or 3 "3"
& H Divide 2 "1"
& I Divide 2 "2"
& J Divide 2 "3"
Figure C-21 Function block FB-907 (part of FB-905)
Software Manual
FB-908
Dif 1-2
E
Signal type: W
=
Dif 1-3
F &
Signal type: W
Dif 2-3
G
Signal type: W
=
&
>1
_ H All 1-2-3
&
Divide 3 A
Divide 2 or 3 "1" B
Divide 2 or 3 "2" C
Divide 2 or 3 "3" D
Dif 1-2
Signal type: W
F
<
FB-909 &
Dif 1-3
G
Signal type: W
Dif 2-3
H >1
_ I
Signal type: W
<
&
>
&
>1
_ J
<
&
>
&
>
_1 K
>
Divide 2 or 3 "1" B &
Divide 2 or 3 "2" C
Divide 2 or 3 "3" D
Divide 2 "1" E
Divide 2 "2" A
Divide 2 "3" L
Software Manual
FB-910
Transmitter 1
E
Signal type: W
&
Transmitter 2 W 3
F
Signal type: W
Transmitter 3
G &
Signal type: W
W 2
Transmitter
H
Signal type: W
&
W 2
&
W 2
All 1-2-3 D
Only 1-2 C
Only 1-3 B
Only 2-3 A
Software Manual
Software Manual
Fail Safe Control
Appendix D:
On-Line Modification
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix D: On-Line Modification
D.1 Introduction ....................................................................................................D-1
D.2 Important Considerations ..............................................................................D-2

D.2.1 FSC Navigator Functionality.............................................................................................D-2
D.2.2 Limitations ........................................................................................................................D-2
D.2.3 Sheet Differences.............................................................................................................D-3
D.3 Preparations ...................................................................................................D-4

D.3.1 Installation Tools ..............................................................................................................D-4
D.3.2 Preparing EPROMs..........................................................................................................D-4
D.3.3 Electrostatic Discharge (ESD)..........................................................................................D-5
D.4 Procedure Overview.......................................................................................D-7
D.5 Preparing the On-Line Modification ............................................................D-11

D.5.1 Overview ........................................................................................................................D-11
D.5.2 Verifying TPS Compatibility With FSC System Software...............................................D-11
D.5.3 Comparing Applications in FSC System and User Station ............................................D-13
D.5.4 Making a Backup of the Application Files ......................................................................D-14
D.5.5 Verifying the On-Line Modification Option .....................................................................D-15
D.6 Modifying the Application............................................................................D-17

D.6.1 Overview ........................................................................................................................D-17
D.6.2 Making the Required Modifications to the Application ...................................................D-17
D.6.3 Translating the Application.............................................................................................D-18
D.6.4 Programming EPROMs..................................................................................................D-19
D.7 Upgrading the FSC System (FLASH Mode) ................................................D-21

D.7.1 Overview ........................................................................................................................D-21
Software Manual
Appendix D: On-Line Modification i
D.8 Upgrading the FSC System (RAM Mode) ................................................... D-34

D.8.1 Overview........................................................................................................................ D-34
D.8.4 Exchanging the CPU System EPROMs in Central Part 1............................................. D-37
D.8.5 Exchanging the Communication EPROMs in Central Part 1 ........................................ D-39
D.8.6 Exchanging the FSC-SMM EPROM in Central Part 1 .................................................. D-40
D.8.7 Downloading the CPU Application Program in Central Part 1 ...................................... D-41
D.8.11 Exchanging the CPU System EPROMs in Central Part 2............................................. D-48
D.8.14 Downloading the CPU Application Program in Central Part 2 ...................................... D-52
D.9 Upgrading the FSC System (EPROM Mode) .............................................. D-58

D.9.1 Overview........................................................................................................................ D-58
D.9.4 Exchanging the CPU EPROMs in Central Part 1.......................................................... D-61
D.9.7 Preparing Central Part 1 for Start-Up............................................................................ D-65
D.9.11 Exchanging the CPU EPROMs in Central Part 2.......................................................... D-69
D.9.14 Preparing Central Part 2 for Start-Up............................................................................ D-73
D.10 Extended Diagnostics During OLM ............................................................ D-76

D.10.1 Overview........................................................................................................................ D-76
D.10.2 Compatibility Check....................................................................................................... D-77
D.10.3 FSC Networks ............................................................................................................... D-78
D.11 Error Diagnostics ........................................................................................ D-79

D.11.1 Diagnostics Relating to Internal On-Line Modification Check ....................................... D-79
D.11.2 Diagnostics Relating to FSC Network Configuration Check ......................................... D-81
D.12 On-Line Rebuild........................................................................................... D-82
D.13 Modifying Tag Numbers On-Line................................................................ D-84

D.13.1 Input Tag Numbers........................................................................................................ D-84
D.13.2 Output Tag Numbers..................................................................................................... D-86
Software Manual
ii Appendix D: On-Line Modification
FIGURES
Figure D-1 ESD wrist-strap connected to ESD bonding point ......................................................D-5

Figure D-2 Activating the on-line modification option..................................................................D-16
Figure D-3 Download screen (FLASH) .......................................................................................D-25
Figure D-4 Downloading CPU application to RAM .....................................................................D-43
Figure D-5 Extended Diagnostics option ....................................................................................D-76
Figure D-6 Sheet differences during on-line modification...........................................................D-77
Figure D-7 Allocation in variables to locations in system memory..............................................D-82
Figure D-8 On-Line Rebuild option .............................................................................................D-83
Software Manual
Appendix D: On-Line Modification iii
TABLES
Table D-1 Operating modes........................................................................................................ D-7

Table D-2 Compatibility matrix FSC-SM vs. TPS ..................................................................... D-12
Table D-3 Verifying TPS compatibility with FSC system software ........................................... D-12
Table D-4 Verifying the FSC application files ........................................................................... D-14
Table D-5 Backing up your FSC application files ..................................................................... D-14
Table D-6 Activating the on-line modification option................................................................. D-15
Table D-7 Modifying the application.......................................................................................... D-18
Table D-8 Translating the application ....................................................................................... D-18
Table D-9 EPROM requirements for each operating mode...................................................... D-19
Table D-10 Programming the EPROMs...................................................................................... D-19
Table D-11 Making a backup of the modified application files.................................................... D-20
Table D-12 FLASH: Checking the FSC system .......................................................................... D-22
Table D-13 FLASH: Shutting down Central Part 1 ..................................................................... D-23
Table D-14 FLASH: Downloading software for Central Part 1.................................................... D-24
Table D-15 FLASH: Reloading the Personality Image for Central Part 1................................... D-27
Table D-16 FLASH: Starting up Central Part 1 ........................................................................... D-28
Table D-17 FLASH: Shutting down Central Part 2 ..................................................................... D-29
Table D-18 FLASH: Downloading software for Central Part 2.................................................... D-30
Table D-19 FLASH: Reloading the Personality Image for Central Part 2................................... D-31
Table D-20 FLASH: Starting up Central Part 2 ........................................................................... D-32
Table D-21 FLASH: Making a backup of the modified application files...................................... D-33
Table D-22 RAM: Checking the FSC system ............................................................................. D-35
Table D-23 RAM: Shutting down Central Part 1 ......................................................................... D-36
Table D-24 RAM: Exchanging the CPU system EPROMs in Central Part 1 .............................. D-37
Table D-25 RAM: Exchanging the communication EPROMs in Central Part 1.......................... D-39
Table D-26 RAM: Exchanging the FSC-SMM EPROM in Central Part 1 ................................... D-40
Table D-27 RAM: Downloading the CPU application program in Central Part 1........................ D-41
Table D-28 RAM: Reloading the Personality Image for Central Part 1....................................... D-45
Table D-29 RAM: Starting up Central Part 1............................................................................... D-46
Table D-30 RAM: Shutting down Central Part 2 ......................................................................... D-47
Table D-31 RAM: Exchanging the CPU system EPROMs in Central Part 2 .............................. D-48
Table D-32 RAM: Exchanging the communication EPROMs in Central Part 2.......................... D-50
Table D-33 RAM: Exchanging the FSC-SMM EPROM in Central Part 2 ................................... D-51
Table D-34 RAM: Downloading the CPU application program in Central Part 2....................... D-52
Table D-35 RAM: Reloading the Personality Image for Central Part 2....................................... D-56
Table D-36 RAM: Starting up Central Part 2............................................................................... D-57
Table D-37 EPROM: Checking the FSC system ........................................................................ D-59
Table D-38 EPROM: Shutting down Central Part 1.................................................................... D-60
Table D-39 EPROM: Exchanging the CPU system EPROMs in Central Part 1......................... D-61
Table D-40 EPROM: Exchanging the communication EPROMs in Central Part 1..................... D-63
Table D-41 EPROM: Exchanging the FSC-SMM EPROM in Central Part 1.............................. D-64
Table D-42 EPROM: Preparing Central Part 1 for start-up......................................................... D-65
Table D-43 EPROM: Reloading the Personality Image for Central Part 1 ................................. D-66
Table D-44 EPROM: Starting up Central Part 1 ......................................................................... D-67
Table D-45 EPROM: Shutting down Central Part 2.................................................................... D-68
Table D-46 EPROM: Exchanging the CPU system EPROMs in Central Part 2......................... D-69
Table D-47 EPROM: Exchanging the communication EPROMs in Central Part 2..................... D-71
Table D-48 EPROM: Exchanging the FSC-SMM EPROM in Central Part 2.............................. D-72
Table D-49 EPROM: Preparing Central Part 2 for start-up......................................................... D-73
Table D-50 EPROM: Reloading the Personality Image for Central Part 2 ................................. D-74
Table D-51 EPROM: Starting up Central Part 2 ......................................................................... D-75
Software Manual
iv Appendix D: On-Line Modification
Appendix D – On-Line Modification
D.1 Introduction
On-line On-line modification (OLM) is a TÜV-approved FSC system option

modification which allows you to modify the application software, system software
and the FSC hardware configuration of redundant systems, while the
system remains operational. During on-line modification, the changes
are upgraded in one Central Part at a time. Meanwhile, the other
Central Part continues to monitor the process.
During the upgrade, the FSC system performs a compatibility check

across the application-related data, in order to guarantee a safe
changeover from the old software to the new software. The system
reports the numbers of the functional logic diagrams (FLDs) that have
changed. This allows easy verification of the implemented
modification within the application. Additional verification of the
changes can be obtained using the 'Verify Application' option of FSC
Navigator (see Section 11 of this manual).
The on-line modification feature of the FSC system allows changes in

the functional logic diagrams, the FSC system configuration and the
system software to be implemented in the system without the need of
a plant shutdown.
Important!
The amount of human interaction during the modification
process is considerable. On-line modification should therefore
be carried out with the utmost care, and by authorized and
qualified persons only. In case of problems during the on-line
modification, the FSC system can go to a safe state resulting in
a process shutdown.
It is strongly recommended that anyone performing an on-line
modification first follows the On-Line Modification (OLM)
training course offered by HSMS (course number 4502).
Software Manual
Appendix D: On-Line Modification D-1
D.2 Important Considerations
D.2.1 FSC Navigator Functionality
Function As the creation of application-related data is controlled by certain

limitations options of the FSC Navigator software, these options must be
prevented from performing any functions that could lead to
incompatibilities between the old and new application. This is done
by setting the on-line modification to active (see subsection D.5.5 on
page D-15). To protect the system integrity, the following functions
in FSC Navigator are not available when on-line modification is
active:
• System Configuration:
− change the name of allocated tag numbers, and
− change configured hardware modules.
• Design FLDs:
− change the name of used tag numbers,
− renumber FLDs, and
− append an application.
D.2.2 Limitations
Limitations Please note the following limitations with regard to on-line

modification:
1. During an on-line modification, make sure that you do NOT
increase the memory area for any communication channel.
2. The following modifications cannot be made on-line:
− Non-redundant ("single") I/O racks cannot be added or deleted.
− System software cannot be upgraded if the system is running an
FSC release older than 2.80b1.
− It is not possible to add or remove communication links that use
the FSC-FSC communication protocol (e.g. master/slave
combinations).
Software Manual
D-2 Appendix D: On-Line Modification
2. On-line modification and start-up of redundant systems
configured in "warm start" mode may give spurious diagnostic
messages.
3. It is possible to add and delete all types of variables during an
on-line modification, including timers, inputs and outputs. If an
output is deleted which was high at the time of the on-line
modification, the output will remain high after it is removed from
the application program.
4. During on-line modification, the number of SER messages
generated within the FSC network must be limited in order to
reduce the chance that SER data is lost when the modified Central
Part is started and the running Central Part is shut down.
5. The FSC system performs the compatibility check for connected
systems each time it is started, regardless whether modifications
were made in the system or not. The extended diagnostics should
therefore always be examined prior to starting the system, to
verify if all communication links are intact.
D.2.3 Sheet Differences
Sheet differences The following considerations are important with regard to reported
sheet differences:
1. If a function block has changed, a difference will be reported for
all functional logic diagrams that use this function block.
2. If the force enable status of the inputs with location 'COM' or
'FSC' has changed, a sheet difference will be reported for the
FLDs that contain these variables.
3. If you perform an on-line upgrade to FSC Release 530 from a
release prior to R510, sheet differences will be reported for all
functional logic diagrams (FLDs) that contain mathematical
routines, PIDs and/or equation blocks, even though no
modifications were implemented. This is normal behavior. FSC
R510 and higher use a different internal addressing scheme than
previous releases, which causes the above sheet differences to be
reported.
4. During on-line modification, the 'Verify Application' option may
be used to log all revision information (see Section 11 of this
manual for details).
Software Manual
D.3 Preparations
D.3.1 Installation Tools
Installation tools Make sure that you have the following tools at hand when performing
an on-line modification (EPROM mode and RAM mode only):
• Flatblade screwdriver,
• Phillips screwdriver,
• Torque wrench (only if an FSC-SMM is used),
• FSC EPROM programmer type 07170/1/1, including 07170/A/1
adapter module (only if EPROMs are to be exchanged),
• EPROM remover (only if EPROMs are to be exchanged),
• EPROM eraser (only if EPROMs are to be exchanged), and
• Antistatic ESD wrist-strap (see subsection D.3.3).
D.3.2 Preparing EPROMs
Preparing EPROMs If the on-line modification requires EPROMs to be programmed, you

(if required) should preferably do that in advance in order to minimize the time
required to upgrade the software of the FSC system. Make sure that
you prepare the EPROMs for the FSC system software, FSC
applications, and/or FSC communication software before starting the
actual on-line modification. Blank EPROMs may be required for the
following software:
1. FSC system program (RAM and EPROM mode).
This requires one 10002/A/x memory print for each 10002/1/2
CPU module.
2. FSC application program (EPROM mode only).
This requires four EPROMs per CPU module. The size of the
EPROMs is mentioned in the log file that was created when the
application was translated.
For details on log files refer to Section 9 of this manual.
For details on verification refer to Section 11 of this manual.
3. FSC communication program (RAM and EPROM mode).
This requires four EPROMs per communication (COM) module.
The size of the EPROMs is shown in the main window of the
'Program EPROMs' option of FSC Navigator.
For details on EPROM programming refer to Section 10 of this
Software Manual
4. FSC-SMM firmware (all modes, if 10008/2/U module is used).
This EPROM only needs to be replaced if the firmware is to be
updated. It requires one 4-Mb EPROM per 10008/2/U FSC Safety
Manager Module (FSC-SMM).
Notes:
1. The EPROM programming option of FSC Navigator is only
available if the 07170 EPROM programmer is connected to
the FSC user station.
2. The EPROM types that are supported by the 'Program
EPROMs' option of FSC Navigator are listed in Section 10
of this manual ("Loading Software").
3. You need to install a special communication driver to be
able to use the 07170 EPROM programmer. For details refer
to section 2.3 of this manual.
D.3.3 Electrostatic Discharge (ESD)
Electrostatic It is extremely important that you wear a properly connected

discharge (ESD) electrostatic discharge (ESD) wrist-strap while removing, handling
and installing any electronic components. (see Figure D-1).
Figure D-1 ESD wrist-strap connected to ESD bonding point
Software Manual
Slip the strap on your wrist like a wristwatch and connect its clip to
the ESD bonding point, which is located inside the cabinet. There is
no danger of receiving a shock from an approved wrist-strap.
Be sure to keep any electronic component in a static-safe carrying
pouch whenever it is not in use.
An ESD kit is available through your local Honeywell service
organization.
Software Manual
D.4 Procedure Overview
Important!
Before carrying out the on-line modification, make sure that
you read the entire on-line modification procedure and that you
completely understand it.
In case of problems during the on-line modification, the FSC
system may go to a safe state resulting in a process shutdown.
Operating The exact OLM procedure to be followed depends on the operating

modes mode that the FSC system is running in. There are three operating
modes:
• EPROM,
• RAM, and
• FLASH.
The operating mode determines how the FSC-related software is
transferred to the FSC system as shown in the table below:
Table D-1 Operating modes

EPROM RAM FLASH
COM software EPROMs EPROMs download**
CPU software (system) EPROMs EPROMs download**
CPU software (application) EPROMs download* download**
* To on-board RAM or additional 1-Mb or 4-Mb memory boards.
** To flash memory (requires suitable hardware modules).
Notes:
1. Communication software larger than 2 Mb cannot be loaded
into EPROMs. This must be loaded to flash memory
(FLASH).
Main stages On-line modification basically consists of three main stages:

A) Preparing the on-line modification (see subsection D.5),
B) Modifying the application (see subsection D.6), and
C) Upgrading the FSC system (see subsections D.7, D.8, and D.9).
Software Manual
Stage A Preparing the on-line modification (see subsection D.5).
Before the on-line modification can be carried out, some preparations
need to be made. This stage consists of the following steps:
A.1) Verify TPS compatibility with FSC system software
(only for FSC-SM).
A.2) Make sure the application in the FSC system is identical to the
application that is stored on the user station (FSC Navigator).
A.3) Make a backup of the application files in your project folders.
A.4) Make sure the on-line modification option is activated.
For details on each step refer to subsection D.5.
Stage B Modifying the application (see subsection D.6).

This stage involves changing the application program using the FLD
design editor, and preparing it for use in the FSC system. It consists of
the following steps:
B.1) Make the required modifications to the application.
B.2) Translate the application.
B.3) Program the EPROMs (RAM/EPROM mode only).
B.4) Make a backup of the modified application files in your project
files (RAM/EPROM mode only).
Note:
For flash mode, it is not necessary to make a backup of the
modified application files at this point. They need to be backed
up at the very end of the OLM procedure (see subsection
D.7.11).
Software Manual
Stage C Upgrading the FSC system (see subsections D.7 to D.9).
In this stage the actual on-line modification is carried out. The exact
procedure to be followed depends on the operating mode of the FSC
system (FLASH, RAM, or EPROM).
FLASH C.1) Check the system before upgrading the FSC system.
C.2) Shut down Central Part 1.
C.3) Download the software for Central Part 1.
C.4) Reload the Personality Image (PI) for Central Part 1
(only for FSC-SM).
C.5) Start up Central Part 1.
(only for FSC-SM).
C.10) Make a backup of the modified application files.
RAM C.1) Check the system before upgrading the FSC system.
C.3) Exchange the CPU system EPROMs in Central Part 1
(only in case of a software release upgrade).
C.4) Exchange the communication EPROMs in Central Part 1.
C.5) Exchange the FSC-SMM EPROM in Central Part 1
C.6) Download the CPU application program in Central Part 1.
(only for FSC-SM).
C.12) Exchange the FSC-SMM EPROM in Central Part 2.
Software Manual
(only for FSC-SM).
EPROM C.1) Check the system before upgrading the FSC system.
C.3) Exchange the CPU system EPROMs (only in case of a
software release upgrade) and application EPROMs in Central
Part 1.
C.6) Prepare Central Part 1 for start-up.
(only for FSC-SM).
Part 2.
(only for FSC-SM).
Software Manual
D.5 Preparing the On-Line Modification
D.5.1 Overview
ATTENTION ATTENTION — Make sure that you carefully read each step in its
entirety before actually carrying out the step!
Stage A Before any on-line modification can be carried out, some preparations
need to be made. This stage consists of the following steps:
A.1) Verify TPS compatibility with FSC system software
(only for FSC-SM).
A.2) Make sure the application in the FSC system is identical to the
A.3) Make a backup of the application files in your project folders.
A.4) Make sure the on-line modification option is activated.
D.5.2 Verifying TPS Compatibility With FSC System Software
ATTENTION If your system does not contain an FSC Safety Manager (FSC-SM),
skip this step and proceed with step A.2 (see subsection D.5.3 on
page D-13).
Step A.1
FSC-SM ONLY Verify TPS compatibility with FSC system software.
Prior to proceeding with an on-line modification of the FSC system
software, you need to verify that the correct TPS software release has
been loaded.
Note:
If an upgrade of the TPS software is required (see Table D-2),
load the TPS software according to the procedure mentioned in
the TPS documentation without loading the Personality Image
(PI) software of the FSC Safety Manager. The PI software of the
FSC Safety Manager must be loaded during the on-line
modification procedure as described in subsections D.7 to D.9.
Software Manual
Table D-2 Compatibility matrix FSC-SM vs. TPS
FSC-SM TPS
Release 400.2, 400.3 Release 510.7, 510.8,
Release 520.1 and 520.2
Release 420.x Release 521.7 or higher
Release 50x.x Release 521.7 or higher
Release 51x.x (see note 1 below) Release 521.7 or higher
The TPS software version can be obtained from the TPS operator
station (US, UXS, GUS). For details refer to the TPS documentation.
Notes:
1. To see diagnostic information for the modules that were
introduced with FSC Release 510 (10106/2/1, 10012/1/2,
10014/x/x, 10018/2/U), you need TPS Release 600.1 or
higher.
2. To see diagnostic information for the modules that were
introduced with FSC Release 530 (10020/1/1 and
10024/x/x), you need TPS Release 620.1 or higher.
If you use an older release, any messages related to these
modules will refer to "undefined modules", with the error
code being displayed rather than the description.
Table D-3 below describes the procedure for checking the TPS
compatibility with the FSC system software.
Table D-3 Verifying TPS compatibility with FSC system software

Step Action Done
A.1 (=)
a) Make sure the TPS software version is compatible with the
FSC software release that the FSC system is running on
(FSC-SMM only). The TPS software version can be
X
obtained from the TPS operator station (US, U S, GUS).
For details refer to the TPS documentation.
b) You are now ready to compare the applications in the FSC
system and the FSC user station (see next subsection).
Software Manual
D.5.3 Comparing Applications in FSC System and User Station
Step A.2 Make sure the application in the FSC system is identical to the
The FSC Navigator software offers two ways to accomplish this:
1. Verification of the application, or
2. Direct comparison of version information.
Note:
Both methods require a connection to your FSC system via an
FSC Development System (FSC-DS) communication link.
Application Use the 'Verify Application' option of FSC Navigator to verify the
verification application in the FSC system against the application on the FSC user
station. For details refer to Section 11 of this manual ("Verifying an
Application").
This is the preferred verification method. Only if this method cannot
be used may the alternative method below be used.
Version An alternative verification method is comparing the version of the

comparison application in the FSC system with the version of the application that
is stored on the FSC user station (FSC Navigator):
− The version of the application in the FSC system can be determined
using the 'Monitor System' option of FSC Navigator (FSC System \
Sys info \ Versions \ Current application version).
− The version of the application on the FSC user station can be
determined by viewing the translation log file.
Notes:
1. The above method will only work if the previous upgrade
was carried out in accordance with the on-line modification
procedures outlined in this section.
2. The above method will only ensure that the applications in
the FSC system and on the FSC user station are identical if
no modifications were made to the application at the FSC
user station without running the 'Translate Application'
option of the FSC user software afterwards.
Software Manual
Table D-4 Verifying the FSC application files
Step Action Done
A.2 (=)
a) Verify that the application in the FSC system is identical to
the application that is stored on the FSC user station.
Method used: Verify Application / Compare Application*
b) You are now ready to make a backup of your application
files (see next subsection).
* Strike out whatever is not applicable.
D.5.4 Making a Backup of the Application Files
Step A.3 Make a backup of the application files in your project folders.
Table D-5 Backing up your FSC application files

Step Action Done
A.3 (=)
a) Make a backup of the application files in your project
directories. The project directories are all subdirectories of
the FSC application directory (C:\FSC by default). The
names of the directories are identical to the project names.
Thus, if you have a project called 'PROJ', the corresponding
project files will be located in a subdirectory called 'PROJ'
(usually C:\FSC\PROJ\). Make sure that you remember the
directory name, and that you copy all files in the project
directory.
It is recommended that you use removable storage media
for your backup (e.g. floppy disk, CD-R, or ZIP disk).
b) You are now ready to verify the on-line modification option
(see next subsection).
Important!
1. Make sure that Windows shows all files, and does not hide
certain system files. Otherwise the backup will not include
the functional logic diagram (FLD) with the number 386. If
you then restore the backup, you cannot translate because
an FLD is missing. (Please note that this is not a problem
related to FSC Navigator, but a Windows-related issue.)
For details refer to section 2.5 of this manual.
Software Manual
Important!
2. For flash-memory applications, the master project files are
located on the computer where the software downloads are
carried out. Always make sure that you back up the project
files from that computer. Please note that this may be a
different computer than the designated master computer!
3. For EPROM/RAM applications, the master project files are
located on the computer where the EPROMs were
programmed (i.e. the computer that the EPROM
programmer is connected to). Always make sure that you
back up the project files from that computer. Please note
that this may be a different computer than the one used to
communicate with the FSC system!
D.5.5 Verifying the On-Line Modification Option
Step A.4 Make sure the on-line modification option is activated.

On-line modification (OLM) is only possible in systems with
redundant Central Parts. Before on-line modification can be
performed, the on-line modification option must first be activated.
Table D-6 Activating the on-line modification option

Step Action Done
A.4 (=)
a) Choose the 'System Configuration' option of FSC Navigator.
b) Choose Install from the main menu.
c) Choose Configuration from the submenu.
d) Move to the On-line modification wanted field.
e) Make sure this field is set to 'Yes'. If it is not, use <Space>
to toggle the field value to 'Yes', and press <Enter> to
record the status (see Figure D-2 on the next page).
f) You are now ready to modify the application (see next
subsection).
Note:
For systems that do not have redundant Central Parts, the on-line
modification option will be disabled.
Software Manual
Figure D-2 Activating the on-line modification option
Setting the on-line modification option to 'Yes' will not affect the
behavior of the FSC system. The system will always perform a safety
compatibility check across the application-related data when new
software is loaded into the system.
As the creation of application-related data is controlled by certain

options of the FSC Navigator software, these options must be
prevented from performing any functions that could lead to
incompatibilities between the old and new application. This is done by
setting the on-line modification to active. Section D.2.1 contains a list
of the FSC Navigator functions that are affected when on-line
modification has been activated.
Software Manual
D.6 Modifying the Application
D.6.1 Overview
Stage B Before the actual on-line modification can be carried out, you need to
change the application program using the FLD design editor, and
prepare it for use in the FSC system. This stage consists of the
following steps:
B.1) Make the required modifications to the application.
B.2) Translate the application.
B.3) Program the EPROMs (RAM/EPROM mode).
B.4) Make a backup of the application files in your project files
(RAM/EPROM mode only).
D.6.2 Making the Required Modifications to the Application
Step B.1 Make the required modifications to the application.

Use the FLD design editor to change the functional logic diagrams of
the application. For details on FLDs refer to Section 6 of this manual
If there are any changes in the application software, it is strongly

recommended that you test the application in an FSC simulation unit
prior to upgrading the actual system (see Appendix H of this manual).
This allows you to detect and correct any serious errors that could lead
to unsafe situations or a total system shutdown (e.g. calculation errors)
before going on-line.
Software Manual
Table D-7 Modifying the application
Step Action Done
B.1 (=)
a) Make the required modifications to the application.
b) If the FSC system also needs to be upgraded to an FSC
Safety Manager, reconfigure your application in accordance
with the FSC to FSC Safety Manager upgrade kit (model
MP-ZFSCSM2).
c) You are now ready to translate the application (see next
subsection).
D.6.3 Translating the Application
Step B.2 Translate the application.

For details on translating the application refer to Section 8 of this
Table D-8 Translating the application

Step Action Done
B.2 (=)
a) Translate the application.
b) After translating, use the 'View Log' option of FSC Navigator
to read the translation log file. If any errors were detected,
correct these errors and translate the application again.
c) Repeat steps a) and b) until the translation log file reports
no errors.
d) You are now ready to program the EPROMs (if required)
Software Manual
D.6.4 Programming EPROMs
ATTENTION If your system operates in FLASH mode, skip this step and proceed
with step C (see subsection D.6.5 on page D-20).
Step B.3
EPROM/RAM ONLY Program the EPROMs (RAM/EPROM mode).
During the upgrade, EPROMs may need to be replaced. These
EPROMs should be prepared in advance in order to minimize the
off-line time of a Central Part. Table D-9 below lists the EPROM
requirements for each operating mode.
Table D-9 EPROM requirements for each operating mode

FLASH RAM EPROM
FSC system program EPROMs – = =

FSC application program EPROMs – – =
FSC communication program EPROMs – = =
1)
FSC-SMM firmware –/= = =
1) No EPROM is required if 10018/2/U is used.

EPROM is required if 10008/2/U is used.
Use the 'Program EPROMs' option of FSC Navigator to program the

EPROMs. Make sure that you program EPROMs for both Central
Parts. The following sequence is recommended:
1. Blank check,
2. Program, and
3. Verify.
Provide all EPROMs with a unique identification with regard to

module type, module number, Central Part number, date and version
number (in case of more than one upgrade on one day).
For details on programming EPROMs refer to Section 10 of this
Table D-10 Programming the EPROMs

Step Action Done
B.3 (=)
a) Program all required EPROMs.
b) You are now ready to upgrade the FSC system
(see subsection D.7, D.8, or D.9).
Software Manual
D.6.5 Making a Backup of the Modified Application Files
Backup For EPROM and RAM applications, it is essential that you make a
backup of the modified application files in your project folders before
starting the actual system upgrade. Table D-11 below describes the
procedure for making a back-up of the modified FSC application.
Note:
For flash mode, it is not necessary to make a backup of the
modified application files at this point. They need to be backed
up at the very end of the upgrade procedure (see subsection
D.7.11).
Table D-11 Making a backup of the modified application files

Step Action Done
B.4 (=)
directory.
b) You can now proceed with the on-line system upgrade as
described in Sections D.7 to D.9.
Important!
2. The master project files are located on the computer where
the EPROMs were programmed (i.e. the computer that the
EPROM programmer is connected to). Always make sure
that you back up the project files from that computer. Please
note that this may be a different computer than the one used
to communicate with the FSC system!
Software Manual
D.7 Upgrading the FSC System (FLASH Mode)
D.7.1 Overview
ATTENTION ATTENTION — If you have a master/slave configuration, the steps

in stage C must be carried out per system. Make sure that you start
with the master system.
Upgrading The modifications that were made to the application need to be

FSC system implemented in the FSC system, i.e. the software needs to be loaded
(FLASH) into the system's non-volatile flash memory. The software is
upgraded in one Central Part at a time. This stage consists of the
following steps:
C.1) Check the system before upgrading the FSC system.
(only for FSC-SM).
C.6) Shutting down Central Part 2.
(only for FSC-SM).
C.10) Make a backup of the modified application files.
Software Manual
D.7.2 Checking the System
Step C.1 Check the system before downloading the software.

Before upgrading the FSC system, use the 'Extended Diagnostics'
option of FSC Navigator to verify that the FSC system is OK. Make
sure that you check the extended diagnostics of both Central Parts.
You can use Alt+<C> to switch between Central Parts.
If FSC Navigator reports any errors, resolve these errors before
downloading the software. (Please note that the error messages
'Analog input sensor break alarm' and 'Analog output value invalid'
may be ignored here.)
Important!
If you fail to repair all hardware failures before on-line
modification, the process may shut down during the on-line
modification process.
Table D-12 FLASH: Checking the FSC system

Step Action Done
C.1 (=)
a) Before proceeding with the on-line modification, use the
'Extended Diagnostics' option of FSC Navigator to check
both Central Parts of the FSC system. You may only
continue if no faults are found.
b) You are now ready to shut down Central Part 1 (see next
subsection).
Software Manual
D.7.3 Shutting Down Central Part 1
Step C.2 Shut down Central Part 1 (CP 1).
Table D-13 FLASH: Shutting down Central Part 1

Step Action Done
C.2 (=)
a) If the CPU module in the system is of type 10012/1/2, make
sure that the Force Enable key switch is activated. For CPU
modules of type 10020/1/1, the position of the Force Enable
key switch does not matter.
Important!
If the Force Enable key switch is already activated, leave it
as it is. If you deactivate and reactivate the key switch, all
existing forces will be lost, which may result in a system
shutdown.
b) Shut down Central Part 1. This can be done in a number of
ways, depending on the CPU module type in the system:
• 10012/1/2: The bus immediately above the Central Part
may have an ESD key switch, located to the
right of the watchdog flatcable connector. If
this is the case, shut down the Central Part by
setting this switch to the horizontal position.
Otherwise, pull the flatcable from the
connector.
• 10020/1/1: Set the three-way key switch to the 'IDLE'
position.
After the Central Part has shut down, the Watchdog (WD)
LED on the module will go out.
c) After Central Part 1 has shut down, do the following:
• 10012/1/2: Set the ESD key switch to its vertical position
again, or reconnect the flatcable of the
watchdog (depending on the way the Central
Part was shut down in step C.2b).
• 10020/1/1: You do not have to do anything.
d) If the FSC system does not contain a 100x8/2/U FSC Safety
Manager Module (SMM), skip steps e) and f) and proceed
with step g).
e) Shut down the secondary Safety Manager (even node
X
number) via the TPS operator station (US, U S, GUS).
f) Wait for the secondary Safety Manager to become 'ALIVE'
X
on the TPS operator station (US, U S, GUS).
g) You are now ready to download the software for Central
Part 1 (see next subsection).
Software Manual
D.7.4 Downloading the Software for Central Part 1
Step C.3 Download the software for Central Part 1.
Table D-14 FLASH: Downloading software for Central Part 1

Step Action Done
C.3 (=)
a) Start the FSC Navigator user software and choose the
Download option:
Load Software / Download
For further details on downloading software refer to Section
10 of this manual ("Loading Software").
b) You will be asked to select the Central Part whose software
you wish to download. Make sure that you start with Central
Part 1. You can press <Space> to toggle between the
Central Parts. Press <Enter> to confirm.
c) The download screen will appear. This screen includes a
download matrix, which lists all modules in the Central Part
that support downloading to flash memory, as well as their
download status. Figure D-3 on the next page shows an
example of what the download matrix might look like. The
items with status 'Alive' require downloading.
For details on the download matrix and download status
refer to Section 10 of this manual ("Loading Software").
d) Choose the 'Start' option from the menu bar to start the
download process for Central Part 1.
A percentage bar will be displayed to show the progress of
each software component download. The download process
may take some time, depending on the amount of software
to be downloaded and the communication baud rate used.
During downloading, the time indication at the Diagnostic
and Battery Module (DBM) is frozen or blank.
e) After the downloading process has been completed, a
timeout is initiated (indicated by a progress bar) to allow
Central Part 1 to re-initialize (you will hear a number of
clicks from the FSC system).
Software Manual
Figure D-3 Download screen (FLASH)

(continued)
Step Action Done
C.3 (=)
f) After the download has been completed, the Extended
Diagnostics screen will appear. If no faults occurred during
the download, the Extended Diagnostics screen will display
either of three messages:
− No differences detected in application program
(if no FLDs were modified), or
− Difference found at FLD(s) (if FLDs were modified,
followed by all FLD modifications), or
− Processor module key in IDLE position
(10020/1/1 CPU module only).
If any faults did occur, the screen will indicate what went
wrong. Make sure that you correct any reported errors
before continuing. Do not restart Central Part 1 at this
point!
For details on extended diagnostics in conjunction with OLM
refer to subsection D.10 on page D-76.
Software Manual
(continued)
Step Action Done
C.3 (=)
Important!
Old diagnostics messages in the Extended Diagnostics
screen, if any, are not cleared. You should therefore pay
close attention to the exact timestamp of reported
messages.
g) You are now ready to reload the Personality Image for
Central Part 1 (only for FSC-SM) (see next subsection).
Software Manual
D.7.5 Reloading the Personality Image (PI) for Central Part 1
skip this step and proceed with step C.5 (see subsection D.7.6 on
page D-28).
Step C.4 Reload the Personality Image (PI) for Central Part 1
(only for FSC-SM).
Table D-15 FLASH: Reloading the Personality Image for Central

Part 1
Step Action Done
C.4 (=)
a) Load the Personality Image (PI) and the point database into
the secondary Safety Manager Module (SMM).
b) Wait for the message 'LOADED' to appear. The status will
go to 'BKUP_PF'.
c) You are now ready to start up Central Part 1 (see next
subsection).
Software Manual
D.7.6 Starting Up Central Part 1
Step C.5 Start up Central Part 1.
Table D-16 FLASH: Starting up Central Part 1

Step Action Done
C.5 (=)
a) If the download was successful, you will be prompted to
start up Central Part 1.
If the system contains a 10020/1/1 CPU module, you need
to set the processor key switch to the 'RUN' position and
then cycle the RESET key switch.
If the system contains a 10012/1/2 CPU module, you only
need to cycle the RESET key switch.
As soon as Central Part 1 has successfully started up, the
WD LED on the watchdog module (type 10005/1/1) in
Central Part 1 will go on again.
Central Part 2 will now automatically shut down (the WD
LED on the watchdog module in Central Part 2 will go out).
You will return to the download matrix, which will now report
'OK' for all software components of Central Part 1.
b) Use the 'Extended Diagnostics' option of FSC Navigator to
see if Central Part 1 is OK. No error messages should be
reported.
Note:
The following two messages may be safely ignored here:
– Second fault timer started.
– Internal communication failure.
Any other messages should be investigated before
continuing.
c) You are now ready to switch to Central Part 2 and download
its software (see next subsection).
Software Manual
Step C.6 Shut down Central Part 2.
Table D-17 FLASH: Shutting down Central Part 2

Step Action Done
C.6 (=)
a) After you have successfully downloaded the software for
Central Part 1, you need to download it for Central Part 2.
Important!
If you do not download software for both Central Parts, the
system will not be able to start up.
b) In the download screen, you must switch from Central Part

1 to Central Part 2. To switch to Central Part 2, choose the
'Other central part' option from the menu. The download
matrix will now switch to Central Part 2 and show its
download status.
c) Central Part 2 has already shut down. (It was shut down
when Central Part 1 was restarted.) The WD LED on its
watchdog module (type 10005/1/1) is out.
d) If the FSC system does not contain a 100x8/2/U FSC Safety
with step g).
X
X
g) You are now ready to download the software for Central
Part 2 (see next subsection).
Software Manual
D.7.8 Downloading the Software for Central Part 2
Step C.7 Download the software for Central Part 2.

Step Action Done
C.7 (=)
a) After you switched to Central Part 2, the download matrix is
updated to report the actual download status of the software
components in that Central Part. Figure D-3 on page D-25
shows an example of what the download matrix might look
like. The items with status 'Alive' require downloading.
Note:
If the system contains a 10020/1/1 CPU module, you may
first be prompted to set the key switch to the 'IDLE' position.
b) Choose the 'Start' option from the menu bar to start the
download process for Central Part 2.
A percentage bar will be displayed to show the progress of
each software component download. The download process
may take some time, depending on the amount of software
to be downloaded and the communication baud rate used.
During downloading, the time indication at the Diagnostic
and Battery Module (DBM) is frozen or blank.
c) After the downloading process has been completed, a
d) After the download has been completed, the Extended
Diagnostics screen will appear. If no faults occurred during
the download, the following message will be displayed:
− No faults detected.
point.
e) You are now ready to reload the Personality Image for
Software Manual
skip this step and proceed with step C.9 (see subsection D.7.10
below).
(only for FSC-SM).
Table D-19 FLASH: Reloading the Personality Image for Central

Part 2
Step Action Done
C.8 (=)
b) Wait for the message 'LOADED' to appear. The status of
the secondary Safety Manager will go to 'BACKUP'. The
status of the primary Safety Manager will go to 'OK'.
subsection).
Software Manual
Table D-20 FLASH: Starting up Central Part 2

Step Action Done
C.9 (=)
a) If the download was successful, you will be prompted to
start up Central Part 2.
If the system contains a 10020/1/1 CPU module, you need
to set the processor key switch to the 'RUN' position and
then cycle the RESET key switch.
If the system contains a 10012/1/2 CPU module, you only
need to cycle the RESET key switch.
As soon as Central Part 2 has successfully started up, you
will return to the download matrix, which will now report 'OK'
for all software components of Central Part 2.
b) Choose the 'eXit' option from the menu bar to leave the
software download environment and return to the FSC
c) Use the 'Extended Diagnostics' option of FSC Navigator to
reported.
d) Make sure that the Force Enable key switch is in the same
position as it was before starting the on-line modification
procedure (i.e. if it was already activated, leave it as it is,
and if it was deactivated, deactivate it again).
Important!
If the Force Enable key switch was already activated and
you deactivate it, all existing forces will be lost, which may
result in a system shutdown.
e) You are now ready to make a backup of the modified
application files (see next subsection).
Software Manual
D.7.11 Making a Backup of the Modified Application Files
Step C.10 Making a backup of the modified application files.
Table D-21 FLASH: Making a backup of the modified application

files
Step Action Done
C.10 (=)
directory.
b) You have now successfully completed the on-line
modification.
Important!
2. The master project files are located on the computer where
the software downloads were carried out. Always make sure
that you back up the project files from that computer. Please
note that this may be a different computer than the
designated master computer!
3. If the download was not carried out from the master
computer, make sure that you copy the backed up project
files to that master computer.
Software Manual
D.8 Upgrading the FSC System (RAM Mode)
D.8.1 Overview

FSC system implemented in the FSC system, i.e. the application program needs to
(RAM) loaded into the CPU module's non-volatile RAM memory, and
EPROMs need to be programmed and exchanged. The software is
upgraded in one Central Part at a time. This stage consists of the
following steps:
C.1) Check the system before exchanging the EPROMs.
(only for FSC-SM).
(only for FSC-SM).
Software Manual
Step C.1 Check the system before downloading the CPU application
program and exchanging the EPROMs.
proceeding with the on-line modification. (Please note that the error
messages 'Analog input sensor break alarm' and 'Analog output value
invalid' may be ignored here.)
Important!
Table D-22 RAM: Checking the FSC system

Step Action Done
C.1 (=)
a) Before downloading the CPU application program and
exchanging the EPROMs, use the 'Extended Diagnostics'
option of FSC Navigator to check both Central Parts of the
FSC system. No faults have been found.
subsection).
Software Manual
Table D-23 RAM: Shutting down Central Part 1

Step Action Done
C.2 (=)
a) Make sure that the Force Enable key switch is activated.
Important!
If the Force Enable key switch is already activated, leave it
as it is. If you deactivate and reactivate the key switch, all
existing forces will be lost, which may result in a system
shutdown.
b) Shut down Central Part 1.
The bus immediately above the Central Part may have an
ESD key switch, located to the right of the watchdog
flatcable connector. If this is the case, shut down the Central
Part by setting this switch to the horizontal position.
Otherwise, pull the flatcable from the connector.
c) After Central Part 1 has shut down, set the ESD key switch
to its vertical position again, or reconnect the flatcable of the
watchdog (depending on the way the Central Part was shut
down in step C.2b).
d) If the FSC system does not contain a 10008/2/U FSC Safety
with step g).
X
X
g) Switch the CPU RUN/STOP key switch (type 10002/1/2) of
Central Part 1 to the 'STOP' position (horizontal).
h) You are now ready to exchange the CPU system EPROMs
in Central Part 1 (if required) (see next subsection).
Software Manual
D.8.4 Exchanging the CPU System EPROMs in Central Part 1
ATTENTION If no system software is to be upgraded, skip this step and proceed

with step C.4 (see subsection D.8.5 on page D-39).
Step C.3 Exchange the CPU system EPROMs in Central Part 1

Table D-24 RAM: Exchanging the CPU system EPROMs in Central

Part 1
Step Action Done
C.3 (=)
a) Loosen the screws at the top and bottom of the 10002/1/2
Central Processing Unit (CPU) module in Central Part 1.
b) Carefully remove the module from the Central Part rack by
pulling the grip at the front of the CPU module.
c) Remove the 10002/A/x memory board from the CPU
module.
d) Identify whether the CPU module uses a 10002/A/1 or
10002/A/2 memory board. Please note that 10002/A/2
modules need not be erased.
10002/A/1 10002/A/2
e) Use an EPROM eraser to —
erase the memory board.
f) Use the FSC EPROM programmer and FSC Navigator
software to reprogram the 10002/A/x memory board.
Important!
In addition to the CPU system EPROMs, 10002/A/x memory
boards may also contain extra RAM chips. Make sure that
you remove these before reprogramming a 10002/A/x
memory board. If you do not, the RAM chips will be
irreparably damaged.
g) Reinstall the reprogrammed 10002/A/x memory board onto
the CPU module.
Important!
If the 10002/A/x memory board contained additional RAM
chips, make sure that you put these back into place on the
memory board before reinstalling it on the CPU module.
h) If the RAM EPROM size has changed, make sure that the
jumpers on the CPU module are set correctly.
For details refer to the FSC Hardware Manual.
Software Manual
Part 1 (continued)
Step Action Done
C.3 (=)
i) Make sure that the CPU RUN/STOP key switch is in the
'STOP' position (horizontal), and put the CPU module back
into place.
j) Fasten the screws of the CPU module.
k) You are now ready to exchange the communication
EPROMs in Central Part 1 (see next subsection).
Software Manual
D.8.5 Exchanging the Communication EPROMs in Central Part 1
Step C.4 Exchange the communication EPROMs in Central Part 1.
Table D-25 RAM: Exchanging the communication EPROMs in

Central Part 1
Step Action Done
C.4 (=)
a) Remove the communication cables from the first COM
module (type 10004/x/x or 10024/x/x) in Central Part 1.
b) Loosen the screws of the first communication module.
c) Carefully pull the communication module from Central
Part 1.
d) Make sure you remember the order in which the EPROMs
are placed, and remove the EPROMs from the
communication module.
e) Install the new EPROMs on the communication module.
f) Inspect the EPROMs visually and check if the correct set of
EPROMs has been installed and in the correct sequence.
g) If the EPROM size has changed, check the jumper settings
on the communication module.
For details on the jumper settings refer to the FSC
Hardware Manual.
h) Put the communication module back into place.
i) Fasten the screws of the communication module.
j) Reconnect the communication cables to the communication
module.
k) If more communication modules are installed in Central
Part 1, repeat steps a) to j) for the other communication
modules.
l) You are now ready to exchange the FSC-SMM EPROM in
Central Part 1 (if required) (see next subsection).
Software Manual
D.8.6 Exchanging the FSC-SMM EPROM in Central Part 1
page D-41).
Step C.5 Exchange the FSC-SMM EPROM in Central Part 1

FSC-SM ONLY (only in case of a software release upgrade).
Table D-26 RAM: Exchanging the FSC-SMM EPROM in Central

Part 1
Step Action Done
C.5 (=)
a) Make sure that the TPS software is compatible with the FSC
system software (see Table D-2 on page D-12).
b) Use a torque wrench to disconnect the UCN drop cables
from the FSC-SMM module (type 10008/2/U) of Central
Part 1.
c) Loosen the screws of the FSC-SMM module.
d) Carefully pull the FSC-SMM module from the Central Part
rack.
e) Remove the EPROM from the FSC-SMM module.
f) Install the new EPROM on the FSC-SMM module.
g) Inspect the EPROM visually.
h) Put the FSC-SMM module back into place.
i) Fasten the screws of the FSC-SMM module.
j) Use a torque wrench to reconnect the UCN drop cables to
the FSC-SMM module.
k) You are now ready to download the CPU application
program in Central Part 1 (see next subsection).
Software Manual
D.8.7 Downloading the CPU Application Program in Central Part 1
Step C.6 Download the CPU application program in Central Part 1.
Table D-27 RAM: Downloading the CPU application program in

Central Part 1
Step Action Done
C.6 (=)
a) Switch the CPU RUN/STOP key switch of Central Part 1 to
the 'RUN' position (vertical).
b) Wait for the vertical bus drivers (VBDs) to "click".
c) If the VBDs do not "click", switch the CPU RUN/STOP key
switch to the 'STOP' position (horizontal). Make sure that all
modules have been placed in the correct position of the
Central Part rack, that all jumper settings are correct, and
that all EPROMs are placed correctly and in the proper
order. Then repeat steps a) and b).
The exact download procedure depends on the type of link that is

used to download the application to RAM:
• a direct Development System (DS) link with the FSC user station,
or
• an FSC-FSC link for multidrop (MD) slaves.
WARNING WARNING — FSC Navigator software R530 does not support

downloading to multidrop (MD) slaves via an FSC-FSC link with a
baud rate of 1 Mbaud or 2 Mbaud.

Central Part 1 (continued)
Step Direct DS link with FSC-FSC link for Done
C.6 FSC user station multidrop slaves (=)
d) — Disconnect the cable from
the multidrop FSC-FSC link
port on the communication
module in Central Part 1,
and connect the PC-FSC
cable.
Software Manual
e) Start the FSC Navigator user software and choose the
Download option:
f) The following message will be displayed:
"Make sure the communication EPROMs have been
programmed. Continue? (Y/N)".
This warning is displayed to remind you that you should not
forget to program new communication EPROMs before
continuing with the download. If you do not, you may load
new CPU software, while the COM software is not updated.
If you programmed the EPROMs and successfully installed
them in the system, press <Y> to continue.
g) You will be asked to select the Central Part whose
application program you wish to download. Make sure that
you start with Central Part 1. You can press <Space> to
toggle between the Central Parts. Press <Enter> to confirm.
The download screen will appear.
h) Choose the 'Start' option from the menu bar to start the
download process. A percentage bar will be displayed to
show the progress of the download (see Figure D-4 on the
next page). The download process may take some time,
depending on the amount of software to be downloaded and
the communication baud rate used. During downloading, the
time indication at the Diagnostic and Battery Module (DBM)
is frozen or blank.
i) After the downloading process has been completed, a
Software Manual
Figure D-4 Downloading CPU application to RAM

j) — Wait for the following
message to appear on
screen: "Waiting for OLM
check and FSC-FSC COM
check...". Then switch the
CPU RUN/STOP key switch
in Central Part 1 to the
'STOP' position (horizontal).
Disconnect the PC-FSC
cable and reconnect the
multidrop FSC-FSC cable.
Switch the CPU RUN/STOP
key switch on Central Part 1
to the 'RUN' position
(vertical).
Software Manual
k) After some time, the diagnostic and battery module (DBM,
10006/x/x) starts updating the time again. This means that
the download process and all subsequent checks have
been completed successfully.
l) The Extended Diagnostics Exit the download
screen will be displayed environment and choose the
automatically for Central 'Extended Diagnostics'
Part 1. option of FSC Navigator.
This will open the Extended
Diagnostics screen. Make
sure the screen shows the
diagnostics for Central
Part 1. If it does not, use
Alt+<C> to toggle between
Central Parts.
m) If no faults occurred during the download, the Extended
Diagnostics screen will display either of two messages:
followed by all FLD modifications).
point.
Important!
Old diagnostics messages, if any, are not cleared. You
should therefore pay close attention to the exact timestamp
of reported messages.
n) The following message will —
be displayed in the status
bar: "Load successful. Cycle
RESET key switch to start."
Do not start up Central Part
1 at this point.
o) You are now ready to reload the Personality Image for
Software Manual
page D-46).
(only for FSC-SM).
Table D-28 RAM: Reloading the Personality Image for Central

Part 1
Step Action Done
C.7 (=)
go to 'BKUP_PF'.
subsection).
Software Manual
Table D-29 RAM: Starting up Central Part 1

Step Action Done
C.8 (=)
a) Restart the Central Part by cycling the RESET key switch.
b) As soon as Central Part 1 has successfully started up, the
reported.
Note:
continuing.
d) You are now ready to upgrade Central Part 2 of the
FSC system (see next subsection).
Software Manual
Table D-30 RAM: Shutting down Central Part 2

Step Action Done
C.9 (=)
a) Due to on-line modification, Central Part 2 will already be
shut down. The WD LED on its watchdog module (type
10005/1/1) is out.
b) If the FSC system does not contain a 10008/2/U FSC Safety
Manager Module (SMM), skip steps c) and d) and proceed
with step e).
c) Shut down the secondary Safety Manager (even node
X
d) Wait for the secondary Safety Manager to become 'ALIVE'
X
e) Switch the CPU RUN/STOP key switch (type 10002/1/2)
from Central Part 2 to the 'STOP' position (horizontal).
f) You are now ready to exchange the CPU system EPROMs
Software Manual
D.8.11 Exchanging the CPU System EPROMs in Central Part 2
ATTENTION If no system software is to be upgraded, skip this step and proceed

with step C.11 (see subsection D.8.12 on page D-50).
Step C.10 Exchange the CPU system EPROMs in Central Part 2


Part 2
Step Action Done
C.10 (=)
a) Loosen the screws at the top and bottom of the 10002/1/2
c) Remove the 10002/A/x memory board from the CPU
module.
d) Identify whether the CPU module uses a 10002/A/1 or
10002/A/1 10002/A/2
e) Use an EPROM eraser to —
f) Use the FSC EPROM programmer and FSC Navigator
software to reprogram the memory board.
Important!
g) Reinstall the reprogrammed 10002/A/x memory board onto
the CPU module.
Important!
h) If the RAM EPROM size has changed, make sure that the
Software Manual
Part 2 (continued)
Step Action Done
C.10 (=)
i) Make sure that the CPU RUN/STOP key switch is in the
into place.
j) Fasten the screws of the CPU module.
k) You are now ready to exchange the communication
Software Manual
Table D-32 RAM: Exchanging the communication EPROMs in

Central Part 2
Step Action Done
C.11 (=)
Part 2.
Hardware Manual.
module.
modules.
Software Manual
page D-52).

Table D-33 RAM: Exchanging the FSC-SMM EPROM in Central

Part 2
Step Action Done
C.12 (=)
a) Use a torque wrench to disconnect the UCN drop cables
Part 2.
b) Loosen the screws of the FSC-SMM module.
c) Carefully pull the FSC-SMM module from the Central Part
rack.
d) Remove the EPROM from the FSC-SMM module.
e) Install the new EPROM on the FSC-SMM module.
f) Inspect the EPROM visually.
g) Put the FSC-SMM module back into place.
h) Fasten the screws of the FSC-SMM module.
i) Use a torque wrench to reconnect the UCN drop cables to
the FSC-SMM module.
j) You are now ready to download the CPU application
program in Central Part 2 (see next subsection).
Software Manual
D.8.14 Downloading the CPU Application Program in Central Part 2
Step C.13 Download the CPU application program in Central Part 2.

Central Part 2
Step Action Done
C.13 (=)
The exact download procedure depends on the type of link that is

used to download the application to RAM:
• a direct Development System (DS) link with the FSC user station,
or
• an FSC-FSC link for multidrop (MD) slaves.
WARNING WARNING — FSC Navigator software R530 does not support

downloading to multidrop (MD) slaves via an FSC-FSC link with a
baud rate of 1 Mbaud or 2 Mbaud.

d) — Disconnect the cable from
the multidrop FSC-FSC link
port on the communication
module in Central Part 2,
and connect the PC-FSC
cable.
Software Manual
e) Start the FSC Navigator user software and choose the
Download option:
f) The following message will be displayed:
"Make sure the communication EPROMs have been
programmed. Continue? (Y/N)".
This warning is displayed to remind you that you should not
forget to program new communication EPROMs before
continuing with the download. If you do not, you may load
new CPU software, while the COM software is not updated.
If you programmed the EPROMs and successfully installed
them in the system, press <Y> to continue.
g) You will be asked to select the Central Part whose
application program you wish to download. Use <Space> to
toggle to Central Part 2, and press <Enter> to confirm. The
download screen will appear.
h) Choose the 'Start' option from the menu bar to start the
download process. A percentage bar will be displayed to
show the progress of the download (see Figure D-4 on page
D-43). The download process may take some time,
depending on the amount of software to be downloaded and
the communication baud rate used. During downloading, the
time indication at the Diagnostic and Battery Module (DBM)
is frozen or blank.
i) After the downloading process has been completed, a
Software Manual
j) — Wait for the following
message to appear on
screen: "Waiting for OLM
check and FSC-FSC COM
check...". Then switch the
CPU RUN/STOP key switch
in Central Part 2 to the
'STOP' position (horizontal).
Disconnect the PC-FSC
cable and reconnect the
multidrop FSC-FSC cable.
Switch the CPU RUN/STOP
key switch on Central Part 2
to the 'RUN' position
(vertical).
k) After some time, the diagnostic and battery module (DBM,
10006/x/x) starts updating the time again. This means that
the download process and all subsequent checks have
been completed successfully.
l) The Extended Diagnostics Exit the download
screen will be displayed environment and choose the
automatically for Central 'Extended Diagnostics'
Part 2. option of FSC Navigator.
This will open the Extended
Diagnostics screen. Make
sure the screen shows the
diagnostics for Central
Part 2. If it does not, use
Alt+<C> to toggle between
Central Parts.
m) If no faults occurred during the download, the Extended
Diagnostics screen will display the following message:
No faults detected.
point.
Important!
Software Manual
n) The following message will —
be displayed in the status
bar: "Load successful. Cycle
RESET key switch to start."
Do not start up Central Part
2 at this point.
o) You are now ready to reload the Personality Image for
Software Manual
page D-57).
(only for FSC-SM).
Table D-35 RAM: Reloading the Personality Image for Central

Part 2
Step Action Done
C.14 (=)
subsection).
Software Manual
Table D-36 RAM: Starting up Central Part 2

Step Action Done
C.15 (=)
b) If a reset is given, Central Part 2 will start "running" together
with Central Part 1. (The WD LEDs for both Central Parts
will now be on.)
see if the FSC system is OK. No errors should be reported.
d) Make sure that the Force Enable key switch is in the same
position as it was before starting the on-line modification
procedure (i.e. if it was already activated, leave it as it is,
and if it was deactivated, deactivate it again).
Important!
If the Force Enable key switch was already activated and
you deactivate it, all existing forces will be lost, which may
result in a system shutdown.
e) You have now successfully completed the on-line
modification.
Software Manual
D.9 Upgrading the FSC System (EPROM Mode)
D.9.1 Overview

FSC system implemented in the FSC system, i.e. EPROMs are programmed and
(EPROM) exchanged. The software is upgraded in one Central Part at a time.
This stage consists of the following steps:
C.1) Check the system before exchanging the EPROMs.
Part 1.
(only for FSC-SM).
Part 2.
(only for FSC-SM).
Software Manual
Step C.1 Check the system before exchanging the EPROMs.

proceeding with the on-line modification. (Please note that the error
messages 'Analog input sensor break alarm' and 'Analog output value
invalid' may be ignored here.)
Important!
Table D-37 EPROM: Checking the FSC system

Step Action Done
C.1 (=)
a) Before proceeding with the on-line modification, use the
'Extended Diagnostics' option of FSC Navigator to check
both Central Parts of the FSC system. You may only
continue if no faults are found.
subsection).
Software Manual
Table D-38 EPROM: Shutting down Central Part 1

Step Action Done
C.2 (=)
a) Shut down Central Part 1.
The bus immediately above the Central Part may have an
ESD key switch, located to the right of the watchdog
flatcable connector. If this is the case, shut down the Central
Part by setting this switch to the horizontal position.
Otherwise, pull the flatcable from the connector.
b) After Central Part 1 has shut down, set the ESD key switch
to its vertical position again, or reconnect the flatcable of the
watchdog (depending on the way the Central Part was shut
down in step C.2a).
c) If the FSC system does not contain a 10008/2/U FSC Safety
Manager Module (SMM), skip steps d) and e) and proceed
with step f).
d) Shut down the secondary Safety Manager (even node
X
e) Wait for the secondary Safety Manager to become 'ALIVE'
X
f) Switch the CPU RUN/STOP key switch (type 10002/1/2) of
Central Part 1 to the 'STOP' position (horizontal).
g) You are now ready to exchange the CPU system EPROMs
Software Manual
D.9.4 Exchanging the CPU EPROMs in Central Part 1
ATTENTION If no system software is to be upgraded, you may skip steps C.3d to

C.3h below.
Step C.3 Exchange the CPU EPROMs in Central Part 1.
Table D-39 EPROM: Exchanging the CPU system EPROMs in

Central Part 1
Step Action Done
C.3 (=)
a) Loosen the screws at the top and bottom of the 10002/1/x
c) Remove the application EPROMs from the 10002/A/x
memory board
d) Remove the 10002/A/x memory board from the CPU
module.
e) Identify whether the CPU module uses a 10002/A/1 or
10002/A/1 10002/A/2
f) Use an EPROM eraser to —
g) Use the FSC EPROM programmer and FSC Navigator
Important!
h) Reinstall the reprogrammed 10002/A/x memory board onto
the CPU module.
Important!
Software Manual
Step Action Done
C.3 (=)
i) Install the new application EPROMs on the 10002/A/x
memory board on the CPU module.
j) Inspect the EPROMs visually and check if the correct set of
k) If the EPROM size has changed, make sure that the
l) Make sure that the CPU RUN/STOP key switch is in the
into place.
m) Fasten the screws of the CPU module.
n) You are now ready to exchange the communication
Software Manual
Table D-40 EPROM: Exchanging the communication EPROMs in

Central Part 1
Step Action Done
C.4 (=)
Part 1.
Hardware Manual.
module.
modules.
Software Manual
page D-65).

Table D-41 EPROM: Exchanging the FSC-SMM EPROM in Central

Part 1
Step Action Done
C.5 (=)
Part 1.
rack.
the FSC-SMM module.
k) You are now ready to prepare Central Part 1 for start-up
Software Manual
D.9.7 Preparing Central Part 1 for Start-Up
Step C.6 Prepare Central Part 1 for start-up.
Table D-42 EPROM: Preparing Central Part 1 for start-up

Step Action Done
C.6 (=)
d) Go to the FSC system and wait until the diagnostic and
battery module (DBM, 10006/x/x) starts updating the time
again. As long as the DBM time is frozen or blank, the
system is performing the internal check between Central
Parts and systems.
e) When the DBM starts updating the time again, use the
'Extended Diagnostics' option of FSC Navigator to see if any
errors have occurred via the FSC user station that is
connected to the FSC (master) system. If no faults
occurred, the Extended Diagnostics screen will display
either of two messages:
followed by all FLD modifications).
point! For details on extended diagnostics in conjunction
with OLM refer to subsection D.10 on page D-76.
Important!
f) You are now ready to reload the Personality Image for
Software Manual
page D-67).
(only for FSC-SM).
Table D-43 EPROM: Reloading the Personality Image for Central

Part 1
Step Action Done
C.7 (=)
go to 'BKUP_PF'.
subsection).
Software Manual
Table D-44 EPROM: Starting up Central Part 1

Step Action Done
C.8 (=)
a) Restart Central Part 1 by cycling the RESET key switch.
b) As soon as Central Part 1 has successfully started up, the
reported.
Note:
continuing.
d) You are now ready to upgrade Central Part 2 of the
FSC system (see next subsection).
Software Manual
Table D-45 EPROM: Shutting down Central Part 2

Step Action Done
C.9 (=)
a) Due to the on-line modification, Central Part 2 will already
be shut down. The WD LED on its watchdog module (type
10005/1/1) is out.
b) If the FSC system does not contain a 10008/2/U FSC Safety
Manager Module (SMM), skip steps c) and d) and proceed
with step e).
c) Shut down the secondary Safety Manager (even node
X
d) Wait for the secondary Safety Manager to become 'ALIVE'
X
e) Switch the CPU RUN/STOP key switch (type 10002/1/2)
from Central Part 2 to the 'STOP' position (horizontal).
f) You are now ready to exchange the CPU system EPROMs
Software Manual
D.9.11 Exchanging the CPU EPROMs in Central Part 2
ATTENTION If no system software is to be upgraded, you may skip steps C.10d to

C.10h below.
Step C.10 Exchange the CPU EPROMs in Central Part 2.

Central Part 2
Step Action Done
C.10 (=)
a) Loosen the screws at the top and bottom of the 10002/1/x
c) Remove the application EPROMs from the 10002/A/x
memory board
d) Remove the 10002/A/x memory board from the CPU
module.
e) Identify whether the CPU module uses a 10002/A/1 or
10002/A/1 10002/A/2
f) Use an EPROM eraser to —
g) Use the FSC EPROM programmer and FSC Navigator
Important!
h) Reinstall the reprogrammed 10002/A/x memory board onto
the CPU module.
Important!
Software Manual
Step Action Done
C.10 (=)
i) Install the new application EPROMs on the 10002/A/x
memory board on the CPU module.
j) Inspect the EPROMs visually and check if the correct set of
k) If the EPROM size has changed, make sure that the
l) Make sure that the CPU RUN/STOP key switch is in the
into place.
m) Fasten the screws of the CPU module.
n) You are now ready to exchange the communication
Software Manual
Table D-47 EPROM: Exchanging the communication EPROMs in

Central Part 2
Step Action Done
C.11 (=)
Part 2.
Hardware Manual.
module.
modules.
Software Manual
page D-73).

Table D-48 EPROM: Exchanging the FSC-SMM EPROM in Central

Part 2
Step Action Done
C.12 (=)
Part 2.
rack.
the FSC-SMM module.
k) You are now ready to prepare Central Part 2 for start-up
Software Manual
D.9.14 Preparing Central Part 2 for Start-Up
Step C.13 Prepare Central Part 2 for start-up.
Table D-49 EPROM: Preparing Central Part 2 for start-up

Step Action Done
C.13 (=)
d) Go to the FSC system and wait until the diagnostic and
battery module (DBM, 10006/x/x) starts updating the time
again. As long as the DBM time is frozen or blank, the
system is performing the internal check between Central
Parts and systems.
e) When the DBM starts updating the time again, use the
'Extended Diagnostics' option of FSC Navigator to see if any
errors have occurred via the FSC user station that is
connected to the FSC (master) system. If no faults
occurred, the Extended Diagnostics screen will display the
following message:
− No faults detected.
point! For details on extended diagnostics in conjunction
with OLM refer to subsection D.10 on page D-76.
Important!
f) You are now ready to reload the Personality Image for
Software Manual
page D-75).
(only for FSC-SM).
Table D-50 EPROM: Reloading the Personality Image for Central

Part 2
Step Action Done
C.14 (=)
subsection).
Software Manual
Table D-51 EPROM: Starting up Central Part 2

Step Action Done
C.15 (=)
b) If a reset is given, Central Part 2 will start "running" together
with Central Part 1. (The WD LEDs for both Central Parts
will now be on.)
see if the FSC system is OK.
d) You have now successfully completed the on-line
modification.
Software Manual
D.10 Extended Diagnostics During OLM
D.10.1 Overview
Extended Extended diagnostics play a crucial role during the on-line

diagnostics modification procedure. They basically serve three purposes:
1. They allow you to verify that the FSC system is OK before
starting the on-line modification procedure.
2. They report all modifications that were made to the FLDs of the
application.
3. They report any errors that occurred during the on-line
modification procedure (e.g. communication errors).
Important!
Make sure that you always check the extended diagnostics
before putting the FSC system back on line. Any reported faults
must be resolved before proceeding.
If you perform an on-line modification in FLASH or RAM
mode, the extended diagnostics screen will be displayed
automatically. In EPROM mode, you need to call up this screen
manually (see Figure D-5 below).
Figure D-5 Extended Diagnostics option
Software Manual
D.10.2 Compatibility Check
Compatibility After the upgrade of the software in the first Central Part, the FSC
check system carries out a compatibility check to verify if a safe changeover
can be made from the old software to the new software. This check
may last several minutes, depending on the application. While the
check is being executed, the time at the display of the diagnostic and
battery module (DBM, 10006/x/x) is not updated.
As soon as the time at the DBM display is updated again, the check is
finished. You can then use the 'Extended Diagnostics' option of FSC
Navigator to read the results (see Figure D-5).
The extended diagnostics screen will show the numbers of the

functional logic diagrams that have been changed (see Figure D-6). If
no sheet differences exist, this is also reported. This allows final
verification of the modifications.
Figure D-6 Sheet differences during on-line modification
Software Manual
Apart from the report regarding sheet differences, no messages should
be present. Any other message indicates an incompatibility of the
current application with the previous version. As a result, either
on-line modification is not possible, or the new software will run with
limited functionality. The possible messages and their consequences
are listed in subsection D.11 on page D-79.
If the first Central Part reports no errors, it may be started. At the same
time, the other Central Part will shut down via the system software.
The software can then be exchanged in the other Central Part.
Note:
The error message "Diagnostic data invalid" will be displayed if
the CPU has been removed and no sheet differences exist.
D.10.3 FSC Networks
FSC networks If a system is part of an FSC communication network, it will perform

a compatibility check for all connected systems.
If no errors occurred, the message "No faults detected" is displayed,
and start-up is possible. If any inconsistencies are detected or if the
check for a specific system cannot be completed for any other reason,
an error message is generated in the extended diagnostics. In case of
such an error, no data will be exchanged with the system after start-up.
The communication can only be re-established after successful
completion of the compatibility check by any of the systems.
Note:
The FSC system performs the compatibility check for connected
systems each time it is started, regardless whether modifications
were made in the system or not. The extended diagnostics
should therefore always be examined prior to starting the
system, to verify if all communication links are intact.
Software Manual
D.11 Error Diagnostics
Error diagnostics Apart from the reported sheet differences, a number of other
messages may appear in the extended diagnostics screen during
on-line modification. These can be either of two types:
• relating to internal on-line modification check, or
• relating to the FSC network configuration check.
The following subsections list the possible messages.

Extended diagnostic messages can be viewed using FSC Navigator's
on-line environment features (see Section 12 of this manual).
D.11.1 Diagnostics Relating to Internal On-Line Modification Check
Internal check The following diagnostic messages relate to internal on-line

modification check:
Communication failure during OLM. (see note below!)

Description: This message indicates that the compatibility check
was aborted because communication with the running Central Part
failed. Additional information is included to indicate during which
part of the check the error was detected.
Corrective action: Check the communication cable between the
Central Parts. Put the CPU key switch of the Central Part in
shutdown to the 'STOP' position, and back to the 'RUN' position.
Wait until the DBM starts running and check the diagnostics again.
Important!
If the Communication failure during OLM message is
reported, it is not possible to start up the Central Part that
contains the new software. Trying to start up anyhow may
result in a total system shutdown.
Software Manual
Incompatible variable allocation. (see note below!)
Description: This message indicates that the variable allocation in
the new software clashes with the variable allocation in the old
software. If this message appears, on-line modification is not
possible.
The type and tag number of the improperly allocated variable are
included in the diagnostic report. Please note that if more than one
variable has been allocated improperly, only one of them is
reported.
Corrective action: Make sure that the on-line modification option
is set to 'Yes' (see subsection D.5.5).
Corrective action: Reinstall the backup that was created earlier,
activate the on-line modification option and implement the changes
again.
Corrective action: Perform an on-line rebuild to obtain an
application database which is compatible with the application as
present in the system (see Section 4 of this manual).
Corrective action: Reallocate any unallocated variables.
Proceed in accordance with the normal application development
procedures.
Important!
If the Incompatible variable allocation message is reported, it
is not possible to start up the Central Part that contains the new
software. Trying to start up anyhow may result in a total system
shutdown.
No start-up due to different application.

Description: This message appears if you try to start up both
Central Parts simultaneously, with incompatible software loaded in
the Central Parts. Refer to Section 12 of this manual ("On-Line
Environment") for details on FSC system diagnostics.
Corrective action: Load consistent software in both Central Parts
before system start-up.
Shutdown due to on-line modification.

Description: This message does not indicate an error. It will
always appear during the upgrade stage. The message is reported
by the Central Part that contains the old software if it has shut
down just after the changeover to the Central Part that contains the
new software.
Software Manual
D.11.2 Diagnostics Relating to FSC Network Configuration Check
Network check The following diagnostic messages relate to the FSC network
configuration check:
Communication failure during configuration check for system

<no.>.
Description: The message indicates that the configuration check
was aborted because communication with the target system failed.
The number of the target system is included in the diagnostic
report.
Corrective action: Check the communication connections between
the systems.
Incompatible FSC-FSC configuration for system <no.>.

was aborted due to different sizes of the marker and/or register
areas for data exchange with the target system. The number of the
target system is included in the diagnostic report.
Corrective action: Adjust the size of the marker and/or register
areas.
Incompatible FSC-FSC variable allocation.

was aborted because the variable allocation in the system collides
with the variable allocation in the target system. The type and tag
number of the improperly allocated variable are included in the
diagnostic report.
Corrective action: Make sure that the on-line modification option
is set to 'Yes' (see subsection D.5.5).
Corrective action: Perform an on-line rebuild to obtain an
application database which is compatible with the application as
present in the system.
Corrective action: Reallocate any unallocated variables.
Note:
If the system is started while one of these faults is present, no
communication with the target system will be accomplished.
Software Manual
D.12 On-Line Rebuild
On-line rebuild When an application is created, variables are allocated to locations in

system memory (see Figure D-7).
If the application is then changed, variable allocations will change as
well. This is partly because of user interaction (e.g. removal of a
variable allocated to a hardware channel), and partly because of
actions by the FSC Navigator software, e.g. change in the number of
internal compiler variables (feedback markers) required to realize a
functional logic diagram.
If the application has been configured for on-line modification, the

allocation of any variable that is deleted from the application is
blocked for further use (Figure D-7) in order to guarantee application
compatibility with the previous version. As a consequence of this
mechanism, the required amount of system memory will increase,
while the allocated memory becomes more and more fragmented.
Initial application memory allocation memory allocation

memory allocation after modifications after on-line rebuild
Free Allocated Blocked
Figure D-7 Allocation in variables to locations in system memory
The only way to release blocked allocations is via the 'On-Line

Rebuild' option of FSC Navigator (see Figure D-8). This option
should only be used if the amount of memory is not enough to
continue design or configuration. It must be selected after the
application has been compiled and upgraded into the FSC system.
During the on-line rebuild, the variable allocation is read from the
FSC system and the unused memory locations are unlocked.
Software Manual
For further information on the on-line rebuild function refer to
Section 4 of this manual ("System Configuration").
Figure D-8 On-Line Rebuild option
If you choose the on-line rebuild option, you will be asked to confirm
the operation:
Are you sure? (Y/N)
If you answer 'Yes', the on-line rebuild process will start.
Software Manual
D.13 Modifying Tag Numbers On-Line
D.13.1 Input Tag Numbers
Input tag In order to change input tag numbers in a system on-line, the
numbers following steps must be carried out:
1. Delete the tag numbers that are to be modified. Modify the FLD
relating to these tags in such a way that the FLDs remain in a
steady state. Translate, make new EPROMs, and transfer the
application software to the FSC system in accordance with the
OLM procedure described in Sections D.5 to D.9.
2. Carry out the on-line rebuild.
3. Add the modified tag numbers to the FSC database and add the
tag numbers back into the corresponding FLD. Translate and
download the application software in accordance with the OLM
procedure described in Sections D.5 to D.9.
Deleting tag
numbers To delete input tag numbers, do the following:
a) Start the 'System Configuration' option of FSC Navigator.
b) Choose Signal specs from the main menu.
c) Use the Search option to list the related tag number(s).
d) Press <Ctrl>+<U> to delete the tag numbers.
The message "Variable allocated. Deallocate because of on-line
modification? (Y/N)" will be displayed. Press <Y> to confirm.
e) To modify the FLD relating to the deleted tag number(s), start the
'Design FLDs' option of FSC Navigator. Delete the I/O symbols
of the tag number(s) and replace them with, for example, a
constant boolean signal or force-enable input in order to maintain
the correctness of the FLD. If a constant boolean signal is used,
the process cannot be shut down anymore via that input and closer
process monitoring is required to manually trip the application in
case of dangerous situations.
f) Translate the application and upgrade the system in accordance
with the OLM procedure described in Sections D.5 to D.9.
Software Manual
On-line rebuild To perform an on-line rebuild, do the following:
a) Connect the FSC user station to the FSC system via the
Development System link port or FSC-FSC link port (FSC
multidrop slave systems).
b) From the On-Line menu of FSC Navigator, choose the 'On-Line
Rebuild' option.
c) You will be asked to confirm the on-line rebuild. Press <Y> to
confirm.
d) The following message will appear:
Rebuilding screen file for status display...
Shortly after that, the following message will appear:
Toggle to select the Central Part to be rebuilt: 1
Use <Space> to toggle the Central Part number that the PC is
connected to, and press <Enter> to continue.
e) The results of the rebuild are recorded in the on-line rebuild log
file, which can be viewed using the 'View Log' option of FSC
Navigator.
f) Back up the application, e.g. on floppy disk, CD-R, or ZIP disk.
Adding modified To add the modified tag numbers to the FSC database, do the
tag numbers following:
c) Choose Add to enter the related modified tag number(s).
d) Choose Hardware specs from the main menu of 'System
Configuration'.
Reallocate the tag number(s) to their previous allocation or
relative address (COM I/O).
Also set the 'Safety related', 'SER enable', etc., attributes to their
previous settings.
e) Use the 'Design FLDs' option of FSC Navigator to reassign the tag
number to the respective FLD(s).
Software Manual
D.13.2 Output Tag Numbers
Output In order to change output tag numbers in a system on-line, the

tag numbers following steps must be carried out (depending on the operational
status of the outputs):
1. If the output may be de-energized, the procedure is identical to the
procedure for changing input tag numbers (see subsection D.13.1).
2. If continuous control of the output must be maintained, a
temporary output which is allocated to a spare channel is used to
control the process while the output tag number is being changed.
Output tag numbers Use the same procedure as for input tag numbers (see subsection
that may be D.13.1). However, instead of a constant symbol, use an off-sheet
de-energized reference to maintain the integrity of the functional logic diagrams.
If you use this procedure, the output in question will be de-energized
as soon as Central Part 1 is started with the intermediate application
software. Output control is regained as soon as the final application
software (which contains the new output tag number) has been
upgraded in the system.
Output tag numbers

with continuous
output control If continuous output control is required, use the following procedure:
Deleting tag
numbers To delete output tag numbers, do the following:
c) Choose Add to add a temporary output tag number for each
output tag number being changed.
Configuration'.
Allocate the temporary tag number(s) to spare output channel(s).
e) Use the 'Design FLDs' option of FSC Navigator to modify the
FLD relating to the added temporary tag number(s). Add a new
output symbol for the temporary tag number in parallel with its
corresponding output which is being changed.
Software Manual
f) Wire the hardware channel(s) of the output(s) being changed to
the corresponding temporary output channel(s) in the FSC cabinet.
g) Translate the application and upgrade the system in accordance
h) Start the 'System Configuration' option of FSC Navigator.
i) Choose Signal specs from the main menu.
j) Use the Search option to list the related tag number(s).
k) Press <Ctrl>+<U> to delete the tag numbers of the outputs being
modified. The message "Variable allocated. De-allocate because
of on-line modification? (Y/N)" will be displayed. Press <Y> to
confirm.
Note:
It is important that the tag numbers that are being modified are
deleted from the FSC database. If the tag number is only deleted
from the functional logic diagrams while its hardware allocation
is maintained, the corresponding output channel status is
preserved during the on-line modification and cannot be
controlled after the on-line modification.
l) To modify the FLD relating to the deleted tag number(s), start the
'Design FLDs' option of FSC Navigator. Delete the output symbol
for the tag number(s) being modified.
m) Translate the application and upgrade the system in accordance
On-line rebuild Carry out an on-line rebuild as described in section D.12.
Adding modified To add the modified tag numbers to the FSC database, do the
tag numbers following:
c) Choose Add to add the new tag number(s).
Configuration'.
e) Use the 'Design FLDs' option of FSC Navigator to modify the
FLD relating to the added tag number(s). Add a new output
symbol for the tag number in parallel with its corresponding
temporary output.
Software Manual
with the OLM procedure as described in section D.13.
g) Start the 'System Configuration' option of FSC Navigator.
h) Choose Signal specs from the main menu.
i) Use the Search option to list the temporary tag number(s).
j) Press <Ctrl>+<U> to delete the tag numbers of the temporary
outputs. The message "Variable allocated. Deallocate because of
on-line modification? (Y/N)" will be displayed. Press <Y> to
confirm.
k) Use the 'Design FLDs' option of FSC Navigator to modify the
FLD relating to the deleted tag number(s). Delete the output
symbol for the temporary tag number(s).
l) Remove the wiring to the temporary outputs from the FSC
cabinet.
m) Translate the application and upgrade the system in accordance
with the OLM procedure as described in Sections D.5 to D.9.
On-line rebuild Carry out an on-line rebuild as described in subsection D.12.
Software Manual
Fail Safe Control
Appendix E:
PID Controllers
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix E: PID Controllers
E.1 Introduction .................................................................................................... E-1
E.2 Theoretical Approach..................................................................................... E-3
E.3 Configuration and Implementation of PID Controllers

in the FSC System.......................................................................................... E-6
E.4 Practical Application of PIDs......................................................................... E-8
Software Manual
Appendix E: PID Controllers i
FIGURES
Figure E-1 Feedback in control loop using PID algorithms ..........................................................E-1

Figure E-2 Standard PID algorithm in FSC system software........................................................E-1
Figure E-3 FSC PID control function.............................................................................................E-3
Figure E-4 Standard PID algorithm in FSC system software........................................................E-7
Figure E-5 Implementation example of a cascade PID ................................................................E-8
Figure E-6 Temperature control using PID ...................................................................................E-9
Software Manual
ii Appendix E: PID Controllers
Appendix E – PID Controllers
E.1 Introduction
PID algorithm The most common way to introduce feedback in a control loop is via
PID algorithms. The process input is controlled in such a way that the
process output will approximate a predefined setpoint.
Setpoint Output
PID Process
Measurement
Figure E-1 Feedback in control loop using PID algorithms
The characteristics of the PID controller – such as gain, damping,

overshoot, etc. – are adjusted by several parameters, with the
proportional, integrational and differential (PID) being the most
important ones.
The FSC system software has a built-in software PID algorithm,

which can easily be used via a symbol in the functional logic diagrams
(see Figure E-2).
A Measurement
I
D PID
Setpoint 5 S
1 Output D
CS O
A
M
OM
PID name
Figure E-2 Standard PID algorithm in FSC system software
Software Manual
Appendix E: PID Controllers E-1
PID control The PID control parameters can be altered on-line using the 'Monitor
parameters System' option of FSC Navigator (Process status \ Var status \
Edit PID).
The controller inputs and outputs are shown in graphic bars in the PID
menu of the 'Monitor System' option of FSC Navigator.
Several operating modes are supported, including Auto, Manual and
Cascade. For details on PID modes refer to subsection E.3.
Software Manual
E-2 Appendix E: PID Controllers
E.2 Theoretical Approach
PID controllers To control several analog inputs and outputs, the FSC system can use
a software controller. The most commonly used controller is the PID
(Proportional, Integrational and Differential) controller. The PID will
control a process variable of the process controlled by the FSC
system. This process (output) value is compared to a predefined value
(setpoint). The PID will control the process variable (output) in such
a way that the process state (input) value will approximate the
setpoint. Figure E-3 shows the model used for the FSC PID function.
Parameters
Setpoint high clamp
Setpoint low clamp
Output high clamp

Proportional band
Output low clamp

Differentiate time
Integration time
Deviation limit
Sample time
Setpoint SP’- e'(t) e(t) u(t) u'(t) y(t)

Setpoint Error PID Output Process
clamp + clamp clamp
y(t)
y(t)
FSC PID control function
Figure E-3 FSC PID control function
In general, the FSC PID control function (the function contained in the
dashed lines of Figure E-3) can be seen as a block with the process
output y(t) and the setpoint as input. The output is the process input
y'(t). By changing the parameters, the function within the block can be
controlled.
Software Manual
Equation for PIDs The ideal equation for a PID controller is:
é de(t) ù
ë ò
u(t) = K * êe(t) + 1 / Ti e(t)dt + Td
dt úû
or
æ 1 ö
u(t) = K * ç1 + + Td * S÷ e(t)
è Ti * S ø
where:
u(t) = PID output
u'(t) = process input (clamped PID output)
y(t) = process output
e'(t) = error function = y(t) – SP'
e(t) = PID input (clamped error function)
SP = setpoint
SP' = clamped setpoint
K = gain factor
Ti = integration time (reset time)
Td = differentiate time (rate time) (or derivative time)
PB = proportional band (100/K)
S = derivative operator.
y(t) is sampled by the FSC system with a sample time T0.
The differential quotient can be converted to a first-order difference,

and the integral to a sum (using trapezium approximation).
The continue equation can be made discrete by:
é t
e(i − 1) + e(i) Td ù
å
T0
u(t) = K ê e(t) + + (e(t) − e(t − 1))ú
êë Ti i =1
2 T0 úû
The following recursive relation can be derived from the above

formula:
u(t) = u(t-1) + q0 ∗ e(t) + q1 ∗ e(t-1) + q2 ∗ e(t-2)
Software Manual
PID constants The following constants are used to implement a number of clamp
functions (see below):
q0 = K ∗ (1 + 0.5 ∗ T0 / Ti + Td / T0)
q1 = –K ∗ (1 + 2 ∗ Td / T0 – 0.5 ∗ T0 / Ti)
q2 = K ∗ (Td / T0)
Clamp functions Three clamp functions have been implemented in the FSC software:
• Setpoint clamp,
• Output clamp, and
• Error clamp.
Setpoint clamp The setpoint clamp works as follows:

− If the setpoint is lower than the setpoint low clamp, then the
setpoint (SP) is set to the value of setpoint low clamp.
− If the setpoint is higher than the setpoint high clamp, then the
setpoint (SP) is set to the value of setpoint high clamp.
Output clamp The output clamp works as follows:

− If the output is lower than the output low clamp, then the output
(u'(t)) is set to the value of output low clamp.
− If the output is higher than the output high clamp, then the output
(u'(t)) is set to the value of output high clamp.
Error clamp The error clamp works as follows:

e(t) becomes { sign (e't) } ∗ MIN { abs (e'(t)), abs (deviation limit) }.
Software Manual
E.3 Configuration and Implementation of PID Controllers
in the FSC System
Configuration The project database will contain a PID variable (with type 'P') in the
following two cases:
• A PID controller has been added to the database (using the 'System
Configuration' option of FSC Navigator), or
• A PID controller has been placed on a functional logic diagram
(using the FLD design editor).
The configuration of the parameters, mode and scaling can be done

using the 'System Configuration' option of FSC Navigator (via
Hardware Specs). For details refer to Section 4 of this manual
("System Configuration").
PID modes There are four PID modes:

• Auto,
• Manual,
• Test, and
• Cascade.
Auto mode This mode is active in normal operation. The output is calculated by
the input, setpoint and all the configured parameters.
Manual mode In this mode, the output (set by the 'Monitor System' option of FSC
Navigator or via the OM input in the logic) is copied straight into the
logic. To have a bumpless transfer back to Auto mode, the manual
output is also copied to the calculations.
Test mode In this mode, the input and the setpoint can be entered in the 'Monitor
System' option of FSC Navigator. The input and setpoint connected
by logic are overwritten by these values. This option can be used to
test the PID function.
Cascade mode If the setpoint of the PID is variable and is directly connected to the
output of another PID, this PID is in cascade mode. Cascade mode is
used to control outputs that depend on more than one input variable.
Software Manual
Implementation The PID can be implemented in the logic by a standard PID symbol
(see Figure E-4). For normal operation (Auto mode), only the setpoint
(S) and input (I) must be connected.
A Measurement
I
D PID
Setpoint 5 S
1 Output D
CS O
A
M
OM
PID name
Figure E-4 Standard PID algorithm in FSC system software
If the PID is in manual mode, the output (O) can be set via the
'Monitor System' option of FSC Navigator. If M=1, the PID mode will
be switched to manual mode and the value OM will be copied to the
output O. If M=0, the PID mode stays in the current mode.
Since the input M and OM are linked together, either both or none
must be connected.
In cascade mode, the cascade input (CS) must be connected to the

output (O) of another PID. For cascade PIDs, the controller that is
connected to the cascade input (CS) must be configured. This is done
using the System Configuration option of FSC Navigator (Hardware
specs) by toggling the cascade input to YES and entering the tag
number of the PID that is connected to the CS input.
If the PID is in cascade mode, the connected PID must be in master

mode. If more than two PIDs have been configured, these can be
connected in the chain of controllers. This is done by switching the
first PID in Auto mode and all the other PIDs in cascade mode. The
PID in Auto mode is called master and all others are slaves.
All connected binary inputs and outputs must be of signal type Float
(F).
Software Manual
E.4 Practical Application of PIDs
Example In the following example two PID controllers have been configured:
InputSlave A
InputMaster A I
I
D PID
PID F 5 S 4 D Output
F 10 S 3 O
O CS A
CS
M
M
F 50 OM
OM
pidslave
pidmaster
ManualModeSwitch
"1=Manual"
Figure E-5 Implementation example of a cascade PID
The cascade input of the PID 'pidslave' is used, which means that the
cascade input must be configured to 'Yes' the master PID tag number
must be configured as 'pidmaster'.
PID slave in If PID 'pidslave' is in Auto mode, the output is calculated based on
Auto mode the analog input 'InputSlave' and the setpoint S (= 5). The digital
input 'ManualModeSwitch' (M) must be low.
If 'ManualModeSwitch' is high, the value of OM (= 50) is copied
directly to the value of the output O 'Output'.
In none of the above situations, the operating mode of PID 'pidmaster'
is important.
PID master in If PID 'pidmaster' is in Auto mode, the PID 'pidslave' can be switched
Auto mode over to cascade mode. The master PID 'pidmaster' will calculate its
output based on the input 'InputMaster' and the setpoint S (= 10). The
cascade PID 'pidslave' will calculate its output based on the input
'InputSlave' and its cascade setpoint (CS), which is the output of the
'pidmaster'.
Software Manual
Application A practical application of the above example is temperature control of
an 'open' vessel that is filled with a certain gas as shown in the figure
below:
A PID slave
P-Volume
D
PID master I
A
Pressure I D
D O
A
O S
10 S
Temperature
Figure E-6 Temperature control using PID
Volume and pressure are measured. The temperature is controlled by

the master/slave PID algorithm.
Software Manual
Software Manual
Fail Safe Control
Appendix F:
Communication
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix F: Communication
F.1 Introduction .................................................................................................... F-1
F.2 Definitions....................................................................................................... F-2
F.3 Communication with the TotalPlant Solution (TPS) System ....................... F-5
F.4 Communication with the PlantScape System .............................................. F-6

F.4.1 Introduction....................................................................................................................... F-6
F.4.2 Architecture ...................................................................................................................... F-7
F.4.3 Hardware.......................................................................................................................... F-8
F.4.4 Sequence-of-Event (SOE) Data....................................................................................... F-8
F.4.5 Extended Diagnostics and System Events ...................................................................... F-8
F.4.6 Communication Redundancy ........................................................................................... F-9

the Modbus Protocol.................................................................................... F-10
F.5.1 Introduction..................................................................................................................... F-10
F.5.3 Data Exchange............................................................................................................... F-11
F.5.4 Supported Function and Error Codes ............................................................................ F-13
F.5.6 Addressing ..................................................................................................................... F-15
F.5.10 Cable Lengths ................................................................................................................ F-20
F.5.11 Modbus for Communication with Contronic E/P ............................................................ F-21
F.6 Communication with Distributed Control Systems (DCSs) Using the

RKE3964R Protocol...................................................................................... F-22
F.6.1 Introduction..................................................................................................................... F-22
F.6.3 Data Exchange............................................................................................................... F-24
F.6.4 Timeouts......................................................................................................................... F-26
F.6.11 Cable Lengths ................................................................................................................ F-34
Software Manual
Appendix F: Communication i
F.7 Communication Between FSC Systems Using the FSC-FSC Protocol ..... F-35
F.7.1 Introduction.....................................................................................................................F-35
F.7.3 Data Exchange...............................................................................................................F-37
F.7.4 Timeouts.........................................................................................................................F-38
F.7.7 Configuration ..................................................................................................................F-40
F.7.8 Copying Allocations to Ensure Consistency of Connected Systems .............................F-44
F.7.10 Cable Lengths ................................................................................................................F-46
F.8 Communication Between FSC Systems Using the RKE3964R Protocol .. F-47
F.8.1 Introduction.....................................................................................................................F-47
F.8.3 Data Exchange...............................................................................................................F-49
F.8.4 Timeouts.........................................................................................................................F-51
F.8.5 Supported Commands and Error Messages..................................................................F-51
F.8.7 Block Definition...............................................................................................................F-52
F.8.11 Cable Lengths ................................................................................................................F-58
F.9 Communication With the FSC User Station Using the Development
System (DS) Protocol ................................................................................... F-59
F.9.1 Introduction.....................................................................................................................F-59
F.9.3 Data Exchange...............................................................................................................F-60
F.9.6 Cable Lengths ................................................................................................................F-62
F.10 Communication With the FSC User Station Using a Modem..................... F-63
F.10.1 Using a Modem ..............................................................................................................F-63
F.10.2 Configuring a Modem Channel in the Application..........................................................F-64
F.10.3 Configuration Requirements ..........................................................................................F-65
F.10.4 Establishing a Modem Link ............................................................................................F-66
F.10.5 Direct Control .................................................................................................................F-68
F.11 Output to Printers Using the Printer Protocol ............................................ F-70

F.11.1 Introduction.....................................................................................................................F-70
F.11.3 Data Exchange...............................................................................................................F-70
F.11.4 SER Printing...................................................................................................................F-71
F.11.5 Reports Printing..............................................................................................................F-72
F.11.7 Handshaking ..................................................................................................................F-73
F.11.9 Cable Lengths ................................................................................................................F-75
Software Manual
ii Appendix F: Communication
F.12 Real-Time Clock Synchronization ............................................................... F-76

F.12.1 Introduction..................................................................................................................... F-76
F.12.2 Synchronization Priorities...............................................................................................F-76
F.12.3 Multiple Synchronization Sources .................................................................................. F-78
F.12.4 Synchronization Commands from Time Sources........................................................... F-79
Software Manual
Appendix F: Communication iii
FIGURES
Figure F-1 Physical and logical links ............................................................................................F-2

Figure F-2 Point-to-point link ........................................................................................................F-2
Figure F-3 Multidrop link ...............................................................................................................F-3
Figure F-4 Redundant FSC point-to-point link ..............................................................................F-3
Figure F-5 Redundant DCS point-to-point link .............................................................................F-3
Figure F-6 Redundant multidrop link ............................................................................................F-4
Figure F-7 Redundant device link.................................................................................................F-4
Figure F-8 FSC Safety Manager and TPS....................................................................................F-5
Figure F-9 Example of FSC status display on PlantScape server ...............................................F-6
Figure F-10 FSC and PlantScape...................................................................................................F-7
Figure F-11 PlantScape-FSC interface and redundancy................................................................F-9
Figure F-12 Modbus data area configuration................................................................................F-12
Figure F-13 Process control response time..................................................................................F-18
Figure F-14 Defining RKE3964R marker and register areas........................................................F-24
Figure F-15 RKE3964R block definition in slave mode ................................................................F-28
Figure F-16 RKE3964R block definition in master mode .............................................................F-29
Figure F-17 Process control response time (RKE3964R) ............................................................F-32
Figure F-18 FSC communication network ....................................................................................F-36
Figure F-19 Identifying systems in FSC communication network ................................................F-41
Figure F-20 Communication channel configuration screen ..........................................................F-42
Figure F-21 Allocating variables to connected FSC systems .......................................................F-43
Figure F-22 Copying allocations from connected FSC system ....................................................F-44
Figure F-23 Two-way communication between FSC systems using the RKE3964R protocol.....F-49
Figure F-24 Defining RKE3964R markers and registers ..............................................................F-50
Figure F-25 RKE3964R block definition .......................................................................................F-53
Figure F-26 RKE3964R block numbers........................................................................................F-54
Figure F-27 Modem link between FSC user station and FSC system .........................................F-63
Figure F-28 Configuration of modem communication channel.....................................................F-64
Figure F-29 Modem connection options .......................................................................................F-66
Figure F-30 Dialing options...........................................................................................................F-67
Figure F-31 Status details about the modem connections ...........................................................F-68
Figure F-32 Direct control of modem ............................................................................................F-68
Figure F-33 Printer data area configuration..................................................................................F-71
Figure F-34 Time synchronization sources for FSC networks .....................................................F-77
Figure F-35 Time synchronization in case of multiple sources.....................................................F-78
Figure F-36 Receiving range of the DCF-77 radio transmitter near Frankfurt..............................F-80
Software Manual
iv Appendix F: Communication
TABLES
Table F-1 Supported Modbus function codes ........................................................................... F-13

Table F-2 Supported Modbus error codes ................................................................................ F-13
Table F-3 Calculation of Modbus addresses............................................................................. F-15
Table F-4 Address ranges per function code (Modbus RTU) ................................................... F-16
Table F-5 Configuration options for Modbus protocol ............................................................... F-19
Table F-6 Maximum cable lengths for Modbus communication................................................ F-20
Table F-7 Address ranges per function code (Hartmann & Braun)........................................... F-21
Table F-8 Supported RKE3964R commands for communication between FSC and DCS....... F-26
Table F-9 Supported RKE3964R error codes for communication between FSC and DCS ...... F-26
Table F-10 Configuration options for RKE3964R communication between FSC and a DCS..... F-33
Table F-11 Maximum cable lengths for RKE3964R communication between FSC and a
DCS........................................................................................................................... F-34
Table F-12 FSC-FSC communication timeout ............................................................................ F-39
Table F-13 Configuration options for FSC-FSC protocol ............................................................ F-45
Table F-14 Maximum cable lengths for FSC-FSC communication ............................................. F-46
Table F-15 Supported RKE3964R commands for communication between two FSC
systems ..................................................................................................................... F-51
Table F-16 Supported RKE3964R error codes for communication between two FSC
systems ..................................................................................................................... F-52
Table F-17 Configuration options for RKE3964R communication between two FSC systems .. F-57
Table F-18 Maximum cable lengths for RKE3964R communication between two FSC
systems ..................................................................................................................... F-58
Table F-19 Configuration options for Development System protocol.......................................... F-61
Table F-20 Maximum cable lengths for Development System communication .......................... F-62
Table F-21 Configuration options for Printer protocol ................................................................. F-74
Table F-22 Maximum cable lengths for Printer communication .................................................. F-75
Table F-23 Frequency of time synchronization commands ........................................................ F-79
Software Manual
Appendix F: Communication v
Software Manual
vi Appendix F: Communication
Appendix F – Communication
F.1 Introduction
Communication Process control and safeguarding functions in today's chemical and

petrochemical plants are highly automated via computer systems.
Apart from the processing power offered by these computer systems,
they are also capable of gathering valuable information on the current
status of the process component they are monitoring. In order to make
optimum use of this information and to be able to provide adequate
information to plant operators, both the process control systems and
the safeguarding systems must have communication capabilities to
exchange process information.
The FSC system can communicate with the following devices:

1. Distributed Control Systems (DCSs) or visualization programs
running on PC (MMI), to make optimum use of the available
process information.
The following communication protocols are available:
− TPS network protocol (see subsection F.3),
− PlantScape network protocol (see subsection F.4),
− Modbus RTU (see subsection F.5),
− Modbus H&B (see subsection F.5.11), and
− RKE3964R (see subsection F.6).
2. Other FSC systems, to decentralize process safeguarding in
combination with central monitoring and control capabilities.
− FSC-FSC (see subsection F.7), and
− RKE3964R (see subsection F.8).
3. The FSC user station, with FSC Navigator, FSCSOE, or
visualization programs running on it, to monitor the process and
FSC system status.
− Development System (DS) (see subsection F.9), and
− Modem (see subsection F.10).
4. Printers directly connected to the FSC system, to produce status
reports and sequence-of-event records (see subsection F.11).
For optimum availability and fail-safe communication, the redundant

FSC system configurations allow the use of redundant communication
links as well.
Software Manual
Appendix F: Communication F-1
F.2 Definitions
Definitions The following terminology is important for understanding the FSC

system's communication capabilities:
Logical link The logical link expresses the capability of two systems to exchange
information via the communication network. A logical link may
include several physical links (e.g. via communication servers, see
Figure F-1).
Physical link The physical link defines the interconnection of systems within the
communication network. Multiple logical links may be realized
across a physical link (see Figure F-1).
= physical link
= logical link
communication
server
Figure F-1 Physical and logical links
Point to point A point-to-point link is a physical link that interconnects two

systems, with one system connected to each end of the link (see
Figure F-2).
FSC1
DCS FSC2
FSC user station
Printer
Figure F-2 Point-to-point link
Software Manual
F-2 Appendix F: Communication
Multidrop link A multidrop link is a physical link that interconnects multiple
systems (see Figure F-3). Within the context of the FSC
communication, a multidrop link is the connection of a single master
system with multiple slave systems.
FSC1
DCS
FSC user station
FSC2 FSCx FSCy
Figure F-3 Multidrop link
Redundant link A redundant link is a logical link which is connected to both Central
Parts of a redundant FSC system (see Figure F-4 to Figure F-7). For
FSC-FSC communication, a redundant link is realized via two
independent physical links, each connected to a single Central Part.
For communication with non-FSC systems, a redundant link is
realized via a single physical link which is connected to both Central
Parts.
FSC1 FSC2
Figure F-4 Redundant FSC point-to-point link
DCS
FSC
Figure F-5 Redundant DCS point-to-point link
Software Manual
FSC1
DCS
FSCx FSCy
Figure F-6 Redundant multidrop link
DCS
FSC1
Figure F-7 Redundant device link
Communication master A communication master is a system which is able to initiate an

exchange of data with other systems without being requested by
another system.
Communication slave A communication slave is a system which only exchanges data with
another system when requested by the other system.
Communication server A communication server is a system which is not an end user of the
exchanged data, but serves as a routing device between master and
slave systems (see Figure F-1).
Software Manual
F.3 Communication with the TotalPlant Solution (TPS) System
FSC and TPS The FSC Safety Manager (FSC-SM) is directly connected to the
Universal Control Network (UCN) of the TotalPlant Solution (TPS)
system as shown in Figure F-8. Its interface to the UCN enables the
FSC-SM to share data with its peers on the UCN.
Note:
For details on communication between the FSC-SM and the TPS
system refer to the FSC-SM documentation set (binder
TPS 3076).
Local Control Network

(LCN)
Network
Interface
Module FSC Safety Manager
FSC-SMM Fail Safe Controller

UCN Drop Cables A+B Communication processor Control Processor
and modem
UCN Taps
(M68360 processor)
I/O access
UCN network support
Safety interlock
Network redundancy
User programming
TPS access to FSC-SM data Self-diagnostics
Peer-to-peer communication
UCN
Trunk Cables A+B FSC I/O Subsystem
Digital Input Analog Input Digital Output

24-60 Vdc 0(4)-20 mA 24-220 Vdc Analog Output
115 Vac 0(1)-5 Vdc 115 Vac 0(4)-20 mA
0(2)-10 Vdc
To other UCN nodes
Figure F-8 FSC Safety Manager and TPS
Note:
If there is more than one write command to the same address per
application cycle, then only the last write command will be
valid.
Software Manual
F.4 Communication with the PlantScape System
F.4.1 Introduction
FSC and FSC can interface with the PlantScape system, which means that
PlantScape FSC-related data can easily be exchanged between FSC and
PlantScape. This allows this information to be shared and made
available on the PlantScape server displays (see Figure F-9).
Notes:
1. For optimum performance, it is recommended that the
Ethernet network used for FSC-PlantScape communication
is a dedicated network (i.e. not part of a physical office
network).
2. For details on PlantScape communication refer to the
PlantScape documentation.
Figure F-9 Example of FSC status display on PlantScape server
Software Manual
F.4.2 Architecture
Architecture Figure F-10 below shows the basic architecture of the

FSC-PlantScape communication link.
Plantscape
Server
Ethernet
Network PlantScape Interface
Ethernet Board Fail Safe Controller

Communication processor Control Processor
and Ethernet interface
(M68360 processor) I/O access
Ethernet network support Safety Interlock
Network read / write access User programming
to PlantScape interface data Self-diagnostics
FSC I/O Subsystem
Analog Input
Digital Input Digital Output Analog Output
0(4)-20 mA
24-60 Vdc 24-220 Vdc 0(4)-20 mA
0(1)-5 Vdc
115 Vac 115 Vac
0(2)-10 Vdc
To other Ethernet boxes
Figure F-10 FSC and PlantScape
Software Manual
F.4.3 Hardware
Hardware Communication with the PlantScape system is established through

dedicated FSC Ethernet interface modules which are located in the
Central Part(s) of the FSC system. Two module types are available:
• 10018/E/1 (with one serial Ethernet interface), and
• 10018/E/E (with two serial Ethernet interfaces).
Both module types are equipped with flash memory, which allows the
required communication software to be downloaded from the FSC
user station. This eliminates the need for EPROMs.
Note:
The 10018/E/x PlantScape interface modules can only be used
in conjunction with flash-memory CPU and COM modules, i.e.
10012/1/2, 10020/1/1, 10014/x/x, and 10024/x/x.
F.4.4 Sequence-of-Event (SOE) Data
Sequence-of-event Sequence-of-event (SOE) features as supported by the FSC controller

(SOE) data are integrated into the PlantScape system. Each tag name that has
been "SOE-enabled" is time-stamped by the FSC controller and
reported to the PlantScape server, where it is incorporated into the
standard PlantScape SOE table. Standard SOE displays are available
to view the events as they are reported.
F.4.5 Extended Diagnostics and System Events
Extended
diagnostics In addition to sequence-of-event data, FSC also supports sharing of
and system events extended diagnostics and system events with PlantScape.
Note:
This feature is available in PlantScape Release 300 as an add-on,
and will be included as a standard feature in a future release of
the PlantScape software.
Software Manual
F.4.6 Communication Redundancy
Communication FSC supports redundant communication via the 10018/E/x

redundancy PlantScape interface modules. The interface between the PlantScape
server and FSC supports connection redundancy (dual Ethernet) and
processor redundancy. The configurations supported are shown in
Figure F-11 below.
Note:
For redundant FSC controllers, redundant Ethernet is required,
with redundant NIC cards in the PlantScape server.
PS server PS server
A 1 A B 2
A A
CP B CP
single processor + single processor +

single link redundant link
(using 10018/E/1 module) (using 10018/E/E module)
PS server
A B
3
A
CP1
B
CP2
redundant processor +
redundant link
(using two 10018/E/1 modules)
Figure F-11 PlantScape-FSC interface and redundancy
Software Manual
F.5 Communication with Distributed Control Systems (DCSs)
Using the Modbus Protocol
F.5.1 Introduction
Modbus The Modbus protocol as implemented in the FSC system conforms to

the description in the Gould Modbus protocol reference guide:
PI-MBUS-300 Rev C, 1991.
The FSC system supports the Modbus RTU protocol. A special
"dialect" of the protocol, for communication with Hartmann & Braun
Contronic E and Contronic P systems, is available as an option (see
subsection F.5.11).
During the configuration of the application, the communication of the

FSC system to the DCS is also configured. This is done by assigning
the Modbus protocol to a communication channel, and defining the
protocol parameters.
Frames Information exchange within the Modbus protocol is accomplished in

frames. Each frame contains the following information:
• system address,
• command type (function code),
• function parameters, and
• checksum (CRC-16).
The length of a frame depends on the function code and the function
parameters. The checksum is used to verify the correctness of the
transferred information.
Write/force The Modbus protocol can accept write commands to the FSC system.
commands The FSC user station can send force commands to the FSC system.
In redundant Central Part configurations, the number of write/force

commands to the FSC system per application program cycle is
limited. There is no such limitation in single (non-redundant)
configurations. An approximation of the number of write/force
commands per application cycle in redundant configurations can be
calculated using the following formula:
Software Manual
application cycle time in ms − 160 ms
10
If, for example, the application cycle time is 300 ms, then the
maximum number of write/force commands per application cycle in
redundant configurations is 14 (140/10). This is the total number of
write/force commands of all communication protocols to one FSC
system.
Notes:
valid.
F.5.2 Supported Networks
Supported The Modbus communication protocol is supported on both point-to-

networks point and multidrop networks. The communication link may be
redundant (see Figure F-2 to Figure F-7).
A point-to-point physical redundant link can be configured by
assigning a primary point-to-point Modbus link to Central Part 1 and a
secondary point-to-point Modbus link to Central Part 2. The link
specification of CP2 must point to the Modbus link on CP1. The
configured timeout must have a value that is larger than the maximum
read cycle per link.
F.5.3 Data Exchange
Data exchange During the communication process, the FSC system performs a slave
function, which means that data exchange is initiated by the DCS.
Please note that Modbus communication is only running if the FSC
system is running. This means that there will be no Modbus
communication if the FSC system has shut down or is waiting for a
reset.
If a redundant device link is used and both Central Parts are healthy,
then communication is established via both Central Parts alternately.
A changeover to the other Central Part is made every 10 seconds. If
Software Manual
one Central Part fails, communication is realized via the healthy
Central Part.
The data exchange between the FSC system and the DCS is realized
via predefined marker and register areas (see Figure F-12). The
communication link to the FSC system application is made through
application variables (I, O, BI, or BO) with location 'COM'. These are
allocated to the FSC communication link with the DCS.
The FSC system is able to handle a maximum of 250 data bytes per
read/write transfer, i.e. a maximum number of 2000 coils or 125
holding registers.
Figure F-12 Modbus data area configuration
Software Manual
F.5.4 Supported Function and Error Codes
Supported function Table F-1 and Table F-2 list the Modbus function and error codes
and error codes supported by the FSC system.
Table F-1 Supported Modbus function codes

Code Description
1 read coil status
2 read input status
3 read holding register
4 read input register
5 force coil
6 load register
8 loop back test
15 force multiple coils
16 force multiple registers
Notes:
− Function code 2 is handled the same way as function code 1.
− Function code 4 is handled the same way as function code 3.
− If function code 15 is used to force more than 32 coils at the
same time, the first coil and the number of coils must both be
an integer multiple of 8.
Table F-2 Supported Modbus error codes

Code Description Cause
1 Illegal function code An unsupported function code is

applied.
2 Illegal data address The applied variable address exceeds

the configured communication area
boundaries.
3 Illegal data value Incorrect data format (e.g. invalid time

stamp).
6 Busy Data cannot be accepted at this time.
Software Manual
For a detailed description of the supported function codes (including
function parameters and frame formats) refer to the Gould Modbus
protocol reference guide: PI-MBUS-300 Rev C, 1991.
Reading FSC Modbus function code 3 is used to read the contents of the FSC event
event buffer buffer. At each request, the FSC system sends a response message
(function code 3) that contains 16 events. If the FSC event buffer holds fewer than 16
events, the remaining entries in the response message will be filled
with an SER buffer empty event. Each event contains 8 bytes.
Note:
For details on the event record structure refer to Appendix B of
this manual ("Sequence-of-Event Recording").
When reading FSC event data, the DCS must use the register
addresses 49994 and 49995 alternately. The FSC system uses the
constant switchover as a mechanism to confirm the event response
message that was sent last. As long as the FSC system receives
alternating register addresses, the FSC system sends the next events in
sequence. If, however, the same address is received twice (which
means that something went wrong), the FSC system will resend the
last event message.
The event data read option is only valid if numerical SER is used.
F.5.5 Real-Time Clock Synchronization
Real-time clock The real-time clock of the FSC system can be set by the DCS system
synchronization via the Modbus register write function codes 6 or 16 with specific
register addressing. This feature can be used to synchronize the time
of the FSC system with that of the DCS.
Function code 16 If function code 16 is used, the following format is required:

Function code: 16
Register address: 49996
Number of registers: 4
Register contents:
49996 – Year : Decimal value, e.g. 1997
49997 – Month/Date : Decimal value, e.g. 0812 means August 12.
49998 – Hour/Minute : Decimal value, e.g. 2233 means 22.33h
(a 24-hour clock is used).
49999 – Sec/00 : Decimal value, e.g. 5900 means 59 sec.
Software Manual
Function code 6 If function code 6 is used, the four registers can be written separately.
Upon reception of the first three registers (year, month/date,
hour/minute) the FSC system only stores the received data. Upon
reception of the last register (sec), the FSC system checks the entire
time stamp. The data will be accepted if the time stamp represents a
valid date and time.
Hardwired clock Due to variable delays in the data transfer from the DCS to the FSC
synchronization system (scan delay + duration of the transfer), an additional
input hardwired clock synchronization input must be provided in the FSC
system. When the clock synchronization input is asserted (0 → 1
edge), a previously transferred time stamp is copied to the FSC
real-time clock.
A predefined digital input tag with tag number CLOCK-SYNC is
available and must be allocated to a hardware channel. This clock
synchronization input allows easy adjustment of the FSC clock to
daylight-saving time. If the input is asserted while no time stamp was
transmitted by the DCS, the FSC real-time clock will be set to
3:00 am.
F.5.6 Addressing
FSC system Within the communication, the address of the target FSC system that
addressing the DCS wants to communicate with must be specified. The
communication address of the FSC system is the system number ∗ 4.
Variable The representation of the addresses of variables that is used for

addressing FSC-DCS communication differs between the FSC and DCS system.
Table F-3 below lists the algorithms that can be used to calculate the
Modbus addresses from the FSC addresses. These are generated
automatically when communication is configured (see also Figure
F-12).
Table F-3 Calculation of Modbus addresses

Type Modbus address
I FSC address + 1
O FSC address + 5001
BI (FSC address / 2) + (4)0001
AI (FSC address / 2) + (4)3001
BO (FSC address / 2) + (4)5001
Software Manual
Notes:
− No addressing information is contained in function code 8.
− The Modbus addresses for the variable types I, O, AI, BI and
BO can be output to hardcopy using the 'Print \ Project
− For some DCS systems, the offset of 40000 for addresses of
BI and BO variables cannot be configured. Refer to the
documentation of your DCS vendor for further details.
The FSC system allows access of variable type I and O in multiples of

16 via the Modbus register function codes 3, 4, 6 and 16.
Table F-4 below provides an overview of the supported Modbus
function codes, the applicable address ranges and the FSC variable
types.
Note:
Table F-4 does not apply to the special "dialect" of the Modbus
protocol that is used for communication with Hartmann & Braun
Contronic E and Contronic P systems. The address ranges for
the Hartmann & Braun version of the Modbus protocol are listed
in Table F-7 (see subsection F.5.11).
Table F-4 Address ranges per function code (Modbus RTU)

Function code Address range Remarks
1, 2, 5, 15 1 - 4096 FSC type I
1, 2 5001 - 9096 FSC type O
3, 4, 6, 16 (4)0001 - (4)2048 FSC type BI

(4)8001 - (4)8256 FSC type I
3, 4 (4)3001 - (4)3256 FSC type AI

(4)5001 - (4)7048 FSC type BO
(4)9001 - (4)9256 FSC type O
3 (4)9994 / (4)9995 Event data
6, 16 (4)9996 - (4)9999 RTC data
Software Manual
Note:
The address ranges in FSC releases ≥ 2.9x differ from the ranges
in older versions. However, releases ≥ 2.9x still support these
ranges. This means that no adaptation of the DCS address
configuration is required when upgrading the FSC system to
release ≥ 2.9x. It is recommended that you use the
above-mentioned address ranges for new applications and
modify old applications when required.
F.5.7 Response Times
Response times Two response times are important:

• Communication response time, and
• Process control response time.
Communication
response time The response time of the FSC system is defined as the time between:
− reception of the last character of the DCS message, and
− transmission of the first character of the response message.
The response time has a typical value of 6 ms (maximum value:
25 ms).
Process control The process control response time is defined as the time between two
response time specific events:
− The first event is the alteration of a control variable in the DCS.
− The second event is the detection by the DCS of the FSC system
response to the first event.
The maximum process control response time is calculated by adding

the following parameters (see Figure F-13):
1. internal delay in the DCS to detect the control operation,
2. the communication scan time of the DCS,
3. the transmission time of the Modbus write command frame,
4. the application program time of the FSC system,
6. the communication response time of the FSC system,
Software Manual
7. the transmission time of the Modbus read command,
8. the transmission time of the Modbus response frame, and
9. the internal delay in the DCS system to process the received
information.
9 8
C C 4
DCS O 2 7 O FSC
M 5 M
3 6
Figure F-13 Process control response time
F.5.8 Fault Handling
Fault handling Communication channels that are configured for the Modbus protocol
are expected to be communicating continuously. The correct
operation of these communication channels is monitored by the FSC
system via timeouts, which can be defined by the user when
configuring the communication channel.
A channel is regarded faulty if no valid Modbus frame was received

within the configured timeout period. A fault is then reported via the
extended diagnostics and the DEVICE-COM.FLT alarm marker.
The system automatically recovers from this fault as soon as
communication is re-established.
Software Manual
F.5.9 Link Types and Baud Rates
Link types Modbus communication is configured using the 'System

and baud rates Configuration' option of FSC Navigator (Install \ Modules \ Central
parts \ COM). Table F-5 below presents the various configuration
options for the Modbus communication protocol.
Table F-5 Configuration options for Modbus protocol

Connection Communication Supported
Link type
type module interface baud rates
B-interface* RS-232 ≤ 38k4
E-interface* Current loop ≤ 19k2
F-interface RS-232 ≤ 38k4
Point to point I-interface RS-422 (no encoding) ≤ 125k
I-interface RS-422 (Manchester) 1M, 2M
I-interface RS-422 (FM0) 1M, 2M
I-interface RS-485 (no encoding) ≤ 125k
Multidrop
* The B-interface and E-interface are obsolete.

1. The configurations apply to link status Primary and Secondary.
2. The link can either be redundant or non-redundant. However, a
redundant link is implicitly considered to be a multidrop link.
3. The handshake type (none, hardware), number of stop bits (1, 2)
bits per character (7, 8) and parity type (odd, even, none) are
configurable.
4. The maximum baud rate of channel A is 19k2 instead of 38k4 if a
communication module (100x4/x/x) is used with:
− a Tristate RS-232C interface and a glass fiber interface
(100x4/F/G), or
− a Tristate RS-232C interface and an isolated RS-485/RS-422
interface (10004/F/I).
Software Manual
F.5.10 Cable Lengths
Maximum Table F-6 below lists the maximum cable lengths for Modbus
cable length communication.
Table F-6 Maximum cable lengths for Modbus communication

Communication link
RS-422/485 RS-232 Current loop

Baud rate
(I-interface) (F-interface / B-interface*) (E-interface*)
1200 1.2 km (0.75 mi) 15 m (49.2 ft) 100 m (328 ft)
2400 1.2 km (0.75 mi) 15 m (49.2 ft) 50 m (164 ft)
4800 1.2 km (0.75 mi) 15 m (49.2 ft) 25 m (82 ft)
9600 1.2 km (0.75 mi) 15 m (49.2 ft) 10 m (32.8 ft)
19k2 1.2 km (0.75 mi) 15 m (49.2 ft) –
38k4 1.2 km (0.75 mi) 10 m (32.8 ft) –
50k 1.2 km (0.75 mi) – –
57k6 1.2 km (0.75 mi) – –
115k2 1 km (0.62 mi) – –
125k 1 km (0.62 mi) – –
Software Manual
F.5.11 Modbus for Communication with Contronic E/P
Hartmann & Braun The FSC Modbus protocol driver for communication with Hartmann
Contronic E/P & Braun systems Contronic E and Contronic P conforms to the
description of the Gould Modbus protocol reference guide;
PI-MBUS-300, Rev C, 1991.
The functionality of the driver is identical to that of the general FSC

Modbus RTU driver, with the following exceptions:
1. Real-time clock synchronization (see page F-14) is not supported.
2. There are two differences in the event specification (see page
F-14):
− Two specific event sequence numbers have been defined,
independent of the configured numerical SER range:
EEEEh = event buffer empty
FFFFh = event buffer overflow
− The event value range is [0, 1].
3. The address ranges are different (see Table F-7 below).
Table F-7 Address ranges per function code (Hartmann & Braun)
Function code Address range Remarks
1, 2, 5, 15 0 - 3999 FSC type I
1, 2 5000 - 8999 FSC type O
3, 4, 6, 16 1000 - 1499 FSC type BI

2500 - 2749 FSC type I
3, 4 1500 - 1999 FSC type BO

2000 - 2255 FSC type AI
3 3072 / 3076 Event data
Software Manual
F.6 Communication with Distributed Control Systems (DCSs)
Using the RKE3964R Protocol
F.6.1 Introduction
RKE3964R The RKE3964R protocol, as implemented in the FSC system,

protocol conforms to the Siemens RKE3964/RKE3964R protocol
specification. The protocol can be used for data exchange between an
FSC system and a Distributed Control System (DCS).
Note:
The RKE3964R protocol can also be used for communication
between FSC systems. For details refer to subsection F.8.
The RKE3964R protocol is block-oriented. All data to be exchanged

is allocated within a predefined communication block. Either
complete blocks or partial blocks can be transferred.
Messages Data exchange is accomplished in messages. A message consists of:

• a command (read/write),
• data type,
• block number,
• data offset address within the block,
• a checksum, and
• data (if the message is a data write command).
The checksum is used to verify the correctness of received

information. A message contains a maximum of 128 data bytes.
Master/slave RKE3964R communication between FSC and a DCS supports both

master and slave operating modes.
In slave mode, the FSC system will only send data at the specific
request of the connected DCS.
In master mode, the FSC system may be configured to initiate data
transfer itself, either periodically or if a predefined event occurs.
Software Manual
Write/force The RKE3964R protocol can accept write commands to the FSC
commands system. The FSC user station can send force commands to the FSC
system.


10
system.
Notes:
valid.
Supported When used for communication between an FSC system and a DCS,
networks the RKE3964R protocol supports point-to-point links, redundant
device links and redundant point-to-point links (see Figure F-2,
Figure F-4 and Figure F-7).
A point-to-point physical redundant link can be configured by
assigning a primary point-to-point RKE3964R link to Central Part 1
and a secondary point-to-point RKE3964R link to Central Part 2.
Software Manual
F.6.3 Data Exchange
Data exchange The RKE3964R data exchange between the FSC system and the DCS
is realized via predefined marker and register areas (see Figure F-14).
The communication link to the FSC system application is made
through application variables of type I, O, BI, or BO with location
'COM'. Markers bytes are used for I and O variables, and register
bytes for BI and BO variables.
Figure F-14 Defining RKE3964R marker and register areas
Slave mode If slave mode has been configured for the RKE3964R communication
protocol, then data transfer is always initiated by the DCS.
If a redundant device link is used and both Central Parts are healthy,
then communication is established via both Central Parts alternately.
A changeover to the other Central Part is made every 10 seconds.
If one Central Part fails, communication is realized via the healthy
Central Part.
Software Manual
Master mode If master mode has been configured for the RKE3964R
communication protocol, then initiation of data transfer can be done
by the FSC system as well as by the DCS. The FSC system may be
configured for each block to transmit data under different kinds of
conditions. Possible conditions are:
• upon a specific request by the DCS only,
• each application program cycle,
• timed (each n ∗ 0.5 seconds),
• at occurrence of a specific output activation, or
• combined timed and output activation.
If a redundant device link is used, communication will only be

accomplished via one of the connected Central Parts. Normally this
will be the link via Central Part 1. The communication link connected
to the redundant Central Part serves as a hot stand-by. It takes over
communication if the first link fails.
Note:
If both redundant links fail, the FSC system will continuously
try to re-establish Central Part communication via both links.
Such a situation could occur when the connected system is taken
off-line. Upon restart of the system, incorrect data could be
received by the DCS due to collision of data sent by both
Central Parts within the FSC system. This situation normally
lasts only for a short period of time.
Software Manual
F.6.4 Timeouts
Device A communication channel is regarded faulty if no valid RKE3964R

communication frame was received within the defined device communication
timeout timeout. This timeout is user-configurable. It can be set to any value
between 1 and 90 seconds. However, if the RKE3964R protocol is
used for communication between FSC and a DCS, the device
communication timeout must be set to a multiple of 3 seconds (which
is the default value). Any other setting will result in faulty
communication.
Response timeout The maximum RKE response timeout for a communication process
start-up is 550 ms, which is in full accordance with the RKE3964R
protocol definition.
F.6.5 Supported Commands and Error Messages
Supported Table F-8 and Table F-9 list the supported RKE3964R commands
commands and and error codes.
error messages
Table F-8 Supported RKE3964R commands for communication
between FSC and DCS
Command Description FSC equivalent
AD send data unit(s) Write marker or register area (I, BI)
ED read data unit(s) Read from marker or register area

(I, O, BI, BO)
ES test message Loopback test
Table F-9 Supported RKE3964R error codes for communication

between FSC and DCS
0Fh Communication is blocked The Central Part has stopped.
Software Manual
Real-time clock If the RKE3964R protocol is used for communication between an

synchronization FSC system and a DCS, the real-time clock of the FSC system can be
set by the DCS via a dedicated block write command. This feature
can be used to synchronize the time of the FSC system with that of
the DCS. The frame format of the command is as follows:
Command: "A","D" : Write command

Block number: 63
Start address: 00
Data word count: 00 04
Data format: FF FF
Data: YY YY : Four-digit BCD
MM DD : Four-digit BCD
HH mm SS : hours, minutes and seconds
in BCD (24-hour clock is used)
xx : not used
For example, May 14, 2000 10:33:56 p.m. would become:

20 00 (year)
05 14 (month and date)
22 33 56 (hours, minutes, seconds)
Hardwired clock Due to variable delays in the data transfer from the DCS to the FSC
synchronization system (scan delay + duration of the transfer), an additional
input hardwired clock synchronization input must be provided in the FSC
system. When the clock synchronization input is asserted (0 → 1
edge), a previously transferred time stamp is copied to the FSC real-
time clock.
A predefined digital input tag with tag number CLOCK-SYNC is

available and must be allocated to a hardware channel. This clock
synchronization input allows easy adjustment of the FSC clock to
daylight-saving time. If the input is asserted while no time stamp was
transmitted by the DCS, the FSC real-time clock will be set to
3:00 am.
Software Manual
F.6.7 Block Definition
Block definition The RKE3964R protocol block definitions need to be made when the
data exchange areas are defined. This is done using the 'System
Configuration' option of FSC Navigator (Install \ Modules \ Central
parts \ COM \ Link specification).
Figure F-15 shows the block definition screen for slave mode.
Figure F-16 shows the block definition screen for master mode.
The following fields are available in both slave and master mode:
− Block number,
− Block size, and
− Register type.
The following fields are only available in master mode:

− Frequency,
− Time period, and
− Transmit on event.
Figure F-15 RKE3964R block definition in slave mode
Software Manual
Figure F-16 RKE3964R block definition in master mode
Block number You can enter any value between 0 and 255. Block numbers are
divided into four groups, each with its specific type of data:
0 - 62 : binary inputs (BI)
64 - 127 : binary outputs (BO)
128 - 191 : digital inputs (I)
192 - 255 : digital outputs (O)
Block number 63 is reserved for the real-time clock set command.
Block size This field defines the number of data bytes in the block. The
maximum number of bytes in a block depends on the number of
marker or register bytes configured for input or output, and on the
size of the blocks that have already been defined for the same
variable type.
Software Manual
Please note the following conditions for the various register types:
Bytes: The number of bytes that make up a communication block
must be even.
Words: The number of bytes that make up a communication block
must be even.
Floats: The number of bytes that make up a communication block
must be a multiple of 4.
If the above conditions are not met, communication may become

unstable, which may lead to a Central Part stop.
Register type This field is available for block numbers 0 to 127, i.e. for input or
output registers. It determines the register type that is used within the
block. Only registers of the defined type can be allocated to this
block. The supported types are: Byte, Word or Float.
Frequency This field is only available in master mode. It allows you to define a
condition that must be met before the FSC system will send data.
The following options are available:
Undefined : No periodic master function
Not periodic : No periodic master function
Send data on event possible
Time periodic : Send data time periodic
Each program cycle : Send data each program cycle.
Use <Space> to toggle the various options.
Note:
All blocks can be configured to be transmitted by the FSC
system without specifically being requested by the DCS. This
also applies to input data blocks. The reason for this is that data
transmitted by the DCS via RKE3964R cannot be viewed
locally by the DCS itself. The FSC input areas can therefore also
be read by the DCS to allow a kind of "echoing" of received
data.
Time period This field is only available in master mode and only if the value of
the Frequency field is 'Time periodic'. It allows you to define the
time between data exchanges in steps of 0.5 seconds.
Any value between 0 and 120 can be chosen. This means that the
maximum time period is 1 minute (120∗0.5 second).
Software Manual
Transmit on event This field is only available in master mode and only if the value of
the Frequency field is 'Time periodic' or 'Not periodic'. This field
allows you to add a digital output (with location 'SYS') that is related
to starting data exchange. Whenever this output become active, data
exchange is started for the related block number.
Consider, for example, Figure F-16 on page F-29. At BO block

number 66, the Frequency field is set to 'Not periodic', while the
Transmit on event field is set to 'Yes'. This results in automatic
generation of a digital output with location 'SYS' and its tag number,
which consists of the Central Part number, communication module
number, communication channel and block number: "E 1_1_B_66". If
this output becomes active, block number 66 of Central Part 1,
communication module 1, channel B will be sent to the connected
DCS.
Response times Two response times are important:

• Communication response time, and
• Process control response time.
Communication
− reception of the last character of the DCS message, and

25 ms).
Process control The process control response time is defined as the time between two
response time specific events:
− The first event is the alteration of a control variable in the DCS.
− The second event is the detection by the DCS of the FSC system
response upon the first event.
Software Manual
The maximum process control response time is calculated by adding
the following parameters (see Figure F-17):
1. internal delay in the DCS to detect the control operation,
3. the transmission time of the RKE3964R write command frame,
4. the application program time of the FSC system,
6. the communication response time of the FSC system,
7. the transmission time of the RKE3964R read command frame,
8. the transmission time of the RKE3964R response frame, and
9. the internal delay in the DCS to process the received information.
9 8
C C 4
DCS O 2 7 O FSC
M 5 M
3 6
Figure F-17 Process control response time (RKE3964R)
Fault handling Communication channels that are configured for the RKE3964R
protocol are expected to be communicating continuously. The correct
system via the device communication timeout. If this timeout expires
without any valid RKE3964R frame being received, the
communication channel is regarded faulty.
The device communication timeout is user-configurable, but for
RKE3964R communication between FSC and a DCS it must be set to
a multiple of 3 seconds (which is the default value). Any other setting
Software Manual
will result in faulty communication. A fault is then reported via the
extended diagnostics and the DEVICE-COM.FLT alarm marker.
Link types RKE3964R communication is configured using the 'System

options for the RKE3964R communication protocol.
Table F-10 Configuration options for RKE3964R communication

between FSC and a DCS
Link type
Point to point E-interface* Current loop ≤ 9600
Redundant
E-interface* Current loop ≤ 9600
device link F-interface RS-232 ≤ 19k2
Please note the following consideration:

1. The link can either be a redundant device link (multidrop) or a
point-to-point link.
Software Manual
Maximum Table F-11 below lists the maximum cable lengths for RKE3964R
cable length communication between FSC and a DCS.
Table F-11 Maximum cable lengths for RKE3964R communication

between FSC and a DCS
Communication link
RS-232 Current loop

Baud rate
(F-interface / B-interface*) (E-interface*)
1200 15 m (49.2 ft) 100 m (328 ft)
2400 15 m (49.2 ft) 50 m (164 ft)
4800 15 m (49.2 ft) 25 m (82 ft)
9600 15 m (49.2 ft) 10 m (32.8 ft)
19k2 15 m (49.2 ft) –
Software Manual
F.7 Communication Between FSC Systems Using the
FSC-FSC Protocol
F.7.1 Introduction
FSC systems Several production units may exist within a plant which operate
independently of one another, but often have common utilities (e.g.
steam and air). In order to minimize the consequences for the entire
plant if an emergency arises in one production unit, separate
safeguarding systems can be used to protect the independent
production units.
A disadvantage of this decentralization strategy is that process
information is only available locally whereas it is often needed in a
central control room. Communication between FSC systems provides
the means to decentralize process safeguarding in combination with
central process monitoring and control capabilities.
The protocol normally used for communication between FSC systems

is the proprietary FSC-FSC communication protocol of Honeywell
Safety Management Systems. The protocol includes timing
restrictions and a high level of error detection and recovery, which
makes it suitable for exchanging safety-related information while
maintaining optimum availability.

can also be used in network configurations where large time delays
are to be expected, e.g. modem communication, communication over
The FSC communication network is configured during the

configuration of the application, by defining the interconnections
between the FSC systems and the parameters of the FSC-FSC
protocol. The exchange of information is realized via input variables
(I, BI) and output variables (O, BO) which are allocated to the
connected FSC systems. Both safety-related and non safety-related
information may be exchanged. In addition, diagnostic information is
exchanged automatically.
The inputs and outputs are included in the functional logic diagrams
(FLDs) to realize the required application task of the systems.
Software Manual
Supported FSC-FSC communication supports both point-to-point and multidrop

networks networks. A maximum number of 10 slaves may be connected to one
master via one multidrop link. The actual number of slaves depends
on the baud rate and amount of exchanged data.
If one system in an FSC network has a redundant configuration, all
communication links must be redundant.
Master/slave Communication between FSC systems is based on the master/slave

concept. Within this concept, the master system is responsible for all
communication activities.
When both redundant links are healthy, communication is established
via both links alternately. If one link fails, communication is realized
via the healthy link.
Apart from master and slave systems, the FSC system also supports
communication servers. Communication servers are FSC systems that
are interconnected between the communicating master and slave
system. Their task is to route the data which is exchanged between
master and slave. Figure F-18 shows an example of a network that
contains all three system types.
Master
Communication server
Slaves
Figure F-18 FSC communication network
Note:
Only one level of communication server systems is allowed.
Software Manual
Low baud rate Low baud rate communication is used in those applications where
communication high baud rates are not possible. This may have a number of reasons:
− The type of cable that is used for communication is not suited for
high baud rate communication.
− The communication takes place over long distances.
− There is intermediate equipment that does not support high baud
rate communication.
− Multiple communication channels are sent via one communication
line (using multiplexing), which means that the baud rate of the
channels is smaller than that of the communication line.
F.7.3 Data Exchange
Data exchange The master periodically sends data to the slave systems and initiates a
request for data from the slaves. For point-to-point links, the period is
one application program cycle of the master system. For multidrop
links, a new data transmission and request for a slave are initiated
after the slave reply to the previous request has been received.
Data exchange between the master and the slave is realized via
predefined marker and register areas. These areas contain variables
(I, O, BI and BO) with location 'FSC' that are allocated for
communication with the other system. The configuration of the data
areas and contained variables is accomplished via the 'System
Note:
The configuration of the master and slave systems must be
consistent, i.e. the size of the marker/register output area in one
system must be equal to the size of the marker/register input
area in another system. Also, the tag numbers of the output
variables (O, BO) in one system must be identical to the tag
numbers of the corresponding input variables (I, BI) in the other
system.
Use the Copy Allocation feature of FSC Navigator to
accomplish maximum consistency.
Software Manual
F.7.4 Timeouts
FSC-FSC The FSC-FSC communication timeout is the maximum

communication communication time to exchange all data between the FSC master
timeout and all its slaves. To accommodate for long communication
distances, this timeout is user-configurable. It can be set between 1.2
and 30 seconds (in steps of 0.01 second) using the 'System
Configuration' option of FSC Navigator (Install \ Configuration \
FSC-FSC communication configuration \ FSC-FSC communication
timeout).
Note:
In an FSC network, the FSC-FSC communication timeout must
be set to the same value for all systems in the network.
The response time must be flexible due to the delay time of signals in
the communication medium (cable, radiographic, etc.). The exact
delay time depends on the distance to be traveled, and can be
calculated by the user taking into consideration the time delay for the
distance (300,000 km/sec.) and delays in the intermediate equipment
such as repeaters, modems, etc.
The 'Translate Application' option of FSC Navigator (the compiler)
will calculate the maximum delay time based on the system and
communication configuration in the log file. If the communication
distance is short and there is no intermediate equipment, the compiler
will provide a warning if a communication timeout was defined which
results in a response time of less than 15 ms. If the calculated response
time is lower than 10 ms, an error message will be generated. It is the
user's responsibility to check the actual required response time.
For details on how to calculate the response time refer to Section 5 of
the FSC Safety Manual.
Real-time clock The real-time clock of all FSC systems interconnected in a

synchronization communication network are synchronized. This ensures proper
sequencing of events across the systems, e.g. in case of a plant upset.
The synchronization accuracy between FSC systems is < 100 ms.
For details on real-time clock synchronization refer to subsection
F.12.
Software Manual
Fault handling The FSC system monitors the operation of its physical
communication links by means of a timeout, which depends on the
system function and the type of communication link (see Table F-12).
Table F-12 FSC-FSC communication timeout

Link type System Timeout
Response of slave system is expected within the

Master
Point-to-point same application program cycle.
Slave 1 second.
User-configurable between 1.2 and 30 seconds

(in steps of 0.1 second). The default value is 1.2
Master
seconds. See also Figure F-19 and Section 4 of
Multidrop this manual ("System Configuration").
2x configured communication timeout. See also

Slave
Section 4 ("System Configuration").
Failure of a physical link is reported via the extended diagnostics and

the EXT.COMMUNIC.FLT alarm marker. The extended diagnostics
report includes the Central Part numbers and the system numbers of
all systems for which a logical link was defined across the physical
link.
Note:
There may be situations where an FSC-FSC communication link
has been defined, but no application data is being exchanged
(i.e. no marker bytes and register bytes have been defined in the
link specification). This may, for example, be the case in an
SOE network where the FSC-FSC link is only used to send all
SOE data to one common channel. If, in such configurations, the
communication cable is disconnected from the module, the
communication link will not be reported faulty. If you do want
the link to be reported faulty, you should define "dummy data"
in the link specification (4 marker bytes and 4 register bytes).
Software Manual
Redundant links Within redundant configurations, the communication is preserved as
long as one of the logical links is healthy.
If communication fails on both links – i.e. communication to a
connected system fails – then the value of safety-related input
variables (I, BI) that are allocated to that system are forced to their
safe (i.e. '0') state. The value of the non safety-related input variables
allocated to the system are frozen at their last received value.
F.7.7 Configuration
Configuration This section describes, in general terms, the configuration steps that
are of interest for FSC-FSC communication. For details refer to
Section 4 of this manual ("System Configuration").
Configuring an FSC communication network consists of the following
main steps:
1. Identifying the connected systems,
2. Configuring the communication channel, and
3. Allocating variables for data exchange.
System The first step in the definition of the FSC communication network is
identification identifying the interconnected systems by their application name.
To link system numbers to application names, do the following:
1. Choose the 'System Configuration' option of FSC Navigator.
2. Choose Install from the main menu.
3. Choose Configuration from the submenu.
4. Move the cursor to the FSC-FSC communication configuration
field en press <E>. The screen as shown in Figure F-19 will
appear.
5. Enter the system name(s) that you want to include in the
communication network, or press <?> to choose from a list.
Software Manual
Figure F-19 Identifying systems in FSC communication network
The information entered in this screen can be used to simplify

successive configuration steps. It is also used by the 'Translate
Application' option of FSC Navigator (the compiler) to verify the
correctness of the overall network configuration.
Communication The next step is configuring the communication channel(s).

channel To configure a communication channel, do the following:
2. Choose Install from the main menu.
3. Choose Modules from the submenu.
4. Choose Central parts from the submenu.
5. Choose COM from the submenu. The main configuration screen
for communication channels will appear (see Figure F-20).
Software Manual
Figure F-20 Communication channel configuration screen
Configuration of communication channels includes the following:

• protocol definition,
• network definition,
• link status,
• connected systems, and
• definition of the size of the marker and register areas.
Make sure that all these items have been properly configured.
If they are not, you may not be able to allocate variables to connected
FSC systems.
For details on link types, baud rates and maximum cable lengths refer
to subsections F.7.9 and F.7.10.
Variable allocation The final step in the definition of the FSC communication network is
allocating the variables that are intended for data exchange between
FSC systems (I, BI, O, BO with location 'FSC').
Software Manual
These variables are defined using the 'System Configuration' option of
FSC Navigator (Signal specs \ Add) or during creation of the
functional logic diagrams (FLDs). To allocate the variables to a
connected FSC system, do the following:
2. Choose Hardware specs from the main menu.
3. In the Variable type field, type the abbreviation for the variable
that you wish to edit (I, BI, O, or BO), or type 'NA' for all
unallocated variables.
4. In the Tag number field, type the tag number of the variable you
wish to allocate, or press <?> to choose from a list of available tag
numbers. The variable definition screen will appear (see Figure
F-21).
Figure F-21 Allocating variables to connected FSC systems
5. Move to the System number field. A popup window will appear

which lists the available system numbers. The variable will be
allocated to the system number that you choose.
Software Manual
F.7.8 Copying Allocations to Ensure Consistency of Connected
Systems
Consistency of The configuration of communicating FSC systems must be consistent

connected systems with respect to the size of the marker and register areas, and the tag
numbers of the allocated variables.
To guarantee correct configuration, the 'System Configuration' option
of FSC Navigator offers a 'Copy Allocations' feature, which extracts
this information from the database of the connected systems.
To copy the allocation of a connected FSC system, do the following:
1. Go to the main configuration screen for communication channels.
2. Move the cursor to the Link specification field and press <E>.
Please note that this option is not available if no systems have
been defined to connect to (see subsection 4.5.9 of this manual).
3. A popup window will appear which allows you to copy the
allocations of a connected FSC system. If more than one system is
connected, you are first prompted to specify from which system
the allocations should be copied (see Figure F-22).
Figure F-22 Copying allocations from connected FSC system
Software Manual
You can then press <C> to copy the communication allocations of the
specified system. The 'Copy Allocation' option can save valuable time
during project engineering. It is strongly recommended that you
completely define the data exchange in one system (either master or
slave), and then copy the information to the connected system.
Link types Table F-13 below presents the configuration options for the FSC-FSC
and baud rates protocol.
Table F-13 Configuration options for FSC-FSC protocol

Connection Supported
Communication Link type
type baud rates
module interface
G-interface Fiber optics (Manchester) 1M, 2M
G-interface Fiber optics (FM0) 1M, 2M

Point to point G-interface Fiber optics (FM1) 1M, 2M
F-interface RS-232 9600, 19k2, 38k4
I-interface RS-485 (no encoding) 19k2 to 125k
Multidrop I-interface RS-485 (Manchester) 1M, 2M

1. The configurations apply to link status Master, Slave and
Communication Server.
2. Only one channel on a communication module can be set to a
baud rate of 2M.
Software Manual
Maximum Table F-14 below lists the maximum cable lengths for FSC-FSC
Table F-14 Maximum cable lengths for FSC-FSC communication

Communication link
RS-422/485 RS-232 Fiber optics

Baud rate
(I-interface) (F-interface) (G-interface)
9600 – 15 m (49.2 ft) –
19k2 1.2 km (0.75 mi) 15 m (49.2 ft) –
38k4 1.2 km (0.75 mi) 15 m (49.2 ft) –
50k 1.2 km (0.75 mi) – –
57k6 1.2 km (0.75 mi) – –
115k2 1 km (0.62 mi) – –
125k 1 km (0.62 mi) – –
1M 120 m (394 ft) – 4.5 km (2.8 mi)
2M 60 m (197 ft) – 4.5 km (2.8 mi)
Software Manual
F.8 Communication Between FSC Systems Using the
RKE3964R Protocol
F.8.1 Introduction
RKE3964R The RKE3964R protocol, as implemented in the FSC system,

protocol conforms to the Siemens RKE3964/RKE3964R protocol
specification. Under certain circumstances, this protocol can be used
for data exchange between an FSC system and another FSC system.
Note:
The RKE3964R protocol can also be used for communication
between FSC and a DCS. For details refer to subsection F.6.
The RKE3964R protocol is block-oriented. All data to be exchanged

is allocated within a predefined communication block. Either
complete blocks or partial blocks can be transferred.
FSC-FSC The protocol normally used for communication between FSC systems
communication is the FSC-FSC communication protocol (see subsection F.7). This
protocol includes a high level of error detection and recovery, which
makes it suitable for exchanging safety-related information while
maintaining optimum availability.
can also be used in network configurations where large time delays
are to be expected, e.g. modem communication, communication over
Even though the RKE3964R protocol can be used in such situations as
well, it is recommended that you use the FSC-FSC protocol.
Note:
If the RKE3964R protocol is to be used for safety-related data
exchange, a number of requirements and conditions must be
fulfilled for the communication to work correctly and reliably.
For details refer to Technical Note TN9801 ("Safety-related data
exchange using the RKE3964R communication protocol").
You can obtain a copy of this document by sending an e-mail
message to sms-info@honeywell.com.
Software Manual
Messages Data exchange is accomplished in messages. A message consists of:
• a command (read/write),
• data type,
• block number,
• data offset address within the block,
• a checksum, and
• data (if the message is a data write command).
The checksum is used to verify the correctness of received

information. A message contains a maximum of 128 data bytes.
Two-way Since two-way communication is normally required between FSC

communication systems – which means that both connected FSC systems must be
able to initiate data transfer themselves –, they will both need to be
configured as masters (see also subsection 0).
Write/force The RKE3964R protocol can accept write commands to the FSC
commands system. The FSC user station can send force commands to the FSC
system.

10
system.
Notes:
valid.
Software Manual
Supported When used for communication between FSC systems, the RKE3964R
networks protocol only supports non-redundant point-to-point links (see Figure
F-2 on page F-2). For two-way communication, both Central Parts of
both connected FSC systems must be configured as the master
primary (see Figure F-23 below). To prevent any communication
priority clashes, one of the FSC systems is considered the "master"
system, and the other the "slave". The "master" system must have an
odd system number, and the "slave" an even system number.
FSC “Master” FSC “Slave”

(odd-numbered) (even-numbered)
Master primary Master primary
CP 1 CP 1
Master primary Master primary
CP 2 CP 2
Figure F-23 Two-way communication between FSC systems

using the RKE3964R protocol
F.8.3 Data Exchange
Data exchange The RKE3964R data exchange between the two connected FSC
systems is realized via predefined marker and register areas (see
Figure F-24 on the next page). The communication link to the FSC
system application is made through application variables (I, O, BI, or
BO) with location 'COM'.
If a redundant device link is used, communication will only be

accomplished via one of the connected Central Parts. Normally this
will be the link via Central Part 1. The communication link connected
to the redundant Central Part serves as a hot stand-by. It takes over
communication if the first link fails.
Software Manual
Note:
If both redundant links fail, the FSC system will continuously
try to re-establish Central Part communication via both links.
Such a situation could occur when the connected system is taken
off-line. Upon restart of the system, incorrect data could be
received due to collision of data sent by both Central Parts
within the FSC system. This situation normally lasts only for a
short period of time.
`
Figure F-24 Defining RKE3964R markers and registers
The FSC system may be configured for each block to transmit data
under different kinds of conditions. Possible conditions are:
• upon a specific request by the other connected FSC system only,
• each application program cycle,
• timed (each N ∗ 0.5 seconds),
• at occurrence of a specific output activation, or
• combined timed and output activation.
Software Manual
F.8.4 Timeouts
Device A communication channel is regarded faulty if no valid RKE3964R

communication frame was received within the defined device communication
timeout timeout. This timeout is user-configurable.
If the RKE3964R protocol is used for communication between FSC
systems, the device communication timeout can be set to any value
between 1 and 90 seconds (except for multiples of 3 seconds). The
RKE response timeout will then depend on the value chosen for the
device communication timeout (see below).
Note:
If the device communication timeout is set to a multiple of
3 seconds, communication with a DCS is assumed.
Response timeout The RKE3964R protocol definition specifies that the maximum RKE
response timeout for a communication process start-up should be
550 ms.
If RKE3964R is used for communication between two FSC systems,
this timeout setting is flexible. The default setting is 550 ms (as per
RKE3964R specification). The RKE response timeout is calculated
automatically by dividing the configured device communication
timeout by 6. Thus, if the device communication timeout has been set
to 40 seconds, the RKE response timeout will be 6 seconds (40/6;
decimals are truncated).
F.8.5 Supported Commands and Error Messages
Commands and Table F-15 and Table F-16 list the supported RKE3964R commands
error messages and error codes.
Table F-15 Supported RKE3964R commands for communication

between two FSC systems
Command Description FSC equivalent
AD send data unit(s) Write marker or register area (I, BI)
ED read data unit(s) Read from marker or register area

(I, O, BI, BO)
Software Manual
Table F-16 Supported RKE3964R error codes for communication
0Fh Communication is blocked The Central Part has stopped.
Real-time clock If the RKE3964R protocol is used for communication between two
synchronization FSC systems, the master FSC system(s) cannot issue time
synchronization commands.
Note:
Even though no time synchronization commands are issued by
any of the master FSC systems, block number 63 is still
reserved.
F.8.7 Block Definition
Block definition The RKE3964R protocol block definitions need to be made when the
data exchange areas are defined. This is done using the 'System
Configuration' option of FSC Navigator (Install \ Modules \ Central
parts \ COM \ Link specification).
Figure F-25 on the next page shows the block definition screen.
The following fields are available:

− Block number,
− Block size,
− Register type,
− Frequency,
− Time period, and
− Transmit on event.
Software Manual
Figure F-25 RKE3964R block definition
Block number You can enter any value between 0 and 255. Block numbers are
divided into four groups, each with its specific type of data:
0 - 62 : binary inputs (BI)
64 - 126 : binary outputs (BO)
128 - 191 : digital inputs (I)
192 - 255 : digital outputs (O)
If the RKE3964R protocol is used for communication between two

FSC systems, you must make sure that the defined block numbers for
the "master" FSC system have matching block numbers at the "slave"
FSC system. The matching "slave" block number can be calculated by
subtracting 64 from the "master" block number. This will "link" a
block number from the "master" FSC system to a block number at the
"slave" FSC system (see Figure F-26).
Software Manual
Example:
If you have defined block numbers 195 (digital output) and 98 (binary
output) for the "master" FSC system, you must define block numbers
131 (= 195-64) and 34 (= 98-64) for the "slave" FSC system. Only
then will the outputs from the "master" FSC system be processed
correctly as inputs to the "slave" FSC system.
"Master" FSC "Slave" FSC

(odd-numbered) (even-numbered)
0 - 62 0 - 62
BI BI
64 - 126 64 - 127
BO BO
128 - 191 128 - 191

DI DI
192 - 255 192 - 255

DO DO
Figure F-26 RKE3964R block numbers
Notes:
1. If a block number has been used in the "slave" system, make
sure that you do not use the same block number in the
"master" system as well. This may cause communication
conflicts. In the example above, you should not use block
numbers 131 and 34 in the "master" system.
2. In RKE3964R communication between FSC systems, block
number 63 cannot be used. This is because this block
number is reserved for the real-time clock set command.
3. In RKE3964R communication between FSC systems, block
number 127 (binary output) cannot be used. This is because
the matching binary input (BI) would be 63 (= 127-64),
which is reserved for real-time clock synchronization (even
though this is not used).
Block size This field defines the number of data bytes in the block. The
maximum number of bytes in a block depends on the number of
marker or register bytes configured for input or output, and on the
size of the blocks that have already been defined for the same
variable type.
Software Manual
Please note the following conditions for the various register types:
Bytes: The number of bytes that make up a communication block
must be even.
Words: The number of bytes that make up a communication block
must be even.
Floats: The number of bytes that make up a communication block
must be a multiple of 4.
If the above conditions are not met, communication may become

unstable, which may lead to a Central Part stop.
Register type This field is available for block numbers 0 to 127, i.e. for input or
output registers. It determines the register type that is used within the
block. Only registers of the defined type can be allocated to this
block. The supported types are: Byte, Word or Float.
Frequency This field allows you to define a condition that must be met before
the FSC system will send data.
The following options are available:
Undefined : No periodic master function
Not periodic : No periodic master function
Send data on event possible
Time periodic : Send data time periodic
Each program cycle : Send data each program cycle.
Use <Space> to toggle the various options.
Time period This field is only available if the value of the Frequency field is
'Time periodic'. It allows you to define the time between data
exchanges in steps of 0.5 seconds.
Any value between 0 and 120 can be chosen. This means that the
maximum time period is 1 minute (120∗0.5 second).
Transmit on event This field is only available if the value of the Frequency field is
'Time periodic' or 'Not periodic'. It allows you to add a digital output
(O) with location 'SYS' that is related to starting data exchange.
Whenever this output becomes active, data exchange is started for the
related block number.
Software Manual
Consider, for example, Figure F-25 on page F-53. At BO block
number 66, the Frequency field is set to 'Not periodic', while the
Transmit on event field is set to 'Yes'. This results in automatic
generation of a digital output with location 'SYS' and its tag number,
which consists of the Central Part number, communication module
number, communication channel and block number: "E 1_2_A_66". If
this output becomes active, block number 66 of Central Part 1,
communication module 2, channel A will be sent to the connected
FSC system.
Response times For RKE communication between two FSC systems, only one
response time is important:
• Communication response time.
Communication
− reception of the last character of the FSC message, and

25 ms).
Fault handling Communication channels that are configured for the RKE3964R
protocol are expected to be communicating continuously. The correct
system via the device communication timeout. If this timeout expires
without any valid RKE3964R frame being received, the
communication channel is regarded faulty. A fault is then reported
via the extended diagnostics and the DEVICE-COM.FLT alarm
marker. The system automatically recovers from this fault as soon as
Software Manual
If the RKE3964R protocol is used for communication between FSC
systems, the device communication timeout can be set to any value
between 1 and 90 seconds (except for multiples of 3 seconds). The
RKE response timeout will then depend on the value chosen for the
device communication timeout. It is calculated automatically by
dividing the configured device communication timeout by 6. Thus, if
the device communication timeout has been set to 40 seconds, the
RKE response timeout will be 6 seconds (40/6; decimals are
truncated).
Link types RKE3964R communication is configured using the 'System

options for the RKE3964R communication protocol.
Table F-17 Configuration options for RKE3964R communication

Link type
Point to point E-interface* Current loop ≤ 9600
Redundant
E-interface* Current loop ≤ 9600
device link F-interface RS-232 ≤ 19k2
Please note the following consideration:

Software Manual
Maximum Table F-18 below lists the maximum cable lengths for RKE3964R
cable length communication between two FSC systems.
Table F-18 Maximum cable lengths for RKE3964R communication

Communication link
RS-232 Current loop

Baud rate
1200 15 m (49.2 ft) 100 m (328 ft)
2400 15 m (49.2 ft) 50 m (164 ft)
4800 15 m (49.2 ft) 25 m (82 ft)
9600 15 m (49.2 ft) 10 m (32.8 ft)
19k2 15 m (49.2 ft) –
Software Manual
F.9 Communication With the FSC User Station Using the
Development System (DS) Protocol
F.9.1 Introduction
FSC user station There may be communication between the FSC user station (with
FSC Navigator and/or FSCSOE running on it) and the FSC system
for a number of functions:
− monitor process behavior,
− monitor the FSC system status,
− rebuild the FSC databases on-line,
− verify the application as present in the FSC system,
− load software into the FSC system,
− force/write variables, and
− collect events logged by the FSC sequence-of-event (SER) function.
The communication protocol used for communication between the

FSC user station and FSC systems is the proprietary Development
System (DS) protocol of Honeywell Safety Management Systems.
Supported Communication between the FSC system and the FSC user station
networks supports both point-to-point and multidrop networks (see Figure F-2
and Figure F-3) connected to one or all Central Parts (redundant) of
an FSC system.
Software Manual
F.9.3 Data Exchange
Data exchange In the communication with the FSC user station, the FSC systems
perform a slave function. Data is only sent at the request of the FSC
user station.
The target system(s) for the FSC user station to communicate with
is/are determined either by the currently selected FSC Navigator
option (e.g. 'Monitor System') or by configuration within the program
option itself.
The communication may be related to a specific Central Part (e.g. to
read diagnostic information) or not (process status, event data read). In
the latter case, when a redundant communication link is being used,
the communication will be established via both links alternately. A
changeover to the other link is made every 10 seconds. If
communication via one of the links fails, all communication is
realized via the healthy link.
Fault handling If a communication channel has been configured for communication

with the FSC user station and it has been configured as the SER
reference channel, then the FSC system monitors the operation of the
communication channel. If the communication channel has not been
polled by the event collecting device during a period of one minute,
the channel is reported faulty via the extended diagnostics and the
DEVICE-COM.FLT alarm marker.
Link types Communication with the FSC user station is configured using the
and baud rates 'System Configuration' option of FSC Navigator (Install \ Modules \
Central parts \ COM). Table F-19 below presents the various
configuration options for the Development System communication
protocol.
Software Manual
Table F-19 Configuration options for Development System protocol
Link type

Point to point
I-interface RS-485 (Manchester) 1M
I-interface RS-485 (FM0) 1M

Multidrop I-interface RS-485 (Manchester) 1M
* The B-interface is obsolete.

1. The configurations apply to link status Primary and Secondary.
2. The link can either be redundant or non-redundant.
3. The maximum baud rate of channel A is 19k2 instead of 38k4 if a
communication module (100x4/x/x) is used with:
− a Tristate RS-232C interface and a glass fiber interface
(100x4/F/G), or
− a Tristate RS-232C interface and an isolated RS-485/RS-422
interface (10004/F/I).
Note:
If the FSC user station is used for collection of event data, the
channel must be assigned as the SER reference channel (using
Software Manual
F.9.6 Cable Lengths
Maximum Table F-20 below lists the maximum cable lengths for Development
cable length System communication.
Table F-20 Maximum cable lengths for Development System

communication
Communication link
RS-422/485 RS-232
Baud rate
(I-interface) (F-interface / B-interface*)
1200 1.2 km (0.75 mi) 15 m (49.2 ft)
2400 1.2 km (0.75 mi) 15 m (49.2 ft)
4800 1.2 km (0.75 mi) 15 m (49.2 ft)
9600 1.2 km (0.75 mi) 15 m (49.2 ft)
19k2 1.2 km (0.75 mi) 15 m (49.2 ft)
38k4 1.2 km (0.75 mi) 10 m (32.8 ft)
50k 1.2 km (0.75 mi) –
57k6 1.2 km (0.75 mi) –
115k2 1 km (0.62 mi) –
125k 1 km (0.62 mi) –
1M 120 m (394 ft) –
* The B-interface is obsolete.
Software Manual
F.10 Communication With the FSC User Station Using a
Modem
F.10.1 Using a Modem
Using a modem You can use a modem to establish a communication link between the
FSC user station and a remote FSC system (see Figure F-27).
FSC user station FSC system
Telephone line
Modem Modem
Figure F-27 Modem link between FSC user station and FSC system
Before you can use modem communication, you must have done the
following:
• connect a modem to one of the serial interfaces of the FSC system,
• connect a modem to the FSC user station (internal or external),
• configure a modem in Control Panel of Windows NT/2000 (through
the 'Modem' icon), and
• configure a modem communication channel in your application (see
F.10.2).
Note:
The maximum baud rate for modem communication is
9600 baud.
Software Manual
F.10.2 Configuring a Modem Channel in the Application
Configuring a For modem communication to work, you need to configure a channel

modem channel on an FSC communication module with the protocol 'DS (Modem)'
and network type 'Multidrop'. Figure F-28 shows the configuration
screen for a communication channel that has been configured for use
with a modem.
Figure F-28 Configuration of modem communication channel
Notes:
1. For details on the configuration parameters refer to section 4
of this manual ("System Configuration").
2. If no modem channel has been configured in the application,
the modem features of FSC Navigator are not available.
Software Manual
F.10.3 Configuration Requirements
Configuration The following considerations are important when configuring

requirements modems:
• The FSC modem channel needs to be set up with protocol
'DS (Modem)' and network type 'Multidrop'. It must be multidrop in
order to prevent that the FSC system also responds to commands
that are intended for the modems.
• Every feature which uses or turns on fault correction, flow control,
or interspeeder should be turned off. The modem must serve as
nothing more than a "passthrough gate", without adding anything
extra.
• The modem that will be connected to the FSC system should at least
be configured to support the following:
– load factory settings (often this will be Hayes command AT &F0)
– direct asynchronous mode (often this will be Hayes command
AT &Q0)
– auto-answer (often this will be Hayes command AT A, usually
with S0=1 added to indicate the modem should be respond after
one ring)
– inhibit result codes (often this will be Hayes command AT Q1)
– do not respond to DTR signal (often this will be Hayes command
AT E0)
– store and start (often this will be Hayes command AT &W0)
Please note that the exact Hayes commands may vary between
modems. These features can be included in the initialization string,
e.g. AT &F0 &Q0 A S0=1 Q1 E0 &W0.
You can use the Direct Control option in the dialog as shown in
Figure F-29 to load the initialization string in the firmware of the
modem, so that it will always initialize using these settings.
Software Manual
F.10.4 Establishing a Modem Link
Modem link To establish a modem link, do the following:

1. In FSC Navigator, click the Monitor button on the button bar, or
choose the Monitor System option from the On-Line menu.
2. Choose Modem from the main menu. The dialog as shown in
Figure F-29 will appear.
Note:
The Modem option is not available if no modem channel has
been configured in the application.
Figure F-29 Modem connection options
3. Choose the modem to be used from the Modem drop-down list,

which lists all modems that have been configured in Windows
NT/2000 (through Control Panel / Modems).
4. In the Phone number box, enter the telephone number to be
dialed.
Software Manual
5. You can set the dialing options by choosing the Properties
button. The standard Windows Dialing Properties dialog will
then appear (see Figure F-30). Here you can specify a number of
parameters that apply to modem dialing, e.g. tone/pulse dialing
and any number that needs to be dialed to access an outside line.
Figure F-30 Dialing options
6. After you have specified all dialing parameters (including the

phone number), choose the Connect button to make the modem
connection. After the link has been established successfully, all
options of FSC Navigator's on-line environment are available.
You can choose the Details button to see more details about the
status of the connection (see Figure F-31).
Software Manual
Figure F-31 Status details about the modem connections
To disconnect, choose the Hangup button. The modem link will then
be terminated.
F.10.5 Direct Control
Direct control It is possible to get direct control over a modem by clicking the
Direct control button in the dialog as shown in Figure F-29. This
will open the window as shown in Figure F-32.
Figure F-32 Direct control of modem
Software Manual
Here you can send direct Hayes commands to the modem. This is
useful for test purposes, and for configuring the modem that will be
connected to the FSC system.
For a list of available Hayes commands refer to the documentation
that came with the modem.
Software Manual
F.11 Output to Printers Using the Printer Protocol
F.11.1 Introduction
Printer protocol The Printer protocol within the FSC system is used to create
hardcopy of certain application output:
• Sequence-of-event recording (SER) data, and
• Reports.
The format and layout for this output can be defined using the 'SER
Format' option of FSC Navigator. Reports and SER generation are
briefly explained in subsections F.11.4 and F.11.5.
Supported The Printer protocol can only be used for point-to-point links and
networks redundant device links (see Figure F-2 and Figure F-7).
F.11.3 Data Exchange
Data exchange The communication between FSC system and printer is done
simplex, i.e. the FSC system sends ASCII characters and the printer
prints them on paper.
There is, however, an option to allocate binary output (BO) variables

with location 'COM' to the printer channel. This is done to allow BO
SER messages to be generated for the printer (see Figure F-33).
Software Manual
Figure F-33 Printer data area configuration
Two different types of output can be printed:

• Sequence-of-event recording (SER) data, and
• Reports.
Each of these applications is discussed in more detail below.
F.11.4 SER Printing
SER printing The FSC system provides sequence-of-event recording (SER)

features. The SER data provided by the FSC system can be directly
sent to a printer, or it can be used by FSCSOE.
FSCSOE is a separate Windows application that logs process-related
events as well as all FSC system diagnostics and all force operations
performed on system variables. The user can then view and analyze
this information when needed. This provides excellent time-stamped
information for post-mortem analysis and/or monitoring of (abnormal)
process behavior.
Software Manual
If the SER data is sent to a printer, then the 'SER Formats' option of
FSC Navigator enables you to define an output format for each
variable type. This means that you can indicate yourself which data is
of interest to you when printing SER and which data is not.
Notes:
1. For details on how to configure SER refer to Section 4 of
this manual ("System Configuration").
2. For details on SER events and message generation refer to
Appendix B of this manual ("Sequence-of-Event
Recording").
3. For details on FSCSOE refer to the FSCSOE manuals
(FS50-xxx, FS51-xxx, FS52-xxx, FS53-xxx, or FS55-xxx,
where 'xxx' is the software release).
4. For details on editing SER message formats refer to Section
5 of this manual ("Editing Reports and SER Format").
Numerical SER There is one special feature for generating SER messages that are
sent to a printer device: numerical SER format. This means that an
intelligent device is used to process short hexadecimal SER records
instead of complete ASCII format messages. For more information
refer to Appendix B of this manual ("Sequence-of-Event
Recording)".
F.11.5 Reports Printing
Reports printing Not only abnormal situations may be of interest in a running plant.
For example, you may want to print out a daily report that contains
important information about a number of process variables for
evaluation of process efficiency.
The 'SER Format' option of FSC Navigator allows you to define up to

64 report formats. Based on such a format definition, a report will be
generated and sent to a printer device when at least one of up to three
conditions for that report is met. Conditions that can be defined are:
− SER event : a specific SER event occurs,
− Counter value : a specific counter value is reached,
− Register value : a specific register value is reached.
For details on how to configure and edit report formats refer to
Section 5 of this manual ("Editing Reports and SER Format").
Software Manual
Fault handling The on-line status of communication channels that are configured for
the Printer protocol is monitored by the FSC system via a fixed link
timeout of one minute, and also by the configured handshake
protocol.
F.11.7 Handshaking
Handshaking The Handshake field in the Printer protocol configuration screen

(see Figure F-33) is used to define the handshake type that is used.
This field can have the following values:
• None,
• XON/XOFF, and
• Hardware.
Each of these options is discussed in more detail below.
No handshake If the Handshake field contains the value 'None', no handshaking is

used. In that case, the FSC system has no means of detecting that a
printer is off-line or that it has been disconnected. In that case, the
link timeout is disabled, which means that SER messages and reports
can be lost when the printer goes off-line.
XON/XOFF If the Handshake field contains the value 'XON/XOFF', the FSC
handshaking system expects the printer to repeatedly send an XON character when
it is on-line, and an XOFF character when it is off-line. In that case,
the time required for the FSC system to detect that the printer is
off-line is the time between two successive XON/XOFF characters
sent by the printer.
Furthermore, if the printer is completely disconnected from the FSC

system, then no characters are received at all, and it may take as long
as one minute (the link timeout) before the FSC system detects that
the link to the printer is faulty. This may lead to SER messages being
lost. If, for example, a printer goes off-line, it may be some time
before it sends an XOFF character to the FSC system. All SER
messages that are sent to the printer by the FSC system during this
time will be lost.
Software Manual
Hardware If the Handshake field contains the value 'Hardware', the FSC
handshaking system detects immediately if the printer goes off-line or is
disconnected.
This means that the chance of SER messages being lost is negligible.
It allows the FSC system to buffer SER messages until the printer
goes on-line again or until the link is detected faulty. In the latter case
the FSC system will try to reroute SER message via the redundant
link.
If you do not want to lose SER messages, it is therefore strongly

recommended that you choose the hardware handshaking option when
configuring the printer protocol.
Link types Table F-21 below presents the various configuration options for the
and baud rates Printer protocol.
Table F-21 Configuration options for Printer protocol

Link type
Point to point E-interface* Current loop ≤ 19k2

Multidrop

1. The configurations apply to link types.
Software Manual
Maximum Table F-22 below lists the maximum cable lengths for Printer
Table F-22 Maximum cable lengths for Printer communication

Communication link
RS-232 Current loop

Baud rate
1200 15 m (49.2 ft) 100 m (328 ft)
2400 15 m (49.2 ft) 50 m (164 ft)
4800 15 m (49.2 ft) 25 m (82 ft)
9600 15 m (49.2 ft) 10 m (32.8 ft)
19k2 15 m (49.2 ft) –
Software Manual
F.12 Real-Time Clock Synchronization
F.12.1 Introduction
Real-time clock In order to ensure accurately time-stamped process event data, the
synchronization real-time clocks of the FSC systems in a network need to be
synchronized to each other. FSC networks accept several external
sources to synchronize their real-time clocks: the German atomic
clock (DCF-77), a connected DCS system and the FSC user station
(with FSC Navigator running on it).
F.12.2 Synchronization Priorities
Synchronization If multiple time sources have been configured (e.g. two or more
priorities controllers being connected to a DCS or Modbus device), this can
lead to multiple time synchronization requests being generated. In
order to prevent this from happening, a priority algorithm is used.
This means that clock synchronization data from sources of lower
priority will be ignored as long as data from sources of higher priority
is valid. Thus, synchronization data from only one source is used at
any time. The priorities are defined as follows:
1. German atomic clock (DCF-77)
2. TotalPlant Solution (TPS) system (connected via UCN)
3. PlantScape system (connected via Ethernet)
4. Contronic E/P system (connected via P-Bus)
5. DCS system connected via Modbus or RKE3964,
with or without a hardware strobe input (CLOCK-SYNC)
6. FSC user station (with FSC Navigator or FSCSOE).
As soon as the device from the current priority level is no longer

available, the FSC network will use the time synchronization data
from the device with the next-highest priority.
Software Manual
2. TotalPlant Solution (TPS)
(via UCN)
1. DCF-77
3. PlantScape
(via Ethernet)
FSC Network
4. Contronic E/P
(via P-Bus)
6. FSC User Station

5. DCS via Modbus/RKE3964R
Figure F-34 Time synchronization sources for FSC networks
Note:
As soon as a higher-level source of time synchronization
becomes available again, the FSC network will immediately and
automatically switch back to the source with the highest priority
that is available.
Time master The FSC time master is the FSC system in the network that is at the
top of the network hierarchy. It obtains time information from the
time sources, and issues time synchronization commands to the other
FSC systems in the network. This is done periodically, once every
FSC-FSC communication timeout interval (as set in the FSC-FSC
communication configuration screen, see Figure F-19).
FSC systems If an FSC system is connected to a Universal Control Network

connected to UCN (UCN), you have the option of letting the FSC system be
synchronized to the UCN time or to the FSC time master in the
network. This is specified in the configuration screen for the UCN
communication channel (System Configuration / Install / Modules /
Central parts / COM). For details refer to subsection 4.7.7 of this
manual.
Software Manual
F.12.3 Multiple Synchronization Sources
Multiple If multiple time synchronization sources are available in the network,

synchronization first the priority algorithm on the previous page is applied.
sources If more than one time synchronization source of the same hierarchy
level is available (e.g. several UCNs), the following rules are applied
to determine which source is used to synchronize the real-time clocks
in the FSC network:
1. The real-time clocks are synchronized using the source that is
connected to the FSC system at the highest FSC network
hierarchy level.
2. In case of multiple sources with the same network hierarchy level,
the real-time clocks are synchronized using the source that is
connected to the FSC system with the lowest system number.
Note:
It may be that the source that is connected to the FSC system
with the lowest system number has not been set to send time
synchronization commands. In that case the FSC system with
the next-highest number is used.
As an example, consider the network as shown in Figure F-35, which

has four time synchronization sources of the same hierarchy level
(UCN).
UCN
FSC Network
FSC
Time Controller
Master 10
FSC FSC FSC

Controller Controller Controller
1 2 3
UCN UCN UCN
Figure F-35 Time synchronization in case of multiple sources
Software Manual
Since FSC Controller 10 has the highest network hierarchy, it will be
the time master, and time synchronization commands from the UCN
connected to it will be used to synchronize the real-time clocks across
the FSC network.
If no UCN had been connected to FSC Controller 10, the UCN
connected to FSC Controller 1 would be used, since this controller has
the lowest system number. If the UCN connected to FSC Controller 1
has not been set to issue time synchronization commands, the UCN
connected to FSC Controller 2 will be used.
F.12.4 Synchronization Commands from Time Sources
Synchronization The time sources periodically give time synchronization commands

commands from to the time master. The frequency in which this is done depends on
time sources the time source used. Table F-23 below provides an overview of the
frequencies for the various time synchronization sources.
Table F-23 Frequency of time synchronization commands

Time synchronization
Source Frequency
1. DCF-77 The FSC time master reads the value of the DCF-77
signal every 30 seconds.
2. DCS connected via UCN The DCS issues a time synchronization command to the
(TPS) FSC time master every 6 seconds.
3. PlantScape The PlantScape system issues a time synchronization

command to the FSC time master:
a) as soon as the communication link is
(re-)established (at system startup, and every time
the FSC enable status on the PlantScape server
display is cycled), and
b) every 24 hours at a user-defined number of minutes
after midnight.
4. Contronic E/P system The DCS issues a time synchronization command to the
connected via P-Bus FSC time master every second.
5. DCS connected via Modbus The frequency in which the DCS issues a time
or RKE3964R synchronization command to the FSC time master
depends on the configuration at the DCS side.
6. FSC user station Time synchronization commands must be given

(with FSC Navigator or manually from FSC Navigator (On-Line Environment \
FSCSOE) Diagnostics \ System Information \ Set real-time clock).
Software Manual
DCF-77 The FSC network can use the radio signal of the German atomic
clock (DCF-77) as the primary source for time synchronization,
providing it is located within the receiving range of the DCF-77
transmitter near Frankfurt, Germany (see Figure F-36). The inner
circle in Figure F-36 shows the region of Europe where reception of
the DCF radio signal is usually good. The outer circle in Figure F-36
shows the region where reception of the DCF signal is usually
possible.
Frankfurt
Figure F-36 Receiving range of the DCF-77 radio transmitter

near Frankfurt
Outside the receiving range of the DCF-77 radio transmitter, a

GPS-to-DCF converter can be used for the 10006/2/2 Diagnostic and
Battery Module (DBM). More information can be obtained through
the manufacturer of this converter (Hopf).
As long as the DCF-77 signal is valid (which is determined by special

hardware), the FSC time master will read the DCF-77 time once every
30 seconds, and use it to synchronize the other FSC systems in the
network. This is done once every FSC-FSC communication timeout
interval (as set in the FSC-FSC communication configuration screen,
see Figure F-19).
The FSC network will use this signal to set its real-time clock. If, for
whatever reason, the DCF-77 signal is no longer found to be valid
(e.g. due to interference), a two-minute timeout will be initiated. This
will prevent transient errors having a greater impact than they should.
If the time signal recovers before the timeout expires, the FSC
network will continue to use the DCF-77 signal as the source for time
synchronization.
Software Manual
DCS systems If the time signal does not recover before the two-minute DCF-77
timeout expires, the FSC network will switch to the source with
next-highest priority: a DCS system or – if none has been connected
to the FSC network or the connected DCS system is not used to issue
time-set commands – to the FSC user station.
Not all DCSs have the same priority. The TotalPlant Solution (TPS)
system (connected via UCN) has the highest priority, followed by
PlantScape (connected via Ethernet), Contronic E/P (connected via
P-Bus), and finally a DCS connected via Modbus or RKE3964R.
Thus, if more than one DCS are present, the TPS system will always
take precedence over others.
A connected DCS system can be configured to send time

synchronization commands automatically in fixed (configurable)
intervals, or the user can send them manually. Every time a time
synchronization command from the DCS system is executed, a
30-hour timeout is initiated. The DCS system is regarded faulty for
time synchronization if no new time synchronization command is
received within these 30 hours. During this 30-hour time period, the
FSC network will remain synchronized with the DCS system, and will
ignore any time synchronization data from other sources of lower
priority: a 'lower-level' DCS system or the FSC user station. As soon
as the timeout expires without a new time synchronization command
having been received, the FSC network will accept time
synchronization commands from a lower-level source.
FSC user station Only if no DCS system is available any more will the system accept
(FSC Navigator or time synchronization commands from the FSC user station. Time
FSCSOE) synchronization commands from the FSC user station are issued
manually via FSC Navigator (On-Line Environment \ Diagnostics \
System Information \ Set real-time clock) or FSCSOE (R130 or
higher).
Software Manual
Hardware A DCS system connected via Modbus or RKE3964 may be equipped
strobe input with a hardware strobe input (CLOCK-SYNC). If that is the case, any
time synchronization command sent by the DCS system is executed
only after the CLOCK-SYNC system input has been asserted. If no
CLOCK-SYNC input is present, the time synchronization command
is executed immediately.
In some configurations, the hardware strobe input may also be

asserted without a time synchronization command being sent by the
DCS system (e.g. if it can be actuated manually by turning a switch).
In that case, the FSC real-time clock will be set to 03:00:00 (3 am).
Synchronization As soon as a higher-level source of time synchronization becomes

source recovery available again, the FSC network will immediately and automatically
switch back to the source with the highest priority that is available.
Software Manual
Fail Safe Control
Appendix G:
FSC Multiplexers
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix G: FSC Multiplexers
G.1 Introduction ................................................................................................... G-1
G.2 Output Multiplexers....................................................................................... G-3
G.3 Input Multiplexers.......................................................................................... G-5
G.4 Multiple I/O That Uses Multiplexers ............................................................. G-7
G.5 Configuring Multiplexers .............................................................................. G-8

G.5.1 Multiplexers ..................................................................................................................... G-8
G.5.2 Multiplexed I/O .............................................................................................................. G-10
G.6 Using Multiplexers .......................................................................................G-13
Software Manual
Appendix G: FSC Multiplexers i
FIGURES
Figure G-1 Output multiplexer timing ........................................................................................... G-4

Figure G-2 Input multiplexer timing .............................................................................................. G-6
Figure G-3 Multiplexer attributes .................................................................................................. G-9
Figure G-4 Allocation of multiplexed I/O to hardware I/O........................................................... G-12
Figure G-5 Multiplexers and 7-segment displays ....................................................................... G-13
Figure G-6 Multiplexed register read-out.................................................................................... G-14
TABLES
Table G-1 Attributes of output multiplexer................................................................................... G-3

Table G-2 Attributes of input multiplexer..................................................................................... G-5
Software Manual
ii Appendix G: FSC Multiplexers
Appendix G – FSC Multiplexers
G.1 Introduction
Multiplexers and The FSC software supports multiplexers in order to reduce the
the FSC system number of input and output channels to and from the FSC system.
The FSC system does not use hardware multiplexers. Instead, the
principle of a multiplexer is simulated by the FSC software.
Each multiplexer (de)multiplexes the register data of a number of
binary input/output variables.
The maximum number of multiplexers that can be configured is 16.
Terminology for
input multiplexers The following terminology is important for input multiplexers
Data hold time The time in which the data stabilizes on the multiplexer data bus.
Debounce data Method to verify that the multiplexer data is stable. The data on the
data bus is read twice. If two consecutive samples on the input data
bus of the multiplexer return the same data result, the data is stable.
Whether this method should be used can be configured by the user.
Multiplexer data The status of the multiplexer data specifies if the data is either
bus status represented normally or inverted. If the status is inverted, the data is
inverted after it has been read from the multiplexer data bus.
Sample Data of a binary input is read in parts. One such part is a sample.
Scan time The time in which all binary inputs of a multiplexer are read.
Selection outputs The status of the selection outputs determines which sample of the
data will be read. Only one of the selection outputs can be active at
any given time.
Selection output Selection of the sample can be either active high or active low.
active status On = active high, Off = active low.
Selection output The time which the selection output should be active before the data
active time of the multiplexer bus is valid.
Software Manual
Appendix G: FSC Multiplexers G-1
Terminology for
output multiplexers The following terminology is important for output multiplexers:
Data hold time The time during which the data on the multiplexer data bus must stay
active after the selection output is deactivated.
Data setup time The time during which the data on the multiplexer bus has the correct
data status before the selection output will be activated.
Multiplexer data The status of the multiplexer data specifies if the data is either
bus status represented normally or inverted. If the status is inverted, the data is
inverted before it is written on the multiplexer data bus.
Sample Data of a binary output is written in parts. One such part is a sample.
Scan time The time in which all binary outputs of a multiplexer are written.
Selection outputs The status of the selection outputs determines which sample of the
data will be written. Only one of the selection outputs can be active at
any given time.
Selection output Selection of the sample can be either active high or active low.
active status On = active high, Off = active low.
Selection output The time during which the selection output must be active.
active time
Software Manual
G-2 Appendix G: FSC Multiplexers
G.2 Output Multiplexers
Application Output multiplexers may, for example, be used to provide a

numerical value at a seven-segment display.
Attributes Table G-1 below lists the attributes of an output multiplexer:
Table G-1 Attributes of output multiplexer

Attribute Remarks
Data hold time This must be between 1 ms and 100 ms.
Data setup time This must be between 0 ms and 100 ms.
Multiplexer data bus status
Number of output multiplexer This is the number of channels used to

channels write the multiplexed data of all connected
binary outputs.
Scan time This must be between 100 ms and

60,000 ms (= 1 minute).
Selection output active time This must be between 1 ms and 100 ms.
Selection output active status
Timing calculation The calculation of the output multiplexer timing concerns all output
multiplexers.
The compiler calculates a worst case timing that will be used by the
FSC system software for every output multiplexer. Worst case timing
calculation means:
• use of the multiplexer with the lowest scan time.
• use of the multiplexer with the highest data setup time.
• use of the multiplexer with the highest selection output active time.
• use of the multiplexer with the highest data hold time, and
• use of the multiplexer that needs the highest number of samples.
The time required to scan all binary outputs connected to every

multiplexer configured cannot exceed the scan time.
Software Manual
Calculation The following algorithm is used for calculating the time to scan all
algorithm mentioned outputs:
• Sample time =
Data setup time + Selection output active time + Data hold time.
• Number of samples required for a binary output =
Number of channels of the binary output divided by the number of
channels per sample of the output multiplexer it is assigned to,
rounded off to the next whole value. As a formula:
Ch Mult.O − 1
Ch O.Mux + 1
• The total number of samples required to scan every binary

output of an output multiplexer is determined by adding the
number of samples of every connected binary output.
• The total time to scan =
Total number of samples ∗ sample time.
If the total time to scan is larger than the lowest scan time, the FSC
system will not be able to scan the output multiplexers within the
required time. In that case, one of the calculation parameters needs to
be adjusted.
Figure G-1 shows a diagram of the output multiplexer timing.
Data
Sel.
Selection output
active time
Setup time Data hold

time
< Application time
< Cycle time
Figure G-1 Output multiplexer timing
Software Manual
G.3 Input Multiplexers
Application Input multiplexers may, for example, be used to read a number of

thumbwheel switches that constitute a multiple-digit numerical value.
Attributes Table G-2 below lists the attributes of an input multiplexer:
Table G-2 Attributes of input multiplexer

Attribute Remarks
Data hold time This must be between 0 ms and 100 ms.
Multiplexer data bus status
Number of input multiplexer This is the number of channels used to

channels read the multiplexed data of all connected
binary inputs.
Scan time The maximum value is 60,000 ms

(= 1 minute). The minimum time is at least
be the application cycle time.
Selection output active status
Selection output active time This must be between 2 and 100 ms.
The minimum value depends on the delay
time of the inputs of the input module that
is used for the multiplexer channels. The
minimum value is at least twice the delay
time of the inputs.
Timing calculation The calculation of the input multiplexer timing concerns all input
multiplexers.
The compiler calculates a worst case timing that will be used by the
FSC system software for every input multiplexer. Worst case timing
calculation means:
• use of the multiplexer with the lowest scan time.
• use of the multiplexer with the highest selection output active time.
• use of the multiplexer with the highest data hold time, and
• use of the multiplexer that needs the highest number of samples.
The time required to scan all binary inputs connected to every

multiplexer configured cannot exceed the scan time.
Software Manual
Calculation The following algorithm is used for calculating the time to scan all
algorithm mentioned inputs:
• Sample time =
Selection output active time + Data hold time.
• Number of samples required for a binary input =
Number of channels of the binary input divided by the number of
channels per sample of the input multiplexer it is assigned to,
rounded off to the next whole value. As a formula:
Ch Mult.I − 1
Ch I.Mux + 1
• The total number of samples required to scan every binary

input of an input multiplexer is determined by adding the number
of samples of every connected binary input.
• The total time to scan =
Total number of samples ∗ sample time.
If the total time to scan is larger than the lowest scan time, the FSC
system will not be able to scan the input multiplexers within the
required time. In that case, one of the calculation parameters needs to
be adjusted.
Figure G-2 shows a diagram of the input multiplexer timing.
Data
Sel.
Selection active Data hold

time time
< Application time
< Cycle time
Figure G-2 Input multiplexer timing
Software Manual
G.4 Multiple I/O That Uses Multiplexers
Multiple I/O Binary input/output variables that use multiplexers to exchange data
are called multiplexed I/O. They do not need the 'normal' number of
channels that an ordinary binary input/output uses.
It, of course, uses the channels of the multiplexer to exchange data.
The data is exchanged in a number of samples (see 'Timing
calculation' in subsections G.2 and G.3). The application controls the
sample that is read/written. It uses selection outputs to select the
sample. Each sample has its own selection line.
Note:
Both binary inputs (BIs) and binary outputs (BOs) whose data is
exchanged via a multiplexer are allocated to output channels
(the selection lines)!
Software Manual
G.5 Configuring Multiplexers
Configuration The configuration of multiplexers consists of six basic steps:

1. Adding multiplexers to the application,
2. Setting the multiplexer attributes,
3. Adding multiplexed I/O to the application,
4. Linking the multiplexed I/O to multiplexers,
5. Specifying the number of channels of the multiplexed I/O
variable, and
6. Allocating the multiplexed I/O to actual hardware inputs and
outputs.
G.5.1 Multiplexers
Adding To add multiplexers to the application, do the following:

2. Choose Signal specs from the main menu.
3. Choose Add from the submenu.
4. In the V field, type 'XI' (for a multiplexer input) or 'XO' (for a
multiplexer output). After you have entered a tag number, the
variable location (in the 'Loc' column) will automatically be set to
'MUX'.
Note:
Up to 16 multiplexers can be configured.
Setting attributes To set the attributes of the multiplexers, do the following:

3. In the Variable type field, type 'XI' (for a multiplexer input) or
'XO' (for a multiplexer output).
Software Manual
4. In the Tag number field, type the tag number of the multiplexer
you wish to edit, or press <?> to choose from a list of the
available tag numbers.
A screen as shown in Figure G-3 will appear which allows you to
edit the multiplexer's attributes.
Figure G-3 Multiplexer attributes
Software Manual
G.5.2 Multiplexed I/O
BI and BO After you have specified the attributes of the multiplexers that you
variables will be using, you need to configure all multiplexed I/O. These are BI
and BO variables with special location 'MUX'.
Adding First, you must add multiplexed I/O to the application:

2. Choose Signal specs from the main menu.
3. Choose Add from the submenu.
4. In the V field, type 'BI' (for multiplexed input) or 'BO' (for
multiplexed output). Make sure that enter a tag number and that
you set the 'Loc' column to 'MUX'.
Repeat this step for all BI and BO variables that you want to add.
Linking to
multiplexers Next, you need to link the multiplexed I/O to multiplexers:
you wish to edit, or press <?> to choose from a list of available
tag numbers.
5. In the MUX tag number field, specify the multiplexer you wish
the multiplexed input or output to be linked to.
Multiplexed inputs can only be linked to input multiplexers, and
multiplexed outputs to output multiplexers.
Multiplexed I/O can be linked to a multiplexer as long as all

connected multiplexed I/O can be scanned within the configured scan
time of the multiplexer. For details on timing calculation refer to
subsection G.2 (output multiplexers) or G.3 (input multiplexers).
Software Manual
Number of You also need to specify the number of channels of the multiplexed
channels I/O variable. This is done in the multiplexer attributes screen (see
Figure G-3):
you wish to edit, or press <?> to choose from a list of the
available tag numbers.
5. In the Number of input bits (or Number of output bits) field,
type the required number of the channels.
After you have specified the number of channels, the application

program calculates the number of samples required to exchange the
variable data. A selection output must be configured for each sample.
You must allocate the selection outputs for the variable. For example:
XI: 4 channels.
BI (with loc. 'MUX'): 20 channels.
The number of samples is 20/4 = 5. This is also the number of
selection outputs that must be allocated.
Allocation The final step is to allocate the multiplexed I/O to actual hardware
inputs and outputs. This is done in the multiplexer attributes screen.
To arrive at the screen as shown in Figure G-4, press <Enter> until the
last line is cleared.
Software Manual
Figure G-4 Allocation of multiplexed I/O to hardware I/O
Configuration XO: scan time = 1000 ms

example data setup time = 10 ms
data hold time = 15 ms
selection output active time = 25 ms
number of channels = 4
BO 1: 20 channels (= 20/4 = 5 samples)

Sample time = 10 + 15 + 25 = 50 ms
Total number of samples = 5 + 8 + 4 = 17.
The total scanning time needed by the FSC software is
17 ∗ 50 = 850 ms.
It is possible to configure an additional multiplexed BO using a

maximum of 12 channels (which will lead to a scanning time of
1000 ms). It is not possible to configure a multiplexed BO with more
than 12 channels.
Software Manual
G.6 Using Multiplexers
Output multiplexers When it comes to channel usage, multiplexed I/O can be very
efficient to control a 7-segment display.
If, for example, the application controls a 5-digit 7-segment display,
the application would normally need 5 ∗ 4 = 20 channels if no
multiplexer was used. However, if a multiplexer is used, only 9
channels are needed (see Figure G-5): 5 channels (20/4) for the
selection outputs of the BO, and 4 channels of the XO. The BO
contains the segment information (bits 0-3 = segment 1, etc.).
enable
FSC Non-FSC d0
d1
d2
OUTPUTS
d3
SELECT
BO
Location
'MUX'
BO
CHAN
XO
XO
Figure G-5 Multiplexers and 7-segment displays
Software Manual
Input multiplexers When it comes to channel usage, multiplexed I/O can be very
efficient to monitor four hardware registers (8-bit).
The application would normally need 8 ∗ 4 = 32 channels if no
multiplexer was used. However, if a multiplexer is used, only 12
channels are needed (see Figure G-6): 1 (8/8) for each selection output
of the BI, and 8 channels of the XI. Each BI contains the value of one
of the hardware registers.
FSC Non-FSC
BI 1 Loc MUX
Selection output
BI 2 Loc MUX
Selection output
BI 3 Loc MUX
Selection output
BI 4 Loc MUX
Selection output
O S0
d0
U S1
d1 S2
T
Channels
d2 S3
d3 P
XI
XI d4 U Reg 1
d5 T
d6 D0-D7 Reg 2
d7 M Reg 3
U
X Reg 4
Figure G-6 Multiplexed register read-out
For another application example refer to the data sheet of the

10207/1/1 output module in the FSC Hardware Manual.
Software Manual
Fail Safe Control
Appendix H:
Simulation Mode
Release 531
Revision 01 (03/2001)
Release 531
Revision 01 (03/2001)

B.V.
TABLE OF CONTENTS
Appendix H: Simulation Mode
H.1 Introduction ....................................................................................................H-1
H.2 Using Simulation Mode..................................................................................H-2

H.2.1 Introduction.......................................................................................................................H-2
H.2.2 Specifying the Simulation Unit .........................................................................................H-2
H.2.3 Defining the Communication Channel Assignment..........................................................H-5
H.2.4 Translating the Simulated Application..............................................................................H-6
H.2.5 Loading the Simulated Application into the Simulation Unit ............................................H-6
H.2.6 Using the On-Line Environment to Simulate the Application ...........................................H-7
H.2.7 Considerations .................................................................................................................H-7
H.3 Hardware Layout of Simulation/Training Units ............................................H-8

H.3.1 Single-Rack FSC Unit 23260/4/1 (EPM, ECM, Flash Memory) .......................................H-8
H.3.2 Single-Rack FSC Unit 23260/4/2 (EPM, ECM, Flash Memory, FSC-SMM) ..................H-10
H.3.3 Single-Rack FSC Unit 23260/4/3 (EPM, ECM, Flash Memory, PlantScape) ................H-12
H.3.4 Single FSC Unit 23250/4/1 (EPM, ECM, Flash Memory) ..............................................H-14
H.3.5 Single FSC Unit 23250/4/2 (ECM, EPM, Flash Memory, FSC-SMM) ...........................H-16
H.3.7 Redundant FSC Unit 23270/4/1 (EPM, ECM, Flash Memory).......................................H-20
H.3.9 Redundant FSC Unit 23270/4/3 (EPM, ECM, Flash Memory, PlantScape) ..................H-24
H.3.10 Single-Rack FSC Unit 23260/3/1 (Flash Memory).........................................................H-26
H.3.11 Single-Rack FSC Unit 23260/3/2 (Flash Memory, FSC-SMM) ......................................H-27
H.3.12 Single-Rack FSC Unit 23260/3/3 (Flash Memory, PlantScape) ....................................H-29
H.3.13 Single FSC Unit 23250/3/1 (Flash Memory) ..................................................................H-31
H.3.14 Single FSC Unit 23250/3/2 (Flash Memory, FSC-SMM) ...............................................H-33
H.3.16 Redundant FSC Unit 23270/3/1 (Flash Memory)...........................................................H-37
H.3.18 Redundant FSC Unit 23270/3/3 (Flash Memory, PlantScape) ......................................H-41
H.3.19 Single-Rack FSC Unit 23260/1/1 (EPROMs/RAM)........................................................H-43
H.3.20 Single-Rack FSC Unit 23260/2/1 (EPROMs/RAM, FSC-SMM).....................................H-44
H.3.21 Single FSC Unit 23250/1/1 (EPROMs/RAM) .................................................................H-45
H.3.22 Single FSC Unit 23250/2/1 (EPROMs/RAM, FSC-SMM) ..............................................H-47
H.3.23 Redundant FSC Unit 23251/1/1 (EPROMs/RAM) .........................................................H-49
H.3.24 Redundant FSC Unit 23270/2/1 (EPROMs/RAM, FSC-SMM) ......................................H-51
Software Manual
Appendix H: Simulation Mode i
FIGURES
Figure H-1 Configuring simulation mode...................................................................................... H-3

Figure H-2 Defining simulation mode........................................................................................... H-4
TABLES
Table H-1 Simulation/training hardware units ............................................................................. H-4

Table H-2 Hardware layout of 23260/4/1 FSC unit..................................................................... H-8
Table H-3 System I/O allocation of 23260/4/1 FSC unit ............................................................. H-9
Table H-4 Hardware layout of 23260/4/2 FSC unit................................................................... H-10
Table H-5 System I/O allocation of 23260/4/2 FSC unit ........................................................... H-11
Software Manual
ii Appendix H: Simulation Mode
TABLES (continued)
Table H-41 System I/O allocation of 23260/2/1 FSC unit ............................................................H-44

Table H-42 Hardware layout of 23250/1/1 FSC unit....................................................................H-45
Software Manual
Appendix H: Simulation Mode iii
Software Manual
iv Appendix H: Simulation Mode
Appendix H – Simulation Mode
H.1 Introduction
Simulation The FSC simulation option allows any FSC application to be loaded
into the standard FSC simulation/training units. In simulation mode,
the FSC control processor executes the application program using the
serial interface with the FSC user station as its field interface. The
actual defined Central Part hardware is ignored and "mapped" to the
hardware of the simulation/training units.
Input values are applied by the user via the FSC Navigator software,
using the input signal force feature (see subsection 12.12 of this
manual). The output values can be monitored on screen using the
on-line environment of FSC Navigator (see Section 12 of this
manual).
In combination with the standard "live" FLD viewing feature of FSC

Navigator (see subsection 12.10 of this manual), the simulation option
provides an excellent means for design engineers to validate the FSC
application program prior to initial installation and to verify
modifications before an on-line upgrade. The interfaces with TPS
(FSC-SMM) and PlantScape are also supported in simulation mode,
which allows an integrated validation of the entire safety application.
Note:
Before you modify an application to be used in simulation
mode, make sure that you back up the application files. It is
strongly recommended that you only use "copies" of the original
application for simulation purposes.
Software Manual
Appendix H: Simulation Mode H-1
H.2 Using Simulation Mode
H.2.1 Introduction
Using To use simulation mode successfully, the following steps need to be

simulation mode performed:
1. Specification of the simulation/training unit type.
2. Definition of the communication channel assignment.
3. Translation of the simulated application.
4. Loading of the simulated application program into the
simulation/training unit.
5. Simulation of the application using the on-line environment
features of FSC Navigator.
Each of these items is discussed in more detail in the following

subsections.
H.2.2 Specifying the Simulation Unit
Specifying the The first step that you need to do to use simulation mode successfully
simulation unit is to specify the simulation/training unit that should be used in
conjunction with your simulated application:
1. In FSC Navigator, choose the System Configuration option
(e.g. by clicking on the I/O button in the button bar).
2. Choose the Install option.
3. Choose the Configuration option. The screen as shown in Figure
H-1 will appear.
4. Move the cursor to the Simulation mode field, and press <E> to
edit. The screen as shown in Figure H-2 will appear.
Here you can specify that you want your application to run in
simulation mode. You can also specify which simulation hardware
should be used as well as the communication channel assignment.
Software Manual
H-2 Appendix H: Simulation Mode
Figure H-1 Configuring simulation mode
Simulation mode The Simulation mode field in Figure H-2 allows you to specify the
simulation hardware unit that should be used in conjunction with
your simulated application. Use <Space> to toggle between the
available options or press <?> to select from a list. The default is
'None' (i.e. no simulation). Table H-1 below provides an overview of
the available simulation hardware units, with their main
characteristics.
Notes:
1. Subsection H.3 on page H-8 provides details on the
hardware layout of the various simulation/training units.
2. If your simulation unit does not have a model specification
(or one that is not included in the selection list), inspect your
unit's hardware configuration to identify which unit type
you should use. For details refer to subsection H.3.
3. Make sure that the simulation mode you select is compatible
with the application's memory type (see Figure H-1 and
Table H-1).
4. Redundant applications can be simulated in single (i.e. non-
redundant) units, and single applications in redundant units.
Software Manual
Figure H-2 Defining simulation mode
Table H-1 Simulation/training hardware units

Simulation Memory type CP module Configuration FSC-SMM PlantScape Software
23260/4/1 FLASH QPM+ECM Single-rack – – ≥ R530
23260/4/2 FLASH QPM+ECM Single-rack = – ≥ R530
23260/4/3 FLASH QPM+ECM Single-rack – = ≥ R530
23250/4/1 FLASH QPM+ECM Single – – ≥ R530
23250/4/2 FLASH QPM+ECM Single = – ≥ R530
23250/4/3 FLASH QPM+ECM Single – = ≥ R530
23270/4/1 FLASH QPM+ECM Redundant – – ≥ R530
23270/4/2 FLASH QPM+ECM Redundant = – ≥ R530
23270/4/3 FLASH QPM+ECM Redundant – = ≥ R530
23260/3/1 FLASH CPU+COM Single-rack – – ≥ R510
23260/3/2 FLASH CPU+COM Single-rack = – ≥ R510
23260/3/3 FLASH CPU+COM Single-rack – = ≥ R520
23250/3/1 FLASH CPU+COM Single – – ≥ R510
23250/3/2 FLASH CPU+COM Single = – ≥ R510
23250/3/3 FLASH CPU+COM Single – = ≥ R520
23270/3/1 FLASH CPU+COM Redundant – – ≥ R510
Software Manual
Table H-1 Simulation/training hardware units (continued)
Simulation Memory type CP module Configuration FSC-SMM PlantScape Software
23270/3/2 FLASH CPU+COM Redundant = – ≥ R510
23270/3/3 FLASH CPU+COM Redundant – = ≥ R520
23260/1/1 RAM CPU+COM Single-rack – – ≥ R3.00
23260/2/1 RAM CPU+COM Single-rack = – ≥ R510
23250/1/1 RAM CPU+COM Single – – ≥ R3.00
23250/2/1 RAM CPU+COM Single = – ≥ R510
23251/1/1 RAM CPU+COM Redundant – – ≥ R3.00
23270/2/1 RAM CPU+COM Redundant = – ≥ R510
* QPM = 10020/1/1 Quad Processor Module,
ECM = 10024/x/x Enhanced Communication Module
H.2.3 Defining the Communication Channel Assignment
Channel The bottom section of the screen as shown in Figure H-2 allows you
assignment to define the communication channel assignment that will be used in
simulation mode. You can specify which communication channels of
your application are mapped to the simulated channels.
The left columns show all available communication channels in the
selected simulation hardware unit. The channel configuration shown
depends on the selected simulation/training unit. The right columns
show which communication channels of your application have been
assigned to the simulated channels. For ease of verification, the
communication protocols are shown as well.
Mapping channels You can specify which of the actual communication channels in your
application should appear in the simulation/training unit. This allows
you to use the application itself to test whether the communication for
any particular channel is working correctly.
You map a communication channel to a simulated channel by
specifying its location in the FSC system (CP number, module
position, channel, e.g. 1,1B). Use <Space> to toggle between the
available channels or press <?> to select from a list. You can only
select channels in your application whose interface hardware is
identical to that of the simulation hardware. This means that if the
simulation hardware contains a particular interface, you can only
select all communication channels of your application that contain the
same interface.
Software Manual
For each user-configurable channel, you can also choose 'None'. This
means that no mapping is done. This option is useful if you do not
want to test the communication, but the behavior of the application as
defined in the FLDs. It will cause the simulated system to use the
Development System protocol, providing this is allowed on the
available hardware interface. (For the UCN interfaces, for example,
the Development System protocol is not supported, and therefore it
cannot be selected.)
For all redundant simulation modes, the internal FSC-FSC

communication channel (channel 1A) is not user-configurable. This
means that the Channel field will always be set to 'None' and cannot
be modified.
H.2.4 Translating the Simulated Application
Translation After you have defined the simulation parameters, the simulated
application needs to be translated into code that can be used by the
FSC processor(s) in the simulation/training unit.
For details on translating an application refer to Section 8 of this
Note:
Please note the considerations as laid down in subsection H.2.7
on page H-7.
H.2.5 Loading the Simulated Application into the Simulation Unit
Loading After you have translated the simulated application, you need to
transfer it to the simulation/training unit. This can either be done by
downloading it to (flash) memory or by programming EPROMs,
depending on the simulation unit. For details on loading an
application refer to Section 10 of this manual ("Loading Software").
Note:
Please note the considerations as laid down in subsection H.2.7
on page H-7.
Software Manual
H.2.6 Using the On-Line Environment to Simulate the Application
Simulation After you have successfully loaded the simulated application into the
simulation unit, you can use the on-line features of FSC Navigator to
check the application's behavior in a non-operational environment.
You can apply any value to the inputs ("forcing") to see what the
output results are. This allows you to check whether the application
behaves in accordance with design specifications. For details on input
signal forcing refer to subsection 12.13 of this manual.
The output results can be viewed on-line in various ways, including
"live" FLD displays and variable status screens. For details refer to
H.2.7 Considerations
Considerations Please note the following considerations that are important for
simulation mode:
1. Always back up your application before modifying it to be used in
simulation mode. It is strongly recommended that you only use
"copies" of the original application for simulation purposes.
2. The system number will always be set to '1' in simulation mode.
This means that the Modbus address will always be '4'.
3. Outputs cannot be forced.
4. For applications that are simulated in a single FSC unit
(i.e. 23260/x/x and 23250/x/x), the version counter will be set to
'1', and will remain to be '1' as long as the application is translated
in simulation mode. As soon as simulation mode is deactivated,
the version counter will return to its original value. For example:
4, 5, 1, 1, 1, 5, 6 (italics = simulation mode).
5. For applications that are simulated in a redundant FSC unit
(i.e. 23270/x/x and 23251/x/x), the version counter will not be set
to '1', but will keep its original value. Each time the application is
translated (either in simulation mode or "normal" mode), the
version counter is incremented by one. For example:
4, 5, 6, 7, 8, 9, 10 (italics = simulation mode).
Software Manual
H.3 Hardware Layout of Simulation/Training Units
Hardware layout This section describes the hardware layout of the supported
simulation/training units.
Note:
If your simulation unit does not have a model specification (or
one that is not included in the selection list), inspect your unit's
hardware configuration to identify which unit type you should
use. The 'Mandatory' fields in the tables below indicate which
modules must be present in your FSC unit. The others are
optional.
H.3.1 Single-Rack FSC Unit 23260/4/1 (QPM, ECM, Flash Memory)
23260/4/1 unit Table H-2 below shows the hardware layout of the 23260/4/1 FSC
unit (single-rack configuration with QPM, ECM, and flash memory).
Table H-2 Hardware layout of 23260/4/1 FSC unit

23260/4/1 — Single-rack configuration with QPM, ECM, and flash memory
Central Part
Rack Pos. Module type Description Mandatory
1 1 10101/2/1 Fail-safe digital input module (24Vdc, 16 channels) =
1 2 16226/2/1 Simulation module of 12 DI's of a 10101/2/1 module =
1 3 10105/2/1 Fail-safe analog input module (24Vdc, 16 channels) –
1 4 16227/2/2 Simulation module of 4 AI's of a 10105/2/1 module –
1 5 10205/2/1 Fail-safe analog output module (0(4)-20mA, 2 ch.) –
1 6 10201/2/1 Fail-safe digital output module (24Vdc, 0.55A, 8 ch.) –
1 7 10206/2/1 Digital output module (24Vdc, 0.55A, 12 channels) –
1 10 16176/1/1 Quadruple fuse module =
1 12 10020/1/1 Quad Processor Module (QPM) =
1 14,15 10024/I/F Enhanced communication module (ECM) =
1 16 10007/1/1 Single bus driver (SBD) =
1 17 10005/1/1 Watchdog module (WD) =
1 18,19 10006/2/1 Diagnostic and battery module (DBM) =
1 20,21 – Power Supply Unit 230-115 Vac → 24 Vdc + 5 Vdc =
Software Manual
System I/O Table H-3 below shows the system I/O allocation of the 23260/4/1
allocation FSC unit (single-rack configuration with QPM, ECM, and flash
memory).
Table H-3 System I/O allocation of 23260/4/1 FSC unit

23260/4/1 — Single-rack configuration with QPM, ECM, and flash memory
System I/O allocations
Rack Position Channel System variable Mandatory
1 1 12 System reset (RESET) =

1 1 11 Force enable (ENABLE) –
Software Manual
H.3.2 Single-Rack FSC Unit 23260/4/2 (QPM, ECM, Flash Memory,
FSC-SMM)
unit (single-rack configuration with QPM, ECM, flash memory, and
FSC-SMM simulation).

23260/4/2 — Single-rack configuration with QPM, ECM, flash memory, and FSC-SMM simulation
Central Part


1 11,12 10018/2/U FSC-SMM communication module =
Software Manual
allocation FSC unit (single-rack configuration with QPM, ECM, flash memory,
and FSC-SMM simulation).

23260/4/2 — Single-rack configuration with QPM, ECM, flash memory, and
FSC-SMM simulation

Software Manual
H.3.3 Single-Rack FSC Unit 23260/4/3 (QPM, ECM, Flash Memory,
PlantScape)
unit (single-rack configuration with QPM, ECM, flash memory, and
PlantScape interface simulation).

23260/4/3 — Single-rack configuration with QPM, ECM, flash memory, and PlantScape interface
simulation
Central Part


1 11,12 10018/E/1 PlantScape communication module =
Software Manual
allocation FSC unit (single-rack configuration with QPM, ECM, flash memory,
and PlantScape interface simulation).

23260/4/3 — Single-rack configuration with QPM, ECM, flash memory, and
PlantScape interface simulation

Software Manual
H.3.4 Single FSC Unit 23250/4/1 (QPM, ECM, Flash Memory)
unit (single configuration with QPM, ECM, and flash memory).

23250/4/1 — Single configuration with QPM, ECM, and flash memory
Central Part
1 4 10311/2/1 Dual key-switch module =

1 17 10001/R/1 Vertical bus driver (VBD) =
1 20,21 10300/1/1 24Vdc to 5Vdc / 12A converter =
I/O rack

2 2 16226/2/1 Simulation module of 12 DI's of a 10101/2/1 module –
2 7 10106/2/1 Fail-safe line-monitored digital input module with earth –

fault monitor (16 channels)
2 8 16226/2/2 Simulation module of 12 LM DI's of a 10106/2/1 mod. –
2 9 10208/2/1 Relay output module (dry contacts, 10 channels) –
2 21 10100/2/1 Horizontal bus driver (HBD) =
Software Manual
allocation FSC unit (single configuration with QPM, ECM, and flash memory).

23250/4/1 — Single configuration with QPM, ECM, and flash memory

Software Manual
H.3.5 Single FSC Unit 23250/4/2 (ECM, QPM, Flash Memory,
FSC-SMM)
unit (single configuration with ECM, QPM, flash memory, and

23250/4/2 — Single configuration with QPM, ECM, flash memory, and FSC-SMM simulation
Central Part

I/O rack


Software Manual
allocation FSC unit (single configuration with QPM, ECM, and flash memory).

23250/4/2 — Single configuration with QPM, ECM, flash memory, and FSC-SMM
simulation

Software Manual
H.3.6 Single FSC Unit 23250/4/3 (Flash Memory, PlantScape)
unit (single configuration with QPM, ECM, flash memory, and

23250/4/3 — Single configuration with QPM, ECM, flash memory, and PlantScape interface
simulation
Central Part

1 7 100201/1 Quad Processor Module (QPM) =
I/O rack

Software Manual
allocation FSC unit (single configuration with QPM, ECM, flash memory, and

23250/4/3 — Single configuration with QPM, ECM, flash memory, and

Software Manual
H.3.7 Redundant FSC Unit 23270/4/1 (QPM, ECM, Flash Memory)
unit (redundant configuration with QPM, ECM, and flash memory).

23270/4/1 — Redundant configuration with QPM, ECM, and flash memory
Central Part 1

1 14,15 10024/H/I Enhanced communication module (ECM) =
Central Part 2

2 14,15 10024/H/F Enhanced communication module (ECM) =
I/O rack

3 1,2 10101/2/1 Fail-safe digital input module (24Vdc, 16 channels) =
3 5,6 10105/2/1 Fail-safe analog input module (24Vdc, 16 channels) –
3 9,10 10106/2/1 Fail-safe line-monitored digital input module with earth –
3 13,14 10216/2/1 Fail-safe loop-monitored output mod. (24Vdc, 1A, 4 ch) –
3 17,18 10201/2/1 Fail-safe digital output module (24Vdc, 0.55A, 8 ch.) =
3 20,21 10100/2/1 Horizontal bus driver (HBD) =
Software Manual
allocation FSC unit (redundant configuration with QPM, ECM, and flash
memory).

23270/4/1 — Redundant configuration with QPM, ECM, and flash memory

3 1 1 COM-I/O =
3 17 1 COM-I/O =
Software Manual
H.3.8 Redundant FSC Unit 23270/4/2 (Flash Memory, FSC-SMM)
unit (redundant configuration with QPM, ECM, flash memory, and

23270/4/2 — Redundant configuration with QPM, ECM, flash memory, and FSC-SMM simulation
Central Part 1
Central Part 2
I/O rack
3 13,14 10216/2/1 Fail-safe loop-monitored output mod. (24Vdc, 1A, 4 c.) –
Software Manual
allocation FSC unit (redundant configuration with QPM, ECM, flash memory,
and FSC-SMM simulation).

23270/4/2 — Redundant configuration with QPM, ECM, flash memory, and
FSC-SMM simulation

3 1 1 COM-I/O =
3 17 1 COM-I/O =
Software Manual
H.3.9 Redundant FSC Unit 23270/4/3 (QPM, ECM, Flash Memory,
PlantScape)
unit (redundant configuration with QPM, ECM, flash memory, and

23270/4/3 — Redundant configuration with QPM, ECM, flash memory, and PlantScape interface
simulation
Central Part 1

Central Part 2

Software Manual
Table H-18 Hardware layout of 23270/4/3 FSC unit (continued)
I/O rack



allocation FSC unit (redundant configuration with QPM, ECM, flash memory,
and PlantScape interface simulation).

23270/4/3 — Redundant configuration with QPM, ECM, flash memory, and

3 1 1 COM-I/O =
3 17 1 COM-I/O =
Software Manual
H.3.10 Single-Rack FSC Unit 23260/3/1 (Flash Memory)
unit (single-rack configuration with flash memory).

23260/3/1 — Single-rack configuration with flash memory
Central Part
1 12 10012/1/2 Central processor unit (CPU) =
1 14,15 10014/I/F Communication module (COM) =
allocation FSC unit (single-rack configuration with flash memory).

23260/3/1 — Single-rack configuration with flash memory

Software Manual
H.3.11 Single-Rack FSC Unit 23260/3/2 (Flash Memory, FSC-SMM)
unit (single-rack configuration with flash memory and FSC-SMM
simulation).

23260/3/2 — Single-rack configuration with flash memory and FSC-SMM simulation
Central Part


Software Manual
allocation FSC unit (single-rack configuration with flash memory and

23260/3/2 — Single-rack configuration with flash memory and
FSC-SMM simulation

Software Manual
H.3.12 Single-Rack FSC Unit 23260/3/3 (Flash Memory, PlantScape)
unit (single-rack configuration with flash memory and PlantScape
interface simulation).

23260/3/3 — Single-rack configuration with flash memory and PlantScape interface simulation
Central Part


Software Manual
allocation FSC unit (single-rack configuration with flash memory and

23260/3/3 — Single-rack configuration with flash memory and

Software Manual
H.3.13 Single FSC Unit 23250/3/1 (Flash Memory)
unit (single configuration with flash memory).

23250/3/1 — Single configuration with flash memory
Central Part

I/O rack


Software Manual
allocation FSC unit (single configuration with flash memory).

23250/3/1 — Single configuration with flash memory

Software Manual
H.3.14 Single FSC Unit 23250/3/2 (Flash Memory, FSC-SMM)
unit (single configuration with flash memory and FSC-SMM
simulation).

23250/3/2 — Single configuration with flash memory and FSC-SMM simulation
Central Part

I/O rack


Software Manual
allocation FSC unit (single configuration with flash memory).

23250/3/2 — Single configuration with flash memory and FSC-SMM
simulation

Software Manual
H.3.15 Single FSC Unit 23250/3/3 (Flash Memory, PlantScape)
unit (single configuration with flash memory and PlantScape

23250/3/3 — Single configuration with flash memory and PlantScape interface simulation
Central Part

I/O rack

Software Manual
allocation FSC unit (single configuration with flash memory and PlantScape

23250/3/3 — Single configuration with flash memory and

Software Manual
H.3.16 Redundant FSC Unit 23270/3/1 (Flash Memory)
unit (redundant configuration with flash memory).

23270/3/1 — Redundant configuration with flash memory
Central Part 1

1 14,15 10014/H/I Communication module (COM) =
Central Part 2

2 14,15 10014/H/F Communication module (COM) =
I/O rack

3 13,14 10216/2/1 Fail-safe loop-monitored output mod. (24Vdc, 1A, 4 ch) –
Software Manual
allocation FSC unit (redundant configuration with flash memory).

23270/3/1 — Redundant configuration with flash memory

3 1 1 COM-I/O =
3 17 1 COM-I/O =
Software Manual
H.3.17 Redundant FSC Unit 23270/3/2 (Flash Memory, FSC-SMM)
unit (redundant configuration with flash memory and FSC-SMM
simulation).

23270/3/2 — Redundant configuration with flash memory and FSC-SMM simulation
Central Part 1
Central Part 2
I/O rack
Software Manual
allocation FSC unit (redundant configuration with flash memory and FSC-SMM
simulation).

23270/3/2 — Redundant configuration with flash memory and
FSC-SMM simulation

3 1 1 COM-I/O =
3 17 1 COM-I/O =
Software Manual
H.3.18 Redundant FSC Unit 23270/3/3 (Flash Memory, PlantScape)
unit (redundant configuration with flash memory and PlantScape

23270/3/3 — Redundant configuration with flash memory and PlantScape interface simulation
Central Part 1

Central Part 2

Software Manual
Table H-36 Hardware layout of 23270/3/3 FSC unit (continued)
I/O rack



allocation FSC unit (redundant configuration with flash memory and PlantScape

23270/3/3 — Redundant configuration with flash memory and

3 1 1 COM-I/O =
3 17 1 COM-I/O =
Software Manual
H.3.19 Single-Rack FSC Unit 23260/1/1 (EPROMs/RAM)
unit (single-rack configuration with EPROMs/RAM).

23260/1/1 — Single-rack configuration with EPROMs/RAM
Central Part 1

allocation FSC unit (single-rack configuration with EPROMs/RAM).

23260/1/1 — Single-rack configuration with EPROMs/RAM

Software Manual
H.3.20 Single-Rack FSC Unit 23260/2/1 (EPROMs/RAM, FSC-SMM)
unit (single-rack configuration with EPROMs/RAM and FSC-SMM
simulation).

23260/2/1 — Single-rack configuration with EPROMs/RAM and FSC-SMM simulation
Central Part 1


23260/2/1 — Single-rack configuration with EPROMs/RAM and
FSC-SMM simulation

Software Manual
H.3.21 Single FSC Unit 23250/1/1 (EPROMs/RAM)
unit (single configuration with EPROMs/RAM).

23250/1/1 — Single configuration with EPROMs/RAM
Central Part 1

I/O rack

2 9,10 10101/2/1 Fail-safe digital input module (24Vdc, 16 channels) –
2 14,15 10201/2/1 Fail-safe digital output module (24Vdc, 0.55A, 8 ch.) –
Software Manual

23250/1/1 — Single configuration with EPROMs/RAM

Software Manual
H.3.22 Single FSC Unit 23250/2/1 (EPROMs/RAM, FSC-SMM)
unit (single configuration with EPROMs/RAM and FSC-SMM
simulation).

23250/2/1 — Single configuration with EPROMs/RAM and FSC-SMM simulation
Central Part 1

I/O rack

2 9,10 10101/2/1 Fail-safe digital input module (24Vdc, 16 channels) –
2 14,15 10201/2/1 Fail-safe digital output module (24Vdc, 0.55A, 8 ch.) –
Software Manual
allocation FSC unit (single configuration with EPROMs/RAM and FSC-SMM
simulation).

23250/2/1 — Single configuration with EPROMs/RAM and
FSC-SMM simulation

Software Manual
H.3.23 Redundant FSC Unit 23251/1/1 (EPROMs/RAM)
unit (redundant configuration with EPROMs/RAM).

23251/1/1 — Redundant configuration with EPROMs/RAM
Central Parts
Position
Rack CP1 CP2 Module type Description Mandatory
1 2 12 10002/1/2 Central processor unit (CPU) =

1 6 16 10005/1/1 Watchdog module (WD) =
1 7 17 10001/R/1 Vertical bus driver (VBD) =
1 8,9 18,19 10006/2/1 Diagnostic and battery module (DBM) =
1 10,11 20,21 10300/1/1 24Vdc to 5Vdc / 12A converter =
I/O rack
Rack Position Module type Description Mandatory
2 9,10 10101/2/1 Fail-safe digital input module (24Vdc, 16 ch.) =

2 15,16 10201/2/1 Fail-safe dig. outp. mod. (24Vdc, 0.55A, 8ch.) =
Software Manual
simulation).

23251/1/1 — Redundant configuration with EPROMs/RAM
2 9 16 COM-I/O =
2 15 8 COM-I/O =
Software Manual
H.3.24 Redundant FSC Unit 23270/2/1 (EPROMs/RAM, FSC-SMM)
unit (redundant configuration with EPROMs/RAM and FSC-SMM
simulation).

23270/2/1 — Redundant configuration with EPROMs/RAM and FSC-SMM simulation
Central Part 1

Central Part 2

I/O rack

Software Manual
simulation).

23270/2/1 — Redundant configuration with EPROMs/RAM AND
FSC-SMM simulation

3 1 1 COM-I/O =
3 17 1 COM-I/O =
Software Manual

Fail Safe Control - FSC Primer

Uploaded by

Document Information

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

Fail Safe Control - FSC Primer

Uploaded by

Copyright:

Available Formats

© 2000 – Honeywell Safety Management Systems B.V.

While this information is presented in good faith and believed to be accurate,

PlantScape is a trademark of Honeywell International Inc.

Other brands or product names are trademarks of their respective holders.

SECTION 1: FSC PRIMER

SECTION 2: INSTALLATION GUIDE

SECTION 3: USING FSC NAVIGATOR

SECTION 3: USING FSC NAVIGATOR (continued)

SECTION 4: SYSTEM CONFIGURATION

SECTION 4: SYSTEM CONFIGURATION (continued)

SECTION 4: SYSTEM CONFIGURATION (continued)

SECTION 5: EDITING REPORTS AND SER FORMAT

SECTION 5: EDITING REPORTS AND SER FORMAT (continued)

SECTION 6: FUNCTIONAL LOGIC DIAGRAMS

SECTION 6: FUNCTIONAL LOGIC DIAGRAMS (continued)

SECTION 7: PRINTING (continued)

SECTION 8: TRANSLATING AN APPLICATION

SECTION 9: LOG FILES

SECTION 10: LOADING SOFTWARE

SECTION 10: LOADING SOFTWARE (continued)

SECTION 11: VERIFYING AN APPLICATION

SECTION 12: ON-LINE ENVIRONMENT

SECTION 12: ON-LINE ENVIRONMENT (continued)

SECTION 12: ON-LINE ENVIRONMENT (continued)

SECTION 13: SAFETY CHECKER

APPENDIX A: ALARM FUNCTIONS

APPENDIX B: SEQUENCE-OF-EVENT RECORDING

APPENDIX C: SAFETY-RELATED INPUTS WITH NON FAIL-SAFE SENSORS

APPENDIX D: ON-LINE MODIFICATION

APPENDIX D: ON-LINE MODIFICATION (continued)

APPENDIX D: ON-LINE MODIFICATION (continued)

APPENDIX E: PID CONTROLLERS

APPENDIX F: COMMUNICATION (continued)

APPENDIX F: COMMUNICATION (continued)

APPENDIX G: FSC MULTIPLEXERS

APPENDIX H: SIMULATION MODE

FSC Safety Manual R531 FS90-531

FSC Software Manual R531 FS80-531

FSC Hardware Manual FS02-500

FSC Obsolete Modules FS02-501

FSC Service Manual FS99-504

FSCSOE – Basic Version FS50-xxx*

FSCSOE – Network Option FS51-xxx*

FSCSOE – Foxboro I/A Interface Option FS52-xxx*

FSCSOE – Yokogawa CS Interface Option FS53-xxx*

FSCSOE – Ronan Interface Option FS55-xxx*

FSC Safety Manager Installation Guide FS20-500

FSC Safety Manager Implementation Guidelines FS11-500

FSC Safety Manager Control Functions FS09-500

FSC Safety Manager Parameter Reference Dictionary FS09-550

FSC Safety Manager Configuration Forms FS88-500

FSC Safety Manager Service Manual FS13-500

BY E-MAIL: Send an e-mail message to sms-info@honeywell.com

Title of Document: Fail Safe Control Issue Date: 03/2001

Document Number: FS80-531 Writer: HSMS Worldwide Marketing

© 2001 – Honeywell Safety Management Systems B.V.

While this information is presented in good faith and believed to be accurate,

PlantScape is a trademark of Honeywell International Inc.

Other brands or product names are trademarks of their respective holders.

Section 1: FSC Primer

1.1 Introduction .................................................................................................... 1-1

1.2 FSC System Overview.................................................................................... 1-3

1.3 Standards Compliance and Certification...................................................... 1-8