GEZE IO 420 User manual

IO 420
164898-03
EN User manual

GEZE IO 420
2
Contents
1 About this document.............................................................................................................................................3
1.1 Product description.........................................................................................................................................................................................3
1.2 Further documents..........................................................................................................................................................................................3
1.3 Symbols and illustrations ..............................................................................................................................................................................3
2 Safety and responsibility.......................................................................................................................................3
2.1 Fundamental safety precautions ...............................................................................................................................................................3
2.2 Assigning sta ...................................................................................................................................................................................................4
2.3 Product liability.................................................................................................................................................................................................4
2.4 Guidelines............................................................................................................................................................................................................4
3 Product overview/installation details...............................................................................................................4
3.1 Technical data....................................................................................................................................................................................................4
3.2 LEDs, connections and conguration of the IO 420............................................................................................................................4
3.3 BACnet for GEZE IO 420..................................................................................................................................................................................6
4 Parameter setting GEZE IO 420...........................................................................................................................8
5 Module description...............................................................................................................................................11
5.1 Module type “watchdog” ............................................................................................................................................................................11
5.2 Module type “1 door” ...................................................................................................................................................................................12
5.3 Module type “2 doors” .................................................................................................................................................................................13
5.4 Module type “4 doors”..................................................................................................................................................................................14
5.5 Module type “automatic stat” / “automatic 4 sec”.............................................................................................................................15
5.6 Module type “window” ............................................................................................................................................................................... 16
5.7 Module type “universal” ............................................................................................................................................................................. 16
5.8 Module type “IQ lock El + Aut”..................................................................................................................................................................17
5.9 Module type “RWS + KL” ..............................................................................................................................................................................19
5.10 Module type “DCU1, 2 and 8”.................................................................................................................................................................... 21
5.11 Module type “DCU6” (revolving door)................................................................................................................................................... 21
5.12 Module type “DCU128+RWS+KL” .......................................................................................................................................................... 21
6 Annex ....................................................................................................................................................................... 22
6.1 EDE lists ............................................................................................................................................................................................................. 22
6.2 State text........................................................................................................................................................................................................... 26
6.3 Service menu................................................................................................................................................................................................... 29
6.4 Passwords for BACnet .................................................................................................................................................................................. 33
7 Firmware update for IO 420 .............................................................................................................................. 33

GEZE IO 420
3
1 About this document
This user manual describes the installation, commissioning and parameter setting of the GEZE IO 420.
Installation and commissioning of the windows and doors are not part of this user manual.
1.1 Product description
With GEZE IO 420, GEZE components for door and window systems as well as the RWS-system of GEZE are
controlled. The IO 420 is a coupler module for the networking of components and for the integration of non-bus-
compliant components in the GEZE system. This user manual describes the individual module types th at can be
implemented using this system .
1.2 Further documents
The components supplied by GEZE include the relevant data sheets with technical data. These must be heeded.
All data sheets and further documents can also be found on the internet at www.geze.com.
1.3 Symbols and illustrations
Warning notices
Warning notices are used in these instructions to warn you of property damage and personal injury.
XAlways read and observe these warning notices.
XFollow all measures that are labelled with the warning symbol and warning word.
Warning symbol Warning word Meaning
– CAUTION Information to prevent property damage, to understand or optimise the
operation sequences.
More symbols and illustrations
In order to illustrate proper operation, important information and technical information is highlighted.
Symbol Meaning
means “important information”
means “additional Information”
XSymbol for an action: Here you have to do something.
If there are several actions to be taken, keep to the given order.
Abbreviations
ANSI American National Standard Institute
APDU application layer protocol data unit
B/IP BACnet/IP broadcasting management device
BACnet Building Automation and Control networks
BBMD BACnet/IP broadcasting management device
BIBBs BACnet Interoperability Building Blocks
BMA Fire alarm system
COV change of value
CP Capacitor plate (capacitor power)
DCC Device communication control
EDE Engineering Data Exchange
IQ Lock Aut Motor lock for the passive leaf
IQ Lock EL Motor lock
KL 220 Terminal box 220
KZF Short-term release
MAC medium access control
MS/TP Master Slave Token Passing
NC Opening contact (normally closed)
NO Closing contact (normal open)
PICS
Protocol Implementation Conformance Statement
RWA Smoke and heat extraction
SCT Key operated button
ST 220 Service terminal
TZ 320 Door control unit 320
TE 200 Control panel 200
VAT 220 Virtual display indicator board
ZSU Timer
AL Active leaf
IL Passive leaf
BMA Fire alarm system.
RWS Escape route system.
2 Safety and responsibility
2.1 Fundamental safety precautions
XUse only original GEZE parts for repair work.
XUnauthorised changes to the system exclude GEZE's liability for any resulting damage.
XPrimary protective measures are to be carried out on site.
XFollow the VDE 0100 and VDE 0815 standards when laying the cables.

GEZE IO 420
4
2.2 Assigning sta
Installation, commissioning and repair work must be performed by properly trained personnel authorised by GEZE.
2.3 Product liability
In compliance with the manufacturer’s product liability as dened in the German "Product Liability Act", the inst-
ructions included here must be noted and followed. Failure to comply releases the manufacturer from his statuto-
ry liability. Only experts authorised by GEZE may carry out installation, functional checks and maintenance work.
2.4 Guidelines
The GEZE IO 420 fulls the following standards:
àDIN EN 61000-6-2: 2005 (in accordance with VDE 0839 Part 6-2 / March 2006)
àDIN EN 61000-6-6: 2007+ A1:2011 in accordance with VDE 0839 Part 6-3 / September 2011
3 Product overview/installation details
3.1 Technical data
Device name:IO 420
H
T
B
Function: Universal IO modules
Installation: Fitting to top hat rail
Main dimensions [mm] (W x H x D): 107 x 111 x 59
Operating voltage: 24 V DC +/-15 % with reverse polarity protection
Induced current intake: max. 300 mA at 24 V
Total power consumption: 2 A at 24 V
Output current (pin 1 and 2): max. 1 A at 24 V
Contact rating for relay: 1 A at 30 V
Operating temperature [°C]: -20 to 80°C
Safetey use: F900: Value 2.5 A
3.2 LEDs, connections and conguration of the IO 420
Fig. 1: LEDs and connections GEZE IO 420

