Thema4 Control System SCADA Integration

Thema4 control system - THEMA4-SCADA INTEGRATION Page 1/155
THEMA4 CONTROL SYSTEM
THEMA4-SCADA
INTEGRATION
THEMA4 OPTIONS 2, 3, 15
Document Rev. 26
FEDEGARI AUTOCLAVI SpA

S.S. 235 km 8 - 27010 Albuzzano (PV) - ITALY
 +39 0382 434111  +39 0382 434150  http://www.fedegari.com
Fedegari Autoclavi SpA D/O# 162480.27 January 2018

DOCUMENT REVISION LIST

26 31/01/2018 GAV MGH D/O#162480.27 Updated to SW version W43.1
25 26/05/2017 ABR MGH D/O#162480.26 Updated to SW version W42.3
24 09/03/2017 MBO MGH D/O#162480.25 Added Phase Time Table tags (W42.2)
20 20/12/2013 MBO MGH D/O#162480.21 Updated to SW version W40.1
19 31/05/2013 MBO MGH D/O#162480.20 Updated to SW version W39
17 17/02/2012 RDB MGH D/O#162480.18 Document new format. No change of
contents
15 04/08/2011 ABR MGH D/O#162480.16 Updated to SW version W36
14 09/05/2011 RDB MGH D/O#162480.15 Correct mistakes is data tables
10 25/02/2010 MBO MGH D/O#162480.11 Updated to SW version W32
7 19/01/2009 MGH/ MGH D/O#162480.8 Document structure revision. Add
DAR/ABR paragraph “3.3.3 OPC Client
compatibility”
6 03/09/2008 ABR MGH D/O#162480.7 Fixed error in paragraph 7.1
4 28/04/2008 RDB MGH D/O#162480.5 Correct error in paragraph 6.3.3 Analog
Input
1 17/04/2007 LCA MGH D/O#162480.2 Updated to SW version W24.1
0 05/04/2007 MGH MGH D/O#162480.1 First Edition (up to SW version W24)
Revisi Date Author Approver Document Revision Subject
on Nr. (dd/mm/yy) Code Code Code

DOCUMENT MODIFICATION HISTORY

Document modifications history
Revision 7 Revision 7 derived from “thema4 SCADA integration” DM#162480.7 with the following
change
ALL Document structure revision
Paragraph 3.3.3 OPC client compatibility (new paragraph)
Revision 8 Paragraph 1.1 Updated table of software version applicable
Paragraph 4.1 Updated table of archived data
Paragraph 5.3 Changed “Data update” for items 10, 10.1 and 10.2
Paragraph 6.5 Added PROCESS.PGCODE and note #5
Paragraph 6.7.2 Splitted into subsections and added 6.7.2.2
Paragraph 6.8.1 Added items Par.27, Par.28 and free list
Paragraph 6.10.4 Fixed tag name CRITICALALARMS
Paragraph 6.14.2.2 Changed description for program composition
Paragraph 6.14.2.3 Changed description for program composition
Paragraph 6.14.3 Changed description for program composition
Paragraph 6.14.5 Changed description for program composition
Paragraph 6.15.15 Splitted into subsections and added 6.15.15.2
Paragraph 7.1.3.2 Added example of program phase list with P/G codes
Paragraph 6.6.2 Added RUNPROG.GOLDENCYCLE, .SUTU, .PVSAT and .EQTIME
Paragraph 6.6.9 Added RUNPROG.TPCHECK
Paragraph 6.6.10 Added RUNPROG.TECHECK
Paragraph 6.8.4 Added PRINTER.GCDEFINITION and PRINTER.GCREPORT
Paragraph 6.8.5 Added Eurotherm Chessel
Paragraph 6.8 Added paragraph 6.8.5.3 for Eurotherm Chessel
Paragraph 6.10.4 Added GC.WITH and GC.OK
Paragraph 6.15.4 Added PROG.GOLDENCYCLE, .SUTU, .PVSAT and .EQTIME
Paragraph 6.15.11 Added PROG.TPCHECK
Paragraph 6.15.12 Added PROG.TECHECK
Paragraph 7.1.5 Added Case 5 – Golden Cycle
Paragraph 5.3 Updated table Data Base “Main Summary Table”
Paragraph 6.2 Added STATE.WAITINGACCEPTANCE
Paragraph 6.6.2 Added RUNPROG.PRT.USE
Paragraph 6.8.2 Added SYSTEM.DOOR.GCACCEPTANCE, .DOOR.PRTACCEPTANCE
Paragraph 6.8.4 Added SYSTEM.PRINTER.PHASECHANGE, .PRINTER.PRTTABLE,
.PRINTER.PRTREPORT
Paragraph 6.10.4 Added BATCHEND.PRT.WITH, .PRT.OK
Paragraph 6.10 Added paragraph 6.10.7 for Batch acceptance final data
Paragraph 6.15.4 Added PROG.PRT.USE
Paragraph 6 Added paragraph 6.23 for Parametric Release Report
Paragraph 5.2 Added paragraph 5.2.2
Paragraph 6.6.1 Added unicode string tags DESCRIPTION_U and PROGRAMMER_U
Paragraph 6.6.15 Added unicode string BASECYCLE.NAME_U
Paragraph 6.10.2 Added unicode string version for all string of the table
Paragraph 6.10.7 Added unicode string USERNAME_U and COMMENT_U
Paragraph 6.11 Added unicode string version for all string of the table
Paragraph 6.15.3 Added unicode string PROGRAMMER_U and note about unicode usage
Paragraph 6.15.17 Added unicode string DESCRIPTION_U and note about unicode usage
Paragraph 6.15.20 Added unicode string BASEYCLE.NAME_U and note about unicode usage
Paragraph 6.16.2 Added unicode string version for many strings of the table and note about
unicode usage

Revision 12 Paragraph 5.2.2.1 Corrected important note about selection of String and Unicode String
Paragraph 5.2.2.2 Corrected important note about selection of String and Unicode String
Paragraph 5.3 Updated summary table
Paragraph 5.4 Changed column headers and their description
Chapter 6 Changed format of all tables replacing Type and Par. with 1, 2, 3.
Added paragraph 6.20
Paragraph 6.3.3 Extended NLAI to 199
Paragraph 6.3.5 Extended NLAO to 99
Paragraph 6.5 Added new PROCESS tags and note #6
Paragraph 6.6 Added 0
Paragraph 6.6.12 Added PIDx.INVERT
Paragraph 6.8 Added 6.8.4, 6.8.5 and 6.8.16
Paragraph 6.8.1 Added system parameters for Type 3
Paragraph 6.8.5 Added PRINTER.OTHER
Paragraph 6.9 Extended FACTORY.TMAXTExx
Paragraph 6.10.4 Added new BATCHEND tags for Type 3
Paragraph 6.14.1 Added command codes for Unicode-based systems
Paragraph 6.15 Added 6.15.13
Paragraph 6.15.3 Corrected details about selection of String and Unicode String
Paragraph 6.15.14 Added PIDx.INVERT
Paragraph 6.18.1 Extended to 179
Paragraph 6.18.2 Extended to 179
Paragraph 5.3 Updated summary table, added Tank management
Paragraph 5.4 Added Type 4 to column headers
Chapter 6 Changed format of all tables adding Type 4
Chapter 6 Added a new paragraph 6.8.16 before the existing paragraph “Standby
management”
Chapter 6 Added a new paragraph 6.21 before existing “THEMA4-SCADA
SYNCRONIZATION AND LOCAL/REMOTE OPERATION”
Paragraph 6.8.1 Added system parameters for type 4
Paragraph 6.10.4 Added new BATCHEND tags for Type 4
Revision 14 Paragraph 6.18.2 Updated table of Calibration: Measured
Paragraph 6.6.10 Program parameters: TE list
Paragraph 5.3 Added 8.18 for background management
Paragraph 6.8 Added paragraph 6.8.18 about background management
Paragraph 6.8.7.2 Added 8 recorder probes
Paragraph 6.8.7.3 Added 8 recorder probes
Paragraph 6.10.4 LEAKTEST tags are now applicable also to type 2 and 3
Paragraph 6.10.4 LEAKTEST tags are now applicable also to type 4
Revision 17 - -
Paragraph 6.3.3 Fixed Tag name for element NLAI100-199.UNCALIBRATED
Paragraph 6.6.12 Added decimal ciphers for PID parameters of loaded program
Paragraph 6.15.14 Added decimal ciphers for PID parameters of program managment
Paragraph 6.8.19 Added decimal ciphers for PID parameters of standby management
Paragraph 0 Added decimal ciphers for PID parameters of background management

Revision 19 Paragraph 6.6.2 Added bit RUNPROG.F0ALL

Paragraph 6.6.15 Added bit RUNPROG.BASECYCLE.USETMAX2
Paragraph 6.6.2 Added bit RUNPROG.CUSTOMDOC
Paragraph 6.6.13 Created new paragraph: “Program parameters: Procedures“, shifted old
6.6.13 and 6.6.14 to 6.6.14 and 6.6.15
Paragraph 6.6.13 Added RUNPROG.CUSTOMDOCREADACK and RUNPROG.LINK
Paragraph 6.6.1 Added RUNPROG.PROGSTATUS, RUNPROG.PROGSTATUS.DESC, and
RUNPROG.PROGSTATUS.DESC_U
Paragraph 6.8.1 Added SYSTEM.CUSTOMDOC, SYSTEM.PROGSTATUS.USE,
SYSTEM.PROGSTATUS.LEVEL3.USE,
SYSTEM.PROGSTATUS.LEVEL2.BACK,
SYSTEM.PROGSTATUS.LEVEL3.BACK,
SYSTEM.PROGSTATUS.LEVEL1.DESC,
SYSTEM.PROGSTATUS.LEVEL1.DESC_U,
SYSTEM.PROGSTATUS.LEVEL2.DESC_U,
SYSTEM.PROGSTATUS.LEVEL3.DESC_U
Paragraph 6.15.2 Added PROG.PROGSTATUS, PROG.PROGSTATUS.LEVEL.DESC,
PROG.PROGSTATUS.LEVEL.DESC_U, PROG.F0ALL,
PROG.CUSTOMDOC
Paragraph 6.15.18 Created new paragraph: “Program Procedures“, shifted old 6.15.18 and
6.15.19 to 6.15.19 and 6.15.20
Paragraph 6.15.20 Added PROG.BASECYCLE.USETMAX2
Paragraph 6.10.6 Added BATCHEND.EXPOSURE.MONITORED.F0MIN,
BATCHEND.EXPOSURE.MONITORED.F0MAX,
BATCHEND.EXPOSURE.MONITORED.NLF0MIN,
BATCHEND.EXPOSURE.MONITORED.NLF0MAX
Paragraph 6.9 Add FACTORY.MODEL1, FACTORY.TMAX2, FACTORY.MODEL2
Revision 20 Paragraph 6.8.8 Updated SYSTEM tags related to WIT
Paragraph 1.1 Updated table of applicable versions
Paragraph 6.10.4 Added WITTESTx tags for summary of WIT on FA1, FA2, FA3
Paragraph 6.10.5 Added WITTESTx tags for result of WIT on FA1, FA2, FA3
Revision 21 Paragraph 5.3 Added sections 8.17 and 8.18 to database table
Section 6 Added machine type 9 to all data tables
Paragraph 6.5 Added tags from 158 to 195
Paragraph 6.8.9 Added tags from 5 to 7
Paragraph 6.8 Added paragraph 6.8.17 for cleanser management
Paragraph 6.8 Added paragraph 6.8.18 for torque management
Paragraph 6.10.4 Extended batch end data
Revision 22 Paragraph 6.6.2 Added RUNPROG.CUSTOMDOCREADACKALLPAGES
Paragraph 6.15.4 Added PROG.CUSTOMDOCREADACKALLPAGES
Revision 23 Section 6 Added machine type 10 to all data tables
Paragraph 6.8.6 Added REMOTEPRINTER.IPADDRESS
Section 6 Added paragraph 6.8.21 about combined machines
Paragraph 6.15.1 Added CYCLEID and SELECTIONID
Revision 24 Paragraph 6.5 Added Remaining Time parameter
Paragraph 6.6.16 Added Run program prog. parameters: Phase time table
Paragraph 6.15.21 Added Program parameters: Phase time table
Revision 25 Paragraph 5.3 Updated table with element 26
Paragraph 6.8.21 Fixed Modbus address of SYSTEM.MACHINE2.IPADDRESS and added
MACHINE3 and MACHINE 4
Paragraph 6.24 Added OPCTIMESTAMPOFFSETMINUTES
Chaper 6 Added paragraph 6.25 for Enhanced Process Report
Revision 26 Paragraph 6.6.8 Added new utilities in Program parameters: Utility management table
Paragraph 6.8.7 Added recorder 4 and 5
Paragraph 6.8.7.1 Modified selection title to specify Yokogawa recorder type
Paragraph 6.8.7.4 Added this section to describe the parameters relative to Yokogawa GX10
recorder

NOTATIONS
In this document, these notations are used:
NOTE
for additional note
REFERENCE
for references to other sections
IMPORTANT NOTE
for important note
WARNING!!
For very important note

DOCUMENT SECTIONS
This document is composed of the following sections
PURPOSE
1 Document History and application to THEMA4 software version.
THEMA 4 ARCHITECTURE
2 Thema4 hardware and software architecture, with highlighted the SCADA integration
3 COMMUNICATION PROTOCOLS USED IN THEMA4 SCADA

CONNECTION
Thema4 communication protocols : list, modes, enablement.
Modbus and OPC protocols: architecture, configuration, client compatibility.
THEMA4 ARCHIVE MANAGEMENT

4 Thema4 archives architecture and archive disable.
THEMA4 DATA BASE
5 THEMA4 data base management (OPC client “polling time”,...) and adopted “data format” used in
Thema4, internally the controller and for OPC and Modbus communication.
Data base “MAIN SUMMARY TABLE” and “TAGS TABLES” Columns.
DATA BASE “TAGS TABLES

6 “THEMA4 data base, grouped in TAGS TABLE”, based on Thema4 functions.
PROCESS REPORT TAGS

7 Relation between THEMA4 process report data and SCADA tags

INDEX
1 PURPOSE ...........................................................................................................................................11
1.1 APPLICATION TO THEMA4 SOFTWARE VERSION .........................................................................12
2 THEMA 4 ARCHITECTURE ...............................................................................................................13
2.1 THEMA4 HARDWARE ARCHITECTURE (WITH EXTERNAL SCADA CONNECTION) ....................14
2.2 THEMA4 SOFTWARE ARCHITECTURE ............................................................................................15
3 COMMUNICATION PROTOCOLS USED IN THEMA4 SCADA CONNECTION...............................17
3.1 COMUNICATION PROTOCOLS .........................................................................................................18
3.1.1 Communication protocols list ...............................................................................................................18
3.1.2 Communication modes ........................................................................................................................18
3.1.3 Protocols enablement ..........................................................................................................................18
3.2 MODBUS PROTOCOLS......................................................................................................................19
3.2.1 Modbus RTU/ASCII communication architecture (on serial line) ........................................................19
3.2.2 Modbus TCP/IP communication (on Ethernet network) ......................................................................19
3.2.3 General features of the Modbus communication protocol ...................................................................20
3.2.4 Modbus integration modes ..................................................................................................................21
3.2.5 Thema4 parameter setting to configure the Modbus integration .........................................................22
3.2.6 Possible network configurations using a Thema4 Modbus protocol with serial line ...........................22
3.3 OPC PROTOCOL (ON ETHERNET NETWORK) ................................................................................23
3.3.1 OPC connection architecture ...............................................................................................................23
3.3.2 Thema4 parameter setting to configure the OPC integration ..............................................................23
3.3.3 OPC Client compatibility ......................................................................................................................23
4 THEMA4 ARCHIVE MANAGEMENT .................................................................................................25
4.1 ARCHIVED DATA ................................................................................................................................26
4.2 DISABLE OF ARCHIVED DATA ..........................................................................................................27
5 THEMA4 DATA BASE ........................................................................................................................29
5.1 THEMA4 DATA BASE MANAGEMENT...............................................................................................30
5.1.1 OPC client “polling time” ......................................................................................................................30
5.2 ADOPTED DATA FORMAT .................................................................................................................30
5.2.1 Details of Modbus representation for common data types ..................................................................31
5.2.2 Encoding of string data types ..............................................................................................................32
5.3 DATA BASE “MAIN SUMMARY TABLE” .............................................................................................34
5.4 “TAGS TABLES” COLUMNS ...............................................................................................................39
6 DATA BASE “TAGS TABLES” ..........................................................................................................41
6.1 MODBUS ADDRESS ...........................................................................................................................45
6.2 MACHINE STATE ................................................................................................................................46
6.3 INPUT- OUTPUT .................................................................................................................................47
6.3.1 Digital Input ..........................................................................................................................................47
6.3.2 Digital Output .......................................................................................................................................47
6.3.3 Analog Input.........................................................................................................................................48
6.3.4 “Command register” for autodiagnose .................................................................................................50
6.3.5 Analog Output ......................................................................................................................................50
6.4 ALARMS ..............................................................................................................................................51
6.4.1 Alarms management............................................................................................................................51
6.4.2 Alarms state (ALL+ACK) .....................................................................................................................52
6.4.3 Alarms effects and delay .....................................................................................................................53
6.4.4 Configuration alarms parameters ........................................................................................................54
6.4.5 “Command register” for alarms acknowledge/reset ............................................................................55
6.4.6 “Command register” for alarms configuration ......................................................................................56
6.4.7 Alarms active state (ALM)....................................................................................................................57
6.5 CURRENT PROCESS DATA ..............................................................................................................58
6.6 PARAMETERS OF THE LOADED PROGRAMS ................................................................................62
6.6.1 Program identification data ..................................................................................................................62
6.6.2 Program parameters: General .............................................................................................................62

6.6.3 Program parameters: Sterilization .......................................................................................................63

6.6.4 Program parameters: Auxiliary heating ...............................................................................................64
6.6.5 Program parameters: Air detector .......................................................................................................65
6.6.6 Program parameters: Steam generator ...............................................................................................65
6.6.7 Program parameters: H2O sterilization ...............................................................................................65
6.6.8 Program parameters: Utility management ...........................................................................................65
6.6.9 Program parameters: TP list ................................................................................................................66
6.6.10 Program parameters: TE list ................................................................................................................67
6.6.11 Program parameters: PROBE list ........................................................................................................68
6.6.12 Program parameters: PID parameters ................................................................................................69
6.6.13 Program parameters: Procedures .......................................................................................................71
6.6.14 Program parameters: Barcodes ..........................................................................................................71
6.6.15 Program parameters: Base program cycle ..........................................................................................71
6.6.16 Program parameters: Phase time table ...............................................................................................71
6.7 COMPOSITION OF THE LOADED PROGRAM(READ ONLY) ...........................................................72
6.7.1 List of the P/Gs parameters of the program ........................................................................................72
6.7.2 List of the P/Gs of the program ............................................................................................................72
6.8 SYSTEM PARAMETERS ....................................................................................................................74
6.8.1 System parameters: General ...............................................................................................................74
6.8.2 System parameters: Doors ..................................................................................................................77
6.8.3 System parameters: Oven ...................................................................................................................77
6.8.4 System parameters: H2O2 transducer ................................................................................................77
6.8.5 System parameters: VHP generator....................................................................................................77
6.8.6 System parameters: Onboard printer ..................................................................................................78
6.8.7 System parameters: Recorder .............................................................................................................78
6.8.8 System parameters: Sartorius WIT .....................................................................................................82
6.8.9 System parameters: Steam generator and degasser..........................................................................82
6.8.10 System parameters: Degasser sub-parameters ..................................................................................83
6.8.11 System parameters: Barcode sub-parameters ....................................................................................83
6.8.12 System parameters: SNTP sub-parameters........................................................................................83
6.8.13 System parameters: DST sub-parameters ..........................................................................................84
6.8.14 System parameters: Date-Time format ...............................................................................................84
6.8.15 System parameters: External SQL database parameters ...................................................................85
6.8.16 System parameters: Tank management .............................................................................................86
6.8.17 System parameters: Cleanser management .......................................................................................87
6.8.18 System parameters: Torque management ..........................................................................................88
6.8.19 System parameters: Stand-by management .......................................................................................89
6.8.20 System parameters: Background management ..................................................................................90
6.8.21 System parameters: combined machines ...........................................................................................92
6.8.22 “Command register” for system parameters management..................................................................93
6.9 FACTORY PARAMETERS(READ ONLY) ...........................................................................................94
6.10 BATCH END DATA ..............................................................................................................................95
6.10.1 Batch program data .............................................................................................................................95
6.10.2 Batch input data ...................................................................................................................................95
6.10.3 Batch time data ....................................................................................................................................96
6.10.4 Batch treatment final data ....................................................................................................................97
6.10.5 Batch WIT final data ..........................................................................................................................100
6.10.6 Batch treatment time, temperature and pressure ..............................................................................102
6.10.7 Batch acceptance final data ..............................................................................................................104
6.11 LOGGED SESSION...........................................................................................................................105
6.12 AUDIT TRAIL RECORDS (FUTURE DEVELOPMENT) ....................................................................106
6.13 CURRENT TIME DATE .....................................................................................................................107
6.13.1 Set time-date .....................................................................................................................................107
6.14 PROGRAM/RECIPE MANAGEMENT BY SCADA ............................................................................108
6.14.1 Operations on programs/recipes archived in Thema4 ......................................................................108
6.14.2 Creation of new programs/recipes.....................................................................................................109
6.14.3 TAG summary for operations on program/recipe ..............................................................................111
6.14.4 Run of an existing program ...............................................................................................................111
6.14.5 Architecture of the programs/recipes management in Thema4 ........................................................112
6.15 PROGRAM/RECIPE COMPOSITION BY SCADA ............................................................................113
6.15.1 Program selection ..............................................................................................................................113

6.15.2 Program identification ........................................................................................................................113

6.15.3 Author of the program .......................................................................................................................113
6.15.4 Program parameters: General ...........................................................................................................114
6.15.5 Program parameters: Sterilization .....................................................................................................116
6.15.6 Program parameters: Auxiliary heating .............................................................................................116
6.15.7 Program parameters: Air detector .....................................................................................................117
6.15.8 Program parameters: Steam generator .............................................................................................117
6.15.9 Program parameters: H2O sterilization .............................................................................................117
6.15.10 Program parameters: Utility management ......................................................................................118
6.15.11 Program parameters: TP list ...........................................................................................................118
6.15.12 Program parameters: TE list ...........................................................................................................118
6.15.13 Program parameters: PROBE list ...................................................................................................119
6.15.14 Program parameters: PID parameters ............................................................................................119
6.15.15 Actual value of P/G parameters ......................................................................................................119
6.15.16 Program composition ......................................................................................................................120
6.15.17 Program description ........................................................................................................................121
6.15.18 Program Procedures .......................................................................................................................121
6.15.19 Barcode codes for program selection .............................................................................................122
6.15.20 Base program cycle for program selection .....................................................................................123
6.15.21 Phase time table .............................................................................................................................123
6.16 PROGRAM RUN BY SCADA .............................................................................................................124
6.16.1 Program run error code .....................................................................................................................124
6.16.2 Program selection and input of initial data.........................................................................................125
6.16.3 Run management commands ...........................................................................................................126
6.16.4 Enablement state of the run management commands......................................................................127
6.17 SOFTWARE VERSION .....................................................................................................................128
6.18 CALIBRATION ...................................................................................................................................129
6.18.1 Calibration: Reference .......................................................................................................................129
6.18.2 Calibration: Measured........................................................................................................................131
6.18.3 Calibration: Save command ..............................................................................................................133
6.19 FILTER STERILIZATION ...................................................................................................................134
6.19.1 Filter sterilization: Filter identification.................................................................................................134
6.19.2 Filter sterilization: Reset command ...................................................................................................134
6.20 VHP GENERATOR ............................................................................................................................135
6.20.1 VHP generator: Status .......................................................................................................................135
6.20.2 VHP generator: Commands ..............................................................................................................136
6.21 TANK MANAGEMENT.......................................................................................................................137
6.21.1 Tank management: Status ................................................................................................................137
6.21.2 Tank management : Commands .......................................................................................................137
6.22 THEMA4-SCADA SYNCRONIZATION AND LOCAL/REMOTE OPERATION..................................138
6.22.1 Operation signal of Local/Remote (operated only by SCADA)..........................................................139
6.23 THEMA4 SHUTDOWN ......................................................................................................................140
6.24 OPC SETTING...................................................................................................................................141
6.25 PARAMETRIC RELEASE REPORT ..................................................................................................142
6.26 ENHANCED PROCESS REPORT ....................................................................................................144
7 PROCESS REPORT TAGS ..............................................................................................................147
7.1 PROCESS REPORT DATA ACQUISITION BY SCADA TAGS .........................................................148
7.1.1 Initial data ..........................................................................................................................................148
7.1.2 Sterilization control data ....................................................................................................................150
7.1.3 Phase and parameters of the program ..............................................................................................151
7.1.4 Process data ......................................................................................................................................153
7.1.5 Batch end data...................................................................................................................................155

Section 1 THEMA4 CONTROL SYSTEM
1 PURPOSE
1.1 – APPLICATION TO THEMA4
SOFTWARE VERSION

1.1 APPLICATION TO THEMA4 SOFTWARE VERSION

This document is derived from the previous specifications:
- D/O#109386 – “Modbus Protocol Integration – Thema4 Control System”.

- D/O#122265 – “OPC Protocol Integration – Thema4 Control System”
This document is applicable to the Thema4 control system, starting from the software version W24 to the
current software version, as reported in the “revision table”.
Changes of following software versions, affecting this function, will be documented with an update of this
specification.
For previous software version, starting from W7, for Modbus communication, and from W16, for OPC
communication, please see the following table with the reference to the applicable specification documents.
Modbus OPC Protocol THEMA4- Revision Subject

Protocol Integration SCADA
Integration integration
- - D/O 162480.26 Revision (software version W42.3)
- - D/O 162480.20 Revision (software version W39)
- - D/O 162480.18 Document new format. No change of contents
- - D/O 162480.8 Document structure revision. Add paragraph “3.3.3 –
OPC Client compatibility” (software version W29)
- - D/O 162480.7 Fixed error in paragraph 7.1 (software version W29)
- - D/O 162480.5 Fixed error in paragraph 6.3.3 Analog Input(software
version W29)
D/O 109386.10 D/O 122265.10 D/O 162480.3 Revision (software version W25)
D/O 109386.9 D/O 122265.9 D/O 162480.2 Revision (software version W24.1)
D/O 109386.8 D/O 122265.8 D/O 162480.1 Revision (software version W24)
D/O 109386.7 D/O 122265.7 - Revision (software version W22)
D/O 109386.4 D/O 122265.3 - Revision with “control mode” (W16)
D/O 109386.3 - - Document translation in English (W14/ W15/ W17)
D/O 109386.2 - - Complete revision (Software version W14)
D/O 109386.1 - - First Edition (Software version W7)

2 THEMA 4 ARCHITECTURE
2.1 - THEMA4 HARDWARE ARCHITECTURE (WITH
EXTERNAL SCADA CONNECTION)
2.2 - THEMA4 SOFTWARE ARCHITECTURE

2.1 THEMA4 HARDWARE ARCHITECTURE (WITH EXTERNAL

SCADA CONNECTION)
Lay-out of the standard Thema4 configuration.
File config. File config.I/O RTOS

Coverter BUS board +
4-20/Pt100 bootrom
thermal
STERILIZER 1 printer
UPS 2
Panel PC
L2
3 FIELD BUS
Panel PC
AL. BUS D D AN AN BUS L1 Panel PC
IN OUT IN OUT board (Side 1) L3
HUB
Converter
4-20mA/Pt100
RS232
SCADA
8
Log Data PC
WINDOWS
PCS FECP GUI OS
Nucleus SRVR + Windows
Lib. G/F JWORKS
Conf. Data
ARC
DATA AND FILE

STORAGE Remote location
The external system (SCADA) can be connected to the Panel PC primary (side 1), by a serial line or a Ethernet
connection (directly or by an HUB/SWITCH)

2.2 THEMA4 SOFTWARE ARCHITECTURE

Thema4 application software, is composed of several components with the following architectures, that
highlights the SCADA integration.
REAL TIME OPERATIVE SYSTEM(RTOS)
GUI
PCS FECP GUI
SERVER
GUI
LIB. G/F NUCLEUS
CLIENT
Modbus
server
OPC server
MS Windows O.S. MS Windows

OPC O.S.
client
SCADA GUI
Modbus
RTU/ASCII Remote
client (OPT.)
Modbus
TCP/IP CLIENT
client
These Thema4 software components are here listed:
- R.T.O.S (Real Time Operating System) VxWorks, (by WindRiver, market leader in RTOS).
- PCS (Process Control System), for the management of: the process, the autoclave devices and the
client/server interface with GUI. PCS is composed of two parts: Nucleus and P/Gs Library.
- FECP (Fedegari External Communication Protocol) for the management of the Client-server TCP/IP
communication, between the PCS and all of the sterilizer GUIs.
- GUI (Graphical User Interface), for the man-machine interface (colour, touch screen), developed in Java
language. The software written in JAVA is HW and OS independent, therefore it can even run on MS
Windows operating system
- OPC (OLE for Process Control) server based on WIND NET OPC that is Wind River’s implementation of
the OPC specifications for the VxWorks Real-time Operating System (It includes implementations of the
OPC Alarms and Events (A&E), Data Access (DA), and Data eXchange (DX) servers as well as interactive
client tools). Thema4 OPC server implements the Data Access (DA) based on OPC Data Access
Custom Interface Standard Specification, 2.05a.
- Modbus server RTU/ASCI that allows Modbus communication RTU or ASCII, on serial line

- Modbus server TCP/IP that allows Modbus communication on Ethernet networks
This page is left intentionally blank

3 COMMUNICATION PROTOCOLS USED

IN THEMA4 SCADA CONNECTION
3.1 - COMUNICATION PROTOCOLS
3.1.1 – Communication protocols list
3.1.2 – Communication modes
3.1.3 - Protocols enablement
3.2 - MODBUS PROTOCOLS
3.2.1 – Modbus RTU/ASCII communication
architecture (on serial line)
3.2.2 – Modbus TCP/IP communication (on
Ethernet network)
3.2.3 – General features of the Modbus
communication protocol
3.2.4 – Modbus integration modes
3.2.5 – Thema4 parameter setting to configure the
Modbus integration
3.2.6 – Possible network configurations using a
Thema4 Modbus protocol with serial line
3.3 - OPC PROTOCOL (ON ETHERNET
NETWORK)
3.3.1 - OPC connection architecture
3.3.2 - Thema4 parameter setting to configure
the OPC integration
3.3.3 – OPC Client compatibility

3.1 COMUNICATION PROTOCOLS
3.1.1 Communication protocols list

For SCADA integration, Thema4, can use these different protocols:
Protocol Physical Software utilized Ethernet connection

connection
1 Modbus RTU/ASCII serial line RS232 Modbus RTU/ASCII server Possible connection on a
integrated in Thema4 Ethernet network, only using
an external protocol
converter
2 OPC Ethernet Wind River OPC server Standard
(OLE for Process Control) network integrated in Thema4
3 Modbus TCP/IP Ethernet Modbus TCP/IP server Standard

network integrated in Thema4
3.1.2 Communication modes

For each protocol, Thema 4 allows two different communication modes:
 SUPERVISOR mode (or Read only), that allows SCADA, only to read Thema4 tags.
 CONTROL mode (or Read/Write) , that allows SCADA both, to read and to write Thema4 tags. By this
mode, it is possible to control Thema4 operation, directly from an external system.
3.1.3 Protocols enablement

The enablement of the protocols and their communication mode, needs a Factory setting.
The customer possible choices are listed in the following table, where it is reported if the function is standard or
optional.
Option No. Communication protocol Connection Communication mode Function
OPT.2a Modbus RTU/ASCII RS232 SUPERVISOR Standard (*)

(read only)
OPT.2b Modbus RTU/ASCII RS232 CONTROL Optional
(read / Write)
OPT.3a OPC Ethernet SUPERVISOR Optional
(read only)
OPT.3b OPC Ethernet CONTROL Optional
(read / Write)
OPT.15a Modbus TCP/IP Ethernet SUPERVISOR Optional
(read only)
OPT.15b Modbus TCP/IP Ethernet CONTROL Optional
(read / Write)
IMPORTANT NOTE
(*) This standard option is free and available only for the Panel PC models, with the second
serial port.

3.2 MODBUS PROTOCOLS
3.2.1 Modbus RTU/ASCII communication architecture (on serial line)

This is a standard function on Thema4 system, but the user has to enable and configure it on Thema4 GUI, by
means of some System parameters.
Modbus RTU/ASCII communication protocol, by a Modbus server (slave) uses the serial port, of the primary
panel PC. The SCADA system needs a Modbus client (master), to communicate with Thema4.
Ethernet
THEMA4
panel PC
Side1 PC
SCADA
RS232
Modbus
Slave
Modbus
Master
3.2.2 Modbus TCP/IP communication (on Ethernet network)

