Asset_513657
Asset_513657
Description of
for
Content:
1987 The "ICS MUX fieldbus system" from R. STAHL is the first intrinsically safe bus system for sensors
and actuators in hazardous areas (Zone 1) on the market. A master station installed in the control
room establishes the connection to the automation systems. Intrinsically safe communication with
explosion-protected on-site or field stations (VOS) installed in Zone 1 is carried out using a single
coaxial cable.
1993 The system variant "VOS 200", which is based on ICS MUX, is presented. The "VOS 200" is better
suited to smaller signal quantities or decentralized automation units. A master station is no longer
required. Multi-drop is supported and couplings are also available in redundant designs.
1997 "VOS 200" can now also communicate with the PROFIBUS DP, which was new at the time.
R. STAHL achieved this by being the first to develop an intrinsically safe design which, with a few
modifications, is part of the PNO standard today under the name RS485-IS.
2000 Drawing from experience with the ICS MUX and VOS 200, a completely new Remote I/O – IS1 is
developed. This system is substantially more flexible, easier to use, more powerful and extremely
affordable. Over the years, the IS1 has become the market leader in Zone 1 and is still used around
the globe. IS1 supports open bus protocols such as PROFIBUS DP or Modbus RTU and is available
in different versions for Zone 1, Zone 2 and even Division 1 and 2.
2009 A new communication unit for Ethernet is added to IS1. With this, IS1 is the first remote I/O system
that operates at 100 Mbps/Ethernet in Zone 1. A fibre optic cable with the 'op is' type of protection is
used as a communication medium. Modbus TCP, EtherNet/IP and PROFINET are supported
protocols.
2013 The I/O level is completely modernised and introduced on the market as IS1+. The new
multifunctional I/O modules have configurable inputs/outputs and an innovative diagnostics function
that reports potential module failures up to 12 months before they would occur. IS1+ is even better
suited to extreme ambient conditions from -40 to +75 °C. The new IS1+ modules are fully compatible
with their IS1 predecessors.
2018 The new Zone 2 head assembly consists of a CPU, power module and socket makes IS1+ even
more flexible and has expanded its application range. The previously supported protocols
PROFIBUS DP, Modbus TCP+RTU, EtherNet/IP and PROFINET are now all supported by one CPU
and can be selected by the user. The new assembly has the same predictive diagnostic functions
and the extended temperature range of -40 to 75 °C that are features of the IS1+ modules.
The description below shows the system features of the IS1+ system when connecting to an automation
system via PROFIBUS DP.
1 System Overview
1.1 Connection principle of IS1+ field stations to the PROFIBUS
As an off-the-shelf explosion protected mounted unit, the IS1+ field station can be installed directly in the
hazardous area (Zone 1 or Zone 2 and Division 1 or Division 2). It can also be installed in the safe area. The
diagram above shows a Zone 1 solution.
The IS1+ field station has several interfaces. One of them is used to connect to an automation system
(Process Bus) and the second interface can be used as a bus-capable maintenance interface for the
configuration, error diagnosis and communication with HART field devices.
This functions can optionally be used via FDT technology and IS1 DTMs. Communication via PROFIBUS or
Service Bus DTMs is used in this case.
In addition, the 9442 CPU has an Ethernet interface. Diagnostics and firmware update functions are
available here via Web Server.
Several IS1+ field stations can be used in the hazardous area to form a PROFIBUS DP network that is
connected directly - both hierarchically and topologically - with the PROFIBUS network in the non-hazardous
area.
The following applies to Zone 1 installations:
From a safety-engineering aspect relating to explosion protection, the field bus isolating repeater for the
PROFIBUS takes on the function of a “barrier” between the Ex area and non-hazardous area.
The PROFIBUS installed in the hazardous area is using the RS 485-IS standard.
In such a PROFIBUS DP network, the IS1+ field station behaves hierarchically as a PROFIBUS slave where
the configuration of the field station is performed via the PROFIBUS master. Optional extended diagnostic and
parameterizing functions can be provided via PC-supported configuration programs (IS1 DTM via PROFIBUS
DP or IS Wizard via Servicebus).
Fig. 2 shows the possible transmission structures of several IS1+ field stations in a PROFIBUS network.
IS1+ field stations can be connected to the PROFIBUS in the hazardous area as well as in the non-
hazardous area. Both fiber optic technology as well as bus structures in multi-drop cabling
configurations are available in the hazardous area.
Class 1 masters are masters that are allocated one or more slaves. Only class 1 masters have write (setting
the outputs) and read (reading inputs) access to the slaves allocated to them. Class 2 masters only have read
access to slaves. Each slave can have only one class 1 master but several class 2 masters can be available
for each slave. A network can have several class 1 masters. However, only one class 1 master can have write
access to the slaves allocated to it. Masters can be both class 1 masters for one particular slave while they
are class 2 masters for other slaves.
Example:
Slaves A1 and A2 are allocated Master A as their class 1 master. Master A has no slaves allocated to it as
class 2 master.
Master B is allocated as the class 1 master of the Slave B1 and as the class 2 master of both Slave A1 and
Slave A2.
Data_Exchange Cyclic data exchange with a class 1 master, e.g. an automation system with one slave.
RD_Inp Reading of the input data by a class 2 master, e.g. PC for configuration and diagnosis
or another automation system.
RD_Out Reading of the output data of a slave by a class 2 master.
Slave_Diag Diagnosis data are sent to the class 1 master.
Set_Prm Configuration data are sent by the class 1 master to the slave (IS1).
Chk_Cfg Transmission of configuration data by the class 1 master to the slave and checking of
the configuration data received by the slave.
Get_Cfg Request of a class2 master to read the current configuration data of a slave.
Set_Slave_Add Not supported! The slave address is set by operating keys on the 9440 CPM of the
IS1+ field station or via rotary switches on the Socket of the 9442 CPU.
2 Commissioning
2.1 Overview
- Set up the bus connections. Ensure the correct bus termination of all segments!
- Set up the baud rate on the field bus isolating repeaters (9185, 9186,…) or select
´Auto Baudrate detection´ (available with 9185 and 9186).
- Put the master into operation. This results in the automatic start-up of the cyclic master <-> slave
Communication.
PROFIBUS diagnostic telegrams are supported in the two variants DPV0 and DPV1. The selection is
made by using different GSE file major versions (V2.xx, V3.XX, V4.xx V5.xx), as well as depending on the
support of the used PROFIBUS masters (PLC, DCS). Details see Diagnosis data
The data volume for the IO-Module of an IS1+ field station that can be transmitted is limited in the
PROFIBUS DP. Thus, the maximum possible number of IO-Modules in a field station is limited.
9440 CPM limitations apply when using the 9442 CPU with GSE V2.xx or V3.xx.
Length of the cyclic CPU/CPM data using GSE V2.xx und V3.xx
Cyclic data
Module selection text in the length [bytes] PROFIBUS
GSE file Input Output identifier [HEX]
9440/12-01-11 CPM Z1 Stahl 24V 1 1 30 - - - -
9440/15-01-11 CPM Z2 Stahl 24V 1 1 30 - - - -
9440/22-01-11 CPM Z1 PNO 24V 1 1 GIF 30 - - - -
9440/22-01-21 CPM Z1 PNO 230V 1 1 30 - - - -
9440/.. CPM without cyc Data *1) 0 0 00 - - - -
Length of the cyclic 9442 CPU data using GSE V4.xx and V5.xx
Cyclic data
Module selection text in the length [bytes] PROFIBUS
GSE file Input Output identifier [HEX]
CPU Status and Control Register *2) 1 1 c2 00 00 00 35
9445/35-12 PM 24V/5A Z2 *3) 0 0 SIF 02 00 34 - -
EM Extension Module *3) 0 0 02 00 36 - -
*2) The CPU status / control registers can be projected at 9442 CPU if necessary on any slot optionally.
It behaves like an empty module and the slot must remain empty. For this reason the slot address of the
following IO-Module are moved.
Hint: If the status / control registers is projected as the last module the after the real plugged IO-Module, the
slot addresses of the real plugged IO-Module remain unchanged.
The following table shows the length of the cyclic data of different types of IO-Module:
Cyclic data IO-
Komp.
Mode
Module selection text in the length [bytes] PROFIBUS
Module
GSE file Input Output identifier [HEX]
Type
9460/12-08-11 AIM 4/8 Exi 16 0 42 47 30 03 -
9461/12-08-11 AIMH 8 2w Exi 16 0 42 47 30 05 -
9461/12-08-11 AIMH 8+4HV 2w Exi 32 0 42 4f (cf *1) 31 05 -
9461/12-08-11 AIMH 8+8HV 2w Exi 48 0 42 57 (d7 *1) 32 05 -
9461/12-08-21 AIMH 8 Exi 16 0 42 47 30 06 -
9461/12-08-21 AIMH 8+4HV Exi - SIF IS1
32 0 42 4f (cf *1) 31 06 -
9461/12-08-21 AIMH 8+8HV Exi 48 0 42 57 (d7 *1) 32 06 -
9461/15-08-12 AIMH 8 2w Exn 16 0 42 47 30 07 -
9461/15-08-12 AIMH 8+4HV 2w Exn 32 0 42 4f (cf *1) 31 07 -
9461/15-08-12 AIMH 8+8HV 2w Exn 48 0 42 57 (d7 *1) 32 07 -
9462/12-06-11 SAIMH6 V1 2w Exi 16 4
9462/12-06-11 SAIMH6 V2 2w Exi 16 4 see operating PROFI
9462/12-08-11 SAIMH8 V1 2w Exi - ESIF
22 6 instructions SAIMH safe
9462/12-08-11 SAIMH8 V2 2w Exi 22 6
9465/12-08-11 AOM 8 Exi 0 16 82 47 40 09 -
9466/12-08-11 AOMH 8 Exi 0 16 82 47 40 0b -
9466/12-08-11 AOMH 8 +4HV Exi 16 16 c2 47 47 (c7 *1) 41 0b
9466/12-08-11 AOMH 8 +8HV Exi - 32 16 c2 47 4f (cf *1) 42 0b IS1
9466/15-08-12 AOMH 8 Exn 0 16 82 47 40 0c -
9466/15-08-12 AOMH 8 +4HV Exn 16 16 c2 47 47 (c7 *1) 41 0c
9466/15-08-12 AOMH 8 +8HV Exn 32 16 c2 47 4f (cf *1) 42 0c
9468/3x-08-xx 8AIH 18 0 42 48 70 2b -
9468/3x-08-xx 8AOH 2 16 c2 47 40 71 2b
9468/3x-08-xx 6AIH+2AOH 14 4 c2 41 46 72 2b
9468/3x-08-xx 8AIH/8AOH 18 16 c2 47 48 73 2b
9468/3x-08-xx 8AIH +4HV 34 0 42 50 (d0 *1) 74 2b -
- SIF
9468/3x-08-xx 8AOH +4HV 18 16 c2 47 48 (c8 *1) 75 2b
9468/3x-08-xx 8AIH/8AOH +4HV 34 16 c2 47 50 (d0 *1) 76 2b
9468/3x-08-xx 8AIH +8HV 50 0 42 58 (d8 *1) 77 2b -
9468/3x-08-xx 8AOH +8HV IS1+
34 16 c2 47 50 (d0 *1) 78 2b
9468/3x-08-xx 8AIH/8AOH +8HV 50 16 c2 47 58 (d8 *1) 79 2b
9468/3x-08-xx 8AIMH No Stat 16 0 42 47 30 05 -
9468/3x-08-xx 8AIMH+4HV No Stat 32 0 42 cf 31 05 -
9468/3x-08-xx 8AIMH+8HV No Stat 48 0 42 d7 32 05 -
x
9468/3x-08-xx 8AOMH No Stat 0 16 82 47 40 0b -
9468/3x-08-xx 8AOMH+4HV No Stat 16 16 c2 47 c7 41 0b
9468/3x-08-xx 8AOMH+8HV No Stat 32 16 c2 47 cf 42 0b
9469/35-08-xx 8IH Exn 18 0 42 48 80 32 -
9469/35-08-xx 8OH Exn 2 16 c2 47 40 81 32
9469/35-08-xx 6IH+2OH Exn 14 4 c2 41 46 82 32
9469/35-08-xx 8IH/8OH Exn 18 16 c2 47 48 83 32
9469/35-08-xx 8IH +4HV Exn 34 0 42 50 (d0 *1) 84 32 -
-
9469/35-08-xx 8OH +4HV Exn 18 16 c2 47 48 (c8 *1) 85 32
9469/35-08-xx 8IH/8OH +4HV Exn 34 16 c2 47 50 (d0 *1) 86 32
9469/35-08-xx 8IH +8HV Exn 50 0 42 58 (d8 *1) 87 32 -
9469/35-08-xx 8OH +8HV Exn 34 16 c2 47 50 (d0 *1) 88 32 IS1+
9469/35-08-xx 8IH/8OH +8HV Exn 50 16 c2 47 58 (d8 *1) 89 32
9469/35-08-xx 8AIMH No Stat 16 0 42 47 30 07 -
9469/35-08-xx 8AIMH+4HV No Stat 32 0 42 4f (cf *1) 31 07 -
9469/35-08-xx 8AIMH+8HV No Stat 48 0 42 57 (d7 *1) 32 07 -
x
9469/35-08-xx 8AOMH No Stat 0 16 82 47 40 0c -
9469/35-08-xx 8AOMH+4HV No Stat 16 16 c2 47 47(c7 *1) 41 0c
9469/35-08-xx 8AOMH+8HV No Stat 32 16 c2 47 4f (cf *1) 42 0c
Disadvantage: When using IS1 DTM or I.S.Wizard is to note in this case, that the compatible older
IS1 IO-Module without signal status bits has to be configured in these tools manually to enable a consistent
upload of the parameter from IS1. The ´scan topology´ function of FDT frames or the function ´Generate
Configuration Data According Hardware´of I.S.Wizard cannot be used in this case because here the
descriptors of the IS1 + IO-Modules and not the descriptors of the older IS1 IO-Modules are added to the
project. Mapping of compatible IO-Module see Compatibility of new IS1+ IO-Module
Therefore the use of module descriptions with ´No Stat´, ´9470/2´ or ´9471/1´ in combination with
applications using IS1 DTM or I.S.Wizard is possible with above mentioned reservations, but not
recommended.
The telegram length of the cyclic input and output data of a field station depends on the type and number of
IO-Module used. The above mentioned limits of a field station depending on the used CPU and GSE version
must also be observed here.
Moreover, further limitations of the number of IO-Modules, the maximum number of signals and the maximum
number of slaves in a network ... depend on the performance of the DP master used. Thus, the limits of the
DP master used must also be taken into account during the engineering.
9442 CPU with power module PM 9444 and socket 9496 can replace previous 9440/15 CPM fully compatible
with the exception of line redundancy.
Existing configurations of 9440/15 with GSE V2.xx or GSE V3.XX can remain in the PROFIBUS Master
unchanged. The limitations of data length on PROFIBUS of the CPM 9440/15 remain unchanged in this
case.
If extended data length of 9442 CPU shall be used, a modified configuration with 9442 CPU and GSE V4.xx
(DPV0) or V5.xx (DPV1) has to be configured.
Date Length see Engineering limits
New IS1+ IO-Module can be used in existing plants for compatible replacement of previous IS1 IO-Module.
No change of GSE File or configuration is required in such case.
The IS1+ IO-Module switch to a compatible mode in case of detection of an allowed configuration of the
previous IO-Module.
If new features of the IS1+ IO-Module shall be used which are not supported by the previous IO-Module new
configuration with new GSE file according type number of the IS1+ IO-Module is required.
Software requirements:
9442 CPU: All CPU FW Revisions together with IS1 IO-Module from FW 02-00
or IS1+ IO-Module (94xx/3x….) from FW 03-01
Older IS1 IO-Modules with firmware 01-xx can be operated with 9440 CPUs only!
9440 CPM:
IS1+ IO- CPM FW from V01-47 CPM FW from V02-47, 03-47 or 09-47
from
Module
03-01
(94xx/3x….) GSE from V2.32 GSE from V3.10 GSE from V2.32 GSE from V3.10
The IS1+ Remote I/O-system with PROFIBUS DPV1 supports the following additional functions:
o from Revision 02-00 and up for non PROFIsafe IS1 I/O modules
o from Revision 03-00 for all IS1+ I/O modules (94xx/3x……)
Using 9442 CPUs or 9440 CPM with firmware from V02-40 and GSE from V3.00 the contents of the
diagnosis telegram for the complete IS1+ station has been changed according DPV1 rules. Check if
Master System supports DPV1 diagnosis mechanism.
PROFIBUS IS1
GSE File Documentation Application
diagnosis Parameter set
document ´ Operating Product maintenance
Revisions V1.xx Instructions (Use of IO-Modules V1.xx)
Standard Not for new projects !
(File name: STA_049A.gse) PROFIBUS DP for
Not supported by 9442 CPU.
IS1+ field stations´
DPV0
Revisions V2.xx Standard solution
for new projects with
(File name: STA2049A.gse)
9440 CPM
New projects
with DPV1 compatible
Revisions V3.xx DP Masters
DPV1 and for use with
extended (File Name: STA3049A.gse) this document PROFIsafe
e.g. S7-400H
S7-300F, S7-400F …
Revisions V4.xx
DPV0 Standard solution
(File Name: S4xx049A.GSE)
for new projects with
Revisions V5.xx 9442 CPU
DPV1
(File Name: S5xx049A.GSE)
Configuration rules:
9440 CPM with GSE V2.xx and V3.xx 9442 CPU with GSE V4.xx and V5.xx
The CPM module (module no. / slot = 0) must be
Only I/O modules are configured starting from slot 1.
configured first.
A separate CPU descriptor as used with 9440 CPMs
Even if redundant CPMs are used, only the CPM in
is not used. Optionally the status / control register
slot 0 needs to be configured as, from the point of
can be projected once when needed as a separate
view of the master, there is only one CPM per IS1+
module.
Fieldstation.
Configuration of the IO-Module slot coded from slot 1 (module no. 1)
according to the IO-Modules that are planned or are present in the system.
Only PROFIBUS Identifiers ac. the list in chapter 2.2 are allowed
max. telegram length (239 (+1) Bytes Input and 127 max. telegram length (244) Bytes Input and 244 Byte
(+1) Byte Output data is checked Output data is checked
max. number of IO-Module (max. 16) is checked with
Check of
GSE V2.xx and up to V3.02
- max. 16 IO-Modules using GSE V4.xx
max. number of IO-Module (max. 15) is checked with
- max. 15 IO-Modules using GSE V5.xx
GSE from V3.03 supporting PNO redundancy and
+ status / control register (once, optional)
structured parameterization.
The configuration data and parameters required for the slave are transmitted from the master to the slave
during the start-up process.
Attention!
The CPU checks the a. m. engineering and configuration rules.
-> In case of error, the CPU does not go into the “Data_Exchange” state.
The “Cfg_Fault” message is transmitted in the diagnosis telegram.
If none of the errors listed above occur, the CPU accepts the configuration data and goes into the
“Data Exchange” state with the DP master.
If the modules that are plugged in do not correspond to the modules configured in the master,
those modules that do not do not correspond with the configuration data of the master are
indicated in the diagnosis data.
The signals of the wrongly configured modules are considered to be garbled (corrupted) and
processed according to the parameterised behaviour that applies if an error occurs.
All signals of modules which correspond to the modules configured in the master are in operation
(signals are updated cyclically).
Example of a configuration list of an IS1+ field station in the configuration software of a DP master:
*1) For example, register addresses of a PLC. An address can only be allocated in the green areas. Grey
areas are locked as no slave data are allocated here.
Please note that addresses may only be allocated once in a PROFIBUS network.
The same address is also valid for addressing the IS1+ field station on the service bus.
(see also the CPU operating manual)
The start-up behavior of the cyclic communication between a class 1 master and a DP slave is standardized
and is handled automatically by the master. During the start-up process, the master and slave exchange
information on data block length, structure of data blocks (assignment to modules), parameters and Watchdog
status .....
The class 1 master transmits configuration data to the CPU by means of the "Chk_config" service. This service
checks the data for compatibility. After checking this successfully, the CPU takes over the new configuration
data and subsequently responds to "Get_Config" telegrams with the new data.
The implementation of the service bus and the I. S. Wizard PC software is not necessary in this operating
mode. However, these tools and the HART Management System can be used if required.
The data block length and module assignment are not parameterized in the configurator of the master in this
variant. This information is read by the master from the slave during the start-up process using the “Get_Config”
service. Only the allocation of data to the internal registers needs to be either defined in the master or
automatically allocated.
If the CPU is involved in cyclic data exchange with a class 1 master, the module configuration defined by the
class 1 master is used vis-à-vis the class 2 master.
If the CPU is not involved in cyclic data exchange with a class 1 master, empty modules are transmitted to the
class 2 master by means of the “Get_Config” service. The real present modules cannot be read in this
operation mode.
Typical start-up process between a class 1 master (M) and slave (S)
The following table shows the typical telegram traffic between master and slave during the start-up process:
Start-up process:
IS1 supports both solutions. The two solutions are not compatible with one another and must be projected
differently. Therefore, a clear distinction must be made as to which version is to be used.
Selection for the 9442 CPU via the backplane switch S1:
S1 = 1 PROFIBUS PNO Redundancy. (recommended for new projects)
S1 = 2 PROFIBUS Stahl Redundancy Addr. Offs. 1
S1 = 3 PROFIBUS Stahl Redundancy Addr. Offs. 0
The distinction between STAHL and PNO redundancy for the 9440 CPM is done by selecting the CPM
firmware and the associated GSE file:
DPV1 Version
IS1 CPM V02-42 from V03-42 (with C2 communication, HART,
Firmware DTM support, I&M, …)
DPV1 Version
V09-42 - (as above, but
Offset backup addr. = 0 )
*1) Attention! When using GSE files from V3.03 in connection with IS1 9440 firmware up to V0x-41, a
parameterization error is reported when IS1 is started, if the PLC supports structured parameterization
according to DPV1 (e.g. S7-300 and S7-400). In this case, IS1 will not enter Data_Exchange.
Remedy: use firmware from V0x-42 or GSE up to 3.02.
A mix of redundant CPMs with firmware acc. R.STAHL spec. and PNO spec. is not allowed in one IS1 field
station. Rule for redundant operation of two IS1 CPMs: Firmware from the same row (01-xx or 02-xx or 03-xx
or 09-xx) shall be used in both CPMs.
In the PNO specification for PROFIBUS slave redundancy (Doc. 2.212 R1.2), different redundancy structures
have been defined. IS1 supports all versions of these redundancy structures. Master and Slave redundancy
are independent and can be combined optionally.
Function:
During slave start-up, the DP master transmits specific parameters redundantly to the slaves and monitors the
connection both to the primary and the backup slave. Cyclic data are exchanged with the primary slave.
The decision to switch over when an error occurs is made by the slave. When a switchover takes place, the
previous backup CPU takes over and becomes primary. Input and output signals are frozen during the
switchover.
Optionally in case of system redundancy, the DP master can trigger a switchover of a redundant slave, for
example for testing, via a control command (DPV1 PrmCmd).
In case of flying redundancy the primary- and backup address of a redundant slave are exchanged during
switch over.
A failure of the backup CPU is reported via the “Backup Slave Not Available” device-specific diagnosis as well
as the CPU status register in the cyclic data of the primary CPU.
Backup CPU has no connection to PROFIBUS and does not detect ´Baudrate found´.
Short- or open circuit on Profibus
Wrong end of line termination switching
Fault or no power of fieldbus isolation repeater
Communication between primary and backup CPU failed
Power fail of backup CPU
Hardware fault of backup CPU
IS1 CPU 9442 with protocol selection switch S1 = 1 or CPM 9440 with Firmware from V03-42 is required.
Both 9442 CPUs of an IS1+ field station work with the DP address set via rotary switches S2 and S3 on
the socket.
Both 9440 CPMs in one redundant IS1+ field station are set to the same DP Address.
The backup CPU or CPM adds an offset to this address according the parameter ´Address offset backup
CPU PNO Red´.
Only one of two redundant CPUs is configured in the DP master with the primary DP address.
The application in PLC/DCS is using only the primary CPU for exchanging I/O data.
Consider that the backup address according parameter ´Address offset backup CPU PNO Red´
is allocated and shall not be used twice.
Cyclic or acyclic communication between DP master and the backup CPU may be optionally used for
checking the backup communication line.
The accepted ´Max. Slave switch over time´ from the DP master for bumpless switch over depends on
the setting of DP Watchdog time and the DP master cycle.
Max. Slave switch over time [ms] = DP-Watchdog + (3 * DP master cycle) + 470ms
Recommendation using Siemens PLCs with IS1+: use DP Master profile ´Universal (DP/FMS)´.
Hint: Additionally to the IS1 GSE parameter a parameter Output_Hold_Time may exist in the DP master or slave
parameter area of some DPV1 host systems supporting slave redundancy according PNO specification.
IS1 GSE parameter remain always effective. Settings from the host system are not applied in this case to achieve
identical behavior in all systems.
1 proprietary Solutions
* 1) The address of the backup CPU must be as at all DP devices in the range 1 to 127.
Therefore, only addresses from 1 to 63 are allowed for the primary CPUs.
PLC / PLC /
Master
Master
DCS DCS
DP
DP
9185 or 9186
Fieldbus Isolating Repeater
Ex Zone 1
X1 X1 X1 X1
CPU
CPU
CPU
X1 X1 X1 X1
CPU
CPU
CPU
(backup)
DCS
DP M
DP M
Ex Zone 1
X1 X1
IS1 I/O
CPU
CPU
X1 X1
IS1 I/O
CPU
CPU
Function:
- The switchover criterion between primary and backup CPU is generated in the IS1 CPUs. No support from
control commands by the DP master is required.
- Our GSE versions 2.xx support DP master systems which do not yet support DPV1 diagnoses.
- A failure of the backup CPU is reported via the “Backup Slave Not Available” device-specific diagnosis as
well as the CPU status register in the cyclic data of the primary CPU.
- From the point of view of the DP masters, the slave (IS1 CPU) will fail for a short period during a switchover
between the primary and backup CPU and return to the Data_Exchange after approx. 500 ms - 800 ms
using 1,5 MBaud (see table in chapter Project planning ).
During the switchover of IS1, output signals are frozen are thus bumpless. The maximum allowed switch
over time can be set by the parameter ´timeout output modules´.
For bumpless switchover of the input signals, the only additional support required by the DP master is a
toleration of such a short-term slave failure. Input signals and the signal and device status must be
frozen during this DP master switchover time. Thus, the short slave failure is hidden from the application
software in AS. If possible, the slave failure time tolerated by the DP master should be configurable. If a
slave fails for more than the configured slave failure time, the appropriate safety reaction can take place
in the AS.
- For standard DP masters which do not tolerate such a short slave failure, the application software will see
this short slave failure in the AS.
With some systems and suitable design of the application software, such a bump can be tolerable. This
must be checked in each individual project.
- Optionally, the bumpless switchover of input signals can be effected on the application level in the
AS for each specific project.
For example, input signals can be copied from the DP master input/output image to a second memory
area the remaining application software has access to. In this case, during the slave switchover phase,
transfer between these two memory images is prevented, thus freezing the memory area of the
application. The behavior of the system messages in the AS must also be taken into account.
For function-block-based systems, it is possible, for example, to insert a proprietary block, which carries
out a bumpless switchover, for each input signal.
2.10.2.1 Functions
An IS1+ field station can be equipped with two central units (CPU), whereby each CPU has its own independent
PROFIBUS DP interface.
From the point of view of the automation system, each field station has 2 separate DP slaves, and both are
involved in the cyclical data exchange with the DP master. Thus, there are two independent transmission paths
between the DP master and the field station.
These two transmission paths are monitored for proper and error-free operation by user software in the
automation system. In addition, one of the transmission paths is selected to transmit the useful data. The
CPU linked to the transmission path selected by the AS is switched to primary mode (active) by transmitting a
control register from the AS to the CPU.
Of course, data can also be transmitted through the other (inactive) transmission path. However, it only helps
to monitor the connection. Data transmitted here is not used.
Only the active CPU handles the data traffic to the field station I/O modules. The active CPU monitors the
inactive CPU and likewise provides it with the current input data.
AS DP
Master
Module
PROFIBUS DP
Ex Area
CPU CPU I/O
left right Module
IS1+ Fieldstation
AS
DP DP
Master Master
Module Module
IS1+ Fieldstation
IS1
AS DP AS DP
Master Master
Module Module
.
IS1+ Fieldstation
IS1
Parallel cyclical data traffic can be defined via PROFIBUS DP for both CPUs (both CPUs are in data
exchange).
Both CPUs in an IS1+ fieldstation are connected with the non-redundant installed I/O modules.
The two CPUs in an IS1+ fieldstation are not allowed simultaneous access to the I/O modules. For this reason,
only one CPU is switched to active status by a control register from the AS software.
The active CPU takes over the access to the I/O modules (read and write).
The other CPU is in the ‘inactive’ status. The active CPU updates the input data in the inactive CPU in a cycle
and monitors it for correct operation.
As a result, input data can be read cyclically by both CPUs, in error free standard operation mode.
The data between the active CPU and the inactive CPU can be different in case of error! Therefore the data
of the inactive CPU should not be used for the application software.
Although the automation system does receive output data in ‘inactive’ status via the PROFIBUS and this data
is stored in the CPU RAM, it is, however, not forwarded to the output modules.
The actual status of the two redundant CPUs can be read from the Status register CPM
TMod must be parameterised greater than the maximum total time between the occurrence of a
transmission error and the activation of the hitherto inactive CPU (switching time).
The maximum switching time is defined by the parameterized DP master bus cycle, the PROFIBUS baud
rate, the monitoring software cycle time in the automation system and the startup delay of the CPU (< 500
ms).
The IS1 timeout time for output modules (T MOD) can be parameterized in the DP master in the range of 100
ms to 25.5 sec. (default value: 1 s).
When the status of a CPU is changed from inactive to active via the control register, there is a delay of
500ms (maximum) before the CPU will report its status as active.
If the (previously active) CPU contains valid input data, then this information is transferred to the AS within
this time. The AS can then use this input data immediately after switch over.
If the now active CPU receives new configuration data, so that the input data of the previously active CPU
cannot be used, all the IO-Module must be initialized by the now active CPU. In this case, new input data is
not available before the CPU reports its status as active in the status register.
The AS therefore cannot use any data that was transmitted before the CPU reported its status as active.
CPU 9442
CPM 9440 Offset right
Protocol selection left CPU right CPU Application
Firmware Rev. CPU address
(Socket Switch S1)
S1 = 2
V01-xx, V02-xx PROFIBUS Stahl Red. address n address n+1 +1 standard
Addr. Offs. 1
S1 = 3
V09-xx PROFIBUS Stahl Red. address n address n 0 on demand only
Addr. Offs. 0
Both slave devices must be configured separately in the DP master configurator with identical I/O
arrangements and parameterized with identical slave parameters.
(Recommendation: first configure and parameterize the left slave and then copy the complete slave to the
second (right) slave.
Consequently, there is a separate memory area with the respective associated I/O data for each of the CPUs.
For the CPU parameters, set the parameter ‘CPU redundant = Yes’ in the DP master configurator.
When configuring a field station with CPU redundancy, the CPU with the additional ‘Red.’ from the module list
of the GSE file must be configured as the first module in both slaves (Module No. / Slot = 0) (for example,
‘9440/..-..-.. CPM Zone 1 Red.’) in the DP master.
The CPU has 1 byte input data (status register) and 1 byte output data (control register), which is transmitted
in the cyclical data area from PROFIBUS DP. These registers help to control and monitor the redundancy by
means of the AS.
Even if redundant CPUs are used, you must configure only one CPU in slot 0 per field station, as from the
point of view of the master, there are two slaves with one CPU each respectively.
Software parts required in the automation system for redundancy support are almost identical for all the
described redundancy structures.
Check the availability of both transmission paths in the automation system by using an application program
and make one of the transmission paths active. Data can be exchanged between the application software and
the IS1+ fieldstation I/O modules only via the active transmission path.
The automation system monitors the redundant transmission paths by implementation and analysis of the
PROFIBUS service ‘Read Slave Diagnosis’.
In the first byte of the received diagnosis telegram, Bit No. 0 returns and indicates whether the addressed
PROFIBUS slave is involved in the cyclical data exchange or not.
After using this service for both CPUs, a logic in the AS helps to select one of the transmission paths (from
either CPU) to be activated. By transmitting the control register from the AS to the CPUs, the result of this
decision is notified to the CPUs, which react accordingly.
Analysis of
diagnosis telegrams
No
Left and right
CPU available ?
Yes No
Left and right
CPU disturbed ?
Automation system
Application (User program)
I/O-Data (RAM)
Application
PROFIBUS DP
IS1+
Field station
CPU CPÚ
left I/O-Data right I/O-Data
(RAM) (RAM)
I/O-Module
Automation system
I/O-Data (RAM)
Application
PROFIBUS DP right
PROFIBUS DP left
IS1+
Field station
CPU CPU
I/O Data I/O Data
left right
(RAM) (RAM)
I/O Module
Initialization of the
data memory of the
application
Left CPU
No
active ?
No
Yes Right CPU
active ?
Yes
Interface
Zone Type Power supply Protocol as of Release
CPM / FB-TÜ PLC
1 9440/22-01-11 24 V DC PROFIBUS A 01-32, 02-32 X1 / X2 -
1 9940/22-01-21 90-250 V AC PROFIBUS B 01-32, 02-32 X1 / X2 -
2 9440/15-01-11 24 V DC PROFIBUS G 01-32, 02-32 X1 / X2 -
1 (bus) 9185/11-35-10 24 V DC - D 01-02 X3 X2
2 9185/12-45-10 24 V DC - D 01-02 X3 X2
9185
Fieldbus
Isolating
Repeater
Protocol: PROFIBUS DP
Bus structure:
Bus data:
• CPM with and without Line Redundancy can be used on one redundant bus segment.
• Number of devices per bus segment ≤ 32
• Max 2 repeater 9185 can be used in series.
• Cable length per bus segment according PNO standard
• Operation of any PROFIBUS slaves on redundant and on non redundant bus segment
allowed ( and ). For all DP slaves on the redundant bus segment the parameter
Tsdr-min must be set to ≥ 33 t-bit in the PROFIBUS DP master !
3 Data traffic
3.1 Configuration
Input data (Read) and output data (Write) are each transmitted cyclically in a telegram.
In this case, the data blocks of the individual modules are grouped into telegrams in the order defined in the
configuration software of the PROFIBUS master.
If empty modules are configured, no data is transported in these locations of the data telegram and no
diagnosis data is generated for the associated slot.
During the start-up of the automation system, parameters are transmitted by the DP class 1 master to the CPU
in the "Set parameters" telegram. In addition to the standardized part of this telegram, the optional
"USER_PRM_DATA" data area is also transmitted. The data area used for an IS1+ field station has a fixed
length of 3 Bytes DPV1 status + 7 bytes (10 Bytes using GSE V5.xx) for the CPU and additional 14 Bytes
(extended parameter set) for every IO-Module.
00 01 00 00 00 00 0x 01 01 00 xx xx … xx xx xx xx … xx xx .. .. .. xx xx … xx xx
3 bytes DPV1 status + 7 bytes 14 bytes for IO-Module1 14 bytes for IO-Module 2 .. IO-Module n
(3 bytes DPV1 stat.+ 3 bytes block. H.
+ 7 bytes using GSE V5.xx)
parameters for CPU
The CPU checks the length of the parameter data and rejects the parameter data if this length is
incorrect. If an error occurs, the CPU does not go into the “Data_Exchange” state. The “Prm_Fault”
message is transmitted in the diagnosis telegram.
CPU parameters
Default
Byte Bit Function
Value
0 - 0x00
(0x00 using DPV0) DPV1
1 - 0x01 Content pending on used DPV1 functions according DPV1 Status
Spec. Bytes
2 - 0x00
- 0x0a
-
3 Byte Block
0x81 (used with GSE V5.xx only)
header
- 0x00
Address offset backup CPU
Bit 1 Bit 0
0 using PNO Redundancy
0 0 128 FR -
1 1 0 1 FR -
1 1 64 FR acc. PNO Spec.
2-7 Reserved
4 - 0x00
Reserved
5 - 0x00
0x01 DPV0 + standard parameter set (GSE 1.xx) for 9440 CPM
0x02 DPV0 + extended parameter set (GSE 2.xx) “
6 - 0x03 DPV1 + extended parameter set (GSE 3.xx) “ CPU
0x04 DPV0 + extended parameter set (GSE 4.xx) for 9442 CPU Parameter
0x05 DPV1 + extended parameter set (GSE 5.xx) “
*1) GSE V3.xx and V5.xx only: Slot information in DPV1 diagnosis telegram is incremented by 1 in Module
status und IO-Module status blocks if parameter Slot Offset DPV1 Diagnosis = 1.
Usage:
For DPV1 Master systems which start slot counting from 1 and not from 0 as usual for IS1+ systems.
(e. g. Siemens S7). Available with 9440 CPM firmware from Rev. 03-45 and GSE V3.05
*2) used with CPM 9440 and GSE V2.xx and V3.xx only
IO-Module parameters
3.2.3.1 AIM / AIMH (SAIMH see operating instruction SAIMH 9462/... PROFIsafe)
*1) The parameters ´ Measurement range ac. NAMUR ´ are valid only for Input Signals!
The parameters are visible for all switchable AI/AO Signals but are without effect for the AO signals.
*2) The parameters ´Signal type Sx´ are available only for AI/AO switchable channels in the operating
modes 9468/3x-08-xx 8AIH/8AOH (+4HV / +8HV)
Off
Scan HART livelist On
On
Input No. HART device for pos. 1 Not used
Input No. HART device for pos. 2 Not used
Input No. HART device for pos. 3 Not used
Input No. HART device for pos. 4 Not used
Input No. HART device for pos. 5 Not used 0…7
Input No. HART device for pos. 6 Not used ´Not used´
Available only
Input No. HART device for pos. 7 Not used on HARTmodules
Input No. HART device for pos. 8 Not used (AIMH) !
No. HART variable for pos. 1 HART variable No. 2
No. HART variable for pos. 2 HART variable No. 2
No. HART variable for pos. 3 HART variable No. 2 HART variable No. 1
No. HART variable for pos. 4 HART variable No. 2 HART variable No. 2
No. HART variable for pos. 5 HART variable No. 2 HART variable No. 3
No. HART variable for pos. 6 HART variable No. 2 HART variable No. 4
No. HART variable for pos. 7 HART variable No. 2
No. HART variable for pos. 8 HART variable No. 2
No *1)
Measurement range ac. NAMUR No
Yes
0-20 mA
Signal range 4-20 mA
4-20 mA
Signal in case of error I0 AI Status Code / AO 0% /0
Signal in case of error I1 AI Status Code / AO 0% /0 -10 % (nur 4 mA) /0
Signal in case of error I2 AI Status Code / AO 0% /0 0% /0
100 % /1
Signal in case of error I3 AI Status Code / AO 0% /0
AI Status Code / AO110 % / 1
Signal in case of error I4 AI Status Code / AO 0% /0
AI Status Code / AO 0% / 0
Signal in case of error I5 AI Status Code / AO 0% /0 freeze (initial value 0% / 0)
Signal in case of error I6 AI Status Code / AO 0% /0 freeze (initial value 100% / 1)
Signal in case of error I7 AI Status Code / AO 0% /0
Error detection I 0 On
Error detection I 1 On
Error detection I 2 On
Error detection I 3 On Off
Error detection I 4 On On
Error detection I 5 On
Error detection I 6 On
Error detection I 7 On
Connection S 0 2 wire analog
Connection S 1 2 wire analog
2 wire analog
Connection S 2 2 wire analog
Connection S 3 2 wire analog
Connection S 4 2 wire analog
2 wire analog
Connection S 5 2 wire analog
3/4 wire analog (Input only)
Connection S 6 2 wire analog
digital
Connection S 7 2 wire analog
Signal type S0
Signal type S1
Signal type S2
Signal type S3 Input *2)
Input
Signal type S4 Output
Signal type S5
Signal type S6
Signal type S7
Off
Scan HART Livelist On
On
Input No. HART device for pos. 1 Not used
0…7 Available if HART
... ... variables (HV) are
´Not used´
Input No. HART device for pos. 8 Not used configured
only.
No. HART variable for pos. 1 HART variable No. 2 HART variable No. 1
HART variable No. 2
... ... HART variable No. 3
No. HART variable for pos. 8 HART variable No. 2 HART variable No. 4
Parameter
Signal Measurement
Signal Signal Error Signal in Input
connection range ac.
type range detection case of error Filter
NAMUR
2 wire
2 wire 0/4-20 mA Input Input analog
0-20 / 4-20 Yes / No
Small
2/3 wire
2/3 wire Initiator Input Input digital
- - Medium
-10 % (nur 4 mA) /0 Big ( 50 Hz)
0% /0
3/4 wire 100 % /1
Big (60 Hz)
3/4 wire 0/4-20 mA Input Input analog 0-20 / 4-20 On / Off Yes / No AI Status Code / AO110 % / 1
(Input only) AI Status Code / AO 0% / 0
freeze (initial value 0% / 0)
freeze (initial value 100% / 1)
2 wire
2 wire 0/4-20 mA Output Output analog
0-20 / 4-20 - -
2/3 wire
Digital Output Output digital
- - -
*1) The parameter ´Measurement range ac. NAMUR ´ are effective for analog input signals only!
*2) The Parameter ´Signal type´ is available for switchable signals in the operating modes with 8I + 8O only.
Type I 0 Pt 100
Pt100
Type I 1 Pt 100 Pt500
Pt1000
Ni100
Type I 2 Pt 100 Ni500
Ni1000
Type I 3 Pt 100 Resistance 10k
Resistance 5k
Type I 4 Pt 100 Resistance 2k5
Resistance 500R
Type I 5 Pt 100 Pt100 GOST
M50 GOST from Fw. V02-04
M100 GOST
Type I 6 Pt 100 Cu53 GOST
Pt46 GOST from Fw. V02-05
Type I 7 Pt 100 Pt50 GOST
Connection I0 4 wire
Connection I1 4 wire
Connection I2 4 wire
Connection I3 4 wire 2 wire
3 wire
Connection I4 4 wire
4 wire
Connection I5 4 wire
Connection I6 4 wire
Connection I7 4 wire
*1) Parameter ´Connection´ using THC not functioning. 2 wire measurement is used for TCH
3.2.3.10 DOM
10 .. 13 00 Not used
0 0 = PT100
5 00 Type TC ext. cold junction I6-I7 1 = PT1000
0 2 = PT100 GOST
0 Reserviert
0 Reserviert
0 Reserviert
0 Reserviert
0 0 0 0 0 0 Type I 0 Type :
6 80 0 = Pt100
1 = Pt500
1 0 Connection (R) I 0 2 = Pt1000
3 = Ni100
0 0 0 0 0 0 Type I 1 4 = Ni500
7 80 5 = Ni1000
1 0 Connection (R) I 1 6 = Resistance (Pot)10k
7 = Resistance (Pot) 5k
8 = Resistance (Pot) 2k5
0 0 0 0 0 0 Type I 2 9 = Resistance (Pot) 500R
8 80 10 = Pt100 GOST
1 0 Connection (R) I 2 11 = M50 GOST
12 = M100 GOST
0 0 0 0 0 0 Type I 3 13 = Cu53 GOST
14 = Pt46 GOST
9 80
15 = Pt50 GOST
1 0 Connection (R) I 3 (16…31 = reserved)
32 = 0…100 mV
0 0 0 0 0 0 Type I 4 33 = THC Type B
10 80 34 = THC Type E
1 0 Connection (R) I 4 35 = THC Type J
36 = THC Type K
37 = THC Type N
0 0 0 0 0 0 Type I 5
38 = THC Type R
11 80 39 = THC Type S
1 0 Connection (R) I 5 40 = THC Type T
41 = THC Type L
0 0 0 0 0 0 Type I 6 42 = THC Type U
12 80 43 = THC Type XK(L)
(44…63 = reserved)
1 0 Connection (R) I 6
Connection (R): *1)
0 0 0 0 0 0 Type I 7 0 = 2 wire measure (Pot in Ohm)
1 = 3 wire measure (Pot in %)
13 80 2 = 4 wire measure (Pot in Ohm)
1 0 Connection (R) I 7 3 = 4 wire measure (Pot in %)
*1) Parameter ´Connection´ using THC not functioning. 2 wire measurement is used for TCH
12 .. 13 00 Not used
3.2.4.9 DOM
Byte Hex 7 6 5 4 3 2 1 0 Parameter Value
0 = Off
1 Diagnostic messages of the module
0 01 1 = On
0 0 0 0 0 0 0 Not used
0 0 0 Signal in case of error O 0 0=0
0 Not used 1=1
1 00
0 0 0 Signal in case of error O 1 2 = Freeze
0 Not used
0 0 0 Signal in case of error O 2
0 Not used
2 00
0 0 0 Signal in case of error O 3
0 Not used
0 0 0 Signal in case of error O 4
0 Not used
3 00
0 0 0 Signal in case of error O 5
0 Not used
0 0 0 Signal in case of error O 6
0 Not used
4 00
0 0 0 Signal in case of error O 7
0 Not used
1 0 Error detection O 0 0 = Off
1 0 Error detection O 1 1 = On without test current
5 AA
1 0 Error detection O 2 2 = On
1 0 Error detection O 3
1 0 Error detection O 4
1 0 Error detection O 5
6 AA
1 0 Error detection O 6
1 0 Error detection O 7
0 Output 0 and 1 parallel 0 = Outputs separate
0 Output 2 and 3 parallel 1 = Outputs parallel
7 00 0 Output 4 and 5 parallel
0 Output 6 and 7 parallel
0 0 0 0 Not used
8 .. 13 00 Not used
0 mA 0 0 0%
< 0 mA 0 0 0%
The limits of the measurement range to the short circuit and open circuit area can be modified by the
parameter ´Measurement range limits according NAMUR´ according the above table.
For 9468 AUMH the parameters ´ Measurement range ac. NAMUR ´ are valid for Input Signals only!
The parameters are visible for all switchable AI/AO Signals but are without effect for the AO signals.
This parameter is available with firmware Revision V01-02 of all AIM and AIMH modules
(9460/.. und 9461/..).
Modules with older firmware revisions do not support this parameter. This modules use the fix setting
´Measurement range limits according NAMUR = No´.
Data word structure cyclic analog data AIM 9460/…, AIMH 9461/…, AUMH 9468/.. (No Stat)
without Signal Status
15 – 16 AI7
17 – 20 HV-P1
21 – 24 HV-P2
25 – 28 HV-P3
29 – 32 HV-P4 HART Variables
Float
- transmitted on
33 – 36 HV-P5 32
positions P1 - P8
37 – 40 HV-P6
-
41 – 44 HV-P7
45 – 48 HV-P8
Data word structure cyclic data AUMH 9468/… and UMH 9469/.. with Signal Status
8I 8O 8I/8O 8I 8O 8I/8O
9469: 8I 8O 6I+2O 8I/8O
+4HV +4HV +4HV +8HV +8HV +8HV
Data Byte Operation mode
1 S0 - S7 S0 - S7 S0 - S7
I0 I0 I0 I0 I0 I0 I0
2 0 0 0
3
I1 I1 I1 I1 I1 I1 I1
4
HV-P1 HV-P1
5
I2 I2 I2 I2 I2 I2 I2
6
7
I3 I3 I3 I3 I3 I3 I3
8
HV-P2 HV-P2
9
I4 I4 I4 I4 I4 I4 I4
10
11
I5 I5 I5 I5 I5 I5 I5
12
HV-P3 HV-P3
Input
13 S0-S7
I6 I6 I6 I6 I6 I6
14 0
15
I7 I7 I7 I7 I7 I7
16
HV-P4 HV-P4
17 S0 - S7 S0 - S7 S0 - S7 S0 - S7 S0 - S0 - S7
18 0 0 0 0 S7
0 0
19 - 22 HV-P1 HV-P1 HV-P1 HV-P5 HV-P1
23 - 26 HV-P2 HV-P2 HV-P2 HV-P6 HV-P2
-
27 - 30 HV-P3 HV-P3 HV-P3 HV-P7 HV-P3
31 - 34 HV-P4 HV-P4 HV-P4 HV-P8 HV-P4
- - -
35 - 38 HV-P5 HV-P5
39 - 42 HV-P6 HV-P6
- - -
43 - 46 HV-P7 HV-P7
47 - 50 - HV-P8 HV-P8
1-2 O0 O6 O0 O0 O0 O0 O0
3-4 O1 O7 O1 O1 O1 O1 O1
5-6 O2 O2 O2 O2 O2 O2
Output
7-8 O3 O3 O3 O3 O3 O3
- - -
9-10 O4 O4 O4 O4 O4 O4
-
11-12 O5 O5 O5 O5 O5 O5
13-14 O6 O6 O6 O6 O6 O6
15-16 O7 O7 O7 O7 O7 O7
Readback: In all 8AI/8AO operation modes using channel parameterization as AO the written output value
can be read via the associated AI signal (Readback). Using channel parameterization as AI, written
dedicated AO signals have no effect.
1 OK
HART variables HV Float 32 HART Variables (HV-Px) are transmitted on positions P1 to P8
2 wire and 4 wire Resistance Measurement Pot in Ohm 500 R ...10K (module 9480 /.. , 9482/..)
3 wire and 4 wire Resistance Position Measurement Pot in % 500 R...10K (module 9480/.. , 9482/..)
Value transmitted if
Parameterized behavior if an error occurs Type of error
an error occurs
freeze All IO-Module errors Last valid value
Short circuit *2) + / - 32767 7FFF / 8001
Open circuit *2) + / - 32762 7FFA / 8006
Upper limit exceeded 32761 7FF9
Status code
Lower limit exceeded -32760 8008
General rule to generate status information in AS Cold Junction error -32752 8010
for all AI signals: 2 wire calibration failed -32749 8013
Signal is disturbed if value >= 32512 or value<= -32512 IO-Module does not respond -32736 8020
see 3.4.1 Behavior of input signals in case of error Config. unequal from module -32735 8021
Data not available -32734 8022
IO-Module hardware error -32733 8023
*2) depending of the direction of signal change at the respective error type a positive or negative Status
code is used:
For 2 wire calibration of module TIM R 9480/.. and TIM 9482/.. the user interface (LCD display with buttons)
of the CPM 9440 has to be used.
Automatic 2 wire calibration of derTIM modules by short circuit at the end of the line can be used in
combination with 9442 CPUs. Details see the operating instructions of the TIM modules.
Data word structure cyclic data TIM 9482/.. with Signal Status
Data / Var.
Type Byte Usage
channel Type
1
I0
2
3
I1
4
5
I2
6
7
I3
8
INT 16 Analog input data
Input
9
I4
10
11
I5
12
13
I6
14
15
I7
16
17 S0 - S7 Signal Stati 0-7
INT 16
18 0 0=Signal disturbed, 1=Signal OK
Measuring Units
range % Range
Decimal Hexadecimal
0 – 20 mA
*1) >30137 >75B9
21,8 mA 30137 75B9 109%
. . . Over range
AOM 4 – 20 mA
Measuring Units
range % Range
Decimal Hexadecimal
4 – 20 mA
*1) >30759 >7827
21,8 mA 30759 7827 111,25%
. . . Over range
*1) : The AOM attempts to increase the current further according to the control value. However, depending
on the burden effective resistance, the maximum output voltage of the AOM may be reached whereby
the current can no longer be increased.
Data word structure cyclic analog data AOM 9460/…, AOMH 9461/…, AUMH 9468/.. (No Stat)
On the modules 9470, 9471 and 9472 some of the 16 inputs can optionally be used as digital- (DI), counter-
(C) or frequency input (F).
Through selection of different module descriptions from the GSE-file the transmitted data area as well as the
used identifier format on PROFIBUS DP can be chosen.
Signal definition with Parameter ´Invert all inputs of the module = No´:
Even if DIM 16+CF (with counter / frequency) is selected the inputs 14 und 15 are mapped to the standard
DI data area (byte 2) and therefore can be used as standard DI inputs.
Status allocation:
1 OK
Signals and states are generated and transmitted synchronized and consistent
if parameter ´Error detection´ = On
Data
all DIM DIOM 9470/3x, 9471/35, 9472/35 (IS1+)
(947x/3x in compatible mode)
Data Byte Type
DIM DIM DI/DO DI/DO DI/DO
DIM DIM DI/DO
+Stat +2CF +2CF +6CF +8CF
1 DI signals 0 – 7 *1)
2 DI signals 8 – 15 *1)
UINT16
3 Signal Status 0 – 7
4 Signal Status 8 – 15
5+6 C/F I14 C/F S15 C/F S15 C/F S15
7+8 C/F I15 ! C/F S14 C/F S14 C/F S14
Input
9 + 10 C/F S13 C/F S13
11+12 C/F S12 C/F S12 UINT16
- - - - - -
13+14 C/F S11 C/F S11 (UINT32)
15+16 C/F S10 C/F S10
17+18 C/F S9
-
19+20 C/F S8
1 *2) DO 0 - 7 DO 0 - 7 DO 0 - 7 DO 0 - 7
UINT16
2 DO 8 - 15 DO 8 - 15 DO 8 - 15 DO 8 - 15
*1) In operation mode DI/DO and parameterization as DO written output values can be read back via the
dedicated DI signals.
In operation mode DI/DO and parameterization as DI the dedicated DO signals have no effect.
For summation of 16 Bit counters in the AS the count difference of two consecutive read cycles must be
added from the AS. Counter overflow / underflow must be detected and considered. Maximum one overflow
/ underflow within one AS cycle shall occur.
Max. number
Measurement Scaling Resolution
Module signals Operation mode
method [Hz / Bit] [Hz]
per module
Pulse time
all DIM with Frequency 1 Hz - 1 kHz 0,05 +/- 0,05
measurement
Frequency-
Frequency 20 Hz - 20 kHz Gate time 50 ms 1 +/- 20
measurement 2
(9470/3x in Frequency 5 Hz - 20 kHz Gate time 200 ms 1 +/- 5
comp. Mode)
Frequency 1 Hz - 20 kHz Gate time 1 s 1 +/- 1
Frequency 0,1 - 600 Hz 0,01 +/- 0,01
DIOM
9470/3x, 8 Frequency 1 Hz - 3 kHz 0,05 +/- 0,05
Pulse time
9471/35, Frequency 1 Hz - 20 kHz 0,5 +/- 0,5
measurement
9472/35
(IS1+) Frequency 1 Hz - 20 kHz
4 pairs 0,5 +/- 0,5
with direction
Signal scaling:
0 Hz 0 kHz 0 0 0%
all DIM with Frequency (9470/3x in comp. mode) Phys. 0 – 100% correlate digital 0 – 20000
DIOM 9470/3x (IS1+) Phys. 0 – 100% correlate digital 0 – 40000
Signal Filter:
The measured frequency signal can be filtered by the DIOM 9470/3x to reduce jitter.
Additionally a pulse extension function is executed for the DI signals.
Pulse extension:
This function can be used to increase the length of short pulses. With this e.g. a short activity of a manual
sensor (term approx. 10 .. 50 ms) can be extended to a time selectable by parameterization (T = 0,6 sec.,
1.2 sec., 2.4 sec.).
Short pulses can be recognized surely from the AS also with slower cycle times of the application software
Signal to AS
T
Pulses which are longer than the parameterized time T, are not extended.
Short pulses during time T are suppressed.
Input signal
Signal to AS
T
Input signal
Signal to AS
T
Signal LEDs:
DIOM with signal LEDs display the extended ´Signal to AS.
Signal allocation
DOM 8 + DOM 4 +
DOM 8 DOM 6 DOM 4
Data Byte Bit Status Status
9475/3x 9475/3x 9477/12-06-12
0 Status_S0 Status_S0 -
1 Status_S1 Status_S1 -
2 Status_S2 Status_S2 -
3 Status_S3 Status_S3 -
1
Input 4 Status_S4 - -
5 Status_S5 - -
6 Status_S6 - -
7 Status_S7 - -
2 0–7 0 0 -
0 DO 0 DO 0 DO 0 DO 0 DO 0
1 DO 1 DO 1 DO 1 DO 1 DO 1
2 DO 2 DO 2 DO 2 DO 2 DO 2
3 DO 3 DO 3 DO 3 DO 3 DO 3
Output 1
4 DO 4 - DO 4 DO 4 -
5 DO 5 - DO 5 DO 5 -
6 DO 6 - DO 6 - -
7 DO 7 - DO 7 - -
1 OK
If no valid signal value can be formed as a result of a malfunction (short circuit, open circuit, defective
subassembly...), a diagnosis information is created and transmitted to the master. Despite the outstanding
malfunction, cyclic data including signal status information continues to be transmitted to the master.
The behavior of the signal values transmitted if a malfunction has occurred can be selected separately for
every module using parameterization (see IO-Module parameters ).
Application hint:
If the behavior of input signals in case of error is realized through the IS1+ system, this behavior seen from
the application software in the automation system can only be guaranteed with undisturbed communication
on PROFIBUS DP.
At loss of cyclic communication on PROFIBUS DP additional project specific reactions have to be realized in
the application software in the automation system.
To guarantee the same behavior of all input signals in any case of error (even in case of bus failure), we
recommend the following procedure:
Generate a Status Bit for each input signal in the automaton system:
- For DI signals and for all signals of IS1+ IO-Modules (FW 03-xx) ) the signal status bits available
optionally from IS1 are used in the input data area.
- For AI signals of the IS1 IO-Modules (FW 02-xx) the behavior in case of error = ´Status code´ has to be
chosen in the parameters of all AI signals (default). In the application software of the automation system
the following function has to be used for each AI signal:
The signal behavior in case of error (freeze, substitute value ...) should now be realized in the automation
system
In this case the event ´loss of cyclic communication on PROFIBUS´ can be logical wired with the signal
status bit whereby the ´signal behavior in case of error´ is always the same under all error conditions.
The additional information’s of the diagnosis telegram can be used optionally to generate message lists for
maintenance purposes.
Consequently, the safety position of the output modules follows at a delay of T S after failure of the
communication to the master where:
TS = TWD + TMod
The safety position of the output signals can be parameterized separately for every module (see 3.2.2 IO-
Module parameters).
PROFIBUS Failsafe Mode Support: Behavior of different IS1 CPUs in the PROFIBUS DP clear mode.
Using the 9442 CPU with GSE V2.xx or V3.XX all output signals are set to the value ´ 0 ´ in the DP
clear mode regardless of the parameterized safe positions in the IS1 parameters.
Using the 9440 CPM or 9442 CPU with GSE V4.xx or V5.xx, the projected security positions of the
output signals are processed correctly as parameterized in the IS1 parameters.
Supply of HART devices using Analog Universal Module AUMH 9468/3x and UMH 9469
Each channel of an AUMH can be parameterized as analog input for HART sensors or as analog output for
HART actuators. The supply of HART sensors and HART actuators is different and will be switched too.
For communication with a HART sensor the channel shall be parameterized as ´Input´.
For communication with a HART actuator the channel shall be parameterized as ´Output´.
In a non-parameterized state the channels of an AUMH are in the position ´Output´ and HART
communication is possible with HART actuators only.
Data format
HART variables are transmitted as IEEE floating-point numbers (4 byte).
If a HART variable cannot be read (e.g. HART device undergoing startup, not connected, defective or HART
variable not found, ... ), value 7F A0 00 00 (Not a Number) is transmitted. This may be evaluated in the AS for
generation of a signal status of the HART variables. Detailed status and diagnostic information of the HART
field devices can be evaluated via HART Management Systems.
Up to 8 HART field devices can be connected to one HART module of IS1. Since each HART field device may
have up to 4 variables, this mean that a maximum of 32 HART variables are possible per module.
The assignment of 4 or 8 out of these 32 variables to the positions P1 to P8 in the cyclic transmission area of
PROFIBUS DP or to MODBUS Registers can be selected by parameter assignment:
Value
Parameter name Function
range
Selection of the channel No. (input / output No.) of the HART module to which
Input No. HART device for pos. 1 the HART field device is connected which is to be transmitted at pos. 1.
If ´Not Used´ is selected, value ´Not a Number´ (7F A0 00 00) is transmitted.
Input No. HART device for pos. 2 0 ... 7, Selection for pos. 2
Not used
.....
Input No. HART device for pos. 4 (8) Selection for pos. 4 (8)
The occurrence of diagnosis changes is registered to the class 1 master by the IS1+ field station in the cyclic
data exchange. The class 1 master then demands the diagnosis data from the IS1+ field station in an acyclic
telegram.
In addition to the 6 bytes of standard information complying with the DP standard, the IS1+ field station can
supply identifier-related diagnosis data, CPU-, module- redundancy and IO-Module status and channel-related
diagnosis data.
Diagnosis data can be displayed in a diagnosis user interface of the master configuration software and can be
evaluated via the user program in the automation system.
If there are no alarms in a field station, then only the 6 bytes of standard information (byte 0 to byte 5) are
transmitted in DPV0. Only if one or more alarms are present, the additional information (starting from byte 6)
is transmitted. This has to be considered at the evaluation of diagnosis data in the AS.
Byte 4 manufacturer id
Byte 5 0x049A for IS1
Byte 6
.
up to . Device related diagnosis IS1+ Fieldstation (DPV0)
. 20 bytes
Byte 25
Byte 26
.
. Identifier related diagnosis of the IS1+ modules
. 6 bytes
Byte 31
Byte 32
Channel-related diagnosis
Byte 34 of 3 bytes per garbled signal.
Variable length up to the maximum
Byte 35 size of the diagnosis telegram
of the IS1+ field station
Byte 37
Byte 6
. Identifier related diagnosis of the IS1+ modules
. 4 bytes
Byte 9
Data is
transmitted in
Byte 10 every diagnosis
. telegram if
. CPU Status (DPV1) config- and
. 8 bytes parameter data
Byte 17 are available in
IS1.
Byte 18
.
. Module Status (DPV1)
. 8 Byte
Byte 25
Byte 26
If parameter
.
´CPU Redundant
. Redundancy Status (DPV1)
= Yes´, only
. 8 Byte
Byte 33 (only used with PNO slave Redundancy)
Byte 34
or 26 *1) .
. IO-Module Status (DPV1) Data is
. 6 Byte per disturbed IO-Module transmitted in
slot order if
disturbed
modules or
signals are
Channel-related diagnosis
present, only.
of 3 bytes per disturbed signal.
.
Variable length
up to the
. maximum length
. DPV1 Alarm of the diagnosis
. 8 Byte per Alarm telegram of the
IS1+ fieldstation.
The first 6 bytes of a diagnosis telegram contain the following information in compliance with the PROFIBUS
standard:
3 1 = Diagnosis data of the IS1 - The diagnosis data can be read out.
station are present. (global alarm bit of complete field station)
4 1 = Telegram type not supported - Slave cannot answer a telegram type used by the
master.
5 1 = DP Master cannot interpret the - Check the bus physics
response of the slave.
6 1 = “Set parameters” telegram is rejected - Check the parameterization of the slave in the master
by slave.
7 1 = DP slave was parameterized by - Another master accesses the IS1+ station (see 1.3
another DP master Access procedure)
Master PROFIBUS address (Byte 3): PROFIBUS address of the master that parameterized the DP slave
and has read and write access to the DP slave.
Manufacturer ID (Byte 4, 5): The manufacturer ID is stored in the DP slave as well as in the
related GSE file.
( 0x049A for IS1)
*3) From FW 0x-43: Behavior of Identifier related diagnosis bits in case of undisturbed signals and without
other module diagnoses ( e.g. ´ IO-Module xx hardware disable outputs will set Identifier related diagnosis =
1)
IO-Module Status
Bit Message Measure / Remedy
(NE107)
The temperature around the IO-Module is too
high. Out of
0, 4 Overtemperature
Reduce ambient temperature or increase Spec.
ventilation, shadowing …
The module has detected a incorrect change of
the slot address during operation.
1, 5 Slot address error
-> exchange IO-Module and send it back to Maintenance
STAHL. Required
Exchange of module recommended due to
2, 6 Module maintenance request
operating conditions.
IO-Module Note - -
Maximum total output current of
9475/3x-04-72 module exceeded. Out of
DOM4 Channel 3 is switched off. Spec.
Reduce total loop current.
wrong external wiring.
3, 7 Check module note 9471/35-16-xx
Check external signal wiring or Failure
DIOM Z2 Ex n signal type configuration
wrong external supply (18 .. 32V) or
9472/35-16-xx wrong external wiring.
DIOM 24V Z2 Check external supply (18..32V) or Failure
Ex n external signal wiring or signal type
configuration
*1) 9442 CPU with GSE Files from V2.34, V3.12, V4.13 or V5.13 only.
*1) Byte 16 was used als ´Diag Update Counter´ which was fixed to zero from 9440 CPM Rev. 0x-49.
Byte was allocated for the 9442 CPU with new features.
00 Module OK - No Error
0 = All signals of IO-
Module undisturbed Maintenance
Module- and signal Required
common error See details in IO-Module
01 1 = one or more
(e. g. Line break, Short circuit, Rail
Status and signal diagnosis
error, Overtemperature ... ) signals of IO-Module Failure
are disturbed
Plug configured module
Wrong module
10 type or change Failure
Type 1 = all signals
configuration of DP master.
of IO-Module
No module are disturbed Plug correct module type
11 Failure
(No or wrong response) or exchange module.
Attention! The Redundancy Status is only transmitted with activated PNO Slave Redundancy
(supported by 9440 CPM firmware from revision V03-42).
PROFIsafe status
Value
Byte Diagnosis Text Diagnosis Help Text
Hex Dec
0x40 64 F_Dest_Add mismatch Mismatch of safety destination address
0x41 65 F_Dest_Add not valid Safety destination address not valid
0x42 66 F_Source_Add not valid Safety source address not valid
0x43 67 F_WD_Time not defined Safety watchdog time value is 0 ms
n+5
0x44 68 F_SIL parameter error Parameter „F_SIL“ exceeds SIL from specific device application
0x45 69 F_CRC_Length error Parameter „F_CRC_Length“ does not match the generated values
0x46 70 F-Param. version error Version of F-Parameter set incorrect
0x47 71 CRC1-Fault CRC1-check of received F-data failed
Channel-related diagnosis
Optionally, additional channel-related diagnosis information in the diagnosis telegram to the master can also
be transmitted. The generation of the channel-related diagnosis can be released in the "USER_PRM_DATA"
area. For each outstanding alarm of the input signals, 3 bytes are transmitted.
0 Reserved - - - -
Attention!
If not all of the IO-Module status and channel-related diagnosis data can be transmitted due to a
diagnosis buffer overflow, this is displayed in the standardised diagnosis area by the message,
“Diagnosis overflow”.
1 byte input data (status register) and 1 byte output data (control register) are transmitted for the CPU in the
cyclic range of PROFIBUS DP.
The contents of the status register can be used in the AS for generation of a field station-global group alarm.
In the case of applications without Stahl CPU redundancy, the function on the control register is deactivated
by parameter ´CPU redundant = No´ (default setting).
Using GSE V2.xx and V3.XX this data is included in the CPM Module descriptor.
Using GSE V4.xx or V5.xx with the 9442 CPU the optional module descriptor ´CPU status / control registers´
can be projected on any slot optionally if necessary. The slot address of the following IO-Modules are moved
in this case.
Maximum of 15 IO-Modules + status / control registers are configurable, as far as no cyclical data length
limits are violated.
Hint: If the status / control registers is projected as the last module the after the real plugged IO-Module, the
slot addresses of the real plugged IO-Modules remain unchanged.
7 0 Bit no.
0 0 0 0 0 0 x x
Status CPU:
Value Message / Function Measure / Remedy
Value 1 (001) *1) Hardware fault CPU Exchange CPU
Data exchange with AS with diag. data! Use diagnostic tool of AS or IS1
Value 2 (010)
--> Generate group alarm FS DTM to check for details.
Startup data exchange from DP
Value 3 (011) *1) No data exchange (after Power On)
master
Check configuration and parameter
Value 4 (100) *1) Configuration or parameter error
data in DP master
Check bus connection to AS.
Value 5 (101) *1) Quit data exchange with AS Startup data exchange from DP
master
Data exchange with AS without diag. data
Value 6 (110) No errors
--> all IO-Modules and CPUs are error free
Check:
- Bus connection of red. CPU
Value 7 (111) *1) Backup CPU not accessible - Power of red. CPU
- Function of red. CPU
- Rail connection between red. CPUs
*1) Important:
Value can be evaluated practically only in the case of CPU redundancy.
In the case of operation without CPU redundancy, the status register can no longer be updated in the event
of bus or slave failure in the AS. Group alarm ´Diagnostic data available´ can thus be practically evaluated
only in the case of cyclic bus operation. Status ´Slave failure´ must be scanned separately in the AS and
cannot be detected by evaluation of the status register.
The status register contains information about both CPUs. During regular operation, this status information is
cross-coupled between both CPUs and can thus be read by both CPUs. However, in case of malfunction, the
status information in the backup CPU may be lost. Therefore, the AS always analyses just the status register
of the primary (active) CPU.
For details, see the IS1 operating instructions CPM 9440 and operating instructions IS1 CPM display.
write_ind read_ind
Slot Telegram transaction Description
[DS Index] [DS Index]
255 -> 65000 255 write_ind -> read_ind I&M0 Function
… … … I&M1 … I&M3
Supported by 9442 CPU only
255 -> 65004 255 write_ind -> read_ind I&M4 Function
- 7 read_ind HART Livelist
0
8 8 write_ind -> read_ind Servicebus protocol tunneling via DPV1
(CPU) Readback of adjusted ´F-Destination address´ of all
- 9 read_ind
PROFIsafe I/O modules
- 129 read_ind HART Parameter
- 148 read_ind HART DS Information
- 149 read_ind HART Feature Flags
255 -> 65000 255 write_ind -> read_ind I&M0 Function
… … … I&M1 … I&M3
Supported by 9442 CPU only
255 -> 65004 255 write_ind -> read_ind I&M4 Function
- 129 read_ind HART Parameter
- 148 read_ind HART DS Information
- 149 read_ind HART Feature Flags
1-16 80 81 HART transaction channel 0
(IOM) 82 83 HART transaction channel 1
84 85 HART transaction channel 2
86 87 write_ind -> read_ind HART transaction channel 3
88 89 with delayed response HART transaction channel 4
90 91 HART transaction channel 5
92 93 HART transaction channel 6
94 95 HART transaction channel 7
Even when using multiple parallel C2 channels only one HART telegram processing is supported at a time.
IS1+ supports the I&M (Identification and maintenance) function according PNO
specification and delivers the following I&M data on Index 255:
*1) HARDWARE_REVISION:
STAHL is using the letters ´A´ to ´X´ which are represented as characters (example: ´A´ = 0x0041).
*2) SOFTWARE_REVISION:
example of allocation:
Stahl software revision: V 02-31
Data Type Char Uint8 Uint8 Uint8
Data ´V´ = 0x56 0x02 0x1F 0x00
displayed ´V´ 02 31 0
TAG_FUNCTION 32 Octets Visible String User specific data which is stored in the device.
TAG_LOCATION 22 Octets Visible String Default: filled with ´0x20´ (blank)
The IS1+ field station is supporting the standard start-up behavior with a class 1 master (see 2.11 start-up
behavior). Additionally the following features are supported:
Parameter change.
If an IS1+ field station is in data exchange with a DP master, the telegram ´Set_Prm´ (send parameter) can be
transmitted from the master to the field station between the cyclic data telegrams.
The field station checks the length of the telegram ´Set_Prm´ and accepts the new parameter data without
leaving data exchange if the length of the telegram is OK.
With this, online changes of parameter data of the IS1+ field station from a PROFIBUS DP (Class1 V0) master
are possible.
If the length of the ´Set_Prm´ telegram is not OK the new parameter data are not accepted. The field station
changes to the mode ´wait parameter´ whereby a new start-up of the cyclic communication is forced.
Configuration change.
If a IS1+ field station is in data exchange with a DP master, the telegram ´Chk _Cfg´ is only accepted from the
field station if the configuration data of the field station has not changed.
If a telegram ´Chk _Cfg´ with changed configuration data is received during data exchange, the field station is
leaving the data exchange and goes to the mode ´wait parameter´ whereby a new start-up of the cyclic
communication is forced.
If a master wants to change the configuration data of the field station or wants to interrupt the data exchange
for a defined time, the data exchange should be stopped from the master by sending the telegram ´Set_Prm´
with ´Unlock_Req = TRUE´ (Lock). This will bring the field station to the mode ´wait parameter´.
After this the master can do a new start-up with new configuration and parameter data.
With the parameter ´ timeout for output modules´ or via response monitoring (see chapter 3.4.2) the output
signals of the field station can be freezed during an interruption of the data exchange for a parametrizable
time.
If the master is coming back to data exchange with the field station before exceeding of this watchdog times,
the output signals are not going to the selected save position and are now updated cyclic from the master
again.
If the master has changed configuration data, which has influence to the signal marshaling in the data
telegrams, he is responsible for the correct new marshaling inside of the master and the PLC / DCS.
During the new start-up the field station is checking the new configuration and parameter data individually for
each slot (each I/O-module).
All modules of the field station where the configured module type agree with the existing module type in the
field station are updated cyclically after start-up.
For modules, which do not agree with the configuration data, alarms are generated. The signals of this modules
are not updated and react according the parameterized behavior in case of error.
A change of IP addresses is blocked during active data exchange to the Automation System.
Caution! IP-AS and IP-SB addresses of a CPU must be unique as all IP addresses of an Ethernet network.
The IP address information is stored in the socket backup memory as well. Configuration and address
information of an IS1+ field station are therefore preserved in case of exchange of CPUs.
IP-SB addresses of found IS1+ 9442 CPUs can be changed if necessary and must be inside of the IP-
addressable address range of the network.
Thus the IS1+ CPUs are accessible via the integrated Web server. Diagnostic information can be displayed
here and further adjustments can be made.
User LogIn/Out
The user password by default is set to: R.STAHL
The user shall to change it after a successful user login.
IP-SB Address
The IP-AS address for the IP-SB Address can be adjusted via the Web server of 9442 CPU optionally.
The IP-AS address is not used with PROFIBUS.
The IP-AS, IP-SB addresses and the Device Name of both CPUs (left - and right CPU) of a redundant pair
are displayed in the IS1 Webserver while the Web server is connected with one of the two CPUs
(connected).
The IP-SB as well as IP-AS address can only be changed in the CPU, with which the Web server is currently
connected. A valid user login is required for change.
A manual change is only possible with a valid user login and without DataExchange with an MODBUS TCP
client. DHCP must be disabled. An existing connection to the Web server is closed after a change of IP SB
address and must be reopened to the modified IP SB address.
Driver for PCS7 V8. 0 SP2 based IS1 GSE V3 05 supports CPM 9440 redundancy.
Support for 9442 with CPU redundancy in preparation.
6 List of abbreviations:
AS Automation System
AIM Analogue Input module
AIMH Analogue Input module + HART
AUMH Analog Universal Module AI/AO with HART
SAIMH Safety Analogue Input module + HART (PROFIsafe)
AOM Analogue Output module
AOMH Analogue output module +HART
CPU + PM = CPM Central unit 9440 consisting of communication processor with
CPM
power pack
DIM Digital Input Module
DIOM Digital Input Output Module
DOM Digital Output Module
DOMR Digital Output Module Relays
DOMV Digital Output Module Valves
HW Hardware
IOP I/O Processor of the central unit
IOM General description of I/O Module
PM Power Module (power pack)
SW Software
SIL Safety Integrity Level
TIM Temperature Input Module
7 Release Notes:
Revision Revision
Extensions / Changes
This document GSE file
8 Support address
R. STAHL Schaltgeraete GmbH
Business Unit Automation Interface and Solutions
eMail: [email protected]
Support information: http://www.r-stahl.com
Service hotline IS1: +49 (7942) 943-4123
Telefax : +49 (7942) 943-40 4123
The CPM firmware mentioned here will run on 9440/15, 9440/12 hardware rev.F (released end 2001) and
later and 9440/22 all hardware rev. If older CPM firmware than x-33 is used or the I/O module firmware is
1-xx (version 2-xx was released June 2003) contact: [email protected] for upgrade options.
In general the latest CPM firmware and the latest GSD version should be used (latest mean: V1.xx, V2.xx,
V3.xx => were xx has the highest available count)
Remote I/O Technologie