GEZE IO 420
5
3.2.1 LEDs
LED 1 - (red) LED ashes if the microSD card is read or written.
LED 2 - (yellow) LED lights up if “CP” (capacitor plate) is connected.
LED 3 - (red) LED ashes in case of a fault.
LED 4 - (green) LED ashes during normal operation.
LED 5 - (green) LED lights up if voltage supply for microcontroller is active.
LED 6 - (yellow) LED ashes if data is exchanged via BACnet.
LED in - (green) LED-in 4/3/2/1 lights up if input “in” 4/3/2/1 is active.
LED out - (red) LED-out 4/3/2/1 lights up if output “out” 4/3/2/1 is active.
3.2.2 Interfaces / GEZE IO 420
Interfaces àCAN: 50 kBit/s, used for TE 200, VAT 220, TZ 320.
àST 220: used for ST 220, IQ-Aut passive leaf.
àGEZE-Bus: used for IQ-Aut active leaf.
àBACnet: used for BACnet MS/TP interface.
3.2.3 DIP switch conguration
CAN: Terminating resistor “CAN” 120 Ohm
XSet the DIP switch at the start and end of the CAN-BUS to ON
.
BACnet: Terminating resistor “BACnet” 120 Ohm
XSet the BACnet DIP switch on the rst and last IO 420 of the BACnet MS/TP bus to ON
.
GEZE-Bus: DIP switch terminating resistor “GEZE-Bus” 120 Ohm
XWhen GEZE motor lock or TZ 320 (connection for KL 220) is connected, set DIP switch to ON.
Network bias: DIP switch “Network bias”
XSet the DIP switch to ON to enable the network bias for BACnet MS/TP.
Only one bias may be enabled in a BACnet MS/TP network system.
3.2.4 microSD
microSD card The microSD card (SDHC) is written and read in the FAT16/32 le format. Other formats are not sup-
ported. The IO 420 les can be copied to a microSD card. The ST 220 is required for this. The data can
be adapted further at the PC if necessary (parameter setting or changing of BACnet names).
A microSD card can then be used to load the prole to another IO 420 with the same rmware.
The following les are created on the card:
àName le for BACnet names: “IO420_V1.BAC”;
àConguration le: “IO420_V1.CON”; contains all parameters for the IO 420.
àLog le: “IO420_00.LOG” to “IO420_39.LOG”;
Depending on the setting, alarm messages and actions are written into the log le.
If the LED for microSD card is ashing, the microSD card must not be taken out of the slot. The IO 420 must be de-
energised for the microSD card to be removed and inserted.
3.2.5 Reset
Reset push
button
The factory settings can be restored using the reset push button.
Carrying out a reset
XDe-energise the device.
XKeep the reset button pressed on the printed circuit board.
XSwitch the voltage supply on.
The device is restored to the factory settings after 6 seconds.
LED 3 “fault” and LED 4 “normal mode” ash simultaneously in 0.4 second cycle.
XRelease the reset button when the LEDs start to ash.
XTo return the device to operating mode, switch the voltage supply o and on again.

GEZE IO 420
6
3.3 BACnet for GEZE IO 420
Networked MS/TP devices
When MS/TP devices are networked, the line topology must always be observed. To avoid branch lines, each IO
420 has two BACnet connections.
Fig. 2: Wiring of BACnet MS/TP and setting of terminating resistor and network bias.
A BACnet MS/TP network requires one active network-bias. The “BACnet” terminating resistor built inside the
device must be switched on at the beginning and end of the bus using the respective DIP switch.
Maximum 32 MS/TP devices can be connected in one segment.
The wiring must meet or exceed the BACnet and MS/TP EIA-485 network standard and be specied as follows:
àShielded cable, pair-wise twisted.
àImpedance 100-130 Ohm.
àCapacity between the wires < 100 pF/m (30 pF/ft).
àCapacity between the wire and the shield < 200 pF/m (60 pF/ft).
àThe maximum length of any individual segment is 900 m (AWG18 cable; wire cross-section 0.82 mm²).
With large cable lengths, an amplier may have to be integrated in the bus to guarantee function.
Standard setting of the interface:
àBaud rate: 76.8 kB
àData bit: 8
àStop bit: 1
àParity: none
The following BACnet object types are used for the GEZE IO 420:
àDevice object (one object)
àBinary input (up to four objects)
àMulti state value (up to ten objects)
àNotication class object (one object)
3.3.1 Object structure of BACnet for GEZE IO 420
The IO 420 oers 12 module types, each of which can be used with up to 22 objects. The BACnet objects are adapted
to the selected module type. The respective EDE lists can be found in the annex to this document.
Index Object Instance number Explanation
1device object 1 contains the device description.
2 multistate value 1 shows the current module type.
3 multistate value 2 shows the current alarm message.
Termination 120 Ohm Router Termination 120 Ohm
Only one bias may be enabled
in a BACnet MS/TP network system.
Only one bias may be enabled in a BACnet
MS/TP network system.