The connection is achieved by an Ethernet port.
Ethernet
THEMA4
panel PC
Side1 PC
SCADA
Modbus
Slave
Modbus
Master

3.2.3 General features of the Modbus communication protocol

Since the introduction in 1979, Modbus (AEG-MODICON) protocol has become a worldwide communication
standard in the industrial LANs (Local Area Networks), thanks to its reliability, simplicity and its consequently
low-cost implementation.
The Modbus is a master/slave communication system that allows a master system to communicate with one
or more slave systems (each with its own individual address). All communications are initiated by the master
device (which can be a Host computer, a user interface, a programming panel or a PLC). There are two cases:
4394) In the MODBUS protocol over serial line (MODBUS RTU/ASCII), data are transmitted by means
of messages with the following structure:
Device Function Data bytes Error

address Code check
For the protocol over serial line, depending on the structure of the messages (framing) MODBUS is working
in ASCII mode, (the data are transmitted in ASCII, with a starting code, an ending code and an LCR Error
check) or in RTU mode (the data are transmitted in binary form and with CRC-16 Error check).
2) In the MODBUS protocol over Ethernet (MODBUS TCP/IP), data are transmitted by means of messages
very similar to the ones transmitted over serial line:
Prefix Device Function Data bytes
address Code
In this case Error Check is not part of the message but is provided directly by Ethernet protocol, and there
is a 6 bytes Prefix that contains extra informations such as the length of the whole message.
In both cases the Function codes specify the type of command (read, or write, or other) that is transmitted to
the slave.
The communication can be of two types:

a) query/response : the master addresses one slave only at a time, transmits a query and receives the
response from the slave.
b) broadcast/no response : the master nicode multiple slaves simultaneously, and transmits a command
without waiting for a response from the slaves.

3.2.4 Modbus integration modes

The Thema4 system integrates the MODBUS protocol as described in this paragraph. The following general
considerations apply:
 The system behaves as a slave in query/response mode and responds only to the specific queries
(broadcasting is not supported).
 The implementation of the Modbus protocol consists of managing the functions READ HOLDING
REGISTER and PRESET MULTIPLE REGS for, respectively, reading and writing of n 16 bit registers. With
those calls, by means of WORD operations, it is possible to read and write in the Modbus database. Every
other query code will generate the message ILLEGAL FUNCTION as a response.
3.2.4.1 Modbus serial
The following considerations apply:
 Both ASCII and RTU modes are supported.
 Communication will occur by means of the PanelPC L1 (primary) RS232C serial port of the Thema4
system.
 Enabling of the RS232 port and its serial nicode r on parameters’ setting, will be possible by means of
specific Thema4 system parameters.
3.2.4.1.1 RTU mode
The RTU mode implements the acknowledgement of the message by means of a “time-interval without any
transmission”. This interval is fixed in 3.5 characters and depends on the transmission speed.
Because of the limitations due to the PC’s internal timer, a time-out of 10ms is used for transmission speeds
higher than 9600 baud.
The data are transmitted continuously. When between two characters an interval greater or equal the fixed
interval is detected, the receiver considers the message as completed and waits for the following character that
represents the begin of a new message. If two messages are too close, one unique message is detected and
this one will be rejected because of the failing result of the CRC control.
The telegram format has been established in the document “Modicon nicod Protocol Reference Guide” (PI-
MBUS-300 Rev. H) : one address byte, one byte of query code, n data bytes, two CRC control bytes.
3.2.4.1.2 ASCII mode
The ASCII mode identifies the begin and the end of the messages by means of delimiting characters. The
message begins with the character 0x3A( and ends with the couple of characters 0x0D 0x0A (Carriage Return
and Line Feed).
Moreover, a time-out of 1 second between the message characters is implemented: if the elapsed time interval
is greater, then the message is considered to be ended with an error.
The telegram format has been established in the document “Modicon nicod Protocol Reference Guide” (PI-
MBUS-300 Rev. H) : one byte 0x3A, two address bytes, two bytes of query code, n data bytes, 2 LRC control
bytes, one byte 0x0D and one byte 0x0A.
3.2.4.2 Modbus TCP/IP (Ethernet protocol)
The following considerations apply:
 Communication will occur by means of the PanelPC L1 (primary) Ethernet port of the Thema4 system.
 Enabling and parametrization of the protocol, will be possible by means of specific Thema4 system
parameters.
 Only one connection at a time is supported.
Modbus TCP takes advantage of TCP protocol to manage packets and to keep track of transactions. For this
reason there is no need for the Error Check field which is not present in the message: TCP protocol ensures
that valid packets will be correctly received.
The telegram format has been established in the document “OPEN MODBUS/TCP SPECIFICATION” (Release
1.0, 29 March 1999): six bytes preamble, one address byte, one byte of query code, n data bytes.
All requests are sent via TCP on registered port 502.
Thema4 implementation does not support more than one connection at a time but is tolerant to clients that
pipeline requests.

3.2.5 Thema4 parameter setting to configure the Modbus integration

Using the System parameters it is possible to enable the Modbus communication protocol, to enable write
access (program execution and parameters setting), to assign the Modbus address to the sterilizer and to set
the PanelPC serial communication parameters.
To activate the communication protocol response, it is necessary to set the “SCADA Enabled” flag. Then it is
necessary to choose the communication protocol as Modbus Serial or Modbus TCP.
1) Enable Write – if enabled it is possible to start programs remotely and modifiy Thema4 data;
2) Enable Scada Connection alarm – if enabled an alarm is raised if Thema4 detects that the SCADA
system is not connected.
3.2.5.1 Modbus serial
Once enabled, the following series of parameters and setting options appear:
1) Modbus address – the Modbus address for Thema4.
2) Serial port parameters :
a) Communication port [COM1, COM2]. COM1 is not available if occupied by the door messages
displayer.
b) Mode [ASCII, RTU]
c) Transmission speed [110, 300, 1200, 2400, 4800, 9600, 19200, 38400]
d) Transmission bits [7 bits, 8 bits]
e) Parity [No, Even, Odd]
f) Stop bit [1 bit, 2 bits]
3.2.5.2 Modbus TCP/IP
Once enabled, the following parameter appears:
1) Modbus address – the Modbus address for Thema4.
3.2.6 Possible network configurations using a Thema4 Modbus protocol

with serial line
The use of the Modbus protocol consents to integrate the THEMA4 control system in external systems that use
the Modbus protocol with different network configurations. Follow some possible configurations :
4394) Connection point-point
Allows the connection of a single THEMA4 to one external system, in MODBUS, in serial way.
b) Connection multi-drop
Allows the connection of more THEMA4 (and other systems), to an external system, in MODBUS. Maximum
number of systems that can be addressed N=247. It requires a RS232/RS485 converter.
c) Connection multi-serial
Allows the connection of more THEMA4 (and other systems), to an external system, in MODBUS. It requires
to use a multi-serial boards into the SCADA system.
d) Connection to Modbus Plus networks
Allows the connection of 4 THEMA4, to an external system that is integrated into a peer-to-peer MODBUS
PLUS network, by means of Bridge/Multiplexer BM85 MB+ BRIDGE/MUX MODICON.
e) Connection to PROFIBUS networks
Allows the connection of a THEMA4, to an external system that is integrated into a PROFIBUS DP/FMS
network, by means of a MODBUS RTU (Slave) to PROFIBUS DP/FMS (Master-Slave) protocol converter.
4394) Connection to Ethernet networks
Allows the connection of a THEMA4, to an external system that is integrated into an Ethernet network, by
means of a MODBUS to Ethernet protocol converter.
Ethernet
Using a market “RS232-Ethernet THEMA4

protocol converter”, the SCADA panel PC PC
system can use the Ethernet port, for Side1
SCADA
the communication with the serial line
of Thema4. RS232 Ethernet
Modbus
RS232/Ethernet
Slave
converter
Modbus
Master

3.3 OPC PROTOCOL (ON ETHERNET NETWORK)
3.3.1 OPC connection architecture

Thema4 OPC server allows to use OPC communication protocol (Data Access) for Thema4-SCADA integration,
by Ethernet port of the primary panel PC.SCADA. An OPC client is necessary to communicate with Thema4.
Ethernet
THEMA4
panel PC
Side1 PC
SCADA
Ethernet
OPC
Server
OPC
Client
Thema4 internal OPC server uses, for this connection, the following parameters:
- IP address of the Thema4 controller,
- Server name: THEMA4.OPCDAServer.V1.
IMPORTANT NOTE
In order to correctly work, some particular settings may be required on the SCADA PC.
If SCADA PC operating system uses “Microsoft Windows XP Service Pack 2”, it is
necessary to be sure to apply settings recommended by OPC Foundation explained in the
document “Using OPC via DCOM with Microsoft Windows XP Service Pack 2”.
IMPORTANT NOTE
When using “OPC PowerTool” as a client it may be necessary to register Thema4 OPC in
Windows Registry in order to successfully connect. This can be done by executing once the
OPCReg.exe utility supplied by Fedegari.
3.3.2 Thema4 parameter setting to configure the OPC integration

Using the System parameters it is possible to enable the Modbus communication protocol, to enable write
access (program execution and parameters setting), to assign the Modbus address to the sterilizer and to set
the PanelPC serial communication parameters.
To activate the communication protocol response, it is necessary to set the “SCADA Enabled” flag. Then it is
necessary to choose the communication protocol as OP.
3) Enable Write – if enabled it is possible to start programs remotely and modifiy Thema4 data;
4) Enable Scada Connection alarm – if enabled an alarm is raised if Thema4 detects that the SCADA
system is not connected.
No other setting is required
3.3.3 OPC Client compatibility

Thema4 OPC Server has been tested, in Fedegari, with the following OPC clients:
- Kepware, OPC Quick Client V4.40.90 – U
- Matrikon, OPC Explorer 3.2.1.150
- Ifix, OPC PowerTool 7.33 (*)
- Woodhead, OPCClient Version 4.0.6.0 (*)
IMPORTANT NOTE
This don’t means that other client brands are not applicable. In fact several Thema4 user
utilize other clients, not present in this list.
IMPORTANT NOTE
(*) In these cases, in order to get a connection, it is necessary to register the Thema4 OPC
Server into the Windows registry of the machine that is running the client. This can be done
with the small OPCReg application contained in the KIT.


4 THEMA4 ARCHIVE MANAGEMENT

4.1 - ARCHIVED DATA
4.2 - DISABLE OF ARCHIVED DATA

4.1 ARCHIVED DATA

Thema4 archives are “file-based”: the software PCS stores all the data that need to be archived in files having a
fixed and preset format. All these files are archived in the memories of the Panel PC on the side 1, in specific
directories.
The management of these files, as they are “electronic records”, is compliant with 21 CFR Part 11. These
archived files, therefore, cannot be modified and any attempt of tampering them is detected and recorded (the
file integrity check is based on a CRC32 algorithm); furthermore, after each change by the user, the previous
values of the data are stored in another memory location. All changes made are traced (date and author), and
safe data backup/restore procedures are available to the user.
There are two types of files archived in Thema4 :

 “Process Report”. These files contain the reports of the “cycles run” on the sterilizer and are saved in
ASCII text format.
 “Data of the sterilizer”; These are the other archive files of the sterilizer. They are divided in:
 files of “Parameter” For these type of data, every time there is a data change, the system
creates a new file and saves the previous version of the file in the “historic folder”. These
“versioned” file are in binary format.
 files of “Records” For these type of data, every time there is a data change, the system adds a
new record on a same file, that is saved, continuously updated. These “not versioned” file are in
ASCII format. Historical Alarms List file represents an exception, because it is not an “electronic
records”, but it is a “temporary file” (resident only in RAM), that is lost at the machine shutdown.
All these file are not “encrypted”. Only some data, relative to the users (ID code and password) are encrypted,
by special algorithm.
All the archived files are listed in the following table, where “Hist.files” indicates the presence of the “historical”
versions of the file, other than the “current” version.
Process Sterilizer data Format Current Hist.
Report
N° File name Parameter Recorder File Files
1 Historic Alarm list (*) - - X Binary - -
2 Process reports X ASCII - X
3 Equipment configuration
4 D/IN configuration for NL
5 D/OUT configuration for NL
6 A/IN configuration for NL
7 A/OUT configuration for NL
8 AN channel conversion data
9 Factory parameters
10 System parameters
11 Program parameters and data X Binary X X
12 Golden Cycle data
13 Parametric Release data
14 Cycle data
15 Calibration data
16 Configuration alarm list
17 Alarm list (Effect and delay)
18 Maintenance calendar
19 Filter maintenance
20 Hard disk maintenance
21 List and data of configured users
22 User Access General Data
23 List and data of selected user
24 Backup jobs configurations
25 Audit Trail recording list X ASCII X -
26 System state retained data (***) X Binary X -
27 Internal diagnostical report (****) X ASCII - X(**)
(*) Temporary file
(**) Maximum 10 (cyclical with logic FIFO) not visible, generated as follows of a system PCS tasks watchdog.
(***) Internal state data used by the system; file not visible and printable (read only data).
(****) Fedegari use only.

IMPORTANT NOTE
All the files, except the “Process Report”, are archived independently of the language being
used, because the strings are not stored in these files, but only the reference number to the
“string number”. The strings, in different languages, are contained in specific text files, that
are indexed by “pointers”.
For this reason, every Thema4 station can display and print the archives, in the selected
language.
4.2 DISABLE OF ARCHIVED DATA

By means of an opportune factory configuration, in the “Authorization file” of the single sterilizer, it is
possible to disable the data recording, of the following archives:
- Process Report (2)
- Parameter (3-19)
- Audit trail (20)
In this way, the only archived data will be those managed from SCADA, while Thema4 will manage only the
current “live data”.


5 THEMA4 DATA BASE

5.1 – THEMA4 DATA BASE MANAGEMENT
5.1.1- OPC client “polling time”
5.2 – ADOPTED DATA FORMAT
5.2.1- Details of Modbus representation for
common data types
5.2.2 – Encoding of string data types
5.3 – DATA BASE “MAIN SUMMARY TABLE”
5.4 – “TAGS TABLES” COLUMNS

5.1 THEMA4 DATA BASE MANAGEMENT

The following chapter lists, for all the Thema4 data that it is possible to exchange with a SCADA, the proper “tag
address”, for both OPC and Modbus protocols.
Data are stored in an internal area and refreshed cyclically with a defined refresh time (that depends on the data
type). Both the protocols, by Modbus and OPC servers, access the same data.
5.1.1 OPC client “polling time”

SCADA OPC client polls Thema4 data with its polling time. This implies that OPC data on the SCADA are
stored with a maximum delay, that is the sum of the “Thema4 data base refresh time” and the “SCADA OPC
client polling time”.
Thema4 OPC Server doesn’t allow SCADA OPC client to set an ”OPC client polling time” less then
250msec.
5.2 ADOPTED DATA FORMAT

In the internal operations (program PCS), in Modbus protocol and in OPC protocol, Thema4 utilizes different
formats , for the process data:
PCS program Modbus OPC

Time tenths of a second, tenths of a second tenths of a second
memorized in INT (32 bit) memorized in DWORD (32 bit) memorized in VT_UI4 (unsigned
integer)
Date and time
memorized in VT_DATE
Temperature hundreds of a degree °C, hundreds of a degree °C hundreds of degree °C
memorized in INT (32 bit) memorized in WORD (16 bit) memorized in VT_UI2 (unsigned
short integer)
hundreds of degree °C
memorized in VT_I2 (signed
short integer)
Pressure Pascal, (Pa) Hectopascal (hPa) Hectopascal
(for autoclave) memorized in INT (32 (1 hPa=100 Pa= 1 mbar) memorized in VT_UI2 (unsigned
bit), memorized in WORD (16 bit) short integer)
Pressure tenths of Pascal, Pascal Pascal

(for oven) memorized in INT (32 memorized in WORD (16 bit) memorized in VT_UI2 (unsigned
bit), short integer)
Pascal
memorized in VT_I2 (short
integer)
Logic numbers integers, Integers Integers
memorized in INT (32 bit) memorized in WORD (16 bit) memorized in VT_UI2 (unsigned
short integer)
Logic states nicode states, nicode states nicode states
memorized in BOOL (32 memorized in BIT of a WORD memorized in VT_BOOL
bit) (1 bit) ( nicode)

5.2.1 Details of Modbus representation for common data types

The following section explains the nicod representation, based on WORD wide registers, of common data
types that are used in this document.
Num (W) - These fields correspond to number memorized in single WORDs. When there are specific
upper and lower limits it may be represented also with the interval (for example 0/1 or 0/247).
4xxxx
10xsec (DW) – These fields correspond to time in tenth of seconds, memorized in DOUBLE WORDs:
LOWORD HIWORD
4xxxx 4xxxx + 1
hPa (W) - These fields correspond to pressures in Hectopascal (100 Pa = 1 mbar), memorized in WORDs:
xxxx mbar
4xxxx
Pa (W) - These fields correspond to pressures in Pascal (100 Pa = 1 mbar), memorized in WORDs:
xxxx Pa
4xxxx
100x°C (W) – These fields correspond to temperatures in hundreds of a degree Celsius, memorized in
xxxx °C*100
4xxxx
String - These fields correspond to an ASCII string of arbitrary length, memorized in an array of WORDs. If
the actual length of the string is lower than the capacity of the WORD array the string is null terminated by
means of a zero char.
char[1] .. char[0] char[3] .. char[2] char[n] .. char[n-1]
…
4xxxx 4xxxx+ 1 4xxxx +n/2
Unicode String - These fields correspond to an UNICODE UCS-2 string of arbitrary length, memorized in
an array of WORDs. If the actual length of the string is lower than the capacity of the WORD array the string
is null terminated by means of a zero char.
wchar[0] wchar[1] wchar[n]
…
4xxxx 4xxxx + 1 4xxxx+n
Bit - These fields correspond to BOOLEAN values, memorized in WORDs. The bit number into the WORD
is specified by the address. For example 41230.4 is the 5th bit of the WORD.
15 … 10
4xxxx
4xxxx.1

5.2.2 Encoding of string data types

Thema4 is able to manage characters beyond the ASCII range, depending by languages installed. The system
works internally with a codepage which can be:
- a single-byte codepage (CP1252, CP1251, CP1250…);
- nicode-based (CPXXXX*, such as CP1252* for Chinese).
5.2.2.1 Single-byte codepage
There can be two scenarios depending by the protocol used:
- Modbus (Serial or TCP/IP): String are exchanged on Modbus registers, packing two chars for each register.
The chars obtained unpacking the register must be interpreted applying the codepage used by Thema4, in
order to be read correctly. Failing to do so might cause to interpret incorrectly extended-ASCII characters
(range 128-255). Similarly, when a String is written from the SCADA to Thema4, the controller will interpret
the binary value of each character received applying the codepage used, so it might interpret incorrectly
extended-ASCII characters.
IMPORTANT NOTE
This step is generally not necessary in what the most common case is that both
Thema4 and the SCADA are working with the codepage CP1252, or with the same
codepage anyway.
This conversion step is necessary when the codepage used by Thema4 is different from
the one that is used by the SCADA.
- OPC: String are exchanged using the VT_BSTR data type which is always Unicode. When the SCADA is
reading a String, Thema4 converts it to Unicode before to pass it to the SCADA: this operation is always
possible so the SCADA always reads the correct information. When a SCADA needs to write a String to
Thema4 the controller will convert it to the internal codepage: this operation is not always possible, and if
the String contains characters not supported the information is not written correctly.
Starting from W33 the system supports for some String data also the Unicode String data type (for OPC
protocol tags whose name ends with “_U”).
These area carry the same information, but are encoded in a different way:
- Modbus (Serial or TCP/IP): Unicode String are exchanged on Modbus registers packing one character for
each register (UCS-2 encoding).
- OPC: String are exchanged using the VT_BSTR data type, and the information obtained is identical from
String tags (for example RUNPROG.DESCRIPTION and RUNPROG.DESCRIPTION_U are identical)
IMPORTANT NOTE
Tags which have R access are used only to extract information from Thema4, and the
SCADA is free to read String or Unicode String data at will.
Tags which have RW access are used to send data to Thema4 (program data, batch data…)
when a specific command is issued (create a new program, start a new batch…). To specify
if data have to be taken from String or from Unicode String data different write commands
have to be used (for example set PROGLOAD.COMMAND = 1 to use String, set it to 11 to
use Unicode String). For compatibility reasons the existing command values cause the
controller to accept text from String data; to accept text for Unicode String data, new
command values have to be used.
5.2.2.2 Unicode-based
IMPORTANT NOTE
This scenario applies only to special languages identified by a codepage CPXXXX*, such as
Chinese language.
This case can happen only starting from W33, where the Unicode String data type has been added (for OPC
protocol tags whose name ends with “_U”).
In order to exchange string data correctly, it is mandatory to work with the Unicode String data when they are
available (avoid the String data version for every data that has a Unicode String data version, because these
are likely to contain incorrect data) both for Modbus and OPC protocols.

IMPORTANT NOTE
Tags which have R access are used only to extract information from Thema4, but the
information which has to be read could contain in some case Unicode characters, for this
reason it is mandatory to read Unicode String data when available (Unicode String data are
not available only for data which can’t contain Unicode information, such as for example
“machine identifier”, “user id”…).
Tags which have RW access are used to send data to Thema4 (program data, batch data…)
when a specific command is issued (create a new program, start a new batch…). To specify
if data have to be taken from String or from Unicode String data different write commands
have to be used (for example set PROGLOAD.COMMAND = 1 to use String, set it to 11 to
use Unicode String). For compatibility reasons the existing command values cause the
controller to accept text from String data; to accept text for Unicode String data, new
command values have to be used.

5.3 DATA BASE “MAIN SUMMARY TABLE”

Thema4 DATA BASE tags are grouped in several “TAGS TABLES”, based on Thema4 functions.
These table are listed in this MAIN SUMMARY TABLE, the user can see in order to found Thema4 data and corresponding tags.
N° Table Description SCADA Data Parag.

R/W access update Refer.
1 Modbus Address Thema4 Modbus address (only for Modbus communication) R variation 6.1
2 Machine state Boolean variables that provide some information about the machine R variation 6.2
state
3 Input-output I/O current status R and R/W - 6.3
3.1 Digital Input Digital Input current status R 0.5 sec 6.3.1
3.2 Digital Output Digital Output current status R/W 0.5 sec 6.3.2
3.3 Analog Input Analog Input current status R 0.5 sec 6.3.3
3.4 “Command register” for autodiagnose Command register to force the digital and/or analog output R/W variation 6.3.4
3.5 Analog Output Analog Output current status with autodiagnose function (by “command R/W 0.5 sec 6.3.5
register”)
4 Alarms Alarms: state, ack, effects, delay and configuration R and R/W - 6.4
4.1 Alarms management Alarms management - - 6.4.1
4.2 Alarms state (ALL+ACK) Alarms state: activated (ALL) and acknowledged (ACK) R 0.5 sec 6.4.2
4.3 Alarms effects and delay Alarm parameters: effects and delay R/W variation 6.4.3
4.4 Configuration alarms parameters Configuration alarms parameters: NLI, NLO, LOG, AUX, SCM R/W variation 6.4.4
4.5 “Command register” for alarms Command register to acknowledge the alarms or to reset the retained active R/W variation 6.4.5
acknowledge/reset alarms
4.6 “Command register” for alarms Command register to configure the alarms: effects and delays and R/W variation 6.4.6
configuration “configuration alarm” parameters
4.7 Alarms active state (ALM) Alarms “active” state (ALM) for retained or not-retained alarms R 0.5 sec 6.4.7
5 Current process data Current process data: sensors TE and TP, phases target, phase N°, Fx R 0.5 sec 6.5
values
follows,..


6 Parameters of the loaded program Program parameters of the loaded program for running R at 6.6
prog..loading
6.1 Program identification data Program number/description and programmer public name R at prog..loading 6.6.1
6.2 Program parameters: General General parameters R at prog..loading 6.6.2
6.3 Program parameters: Sterilization Sterilization parameters R at prog..loading 6.6.3
6.4 Program parameters: Auxiliary heating Auxiliary heating parameters R at prog..loading 6.6.4
6.5 Program parameters: Air detector Air detector parameters R at prog..loading 6.6.5
6.6 Program parameters: Steam generator Steam Generator parameters R at prog..loading 6.6.6
6.7 Program parameters: H2O sterilization H2O sterilization parameters R at prog..loading 6.6.7
6.8 Program parameters: Utility management Utility management R at prog..loading 6.6.8
6.9 Program parameters: TP list List of TP used into the program R at prog..loading 6.6.9
6.10 Program parameters: TE list List of TE used into the program R at prog..loading 6.6.10
6.11 Program parameters: PROBE list List of PROBE used into the program R at prog..loading 6.6.11
6.12 Program parameters: PID parameters PID used into the program R at prog..loading 6.6.12
6.13 Program parameters: Barcode Barcode parameters R at prog..loading 6.6.13
6.14 Program parameters: Base program Cycle Base program cycle parameters R at prog..loading 6.6.14
7 Composition of the loaded program Composition of the loaded program for running R at 6.7
prog..loading
7.1 List of the P/Gs parameter of the program List of the P/Gs parameter of the program for running R at prog..loading 6.7.1
7.2 List of the P/Gs numbers of the program List of the P/Gs numbers of the program for running R at prog..loading 6.7.2
8 System parameters Parameters of the system R/W variation 6.8
8.1 System parameters: General General parameters of the system R/W variation 6.8.1
8.2 System parameters: Door(s) Doors parameters of the system R/W variation 6.8.2
8.3 System parameters: Oven Oven parameters of the system R/W variation 6.8.3
8.4 System parameters: VHP transducer VHP transducer parameters of the system R/W variation 6.8.4
8.5 System parameters: VHP generator VHP generator parameters of the system R/W variation 6.8.5
8.6 System parameters: Onboard printer Onboard printer parameters of the system R/W variation 6.8.6
8.7 System parameters: Recorder Recorder parameters of the system R/W variation 6.8.7
8.8 System parameters: Sartorius WIT Sartorius WIT parameters of the system R/W variation 6.8.8
8.9 System parameters: Steam generator and Stem generator parameters of the system R/W variation 6.8.9
degasser
8.10 System parameters: Degasser sub- Degasser sub-parameters of the system R/W variation 6.8.10
parameters
8.11 System parameters: Barcode sub- Barcode sub-parameters of the system R/W variation 6.8.11
parameters
follows,..


8.12 System parameters: SNTP sub- SNTP sub-parameters of the system R/W variation 6.8.12
parameters
8.13 System parameters: DST sub- DST sub-parameters of the system R/W variation 6.8.13
parameters
8.14 System parameters: Date-Time format Date-Time format parameters of the system R/W variation 6.8.14
8.15 System parameters: External SQL External SQL database parameters of the system R/W variation 6.8.15
database parameters
8.16 System parameters: Tank management Tank management parameters of the system R/W variation 6.8.16
8.17 System parameters: Cleanser Management of cleansers R/W variation 6.8.17
management
8.18 System parameters: Torque Torque management R/W variation 6.8.18
management
8.17 System parameters: Stand-by Stand-by management parameters of the system R/W variation 6.8.19
management
8.18 System parameters: Background Background management parameters of the system R/W variation 6.8.20
management
8.19 “Command register” for system “Command register” for system parameters management R/W variation 6.8.21
parameters management
8.20 System parameters: combined machines Combined machines R/W variation 6.8.22
9 Factory parameters (read only) Factory parameters of the system R variation 6.9
10 Batch end data Data at the end of the cycle R at program 6.10
load and end
10.1 Batch program data Data of the program at the end of the cycle R at program load 6.10.1
10.2 Batch input data Data of the input at the end of the cycle R at program load 6.10.2
10.3 Batch time data Data of the time at the end of the cycle R at program end 6.10.3
10.4 Batch treatment final data Data of the treatment at the end of the cycle R at program end 6.10.4
10.5 Batch WIT final data Data of the WIT at the end of the cycle R at program end 6.10.5
10.6 Batch treatment time, temperature and Data of the treatment time, temperature and pressure at the end of the cycle R at program end 6.10.6
pressure
10.7 Batch acceptance final data Data of batch acceptance (option) R at program end 6.10.7
11 Logged sessions Logged sessions R variation 6.11
12 Audit trail records (Future Audit trail records (Future development) R variation 6.12
development)
13 Current Time-Date Actual Time and Date R 1s 6.13
13.1 Set time-date Setting of the time and date R/W variation 6.13.1
follows,..


14 Program/Recipe management Program/Recipe management (written only by SCADA) R and R/W - 6.14
14.1 Operations on programs/recipes archived in Operations on programs/recipes archived in Thema4 - - 6.14.1
Thema4
14.2 Creations of new programs/recipes Creations of new programs/recipes - - 6.14.2
14.2.1 Programs/recipes generation from Thema4 Programs/recipes generation from Thema4 - - 6.14.2.1
14.2.2 Download recipe/program from supervisor Download recipe/program from supervisor and memorization in Thema4 - - 6.14.2.2
and memorization in Thema4
14.2. Download and execution of recipe/program Download and execution of recipe/program from supervisor, without - - 6.14.2.3
3 from supervisor, without memorization in memorization in Thema4
Thema4
14.3 TAG summary for operations on TAG syntax for operations on programs/recipes R and R/W variation 6.14.3
programs/recipes
14.4 Run of an existing program Run of an existing program - - 6.14.4
14.5 Architecture of the programs/recipes Architecture of the programs/recipes management in Thema4 - - 6.14.5
management in Thema4
15 Program/Recipe composition by SCADA Program/Recipe composition by SCADA R and R/W variation 6.15
15.1 Program selection Program selection R/W variation 6.15.1
15.2 Program identification Program identification R/W variation 6.15.2
15.3 Author of the program Identification data of the author of the program R/W variation 6.15.3
15.4 Program parameters: General General parameters R/W variation 6.15.4
15.5 Program parameters: Sterilization Sterilization parameters R/W variation 6.15.5
15.6 Program parameters: Auxiliary heating Auxiliary heating parameters R/W variation 6.15.6
15.7 Program parameters: Air detector Air detector parameters R/W variation 6.15.7
15.8 Program parameters: Steam generator Steam Generator parameters R/W variation 6.15.8
15.9 Program parameters: H2O sterilization H2O sterilization parameters R/W variation 6.15.9
15.10 Program parameters: Utility management Utility management R/W variation 6.15.10
15.11 Program parameters: TP list List of TP used into the program R/W variation 6.15.11
15.12 Program parameters: TE list List of TE used into the program R/W variation 6.15.12
15.13 Program parameters: PROBE list List of PROBE used into the program R/W variation 6.15.13
15.14 Program parameters: PID parameters PID used into the program R/W variation 6.15.14
15.15 Actual value of P/G parameters Actual value of P/G parameters R/W variation 6.15.15
15.16 Program composition P/Gs number sequence of the program R/W variation 6.15.16
15.17 Program description Program description R/W variation 6.15.17
15.18 Barcode codes for program selection Barcode codes for program selection R/W variation 6.15.18
15.19 Base program cycle for prog. Selection Base program cycle for program selection R/W variation 6.15.19
follows,..

16 Program run by SCADA Program run by SCADA R and R/W - 6.16

16.1 Program run error code Program run error code R at remote prog. 6.16.1
Selection
16.2 Program selection and input of initial data Program selection and input of initial data RW variation 6.16.2
16.3 Run management commands Run management commands RW at remote prog. 6.16.3
Selection
16.4 Enablement state of run management Enablement state of run management commands R variation 6.16.4
commands
17 Software version Software version of the system R at system start 6.17
18 Calibration Calibration of the system R/W variation 6.18
18.1 Calibration: Reference Calibration: Reference R/W variation 6.18.1
18.2 Calibration: Measured Calibration: Measured R/W variation 6.18.2
18.3 Calibration: Save command Calibration: Save command R/W variation 6.18.3
19 Filter sterilization Filter sterilization R and R/W variation 6.19
19.1 Filter sterilization: Filter identification Filter sterilization: Filter identification R and R/W variation 6.19.1
19.2 Filter sterilization: Reset comand Filter sterilization: Reset comand R/W variation 6.19.2
20 VHP generator VHP generator data and commands R and R/W variation 6.20
20.1 VHP generator: Status Status of the VHP generator R variation 6.20.1
20.2 VHP nicode : Commands Command to manage the VHP generator R/W variation 6.20.2
21 Tank management Tank management R/W variation 6.21
21.1 VHP generator: Status Status of the VHP generator R variation 6.21.1
21.2 VHP nicode : Commands Command to manage the VHP generator R/W variation 6.21.2
22 Scada synchronization Scada synchronization of the system R/W cyclical and 6.22
variation
22.1 Operation signal of Local/Remote Operation signal of Local/Remote operation - - 6.22.1
operation
23 Shutdown Shutdown of the system R and R/W variation 6.23
24 OPC settings OPC settings of the system R/W variation 6.24
25 Parametric Release report Parametric Release report R at program 6.25
end
26 Enhanced Process report Enhanced Process report R variation 6.26

5.4 “TAGS TABLES” COLUMNS

In the “TAGS TABLES of the next section, the columns contain the following data
Section Colunm Description
DATA N° Tag number in the section