GEZE IO 420
7
4 binary input 1 assigned dierently depending on the module type
5 binary input 2
6 multistate value 3 status message
7 multistate value 4 command
8 notication class object 1 object for alarm message
9 multistate value 5 status message
10 multistate value 6 command
11 binary input 3 assigned dierently depending on the module type
12 binary input 4
13 multistate value 7 status message
14 multistate value 8 command
15 multistate value 9 status message
16 multistate value 10 command
17 multistate value 11 alarm 1 for DCU
18 multistate value 12 alarm 1 for DCU
19 multistate value 13 alarm 1 for DCU
20 multistate value 14 command
21 multistate value 15 command
22 multistate value 16 command
3.3.2 Changing the object description
The object description is changed through the BACnet connection. Any BACnet congurator can be used for this.
3.3.3 Changing the BACnet parameters
The IO 420 has four BACnet parameters which can be set using the GEZE service terminal ST 220 or by editing the
conguration le at the PC using the microSD card.
àDevice ID: must be unambiguous in the BACnet network. It may not be allocated twice.
àMAC address: must be unambiguous in an MS/TP network.
àBaud rate: 76.8 kB (standard setting).
àInstance number of “notication class object”: The IO 420 only has one “notication class object” since there
is only one object for alarm messages. In the factory setting, multi state value #2 is allocated to this, but it can
be changed by the user. The value range is between 1 and 90.
3.3.4 Changing the object name
This change is carried out by editing the name le “IO420_V1.BAC” at the PC (microSD card).
If the LED for microSD card is ashing, the microSD card must not be taken out of the slot. The IO 420
must be de-energised for the microSD card to be removed and inserted.
XAfter the name le has been edited and entered, the following function must be carried out in the service
menu for the changes to be applied: “Parameter SD-Card” --> “BAC-Name SD -> IO420”.
Title Name of BACnet object
0.Device object =BAC-PR47-232;
1.binary input 1 =GEZE047AE1E2EL32B125000801;
2.binary input 2 =GEZE047AE1E2EL32B225000801;
3.binary input 3 =not_used;
4.binary input 4 =not_used;
5.Multistate value 1 =module_type;
6.Multistate value 2 =GEZE047AE1E2EL32A106000801;
7.Multistate value 3 =TZ320_state;
8.Multistate value 4 =TZ320_command;
9.Multistate value 5 =alarm_details;
10.Multistate value 6 =not_used;
11.Multistate value 7 =not_used;
12.Multistate value 8 =not_used;
13.Multistate value 9 =not_used;
14.Multistate value 10 =not_used;
15.Multistate value 11 =not_used;
16.Multistate value 12 =not_used;
17.Multistate value 13 =not_used;

GEZE IO 420
8
18.Multistate value 14 =not_used;
19.Multistate value 15 =not_used;
21.Notication class =xxxyyy;
END OF FILE----------------------------------------------
The title part including the “=” sign must not be changed. The “=” has the function of separating the title and
BACnet name. The name of the individual BACnet objects may be changed. Care must be taken that the line ends
with a semicolon “;” and the name does not contain more than 32 characters. Special characters may not be used,
with the exception of space, underscore, hyphen, full stop and comma.
4 Parameter setting GEZE IO 420
The rst time parameters are set for the IO 420, the GEZE service terminal ST 220 should always be used. Once
entered, the conguration le “IO420_V1.CON” can be copied to a microSD card and adapted further at the PC if
necessary. A microSD card can then be used to load this prole to another IO 420 with the same rmware.
If the LED for microSD card is ashing, the microSD card must not be taken out of the slot.
The IO 420 must be de-energised for the microSD card to be removed and inserted.
The following points must be remembered when the conguration le is modied at the PC:
àThe parameter name including the “=” sign must not be changed. The “=” has the function of separating the
title part and the value.
àThe parameter value may only contain numbers.
àHeed the min./max. values given in brackets.
Parameter name Value Description
0.CAN_ADDR1(0~63) = 1; CAN address for door #1
1.CAN_ADDR2(0~63) = 0; CAN address for door #2
2.CAN_ADDR3(0~63) = 0; CAN address for door #3
3.CAN_ADDR4(0~63) = 0; CAN address for door #4
4.BACNET_MACADR(0~127) = 1; BACnet MAC address
5.BACNET_DEVICEID(1~4194303) = 1; BACnet DEVICE-ID
6.BACNET_BAUDRATE(0~6) = 5; 0 = Not active
1= 9.6 kB
2= 19.2 kB
3= 38.4 kB
4= 57.6 kB
5= 76.8 kB
6= 115.2 kB
7.BACNET_NOTIFYCLASS(1~90) = 50; Instance number of the notication class object.
8.VALUE_UTC_OFFSET(0~780) = 60; UTC time oset in minutes; amount shown without sign (e.g. EN = 60 min.)
9.SIGN_UTC_OFFSET(1:-/0:+) = 1; Sign for UTC oset.
1 : Negative oset
0: Positive oset
Oset = [UTC] - [local time], which is why Germany has a negative value.
10.CONF_OUTPUT3(0~4)
11.CONF_OUTPUT4(0~4)
=
=
0;
0;
Conguration of output 3 and 4 for door solution
0: Output inactive
1: Alarm
2: Locked
3: Closed
4: Locked and closed.
12.INPUT1_TYPE(0~10)
13.INPUT2_TYPE(0~10)
14.INPUT3_TYPE(0~12)
15.INPUT4_TYPE(0~12)
=
=
=
=
10;
10;
10;
10;
The valid value range for the respective input varies depending on the module
type.
The following list is used to decipher the numbers. Changes to the inputs must be
made using the GEZE service terminal ST 220.
0: Inactive
1: Active leaf unlocked
2: Unlock active leaf (command)
3: Short-term release (KZF) active leaf
(AL) and passive leaf (IL) (commands)
4: Active leaf closed
5: Fire alarm system (opener)
6: RWA (opener)
7: Passive leaf closed
8: KZF-AL (command)
9: Time switch (ZSU) master
10: Switch function
11: Fire alarm system for universal module
(closer)
12: RWA for universal module (closer)
16.KZF1_ABORT(0/1) = 0; 0: Short-term release door #1 not interruptible
1: Short-term release door #1 interruptible
17.KZF1_AFTERTRG(0/1) = 0; 0: Short-term release door #1 cannot be triggered later
1: Short-term release door #1 can be triggered later
18.KZF1_TIME(3~30) = 10; Short-term release time door #1 (3 to 30 seconds)
19.KZF2_ABORT(0/1) = 0; 0: Short-term release door #2 not interruptible
1: Short-term release door #2 interruptible

GEZE IO 420
9
20.KZF2_AFTERTRG.(0/1) = 0; 0: Short-term release door #2 cannot be triggered later
1: Short-term release door #2 can be triggered later
21.KZF2_TIME(3~30) = 10; Short-term release time door #2 (3 to 30 seconds)
22.KZF3_ABORT(0/1) = 0; 0: Short-term release door #3 not interruptible
1: Short-term release door #3 interruptible
23.KZF3_AFTERTRG.(0/1) = 0; 0: Short-term release door #3 cannot be triggered later
1: Short-term release door #3 can be triggered later
24.KZF3_TIME(3~30) = 10; Short-term release time door #3 (3 to 30 seconds)
25.KZF4_ABORT(0/1) = 0; 0: Short-term release door #4 not interruptible
1: Short-term release door #4 interruptible
26.KZF4_AFTERTRG.(0/1) = 0; 0: Short-term release door #4 cannot be triggered later
1: Short-term release door #4 can be triggered later
27.KZF4_TIME(3~30) = 10; Short-term release time door #4 (3 to 30 seconds)
28. ADJ_DAY_LIGHT_SAVING (0/1) = 1; 0: Automatic switch over between summer and winter time is disabled
1: Automatic switch over between summer and winter time is enabled
29.not_used = 0;
30.AL_SUPPR_DUR(0~250) = 50; Duration of the alarm suppression with “watchdog” module type in seconds
31.AL_DELAY_TIME(0~250) = 100; Duration of the alarm delay with “watchdog” module type in seconds
32.MODULETYPE(0~12) = 10; 0: Watchdog;
1: One-door solution
2: Two-door solution
3: Four-door solution
4: IQ Lock EL + AUT
5: IQ Lock 72 + AUT (from software
version 2)
6: Automatic stat.
7: Automatic 4Sec
8: Window
9: Universal
10: RWS + KL400
33.LOGFILE_LEVEL(0~2) = 0; 0: Level 0. No protocol is written in the log le
1: Level 1. Alarm messages are written in the log le
2: Level 2. Alarm messages and actions are written in the log le
34.ZSUMASTER1_ACTIVITY(0/1) = 0; 0: As “ZSU master group 1” not active
1: As “ZSU master group 1” active
35.ZSUMASTER1_SUNDAY(0/1)
36.ZSUMASTER1_MONDAY(0/1)
37.ZSUMASTER1_TUESDAY(0/1)
38.ZSUMASTER1_WEDNESDA(0/1)
39.ZSUMASTER1_THURSDAY(0/1)
40.ZSUMASTER1_FRIDAY(0/1)
41.ZSUMASTER1_SATURDAY(0/1)
=
=
=
=
=
=
=
0;
0;
0;
0;
0;
0;
0;
Day conguration “ZSU master group 1”
0: As “ZSU master group 1” inactive on this day of the week
1: As “ZSU master group 1” active on this day of the week
42.ZSUMASTER1_START_HH(0~23)
43.ZSUMASTER1_START_MM(0~59)
=
=
0;
0;
Start time “ZSU master group 1”
Specication of “hours” 0-23; specication of “minutes” 0-59
44.ZSUMASTER1_END_HH(0~23)
45.ZSUMASTER1_END_MM(0~59)
=
=
0;
0;
End time “ZSU master group 1”
Specication of “hours” 0-23; specication of “minutes” 0-59
46.ZSUMASTER2_ACTIVITY(0/1) = 0; 0: As “ZSU master group 2” not active.
1: As “ZSU master group 2” active.
47.ZSUMASTER2_SUNDAY(0/1)
48.ZSUMASTER2_MONDAY(0/1)
49.ZSUMASTER2_TUESDAY(0/1)
50.ZSUMASTER2_WEDNESDAY(0/1)
51.ZSUMASTER2_THURSDAY(0/1)
52.ZSUMASTER2_FRIDAY(0/1)
53.ZSUMASTER2_SATURDAY(0/1)
=
=
=
=
=
=
=
0;
0;
0;
0;
0;
0;
0;
Day conguration “ZSU master group 2”.
0: As “ZSU master group 2” inactive on this day of the week
1: As “ZSU master group 2” active on this day of the week
54.ZSUMASTER2_START_HH(0~23)
55.ZSUMASTER2_START_MM(0~59)
=
=
0;
0;
Start time “ZSU master group 2”
Specication of “hours” 0-23; specication of “minutes” 0-59
56.ZSUMASTER2_END_HH(0~23)
57.ZSUMASTER2_END_MM(0~59)
=
=
0;
0;
End time “ZSU master group 2”
Specication of “hours” 0-23; specication of “minutes” 0-59
58.ZSUMASTER3_ACTIVITY(0/1) = 0; 0: As “ZSU master group 3” not active.
1: As “ZSU master group 3” active.
59.ZSUMASTER3_SUNDAY(0/1)
60.ZSUMASTER3_MONDAY(0/1)
61.ZSUMASTER3_TUESDAY(0/1)
62.ZSUMASTER3_WEDNESDAY(0/1)
63.ZSUMASTER3_THURSDAY(0/1)
64.ZSUMASTER3_FRIDAY(0/1)
65.ZSUMASTER3_SATURDAY(0/1)
=
=
=
=
=
=
=
0;
0;
0;
0;
0;
0;
0;
Day conguration “ZSU master group 3”.
0: As “ZSU master group 3” inactive on this day of the week
1: As “ZSU master group 3” active on this day of the week
66.ZSUMASTER3_START_HH(0~23)
67.ZSUMASTER3_START_MM(0~59)
=
=
0;
0;
Start time “ZSU master group 3”
Specication of “hours” 0-23; specication of “minutes” 0-59
68.ZSUMASTER3_END_HH(0~23)
69.ZSUMASTER3_END_MM(0~59)
=
=
0;
0;
End time “ZSU master group 3”
Specication of “hours” 0-23; specication of “minutes” 0-59
70.ZSUMASTER4_ACTIVITY(0/1) = 0; 0: As “ZSU master group 4” not active.
1: As “ZSU master group 4” active.