Name Name (description) of the variable contained in the register.
UM Unit of Measure (“sb” means “see table below “)
(Type) 1 Specifies if the data applies to the specific sterilizer type (1 = autoclave, 2 = oven, 3
(Type) 2 = vhp, 4 = dmd). It can be represented by an “X” or by the parameter number that
(Type) 3 can be retrieved from the Thema4 User Manual.
(Type) 4
RW Shows Read and Write permissions of the single data:
 R = READ ONLY
 RW = READ AND WRITE
Update The internal refresh frequency of the data.
MODBUS Address Modbus addresses (WORD).
Locations of type xxxx represent a WORD
Locations of type xxxx.y represent a bit of the WORD.
Locations of type xxxx…yyyy represent two Modbus registers utilized as DWORD
OPC Tag Tagname of the variable. It can be organized as levels and tags
Data The OPC kind of data. It can be
- VT_UI2, unsigned short integer
- VT_I2, signed short integer
- VT_UI4, unsigned integer
- VT_BOOL, unicode
- VT_DATE,
- VT_BSTR[n]. String of n elements
Note that VT_BSTR[52] is a shorthand notation to specify a string of 52 elements

and VT_UI2[6] is used to represents a VT_ARRAY of VT_UI2 with 6 elements.
N.B. The Reserved “free” areas are read-only, always zero, available for future extensions.


6 DATA BASE “TAGS TABLES”

6.1 – MODBUS ADDRESS
6.2 – MACHINE STATE
6.3 – INPUT- OUTPUT
6.3.1 – Digital Input
6.3.2 – Digital Output
6.3.3 – Analog Input
6.3.4 – “Command register” for autodiagnose
6.3.5 – Analog Output
6.4 – ALARMS
6.4.1 – Alarms management
6.4.2 – Alarms state (ALL+ACK)
6.4.3 – Alarms effects and delay
6.4.4 – Configuration alarms parameters
6.4.5 – “Command register” for alarms
acknowledge/reset
6.4.6 – “Command register” for alarms
configuration
6.4.7- Alarms active state (ALM)
6.5 – CURRENT PROCESS DATA
6.6 – PARAMETERS OF THE LOADED
PROGRAMS
6.6.1 – Program identification data
6.6.2 – Program parameters: General
6.6.3 – Program parameters: Sterilization
6.6.4 – Program parameters: Auxiliary heating
6.6.5 – Program parameters: Air detector
6.6.6 – Program parameters: Steam generator
6.6.7 – Program parameters: H2O sterilization
6.6.8 – Program parameters: Utility management
6.6.9 – Program parameters: TP list
6.6.10 – Program parameters: TE list
6.6.11 – Program parameters: PROBE list
6.6.12 – Program parameters: PID parameters
6.6.13 – Program parameters: Procedures
6.6.14 – Program parameters: Barcodes
6.6.15 – Program parameters: Base program cycle
6.6.16 – Program parameters: Phase time table

6.7 – COMPOSITION OF THE LOADED

PROGRAM(READ ONLY)
6.7.1 – List of the P/Gs parameters of the program
6.7.2 – List of the P/Gs of the program
6.8 – SYSTEM PARAMETERS
6.8.1 – System parameters: General
6.8.2 – System parameters: Doors
6.8.3 – System parameters: Oven
6.8.4 – System parameters: H2O2 transducer
6.8.5 – System parameters: VHP generator
6.8.6 – System parameters: Onboard printer
6.8.7 – System parameters: Recorder
6.8.8 – System parameters: Sartorius WIT
6.8.9 – System parameters: Steam generator and
degasser
6.8.10 – System parameters: Degasser sub-
parameters
6.8.11 – System parameters: Barcode sub-
parameters
6.8.12 – System parameters: SNTP sub-parameters
6.8.13 – System parameters: DST sub-parameters
6.8.14 – System parameters: Date-Time format
6.8.15 – System parameters: External SQL database
parameters
6.8.16 – System parameters: Tank management
6.8.17 – System parameters: Cleanser management
6.8.18 – System parameters: Torque management
6.8.19 – System parameters: Stand-by management
6.8.20 –
System parameters: Background management
6.8.21 – “Command register” for system parameters
management
6.8.22 – System parameters: combined machines
6.9 – FACTORY PARAMETERS(READ ONLY)
6.10 – BATCH END DATA
6.10.1 – Batch program data
6.10.2 – Batch input data
6.10.3 – Batch time data
6.10.4 – Batch treatment final data
6.10.5 – Batch WIT final data
6.10.6 – Batch treatment time, temperature and
pressure
6.10.7 – Batch acceptance final data

6.11 – LOGGED SESSION

6.12 – AUDIT TRAIL RECORDS (FUTURE
DEVELOPMENT)
6.13 – CURRENT TIME DATE
6.13.1 – Set time-date
6.14 – PROGRAM/RECIPE MANAGEMENT BY
SCADA
6.14.1 – Operations on programs/recipes archived
in Thema4
6.14.2 – Creation of new programs/recipes
6.14.3 – TAG summary for operations on
program/recipe
6.14.4 Run of an existing program
6.14.5 Architecture of the programs/recipes
management in Thema4
6.15 – PROGRAM/RECIPE COMPOSITION BY
SCADA
6.15.1 – Program selection
6.15.2 – Program identification
6.15.3 – Author of the program
6.15.4 – Program parameters: General
6.15.5 – Program parameters: Sterilization
6.15.6 – Program parameters: Auxiliary heating
6.15.7 – Program parameters: Air detector
6.15.8 – Program parameters: Steam generator
6.15.9 – Program parameters: H2O sterilization
6.15.10 – Program parameters: Utility management
6.15.11 – Program parameters: TP list
6.15.12 – Program parameters: TE list
6.15.13 – Program parameters: PROBE list
6.15.14 – Program parameters: PID parameters
6.15.15 – Actual value of P/G parameters
6.15.16 – Program composition
6.15.17 – Program description
6.15.18 – Program Procedures
6.15.19 – Barcode codes for program selection
6.15.20 – Base program cycle for program selection
6.15.21 – Phase time table

6.16 – PROGRAM RUN BY SCADA

6.16.1 – Program run error code
6.16.2 – Program selection and input of initial data
6.16.3 – Run management commands
6.16.4 – Enablement state of the run management
commands
6.17 – SOFTWARE VERSION
6.18 – CALIBRATION
6.18.1 – Calibration: Reference
6.18.2 – Calibration: Measured
6.18.3 – Calibration: Save command
6.19 – FILTER STERILIZATION
6.19.1 – Filter sterilization: Filter identification
6.19.2 – Filter sterilization: Reset command
6.20 – VHP GENERATOR
6.20.1 – VHP generator: Status
6.20.2 – VHP generator: Commands
6.21 – TANK MANAGEMENT
6.21.1 – Tank management: Status
6.21.2 – Tank management : Commands
6.22 – THEMA4-SCADA SYNCRONIZATION
AND LOCAL/REMOTE OPERATION
6.22.1 – Operation signal of Local/Remote (operated
only by SCADA)
6.23 – THEMA4 SHUTDOWN
6.24 – OPC SETTING
6.25 – PARAMETRIC RELEASE REPORT
6.26 – ENHANCED PROCESS REPORT

6.1 MODBUS ADDRESS

DATA MODBUS OPC
N° Name UM 1 2 3 4 9 10 RW Update Address Tag Data
1 Modbus address of TH4 0/247 x x x x x x R variation 0001 MODUBSADDRESS VT_UI2

6.2 MACHINE STATE

DATA MODBUS OPC
1 Computer ON sb x x x x x x R variation 0002.0 STATE.COMPUTERON VT_BOOL
2 Cycle in progress sb x x x x x x R variation 0002.1 “ .CYCLEINPROGRESS VT_BOOL
3 Cycle complete sb x x x x x x R variation 0002.2 “ .CYCLECOMPLETE VT_BOOL
4 Sterilizing sb x x x x x R variation 0002.3 “ .STERILIZING VT_BOOL
5 Sterilized sb x x x x x R variation 0002.4 “ .STERILIZED VT_BOOL
6 High pathogen sterilized sb x R variation 0002.5 “ .HPSTERILIZED VT_BOOL
7 Alarm ON sb x x x x x x R variation 0002.6 “ .ALARMON VT_BOOL
8 Auxiliary alarm 1 sb x x x x x x R variation 0002.7 “ .AUXALARM1 VT_BOOL
9 Auxiliary alarm 2 sb x x x x x x R variation 0002.8 “ .AUXALARM2 VT_BOOL
10 Emergency sb x x x x x x R variation 0002.9 “ .EMERGENCY VT_BOOL
11 Fatal emergency sb x x x x x x R variation 0002.10 “ .FATALEMERGENCY VT_BOOL
12 Door system alarm sb x x x x x x R variation 0002.11 “ .DOORALARM VT_BOOL
13 Door1 free to open sb x x x x x x R variation 0002.12 “ .DOOR1FREE VT_BOOL
14 Door2 free to open sb x x x x x x R variation 0002.13 “ .DOOR2FREE VT_BOOL
15 Door1 opened sb x x x x x x R variation 0002.14 “ .DOOR1OPEN VT_BOOL
16 Door2 opened sb x x x x x x R variation 0002.15 “ .DOOR2OPEN VT_BOOL
17 Remote start enabled sb x x x x x x R variation 0003.0 “ .REMOTESTART VT_BOOL
18 Program requested sb x x x x x x R variation 0003.1 “ .PROGREQUESTED VT_BOOL
19 Waiting for program start sb x x x x x x R variation 0003.2 “ .WAITINGPROGSTART VT_BOOL
20 Blackout sb x x x x x x R variation 0003.3 “ .BLACKOUT VT_BOOL
21 Program loaded sb x x x x x x R variation 0003.4 “ .PROGLOADED VT_BOOL
22 Printer error sb x x x x x x R variation 0003.5 “ .PRINTERERROR VT_BOOL
23 Autodiagnose sb x x x x x x R variation 0003.6 “ .AUTODIAGNOSE VT_BOOL
24 Waiting acceptance sb x x x x x R variation 0003.7 “ .WAITINGACCEPTANCE VT_BOOL
25-32 free 0003.8 – 0003.15
33-48 free 0004.0 – 0004.15
40002..40003 – Machine state

It occupies two WORDs, utilized as bit to bit. Each bit indicates a boolean state (0 is FALSE, 1 is TRUE).
15 … 15 …
40002 40003

6.3 INPUT- OUTPUT
6.3.1 Digital Input

DATA MODBUS OPC
1 Digital input 1..16 sb x x x x x x R 0.5s 0005 NLDI1 .. NLDI16 VT_BOOL
… … … x x x x x x … … … … …
63 Digital input 993..1000 sb x x x x x x R 0.5s 0067 NLDI993 … NLDI1000 VT_BOOL
64 free 0068 – 0069
40005..40067 – Digital input 1..1000

Each WORD is utilized as bit to bit and shows the state of the 16 consecutive digital inputs. (0 is OFF, 1 is ON).
15 … 15 …
…
40005 40067
NLDI(16) … NLDI(1) NLDI(1000) …NLDI(993)
6.3.2 Digital Output

DATA MODBUS OPC
1 Digital output 1..16 sb x x x x x x RW 0.5s 0070 NLDO1 … NLDO16 VT_BOOL
… … … x x x x x x … … … … …
63 Digital output 993..1000 sb x x x x x x RW 0.5s 0132 NLDO993 ... NLDO1000 VT_BOOL
64 free 0133 – 0134
40070..40132 – Digital output 1..1000

Each WORD is utilized as bit to bit and shows the state of the 16 consecutive digital outputs (0 is OFF, 1 is ON).
15 … 15 …
…
40070 40132
NLDO(16) … NLDO(1) NLDO(1000) …NLDO(993)

6.3.3 Analog Input

DATA MODBUS OPC
N° Name UM 1 2 3 4 9 10 RW Update Address Tag data
1 Analog input un-calibrated 1 sb x x x x x x R 0135 NLAI1.UNCALIBRATED VT_UI2
0.5s
NLAI1.UNCALIBRATED_ VT_I2
… … … x x x x x x … … … … …
0.5s
0.5s
… … … … … … … … … … … … …
0.5s
0.5s
… … … … … … … … … … … … …
199 Analog input un-calibrated 199 sb x x x x x x R 0.5s 7209 NLAI199.UNCALIBRATED VT_UI2
200 Analog input calibrated 1 sb x x x x x x R 0185 NLAI1.CALIBRATED VT_UI2
0.5s
NLAI1.CALIBRATED_ VT_I2
… … … … … … … … … … … … …
249 Analog input calibrated 50 sb x x x x x x R 0234 NLAI50.UNCALIBRATED VT_UI2
0.5s
0.5s
… … … … … … … … … … … … …
298 Analog input calibrated 99 sb x x x x x x R 7098 NLAI99.UNCALIBRATED VT_UI2
0.5s
0.5s
… … … … … … … … … … … … …
398 Analog input calibrated 199 sb x x x x x x R 0.5s 7309 NLAI199.UNCALIBRATED VT_UI2
399 Analog input status 1..16 sb x x x x x x R 0.5s 0235 NLAI1.STATUS … NLAI16.STATUS VT_BOOL
… … … … … … … … … … … … …
402 Analog input status 49..50 sb x x x x x x R 0.5s 0238 NLAI49.STATUS NLAI50.STATUS VT_BOOL
… … … … … … … … … … … … …

40135..40184 – Analog input un-calibrated 1..50

Each WORD indicates the direct value (not calibrated) of the corresponding input. The numeric value read, can be in hectopascal (in case of a pressure
transducer) or in tenths of a degree (in case of a temperature). For each WORD, OPC provides the value in two different formats: VT_UI2 or VT_I2.
…
40135 40184
NLAI(1) NLAI(50)
40185..40234 – Analog input calibrated 1..50

Each WORD indicates the calibrated value of the corresponding input. The numeric value read, can be in hectopascal (in case of a pressure transducer) or in
hundreds of a degree (in case of a temperature). For each WORD, OPC provides the value in two different formats: VT_UI2 or VT_I2.
…
40185 40234
NLAI(1) NLAI(50)
40235..40238 – Analog input status 1..50

Each WORD is utilized as bit to bit. Each bit indicates if the corresponding analog input works correctly. Bit at 0 indicates: working well. Bit at 1 indicates: not
configured or not working well.
15 … 15 …
…
40235 40238
NLAI(16) … NLAI(1) NLAI(50), …. NLAI(49)

6.3.4 “Command register” for autodiagnose

DATA MODBUS OPC
1 Autodiagnose command register 0/1 x x x x x x RW variation 0239 AUTODIAGNOSE VT_UI2
The user can force the digital and/or analog output, by setting the “command register” tag to “1”.
Thema4 confirms the execution of this operation by resetting the “command register” tag to “0”.
IMPORTANT NOTE
The change of these data is possible only in the same conditions of the manual modification, on the user interface (see Thema4 User Manual)
6.3.5 Analog Output

DATA MODBUS OPC
1 Analog output 1 sb x x x x x x RW 0.5s 0240 NLAO1 VT_UI2
… … … … … … … … … … … … …
99 Analog output 99 sb x x x x x x RW 0.5s 0338 NLAO99 VT_UI2
11 free 0339…0349
40240..40249 – Analog output 1..99

Each WORD indicates the output value in hundreds of mA. It accepts the values from 400 to 2000.
…
40240 40338
NLAO(1) NLAO(99)

6.4 ALARMS
6.4.1 Alarms management

For each alarm are available three nicode signals:
- ALL Bit of the alarm “cause” : managed by Thema4 and only read by SCADA.
- ACK Bit of alarm “acknowledgment “ : managed by Thema4 (Local mode) or by SCADA (Remote mode) and reset by Thema4
- ALM Bit of the alarm “active state” : managed by Thema4 and only read by SCADA.
It can be “retained” or not, depending on the configuration of the Thema4 option “Retained alarms”.
Moreover, there is an alarm selection word (1350) and there are two “command register” words, the first one (1351) to acknowledge the selected alarm or to
reset all the “retained” alarms, the second one (1352) to change the Alarms effects and delays or the Parameters of the Configuration alarms.
N° FUNZIONE Sub-function Modbus address R/W Note

1 Alarm state Bit of alarm “cause” and 0350..0387 R SCADA can examine the bit in order to extract the table with the alarm status.
(ALL+ACK) bit of “acknowledge” Hour and date will depend on the hour and date of the SCADA system.
2 Alarms effects and Alarm effects and 0390..0989 RW SCADA can read or force the alarm “effects” and delay
delay activation delays
3 Parameters for Configuration alarm 0990..0995 R/W SCADA can read or force the parameters of each “Configuration alarm”
Configuration parameters …….
alarms (type C) 1344..1349
4 Alarm number Alarm number 1350 R/W SCADA can write the number of the alarm to acknowledge or to reset
selection (it is set to zero after the writing of the command)
5 “Command Command to acknowledge 1351 R/W SCADA can write:
register” for the alarm (ACK) and to - “1” (immediately put to zero) to acknowledge the selected alarm (1350)
Acknowledgment / reset retained alarm - “2” (immediately put to zero) to reset all the retained active alarms.
reset
6 “Command Command to change the 1352 R/W SCADA can write:
register” for Alarms effects and delays - “1” (immediately put to zero) to save changes made to Alarms effects and
alarms or the Parameters of the delays for all alarms
configuration Configuration alarms - “10” (immediately put to zero) to save changes made to Parameters of the
Configuration alarms
7 Alarm active state Active” state of the alarm 1360..1378 R SCADA can examine the bit in order to extract the table, with the “active”
(ALM) alarm status (retained or not).
Hour and date will depend on the hour and date of the of the SCADA system.

6.4.2 Alarms state (ALL+ACK)

DATA MODBUS OPC
1 Alarms state: ALL+ACK (1..8) sb x x x x x x R 0350 ALARMS.ALL1 , ALARMS.ACK1 VT_BOOL
0.5s …
ALARMS.ALL8, ALARMS.ACK8
… … … x x x x x x … … … … …
38 Alarms state: ALL+ACK sb x x x x x x R 0387 ALARMS.ALL297, ALARMS.ACK297 VT_BOOL
(297..300) 0.5s …
ALARMS.ALL300, ALARMS.ACK300
39 free 0388 – 0389
40350..40387 – Alarms state and acknowledge 1..300

Each WORD utilizes one couple of bits. The first bit (status) indicates if the alarm is active (1 is ON, 0 is OFF), while the second bit (ack) indicates if the alarm has
been acknowledged (1 is ACK, 0 is NACK)..
15 … 15 …
…
40350 40387
alarm(8) … alarm(1) alarm(300) … alarm(297)
ALL = STATUS
ACK = ACKNOWLEDGE

6.4.3 Alarms effects and delay

DATA MODBUS OPC
1 Effect & delay alarm 1 sb x x x x x x RW variation 0390..0391 ALARMCONFIG.EFFECTANDDELAY1 VT_UI4
2 Effect alarm 1 sb x x x x x x RW variation 0390 ALARMCONFIG1.EFFECT VT_UI2
3 Delay alarm 1 sb x x x x x x RW variation 0391 ALARMCONFIG1.DELAY VT_UI2
… ….. … … … … … … … … … … …
599 Effect & delay alarm 300 sb x x x x x x RW variation 0988..0989 ALARMCONFIG.EFFECTANDDELAY300 VT_UI4
600 Effect alarm 300 sb x x x x x x RW variation 0988 ALARMCONFIG300.EFFECT VT_UI2
601 Delay alarm 300 sb x x x x x x RW variation 0989 ALARMCONFIG300.DELAY VT_UI2
40390..40989 – Effect & delay alarm 1..300

For every alarm 2 WORDs are defined. The first WORD is utilized as bit to bit and indicates which effects (a,b,c,..) have been assigned to the alarm (1 means:
effect is assigned; 0 means: effects is not assigned). The second WORD indicates the alarm delay in tenths of a second.
15 …
ponmlihgfedcb
40390 40391
alarm(1) alarm(1)
…
15 …
ponmlihgfedcb
40988 40989
alarm(300) alarm(300)

6.4.4 Configuration alarms parameters

DATA MODBUS OPC
1 1° Configuration alarm - N° sb x x x x x x RW 0990..0995 ALARMCONFIG.CONFIGURATION1.NALL VT_UI2
alarm RW ALARMCONFIG.CONFIGURATION1.NLI VT_UI2
- NLI RW ALARMCONFIG.CONFIGURATION1.NLO VT_UI2
Variation
- NLO RW ALARMCONFIG.CONFIGURATION1.LOG VT_UI2
- LOG RW ALARMCONFIG.CONFIGURATION1.AUX VT_UI2
- AUX RW ALARMCONFIG.CONFIGURATION1.SCM VT_UI2
- SCM
… … … … … … … … … … … … …
60 60° Configuration alarm - N° sb x x x x x x RW 1344..1349 ALARMCONFIG.CONFIGURATION60.NALL VT_UI2
alarm RW ALARMCONFIG.CONFIGURATION60.NLI VT_UI2
- NLI RW ALARMCONFIG.CONFIGURATION60.NLO VT_UI2
Variation
- NLO RW ALARMCONFIG.CONFIGURATION60.LOG VT_UI2
- LOG RW ALARMCONFIG.CONFIGURATION60.AUX VT_UI2
- AUX RW ALARMCONFIG.CONFIGURATION60.SCM VT_UI2
- SCM
40990..41349 – Configuration alarm 1..60

For each configuration alarm are defined 6 WORDs.
- The 1° WORD indicates the associated alarm number (accepts values from 1 to 300; 0 means: not configured).
- The 2° WORD indicates the associated input logic number (accepts values from 1 to 1000; 0 means: not assigned).
- The 3° WORD indicates the associated output logic number(accepts values from 1 to 1000; 0 means: not assigned).
- The 4° WORD indicates the alarm logic (accepts values from 0 to 3).
- The 5° WORD indicates the auxilliary logic number (accepts values from 1 to 1000; 0 means: not assigned).
The 6° WORD indicates the modulation control thres-hold (accepts values from 400 to 2000; 0 means: not assigned).
N° ALL NLI NLO LOG AUX SCM
40990 40991 40992 40993 40994 40995

1° alarm 1° alarm 1° alarm 1° alarm 1° alarm 1° alarm
…
N° ALL NLI NLO LOG AUX SCM
41344 41345 41346 41347 41348 41349

60° alarm 60° alarm 60° alarm 60° alarm 60° alarm 60° alarm

6.4.5 “Command register” for alarms acknowledge/reset

DATA MODBUS OPC
1 Number of the alarm to acknowledge sb x x x x x x RW variation 1350 ALARMCONFIGCNTRL.NUMBERTOACK VT_UI2
2 Alarm ack/reset command register sb x x x x x x RW variation 1351 ALARMCONFIGCNTRL.ACK VT_UI2
SCADA can acknowledge a specific alarm, by inserting the value in the “Number of the alarm to acknowledge“ and setting the “ack/reset command register”
tag to “1”.
Thema4 confirms the execution of this operation by resetting both the “ack/reset command register” and “Number of the alarm to acknowledge” tags to “0”.
SCADA can acknowledge all the alarms, by setting the “ack/reset command register” tag to “3”.
Thema4 confirms the execution of this operation by resetting both the “ack/reset command register” and “Number of the alarm to acknowledge” tags to “0”.
SCADA can reset the retained active alarms, by setting the “command register” tag to “2”.
Thema4 confirms the execution of this operation by resetting the “command register” tag to “0”.
SCADA can acknowledge the alarms one by one or all together and reset the alarms all together exactly as for the Thema4 GUI.
IMPORTANT NOTE
41350..41351 – Alarm acknowledge

These two WORDs are both Read\Write and must be used together to acknowledge alarms. To acknowledge an alarm write the number of the alarm (from 1 to
300) to be acknowledged in the first register and then write 1 in the second register. Alternatively all the alarms can be acknowledged by writing 3 in the second
register. The second register can be used to reset the bit table of ALM just writing 2 into it. When the command is acquired the fields are cleared.
Number of the alarm Acknowledge command
41350 41351

6.4.6 “Command register” for alarms configuration

DATA MODBUS OPC
1 Alarms parameters command sb x x x x x x RW variation 1352 ALARMCONFIGCNTRL.COMMAND VT_UI2
register
2 free 1353..1359
The user can change the ”Alarms effects and delays”, by inserting the new values in these tags and setting the “command register” tag to “1”.
Thema4 confirms he execution of is operatio by resetting the “command register” tag to “0”.
The user can change the “Configuration alarm”, by inserting the new values in these tags and setting the “command register” tag to “10”.
Thema4 confirms the execution of is operation by resetting the “command register” tag to “0”.
IMPORTANT NOTE

6.4.7 Alarms active state (ALM)

DATA MODBUS OPC
1 Active alarm state (1..16) sb x x x x x x R 0.5s 1360 ALARMS.ALM1 … ALARMS.ALM16 VT_BOOL
… … … x x x x x x … … … … …
19 Active alarm state (289..300) sb x x x x x x R 0.5s 1378 ALARMS.ALM289 … ALARMS.ALM300 VT_BOOL
20 free 1379…1499
If the retained-option is not configured (see Thema4 User Manual: options) on Thema4 system, an alarm is active (and displayed in Active alarm list) until both
the following conditions are not verified:
- bit ALL is “OFF” (alarm no more present)
- bit ACK is “ON” (alarm acknowledged)
When the alarm is no more active ALM=0.
If the retained-option is configured on Thema4 system, an alarm is retained active even when both the following conditions are true:
- bit ALL is “OFF” (alarm no more present)
- bit ACK is “ON” (alarm acknowledged)
The alarm remains active (ALM=1) until the reset command is received.
IMPORTANT NOTE
The “Retained alarms option” can be necessary, if the SCADA needs to acquire all the alarm events, included the alarms with effects auto-off
and auto-ack, that could be lost, in the Thema4-SCADA communication, because too fast.
41360..41378 – Active alarm status 1..300

This area is a bit table that holds the ALM bit for every alarm.
15 … 15 …
…
41360 41378
ALM

6.5 CURRENT PROCESS DATA