GEZE IO 420
10
71.ZSUMASTER4_SUNDAY(0/1)
72.ZSUMASTER4_MONDAY(0/1)
73.ZSUMASTER4_TUESDAY(0/1)
74.ZSUMASTER4_WEDNESDAY(0/1)
75.ZSUMASTER4_THURSDAY(0/1)
76.ZSUMASTER4_FRIDAY(0/1)
77.ZSUMASTER4_SATURDAY(0/1)
=
=
=
=
=
=
=
0;
0;
0;
0;
0;
0;
0;
Day conguration “ZSU master group 4”
0: As “ZSU master group 4” inactive on this day of the week
1: As “ZSU master group 4” active on this day of the week
78.ZSUMASTER4_START_HH(0~23)
79.ZSUMASTER4_START_MM(0~59)
=
=
0;
0;
Start time “ZSU master group 4”
Specication of “hours” 0-23; specication of “minutes” 0-59
80.ZSUMASTER4_END_HH(0~23)
81.ZSUMASTER4_END_MM(0~59)
=
=
0;
0;
End time “ZSU master group 4”
Specication of “hours” 0-23; specication of “minutes” 0-59
82.ZSUMASTER5_ACTIVITY(0/1) = 0; 0: As “ZSU master group 5” not active
1: As “ZSU master group 5” active
83.ZSUMASTER5_SUNDAY(0/1)
84.ZSUMASTER5_MONDAY(0/1)
85.ZSUMASTER5_TUESDAY(0/1)
86.ZSUMASTER5_WEDNESDAY(0/1)
87.ZSUMASTER5_THURSDAY(0/1)
88.ZSUMASTER5_FRIDAY(0/1)
89.ZSUMASTER5_SATURDAY(0/1)
=
=
=
=
=
=
=
0;
0;
0;
0;
0;
0;
0;
Day conguration “ZSU master group 5”
0: As “ZSU master group 5” inactive on this day of the week
1: As “ZSU master group 5” active on this day of the week
90.ZSUMASTER5_START_HH(0~23)
91.ZSUMASTER5_START_MM(0~59)
=
=
0;
0;
Start time “ZSU master group 5”
Specication of “hours” 0-23; specication of “minutes” 0-59
92.ZSUMASTER5_END_HH(0~23)
93.ZSUMASTER5_END_MM(0~59)
=
=
0;
0;
End time “ZSU master group 5”
Specication of “hours” 0-23; specication of “minutes” 0-59
94.DOOR1_SLAVEZSU_GR1(0/1)
95.DOOR1_SLAVEZSU_GR2(0/1)
96.DOOR1_SLAVEZSU_GR3(0/1)
97.DOOR1_SLAVEZSU_GR4(0/1)
98.DOOR1_SLAVEZSU_GR5(0/1)
=
=
=
=
=
0;
0;
0;
0;
0;
Slave assignment of door #1 to “ZSU master group” 1 to 5
0: Door #1 is not part of this ZSU group
1: Door #1 is part of this ZSU group
99.DOOR1_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #1 not interruptible
1: Time switch function for door #1 interruptible
100.DOOR2_SLAVEZSU_GR1(0/1)
101.DOOR2_SLAVEZSU_GR2(0/1)
102.DOOR2_SLAVEZSU_GR3(0/1)
103.DOOR2_SLAVEZSU_GR4(0/1)
104.DOOR2_SLAVEZSU_GR5(0/1)
=
=
=
=
=
0;
0;
0;
0;
0;
Slave assignment of door #2 to “ZSU master group” 1 to 5
0: Door #1 is not part of this ZSU group
1: Door #1 is part of this ZSU group
105.DOOR2_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #2 not interruptible
1: Time switch function for door #2 interruptible
106.DOOR3_SLAVEZSU_GR1(0/1)
107.DOOR3_SLAVEZSU_GR2(0/1)
108.DOOR3_SLAVEZSU_GR3(0/1)
109.DOOR3_SLAVEZSU_GR4(0/1)
110.DOOR3_SLAVEZSU_GR5(0/1)
=
=
=
=
=
0;
0;
0;
0;
0;
Slave assignment of door #3 to “ZSU master group” 1 to 5
0: Door #3 is not part of this ZSU group
1: Door #3 is part of this ZSU group
111.DOOR3_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #3 not interruptible
1: Time switch function for door #3 interruptible
112.DOOR4_SLAVEZSU_GR1(0/1)
113.DOOR4_SLAVEZSU_GR2(0/1)
114.DOOR4_SLAVEZSU_GR3(0/1)
115.DOOR4_SLAVEZSU_GR4(0/1)
116.DOOR4_SLAVEZSU_GR5(0/1)
=
=
=
=
=
0;
0;
0;
0;
0;
Slave assignment of door #4 to “ZSU master group” 1 to 5
0: Door #4 is not part of this ZSU group
1: Door #4 is part of this ZSU group
117.DOOR4_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #4 not interruptible
1: Time switch function for door #4 interruptible
118.TYPE OF CP(0~3) = 0; 0: No CP
1: One CP
2: Two CPs
3: Pin “+24V” and pin “DET” of the con-
nector “CP” are short-circuited together.
“CP” are short-circuited together.
END OF FILE---------------------------

GEZE IO 420
11
5 Module description
The IO 420 oers 10 module types. The respective inputs/outputs are used in dierent ways depending on the
module type.
5.1 Module type “watchdog”
The “watchdog” module type can be used for monitoring a door. When the monitoring function is armed, the
door may only be opened by release. In all other cases, an alarm message is sent after the alarm suppression and
alarm delay times have expired.
When the monitoring function is not armed, the door can be opened without release.
Connections Assignment/function description Menu
Input 1 àRising ank - monitoring is disarmed
àFalling ank - monitoring is armed
Duration for
short-term
release
2 Release with short-term release function; only with rising ank
3 Lock feedback
4 Door contact
Output 1 Monitoring state; enabled with armed monitoring
2 Electric strike fail safe
3 Alarm suppressed: 1 sec cycle
Alarm delayed: on
Alarm enabled: o
4 Alarm suppressed: o
Alarm delayed: o
Alarm enabled: Permanently on
Tab. 1: Pin assignment for “watchdog” module type
Funktionsbeschreibung der Ein- und Ausgänge
current state State changes to State changes with
Monitoring disarmed Alarm active Sabotage
Monitoring armed àFalling ank at input 1
àCAN command “watchdog enable”
àBACnet command “watchdog enable”
Monitoring armed Alarm active Sabotage
Monitoring disarmed àRising ank at input 1
àCAN command “watchdog disable”
àBACnet command “watchdog disable”
Alarm suppressed If the door is locked but open
Alarm suppressed
(output 1 enabled and output 3 ashing
every few seconds)
Alarm active Sabotage
Monitoring disarmed àRising ank at input 1
àCAN command “watchdog disable”
àBACnet command “watchdog disable”
Monitoring armed If the alarm actuation has been cancelled
and the alarm acknowledged
Alarm delayed If the alarm suppression time has expired
Alarm delayed
(output 1 and 3 enabled.)
Alarm active àSabotage
àIf the alarm delay time has expired
Monitoring armed
(if the alarm actuation has been cancelled
and a command sent either via input 2,
CAN or BACnet as acknowledgement to
the IO 420.)
àShort-term release through input 2
àCAN command “watchdog enable”,
“watchdog disable” or “KZF”
àBACnet command “KZF”
Alarm enabled
(output 1 and 4 enabled.)
Monitoring armed
(if the alarm actuation has been cancelled
and a command sent either via input 2,
CAN or BACnet as acknowledgement to
the IO 420.)
àShort-term release through input 2
àCAN command “watchdog enable”,
“watchdog disable” or “KZF”
àBACnet command “KZF”

GEZE IO 420
12
5.2 Module type “1 door”
The “1 door” module type can be used for controlling one door. The connection of release switch, short-term
release push button, reed contact and lock feedback is possible. The messages are forwarded via bus.
Connections Assignment/function description
Input 1àRising ank - unlock
àFalling ank - lock
2Short-term release is triggered with rising ank
3Lock feedback
4Door contact
Output 1Electric strike fail safe
2Electric strike fail secure
3Can be congured àInactive
àSabotage alarm
àClosed
àLocked
àClosed and locked
4Can be congured àInactive
àSabotage alarm
àClosed
àLocked
àClosed and locked
Tab. 2-pin assignment module type “1-door”
Current state State changes to State changes with
unlocked
In this state output 1 is enabled and output
2 is disabled.
Output 3 and 4 are enabled or disabled
depending on the conguration.
locked
if time switch is not enabled.
àFalling ank from input 1
àCAN command “lock”
àBACnet command “lock”
àSabotage
time switch (ZSU) If ZSU is active and one of the above-menti-
oned release devices occurs
locked
In this state output 2 is enabled and output
1 is disabled.
Output 3 and 4 are enabled or disabled
depending on the conguration.
unlocked àRising ank from input 1
àCAN command “unlock”
àBACnet command “unlock”
short-term release (KZF) àRising ank from input 2
àCAN command “short-term release”
àBACnet command “short-term release”
time switch (ZSU) If ZSU message is enabled and ZSU was not
interrupted
short-term release (KZF)
In this state output 1 is enabled and output
2 disabled.
Output 3 and 4 are enabled or disabled
depending on the conguration. KZF time
can be extended by input 2 if “KZF re-
triggering” is enabled.
locked If KZF time has expired
If KZF interruptible is enabled and the door
is closed again after opening. KZF is enabled
for at least 2.5 seconds
unlocked àRising ank from input 1
àCAN command “unlock”
àBACnet command “unlock”
time switch (ZSU)
In this state output 1 is enabled and output
2 disabled. Output 3 and 4 are enabled or
disabled depending on the conguration.
locked
with enabled option time switch inter-
ruption
àFalling ank from input 1
àCAN command “lock”
àBACnet command “lock”
locked
without enabled option time switch
interruption
àSabotage
àIf time switch message is no longer
enabled
Time switch interruption
If “time switch interruptible” is enabled in the IO 420 conguration, the “time switch” state can be interrupted using
the “lock” command. The state then changes to “locked” and the ag “time switch aborted” is set. No further change
in state can take place when the ag is set. The ag is reset again when the door is unlocked and locked. The mes-
sage “time switch” has to be enabled.

GEZE IO 420
13
5.3 Module type “2 doors”
The “2 doors” module type can be used for controlling two mutually independent doors. The connection of door
contacts and lock feedback to the inputs is possible. The connection of a release switch is not designated for this
module type.
Connections Assignment/function description
Input 1Lock feedback door #1
2Door contact door #1
3Lock feedback door #2
4Door contact door #2
Output 1Electric strike fail safe door #1
2Electric strike fail safe door #2
3Can be congured for door #1 àInactive
àSabotage alarm
àClosed
àLocked
àClosed and locked
4Can be congured for door #2 àInactive
àSabotage alarm
àClosed
àLocked
àClosed and locked
Tab. 3: Pin assignment module type “2-doors”
Current state State changes to State changes with
unlocked
In this state output 1 or 2 is enabled.
Output 3 and 4 are enabled or disabled
depending on the conguration.
locked
if time switch is not enabled.
àCAN command “lock”
àBACnet command “lock”
àSabotage
time switch (ZSU) If ZSU is active and one of the above-men-
tioned release devices occurs.
locked
In this state output 1 or 2 is disabled.
Output 3 and 4 are enabled or disabled
depending on the conguration.
unlocked àCAN command “unlock”
àBACnet command “unlock”
short-term release (KZF) àCAN command “short-term release”
àBACnet command “short-term release”
time switch (ZSU) If ZSU message is enabled and if ZSU was
not interrupted.
short-term release (KZF)
In this state output 1 or 2 is enabled.
Output 3 and 4 are enabled or disabled
depending on the conguration. KZF re-
triggering is not possible in this mode.
locked àIf KZF time has expired
àIf KZF interruptible is enabled and the
door is closed again after opening. The
min. KZF time is 2.5 seconds.
unlocked àCAN command “unlock”
àBACnet command “unlock”
time switch (ZSU)
In this state output 1 or 2 is enabled.
Output 3 and 4 are enabled or disabled
depending on the conguration.
locked
with enabled option time switch interrup-
tion
àCAN command “lock”
àBACnet command “lock”
locked
without enabled option time switch
interruption
àSabotage
àIf time switch message is no longer
enabled

GEZE IO 420
14
5.4 Module type “4 doors”
The “4 doors” module type can be used for controlling four mutually independent doors. Only the connection of
door contacts to the inputs is possible. The connection of a lock feedback or a release switch is not designated
for this module type.
Connections Assignment/function description
Input 1Door contact door #1
2Door contact door #2
3Door contact door #3
4Door contact door #4
Output 1Electric strike fail safe door #1
2Electric strike fail safe door #2
3Electric strike fail safe door #3
4Electric strike fail safe door #4
Tab. 4: Pin assignment module type “4-doors”
Current state State changes to State changes with
unlocked
In this state output 1, 2, 3 or 4 is enabled.
locked
if time switch is not enabled.
àCAN command “lock”
àBACnet command “lock”
àSabotage
time switch (ZSU) If ZSU is active and one of the above-men-
tioned release devices occurs
locked
In this state output 1, 2, 3 or 4 is disabled.
unlocked àCAN command “unlock”
àBACnet command “unlock”
short-term release (KZF) àCAN command “short-term release”
àBACnet command “short-term release”
time switch (ZSU) If ZSU message is enabled and if ZSU was
not interrupted
short-term release (KZF)
In this state output 1, 2, 3 or 4 is enabled.
KZF re-triggering is not possible in this
mode.
locked If KZF time has expired
If KZF interruptible is enabled and the door
is closed again after opening. The min. KZF
time is 2.5 seconds.
unlocked àCAN command “unlock”
àBACnet command “unlock”
time switch (ZSU)
In this state output 1, 2, 3 or 4 is enabled.
locked
with enabled option time switch interrup-
tion
àCAN command “lock”.
àBACnet command “lock”
locked
without enabled option time switch
interruption
àSabotage
àIf time switch message is no longer
enabled.