DATA MODBUS OPC
1 NL of chamber TP in use Num (W) x x R 0.5s 1500 PROCESS.TPNUMBER VT_UI2
2 Current phase progressive number Num (W) x x x x x x R 0.5s 1501 “ .PHASENUMBER VT_UI2
3 Current “progressive run time” 10xsec (DW) x x x x x x R 0.5s 1502..1503 “ .PTT VT_UI4
4 Current “phase time” 10xsec (DW) x x x x x x R 0.5s 1504..1505 “ .FTT VT_UI4
5 Current target Fo 10xsec (DW) (#1) x R 0.5s 1506..1507 “ .TARGETF0 VT_UI4
6 Current target Ft 10xsec (DW) (#1) x R 0.5s 1508..1509 “ .TARGETFT VT_UI4
7 Current target Fh 10xsec (DW) (#1) x R 0.5s 1510..1511 “ .TARGETFH VT_UI4
8 Time target 10xsec (DW) (#1) x x x x x x R 0.5s 1512..1513 “ .TARGETTIME VT_UI4
9 Pressure target hPa (W) (#2) x x R 0.5s 1514 “ .TARGETP VT_UI2
10 Temperature target 100x°C (W) (#3) x x R 0.5s 1515 “ .TARGETT VT_UI2
“ .TARGETT_ VT_I2
11 Humidity target ‰ (W) x x x R 0.5s 1641 “ .TARGETHUMIDITY VT_UI2
12 VHP concentration target 10xppm (W) x x x R 0.5s 1642 “ .TARGETVHP VT_UI2
12 Current exposure time 10xsec (DW) x x R 0.5s 1516..1517 “ .EXPOSURE VT_UI4
13 Chamber pressure hPa (W) x x R 0.5s 1518 “ .PCHAMBER VT_UI2
“ .PCHAMBER_ VT_I2
14 Jacket temperature 100x°C (W) x R 0.5s 1519 “ .TJACKET VT_UI2
“ .TJACKET_ VT_I2
15 Steril side pressure hPa (W) x R 0.5s 1520 “ .PSTERILSIDE VT_UI2
“ .PSTERILSIDE_ VT_I2
16 Max steril side pressure hPa (W) x R 0.5s 1521 “ .PMAXSTERILSIDE VT_UI2
“ .PMAXSTERILSIDE_ VT_I2
17 Temperature of TE1 (#4) 100x°C (W) x x x R 1522 “ .T1 VT_UI2
0,5s
“ .T1_ VT_I2
… … … … … … … … … … … … …
33 Temperature of TE16 100x°C (W) x x x R 1537 “ .T16 VT_UI2
0,5s
“ .T16_ VT_I2
34 Fo of TE1 (#4) 10xsec (DW) x R 0,5s 1538-1539 “ .F01 VT_UI4
… … … … … … … … … … … … …
65 Fo of TE16 10xsec (DW) x R 0,5s 1568-1569 “ .F016 VT_UI4
66 Fh of TE1 (#4) 10xsec (DW) x R 0,5s 1570-1571 “ .FH1 VT_UI4
… … … x … … … … … … … …
97 Fh of TE16 10xsec (DW) x R 0,5s 1600-1601 “ .FH16 VT_UI4
98 Ft of TE1 (#4) 10xsec (DW) x R 0,5s 1602-1603 “ .FT1 VT_UI4
… … … … … … … … … … … … …
129 Ft of TE16 10xsec (DW) x R 0,5s 1632-1633 “ .FT16 VT_UI4

DATA MODBUS OPC

130 Value of generic PROBE1 (#6) x x x x x x R 1643 “ .PROBE1 VT_UI2
0,5s
“ .PROBE1_ VT_I2
… … … … … … … … … … … … …
145 Value of generic PROBE16 (#6) x x x x x x R 1658 “ .PROBE16 VT_UI2
0,5s
“ .PROBE16_ VT_I2
146 Current pressure value hPa (W) x x x R 0.5s 1659 “ .P_VAL VT_UI2
147 NL of current pressure value Num (W) x x x R 0.5s 1660 “ .P_NL VT_UI2
148 Current Temperature value 100x°C (W) x x x x R 0.5s 1661 “ .T_VAL VT_UI2
149 NL of current temperature value Num (W) x x x x R 0.5s 1662 “ .T_NL VT_UI2
150 Current Humidity value ‰ (W) x x x R 0.5s 1663 “ .H_VAL VT_UI2
151 NL of current Humidity value Num (W) x x x R 0.5s 1664 “ .H_NL VT_UI2
152 Current VHP concentration 10xppm (W) x x x R 0.5s 1665 “ .VHP_VAL VT_UI2
153 NL of current VHP concentration Num (W) x x x R 0.5s 1666 “ .VHP_NL VT_UI2
154 ID of the P/G being executed Num (W) x x x x x x R 0.5s 1634 PROCESS.PGNUM VT_UI2
155 Phase number of the P/G being executed Num (W) x x x x x x R 0.5s 1635 “ .PGPHASENUM VT_UI2
156 Remaining sterilization time(time based) Num (W) x x R 0.5s 1636..1637 “ .REMAININGSTERILTIME VT_UI4
157 Five letters code of the P/G being executed (#5) String x x x x x x R 0.5s 1638..1640 “ .PGCODE VT_BSTR[6]
158 Conductivity target us or ms (W) x x x R 0.5s 1667 “ .TARGETCOND VT_UI2
159 Conductivity current value us or ms (W) x x x R 0.5s 1668 “ .COND_VAL VT_UI2
160 Logic number of conductivimeter us or ms (W) x x x R 0.5s 1669 “ .COND_NL VT_UI2
161 Scale of conductivimeter Num (W) x x x R 0.5s 1670 “ .COND_SCALE VT_UI2
162 Disinfection actual value 10xsec (DW) x R 0.5s 1671 “ .DISINFECTION VT_UI4
163 Disinfection target 10xsec (DW) x R 0.5s 1673 “ .TARGETA0 VT_UI4
164 Remaining Time 10xsec (DW) x x x x x x R 0.5s 1675 “ .REMAININGTIME VT_UI4
165 Free 1676…1679
166 Target level tank 1 ml (W) x x x R 0.5s 4432 “ .TARGETLEVEL1 VT_UI2
171 Level value tank 1 ml (W) x x x R 0.5s 4437 “ .LEVEL1_VAL VT_UI2

176 Logic number level 1 Num (W) x x x R 0.5s 4442 “ .LEVEL1_NL VT_UI2
181 Disinfection value probe 1 10xsec (DW) x R 0.5s 4447 “ .PROCESS.A01 VT_UI4
#1: value is 2147483647 if there is no target

#4: note that TE1 does not identify the TE with logic number 1 (NLAI1) but the first TE programmed in the TE list of the running program. For this reason the logic
number associated to TE1 can be different depending on the program being executed.
#5: note that both the ID (PROCESS.PGNUM) and the five letters code (PROCESS.PGCODE) can be used to identify the P/G being executed: the ID is safe only
if the sterilizer does not have P/Gs with the same number, while the five letters code identify exactly the P/G even across different P/G libraries.
#6: the unit of measure depends by the type of probe programmed in the Probe List: if it is a predefined type it will have the canonical representation
(temperature, pressure...); if it is programmable it will be represented accordingly to the definition (visible ciphers defined in the format field).
IMPORTANT NOTE
For some data, OPC provide the value in two different formats: VT_UI2 or VT_I2.

IMPORTANT NOTE
The value of the CURRENT PHASE PROGRESSIVE NUMBER is always less that 1 unit regarding the value showed in the THEMA4 because in
the Modbus/OPC this value starts from 0 and not from 1 (Prepare autoclave).

6.6 PARAMETERS OF THE LOADED PROGRAMS
6.6.1 Program identification data

DATA MODBUS OPC
1 Program description String x x x x x x R at prog.loading 1680..1699 RUNPROG.DESCRIPTION VT_BSTR[40]
Unicode Str. 2194..2233 “ .DESCRIPTION_U VT_BSTR[40]
2 Program number Num (W) x x x x x x R at prog.loading 1700 RUNPROG.NUMBER VT_UI2
3 Programmer public name String x x x x x x R at prog.loading 1701..1726 RUNPROG.PROGRAMMER VT_BSTR[52]
Unicode Str. 2234..2285 “ .PROGRAMMER_U VT_BSTR[52]
4 Program Status String x x x x x x R at prog.loading 6290 RUNPROG.PROGSTATUS VT_UI2
5 Program Status Description String x x x x x x R at prog.loading 6291..6300 “ . “ .DESC VT_BSTR[20]
Unicode Str. 6301..6320 “ . “ .DESC_U VT_BSTR[20]
6.6.2 Program parameters: General

DATA MODBUS OPC
1 Automatic program start Bit G6 G8 G3 G3 G5 G2 R at prog.loading 1727.0 RUNPROG.AUTOMATICSTART VT_BOOL
2 Final temperature check Bit G9 G8 R at prog.loading 1727.1 “ .CHECKTFINAL VT_BOOL
3 Auxiliary heating enabled Bit x R at prog.loading 1727.2 “ .AUXILIARYHEATING.USE VT_BOOL
4 Air detector enabled Bit x R at prog.loading 1727.3 “ .AIRDETECTOR.USE VT_BOOL
5 Steam generator enabled Bit x G12 R at prog.loading 1727.4 “ .STEAMGENERATOR.USE VT_BOOL
6 H2O sterilizer enabled Bit x R at prog.loading 1727.5 “ .H2OSTERILIZER.USE VT_BOOL
7 Fan speed low Bit G6 R at prog.loading 1727.6 “ .FANSPEEDLOW VT_BOOL
8 Auxiliary cooling system Bit x R at prog.loading 1727.7 “ .AUXILIARYCOOLING VT_BOOL
9 Utilities management Bit x R at prog.loading 1727.8 “ .UTILTIY.USE VT_BOOL
10 Calculate F0 for monitoring Bit x R at prog.loading 1727.9 “ .F0ALL VT_BOOL
probes
11 Use Tmax for cycle Bit x x x x x x R at prog.loading 1727.10 “ .BASECYCLE.USETMAX VT_BOOL
12 Has customer document Bit x x x x x x R at prog.loading 1727.11 “ .CUSTOMDOC VT_BOOL
13 Require read ack of customer Bit x x x x x x R at prog.loading 1727.12 “ .CUSTOMDOCKREADACK VT_BOOL
document
14 Require read ack on all pages of Bit x x x x x x R at prog.loading 1727.13 “ VT_BOOL
customer document .CUSTOMDOCREADACKALLPAGES
15 free 1727.14...17 VT_BOOL
27.15
16 Pressure scale Num (W) G1 G1 R at prog.loading 1728 “ .SCALEP VT_UI2
17 Temperature scale Num (W) G2 G2 G1 R at prog.loading 1729 “ .SCALET VT_UI2

18 Time scale Num (W) G3 G3 G1 G1 G2 G1 R at prog.loading 1730 “ .SCALETIME VT_UI2
19 Sterilization type (treatment contr) Num (W) G4 G5 G3 R at prog.loading 1731 “ .TREATMENT VT_UI2
20 Door open sequence Num (W) G5 G4 G2 G2 G4 R at prog.loading 1732 “ .DOORSEQUENCE VT_UI2
21 Maximum blackout time 10xsec (DW) G7 G10 G6 R at prog.loading 1733..1734 “ .MAXBOTIMEF0 VT_UI4
22 Max blackout time Ft 10xsec (DW) x R at prog.loading 1735..1736 “ .MAXBOTIMEFT VT_UI4
23 Max blackout time Fh 10xsec (DW) x R at prog.loading 1737..1738 “ .MAXBOTIMEFH VT_UI4
24 Cycle end alert time 10xsec (DW) G8 G7 G4 G4 G7 G3 R at prog.loading 1739..1740 “ .ENDALERTTIME VT_UI4
25 Print interval multiplier Num (W) G10 G9 G5 G5 G9 G4 R at prog.loading 1741 “ .PRINTMULTIPLIER VT_UI2
26 Executability level Num (W) G11 G6 G6 G10 G5 R at prog.loading 1742 “ .EXECLEVEL VT_UI2
27 Interlock level Num (W) G12 G7 G7 G11 G6 R at prog.loading 1743 “ .INTERLOCKLEVEL VT_UI2
28 Golden Cycle enable Bit G19 G11 G8 G8 G13 G7 R at prog.loading 6225.0 “ .GOLDENCYCLE.USE VT_BOOL
29 Spatial and temporal uniformity Bit G20 G12 R at prog.loading 6225.1 “ .SUTU.USE VT_BOOL
30 Spatial uniformity tolerance 100x°C (W) G20. G12.1 R at prog.loading 6226 “ .SUTU.SUTOLERANCE VT_UI2
1
31 Temporal uniformity tolerance 100x°C (W) G20. G12.2 R at prog.loading 6227 “ .SUTU.TUTOLERANCE VT_UI2
2
32 Saturated Steam control Bit G21 R at prog.loading 6225.2 “ .PVSAT.USE VT_BOOL
33 Equilibration time check Bit G22 R at prog.loading 6225.3 “ .EQTIME.USE VT_BOOL
34 Parametric Release table check Bit G23 G13 G9 G9 G14 G8 R at program end 6225.4 “ .PRT.USE VT_BOOL
35 Equilibration time start probe Num (W) G22. R at prog.loading 6228 “ .EQTIME.TESTART VT_UI2
1
36 Max equilibration time 10xsec (DW) G22. R at prog.loading 6229..6230 “ .EQTIME.MAXEQTIME VT_UI4
2
37 Enable F(T,z) calc. for monit. TE Bit G24 R at prog.loading 1727.9 “ .F0ALL VT_BOOL
38 Show Procedures Bit G25 G14
G1 G1
G15 G9 R at prog.loading 1727.11 “ .CUSTOMDOC VT_BOOL
0 0
6.6.3 Program parameters: Sterilization

DATA MODBUS OPC
1 Min treatment temperature 100x°C (W) S1.1, S2.1, S1.1, S2.1, R at 1744 RUNPROG.TMINTREATMENT VT_UI2
S3.1 S3.1 prog.loading
2 Max treatment temperature 100x°C (W) S1.2, S2.2, S1.2, S2.2, R at 1745 “ .TMAXTREATMENT VT_UI2
3 Control temperature 100x°C (W) S1.3, S2.3, S1.3, S2.3, R at 1746 “ .TCONTROL VT_UI2
4 Exposure time 10xsec(DW) S1.4, S2.4 S1.4, S2.4 R at 1747..1748 “ VT_UI4
prog.loading .EXPOSURETIMETREAMENT
5 Max off time sterilization 10xsec(DW) S1.5, S2.5, S1.5, S2.5, R at 1749..1750 “ .MAXOFFTIMETREATMENT VT_UI4
6 Max execution time 10xsec(DW) S1.6, S2.6, S1.6, S2.6, R at 1751..1752 “ VT_UI4
sterilization S3.6 S3.6 prog.loading .MAXEXECTIMETREATMENT

7 Min tyndall. Temperature 100x°C (W) S5.1 R at 1753 “ .TMINTYNDAL VT_UI2
prog.loading
8 Tyndall. Exposure time 10xsec(DW) S5.2 R at 1754..1755 “ .EXPOSURETIMETYNDAL VT_UI4
prog.loading
9 Tyndall Max. suspension time 10xsec(DW) S5.3 R at 1756..1757 “ .MAXOFFTIMETYNDAL VT_UI4
prog.loading
10 Tyndall. Max execution time 10xsec(DW) S5.4 R at 1758..1759 “ .MAXEXECTIMETYNDAL VT_UI4
prog.loading
11 Fo target value 10xsec(DW) S3.4 R at 1760..1761 “ .F0TARGET VT_UI4
prog.loading
12 z coefficient for Fo 100xN (W) S2.7, S3.7 R at 1762 “ .F0Z VT_UI2
prog.loading
13 Refer. T for Fo calculation 100x°C (W) S2.8, S3.8 R at 1763 “ .F0TRIF VT_UI2
prog.loading
14 Fo calculation lowest 100x°C (W) S2.9, S3.9 R at 1764 “ .F0TCALC VT_UI2
temperature prog.loading
15 Ft target value 10xsec(DW) x R at 1765..1766 “ .FTTARGET VT_UI4
prog.loading
16 z coefficient for Ft 100xN (W) x R at 1767 “ .FTZ VT_UI2
prog.loading
17 Refer. T for Ft calculation 100x°C (W) x R at 1768 “ .FTRIF VT_UI2
prog.loading
18 Ft calculation lowest 100x°C (W) x R at 1769 “ .FTCALC VT_UI2
19 Fh target value 10xsec(DW) x R at 1770..1771 “ .FHTARGET VT_UI4
prog.loading
20 z coefficient for Fh 100xN (W) x R at 1772 “ .FHZ VT_UI2
prog.loading
21 Refer. T for Fh calculation 100x°C (W) x R at 1773 “ .FHRIF VT_UI2
prog.loading
22 Fh calculation lowest 100x°C (W) x R at 1774 “ .FHCALC VT_UI2
6.6.4 Program parameters: Auxiliary heating

DATA MODBUS OPC
1 Default temp. auxiliary heating 100x°C (W) G13.1 R at prog.loading 1775 RUNPROG.AUXILIARYHEATING.T VT_UI2
2 Temp. adjustment tolerance 100x°C (W) G13.2 R at prog.loading 1776 “ .AUXILIARYHEATING.TOLERANCE VT_UI2
3 Jacket temp. alarm tolerance 100x°C (W) G13.3 R at prog.loading 1777 “ .AUXILIARYHEATING.TALARM VT_UI2

6.6.5 Program parameters: Air detector

DATA MODBUS OPC
1 Air detector isolate press. hPa (W ) G14.1 R at prog.loading 1778 RUNPROG.AIRDETECTOR.PISOLATE VT_UI2
2 Air det. Warning pressure hPa (W ) G14.2 R at prog.loading 1779 “ .AIRDETECTOR.PWARNING VT_UI2
6.6.6 Program parameters: Steam generator

DATA MODBUS OPC
1 Max T steam generator 100x°C (W) G15.1 G12.1 R at prog.loading 1780 RUNPROG.STEAMGENERATOR.TMAX VT_UI2
2 Heating temp. diff. gap 100x°C (W) G15.2 G12.1 R at prog.loading 1781 “ .STEAMGENERATOR.TDIFF VT_UI2
6.6.7 Program parameters: H2O sterilization

DATA MODBUS OPC
1 H2O supply line flush. Time 10xsec(DW) G16.1 R at prog.loading 1782..1783 RUNPROG.H2OSTERILIZER.FLUSHTIME VT_UI4
2 Max. time loading H2O 10xsec(DW) G16.2 R at prog.loading 1784..1785 “ .H2OSTERILIZER.MAXLOADINGTIME VT_UI4
3 Max. time heating H2O 10xsec(DW) G16.3 R at prog.loading 1786..1787 “ .H2OSTERILIZER.MAXHEATINGTIME VT_UI4
4 H2O sterilization time 10xsec(DW) G16.4 R at prog.loading 1788..1789 “ .H2OSTERILIZER.STERILIZATIONTIME VT_UI4
5 H2O preheating temper. 100x°C (W) G16.5 R at prog.loading 1790 “ .H2OSTERILIZER.TPREHEATING VT_UI2
6 H2O steriliz. Temperature 100x°C (W) G16.6 R at prog.loading 1791 “ .H2OSTERILIZER.TSTERILIZATION VT_UI2
7 H2O steril. Temp. Toler. 100x°C (W) G16.7 R at prog.loading 1792 “ .H2OSTERILIZER.TOLERANCE VT_UI2
8 Ster.H2O pre-cooling temp. 100x°C (W) G16.8 R at prog.loading 1793 “ .H2OSTERILIZER.TPRECOOLING VT_UI2
6.6.8 Program parameters: Utility management

DATA MODBUS OPC
1 Utilities manag.: clean steam (CS) Bit G18.1 G11.1 G17.1 R at prog.loading 6042.0 RUNPROG.UTILITY.CLEANSTEAM VT_BOOL
2 Utilities manag.: plant steam (PS) Bit G18.2 G11.2 G17.2 R at prog.loading 6042.1 “ .UTILITY.PLANTSTEAM VT_BOOL
3 Utilities manag.: process air (PA) Bit G18.3 G11.3 G17.3 R at prog.loading 6042.2 “ .UTILITY.PROCESSAIR VT_BOOL
4 Utilities man.: water for inject. (WFI) Bit G18.4 G11.4 G17.4 R at prog.loading 6042.3 “ .UTILITY.WATERFORINJECTION VT_BOOL
5 Utilities manag.: purified water (PW) Bit G18.5 G11.5 G17.5 R at prog.loading 6042.4 “ .UTILITY.PURIFIEDWATER VT_BOOL
6 Utilities manag.: tap water (TW) Bit G18.6 G11.6 G17.6 R at prog.loading 6042.5 “ .UTILITY.TAPWATER VT_BOOL
7 Utilities manag.: chilled water (CW) Bit G18.7 G11.7 G17.7 R at prog.loading 6042.6 “ .UTILITY.CHILLEDWATER VT_BOOL
8 Utilities manag.: nitrogen (N2) Bit G18.8 G11.8 G17.8 R at prog.loading 6042.7 “ .UTILITY. NITROGEN VT_BOOL
9 Utilities manag.: Additive 1 Bit G18.9 G11.9 G17.9 R at prog.loading 6042.8 “ .UTILITY.ADDITIVE1 VT_BOOL

6.6.9 Program parameters: TP list

DATA MODBUS OPC
1 NL of TP displayed in pos. 1 Num (W) x x R at progr.loading 6026 RUNPROG.TP1 VT_UI2
… …. Num (W) x x ... at progr.loading … … VT_UI2
16 NL of TP displayed in pos. 16 Num (W) x x R at progr.loading 6041 “ .TP16 VT_UI2
17 Displayed TPs configured as “check “ (Golden Cycle package) sb x x R at progr.loading 6224 RUNPROG.TPCHECK VT_UI2
46026..46041 – Num (W)

These fields correspond to a Number Logic of TP memorized in position from 1 to 16. This number is memorized in single WORDs:
4xxxx
45358 – Displayed TPs configured as “check”

This is a word that is a bit table of the 16 displayed TEs, with the configuration as “check” probes. This applies only if Golden Cycle package is authorized.
15 …
45358
TP(16) … TP(1)
“Check” configuration Displayed TE in position 1
Displayed TE in position 2

6.6.10 Program parameters: TE list

DATA MODBUS OPC
1 No. of control Tes Num (W) S4.4 x R at progr.loading 1794 RUNPROG.TENUMBER VT_UI2
2 NL of TE displayed in pos. 1 Num (W) x x x R at progr.loading 1795 “ .TE1 VT_UI2
… .... ... ... ... ... ... ... ... ... … … VT_UI2
17 NL of TE displayed in pos. 16 Num (W) x x x R at progr.loading 1810 “ .TE16 VT_UI2
18 Displayed Tes config. As “Product Tes” sb x x x R at progr.loading 1811 RUNPROG.TEPRODUCT VT_UI2
19 Displayed Tes config. As “Immers. Tes” sb x x R at progr.loading 1812 RUNPROG.TESAFETY VT_UI2
20 Displayed Tes configured as “check “ (Golden Cycle package) sb x x x R at progr.loading 6223 RUNPROG.TECHECK VT_UI2
41795..41810 – Num (W)

These fields correspond to a Number Logic of TE memorized in position from 1 to 16. This number is memorized in single WORDs:
4xxxx
41811..41812, 46223 – Displayed TEs configuration
These are three words that are a bit table of the 16 displayed TEs, with the configuration as “Product” probes (1811), “Immersion” probes (1812) and “check”
probes.
15 … 15 …
41811 41812
TE(16) … TE(1) Displayed TE in position 1 TE(16) … TE(1) Displayed TE in position 1
“Product” configuration “Immersion” configuration
Displayed TE in position 2 Displayed TE in position 2
15 …
46223
TE(16) … TE(1) Displayed TE in position 1
“Check” configuration
Displayed TE in position 2

6.6.11 Program parameters: PROBE list

DATA MODBUS OPC
1 NL of PROBE displayed in pos. 1 Num (W) x x x x x x R at progr.loading 6271 “ .PROBE1 VT_UI2
… .... ... ... ... ... ... … ... ... … … VT_UI2
16 NL of PROBE displayed in pos. 16 Num (W) x x x x x x R at progr.loading 6286 “ .PROBE16 VT_UI2
17 Displayed PROBEs config. As “Trend” sb x x x x x x R at progr.loading 6287 RUNPROG.PROBETREND VT_UI2
18 Displayed PROBEs config. As “Check” sb R at progr.loading 6288 RUNPROG.PROBECHECK VT_UI2
46271..46286 – Num (W)

These fields correspond to a Number Logic of PROBEs memorized in position from 1 to 16. This number is memorized in single WORDs:
4xxxx
46287, 46288 – Displayed PROBEs configuration
These are two words that are a bit table of the 16 displayed PROBEs, with the configuration as “Trend” probes (6287) and “check” probes (currently not
implemented).
15 … …0
46287
PROBE(16) … PROBE(1) Displayed PROBE in position 1
“Trend” configuration
Displayed PROBE in position 2
15 … …0
46288
PROBE(16) … PROBE(1) Displayed PROBE in position 1
“Check” configuration
Displayed PROBE in position 2

6.6.12 Program parameters: PID parameters

DATA MODBUS OPC
1 DAO : Default analog value 4-20mA x x x x x x R at 1813 RUNPROG.DAO VT_UI2
progr.loading
2-9 PID1: integral parts of P,I,D and PID x x x x x x R at 1814..1821 “ .PID1.P, .I, .D, .UMAX, .UMIN, .U0, .AR, VT_UI2
UMAX,UMIN,U0,AR,AD (8W) progr.loading .AD
10- PID2: integral parts of P,I,D and PID x x x x x x R at 1822..1829 “ .PID2.P, .I, .D, .UMAX, .UMIN, .U0, .AR, VT_UI2
17 UMAX,UMIN,U0,AR,AD (8W) progr.loading .AD
42 PID1: reversed action Bit x x x x x x R at 6289.0 “ .PID1.INVERT VT_BOOL
progr.loading
progr.loading
progr.loading
progr.loading
progr.loading
47- PID1: fractional parts of P,I,D PID x x x x x x R at 6321..6323 “ .PID1.P_DECIMAL, .I_DECIMAL, VT_UI2
49 (3W) progr.loading .D_DECIMAL

4-20mA (W) - DAO: Default analog value

These fields correspond to current values in the range 4...20mA (values are from 400 to 2000) memorized in single WORDs:
xx.xx mA
4xxxx
PID (8W) - The following fields correspond to the values of a “PID column”, memorized in 8 WORDs, where P, I and D carry only the integral part:
- PID 1: P,I,D,UMAX,UMIN,U0,AR,AD
P * 100 I * 10 D * 10 400..2000 400..2000 400..2000 0..100 0..100
41814 41815 41816 41817 41818 41819 41820 41821

PID1: P PID1: I PID1: D PID1: UMAX PID1: UMIN PID1: U0 PID1: AR PID1: AD
…
P * 100 I * 10 D * 10 400..2000 400..2000 400..2000 0..100 0..100
41846 41847 41848 41849 41850 41851 41852 41853

PID6: P PID6: I PID6: D PID6: UMAX PID6: UMIN PID6: U0 PID6: AR PID6: AD
PID (3W) - The following fields correspond to the values of a “PID column”, memorized in 3 WORDs, where P, I and D carry only the integral part:
- PID 1,2,3,4,5: P_DECIMAL,I_DECIMAL,D_DECIMAL
.xx P .x I .x D
The P parameter has two decimal ciphers (.xx)
The I parameter has one decimal cipher (.x)
46321 46322 46323 The D parameter has one decimal cipher (.x)
PID1: P PID1: I PID1: D
.xx P .x I .x D
46333 46334 46335

PID6: P PID6: I PID6: D

6.6.13 Program parameters: Procedures

DATA MODBUS OPC
1 Require read acknowledge Bit G25.1 G14.1 G10.1 G10.1 G15.1 G9.1 R at progr.loading 1727.12 RUNPROG.CUSTOMDOCREADACK VT_BOOL
2 Document Link String G25.2 G14.2 G10.2 G10.2 G15.2 G9.2 R at progr.loading 6336..6367 RUNPROG.LINK VT_BSTR[32]
6.6.14 Program parameters: Barcodes

DATA MODBUS OPC
1 Barcode 1 of loaded program String x x x x x x R at progr.loading 4500..4515 RUNPROG.BARCODE1 VT_BSTR[32]
2 ... … … … … … … … … ... ... ...
3 Barcode 12 of loaded program String x x x x x x R at progr.loading 4676..4691 “ .BARCODE12 VT_BSTR[32]
4 free 4692..4699
6.6.15 Program parameters: Base program cycle

DATA MODBUS OPC
1 Base program cycle : cycle ID String x x x x x x R at progr.loading 6000..6005 RUNPROG.BASECYCLE.ID VT_BSTR[12]
2 Base program cycle: cycle name String x x x x x x R at progr.loading 6006..6025 RUNPROG.BASECYCLE.NAME VT_BSTR[40]
Unicode Str. 6231..6270 RUNPROG.BASECYCLE.NAME_U VT_BSTR[40]
3 Base program cycle: use Tmax2 Bit x x R at progr.loading 1727.10 RUNPROG.BASECYCLE.USETMAX2 VT_BOOL
6.6.16 Program parameters: Phase time table

DATA MODBUS OPC
1 Enable phase time table Bit x x x x x x R at progr.loading 1727.14 RUNPROG.TMTBL.ENABLE VT_BOOL
2 Phase duration 1 Num (DW) x x x x x x R at progr.loading 32000 RUNPROG.TMTBL1.DURATION VT_UI4
... … … … … … … … … ... ... ...
3 Phase duration 80 Num (DW) x x x x x x R at progr.loading 32156 RUNPROG.TMTBL80.DURATION VT_UI4
4 Phase repetitions 1 Num (W) x x x x x x R at progr.loading 32158 RUNPROG.TMTBL1.REPS VT_UI2
... … … … … … … … … ... ... ...
5 Phase repetitions 80 Num (W) x x x x x x R at progr.loading 32236 RUNPROG.TMTBL80.REPS VT_UI2

6.7 COMPOSITION OF THE LOADED PROGRAM(READ ONLY)
6.7.1 List of the P/Gs parameters of the program

DATA MODBUS OPC
1 P/G variable parameters 1 - x x x x x x R at progr.loading 1854 RUNPROG.PAR1 VT_UI2
… … … … … … … … … … … … …
300 P/G variable parameters 300 - x x x x x x R at progr.loading 2153 “ .PAR300 VT_UI2
41854..42153 - List of the P/Gs parameters of the program

The following fields correspond to the parameters of P/G (300 WORDs), each parameter corresponds to a WORD:
- P/G variable parameters
xxxx xxxx
…
41854 42153
1° par. 300° par.
6.7.2 List of the P/Gs of the program

6.7.2.1 By P/G number
DATA MODBUS OPC
1 P/G N° of 1° phase – P/G N° of 2° phase - x x x x x x R at progr.loading 2154 RUNPROG.COMPOSITION1 VT_UI2
… … … … … … … … … … … …
40 P/G N° of 79° phase – P/G N° of 80°phase - x x x x x x R at progr.loading 2193 “ .COMPOSITION40 VT_UI2
41 free 2286..2299
42154..42193 - List of the P/Gs numbers of the program

The following fields correspond to the cycle phase sequence. Each WORD contains two phases, one BYTE for each phase. Each BYTE contains the P/G number of
the phase.
- Program composition
xxxx xxxx
…
42154 42193
phase 2 … phase 1 phase 80 .. phase 79

6.7.2.2 By P/G code

DATA MODBUS OPC
1 Five letters code of the 1° P/G String x x x x x x R at progr.loading 6043..6045 RUNPROG.BASECYCLE.PG1 VT_BSTR[6]
… … … … … … … … … … … …
60 Five letters code of the 60° P/G String x x x x x x R at progr.loading 6220..6222 “ .BASECYCLE.PG60 VT_BSTR[6]
41 Free 6271..6499
46043..46222 - List of the P/Gs codes of the program

The following fields correspond to the cycle phase group sequence. It is a list of up to 60 phase groups identified by their P/G codes. Differently by listing by
numbers, P/G codes are not repeated if the phase group has more than one phase, so it is exactly the cycle composition as can be seen through GUI interface.
xxxx xxxx
…
6043…6045 6220…6222
1° P/G 60° P/G

6.8 SYSTEM PARAMETERS
6.8.1 System parameters: General

DATA MODBUS OPC
1 Min. P atmos. Balance hPa (W) 1 RW variation 2300 SYSTEM.PMINATMOS VT_UI2
2 Max P atmos. Balance hPa (W) 2 RW variation 2301 “ .PMAXATMOS VT_UI2
3 Max. time atm. Balance 10xsec 3 RW variation 2302..2303 “ .TIMEMAXATMOS VT_UI4
(DW)
4 Min. Fo target 10xsec 4 RW variation 2304..2305 “ .F0MINTARGET VT_UI4
(DW)
5 Pogram interlock Bit 5 4 4 1 4 RW variation 2306.0 “ .PROGINTERLOCK VT_BOOL
6 Request machine acknowledge Bit 6 2 2 2 2 RW variation 2306.1 “ .MACHINEACK VT_BOOL
7 Enable immersion TE Bit 8 RW variation 2306.2 “ .TESAFETY VT_BOOL
8 Author program repeat Bit 9 RW variation 2306.3 “ .PROGREPLAY VT_BOOL
9 Steril side TP used Bit 5 RW variation 2306.4 “ .TPSTERILSIDE VT_BOOL
10 Door(s): manual (0) / motorized (1) Bit 10 7 12 RW variation 2306.5 “ .DOORS VT_BOOL
11 Enable steam generator Bit 12 9 RW variation 2306.6 “ .STEAMGENERATOR.USE VT_BOOL
12 Enable SCADA (ex Enable nicod) Bit 13 10 27 10 14 RW variation 2306.7 “ .MODBUS VT_BOOL
13 SCADA Protocol 0/3 13.1 10.1 27.1 10.1 14.1 RW variation 2445 “ .SCADAPROTOCOL VT_UI2
14 Enable write (ex Enable execution Bit 13.2 10.2 27.2 10.2 14.2 RW variation 2306.8 “ .MODBUSEXEC VT_BOOL
from nicod) (Ex (Ex
13.1) 10.1)
15 Enable SCADA connection alarm Bit 13.3 10.3 27.3 14.3 RW variation 2446.0 “ VT_BOOL
.SCADACONNECTIONALARM
16 On-line printer enabled Bit 15 12 29 15 RW variation 2306.9 “ .ONLINEPRINT VT_BOOL
17 Recoder enabled Bit 16.1 13.1 RW variation 2306.10 “ .RECORDER.USE VT_BOOL
18 Program group manag. Enabled Bit RW variation 2306.11 “ VT_BOOL
.PROGGROUPMANAGEMENT
19 Enable degasser Bit 12.5 RW variation 2306.12 “ .DEGASER.USE VT_BOOL
20 Enable barcode Bit 21 14 31 18 RW variation 2306.13 “ .BARCODE.USE VT_BOOL
21 Enable sntp Bit 22 15 32 19 RW variation 2306.14 “ .SNTP.USE VT_BOOL
22 Enable daylight saving time (DST) Bit 23 16 33 20 RW variation 2306.15 “ .DST.USE VT_BOOL
23 Identify machine - 7 9 3 3 3 RW variation 2307..2314 “ .MACHINEID VT_BSTR[16]
24 Enable safety TP2 Bit 25 RW variation 2446.1 “ .SAFETYTP2 VT_BOOL
25 Enable SQL integration Bit 26 18 35 22 RW variation 2446.2 “ .SQL.USE VT_BOOL
26 Enable PV water loop Bit 27 RW variation 2446.3 “ .PVLOOP.USE VT_BOOL
27 Enable retained alarms Bit 28 19 36 30 23 RW variation 2446.4 “ .RETAINEDALARMS.USE VT_BOOL
28 free 2447.0..
2446.15

29 H2O2 threshold for door opening 10xppm 1 1 1 RW variation 5816 “ .VHP.DOOROPENING VT_UI2
30 Chamber (isolator) pressure Pa 5 5 RW variation 5817 “ .VHP.CHAMBER.P VT_UI2
31 Min chamber (isolator) pressure Pa 6 5 6 RW variation 5818 “ .VHP.CHAMBER.PMIN VT_UI2
32 Max chamber (isolator) pressure Pa 7 6 7 RW variation 5819 “ .VHP.CHAMBER.PMAX VT_UI2
33 Chamber temperature 100x°C 8 7 RW variation 5820 “ .VHP.CHAMBER.T VT_UI2
34 Min chamber temperature 100x°C 9 8 RW variation 5821 “ .VHP.CHAMBER.TMIN VT_UI2
35 Max chamber (isolator) 100x°C 10 9 8 RW variation 5822 “ .VHP.CHAMBER.TMAX VT_UI2
temperature
36 Hex temperature gap 100x°C 11 RW variation 5823 “ .VHP.CHAMBER.THEXGAP VT_UI2
37 Technical area depressure Pa 12 RW variation 5824 “ .VHP.TECHAREA.P VT_UI2
38 Max technical area depressure Pa 13 RW variation 5825 “ .VHP.TECHAREA.PMAX VT_UI2
39 Max heater temperature 100x°C 14 RW variation 5826 “ .VHP.HEATER.TMAX VT_UI2
40 Heater off temperature 100x°C 15 RW variation 5827 “ .VHP.HEATER.TOFF VT_UI2
41 Heater on temperature 100x°C 16 RW variation 5828 “ .VHP.HEATER.TON VT_UI2
42 Min heater temperature 100x°C 17 RW variation 5829 “ .VHP.HEATER.TMIN VT_UI2
43 Min pressure expulsion line Pa 18 RW variation 5830 “ .VHP.EXPULSIONLINE.PMIN VT_UI2
44 Min pressure compr.air line hPa 19 9 RW variation 5831 “ .VHP.COMPRAIR.PMIN VT_UI2
45 Min pressure hepa filter in Pa 20 16 RW variation 5832 “ .VHP.HEPAFILTER.IN.PMIN VT_UI2
46 Max pressure hepa filter in Pa 21 17 RW variation 5833 “ .VHP.HEPAFILTER.IN.PMAX VT_UI2
47 Min pressure nic filter out Pa 22 RW variation 5834 “ VT_UI2
.VHP.HEPAFILTER.OUT.PMIN
48 Max pressure nic filter out Pa 23 RW variation 5835 “ VT_UI2
.VHP.HEPAFILTER.OUT.PMAX
49 Heat exchanger temperature gap 100x°C 10 RW variation 5948 “ .DMD.THEXGAP VT_UI2
50 Min pressure biocide tank Pa 11 RW variation 5949 “ .TANK.PMIN VT_UI2
51 Max pressure biocide tank Pa 12 RW variation 5950 “ .TANK.PMAX VT_UI2
52 Min pressure nozzle Pa 13 RW variation 5951 “ .NOZZLE.PMIN VT_UI2
53 Max pressure nozzle Pa 14 RW variation 5952 “ .NOZZLE.PMAX VT_UI2
54 Inlet fan speed mA 15 RW variation 5953 “ .DMD.INLETFANSPEED VT_UI2
55 Enable Customer Procedures Bit 32 23 40 34 27 RW variation 2446.14 “ .CUSTOMDOC VT_BOOL
56 Enable Program Status Bit 31 22 39 33 21 26 RW variation 2446.10 SYSTEM.PROGSTATUS.USE VT_BOOL
57 Program Status Level 3 Use Bit 31.4 22.4 39.4 33.4 21.4 26.4 RW variation 2446.11 “ .PROGSTATUS.LEVEL3.USE VT_BOOL
58 Program Status Level 2 Back Bit 31.3 22.3 39.3 33.3 21.3 26.3 RW variation 2446.12 “ VT_BOOL
.PROGSTATUS.LEVEL2.BACK
59 Program Status Level 3 Back Bit 31.6 22.6 39.6 33.6 21.6 26.6 RW variation 2446.13 “ VT_BOOL
.PROGSTATUS.LEVEL3.BACK
60 Program Status Level 1 String 31.1 22.1 39.1 33.1 21.1 26.1 RW variation 9215..9224 “ VT_BSTR[20]
Description .PROGSTATUS.LEVEL1.DESC
Uni. Str. 31.1 22.1 39.1 33.1 21.1 26.1 9245..9264 “ VT_BSTR[20]
.PROGSTATUS.LEVEL1.DESC_U
Uni. Str. 31.2 22.2 39.2 33.2 21.2 26.2 9265..9284 “ VT_BSTR[20]

Uni. Str. 31.5 22.5 39.5 33.5 21.5 26.5 9285..9304 “ VT_BSTR[20]
63 Enable Identification by Mach. ID Bit 38 26 45 38 25 31 RW variation 2490.3 “ .MACHINEID.USE VT_BOOL

6.8.2 System parameters: Doors

DATA MODBUS OPC
1 Door number (1/2) 1/2 11 1 26 20 8 13 RW variation 2315 SYSTEM.DOOR.NUMBER VT_UI2
2 Initial door 1 / initial door 2 1/2 11.1 26.1 20.1 8.1 13.1 RW variation 2316 “ .DOOR.INITIAL VT_UI2
3 Door 1 control 0/2 11.2 26.2 20.2 8.2 13.2 RW variation 2317 “ .DOOR.LEVEL1 VT_UI2
4 Door 2 control 0/2 11.3 26.3 20.3 8.3 13.3 RW variation 2318 “ .DOOR.LEVEL2 VT_UI2
5 Golden Cycle acceptance Bit 11.4 1.1 26.4 20.4 8.4 13.4 RW at program end 2490.0 “ .DOOR.GCACCEPTANCE VT_BOOL
6 Parametric Release acceptance Bit 11.5 1.2 26.5 20.5 8.5 13.5 RW at program end 2490.1 “ .DOOR.PRTACCEPTANCE VT_BOOL
7 Door2 as middle door Bit 11.6 1.3 26.6 20.6 8.6 13.6 RW variation 2409.6 “ .DOOR2.ISMIDDLE VT_BOOL
6.8.3 System parameters: Oven

DATA MODBUS OPC
1 Sterile side pressure Pa (W) 2 RW variation 2321 SYSTEM.PSTERILSIDE VT_UI2
2 Diff. Pressure non sterile side Pa (W) 3 RW variation 2322 “ .PDIFFNONSTERILSIDE VT_UI2
3 Diff. pressure sterile side Pa (W) 4 RW variation 2323 “ .PDIFFSTERILSIDE VT_UI2
4 Valve control delay 10xsec (DW) 6 RW variation 2324..2325 “ .VALVEDELAY VT_UI4
5 Pressure alarm delay 10xsec (DW) 7 RW variation 2326..2327 “ .PALARMDELAY VT_UI4
6.8.4 System parameters: H2O2 transducer

DATA MODBUS OPC
1 H2O2 transducer type - 24 19 10 RW variation 5836 SYSTEM.VHP.H2O2SENSOR VT_UI2
2 H2O2 concentration for EVH opening 10xppm 24.1 19.1 10.1 RW variation 5837 “ .VHP.EVHOPENING VT_UI2
3 Steril side sample time 10xsec (DW) 24.2 19.2 10.2 RW variation 5838 “ .VHP.TIMESTERILSIDE VT_UI4
4 Non Steril side sample time 10xsec (DW) 24.3 19.3 10.3 RW variation 5840 “ .VHP.TIMENONSTERILSIDE VT_UI4
6.8.5 System parameters: VHP generator

DATA MODBUS OPC
1 VHP generator - 25 11 RW variation 5842 SYSTEM.H2O2GENERATOR VT_UI2
2 Profibus address 0/255 25.1 RW variation 5843 “ .GENERATORPROFIADDR VT_UI2

6.8.6 System parameters: Onboard printer

DATA MODBUS OPC
1 Type: no(0) / serial(1) / parallel(2) 0/2 14 11 28 22 12 15 RW variation 2328 SYSTEM.PRINTER.TYPE VT_UI2
2 General parameters Bit 15.1 12.1 29.1 23.1 12.1 16.1 RW variation 2329.0 “ .PRINTER.GENERAL VT_BOOL
3 Phase list Bit 15.2 12.2 29.2 23.2 12.2 16.2 RW variation 2329.1 “ .PRINTER.PHASELIST VT_BOOL
4 Phase groupsparameters Bit 15.3 12.3 29.3 23.3 12.3 16.3 RW variation 2329.2 “ .PRINTER.PHASEPARAM VT_BOOL
5 TE table Bit 15.4 12.4 29.4 23.4 12.4 16.4 RW variation 2329.3 “ .PRINTER.TETABLE VT_BOOL
6 PID parameters Bit 15.5 12.5 29.5 23.5 12.5 16.5 RW variation 2329.4 “ .PRINTER.PID VT_BOOL
7 Process data Bit 15.6 12.6 29.6 23.6 12.6 16.6 RW variation 2329.5 “ .PRINTER.PROCESS VT_BOOL
8 Temperature/time diagram Bit 15.7 12.7 29.7 23.7 12.7 16.7 RW variation 2329.6 “ .PRINTER.TDIAGRAM VT_BOOL
9 Pressure diagram Bit 15.8 12.8 29.8 23.8 - 16.8 RW variation 2329.7 “ .PRINTER.PDIAGRAM VT_BOOL
10 Alarm report Bit 15.9 12.9 29.9 23.9 12.8 16.9 RW variation 2329.8 “ .PRINTER.ALARMSUMMARY VT_BOOL
11 Alarms acknowledgement Bit 15.10 12.10 29.10 23.10 12.9 16.10 RW variation 2329.9 “ .PRINTER.ALARMACK VT_BOOL
12 Full print Bit 15.11 12.11 29.11 23.11 12.10 16.11 RW variation 2329.10 “ .PRINTER.FULLPRINT VT_BOOL
13 Golden Cycle definition Bit 15.12 12.12 29.12 23.12 12.11 16.12 RW variation 2329.11 “ .PRINTER.GCDEFINITION VT_BOOL
14 Golden Cycle report Bit 15.13 12.13 29.13 23.13 12.12 16.13 RW variation 2329.12 “ .PRINTER.GCREPORT VT_BOOL
15 Phase change Bit 15.14 12.14 29.14 23.14 12.13 16.14 RW variation 2329.13 “ .PRINTER.PHASECHANGE VT_BOOL
16 Parametric Release table Bit 15.15 12.15 29.15 23.15 12.14 16.15 RW variation 2329.14 “ .PRINTER.PRTTABLE VT_BOOL
17 Parametric Release report Bit 15.16 12.16 29.16 23.16 12.15 16.16 RW variation 2329.15 “ .PRINTER.PRTREPORT VT_BOOL
18 Other Bit 15.17 12.17 29.17 23.17 12.16 16.17 RW variation 2446.5 “ .PRINTER.OTHER VT_BOOL
19 Remote printer ip address String 15.18 12.18 29.18 23.18 12.17 16.18 RW variation 9584 “ .REMOTEPRINTER.IPADDRESS VT_BSTR[16]
6.8.7 System parameters: Recorder

DATA MODBUS OPC
1 Recorder type: no one (0 )/ Yokogawa DX100/200 (1)/ 0/2 16 30 17 RW variation 2330 SYSTEM.RECORDER.TYPE VT_UI2
TH4Recorder(2)/ Eurotherm Chessel (3)/ Yokogawa
DX1000/2000 (4)/ Yokogawa GX10 (5)
2 IP address String 16.230.2 17.2 RW variation 2331..2338 “ VT_BSTR[16]
.RECORDER.ADDRESS

6.8.7.1 Yokogawa DX100/200 and DX1000/2000 Recorder

Following parameters apply to Yokogawa Recorder only and are meaningful only if Recorder type is set to “Yokogawa”.
DATA MODBUS OPC
1 Gateway IP address String 16.3 30.3 17.3 RW variation 2339..2346 SYSTEM.RECORDER.GATEWAY VT_BSTR[16]
2 Username String 16.4 30.4 17.4 RW variation 2347..2362 “ .RECORDER.USERNAME VT_BSTR[16]
3 UserID String 16.5 30.5 17.5 RW variation 2363..2378 “ .RECORDER.USERID VT_BSTR[16]
4 Password String 16.6 30.6 17.6 RW variation 2379..2394 “ .RECORDER.PASSWORD VT_BSTR[16]
6.8.7.2 TH4Recorder Recorder

Following parameters apply to TH4Recorder only and are meaningful only if Recorder type is set to “TH4Recorder”.
DATA MODBUS OPC
1 Modbus address 1/247 16.3 30.3 17.3 RW variation 2447 SYSTEM.RECORDER.MODBUSADDRESS VT_UI2
2 TPR1 Bit 16.4 30.4 17.4 RW variation 2448.0 “ .RECORDER.TPR1 VT_BOOL
3 TPR2 Bit “ “ “ RW variation 2448.1 “ .RECORDER.TPR2 VT_BOOL
6 TER1 Bit “ “ “ RW variation 2448.4 “ .RECORDER.TER1 VT_BOOL

6.8.7.3 Eurotherm Chessel Recorder

Following parameters apply to Eurotherm Chessel Recorder only and are meaningful only if Recorder type is set to “Eurotherm Chessel”.
DATA MODBUS OPC
2 TPR1 (Ch.1) Bit 16.4 30.4 17.4 RW variation 2448.0 “ .RECORDER.TPR1 VT_BOOL
3 TPR2 (Ch.2) Bit “ “ RW variation 2448.1 “ .RECORDER.TPR2 VT_BOOL
6 TER1 (Ch.3) Bit “ “ RW variation 2448.4 “ .RECORDER.TER1 VT_BOOL
22 Start/Stop batch Bit 16.6 30.6 17.6 RW variation 2474.0 “ .RECORDER.STARTSTOP VT_BOOL
23 Use secure connection Bit 16.5 30.5 17.5 RW variation 2474.1 “ .RECORDER.SECURECONN.USE VT_BOOL
24 UserID String 16.5.1 30.5.1 17.5.1 RW variation 2475 “ .RECORDER.SECURECONN.USERID VT_BSTR[20]
25 Password String 16.5.2 30.5.2 17.5.2 RW variation 2485 “ .RECORDER.SECURECONN.PASSWORD VT_BSTR[10]

6.8.7.4 Yokogawa GX10 recorder

Following parameters apply to Yokogawa GX10 Recorder only and are meaningful only if Recorder type is set to “Yokogawa GX10”.
DATA MODBUS OPC
2 TPR1 (Ch.1) Bit 16.4 30.4 17.4 RW variation 2448.0 “ .RECORDER.TPR1 VT_BOOL
3 TPR2 (Ch.2) Bit “ “ “ RW variation 2448.1 “ .RECORDER.TPR2 VT_BOOL
6 TER1 (Ch.3) Bit “ “ “ RW variation 2448.4 “ .RECORDER.TER1 VT_BOOL
22 Start/Stop batch Bit 16.7 30.7 17.8 RW variation 2474.0 “ .RECORDER.STARTSTOP VT_BOOL
23 Timeout 0/20000 16.8 30.8 17.8 RW variation 5980 “ .RECORDER.TIMEOUT VT_UI2

6.8.8 System parameters: Sartorius WIT

DATA MODBUS OPC
1 Enable WIT - 17 RW variation 2492.0 SYSTEM.GLOBALWIT.ENABLE VT_BOOL
2 Enable FA - 17.1 RW variation 2492.1 SYSTEM.WIT.ENABLE VT_BOOL
3 FA: Filter type - 17.1.1 RW variation 2395..2402 SYSTEM.WIT.FILTERTYPE VT_BSTR[16]
4 FA: Net volume 10xml (W) 17.1.2 RW variation 2403 “ .WIT.NETVOLUME VT_UI2
5 FA: Fill system time 10xsec(DW) 17.1.3 RW variation 2404..2405 “ .WIT.TIMEFILL VT_UI4
6 FA: Fill pressure hPa (W) 17.1.4 RW variation 2406 “ .WIT.PFILL VT_UI2
7 Enable FA1 - 17.2 RW variation 2492.2 SYSTEM.WIT2.ENABLE VT_BOOL
8 FA1: Filter type - 17.2.1 RW variation 9335..9342 SYSTEM.WIT2.FILTERTYPE VT_BSTR[16]
9 FA1: Net volume 10xml (W) 17.2.2 RW variation 9343 “ .WIT2.NETVOLUME VT_UI2
10 FA1: Fill system time 10xsec(DW) 17.2.3 RW variation 9344..9345 “ .WIT2.TIMEFILL VT_UI4
11 FA1: Fill pressure hPa (W) 17.2.4 RW variation 9346 “ .WIT2.PFILL VT_UI2
6.8.9 System parameters: Steam generator and degasser

DATA MODBUS OPC
1 Max. T. steam generator 100x°C (W) 12.1 9.1 RW variation 2319 SYSTEM.STEAMGENERATOR.TMAX VT_UI2
2 Heating temp. diff. Gap 100x°C (W) 12.2 9.2 RW variation 2320 “ .STEAMGENERATOR.TDIFF VT_UI2
3 Steam generator: purge cycle time 10xsec(DW) 12.3 9.3 RW variation 2407..2408 “ .STEAMGENERATOR.PURGETIMELOOP VT_UI4
4 Steam generator: purge opening time 10xsec(DW) 12.4 9.4 RW variation 2409..2410 “ .STEAMGENERATOR.PURGETIMEOPEN VT_UI4
5 Enable flux and draining - x RW variation 2490.2 “ .STEAMGENERATOR.FLUXDRAIN.USE VT_BOOL
6 Time for flushing 10xsec(DW) x RW variation 2493 “ .STEAMGENERATOR.FLUXDRAIN.TIMEFLUX VT_UI4
7 Time for drain 10xsec(DW) x RW variation 2495 “ .STEAMGENERATOR.FLUXDRAIN.TIMEDRAIN VT_UI4

6.8.10 System parameters: Degasser sub-parameters

DATA MODBUS OPC
1 Degasser: water temperature 100x°C (W) 12.5.1 9.5.1 RW variation 2411 SYSTEM.DEGASER.TWATER VT_UI2
2 Degasser: min. water temperature 100x°C (W) 12.5.2 9.5.2 RW variation 2412 “ .DEGASER.TMINWATER VT_UI2
3 Degasser: recirculation time 10xsec(DW) 12.5.3 9.5.3 RW variation 2413..2414 “ .DEGASER.RECIRCULATIONTIME VT_UI4
6.8.11 System parameters: Barcode sub-parameters

DATA MODBUS OPC
1 Barcode: use to select program Bit 21.1 14.1 31.1 25.1 ? 18.1 RW variation 2415.0 SYSTEM.BARCODE.FORCEPROGSELECTION VT_BOOL
2 Barcode: use to set code to program Bit 21.2 14.2 31.2 25.2 ? 18.2 RW variation 2415.1 “ .BARCODE.FORCEPRODUCTCODEPROG VT_BOOL
3 Barcode: use to enter product code Bit 21.3 14.3 31.3 25.3 18.3 RW variation 2415.2 “ .BARCODE.FORCEPRODUCTCODE VT_BOOL
4 Barcode: use to enter batch number Bit 21.4 14.4 31.4 25.4 18.4 RW variation 2415.3 “ .BARCODE.FORCEBATCHNUMBER VT_BOOL
5 Barcode: use to enter notes Bit 21.5 14.5 31.5 25.5 18.5 RW variation 2415.4 “ .BARCODE.FORCENOTES VT_BOOL
6 Barcode: use to enter sterilizer ID Bit 21.6 14.6 31.6 25.6 18.6 RW variation 2415.5 “ .BARCODE.FORCEMACHINEID VT_BOOL
7 free 2415.6 .. 2415.15 VT_BOOL
6.8.12 System parameters: SNTP sub-parameters

DATA MODBUS OPC
1 SNTP: timezone hour (HH) Num(W) 22.1 15.1 32.1 26.1 14.1 19.1 RW variation 2416 SYSTEM.SNTP.TIMEZONE.HOUR VT_UI2
2 SNTP: timezone minute (MM) Num(W) 22.1 15.1 32.1 26.2 14.2 19.1 RW variation 2417 “ .SNTP.TIMEZONE.MINUTE VT_UI2
3 SNTP: master / slave Num(W) 22.2 15.2 32.2 26.3 14.3 19.2 RW variation 2418 “ .SNTP.MODE VT_UI2
4 SNTP port Num(W) 22.3 15.3 32.3 26.4 14.4 19.3 RW variation 2419 “ .SNTP.PORT VT_UI2
5 SNTP answer timeout 10xsec(DW) 22.4 15.4 32.4 26.5 14.5 19.4 RW variation 2420..2421 “ .SNTP.TIMEOUT VT_UI4
6 SNTP: server IP address String 22.5 15.5 32.5 26.6 14.6 19.5 RW variation 2422..2429 “ .SNTP.IPADDRESS VT_BSTR[16]
7 SNTP: polling time interval 10xsec(DW) 22.6 15.6 32.6 26.7 14.7 19.6 RW variation 2430..2431 “ .SNTP.INTERVAL VT_UI4

6.8.13 System parameters: DST sub-parameters

DATA MODBUS OPC
1 Daylight saving time: start hour (HH) sb 23.1 16.1 33.1 27.1 16.1 20.1 RW variation 2432 SYSTEM.DST.START.HOUR VT_UI2
2 Daylight saving time: start minute (MM) sb 23.1 16.1 33.1 27.1 16.1 20.1 RW variation 2433 “ .DST.START.MINUTE VT_UI2
3 Daylight saving time: start second (SS) sb 23.1 16.1 33.1 27.1 16.1 20.1 RW variation 2434 “ .DST.START.SECOND VT_UI2
4 Daylight saving time: start day mode sb 23.2 16.2 33.2 27.2 16.2 20.2 RW variation 2435 “ .DST.START.DAYSELECTIONMODE VT_UI2
5 Daylight saving time: start day sb 23.3 16.3 33.3 27.3 16.3 20.3 RW variation 2436 “ .DST.START.DAY VT_UI2
6 Daylight saving time: start month sb 23.4 16.4 33.4 27.4 16.4 20.4 RW variation 2437 “ .DST.START.MONTH VT_UI2
7 Daylight saving time: stop hour (HH) sb 23.5 16.5 33.5 27.5 16.5 20.5 RW variation 2438 “ .DST.STOP.HOUR VT_UI2
8 Daylight saving time: stop minute (MM) sb 23.5 16.5 33.5 27.5 16.5 20.5 RW variation 2439 “ .DST.STOP.MINUTE VT_UI2
9 Daylight saving time: stop second (SS) sb 23.5 16.5 33.5 27.5 16.5 20.5 RW variation 2440 “ .DST.STOP.SECOND VT_UI2
10 Daylight saving time: stop day mode sb 23.6 16.6 33.6 27.6 16.6 20.6 RW variation 2441 “ .DST.STOP.DAYSELECTIONMODE VT_UI2
11 Daylight saving time: stop day sb 23.7 16.7 33.7 27.7 16.7 20.7 RW variation 2442 “ .DST.STOP.DAY VT_UI2
12 Daylight saving time: stop month sb 23.8 16.8 33.8 27.8 16.8 20.8 RW variation 2443 “ .DST.STOP.MONTH VT_UI2
6.8.14 System parameters: Date-Time format

DATA MODBUS OPC
1 Date and time format sb 24 17 34 28 17 21 RW variation 2444 SYSTEM.DATEFORMAT VT_UI2
2 free 2491..2499

6.8.15 System parameters: External SQL database parameters

DATA MODBUS OPC
1 Http sb 26.1 18.1 35.1 29.1 18.1 22.1 RW variation 2450..2473 SYSTEM.SQL.HTTP VT_BSTR[48]
2 Enable SQL connection alarm sb 26.2 18.2 35.2 29.2 18.2 22.2 RW variation 2449.0 “ .SQL.CONNECTIONALARM VT_BOOL
3 System parameters sb 26.3 18.3 35.3 29.3 18.3 22.3 RW variation 2449.1 “ .SQL.SYSTEM VT_BOOL
4 Alarm configuration sb 26.4 18.4 35.4 29.4 18.4 22.4 RW variation 2449.2 “ .SQL.ALARM VT_BOOL
5 Calibration sb 26.5 18.5 35.5 29.5 18.5 22.5 RW variation 2449.3 “ .SQL.CALIBRATION VT_BOOL
6 Programs sb 26.6 18.6 35.6 29.6 18.6 22.6 RW variation 2449.4 “ .SQL.PROG VT_BOOL
7 Cycles sb 26.7 18.7 35.7 29.7 18.7 22.7 RW variation 2449.5 “ .SQL.CYCLE VT_BOOL
DST sub-parameters
This field is made of two identical structures: Daylight saving time start and Daylight saving time stop each one containing 6 fields of type Num (W).
The field hour (HH) can be set to values from 0 to 23.
The field minute (MM) can be set to values from 0 to 59.
The field second (SS) can be set to values from 0 to 59.
The field day mode can be set to values:
-1: last x of the month
0: specific monthday
1: first x of the month
2: second x of the month
where x is a specific weekday set with the field day.
The field day has different values depending on the value of the day mode field. If day mode is set to –1, 1 or 2 it represents a weekday with 0 being Monday. If
day mode is set to 0 it represents a specific monthday with 0 being the first day of the month.
The field month represents a specific month with 0 being January.
Date-time format
This field can be set to values from 0 to 2 according to the following list:
0: DD/MM/YY
1: MM/DD/YY
2: YYYY-MM-DD

6.8.16 System parameters: Tank management

DATA MODBUS OPC
1 Enable tank fill management Bit 18 RW variation 2446.7 SYSTEM.TANK.USE VT_BOOL
2 Analog input sb 18.1 RW variation 5921 “ .TANK.NLAI VT_UI2
3 Min tank quantity sb 18.2 RW variation 5922 “ .TANK.MIN VT_UI2
4 Max tank quantity sb 18.3 RW variation 5923 “ .TANK.MAX VT_UI2
5 Custom title String 18.4 RW variation 5924..5931 “ .TANK.CUSTOMTITLE VT_BSTR[16]
Unicode Str. 5932..5947 “ .TANK.CUSTOMTITLE_U VT_BSTR[16]
Tank management sub-parameters

The Analog input sub-parameter is 0 or a valid logic number in the range 1 to 199.
The sub-parameters Min tank quantity and Max tank quantity are scaled accordingly to the format of the NLAI definition of the Analog input sub-parameter
choosen.
If Analog input is set to zero or to an NLAI not defined in the hardware configuration of the specific sterilizer, the sub-parameters Min tank quantity and Max
tank quantity are zero.

6.8.17 System parameters: Cleanser management

DATA MODBUS OPC
1 Water chamber volume ml x x x RW variation 5954 SYSTEM.CLEANSER.VOLUME VT_UI4
2 Identifier of cleanser int tank 1 Num (W) x x x RW variation 5956 “ .CLEANSER.TANK1 VT_UI2

6.8.18 System parameters: Torque management

DATA MODBUS OPC
1 Enable torque management Bit x x x x x x RW variation 2446.15 SYSTEM.TORQUE1.ENABLE VT_BOOL
2 Description motor 1 String x x x x x x RW variation 9371 “ .TORQUE1.DESC VT_BSTR[20]
Unicode str x x x x x x RW variation 9381 “ .TORQUE1.DESC_U VT_BSTR[20]
3 Address motor 1 x.x % x x x x x x RW variation 9401 “ .TORQUE1.ADDRESS VT_UI2
4 Limit motor 1 x.x % x x x x x x RW variation 9402 “ .TORQUE1.LIMIT VT_UI2
…
Description motor 16 String x x x x x x RW variation 9952 “ .TORQUE16.DESC VT_BSTR[20]
Unicode str x x x x x x RW variation 9962 “ .TORQUE16.DESC_U VT_BSTR[20]
Address motor 16 x.x % x x x x x x RW variation 9982 “ .TORQUE16.ADDRESS VT_UI2
Limit motor 16 x.x % x x x x x x RW variation 9983 “ .TORQUE16.LIMIT VT_UI2

6.8.19 System parameters: Stand-by management

DATA MODBUS OPC
1 Enable stand-by management sb 29 20 37 31 19 24 RW variation 2446.6 SYSTEM.STANDBY.ENABLE VT_BOOL
2 Stand-by PG - 29.1 20.1 37.1 31.1 19.2 24.1 RW variation 5844..5846 “ .STANDBY.PG VT_BSTR[6]
3-10 PID 1: P,I,D,UMAX,UMIN,U0,AR,AD PID x x x x x x RW variation 5847..5854 “ .PID1.P, .I, .D, .UMAX, .UMIN, .U0, .AR, VT_UI2
(8W) .AD
11- PID 2: P,I,D,UMAX,UMIN,U0,AR,AD PID x x x x x x RW variation 5855..5862 “ .PID2.P, .I, .D, .UMAX, .UMIN, .U0, .AR, VT_UI2
18 (8W) .AD
26 (8W) .AD
34 (8W) .AD
42 (8W) .AD
43 PID1: reversed action Bit x x x x x x RW variation 5887.0 “ .PID1.INVERT VT_BOOL
48 Default analog value 4-20mA x x x x x x RW variation 5888 “ .DAO VT_UI2
49 Stand-by variable parameters - x x x x x x RW variation 5889 “ .STANDBY.PAR1 VT_UI2
(par.1)
... ... ... ... ... ... … ... ... ... ... ...
80 Stand-by variable parameters - x x x x x x RW variation 5920 “ .STANDBY.PAR32 VT_UI2
(par.32)
81- PID1: fractional parts of P,I,D PID x x x x x x R variation 9305..9307 “ .PID1.P_DECIMAL, .I_DECIMAL, VT_UI2
83 (3W) .D_DECIMAL
86 (3W) .D_DECIMAL
89 (3W) .D_DECIMAL
92 (3W) .D_DECIMAL
95 (3W) .D_DECIMAL

6.8.20 System parameters: Background management

DATA MODBUS OPC
1 Enable background sb 30 21 38 32 19 25 RW variation 2446.8 SYSTEM.BACKGROUND.ENABLE VT_BOOL
management
2 Background PG 1 - 30.1 21.1 38.1 32.1 19.1 25.1 RW variation 9000..9002 “ .BACKGROUND.PG1 VT_BSTR[6]
7 Background PG1 param. (par.1) - x x x x x x RW variation 9015 “ .BACKGROUND.PG1.PAR1 VT_UI2
… ... ... ... ... ... ... … ... ... ... ... ...
… ... ... ... ... ... ... … ... ... ... ... ...
… ... ... ... ... ... ... … ... ... ... ... ...
… ... ... ... ... ... ... … ... ... ... ... ...
… ... ... ... ... ... ... … ... ... ... ... ...
167- PID 1: P,I,D,UMAX,UMIN,U0,AR,AD PID x x x x x x RW variation 9175..9182 “ .BACKGROUND.PID1.P, .I, .D, VT_UI2
174 (8W) .UMAX, .UMIN, .U0, .AR, .AD
182 (8W) .UMAX, .UMIN, .U0, .AR, .AD
190 (8W) .UMAX, .UMIN, .U0, .AR, .AD
198 (8W) .UMAX, .UMIN, .U0, .AR, .AD
206 (8W) .UMAX, .UMIN, .U0, .AR, .AD
207 PID1: reversed action Bit x x x x x x RW variation 5887.5 “ .BACKGROUND.PID1.INVERT VT_BOOL

212- PID1: fractional parts of P,I,D PID x x x x x x R variation 9320..9322 “ .BACKGROUND.PID1.P_DECIMAL, VT_UI2
214 (3W) .I_DECIMAL,
.D_DECIMAL
.D_DECIMAL
.D_DECIMAL
.D_DECIMAL
.D_DECIMAL

6.8.21 System parameters: combined machines
DATA MODBUS OPC

1 Enable combined machines Bit x x x x x x RW variation 2490.4 SYSTEM.MULTIMACHINE.ENABLE VT_BOOL
2 IP address combined machine 1 String x x x x x x RW variation 5961 “ .MACHINE1.IPADDRESS VT_BSTR[16]
6 Enable miniscada Bit x x x x x x RW variation 2490.5 “ .MINISCADA.ENABLE VT_BOOL
7 Modbus address of miniscada Word x x x x x x RW variation 5977 “ .MINISCADA.ADDRESS VT_UI2
8 IP address of miniscada String x x x x x x RW variation 9562 “ .MINISCADA.IPADDRESS VT_BSTR[16]

6.8.22 “Command register” for system parameters management

DATA MODBUS OPC
1 System parameters command register 0/1 x x x x x x RW variation 2999 SYSTEMCNTRL.COMMAND VT_UI2
The user can change the system parameters, by inserting the new values in the “system parameters” tags and setting the “command register” tag to “1”.
Thema4 confirms the change execution by resetting the “command register” tag to “0”.
This system parameters change is possible only in the same conditions of the manual modification, on the user interface (see Thema4 User Manual) .

6.9 FACTORY PARAMETERS(READ ONLY)

DATA MODBUS OPC
N° Name UM 1 2 3 4 9
10 RW Update Address Tag data
1 Factory number String 1 1 1 1
1 R 1 variation 2500..2507 FACTORY.NUMBER VT_BSTR[16]
2 Model String 2 2 2 22 R2 variation 2508..2513 “ .MODEL VT_BSTR[12]
3 Max temper. Sterilizer 100x°C (W) 3 3 R variation 2514 “ .TMAX VT_UI2
4 Max. pressure sterilizer hPa (W) 4 R variation 2515 “ .PMAX VT_UI2
5 Max temperature of TE1 100x°C (W) 5 5 3 3 3 3 R variation 2516 “ .TMAXTE1 VT_UI2
6 ……. … … … … … … … … … … …
54 Max temperature of TE50 100x°C (W) “ “ “ “ “ “ R variation 2565 “ .TMAXTE50 VT_UI2
55 Min treatment duration 10xsec(DW) x R variation 2566..2567 “ .MINTREATDURATION VT_UI4
56 Proportional control 0/1 4 R variation 2568.0 “ .PROPORTIONALCONTROL VT_BOOL
57 free 2568.1.. 2568.15
59 ……. … … … … … … … … … … …
… ……. … … … … … … … … … … …
… ……. … … … … … … … … … … …
203 Model 1 String 3.1 R variation 9500..9505 “ .MODEL1 VT_BSTR
204 Max temperature model 2 100x°C (W) 3.4 R variation 9506 “ .TMAX2 VT_UI2
205 Model 2 String 3.3 R variation 9507..9512 “ .MODEL2 VT_BSTR

6.10 BATCH END DATA
6.10.1 Batch program data

DATA MODBUS OPC
1 No of programs run Num x x x x x x R at 2700 BATCHEND.RUNPERFORMED -
performed (W) program
end
2 No of treat. Success. Num x x x x x x R at 2701 “ -
Performed (W) program .RUNTREATMENTOK
end
6.10.2 Batch input data

DATA MODBUS OPC
1 Product code String x x x x x x R at prog. 2702..2717 BATCHEND.PRODUCTCODE VT_BSTR[32]
Start/end
Unicode 3256..3287 “ VT_BSTR[32]
Str. .PRODUCTCODE_U
2 Batch number String x x x x x x R at prog. 2718..2733 “ .BATCHNUMBER VT_BSTR[32]
Start/end
Unicode 3288..3319 “ VT_BSTR[32]
Str. .BATCHNUMBER_U
3 Notes, 1st row String x x x x x x R at prog. 2734..2749 “ .NOTES1 VT_BSTR[32]
Start/end
Unicode 3320..3351 “ .NOTES1_U VT_BSTR[32]
Str.
4 Notes, 2nd String x x x x x x R at prog. 2750..2765 “ .NOTES2 VT_BSTR[32]
row Start/end
Str.
5 Notes, 3rd row String x x x x x x R at prog. 2766..2781 “ .NOTES3 VT_BSTR[32]
Start/end
Str.
6 Notes, 4th row String x x x x x x R at prog. 2782..2797 “ .NOTES4 VT_BSTR[32]
Start/end
Str.
7 Operator String x x x x x x R at prog. 2798..2823 “ .OPERATOR VT_BSTR[32]
public code Start/end
Unicode 3448..3499 “ .OPERATOR_U VT_BSTR[32]
Str.

6.10.3 Batch time data

DATA MODBUS OPC
1 Start time Num x x x x x x R at program 2824 BATCHEND.TIMESTART.SECOND -
(seconds) (W) end
2 Start time Num x x x x x x R at program 2825 “ .TIMESTART.MINUTE -
(minutes) (W) end
3 Start time (hour) Num x x x x x x R at program 2826 “ .TIMESTART.HOUR -
(W) end
4 Start time (day) Num x x x x x x R at program 2827 “ .TIMESTART.DAY -
(W) end
5 Start time Num x x x x x x R at program 2828 “ .TIMESTART.MONTH -
(month) (W) end
6 Start time (year) Num x x x x x x R at program 2829 “ .TIMESTART.YEAR -
(W) end
7 End time Num x x x x x x R at program 2830 “ .TIMEEND.SECOND -
(seconds) (W) end
8 End time Num x x x x x x R at program 2831 “ .TIMEEND.MINUTE -
(minutes) (W) end
9 End time (hour) Num x x x x x x R at program 2832 “ .TIMEEND.HOUR -
(W) end
10 End time (day) Num x x x x x x R at program 2833 “ .TIMEEND.DAY -
(W) end
11 End time Num x x x x x x R at program 2834 “ .TIMEEND.MONTH -
(month) (W) end
12 End time (year) Num x x x x x x R at program 2835 “ .TIMEEND.YEAR -
(W) end

6.10.4 Batch treatment final data

DATA MODBUS OPC
1 Treatment OK 0/1 x x x x x x R at prog. 2836.0 BATCHEND.TREATMENTOK VT_BOOL
Start/end
2 Program with 0/1 x x x x x R at prog. 2836.1 “ .LEAKTEST.WITH VT_BOOL
chamber leak Start/end
test
3 Leak test OK 0/1 x x x x x R at prog. 2836.2 “ .LEAKTEST.OK VT_BOOL
Start/end
4 Program with 0/1 x R at prog. 2836.3 “ .WITTEST.WITH VT_BOOL
WIT test on FA Start/end
5 WIT OK on FA 0/1 x R at prog. 2836.4 “ .WITTEST.OK VT_BOOL
Start/end
6 Program with 0/1 x R at prog. 2947.0 “ .WITTEST2.WITH VT_BOOL
WIT test on FA1 Start/end
7 WIT OK on FA1 0/1 x R at prog. 2947.1 “ .WITTEST2.OK VT_BOOL
Start/end
Start/end
Start/end
12 With Critical 0/1 x x x R at prog. 2836.5 “ .CRITICALALARMS VT_BOOL
alarms Start/end
13 With Golden 0/1 x x R at prog. 2836.6 “ .GC.WITH VT_BOOL
Cycle Start/end
14 Golden Cycle 0/1 x x R at prog. 2836.7 “ .GC.OK VT_BOOL
OK Start/end
15 With Parametric 0/1 x x x x x x R at 2836.8 “ .PRT.WITH VT_BOOL
Release program
end
16 Parametric 0/1 x x x x x x R at 2836.9 “ .PRT.OK VT_BOOL
Release OK program
end
17 With VHP 0/1 x x R at 2836.10 “ .VHP.WITH VT_BOOL
threatment program
end
18 Room cleaning 0/1 x x x R at 2836.11 “ .ROOMCLEANING.OK VT_BOOL
was ok program
end
19 With DMD 0/1 x R at 2836.12 “ .DMD.WITH VT_BOOL
threatment program
end
20 free 2836.13..
2836.15
21 Chamber leak 10xse x x x x x R at prog. 2837..2838 “ VT_UI4
test duration c(DW) Start/end .LEAKTEST.DURATION
22 Min pressure (#1) x x x x x R at prog. 2839 “ .LEAKTEST.PMIN VT_UI2
during test Start/end
23 Max pressure (#1) x x x x x R at prog. 2840 “ .LEAKTEST.PMAX VT_UI2
during test Start/end
24 Reference (#1) x x x x x R at prog. 2841 “ .LEAKTEST.PRIF VT_UI2
pressure during Start/end
test
25 Exposure phase 10xse x x R at prog. 2842..2843 “ VT_UI4
duration c(DW) Start/end .EXPOSURE.DURATION
26 Actual exposure 10xse x x R at prog. 2844..2845 “ .EXPOSURE.ACTUAL VT_UI4
c(DW) Start/end
27 Min exposure 100x° x x R at prog. 2846 “ .EXPOSURE.TMIN VT_UI2
temperature C (W) Start/end

28 Max exposure 100x° x x R at prog. 2847 “ .EXPOSURE.TMAX VT_UI2

29 NL of TE with Num x x R at prog. 2848 “ .EXPOSURE.NLTMIN VT_UI2
min exp. Temp. (W) Start/end
30 NL of TE with Num x x R at prog. 2849 “ .EXPOSURE.NLTMAX VT_UI2
max exp. Temp. (W) Start/end
31 Min Fo 10xse x R at prog. 2850-2851 “ .EXPOSURE.F0MIN VT_UI4
c(DW) Start/end
32 Max Fo 10xse x R at prog. 2852-2853 “ .EXPOSURE.F0MAX VT_UI4
c(DW) Start/end
33 NL of TE with Num x R at prog. 2854 “ .EXPOSURE.NLF0MIN VT_UI2
min Fo (W) Start/end
34 NL of TE with Num x R at prog. 2855 “ VT_UI2
max Fo (W) Start/end .EXPOSURE.NLF0MAX
35 Min Ft 10xse x R at prog. 2856..2857 “ .EXPOSURE.FTMIN VT_UI4
c(DW) Start/end
36 Max Ft 10xse x R at prog. 2858..2859 “ .EXPOSURE.FTMAX VT_UI4
c(DW) Start/end
37 NL of TE with Num x R at prog. 2860 “ .EXPOSURE.NLFTMIN VT_UI2
min Ft (W) Start/end
38 NL of TE with Num x R at prog. 2861 “ .EXPOSURE.NLFTMAX VT_UI2
max Ft (W) Start/end
39 Min Fh 10xse x R at prog. 2862..2863 “ .EXPOSURE.FHMIN VT_UI4
c(DW) Start/end
40 Max Fh 10xse x R at prog. 2864..2865 “ .EXPOSURE.FHMAX VT_UI4
c(DW) Start/end
41 NL of TE with Num x R at prog. 2866 “ .EXPOSURE.NLFHMIN VT_UI2
min Fh (W) Start/end
42 NL of TE with Num x R at prog. 2867 “ .EXPOSURE.NLFHMAX VT_UI2
max Fh (W) Start/end
43 Progressive Num x x R at prog. 2937 “ VT_UI2
cycle number of (W) Start/end .VHP.GENERATOR.RUNNUMBER
the VHP
generator
44 VHP dose 10xg x x R at prog. 2938 “ .VHP.CONDITIONINGDOSE VT_UI2
during (W) Start/end
conditioning
45 VHP dose 10xg x x R at prog. 2939 “ VT_UI2
during (W) Start/end .VHP.DECONTAMINATIONDOSE
decontamination
46 DMD biocide 10xg x R at prog. 2940 “ .DMD.BIOCIDEDOSE VT_UI2
dose (W) Start/end
47 Number of Num x x x R at prog. 3554 “ .RUNWASHOK VT_UI2
successful (W) Start/end
washing
48 Disinfection 10xse x R at prog. 3555 “ .DISINF.ACTUAL VT_UI4
value obtained c(DW) Start/end
49 Min. disinfection 100x° x R at prog. 3557 “ .DISINF.TMIN VT_UI2
50 Max. 100x° x R at prog. 3558 “ .DISINF.TMAX VT_UI2
disinfection C (W) Start/end
temperature
51 Min. disinfection 10xse x R at prog. 3559 “ .DISINF.A0MIN VT_UI4
value c(DW) Start/end
52 Max. 10xse x R at prog. 3561 “ .DISINF.A0MAX VT_UI4
disinfection c(DW) Start/end
value
53 Logic number Num x R at prog. 3563 “ .DISINF.NLA0MIN VT_UI2
with min (W) Start/end
disinfection
54 Logic number Num x R at prog. 3564 “ .DISINF.NLA0MAX VT_UI2
with max (W) Start/end
disinfection
55 Program with 0/1 x R at prog. 3565.0 “ .DISINF.WITH VT_BOOL
disinfection Start/end

56 Program with 0/1 x R at prog. 3565.1 “ .DISINF.WASH.WITH VT_BOOL

washing Start/end
57 Washing ok 0/1 x R at prog. 3565.2 “ .DISINF.WASH.OK VT_BOOL
Start/end
#1: For type 1 it is scaled as hPa; for type 2 it is scaled accordingly with the programmable analog TP027F; for type 3 it is
scaled accordingly with the programmable analog TPC2.

6.10.5 Batch WIT final data

DATA MODBUS OPC
N° Name UM 1 2 3 4 9 10 R Update Address Tag data
W
1 FA: filter String x R at 2868..287 BATCHEND.WITTEST.FILTER VT_BSTR[16]
name program 5
end
2 FA: limit 10x(ml/1 x R at 2876 “ .WITTEST.LIMIT VT_UI2
0min) program
end
3 FA: value 10x(ml/1 x R at 2877 “ .WITTEST.VALUE VT_UI2
0min) program
end
4 FA: 10xml x R at 2878 “ VT_UI2
netvolume (W) program .WITTEST.NETVOLUME
end
5 FA: 10xml x R at 2879 “ VT_UI2
compacted (W) program .WITTEST.NETVOLUMECOMP
netvolume end
6 FA: atmosp. hPa (W) x R at 2880 “ .WITTEST.PATMOS VT_UI2
Pressure program
end
7 FA: start hPa (W) x R at 2881 “ .WITTEST.PSTART VT_UI2
pressure program
end
8 FA: start 100x°C x R at 2882 “ .WITTEST.TSTART VT_UI2
temperature (W) program
end
9 FA: end hPa (W) x R at 2883 “ .WITTEST.PEND VT_UI2
pressure program
end
10 FA: end 100x°C x R at 2884 “ .WITTEST.TEND VT_UI2
end
11 FA1: filter String x R at 2948..295 “ .WITTEST2.FILTER VT_BSTR[16]
name program 5
end
12 FA1: limit 10x(ml/1 x R at 2956 “ .WITTEST2.LIMIT VT_UI2
0min) program
end
13 FA1: value 10x(ml/1 x R at 2957 “ .WITTEST2.VALUE VT_UI2
0min) program
end
14 FA1: 10xml x R at 2958 “ VT_UI2
netvolume (W) program .WITTEST2.NETVOLUME
end
15 FA1: 10xml x R at 2959 “ VT_UI2
compacted (W) program .WITTEST2.NETVOLUMECOMP
netvolume end
16 FA1: hPa (W) x R at 2960 “ .WITTEST2.PATMOS VT_UI2
atmosp. program
Pressure end
17 FA1: start hPa (W) x R at 2961 “ .WITTEST2.PSTART VT_UI2
pressure program
end
18 FA1: start 100x°C x R at 2962 “ .WITTEST2.TSTART VT_UI2
end
19 FA1: end hPa (W) x R at 2963 “ .WITTEST2.PEND VT_UI2
pressure program
end

20 FA1: end 100x°C x R at 2964 “ .WITTEST2.TEND VT_UI2

end
name program 2
end
0min) program
end
0min) program
end
24 FA2: 10xml x R at 2975 “ VT_UI2
end
25 FA2: 10xml x R at 2976 “ VT_UI2
netvolume end
atmosp. program
Pressure end
pressure program
end
end
pressure program
end
end
name program 9
end
0min) program
end
0min) program
end
34 FA3: 10xml x R at 2992 “ VT_UI2
end
35 FA3: 10xml x R at 2993 “ VT_UI2
netvolume end
atmosp. program
Pressure end
pressure program
end
end
pressure program
end
end

6.10.6 Batch treatment time, temperature and pressure

DATA MODBUS OPC
1 Treatment - x x R at prog. 2885..2890 BATCHEND.EXPOSURE.TIMESTART VT_DATE
start time End
2 Treatment Num (W) x x R at prog. 2885 “ VT_UI2
start time End .EXPOSURE.TIMESTART.SECOND
(seconds)
start time End .EXPOSURE.TIMESTART.MINUTE
(minutes)
start time End .EXPOSURE.TIMESTART.HOUR
(hour)
start time End .EXPOSURE.TIMESTART.DAY
(day)
start time End .EXPOSURE.TIMESTART.MONTH
(month)
start time End .EXPOSURE.TIMESTART.YEAR
(year)
8 Treatment - x x R at prog. 2891..2896 “ .EXPOSURE.TIMEEND VT_DATE
end time End
end time End .EXPOSURE.TIMEEND.SECOND
(seconds)
end time End .EXPOSURE.TIMEEND.MINUTE
(minutes)
end time End .EXPOSURE.TIMEEND.HOUR
(hour)
end time End .EXPOSURE.TIMEEND.DAY
(day)
end time End .EXPOSURE.TIMEEND.MONTH
(month)
end time End .EXPOSURE.TIMEEND.YEAR
(year)
15 Min hPa (W) or x x R at prog. 2897 “ .EXPOSURE.PMIN VT_UI2
treatment Pa (W) End
pressure
(chamber)
16 Max hPa (W) or x x R at prog. 2898 “ .EXPOSURE.PMAX VT_UI2
treatment Pa (W) End
pressure
(chamber)
17 Min Pa (W) x R at prog. 2899 “ .EXPOSURE.P2MIN VT_UI2
treatment End
pressure
(steril side)
18 Max Pa (W) x R at prog. 2900 “ .EXPOSURE.P2MAX VT_UI2
treatment End
pressure
(steril side)
19 Temperature 100x°C (W) x x R at prog. 2901 “ .EXPOSURE.TSTART01 VT_UI2
of TE1 at End
threatment
start
20 … … … … … … at prog. … … …
End

21 Temperature 100x°C (W) x x R at prog. 2916 “ .EXPOSURE.TSTART16 VT_UI2

of TE16 at End
treatment
start
22 Pressure at hPa (W) or x x R at prog. 2917 “ .EXPOSURE.PSTART VT_UI2
threatment Pa (W) End
start
(chamber)
23 Pressure at Pa (W) x R at prog. 2918 “ .EXPOSURE.P2START VT_UI2
threatment End
start (steril
side)
24 Average 100x°C (W) x x R at prog. 2919 “ VT_UI2
temperature End .EXPOSURE.TAVERAGE01
of TE1 at
threatment
start
25 … … … … … … at prog. … … …
End
26 Average 100x°C (W) x x R at prog. 2934 “ VT_UI2
temperature End .EXPOSURE.TAVERAGE16
of TE16 at
threatment
start
27 Avarage hPa (W) or x x R at prog. 2935 “ .EXPOSURE.PAVERAGE VT_UI2
threatment Pa (W) End
pressure
(chamber)
28 Avarage Pa (W) x R at prog. 2936 “ VT_UI2
threatment End .EXPOSURE.P2AVERAGE
pressure
(steril side)
29 Min Fo, 10xsec(DW) x R at prog. 2941..2942 “ VT_UI4
monitoring End .EXPOSURE.MONITORED.F0MIN
30 free 2937..2998
31 Max Fo, 10xsec(DW) x R at prog. 2943..2944 “ VT_UI4
monitoring End .EXPOSURE.MONITORED.F0MAX
32 NL of TE Num (W) x R at prog. 2945 “ VT_UI2
with min Fo, End .EXPOSURE.MONITORED.NLF0MIN
monit.
33 NL of TE Num (W) x R at prog. 2946 “ VT_UI2
with max Fo, End .EXPOSURE.MONITORED.NLF0MAX
monit.

6.10.7 Batch acceptance final data

DATA MODBUS OPC
1 Acceptance start - x x x x x R at 7900 BATCHEND.DATEANDTIME VT_DATE
time program
end
2 Acceptance start Num x x x x x R at 7900 “ VT_UI2
time (seconds) (W) program .DATEANDTIME.SECOND
end
time (minute) (W) program .DATEANDTIME.MINUTE
end
time (hour) (W) program .DATEANDTIME.HOUR
end
time (day) (W) program .DATEANDTIME.DAY
end
time (month) (W) program .DATEANDTIME.MONTH
end
time (year) (W) program .DATEANDTIME.YEAR
end
8 Acceptance 0/1 x x x x x R at 7906.0 “ .REMOTE VT_BOOL
remote program
end
9 Acceptance 0/1 x x x x x R at 7906.1 “ .INVERTED VT_BOOL
doors inverted program
end
10 Acceptance log- String x x x x x R at 7907..7932 “ .USERNAME VT_BSTR[52]
in username program
end
Unicode 3500..3551 “ .USERNAME_U VT_BSTR[52]
Str.
11 Acceptance String x x x x x R at 7933..7965 “ .COMMENT VT_BSTR[64]
comment program
end
Unicode 7965..8028 “ .COMMENT_U VT_BSTR[64]
Str.

6.11 LOGGED SESSION

DATA MODBUS OPC
1 1st: username sb x x x x x x R variation 3000..3025 SESSION1.USERNAME VT_BSTR[52]
str.
2 1st: date sb x x x x x x R variation 3026..3031 “ VT_DATE
.DATEANDTIME
3 2nd: username sb x x x x x x R variation 3032..3057 SESSION2.USERNAME VT_BSTR[52]
str.
4 2nd: date sb x x x x x x R variation 3058..3063 “ VT_DATE
.DATEANDTIME
5 3rd: username sb x x x x x x R variation 3064..3089 SESSION3.USERNAME VT_BSTR[52]
str.
6 3rd : date sb x x x x x x R variation 3090..3095 “ VT_DATE
.DATEANDTIME
7 4th: username sb x x x x x x R variation 3096..3121 SESSION4.USERNAME VT_BSTR[52]
str.
8 4th: date sb x x x x x x R variation 3122..3127 “ VT_DATE
.DATEANDTIME
str.
.DATEANDTIME
str.
.DATEANDTIME
str.
.DATEANDTIME
str.
.DATEANDTIME
43000..43031 – Logged sessions

The session is organized in 8 equal areas in which the first 26 WORDs are utilized for memorizing a string that contains t
next 6 WORDs are utilized for memorizing the date and time of the log-in:
username 0..59 0..60 0..23 1..31 1..12 1900..

…
4xxxx 4xxxx + 25 4xxxx + 26 4xxxx + 27 4xxxx + 28 4xxxx + 29 4xxxx + 30 4xxxx + 31
char[1] .. char[0] char[51]..char[50] seconds minutes hour day month year

6.12 AUDIT TRAIL RECORDS (FUTURE DEVELOPMENT)

DATA MODBUS OPC
1 Event type - R variation 3300..3301 AUDIT.EVENT VT_UI4
2 free 3302
3 time (seconds) - R variation 3303 AUDIT.DATEANDTIME VT_DATE
4 time (minutes) - R variation 3304 AUDIT.DATEANDTIME VT_DATE
5 time (hour) - R variation 3305 AUDIT.DATEANDTIME VT_DATE
6 time (day) - R variation 3306 AUDIT.DATEANDTIME VT_DATE
7 time (month) - R variation 3307 AUDIT.DATEANDTIME VT_DATE
8 time (year) - R variation 3308 AUDIT.DATEANDTIME VT_DATE
9 1st row - R variation 3309..3373 AUDIT.ROW1 VT_BSTR[130]
10 2nd row - R variation 3374..3438 AUDIT.ROW2 VT_BSTR[130]
11 comment - R variation 3439..3503 AUDIT.COMMENT VT_BSTR[130]
12 username - R variation 3504..3529 AUDIT.USERNAME VT_BSTR[52]
13 free 3552..3599

6.13 CURRENT TIME DATE

DATA MODBUS OPC
1 Current time (seconds) sb x x x x x x R 1s 3600 DATEANDTIME.SECOND VT_UI2
2 Current time (minutes) Sb x x x x x x R 1s 3601 DATEANDTIME.MINUTE VT_UI2
3 Current time (hour) sb x x x x x x R 1s 3602 DATEANDTIME.HOUR VT_UI2
4 Current time (day) sb x x x x x x R 1s 3603 DATEANDTIME.DAY VT_UI2
5 Current time (month) sb x x x x x x R 1s 3604 DATEANDTIME.MONTH VT_UI2
6 Current time (year) sb x x x x x x R 1s 3605 DATEANDTIME.YEAR VT_UI2
or or
DATEANDTIME VT_DATE
43600..43605 – Actual date and time

The following fields correspond to the actual system date and time and it’s memorized in 6 WORDs:
- Actual time (…)
0..59 0..60 0..23 1..31 1..12 1900..
4xxxx 4xxxx + 1 4xxxx + 2 4xxxx + 3 4xxxx + 4 4xxxx + 5

seconds minutes hour day month year
6.13.1 Set time-date

DATA MODBUS OPC
1 Time to set (seconds) - x x x x x x RW variation 3606 SETTIME.SECOND VT_UI2
2 Time to set (minutes) - x x x x x x RW variation 3607 SETTIME.MINUTE VT_UI2
3 Time to set (hour) - x x x x x x RW variation 3608 SETTIME.HOUR VT_UI2
4 Time to set (day) - x x x x x x RW variation 3609 SETTIME.DAY VT_UI2
5 Time to set (month) - x x x x x x RW variation 3610 SETTIME.MONTH VT_UI2
6 Time to set (year) - x x x x x x RW variation 3611 SETTIME.YEAR or VT_UI2
SETTIME or
VT_DATE
7 Set time-date command - x x x x x x RW variation 3612 SETTIMECNTRL.COMMAND VT_UI2
register
8 free 3613..3649
Time-date setting
The user can change the “current time” by inserting the new values in the “time to set” tags and then setting
the“Set time-date command register” tag to “1”.
Thema4 acknowledges this request and inserts the new values, confirming the change execution by resetting the
“Set time-date command register” tag to “0”.
This time change is possible only in the same conditions of the time-date manual modification, on the
user interface (see Thema4 User Manual) .

6.14 PROGRAM/RECIPE MANAGEMENT BY SCADA

This paragraph explains how the SCADA can configure, download and run a Thema4 program (recipe)
6.14.1 Operations on programs/recipes archived in Thema4

SCADA can execute the following operations on the programs of Thema4:
1- Visualization of the data of the selected program (Description, Parameters, P/G Parameters, P/G List).
2- Modification of the selected program.
3- Deletion of the selected program from the list (memory), in Thema4.
4- Creation of a new program as a copy of one existing selected.
5- Creation of a brand new program.
It’s possible to select a program(recipe) archived in Thema4, from the list, by knowing the position number of the program (43651).
Here below follows the operations on the programs in details.
1 VISUALIZATION To visualize an existing program:

1. Select the program by the number of the position of the program(43651); if the outcome in address 43652 is zero, go to the next
step.
2. “Visualize” the data of the recipe in the Structure Program (43685… 44178), by means of insertion in the operation command
(43653) of value 1 (use 11 in case of Unicode-based systems); if the command outcome (43652) has value 0, the operation has
succeeded.
2 MODIFICATION To modify an existing program:
1. Execute the VISUALIZATION operations
2. “Modify” the data of the recipe in the Structure Program (43685…44178)
3. “Save”, by means of insertion in the operation command (43653) of value 3 (use 13 in case of Unicode-based systems); if the
command outcome (43652) has value 0 the operation has succeeded.
3 CANCELLATION To delete an existing program:
1. Execute the VISUALIZATION operations
2. “Delete” the program from the archives, by means of insertion in the operation command (43653) of value 2 (use 12 in case of
Unicode-based systems); if the command outcome (43652) has value 0 the operation has succeeded.
4 CREATION AS COPY OF AN To copy an existing program in a new one:
EXISTING PROGRAM 1. Execute the VISUALIZATION operations
2. Modify the number of the position of the program (43651) with one not present.
3. “Save” by means of insertion in the operation command (43653) of value 3 (use 13 in case of Unicode-based systems); if the
command outcome (43652) has value 0 the operation has succeeded.
5 CREATION OF A NEW See the next paragraph
PROGRAM
6 RUN OF AN EXISTING 1. Select the program
PROGRAM 2. Insert the program initial data
3. Load the program

6.14.2 Creation of new programs/recipes

To create a new program is possible to follow three ways:
6.14.2.1 Programs/recipes generation from Thema4 (operating in Local with the functions of Thema4)
It’s possible to generate programs using the functions of the THEMA4 of MANAGEMENT CYCLES and MANAGEMENT PROGRAMS, in local operation.
The advantage of this is to have a composition:
- Automatic : the cycles are made up from present P/G list in library and the programs from the cycles are generated.
- More secure: they are extracted automatically, without errors, the Parameters of the PG and the Parameters of program, to which they can be assigned
of the values by means of GUI interface, with a control of the “range” of formulation of the fields, that it holds also account of the eventual
dependencies of a parameter from others.
6.14.2.2 Download program/recipe from supervisor and memorization in Thema4:

It’s possible to create a new program directly by the SCADA and to download it in the Thema4, being inserted an “identification Number” not used and
inserting the appropriates fields into the “structure program”.
 Insert an unused identification number Position of the program (43651) (or the same on which execute the next nicode )
 Insert the data of the recipe in the Structure Program (43685…44178) composed by
- Program description
- Program’s parameters
- TE List
- PID parameters
- Parameters of the P/G that constitute the program
- List of P/Gs that compose the program. It can be the list of ID of P/Gs of the cycle repeated for each phase (as traditionally was) or the
list of five letters code of P/Gs of the cycle (as allowed starting from W30).
 “Save” the recipe downloaded by means of insertion in the operation command (43653) of value 3 (use 13 in case of Unicode-based systems); if the
command outcome (43652) has value 0 the operation succeeded.
In this case the recipe will be always saved in the memory of Thema4.

6.14.2.3 Download and execution of program/recipe from supervisor, without memorization in Thema4:
It is also possible, if you don’t want to archive programs in the THEMA4, to execute download of one recipe by the nicode r and executed directly,
without memorize it in the Thema4.
 Insert an unused identification number Position of the program (43651) (or the same on which execute the next nicode )
 Insert the data of the recipe in the Structure Program (43685…44178) composed by
- Program description
- Program’s parameters
- TE List
- PID parameters
- Parameters of the P/G that constitute the program
- List of P/Gs that compose the program. It can be the list of ID of P/Gs of the cycle repeated for each phase (as traditionally was) or the
list of five letters code of P/Gs of the cycle (as allowed starting from W30).
 Insert the “initial batch data of the program” (45028..45037).
 “Execute” the downloaded recipe by means of insertion in the operation command (45000) of value 3 (use 13 in case of Unicode-based systems); if the
command outcome (44999) has value 0 the operation succeeded and the program enters in the phase of “Preparation machine”.
 In “Preparation machine”, after the message of ok to start (“Ready to start”), send the start command from SCADA or from the push-button on the
machine.
In this case the recipe will not be present in the memories of the Thema4, but it will be endured executed.
IMPORTANT NOTE: For a program to be executable it must have “an acceptable” composition of P/G with the relative parameters (See also a
Documents of Composition Cycles and Data Sheet of the Phase Groups).

6.14.3 TAG summary for operations on program/recipe

N° Function Sub-function Modbus Address R&W Note
1 Operation on the Selection from programs list (43650) R Visualization of the number of the programs archived in the controller
program (select (43651) R/W Selection of the program in position Number:1=first,2=second,3=third …
from the list or (43652) R Command outcome
creation one Operation for selected (43653) R/W Operation command to execute (codepage): 1=visualize, 2=delete, 3 =save;
new) program or new program ( nicode-based systems): 11=visualize, 12=delete, 13 =save
(43654) R/W Identification number of the program
(43655..43684) R/W Program’s name
2 Program Recipe data (44178..44197) R/W - Program description,
structure (43711..43777) - Program’s parameters,
(Recipe) (43778..43796) - TE List,
(43798..43837) - PID parameters,
(43838..44137) - Parameters of the P/G that constitute the program
(44138..44177) or - List of P/Gs that compose the program. It can be the list of ID of P/Gs of
(46543..46722) the cycle repeated for each phase (as traditionally was) or the list of five
letters code of P/Gs of the cycle (as allowed starting from W30).
6.14.4 Run of an existing program

The operations of a program run by SCADA are:
- Select the program, by inserting an existent Program number (45001) and the Operator public code (45002..45027). Confirm this operation, by the
insertion in the operation command Code for program start (45000) of value 1 (use 11 in case of Unicode-based systems); if the Error code (44999) has
value 0 the operation has succeeded and it is possible to step to the next operation. (Otherwise see the error code table)
- Insert the program initial data: Program name (43655..43684), Product code (45028..45043), Batch number (45044..45059), Notes (45060.45123) and if
required Machine identification (45124…45131). Insert the Start time (45132..45137), for the program delayed start, if configured.
- Load the program by the insertion in the operation command Code for program start (45000) of value 2 (use 12 in case of Unicode-based systems); if the
Error code (44999) has value 0 the operation has succeeded and the program enters in the first cycle phase: “Preparation machine”. (Otherwise see the
error code table). In preparation phase is possible Start the program manually on Thema4 operator panel or by SCADA, by the register Program start
(44200) if enabled (Program start push button enable at value “1” (44400)). The insertion in the operation command (45000) of value 3 (use 13 in case of
Unicode-based systems), the system load the program, to execute, directly from the SCADA.
IMPORTANT NOTE
In order to start a program or to save data it is necessary the SCADA to be master. If SCADA is not master the save operation is rejected and
the start operation fails displaying code 112 in Tag PROGLOAD.ERROR register 44999.
Before the selection occurs, the logged users must release the master control using the specific button. After the selection, they can pick up the master
control again, in order to be able to perform e.g. operations on the cycle management buttons.

6.14.5 Architecture of the programs/recipes management in Thema4

Here below there is the architecture of the management of the Cycles and Programs from which “Recipe THEMA4” is generated. This structure can be
replied on the SCADA
ARCHIVES THEMA4 RECIPE

CYCLE
CYCLE Program Code
-Codice ciclo
(43654)
- Cycle code
Sequenza codici P/G Copy the
P/Gs sequence of the cycle
del ciclo P/G
- Sequence associated to the program, it can
code P/G of sequence be:
the cycle from cycle - the list of ID of P/G the The RECIPE, is sent to
phases belong to (up to 80 the THEMA4 (PCS) , that
phases), (44138..44177) executes the “format
- the list of five letters code of control”.
Enabled P/G LIBRARY the P/G that compose the
cycle (up to 60 P/Gs),
(46543..46722)
P/G
- P/G P/G
Codice
- Fasi P/G
- - P/GParametri
code P/G
- P/G phase Actual value of P/G parameters
Read the List
- P/G parameters (max 300)
P/G
(43838..44137)
parameters
PROGR.PARAM. Actual value of the Program

parameters
- Program Read the List (41500..41635)
parameters list with program
values of default parameters.

6.15 PROGRAM/RECIPE COMPOSITION BY SCADA
6.15.1 Program selection

DATA MODBUS OPC
1 Number of installed programs Num (W) x x x x x x RW variation 3650 PROGCNTRL.NUMBER VT_UI2
2 Program selection register Num (W) x x x x x x RW variation 3651 “ .SELECTION VT_UI2
3 Error code Num (W) x x x x x x R variation 3652 “ .ERROR VT_UI2
4 Command register Num (W) x x x x x x RW variation 3653 “ .COMMAND VT_UI2
5 Cycle ID oft he program String x x x x x x RW variation 3593 “ .CYCLEID VT_BSTR[12]
6 Identifier oft he program tob e selected Num (W) x x x x x x RW variation 3599 “ .SELECTIONID VT_UI2
6.15.2 Program identification

DATA MODBUS OPC
1 Selected program number Num (W) x x x x x x RW variation 3654 PROG.NUMBER VT_UI2
2 Program name String x x x x x x RW variation 3655..3684 “ .NAME VT_BSTR[60]
3 Program Status Num (W) x x x x x x RW variation 6791 PROG.PROGSTATUS VT_UI2
4 Program Status: description String x x x x x x RW variation 6792..6801 “ .PROGSTATUS.LEVEL.DESC VT_BSTR[20]
Unicode str. 6802..6821 “ .PROGSTATUS.LEVEL.DESC_U VT_BSTR[20]
6.15.3 Author of the program

DATA MODBUS OPC
1 Programmer public code String x x x x x x RW variation 3685..3710 PROG.PROGRAMMER VT_BSTR[52]
Unicode Str. 4932..4983 “ .PROGRAMMER_U VT_BSTR[52]
3685..3710 – Programmer public code (8 bit version)

4932..4983 – Programmer public code (unicode version)
After a “visualize” program operation with PROGCNTRL.COMMAND = 1 only the 8 bit version is refreshed (single-byte codepaged mode), whereas with
PROGCNTRL.COMMAND = 11 the unicode version is refreshed (see 5.2.2).
During a “save” or a “run from memory” operation, the controller takes the value from the first one (single-byte codepaged mode) or from the second one (unicode-
based mode) according to the code written in PROGCNTRL.COMMAND.
Be sure to use the correct one depending on the working mode of Thema4 (unicode-based mode is for special languages such as Chinese)

6.15.4 Program parameters: General

DATA MODBUS OPC
1 Automatic program start Bit G6 G8 G3 G3 G5 G2 RW variation 3711.0 “ .AUTOMATICSTART VT_BOOL
2 Check final temperature Bit G9 G8 RW variation 3711.1 “ .CHECKTFINAL VT_BOOL
3 Auxiliary heating Bit x RW variation 3711.2 “ .AUXILIARYHEATING.USE VT_BOOL
4 Control by air detector Bit x RW variation 3711.3 “ .AIRDETECTOR.USE VT_BOOL
5 Steam generator Bit x G12 RW variation 3711.4 “ .STEAMGENERATOR.USE VT_BOOL
6 H2O sterilizer Bit x RW variation 3711.5 “ .H2OSTERILIZER.USE VT_BOOL
7 Fan speed low Bit G6 RW variation 3711.6 “ .FANSPEEDLOW VT_BOOL
8 Auxiliary cooling system Bit x RW variation 3711.7 “ .AUXILIARYCOOLING VT_BOOL
9 Utilities management Bit x RW variation 3711.8 “ .UTILITY.USE VT_BOOL
10 Calculate F0 for monitoring probes Bit x R at 1727.9 “ .F0ALL VT_BOOL
prog.loading
11 Use Tmax for cycle Bit x x x x x x R at 1727.10 “ .BASECYCLE.USETMAX VT_BOOL
prog.loading
12 Has customer document Bit x x x x x x R at 1727.11 “ .CUSTOMDOC VT_BOOL
prog.loading
13 Require read ack of customer Bit x x x x x x R at 1727.12 “ VT_BOOL
document prog.loading .CUSTOMDOCKREADACK
14 Require read ack on all pages of Bit x x x x x x R at 1727.13 “.CUSTOMDOCREADACKALLPAGES VT_BOOL
customer document prog.loading
16 free 3711.9..3711.15
17 Pressure scale 0/3 G1 G1 RW variation 3712 PROG.SCALEP VT_UI2
18 Temperature scale 0/4 G2 G2 G1 RW variation 3713 “ .SCALET VT_UI2
19 Time scale 0/99 G3 G3 G1 G1 G2 G1 RW variation 3714 “ .SCALETIME VT_UI2
20 Treatment control 0/5 G4 G5 G3 RW variation 3715 “ .TREATMENT VT_UI2
21 Doors opening sequence 1/6 G5 G4 G2 G2 G4 RW variation 3716 “ .DOORSEQUENCE VT_UI2
22 Max blackout time Fo 10xsec(DW) G7 G10 G6 RW variation 3717..3718 “ .MAXBOTIMEF0 VT_UI4
23 Max blackout time Ft 10xsec(DW) x RW variation 3719..3720 “ .MAXBOTIMEFT VT_UI4
24 Max blackout time Fh 10xsec(DW) x RW variation 3721..3722 “ .MAXBOTIMEFH VT_UI4
25 Cycle end alert time 10xsec(DW) G8 G7 G4 G4 G7 G3 RW variation 3723..3724 “ .ENDALERTTIME VT_UI4
26 Print interval multiplier 1/99 G10 G5 G5 G9 G4 RW variation 3725 “ .PRINTMULTIPLIER VT_UI2
27 Executably level 1/10 G11 G6 G6 G10 G5 RW variation 3726 “ .EXECLEVEL VT_UI2
28 Interlock level 0/10 G12 G7 G7 G11 G6 RW variation 3727 “ .INTERLOCKLEVEL VT_UI2
29 Golden Cycle enable Bit G19 G11 G8 G8 G13 G7 RW variation 6726.0 “ .GOLDENCYCLE.USE VT_BOOL
30 Spatial and temporal uniformity Bit G20 G12 RW variation 6726.1 “ .SUTU.USE VT_BOOL
31 Spatial uniformity tolerance 100x°C (W) G20.1 G12.1 RW variation 6727 “ .SUTU.SUTOLERANCE VT_UI2
32 Temporal uniformity tolerance 100x°C (W) G20.2 G12.2 RW variation 6728 “ .SUTU.TUTOLERANCE VT_UI2
33 Saturated Steam control Bit G21 RW variation 6726.2 “ .PVSAT.USE VT_BOOL

34 Equilibration time check Bit G22 RW variation 6726.3 “ .EQTIME.USE VT_BOOL
35 Parametric Release table check Bit G23 G13 G9 G9 G14 G8 RW variation 6726.4 “ .PRT.USE VT_BOOL
36 Equilibration time start probe Num (W) G22.1 RW variation 6729 “ .EQTIME.TESTART VT_UI2
37 Max equilibration time 10xsec G22.2 RW variation 6730..6731 “ .EQTIME.MAXEQTIME VT_UI4
(DW)
38 Enable F(T,z) calc. for monit. TE Bit G24 RW variation 3711.9 “ .F0ALL VT_BOOL
39 Show Procedures Bit G25 G14 G10 G10 G15 G9 RW variation 3711.11 “ .CUSTOMDOC VT_BOOL

6.15.5 Program parameters: Sterilization

DATA MODBUS OPC
1 Min treatment temperature 100x°C(W) S1.1, S2.1, S1.1, S2.1, RW variation 3728 PROG.TMINTREATMENT VT_UI2
S3.1 S3.1
2 Max treatment temperature 100x°C(W) S1.2, S2.2, S1.2, S2.2, RW variation 3729 “ .TMAXTREATMENT VT_UI2
S3.2 S3.2
3 Control temperature 100x°C(W) S1.3, S2.3, S1.3, S2.3, RW variation 3730 “ .TCONTROL VT_UI2
S3.3 S3.3
4 Exposure time 10xsec(DW) S1.4, S2.4 S1.4, S2.4 RW variation 3731..3732 “ VT_UI4
.EXPOSURETIMETREAMENT
5 Max off time sterilization 10xsec(DW) S1.5, S2.5, S1.5, S2.5, RW variation 3733..3734 “ .MAXOFFTIMETREATMENT VT_UI4
S3.5 S3.5
6 Max execution time sterilization 10xsec(DW) S1.6, S2.6, S1.6, S2.6, RW variation 3735..3736 “ VT_UI4
S3.6 S3.6 .MAXEXECTIMETREATMENT
7 Min tyndall. Temperature 100x°C(W) S5.1 RW variation 3737 “ .TMINTYNDAL VT_UI2
8 Tyndall. Exposure time 10xsec(DW) S5.2 RW variation 3738..3739 “ .EXPOSURETIMETYNDAL VT_UI4
9 Tyndall Max. suspension time 10xsec(DW) S5.3 RW variation 3740..3741 “ .MAXOFFTIMETYNDAL VT_UI4
10 Tyndall. Max execution time 10xsec(DW) S5.4 RW variation 3742..3743 “ .MAXEXECTIMETYNDAL VT_UI4
11 Fo target value 10xsec(DW) S3.4 RW variation 3744..3745 “ .F0TARGET VT_UI4
12 z coefficient for Fo 100x°C(W) S2.7, S3.7 RW variation 3746 “ .F0Z VT_UI2
13 Refer. T for Fo calculation 100x°C(W) S2.8, S3.8 RW variation 3747 “ .F0TRIF VT_UI2
14 Fo calculation lowest 100x°C(W) S2.9, S3.9 RW variation 3748 “ .F0TCALC VT_UI2
temperature
15 Ft target value 10xsec(DW) x RW variation 3749..3750 “ .FTTARGET VT_UI4
16 z coefficient for Ft 100x°C(W) x RW variation 3751 “ .FTZ VT_UI2
17 Refer. T for Ft calculation 100x°C(W) x RW variation 3752 “ .FTRIF VT_UI2
18 Ft calculation lowest temperature 100x°C(W) x RW variation 3753 “ .FTCALC VT_UI2
19 Fh target value 10xsec(DW) x RW variation 3754..3755 “ .FHTARGET VT_UI4
20 z coefficient for Fh 100x°C(W) x RW variation 3756 “ .FHZ VT_UI2
21 Refer. T for Fh calculation 100x°C(W) x RW variation 3757 “ .FHRIF VT_UI2
22 Fh calculation lowest 100x°C(W) x RW variation 3758 “ .FHCALC VT_UI2
temperature
6.15.6 Program parameters: Auxiliary heating

DATA MODBUS OPC
1 Default temp. auxiliary heating 100x°C(W) G13.1 RW variation 3759 “ .AUXILIARYHEATING.T VT_UI2
2 Auxiliary heating temp. tolerance 100x°C(W) G13.2 RW variation 3760 “ .AUXILIARYHEATING.TOLERANCE VT_UI2
3 Jacket temp. alarm tolerance 100x°C(W) G13.3 RW variation 3761 “ .AUXILIARYHEATING.TALARM VT_UI2

6.15.7 Program parameters: Air detector

DATA MODBUS OPC
1 Air detector isolate pressure hPa (W) G14.1 RW variation 3762 “ .AIRDETECTOR.PISOLATE VT_UI2
2 Air detector warning pressure hPa (W) G14.2 RW variation 3763 “ .AIRDETECTOR.PWARNING VT_UI2
6.15.8 Program parameters: Steam generator

DATA MODBUS OPC
1 Max T steam generator 100x°C(W) G15.1 RW variation 3764 “ .STEAMGENERATOR.TMAX VT_UI2
2 Heating temp. diff gap 100x°C(W) G15.2 RW variation 3765 “ .STEAMGENERATOR.TDIFF VT_UI2
6.15.9 Program parameters: H2O sterilization

DATA MODBUS OPC
1 H2O supply line flush time 10xsec(DW) G16.1 RW variation 3766..3767 “ .H2OSTERILIZER.FLUSHTIME VT_UI4
2 Max time loading H2O 10xsec(DW) G16.2 RW variation 3768..3769 “ .H2OSTERILIZER.MAXLOADINGTIME VT_UI4
3 Max time heating H2O 10xsec(DW) G16.3 RW variation 3770..3771 “ .H2OSTERILIZER.MAXHEATINGTIME VT_UI4
4 H2O sterilization time 10xsec(DW) G16.4 RW variation 3772..3773 “ .H2OSTERILIZER.STERILIZATIONTIME VT_UI4
5 H2O preheating temperature 100x°C(W) G16.5 RW variation 3774 “ .H2OSTERILIZER.TPREHEATING VT_UI2
6 H2O sterilization temperature 100x°C(W) G16.6 RW variation 3775 “ .H2OSTERILIZER.TSTERILIZATION VT_UI2
7 H2O steril temp toler 100x°C(W) G16.7 RW variation 3776 PROG.H2OSTERILIZER.TOLERANCE VT_UI2
8 H2O precooling temperature 100x°C(W) G16.8 RW variation 3777 “ .H2OSTERILIZER.TPRECOOLING VT_UI2

6.15.10 Program parameters: Utility management

DATA MODBUS OPC
1 Utilities manag.: clean steam (CS) Bit G18.1 RW at prog.loading 6542.0 PROG.UTILITY.CLEANSTEAM VT_BOOL
2 Utilities manag.: plant steam (PS) Bit G18.2 RW at prog.loading 6542.1 “ .UTILITY.PLANTSTEAM VT_BOOL
3 Utilities manag.: process air (PA) Bit G18.3 RW at prog.loading 6542.2 “ .UTILITY.PROCESSAIR VT_BOOL
4 Utilities man.: water for inject. (WFI) Bit G18.4 RW at prog.loading 6542.3 “ .UTILITY.WATERFORINJECTION VT_BOOL
5 Utilities manag.: purified water (PW) Bit G18.5 RW at prog.loading 6542.4 “ .UTILITY.PURIFIEDWATER VT_BOOL
6 Utilities manag.: tap water (TW) Bit G18.6 RW at prog.loading 6542.5 “ .UTILITY.TAPWATER VT_BOOL
7 Utilities manag.: chilled water (CW) Bit G18.7 RW at prog.loading 6542.6 “ .UTILITY.CHILLEDWATER VT_BOOL
8 Utilities manag.: nitrogen (N2) Bit G18.8 RW at prog.loading 6542.7 “ .UTILITY.NITROGEN VT_BOOL
6.15.11 Program parameters: TP list

DATA MODBUS OPC
1 NL of TP displayed in pos. 1 Num (W) x x RW at progr.loading 6526 PROG.TP1 VT_UI2
… .... ... ... ... ... ... … ... ... … … VT_UI2
16 NL of TP displayed in pos. 16 Num (W) x x RW at progr.loading 6541 “ .TP16 VT_UI2
17 Displayed TPs configured as “check “ (Golden Cycle package) See 6.6.9 x x RW at progr.loading 6725 PROG.TPCHECK VT_UI2
6.15.12 Program parameters: TE list

DATA MODBUS OPC
1 No. of control Tes Num (W) x RW variation 3778 “ .TENUMBER VT_UI2
2 NL of TE displayed in pos. 1 Num (W) x x x RW variation 3779 “ .TE1 VT_UI2
… … … … … … … … … … … … VT_UI2
17 NL of TE displayed in pos. 16 Num (W) x x x RW variation 3794 “ .TE16 VT_UI2
18 Displayed Tes as “Product Tes” Num (W) x x x RW variation 3795 “ .TEPRODUCT VT_UI2
19 Displayed Tes as “Immers. Tes” Num (W) x RW variation 3796 “ .TESAFETY VT_UI2
20 Displayed Tes configured as “check “ (Golden Cycle package) See 6.6.10 x x R at progr.loading 6724 PROG.TECHECK VT_UI2

6.15.13 Program parameters: PROBE list

DATA MODBUS OPC
1 NL of PROBE displayed in pos. 1 Num (W) x x x x x x RW variation 6772 “ .PROBE1 VT_UI2
… .... ... ... ... ... ... ... ... … … VT_UI2
16 NL of PROBE displayed in pos. 16 Num (W) x x x x x x RW variation 6789 “ .PROBE16 VT_UI2
17 Displayed PROBEs config. As “Trend” sb x x x x x x RW variation 6788 PROG.PROBETREND VT_UI2
18 Displayed PROBEs config. As “Check” sb RW variation 6789 PROG.PROBECHECK VT_UI2
6.15.14 Program parameters: PID parameters

DATA MODBUS OPC
1 Default analog value 4-20mA x x x x x x RW variation 3797 “ .DAO VT_UI2
2-9 PID 1: P,I,D,UMAX,UMIN,U0,AR,AD PID (8W) x x x x x x RW variation 3798..3805 “ .PID1.P, .I, .D, .UMAX, .UMIN, .U0, .AR, .AD VT_UI2
42 PID1: reversed action Bit x x x x x x R at progr.loading 6790.0 “ .PID1.INVERT VT_BOOL
47-49 PID1: fractional parts of P,I,D PID (3W) x x x x x x R at progr.loading 6822..6824 “ .PID1.P_DECIMAL, .I_DECIMAL, .D_DECIMAL VT_UI2
6.15.15 Actual value of P/G parameters

DATA MODBUS OPC
1 Variable parameters (par. 1) - x x x x x x RW variation 3838 PROG.PAR1 VT_UI2
… … … … … … … … … … … VT_UI2
300 Variable parameters (par. 300) - x x x x x x RW variation 4137 “ .PAR300 VT_UI2

6.15.16 Program composition

6.15.16.1 By P/G number
DATA MODBUS OPC
1 Program composition (comp. 1) sb x x x x x x RW variation 4138 PROG.COMPOSITION1 VT_UI2
… … … … … … … … … … … … VT_UI2
40 Program composition(comp. 40) sb x x x x x x RW variation 4177 “ .COMPOSITION40 VT_UI2
44138..44177 - List of the P/Gs numbers of the program

The following fields correspond to the cycle phase sequence. Each WORD contains two phases, one BYTE for each phase. Each BYTE contains the P/G number of
the phase.
xxxx xxxx
…
44138 44177
phase 2 … phase 1 phase 80 .. phase 79
6.15.16.2 By P/G code

DATA MODBUS OPC
1 Five letters code of the 1° P/G String x x x x x x RW variation 6543..6545 PROG.BASECYCLE.PG1 VT_BSTR[6]
… … … … … … … … … … … … VT_BSTR[6]
60 Five letters code of the 60° P/G String x x x x x x RW variation 6720..6722 “ .BASECYCLE.PG60 VT_BSTR[6]
61 Program composition mode selector - x x x x x x RW variation 6723 PROG.BASECYCLE.USE VT_UI2
46543..46722 - List of the P/Gs codes of the program

The following fields correspond to the cycle phase group sequence. It is a list of up to 60 phase groups identified by their P/G codes. Differently by “listing by
numbers”, P/G codes are not repeated if the phase group has more than one phase, so it is exactly the cycle composition as can be seen through GUI interface.
xxxx xxxx
…
6543…6545 6720…6722
1° P/G 60° P/G
46723 – Program composition mode selector

Historically cycle composition was identified by P/G number. From W30 it is possible to specify cycle composition by means of P/G codes. The “program
composition mode selector” allows to specify which list to use, for write operations, to identify the cycle. It is normally set to 0 which defaults to cycle identification
by P/G number. If set to 1 it enables cycle identification by means of P/G codes; in this case the list of P/G numbers is ignored.
Every time a program is loaded by a “visualization” operation, this field is set to 0 and both representations of the cycle (by number and by code) are given. For
“save” operations, this field must explicitly be set to 1 in order to accept the cycle as list of P/G codes. This choice allows backward compatibilities of existing
SCADAAutoclavi
Fedegari systems, SpA
which ignore the existence of this field, so default to “list byD/O#
P/G number”.
162480.27 January 2018
6.15.17 Program description

DATA MODBUS OPC
1 Program description String x x x x x x RW variation 4178..4197 PROG.DESCRIPTION VT_BSTR[40]
Unicode Str. 4892..4931 “ .DESCRIPTION_U VT_BSTR[40]
2 free 4198..4199
4178..4197 – Program description (8 bit version)

4892..4931 – Program description (unicode version)
After a “visualize” program operation with PROGCNTRL.COMMAND = 1 the 8 bit area is refreshed with values stored on the controller (single-byte codepage
mode), whereas with PROGNTRL.COMMAND = 11 the unicode area is refreshed (unicode-based mode).
based mode) according to the command used in PROGCNTRL.COMMAND (see 5.2.2).
6.15.18 Program Procedures

DATA MODBUS OPC
1 Require read acknowledge Bit G25.1 G14.1 G10.1 G10.1 G15.1 G10.1 RW variation 3711.12 PROG.CUSTOMDOCREADACK VT_BOOL
2 Document Link String G25.2 G14.2 G10.2 G10.2 G15.2 G10.2 RW variation 6837..6868 “ .LINK VT_BSTR[32]

6.15.19 Barcode codes for program selection

DATA MODBUS OPC
1 Barcode 1 String x x x x x x RW variation 4700..4715 PROG.BARCODE1 VT_BSTR[32]
2 Barcode 2 String x x x x x x RW variation 4716..4731 “ .BARCODE2 VT_BSTR[32]
13 free 4984..4998

6.15.20 Base program cycle for program selection

DATA MODBUS OPC
1 Base program cycle : cycle ID String x x x x x x RW variation 6500..6505 PROG.BASECYCLE.ID VT_BSTR[12]
2 Base program cycle: cycle name String x x x x x x RW variation 6506..6525 “ .BASECYCLE.NAME VT_BSTR[40]
Unicode Str. 6732..6771 “ .BASECYCLE.NAME_U VT_BSTR[40]
3 free 8978..9999
4 Base program cycle: use Tmax2 Bit x RW variation 3711.10 “ .BASECYCLE.USETMAX2 VT_BOOL
43650..44177 + 44700..44998 + 46500..46525– Program management

This area is specular to the area 41700..42193. The register 43650 holds the number of programs installed in the system. The address 43651 holds a read/write
register that allows to select a specific program. For example: if the address 43650 tells that there are 5 files it is possible to write into 43651 a number from 1 to 5
thus selecting a specific program. Writing in the register 43653 the value 1 loads the content of the first program in the program management area allowing to
watch the program content; writing the value 2 removes the selected program from the system; writing 3 saves data in the program management area as a new
program with the number and name specified in registers 43654 and 43655..43684.
46506..46525 – Base program cycle: cycle name (8 bit version)

46732..46771 – Base program cycle: cycle name (unicode version)
After a “visualize” program operation with PROGCNTRL.COMMAND = 1 the 8 bit area is refreshed with values stored on the controller (single-byte codepage
mode), whereas with PROGNTRL.COMMAND = 11 the unicode area is refreshed (unicode-based mode).
based mode) according to the command used in PROGCNTRL.COMMAND (see 5.2.2).
6.15.21 Phase time table

DATA MODBUS OPC
1 Enable phase time table Bit x x x x x x RW variation 3711.14 PROG.TMTBL.ENABLE VT_BOOL
2 Phase duration 1 Num (DW) x x x x x x R variation 32300 PROG.TMTBL1.DURATION VT_UI4
... … … … … … … … … ... ... ...
3 Phase duration 80 Num (DW) x x x x x x R variation 32456 PROG.TMTBL80.DURATION VT_UI4
4 Phase repetitions 1 Num (W) x x x x x x R variation 32458 PROG.TMTBL1.REPS VT_UI2
... … … … … … … … … ... ... ...
5 Phase repetitions 80 Num (W) x x x x x x R variation 32536 PROG.TMTBL80.REPS VT_UI2

6.16 PROGRAM RUN BY SCADA
6.16.1 Program run error code

DATA MODBUS OPC
1 Error code - x x x x x x R at remote progr. Selection 4999 PROGLOAD.ERROR VT_UI2
44999 – Error code

Deals with a WORD that is utilized as a return code for the remote start operations. It is zero (0) if the operations is successful, otherwise it contains one of the
following error codes:
20 crc32 error in file

111 master already occupied
112 the command it was denied because the user is not the master
130 system parameter machine identification does not match.
131 printer occupied
148 program already loaded
149 program not loaded
150 program blocked
151 wrong program composition
152 the requested program does not exist
153 the cycle associated to the program does not exist
154 a cycle’s P/G does not exist in the installed library
156 program blocked by the door management
157 CRC error in cycle file
158 CRC error in program file
160 the program has a number of parameters or phases different from the library P/G
161 product code or batch number insertion error
164 program run in progress
999 generic error

6.16.2 Program selection and input of initial data

DATA MODBUS OPC
1 Code for program start Num (W) x x x x x x RW variation 5000 PROGLOAD.COMMAND VT_UI2
2 Program number Num (W) x x x x x x RW variation 5001 “ .NUMBER VT_UI2
3 Operator public code String x x x x x x RW variation 5002..5027 “ .OPERATOR VT_BSTR[52]
Unicode Str. X x x x x x 8734..8785 “ .OPERATOR_U VT_BSTR[52]
4 Product code String x x x x x x RW variation 5028..5043 “ .PRODUCTCODE VT_BSTR[32]
Unicode Str. X x x x x x 8786..8817 “ .PRODUCTCODE_U VT_BSTR[32]
5 Batch number String x x x x x x RW variation 5044..5059 “ .BATCHNUMBER VT_BSTR[32]
Unicode Str. X x x x x x 8818..8849 “ .BATCHNUMBER_U VT_BSTR[32]
6 Notes, 1st row String x x x x x x RW variation 5060..5075 “ .NOTES1 VT_BSTR[32]
Unicode Str. X x x x x x 8850..8881 “ .NOTES1_U VT_BSTR[32]
7 Notes, 2nd row String x x x x x x RW variation 5076..5091 “ .NOTES2 VT_BSTR[32]
8 Notes, 3rd row String x x x x x x RW variation 5092..5107 “ .NOTES3 VT_BSTR[32]
9 Notes, 4th row String x x x x x x RW variation 5108..5123 “ .NOTES4 VT_BSTR[32]
10 Machine identification String x x x x x x RW variation 5124..5131 “ .MACHINEID VT_BSTR[16]
11 Start time (seconds) Num (W) x x x x x RW variation 5132 “ .STARTTIME.SECOND VT_UI2
12 Start time (minutes) Num (W) x x x x x RW variation 5133 “ .STARTTIME.MINUTE VT_UI2
13 Start time (hour) Num (W) x x x x x RW variation 5134 “ .STARTTIME.HOUR VT_UI2
14 Start time (day) Num (W) x x x x x RW variation 5135 “ .STARTTIME.DAY VT_UI2
15 Start time (month) Num (W) x x x x x RW variation 5136 “ .STARTTIME.MONTH VT_UI2
16 Start time (year) Num (W) x x x x x RW variation 5137 “ .STARTTIME.YEAR VT_UI2
45002..45123 – Operator public code, Product code, Batch number, Notes (8 bit version)
48734..48977 – Operator public code, Product code, Batch number, Notes (unicode version)
When running a program from SCADA the controller takes the value from the first set (single-byte codepaged mode) or from the second set (unicode-based
mode), according to the command issued in PROGLOAD.COMMAND (see 5.2.2).
Be sure to use the correct set depending on the working mode of Thema4 (unicode-based mode is for special languages such as Chinese)

6.16.3 Run management commands

DATA MODBUS OPC
1 Program start Num (W) x x x x x x RW at remote progr. Selection 4200 RUN.START VT_UI2
2 Program stop Num (W) x x x x x x RW at remote progr. Selection 4201 “ .STOP VT_UI2
3 Step by step Num (W) x x x x x x RW at remote progr. Selection 4202 “ .STEPBYSTEP VT_UI2
4 Manual emergency Num (W) x x x x x x RW at remote progr. Selection 4203 “ .MANUALEMERG VT_UI2
5 Phase extension Num (W) x x x x x x RW at remote progr. Selection 4204 “ .PHASEEXTENSION VT_UI2
6 Door inversion Num (W) x x x x x x RW at remote progr. Selection 4205 “ .DOORINVERSION VT_UI2
7 Shutdown acustic alert Num (W) x x x x x x RW at remote progr. Selection 4206 “ .SILENCEALARM VT_UI2
8 free 4207..4209
44200..44206 – Run & operation commands

This area is composed by 7 WORDs used as command registers.
For registers 44200, 44201, 44202 , 44203 and 44206 writing 1 issues the command. As the command is acquired from the system the register is cleared.
For registers 44204 and 44205 writing 1 enables that function and writing 0 disabled that function. The value written is retained.
By these tags, SCADA can modify the cycle run, allowing the same operations of the push button on the Thema4 interface (during the run “Local”
management). This signal to reset the acoustic alarm (44206) allows the “reset” of the buzzer, in “Remote” operation, by the SCADA. The acoustic
alarm reset, in “Local” operation, will be, according to the standard Fedegari.

6.16.4 Enablement state of the run management commands

DATA MODBUS OPC
1 Program start push button enable Num (W) x x x x x x R variation 4400 RUNENABLE.START VT_UI2
2 Program stop push button enable Num (W) x x x x x x R variation 4401 “ .STOP VT_UI2
3 Step by step push button enable Num (W) x x x x x x R variation 4402 “ .STEPBYSTEP VT_UI2
4 Manual emergency push button enable Num (W) x x x x x x R variation 4403 “ .MANUALEMERG VT_UI2
5 Phase extension push button enable Num (W) x x x x x x R variation 4404 “ .PHASEEXTENSION VT_UI2
6 Door inversion push button enable Num (W) x x x x x x R variation 4405 “ .DOORINVERSION VT_UI2
7 Shutdown acustic alert button enable Num (W) x x x x x x R variation 4406 “ .SILENCEALARM VT_UI2
8 free 4407..4499
These tags provide the information to SCADA, about the enable state of the run management commands during the cycle phases. The enablement
of these commands, depends on the P/Gs phases (as reported into the P/G data sheets). Shutdown acoustic alert command is always enabled.

6.17 SOFTWARE VERSION

DATA MODBUS OPC
1 PCS software version String x x x x x x R at system start 4210..4219 SWVERSION.PCS VT_BSTR[20]
2 P/G software version String x x x x x x R at system start 4220..4229 “ .PG VT_BSTR[20]
3 GUI software version String x x x x x x R at system start 4230..4239 “ .GUI VT_BSTR[20]
4 FECP software version String x x x x x x R at system start 4240..4249 “ .FECP VT_BSTR[20]
5 OS/DRV software version String x x x x x x R at system start 4250..4259 “ .OS VT_BSTR[20]
6 BROM software version String x x x x x x R at system start 4260..4269 “ .BROM VT_BSTR[20]
7 JWORKS software version String x x x x x x R at system start 4270..4279 “ .JWORKS VT_BSTR[20]
8 free 4280..4399

6.18 CALIBRATION
6.18.1 Calibration: Reference

DATA MODBUS OPC
1 Reference value point 1 (1) sb x x x x x x RW variation 5200 CALIBRATION.REFERENCE1_1 VT_UI2
“ .REFERENCE1_1_ VT_I2
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …

… … … … … … … …
… … … … … … … …

6.18.2 Calibration: Measured

DATA MODBUS OPC
1 Measured value point 1 (1) sb x x x x x x RW variation 5350 CALIBRATION.MEASURED 1_1 VT_UI2
“ .MEASURED 1_1_ VT_I2
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …
… … … … … … … …

… … … … … … … …

6.18.3 Calibration: Save command

DATA MODBUS OPC
1 Calibration Save command Num (W) x x x x x x RW variation 5500 CALIBRATIONCNTRL.COMMAND VT_UI2
To perform a calibration fill the data group, Reference and Measured, accordingly with values acquired.
To perform a two point calibration fill values for point 3 with zeroes, otherwise a three point calibration will be performed for every NLAI with the point 3 different
from zero.
To save the calibration write 1 in the Calibration Save register 45500.
The change of these data is possible only in the same conditions of the manual modification, on the user interface (see Thema4 User Manual) .
45200..45779 – CALIBRATION
This area holds calibration values and allows to perform a calibration. It is composed by 6 data groups and a command register. Each data group holds a specific
kind of value for the 79 internal NLAI that can be configured in the system.
NLAI 1 NLAI50 NLAI 51 NLAI79

Reference value point 1
… …
45200 45249 45501 45529
… …
45250 45299 45551 45579
… …
45300 45349 45601 45629
Measured value point 1
… …
45350 45399 45651 45679
… …
45400 45449 45701 45729
… …
45450 45499 45751 45779

6.19 FILTER STERILIZATION
6.19.1 Filter sterilization: Filter identification

DATA MODBUS OPC
1 Number of filter sterilization started Num (W) x R variation 5800 STERFILTER.STARTED VT_UI2
2 Number of filter sterilization ok Num (W) x R variation 5801 “ .OK VT_UI2
3 Max number of filter ster. Started Num (W) x RW variation 5802 “ .MAXSTARTED VT_UI2
4 Max number of filter ster. Ok Num (W) x RW variation 5803 “ .MAXOK VT_UI2
6.19.2 Filter sterilization: Reset command

DATA MODBUS OPC
1 Reset command register Num (W) x RW variation 5804 STERFILTERCNTRL.COMMAND VT_UI2
This function of Filter maintenance is described in the document Fedegari D/O#147602 – “THEMA4 OPTION 05 – Filter maintenance.”
The data exchanged with the SCADA, for the management of this function, are those of the Filter Management Maintenance (45800-45804). The identification
of the filter is already present as Parameter of system. The expiration of the filter is signed, activating a specific alarm, that will be reset (command of reset from
SCADA or push-button on Thema4 in Local) together with the counters, after the substitution of the filter.
To send the reset command from the SCADA write “1” in the command register. As the command is accepted it will be set to “0” from Thema4.

6.20 VHP GENERATOR
6.20.1 VHP generator: Status

DATA MODBUS OPC
N° Name UM 1 2
3 4 9 10 RW Update Address Tag data
1 Ready to start Bit x x R variation 4410.0 VHPGENERATOR.READYTOSTART VT_BOOL
2 Cycle activated Bit x x R variation 4410.1 “ .CYCLEACTIVATED VT_BOOL
3 Cycle aborted Bit x x R variation 4410.2 “ .CYCLEABORTED VT_BOOL
4 Cycle completed Bit x x R variation 4410.3 “ .CYCLECOMPLETED VT_BOOL
5 Cartridge dryier low Bit x x R variation 4410.4 “ .CARTRIDGEDRYLOW VT_BOOL
6 Cartridge H2O2 low Bit x x R variation 4410.5 “ .CARTRIDGEH2O2LOW VT_BOOL
7 Alarm status (1..16) sb x x R variation 4411 “ .ALARM1 … “ .ALARM16 VT_BOOL
… … … … … … … … … …
70 Alarm status (49..64) sb x x R variation 4414 “ .ALARM49 … “ .ALARM64 VT_BOOL
71 Phase number Num (W) x x R variation 4415 “ .PHASENUM VT_UI2
72 Target phase time 10xsec (DW) x x R variation 4416 “ .TARGETPHASETIME VT_UI4
73 Countdown phase time 10xsec (DW) x x R variation 4418 “ .COUNTDOWNPHASETIME VT_UI4
74 Progressive cycle number Num (W) x x R variation 4420 “ .PROGRESSIVENUMBER VT_UI2
75 Cartridge dryier level 10xg x x R variation 4421 “ .CARTRIDGEDRYLEVEL VT_UI2
76 Cartridge H2O2 level 10xg x x R variation 4422 “ .CARTRIDGEH2O2LEVEL VT_UI2
77 Air temperature 100x°C x x R variation 4423 “ .AIRTEMPERATURE VT_UI2
78 Relative humidity % x x R variation 4424 “ .RELATIVEHUMIDITY VT_UI2
79 Absolute humidity - x x R variation 4425 “ .ABSOLUTEHUMIDIDTY VT_UI2
80 Air flow 10xm3h x x R variation 4426 “ .AIRFLOW VT_UI2
81 Vaporizer temperature 100x°C x x R variation 4427 “ .VAPORIZERTEMP VT_UI2
82 Preheater temperature 100x°C x x R variation 4428 “ .PREHEATERTEMP VT_UI2
83 H2O2 dose during conditioning 10xg x x R variation 4429 “ .H2O2CONDITIONING VT_UI2
84 H2O2 dose during decontamination 10xg x x R variation 4430 “ .H2O2DECONTAMINATION VT_UI2
44411..44414 – Alarm status 1..64

This area is a bit table that holds the status bit for every alarm.
15 … …0 15 … …0
…
44411 44414
Alarm activated

6.20.2 VHP generator: Commands

DATA MODBUS OPC
1 VHP generator command sb x x RW variation 4431 VHPGENERATOR.COMMAND VT_UI2
4431 – VHP generator command

This WORD allows to perform a specific command by writing one of the following numbers into it:
- 1: send to the generator a reset active alarms command, this will clear any active alarm if the alarm cause ceased;
- 2: send to the generator a reset dryier level command, this will increase the capacity of the dryier level.
The command is accepted only if the SCADA is master, and the register written is immediately set to 0.

6.21 TANK MANAGEMENT
6.21.1 Tank management: Status

DATA MODBUS OPC
1 Enable load command sb x R variation 4394.0 TANK.ENABLE.LOAD VT_BOOL
2 Enable stop command sb x R variation 4394.1 “ .ENABLE.STOP VT_BOOL
3 Low tank level sb x R variation 4395 “ .LOWLEVEL VT_UI2
4 High tank level sb x R variation 4396 “ .HIGHLEVEL VT_UI2
5 Current tank level sb x R variation 4397 “ .CURRLEVEL VT_UI2
6 Tank status sb x R variation 4398 “ .STATUS VT_UI2
4394.0 .. 4394.1 – Enable load/stop commands

These flags tells the SCADA if the start filling or the stop filling commands will be accepted, according to current process conditions (the “master” access is not considered).
4395..4397 - Tank levels

The Low tank level, High tank level and Current tank level fields are scaled accordingly to the format of the NLAI choosen for the parameter Analog input of the Tank
management section of System parameters.
If the Analog input is set to zero or to an NLAI not defined in the hardware configuration of the specific sterilizer, the levels are zero.
4398 - Tank status

Status is normally 0, except when the filling is in progress, in which case the status is 1.
6.21.2 Tank management : Commands

DATA MODBUS OPC
1 Tank management command sb x RW variation 4399 TANK.COMMAND VT_UI2
4399 – Tank management commands

This WORD allows to perform a specific command by writing one of the following numbers into it:
- 1: send the “start tank filling” command;
- 2: send the “stop tank filling” command.
The command is accepted only if the SCADA is master, and the register written is immediately set to 0.

6.22 THEMA4-SCADA SYNCRONIZATION AND LOCAL/REMOTE OPERATION

DATA MODBUS OPC
1 Heartbeat SCADA Num (W) x x x x x x RW cyclical 5810 SCADA.HEARTBIT VT_UI2
2 Local/Remote Num (W) x x x x x x RW variation 5811 “ .LOCALREMOTE VT_UI2
3 Thema4 Master Num (W) x x x x x x RW variation 5812 “ .TH4MASTER VT_UI2
This area is composed of three registers, needed for Thema4-SCADA synchronization.

- The first is named Heartbeat and it is used by the system to detect if the SCADA system is connected and alive. The SCADA writes 1 in that register and
the system looks periodically (once a minute) at that field: if it finds it equals to 1 the system clears it. If the system does not find it equals to 1 for too much
time then the SCADA is considered unconnected.
- The second register is named Local/Remote. The SCADA writes 1 in that register, to require the Remote control. That field is cleared by the SCADA when
it turns the control in Local mode or by the system when it detects that connection is lost.
- The third register Thema4 Master can be 0 or 1 depending by the owner of the master access. If SCADA is master its value is 1.

6.22.1 Operation signal of Local/Remote (operated only by SCADA)

The register Local/Remote, managed by SCADA, allows Thema4 to understand if SCADA (that must be detected as alive, by “Heartbeat SCADA” ) is
operating in Remote mode (signal is up) or in Local mode(signal is down). These are the Local/Remote management rules:
1. If connected, SCADA can find if Thema4 has the MASTER control by checking the bit “Thema4 MASTER”. If it is set a login on Thema4 owns the
MASTER control, otherwise no one owns the MASTER control of the system.
2. When SCADA selects Remote, there are two possible scenarios:
a. If Thema4 owns the MASTER control, SCADA asks Thema4 to release the MASTER. When the user logged on Thema4 completes operations
he was carrying on and releases the MASTER control, the MASTER control is automatically given to the SCADA.
b. If there is no MASTER in the system SCADA automatically get the MASTER control.
3. Thema4 can get the MASTER control only if Local operation is set by SCADA (i.e.: SCADA releases the MASTER control).
4. If the communication between Thema4 and SCADA goes down, THEMA4 switches to Local operation. In this case SCADA MASTER control is
considered as released and it is possible for a user to get the master control on the Thema4.
By the “SCADA” icon in the list of sessions displayed in the Thema4 controller, it is possible to see on Thema4 if SCADA is connected (if present), if it is asking
for MASTER control (background blinking red) or if it owns the MASTER control (red border).
N States of SCADA SCADA icon THEMA4 Bit Bit Bit

State Heartbeat Local/ Thema4
(SCADA/TH4) Remote MASTER
(SCADA/TH4)
1 SCADA is not connected Not present Local “0” fix “0” reset “0/1”
(reset)
2 SCADA is connected and force the Local mode Present without edges Local “1/0” cyclical “0” “0/1”
3 SCADA is connected and force Remote state in wait for get Present with background blinking red Remote “1/0” cyclical “1” “1”
MASTER (normally on Thema4) MASTER
4 SCADA is connected in Remote MASTER Present with red edges Remote “1/0” cyclical “1” “0”

6.23 THEMA4 SHUTDOWN

DATA MODBUS OPC
1 Shutown command Num (W) x x x x x x RW variation 5813 SHUTDOWN.COMMAND VT_UI2
2 Shutdown status Num (W) x x x x x x R variation 5814 SHUTDOWN.STATUS VT_UI2
This area is composed of two registers, allowing Thema4 shutdown, that it is need before its switch off .
The first is a read and write register named Shutdown Command which is used to perform the safe shutdown procedure of the system. The second is a read
only register named Shutdown Status which shows answers to actions performed on the first register.
By writing 1 on the first register an external system can start a shutdown procedure. If the system can be turned off (i.e.: there is no cycle running, a backup or
restore operation is not being performed…) the Shutdown status register turns to 2, otherwise turns to 1.
If the shutdown can’t be performed the external system has to wait until the blocking operation ends or can force a shutdown by writing 2 in the command
register. This forces the system to finish operations, write 2 in the status register and shutdown the system.
IMPORTANT NOTE
Please note that when the shutdown operation succeeds the communication may be down within two seconds.

6.24 OPC SETTING

DATA MODBUS OPC
1 OPC Timestamp offset Num (W) x x x x x x RW variation 5815 OPCTIMESTAMPOFFSET VT_I2
2 OPC Timestamp offset minutes Num (W) x x x x x x RW variation 5805 OPCTIMESTAMPOFFSETMINUTES VT_I2
3 free 5816..5999
This area is composed of two registers named OPC Timestamp Offset which can be used to adjust the timestamp of the OPC Server to match the time of the
external system.
The first register is programmable with steps of 1 hour, this is kept for compatibility with existing SCADA systems.
The second register is programmable with steps of 1 minute so it can be used to adjust the timing in world area that have a fractionary timezone.
These two registers are alternative so it is necessary to write only one of them, otherwise the timestamp offset will be set according to the last one written.
Please note that these registers are not meaningful for Modbus based systems.
IMPORTANT NOTE
The timestamp reported by an OPC client, connected to a Thema4, system is synchronized with Thema4 date and time only if the client is
under following conditions:
- GMT +00:00
- daylight saving time not in use
Under different operating conditions it is necessary to write a time span in hours into the tag “OPC Timestamp offset “ to align timestamp with
date and time.
Because Thema4 sends “local time” and client calculates a time assuming to receive a GMT +00:00, the time span has to be the difference
between GMT +00:00 and the Thema4 “local time” ( with one hour less, when DST is in use).
For example: With both client and Thema4 in Italy, during daylight saving time (DST) season, it is necessary to write –2, while when DST is
not in use it is necessary to write –1.
If OPCTIMESTAMPOFFSETMINUTES is used instead of OPCTIMESTAMPOFFSET the value must be multiplied by 60.

6.25 PARAMETRIC RELEASE REPORT

DATA MODBUS OPC
1 Value of critical parameter 1 Short x x x x x x R at prog. end 8000 PRT.VALUE1 VT_I2
… … … … … … … … … … … … …
300 Value of critical parameter 300 Short x x x x x x R at prog. end 8299 PRT.VALUE300 VT_I2
301 Result and Validity of critical parameters from 1 to 8 Bit x x x x x x R at prog. end 8300.0 PRT.RESULT1, PRT.VALIDITY1 VT_BOOL
8300.1 …
… PRT.RESULT8, PRT.VALIDITY8
8300.14
8300.15
… … … … … … … … … … … … …
336 Result and Validity of critical parameters from 297 to Bit x x x x x x R at prog. end 8337.0 PRT.RESULT297, PRT.VALIDITY297 VT_BOOL
300 8337.1 …
… PRT.RESULT300, PRT.VALIDITY300
8337.6
8337.7
The exchange area will consist in:

- PRTable: 300 tags for OPC, 300 registers for modbus
- PRReport: 300 tags for OPC, 38 registers for modbus (result is packed in 2 bits)

48000..48299 – Value of critical parameters 1..300

Each WORD indicates the value of the critical parameter. The numeric format and measuring unit depends by the definition of the critical parameter.
…
48000 48299
Value of crit.param 1 Value of crit.param 300
48300..48337 – Result and Validity of critical parameter 1..300
Each WORD uses two bits for each critical parameter and 8 critical parameters are grouped for each WORD. The first bit (result) indicates if the result
of the critical parameter is TRUE or FALSE, while the second bit (validity) indicates if the result is valid or not (it is not valid if the formula has not been
evaluated due to an error in the formula itself or because the phase can’t be found in the process report). If the Validity bit is FALSE then the Result is
FALSE too.
15 … …0 15 … …0
…
48300 48337
crit.par.(8) … crit.par.(1) RESULT of crit.par.1 crit.par.(300)…crit.par.(297) RESULT of crit.par.297
VALIDITY of crit.par 1 VALIDITY of crit.par 297

6.26 ENHANCED PROCESS REPORT

DATA MODBUS OPC
1 Last sample counter Word x x x x x x R variation 10000 ENHANCED.SAMPLECOUNTER VT_UI2
2 Row1: sample counter Word x x x x x x R variation 10001 “ .ROW1.SAMPLECOUNTER VT_UI2
3 Row1: program time DWord x x x x x x R variation 10002 “ .ROW1.PTT VT_UI4
4 Row1: phase time DWord x x x x x x R variation 10004 “ .ROW1.FTT VT_UI4
5 Row1: row type Word x x x x x x R variation 10006 “ .ROW1.TYPE VT_UI2
6 Row1: phase number Word x x x x x x R variation 10007 “ .ROW1.PHASENUMBER VT_UI2
7 Row1: alarm number Word x x x x x x R variation 10008 “ .ROW1.ALARM VT_UI2
8 Row1: map of 16 TPs Word x x x x x x R variation 10009 “ .ROW1.TPMAP VT_UI2
9 Row1: TP1 Word x x x x x x R variation 10010 “ .ROW1.TP1 VT_UI2
… Row1: … Word x x x x x x R variation … … VT_UI2
24 Row1: TP16 Word x x x x x x R variation 10025 “ .ROW1.TP16 VT_UI2
25 Row1: map of 16 TEs Word x x x x x x R variation 10026 “ .ROW1.TEMAP VT_UI2
26 Row1: TE1 Word x x x x x x R variation 10027 “ .ROW1.TE1 VT_UI2
41 Row1: TE16 Word x x x x x x R variation 10042 “ .ROW1.TE16 VT_UI2
42 Row1: map of 16 PROBEs Word x x x x x x R variation 10043 “ .ROW1.PROBEMAP VT_UI2
43 Row1: PROBE1 Word x x x x x x R variation 10044 “ .ROW1.PROBE1 VT_UI2
58 Row1: PROBE16 Word x x x x x x R variation 10059 “ .ROW1.PROBE16 VT_UI2
59 Row1: map of 16 F(T,z) or Fh(T,z) Word x x x x x x R variation 10060 “ .ROW1.FXMAP VT_UI2
60 Row1: F(T,z) or Fh(T,z) 1 DWord x x x x x x R variation 10061 “ .ROW1.FX1 VT_UI4
… Row1: … DWord x x x x x x R variation … … VT_UI4
75 Row1: F(T,z) or Fh(T,z) 16 DWord x x x x x x R variation 10091 “ .ROW1.FX16 VT_UI4
77 Row1: spatial uniformity WORD x x x x x x R variation 10093 “ .ROW1.SPATIAL VT_UI2
… Row2..Row9 … … … … …
677 Row10 : sample counter Word x x x x x x R variation 10901 “ .ROW10.SAMPLECOUNTER VT_UI2
… … … … … … …
751 Row10 : F(T,z) or Fh(T,z) 16 Word x x x x x x R variation 10993 “ .ROW10.SPATIAL VT_UI2

This area allows to retrieve the same process data (values, alarms and phase changes) stored in the Process Report of TH4. This area is composed of a global
register and 10 logical “rows” arranged in a circular way.
The global register contains an integral number which is incremented by one every time a new row is produced. The row produced is saved in the oldest of the
10 “rows” so that rows are never moved and at any time it is always possible to get last 10 rows of data.
By sampling the global counter quite fast it is possible to detect when new rows are written in the circular buffer, the exact rows can be identified and retrieved.
REFERENCE
Details on how to use this feature to obtain an exact copy of the Process Report produced by TH4 are described in the document DM#397839
– TN_A0060 “Addendum for exact collection of Process Report data”


7 PROCESS REPORT TAGS

7.1 - PROCESS REPORT DATA
ACQUISITION BY SCADA TAGS
7.1.1- Initial data
7.1.2 - Sterilization control data
7.1.3 - Phase and parameters of the program
7.1.4 - Process data
7.1.5 - Batch end data

7.1 PROCESS REPORT DATA ACQUISITION BY SCADA TAGS

By the Thema4-SCADA integration is possible to acquire, on-line, the process report tags.
Tables in following section show the parts of a process report, with hightlighted:
- fixed text messages in BLACK (These can’t be acquired by SCADA)
- variable data in BLUE (These can be acquired by the SCADA)
- Modbus address on [YELLOW] background, where variable data are stored,
Following tables list the process report data, divided in:

- INITIAL DATA
- STERILIZATION CONTROL DATA
- PHASES AND PARAMETERS OF THE PROGRAMS
- PROCESS DATA
- BATCH END DATA
7.1.1 Initial data

In the process report there are some fixed initial data like :
- General information
- TE table
- General paramareters
- PID parameters
These fixed data are included in every process report and like is showed below
* FEDEGARI AUTOCLAVI S.p.A. – PROCESS REPORT *
PROGRAM 1
Simulazione 1
FILE 1_SIM1.prg
PROGRAMMER MAINTENANCE
OPERATOR MAINTENANCE [2798-2823]
PRODUCT CODE TEST [2702-2717]
BATCH No. 1 [2718-2733]
ID. STERILIZER NA1040AL [2307-2314]
NOTES [2734-2749]
TEST1
STERILIZER FOAF4/A [2508-2513]

SERIAL NUMBER NA1040AL [2500-2507]
LANGUAGE ENGLISH(ENG)
PROGRESSIVE N. 34 [2700]
GENERAL PARAMETER
n. parameters value
1 PRESSURE SCALE 0-3 0 [1728]
2 TEMPERATURE SCALE 0-4 0 [1729]
3 TIME SCALE x 30 min 1 [1730]
4 STERILIZATION CONTROL 0-5 2 [1731]
5 DOORS OPENING SEQUENCE 1-6 - [1732]
6 AUTOMATIC START 0-1 0 [1727.0]
7 MAX BLACKOUT TIME 5 [1734-1734]
8 CYCLE END ALERT TIME 10 [1739-1740]
9 FINAL TEMPERATURE CHECK 1 [1727.1]
10 PRINT INTERVAL MULTIPLIER 3 [1741]
11 EXECUTABILITY LEVEL - [1742]
12 INTERLOCK LEVEL - [1743]
13 AUXILIARY HEATING 0-1 0 [1727.2]
14 CONTROL BY AIR DETECTOR 0-1 0 [1727.3]
15 STEAM GENERATOR ENABLED 0-1 0 [1727.4]
16 H2O STERILIZER 0-1 0 [1727.5]
17 AUXILIARY COOLING SYSTEM 0-1 0 [1727.7]

TE TABLE
n. DISPLAYED PRODUCT
1 1 [1795] X [1811.0]
2 0 [1796] - [1811.1]
3 0 [1797] - [1811.2]
4 0 [1798] - [1811.3]
5 0 [1799] - [1811.4]
6 0 [1800] - [1811.5]
7 0 [1801] - [1811.6]
8 0 [1802] - [1811.7]
9 0 [1803] - [1811.8]
10 0 [1804] - [1811.9]
11 0 [1805] - [1811.10]
12 0 [1806] - [1811.11]
13 0 [1807] - [1811.12]
14 0 [1808] - [1811.13]
15 0 [1809] - [1811.14]
16 0 [1810] - [1811.15]
PID PARAMETERS
1 2 3 4 5 1 2 3 4 5
P mB-'Cx100 350.00 350.00 350.00 350.00 350.00 [1814][1822][1830][1838][1846]
I sec 80.0 80.0 80.0 80.0 80.0 [1815][1823][1831][1839][1847]
D sec 0.0 0.0 0.0 0.0 0.0 [1816][1824][1832][1840][1848]
UMAX mA 20.00 20.00 20.00 20.00 20.00 [1817][1825][1833][1841][1849]
UMIN mA 4.00 4.00 4.00 4.00 4.00 [1818][1826][1834][1842][1850]
U0 mA 4.00 4.00 4.00 4.00 4.00 [1819][1827][1835][1843][1851]
AR %P 100 100 100 100 100 [1820][1828][1836][1844][1852]
AD %P 0 0 0 0 0 [1821][1829][1837][1845][1853]
DAO mA 14.00 [1813]

7.1.2 Sterilization control data

There are few different types of sterilization control in the THEMA4 Control System :without Sterilization, Time
Based, Time with F(T,z) calculation, F(T,z) based, Time Based ETO model , Tyndallization.
These differences are showed in the printout of the process report as follow :
CASE 1 STERILIZATION TYPE: TIME BASED

STERILIZATION CONTROL
n. parameters value
1 MIN STERILIZATION TEMPERATURE 120.0 [1744]
2 MAX STERILIZATION TEMPERATURE 122.0 [1745]
3 CONTROL TEMPERATURE 121.0 [1746]
4 EXPOSURE TIME 5:00 [1747-1748]
5 MAX OFF TIME STERILISATION 5:00 [1749-1750]
6 MAX EXCESS STERILIZ.TIME 999:00 [1751-1752]
CASE 2 STERILIZATION TYPE: TIME WITH F(T,z) CALCULATION

n. parameters value
4 EXPOSURE TIME 5:00 [1747-1748]
7 Z COEFF. FOR F(T,z) CALC. 10.00 [1762]
8 REFER.T FOR F(T,z) CALCUL. 121.11 [1763]
9 F(T,z) CALC.LOWEST TEMPERATURE 90.0 [1764]
CASE 3 STERILIZATION TYPE: F(T,z) BASED

n. parameters value
4 TARGHET F(T,z) 0:06 [1760-1761]
7 Z COEFF. FOR F(T,z) CALC. 10.00 [1762]
8 REFER.T FOR F(T,z) CALCUL. 121.11 [1763]
9 F(T,z) CALC.LOWEST TEMPERATURE 90.0 [1764]
CASE 4 TYNDALLIZATION
1 MIN TYNDALLIZATION TEMPERATURE 80.0 [1753]
2 TYNDALLIZATION DURATION 180:00 [1754-1755]
3 MAX TYNDALLIZATION STOP TIME 121.0 [1756-1757]
4 MAX TYNDALLIZ. EXCESS DURATION 999:00 [1758-1759]

7.1.3 Phase and parameters of the program

In the table “Loaded program”, of OPC/Modbus addresses table of Thema4, there are two address areas:
- “Variable parameters”
- “Program composition” .
In the “Variable parameters” area , there is the parameters (targets) list of all the phases of the current
program.
In the “Program composition” area, there is the phases list of the current program.
7.1.3.1 Parameters(targets) list
In the table “Loaded program”, address area “Variable parameters” (Modbus address: 1854..2153 / OPC tags:
RUNPROG. PAR1.... RUNPROG. PAR300) there is space for maximum 300 PHASE/GROUPS PARAMETERS.
This is the Phase/Groups parameters list of the current program, as reported the initial data of the
Thema4 process report, as you can see in the following example, where the corresponding Modbus and
OPC addresses are reported:
………………
PHASE/GROUPS PARAMETERS (b)

n. n. phase parameters value
1 1 AUXILIARY OUTPUT 0
[1854]
2 1 AUXILIARY OUTPUT TIMED (s) 0
[1855]
3 1 AUXILIARY HEATING 1
[1856]
4 1 MAX.HEATING DURATION 10
[1857]
5 1 AUXILIARY CONTROL 0
[1858]
6 2 TARGET PRESSURE 0.10
[1859]
[1860]
8 2 DEPRESSURIZE AIR FILTER 0
[1861]
9 2 VACUUM VALVE OPENING PRESSURE 1.25
[1862]
10 2 MAX.PHASE TIME 10
[1863]
11 3 DURATION VACUUM, STEAM INJECT. 2
[1864]
12 3 MIN.PRESSURE RISE 0.02
[1865]
13 3 CHAMBER PRESSURE RISE 0.10
[1866]
14 3 MAX.ALLOWED TEMPERATURE 123
[1867]
15 3 PREPARE AIR FILTER 0
[1868]
16 4, 5 STERILIZE AIR FILTER 0
[1869]
17 4 STERILIZATION START DELAY 0
[1870]
18 4 MAX.HEATING DURATION 40
[1871]
19 4, 5 AUXIL.OUTPUT THRESHOLD (-bar) 0.20
[1872]
20 4, 5 AUXILIARY OUTPUT THRESHOLD(mA) 12.0 [1873]
21 6 TARGET PRESSURE 0.10
[1874]
[1875]
23 6 DEPRESSURIZE AIR FILTER 0
[1876]
24 6 VACUUM VALVE OPENING PRESSURE 1.25
[1877]
25 6 MAX.PHASE TIME 10
[1878]
26 7 DURATION VACUUM 2
[1879]
27 7 MAX.VACUUM VALUE 0.05
[1880]
[1881]
29 7 AUXILIARY HEATING TEMPERATURE 118
[1882]
30 7 VACUUM IN AIR FILTER 0
[1883]
31 9 LEAVE OPEN BALANCE VP 1
[1884]
The 9parameters
32 (target)
LEAVE OPEN list depends
RELIEF VP on the selected program.
1
[1885]
33 9 CYCLE END AUXIL.OUTPUT 0
[1886]
...
(b) There is a space limit for maximum 300 parameters [2153]
……………..

7.1.3.2 Program phase list

In the table “Loaded program”, the area “Program composition” (Modbus address: 2154..2193 / OPC tags:
RUNPROG. COMPOSITION1 .... RUNPROG. COMPOSITION40) reports the cycle phases sequence, with
space for maximum 80 phases.
Each WORD contains two phases (one BYTE for each phase). Each BYTE contains the P/G number of the
phase.
xxxx xxxx
…
42154 42193
phase 2 , phase 1 phase 80 , phase 79
These are the P/G numbers of the cycle phases as listed in the PHASE LISTS of the initial data of the
process report, as you can see (with the corresponding addresses) in this example:
…………..
PHASE LISTS (a)
n. phase group n.
1 PREPARE AUTOCLAVE 1
[2154]
2 DEPRESSURIZE BY VACUUM PUMP 9
[2154]
3 TIMED VACUUM, STEAM INJECTION 20
[2155]
4 HEATING 41
[2155]
5 STERILIZATION 41
[2156]
6 DEPRESSURIZE BY VACUUM PUMP 9
[2156]
7 TIMED VACUUM 21
[2157]
8 RETURN TO ATMOSPHERIC PRESSURE 137
[2157]
9 CYCLE END 148
[2158]
10 EMERGENCY 156
[2158]
...
(a) There is a space limit for maximum 80 phases[2193]
The phase list depends on the selected program.
…………..
Starting from W30 also the P/G code is reported:
…………..
PHASE LISTS (a)
n. phase group n. code
1 PREPARE AUTOCLAVE 1 EA01F [6043..6045]
2 DEPRESSURIZE BY VACUUM PUMP 9 FV01Y [6046..6048]
3 TIMED VACUUM, STEAM INJECTION 20 VT02F [6049..6051]
4 HEATING 41 GH01S [6052..6054]
5 STERILIZATION 41 GH01S
6 DEPRESSURIZE BY VACUUM PUMP 9 FV01Y [6055..6057]
7 TIMED VACUUM 21 ET03F [6058..6060]
8 RETURN TO ATMOSPHERIC PRESSURE 137 KX01F [6061..6063]
9 CYCLE END 148 CY01F [6064..6066]
10 EMERGENCY 156 GZ01J [6067..6069]
...
(a) There is a space limit for maximum 60 P/Gs [6220..6222]
…………..
The five letters code is reported in a new segment of the area “Program composition” (Modbus address:
6043..6222 / OPC tags: RUNPROG.BASECYCLE.PG1 .... RUNPROG.BASECYCLE.PG60) which lists the cycle
as sequence of P/Gs, without repeating the code for the number of phases the P/G is composed of, with space
for maximum 60 P/Gs.

7.1.4 Process data

Process data are printed every 10 seconds in the process report. The printed data are taken by the current value
by the rispective address or TAG.
The print of phases of process data shows:
- Number of phase - Phase total time
- Current time of phase - Final phase data
- Current pressure
- Current temperature
PHASE 1 = PREPARE AUTOCLAVE [1501]

TIME PRESS. TE- 1
0:00 0.46 25.9 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
PHASE TOTAL TIME min.s 0:01 [1504-1505]
FINAL PHASE DATA
0:01 0.46 25.9 [1502-1503] [1518] [1522]
PHASE 2 = DEPRESSURIZE BY VACUUM PUMP [1501]

TIME PRESS. TE- 1
0:00 0.46 25.9 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
FINAL PHASE DATA
0:09 0.08 25.9 [1502-1503] [1518] [1522]
PHASE 3 = TIMED VACUUM, STEAM INJECTION [1501]

TIME PRESS. TE- 1
0:10 0.08 25.9 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
0:20 0.22 26.0 [1502-1503] [1518] [1522]
...
F 0.0 [1538-1539]
2:10 0.22 25.9 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
FINAL PHASE DATA
2:10 0.22 25.9 [1502-1503] [1518] [1522]
PHASE 4 = HEATING [1501]

TIME PRESS. TE- 1
2:10 0.22 25.9 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
2:20 0.34 25.3 [1502-1503] [1518] [1522]
...
F 0.0 [1538-1539]
2:50 1.84 113.0 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
3:00 1.98 120.0 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
FINAL PHASE DATA
3:00 1.98 120.9 [1502-1503] [1518] [1522]

PHASE 5 = STERILIZATION [1501]

TIME PRESS. TE- 1
3:01 1.98 121.6 [1502-1503] [1518] [1522]
F 0.0 [1538-1539]
3:10 1.98 120.1 [1502-1503] [1518] [1522]
.......
F 4.9 [1538-1539]
8:00 1.98 120.9 [1502-1503] [1518] [1522]
F 5.0 [1538-1539]
FINAL PHASE DATA
8:01 1.98 120.9 [1502-1503] [1518] [1522]
...
...
...
PHASE 8 = RETURN TO ATMOSPHERIC PRESSURE [1501]

TIME PRESS. TE- 1
12:49 0.09 31.9 [1502-1503] [1518] [1522]
F 7.9 [1538-1539]
...
F 7.9 [1538-1539]
20:00 0.09 31.9 [1502-1503] [1518] [1522]
F 7.9 [1538-1539]
FINAL PHASE DATA
20:07 1.01 31.9 [1502-1503] [1518] [1522]
PHASE 9 = CYCLE END [1501]

TIME PRESS. TE- 1
20:07 1.01 31.9 [1502-1503] [1518] [1522]
F 7.9 [1538-1539]
...
...

7.1.5 Batch end data

There are few different batch end data printout in Thema4 control system process report.
Here below are showed the different case:
Batch end data: CASE 1 – STERILIZATION WITH F(T,Z) CALCULATION

PROGRAM START TIME 14/03/07 13:03:19 [2824-2829]
PROGRAM END TIME 14/03/07 13:23:26 [2830-2835]
STERILIZATION N. 22 OK [2836.0]
MIN STERILIZ. TEMPERATURE °C 120.1 ( 1) [2846] ([2848])
MAX STERILIZ. TEMPERATURE °C 121.9 ( 1) [2847] ([2849])
STERIL. PHASE DURATION min.ss 5:00 [2842-2843]
STERILIZATION TIME min.ss 5:00 [2844-2845]
F(T,z) MIN: 7.9 ( 1) [2856-2857]([2861])
F(T,z) MAX: 7.9 ( 1) [2858-2859]([2860])
Batch end data: CASE 2 – TYNDALLIZATION

PROGRAM END TIME 14/03/07 13:23:26 [2830-2835]
MIN TYNDALLIZ. TEMPERATURE °C 100.1 ( 1) [2846] ([2848])
MAX TYNDALLIZ. TEMPERATURE °C 101.0 ( 1) [2847] ([2849])
TYNDAL. PHASE DURATION min.ss 5:00 [2842-2843]
Batch end data: CASE 3 - WIT SARTORIUS

FILTER TYPE xxxxxxxxxxxxxxx [2868-2875]
WIT TOLERANCE ml/10min xx.x [2876]
WIT TEST VALUE ml/10min xx.x [2877]
TEST OK or TEST FAILED [2836.4]
NET VOLUME ml xxx.x [2878]
ATMOSPHERIC PRESSURE bar x.xxx [2880]
INITIAL PRESSURE bar x.xxx [2881]
INITIAL TEMPERATURE °C xxx.x [2882]
FINAL PRESSURE bar x.xxx [2883]
FINAL TEMPERATURE °C xxx.x [2884]
Batch end data: CASE 4 - LEAK TEST

PROGRAM END TIME 14/03/07 13:23:26 [2830-2835]
LEAK TEST OK [2836.2]
TEST DURAT.: 10:00 [2837-2838]
NEGATIVE PRESS. VARIATION bar 0.010 [2840]-[2839]
POSITIVE PRESS. VARIATION bar 0.002 [2841]-[2840]
Batch end data: CASE 5 – GOLDEN CYCLE

WITH GOLDEN CYCLE: OK [2836.7]

Thema4 Control System SCADA Integration

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Thema4 Control System SCADA Integration

Uploaded by

Copyright:

Available Formats

Thema4 control system - THEMA4-SCADA INTEGRATION Page 1/155

THEMA4 CONTROL SYSTEM

FEDEGARI AUTOCLAVI SpA

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

DOCUMENT REVISION LIST

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

DOCUMENT MODIFICATION HISTORY

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

Revision 19 Paragraph 6.6.2 Added bit RUNPROG.F0ALL

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

3 COMMUNICATION PROTOCOLS USED IN THEMA4 SCADA

THEMA4 ARCHIVE MANAGEMENT

DATA BASE “TAGS TABLES

PROCESS REPORT TAGS

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

6.6.3 Program parameters: Sterilization .......................................................................................................63

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

6.15.2 Program identification ........................................................................................................................113

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

Section 1 THEMA4 CONTROL SYSTEM

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

1.1 APPLICATION TO THEMA4 SOFTWARE VERSION

- D/O#109386 – “Modbus Protocol Integration – Thema4 Control System”.

Modbus OPC Protocol THEMA4- Revision Subject

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

Section 2 THEMA4 CONTROL SYSTEM

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

2.1 THEMA4 HARDWARE ARCHITECTURE (WITH EXTERNAL

File config. File config.I/O RTOS

DATA AND FILE

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

2.2 THEMA4 SOFTWARE ARCHITECTURE

REAL TIME OPERATIVE SYSTEM(RTOS)

MS Windows O.S. MS Windows

These Thema4 software components are here listed:

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

- Modbus server TCP/IP that allows Modbus communication on Ethernet networks

This page is left intentionally blank

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

Section 3 THEMA4 CONTROL SYSTEM

3 COMMUNICATION PROTOCOLS USED

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

3.1 COMUNICATION PROTOCOLS

3.1.1 Communication protocols list

Protocol Physical Software utilized Ethernet connection

3 Modbus TCP/IP Ethernet Modbus TCP/IP server Standard

3.1.2 Communication modes

3.1.3 Protocols enablement

Option No. Communication protocol Connection Communication mode Function

OPT.2a Modbus RTU/ASCII RS232 SUPERVISOR Standard (*)

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

3.2 MODBUS PROTOCOLS

3.2.1 Modbus RTU/ASCII communication architecture (on serial line)

3.2.2 Modbus TCP/IP communication (on Ethernet network)

Fedegari Autoclavi SpA D/O# 162480.27 January 2018

3.2.3 General features of the Modbus communication protocol

Device Function Data bytes Error

The communication can be of two types:

Fedegari Autoclavi SpA D/O# 162480.27 January 2018