GEZE IO 420
15
5.5 Module type “automatic stat” / “automatic 4 sec”
With this module type, the IO 420 can control a GEZE door drive via inputs/outputs. Switches can be connected
at input 1 and 2 for this. Input 3 and 4 are used to evaluate the door feedback.
With this module type, no fault messages of the drive can be evaluated via the IO 420, since the drive com-
municates via the inputs/outputs rather than via RS485.
Connections Assignment/function description
Input 1àRising ank: change of state to “automatic”
àFalling ank: change of state to “night”
2àRising ank: change of state to “permanently open”
àFalling ank: no eect
3Lock state
4Door contact
Output 1Command to DCU “night”
2Command to DCU “shop closed”
3Command to DCU “automatic”
4Command to DCU “permanently open”
Tab. 5: Pin assignment of module type “automatic”
State State changes to State changes with
automatic
Output 3 is enabled.
If module type “automatic 4 sec” is enab-
led, output 3 is switched o again after 4
seconds.
night àFalling ank input 1
àCAN command “night”
àBACnet command “night”
shop closed àCAN command “close shop”
àBACnet command “close shop”
permanently open àThe rising ank input 2
àCAN command “permanent open”
àBACnet command “permanent open”
shop closed (shop closing)
Output 2 is enabled. If module type
“automatic 4 sec” is enabled, output 2 is
switched o again after 4 seconds.
night àThe falling ank input 1
àCAN command “night”
àBACnet command “night”
automatic àThe rising ank input 1
àCAN command “automatic”
àBACnet command “automatic”
permanently open àThe rising ank input 2
àCAN command “permanent open”
àBACnet command “permanent open”
permanently open:
Output 4 is enabled. If module type
“automatic 4 sec” is enabled, output 4 is
switched o again after 4 seconds.
night àThe falling ank input 1
àCAN command “night”
àBACnet command “night”
shop closed àCAN command “close shop”
àBACnet command “close shop”
automatic àThe rising ank input 1
àCAN command “automatic”
àBACnet command “automatic”
night
Output 1 is enabled. If module type
“automatic 4 sec” is enabled, output 1 is
switched o again after 4 seconds.
automatic àThe rising ank input 1
àCAN command “automatic”
àBACnet command “automatic”
shop closed àCAN command “close shop”
àBACnet command “close shop”
permanently open àThe rising ank input 2
àCAN command “permanent open”
àBACnet command “permanent open”

GEZE IO 420
16
5.6 Module type “window”
With this module type, the IO 420 can control two windows via inputs/outputs. Switches can be connected at
input 1 and 3 for this. Control is by means of collective commands i.e. the windows are triggered together.
With this module type, no fault messages of the drive can be evaluated, since the drive communicates via
the inputs/outputs rather than via RS485.
Connections Assignment/function description
Input 1Collective command “open windows” with rising ank. The falling ank has no function.
2Collective command “close windows” with rising ank. The falling ank has no function.
3Collective command “stop windows”.
Whether a stop is triggered by falling or rising ank can be congured.
4Feedback “closed” for window 1 and 2. The contacts should be closed in series.
Output 1Relais_open_win1. This relay is enabled if window 1 is to be opened.
2Relais_close_win1. This relay is enabled if window 1 is to be closed.
3Relais_open_win2. This relay is enabled if window 2 is to be opened.
4Relais_close_win2. This relay is enabled if window 2 is to be closed.
Tab. 6: Pin assignment of module type “window”
Current state State changes to State changes with
stop
all outputs are disabled.
opening àRising ank from input 1
àBACnet command “open window”
àCAN command “open window”
closing àRising ank from input 2
àBACnet command “close window”
àCAN command “close window”
closing
Output 2 or 4 is enabled.
opening àRising ank from input 1
àBACnet command “open window”
àCAN command “open window”
stop àRising ank from input 3
àIf the time of 90 sec has expired.
àBACnet command “stop”
àCAN command “stop”
opening
Output 1 or 3 is enabled.
closing àRising ank from input 2
àBACnet command “close window”
àCAN command “close window”
stop àRising ank from input 3
àIf the time of 90 sec has expired.
àBACnet command “stop”
àCAN command “stop”
5.7 Module type “universal”
With this module type, the IO 420 has universal control via inputs/outputs. Switches can be connected at input 1
and 4 for this. The inputs can be congured as ZSU masters and the ZSU master can be actuated via the respecti-
ve switch or internal timer. In addition, inputs 3 and 4 can be congured for RWA or BMA.
Connections Assignment/function description
Input 1àSwitch for relay 1:
Output 1 is switched on for rising ank, the output is switched o for falling ank.
àZSU master 1: ZSU master #1 is enabled as long as the switch is switched on.
2àSwitch for relay 2
àZSU master 2
3àSwitch for relay 3
àZSU master 3
àBMA (closer)
àRWA (closer)
4àSwitch for relay 4
àZSU master 4
àBMA (closer)
àRWA (closer)
Output 1Output relay 1
2Output relay 2
3Output relay 3
4Output relay 4
Tab. 7 Pin assignment module type “universal”

GEZE IO 420
17
State State changes to State changes with
o
The corresponding output is disabled.
on àWith rising ank of the corresponding
input, if this is congured as a switch.
àBACnet command “on”
àCAN command “on”
time switch If ZSU message is enabled and if ZSU was
not interrupted.
on
The corresponding output is enabled.
o
if ZSU is not enabled.
àFalling ank of the corresponding
input, if this is congured as a switch.
àBACnet command “o”
àCAN command “o”
time switch àWith the above-mentioned release
devices if the ZSU message is enabled.
time switch
The corresponding output is enabled.
o àIf the ZSU message is disabled.
àBACnet command “o” can trigger this
change in state if ZSU is congured as
“interruptible”.
àCAN command “o” can trigger this
change in state if ZSU is congured as
“interruptible”.
5.8 Module type “IQ lock El + Aut”
The module type “IQ Lock EL + Aut” is used to activate GEZE motor locks.
IQ Aut is connected with the IO 420 via bus (terminal “ST 220”) and controlled accordingly. All the states and fault
messages of IQ Aut can be read out and forwarded via BACnet.
IQ Lock EL is connected with the IO 420 via inputs/outputs and controlled accordingly. For this reason, the IO 420
can neither read out fault messages of IQ Lock EL nor forward these via BACnet.
– CAUTION In the case of re protection door, capacitor power (CP) must be connected to terminal CP
and the parameter“Conf. CP”must be set accordingly (see chapter 6.3 Service menu).
Release of the passive leaf
When the passive leaf is released, the active leaf is automatically released immediately.
Permanently open
With IQ Lock EL the state “permanently open” is possible.
With IQ Aut the door remains opened for the hold-open time set in the IO 420 conguration.
The shoot bolt is held by the switch lock as long as the door is open.
Connections Assignment/function description
Input 1AL_locked (feedback)
2àRelease_AL (command, factory setting)
àKZF_AL_IL (command), triggered with rising ank
3àKZF_AL_IL (command, factory setting), triggered with rising ank
àAL_closed (feedback)
àBMA (evaluated as opener)
àRWA (evaluated as opener)
4àBMA (factory setting, opener)
àRWA (opener)
àIL_closed (feedback)
àKZF_AL (command), triggered with rising ank
Output 1Release for IQ Lock EL
2Day/night for IQ Lock EL
3Feedback Relay active when AL is locked
4Feedback Relay active when AL is locked
Tab. 8: Pin assignment of module type “IQ lock”

GEZE IO 420
18
5.8.1 Active leaf
Current state State changes to State changes with
night
Outputs 1, 2 and 3 are disabled.
day àBACnet command “day”
àCAN command “day”
released àRising ank of input “release”
àBACnet command “release”
àCAN command “release”
short-term release (KZF) àRising ank of input “KZF”
àBACnet command “short-term release”
àCAN command “short-term release”
day
Output 2 is enabled
night àFalling ank from input “day/night”
àBACnet command “night”
àCAN command “night”
released àRising ank of input “release”
àBACnet command “release”
àCAN command “release”
short-term release àRising ank of input “KZF”
àBACnet command “short-term release”
àCAN command “short-term release”
released
Output 3 is enabled.
night àFalling ank of input “release” (the last
previous state was “night”)
àBACnet command “night”
àCAN command “night”
day àBACnet command “day”
àCAN command “day”
short-term release àNot possible
short-term release
Output 1 is enabled.
night àFalling ank of input “release” (the last
previous state was “night”)
àBACnet command “night”
àCAN command “night”
day àBACnet command “day”
àCAN command “day”
released àRising ank of input “release”
àBACnet command “release”
àCAN command “release”
error The error can be acknowledged with
any command.
5.8.2 Passive leaf
current state State changes to State changes with
unlock
(shown as “release” in VAT 220): Output 4
is enabled.
lock àBACnet command “lock”
àCAN command “lock”
lock
(shown as “night” in VAT 220): Output 4 is
disabled.
unlock
if ZSU is not enabled.
àThe rising ank of input “release_IL”
àBACnet command “unlock”
àCAN command “unlock”
into lock
(shown as “day” in VAT 220): This state is an
intermediate state between “unlock” and
“lock”.
into unlock
(shown as “day” in VAT 220): This state is
an intermediate state between “lock” and
“unlock”.
error
(shown as “error” in VAT 220):
The error can be acknowledged with
any command.

GEZE IO 420
19
5.9 Module type “RWS + KL”
In the module type “RWS + KL” the IO 420 works as a gateway between the CAN bus and BACnet and translates
the lifetime message of the TZ 320 into the BACnet protocol. The control commands generated are turned into
CAN commands by the IO 420 and forwarded to the TZ 320.
Gateway CAN BACnet
àTZ 320 transmits a lifetime message every second, which is transformed into the BACnet protocol and forwar-
ded on BACnet MS/TP level.
àBACnet object multi state value 4 is dened for activating the TZ 320. This object comprises three commands:
“short-term release”, “unlock” and “lock”.
àThe bus functions of the TZ 320 e.g. “collective locking”, “BMA group over BUS” etc. are currently not suppor-
ted by the IO 420. The bus function “timer” is implemented and is supported.
àIf a ZSU master transmits a ZSU message via BACnet, the IO 420 translates this into a CAN message.
àIf the IO 420 is congured as a timer master, the IO 420 transmits the ZSU message both via CAN bus and
BACnet.
Terminal box
The inputs and outputs of the IO 420 can be used as an IO extension for the TZ 320.
KL 220 has 4 inputs and 6 outputs. Since the IO 420 has 4 inputs and 4 outputs, the conguration for the fth and
sixth output of the KL 220 is not evaluated.
Fig. 3: Composition BACnet MS/TP and CAN for GEZE IO 420 as Gateway for TZ 320
Setting in TZ 320 and IO 420
àCAN: The CAN address in TZ 320 and IO 420 must be identical for both devices to be able to communicate with
one another via CAN.
àCAN terminating resistor The CAN terminating resistor in TZ 320 and IO 420 must be switched on.
àThe terminating resistor for the GEZE bus in IO 420 must be switched on. This setting is important for the
“terminal box” function.
àTimer function:
The TZ 320 must be congured as a “slave”.
The IO 420 per segment must be congured as “master”.
àThe ZSU master function is supported by the IO 420 with the following module types:
à1-door solution
à2-door solution
à4-door solution
àUniversal

GEZE IO 420
20
Fig. 4: Connection example for the module type “RWS + KL 220”
GND supply
X104 (red terminal strip)
24 V DC supply