GEZE IO 420 User Manual

Download

IO 420

EN User manual

164898-03

GEZE IO 420

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

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-buscompliant components in the GEZE system. This user manual describes the individual module types th 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.

Always read and observe these warning notices.

Follow all measures that are labelled with the warning symbol and warning word.

Warning symbol Warning word Meaning

–

CAUTION

at can be

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”

Symbol 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 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.

Protocol Implementation Conformance Statement

2 Safety and responsibility

2.1 Fundamental safety precautions

Use only original GEZE parts for repair work.

Unauthorised changes to the system exclude GEZE's liability for any resulting damage.

Primary protective measures are to be carried out on site.

Follow the VDE 0100 and VDE 0815 standards when laying the cables.

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 instructions included here must be noted and followed. Failure to comply releases the manufacturer from his statutory 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

GEZE IO 420

Device name: IO 420 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

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:

BACnet:

GEZE-Bus: DIP switch terminating resistor “GEZE-Bus” 120 Ohm

Network bias: DIP switch “Network bias”

Terminating resistor “CAN” 120 Ohm

Set the DIP switch at the start and end of the CAN-BUS to ON

Terminating resistor “BACnet” 120 Ohm

Set the BACnet DIP switch on the rst and last IO 420 of the BACnet MS/TP bus to ON

When GEZE motor lock or TZ 320 (connection for KL 220) is connected, set DIP switch to ON.

Set 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 supported. 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.

3.2.5 Reset

Reset push button

If the LED for microSD card is ashing, the microSD card must not be taken out of the slot. The IO 420 must be deenergised for the microSD card to be removed and inserted.

The factory settings can be restored using the reset push button.

Carrying out a reset

De-energise the device.

Keep the reset button pressed on the printed circuit board.

Switch 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.

Release the reset button when the LEDs start to ash.

To return the device to operating mode, switch the voltage supply o and on again.

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.

Termination 120 Ohm Router Termination 120 Ohm

GEZE IO 420

Only one bias may be enabled in a BACnet

Only one bias may be enabled

in a BACnet MS/TP network system.

MS/TP network system.

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

2 multistate value 1 shows the current module type. 3 multistate value 2 shows the current alarm message.

device object 1 contains the device description.

GEZE IO 420

4 binary input 1 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 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: à MAC address: à 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.

must be unambiguous in the BACnet network. It may not be allocated twice.

must be unambiguous in an MS/TP network.

assigned dierently depending on the module type

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.

After 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;

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.

GEZE IO 420

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

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.

10.CONF_OUTPUT3(0~4)

11.CONF_OUTPUT4(0~4)

12.INPUT1_TYPE(0~10)

13.INPUT2_TYPE(0~10)

14.INPUT3_TYPE(0~12)

15.INPUT4_TYPE(0~12)

16.KZF1_ABORT(0/1) = 0; 0: Short-term release door #1 not interruptible

17.KZF1_AFTERTRG(0/1) = 0; 0: Short-term release door #1 cannot 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

==0;0;Conguration of output 3 and 4 for door solution

= = = =

1= 9.6 kB

1 : Negative oset 0: Positive oset Oset = [UTC] - [local time], which is why Germany has a negative value.

0: Output inactive 1: Alarm 2: Locked

10;

The valid value range for the respective input varies depending on the module

10;

type.

10;

The following list is used to decipher the numbers. Changes to the inputs must be

10;

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)

1: Short-term release door #1 interruptible

1: Short-term release door #1 can be triggered later

1: Short-term release door #2 interruptible

2= 19.2 kB 3= 38.4 kB

4= 57.6 kB 5= 76.8 kB

3: Closed 4: Locked and closed.

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)

6= 115.2 kB

GEZE IO 420

20.KZF2_AFTERTRG.(0/1) = 0; 0: Short-term release door #2 cannot 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

23.KZF3_AFTERTRG.(0/1) = 0; 0: Short-term release door #3 cannot 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

26.KZF4_AFTERTRG.(0/1) = 0; 0: Short-term release door #4 cannot 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

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;

33.LOGFILE_LEVEL(0~2) = 0; 0: Level 0. No protocol is written in the log le

34.ZSUMASTER1_ACTIVITY(0/1) = 0; 0: As “ZSU master group 1” not 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)

42.ZSUMASTER1_START_HH(0~23)

43.ZSUMASTER1_START_MM(0~59) ==0;0;

44.ZSUMASTER1_END_HH(0~23)

45.ZSUMASTER1_END_MM(0~59) ==0;0;

46.ZSUMASTER2_ACTIVITY(0/1) = 0; 0: As “ZSU master group 2” not 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)

54.ZSUMASTER2_START_HH(0~23)

55.ZSUMASTER2_START_MM(0~59) ==0;0;

56.ZSUMASTER2_END_HH(0~23)

57.ZSUMASTER2_END_MM(0~59) ==0;0;

58.ZSUMASTER3_ACTIVITY(0/1) = 0; 0: As “ZSU master group 3” not 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)

66.ZSUMASTER3_START_HH(0~23)

67.ZSUMASTER3_START_MM(0~59) ==0;0;

68.ZSUMASTER3_END_HH(0~23)

69.ZSUMASTER3_END_MM(0~59) ==0;0;

70.ZSUMASTER4_ACTIVITY(0/1) = 0; 0: As “ZSU master group 4” not active.

= = = = = = =

1: Short-term release door #2 can be triggered later

1: Short-term release door #3 interruptible

1: Short-term release door #3 can be triggered later

1: Short-term release door #4 interruptible

1: Short-term release door #4 can be triggered later

1: Automatic switch over between summer and winter time is enabled

1: One-door solution 2: Two-door solution 3: Four-door solution 4: IQ Lock EL + AUT 5: IQ Lock 72 + AUT version 2)

1: Level 1. Alarm messages are written in the log le 2: Level 2. Alarm messages and actions are written in the log le

1: As “ZSU master group 1” active

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 0; 0; 0; 0;

Start time “ZSU master group 1”

Specication of “hours” 0-23; specication of “minutes” 0-59

End time “ZSU master group 1”

Specication of “hours” 0-23; specication of “minutes” 0-59

1: As “ZSU master group 2” active. 0;

Day conguration “ZSU master group 2”. 0;

0: As “ZSU master group 2” inactive on this day of the week 0;

1: As “ZSU master group 2” active on this day of the week 0; 0; 0; 0;

Start time “ZSU master group 2”

Specication of “hours” 0-23; specication of “minutes” 0-59

End time “ZSU master group 2”

Specication of “hours” 0-23; specication of “minutes” 0-59

1: As “ZSU master group 3” active. 0;

Day conguration “ZSU master group 3”. 0;

0: As “ZSU master group 3” inactive on this day of the week 0;

1: As “ZSU master group 3” active on this day of the week 0; 0; 0; 0;

Start time “ZSU master group 3”

Specication of “hours” 0-23; specication of “minutes” 0-59

End time “ZSU master group 3”

Specication of “hours” 0-23; specication of “minutes” 0-59

1: As “ZSU master group 4” active.

(from software

6: Automatic stat. 7: Automatic 4Sec 8: Window 9: Universal 10: RWS + KL400

GEZE IO 420

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)

78.ZSUMASTER4_START_HH(0~23)

79.ZSUMASTER4_START_MM(0~59) ==0;0;

80.ZSUMASTER4_END_HH(0~23)

81.ZSUMASTER4_END_MM(0~59) ==0;0;

82.ZSUMASTER5_ACTIVITY(0/1) = 0; 0: As “ZSU master group 5” not 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)

90.ZSUMASTER5_START_HH(0~23)

91.ZSUMASTER5_START_MM(0~59) ==0;0;

92.ZSUMASTER5_END_HH(0~23)

93.ZSUMASTER5_END_MM(0~59) ==0;0;

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)

99.DOOR1_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #1 not 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)

105.DOOR2_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #2 not 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)

111.DOOR3_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #3 not 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)

117.DOOR4_SLAVEZSU_ABORT(0/1) = 0; 0: Time switch function for door #4 not interruptible

118.TYPE OF CP(0~3) = 0; 0: No CP

END OF FILE---------------------------

= = = = = =

= = = = = = =

= = = = =

Day conguration “ZSU master group 4” 0;

0: As “ZSU master group 4” inactive on this day of the week 0;

1: As “ZSU master group 4” active on this day of the week 0; 0; 0; 0;

Start time “ZSU master group 4”

Specication of “hours” 0-23; specication of “minutes” 0-59

End time “ZSU master group 4”

Specication of “hours” 0-23; specication of “minutes” 0-59

1: As “ZSU master group 5” active 0;

Day conguration “ZSU master group 5” 0;

0: As “ZSU master group 5” inactive on this day of the week 0;

1: As “ZSU master group 5” active on this day of the week 0; 0; 0; 0;

Start time “ZSU master group 5”

Specication of “hours” 0-23; specication of “minutes” 0-59

End time “ZSU master group 5”

Specication of “hours” 0-23; specication of “minutes” 0-59 0;

Slave assignment of door #1 to “ZSU master group” 1 to 5 0;

0: Door #1 is not part of this ZSU group 0;

1: Door #1 is part of this ZSU group 0; 0;

1: Time switch function for door #1 interruptible 0;

Slave assignment of door #2 to “ZSU master group” 1 to 5 0;

0: Door #1 is not part of this ZSU group 0;

1: Door #1 is part of this ZSU group 0; 0;

1: Time switch function for door #2 interruptible 0;

Slave assignment of door #3 to “ZSU master group” 1 to 5 0;

0: Door #3 is not part of this ZSU group 0;

1: Door #3 is part of this ZSU group 0; 0;

1: Time switch function for door #3 interruptible 0;

Slave assignment of door #4 to “ZSU master group” 1 to 5 0;

0: Door #4 is not part of this ZSU group 0;

1: Door #4 is part of this ZSU group 0; 0;

1: Time switch function for door #4 interruptible

3: Pin “+24V” and pin “DET” of the con-

1: One CP

2: Two CPs

nector “CP” are short-circuited together. “CP” are short-circuited together.

GEZE IO 420

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

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

Duration for short-term release

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

Monitoring armed Alarm active Sabotage

Monitoring disarmed à Rising ank at input 1

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

Monitoring armed

Alarm delayed If the alarm suppression time has expired

Alarm delayed (output 1 and 3 enabled.)

Alarm enabled (output 1 and 4 enabled.)

Alarm active à Sabotage

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.)

à CAN command “watchdog enable” à BACnet command “watchdog enable”

à CAN command “watchdog disable” à BACnet command “watchdog disable”

If the alarm actuation has been cancelled and the alarm acknowledged

à If the alarm delay time has expired à Short-term release through input 2

à CAN command “watchdog enable”,

“watchdog disable” or “KZF”

à BACnet command “KZF”

à Short-term release through input 2 à CAN command “watchdog enable”,

“watchdog disable” or “KZF”

à BACnet command “KZF”

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

Output

Tab. 2-pin assignment module type “1-door”

à Rising ank - unlock

à Falling ank - lock

Short-term release is triggered with rising ank

Lock feedback

Door contact

Electric strike fail safe

Electric strike fail secure

Can be congured à Inactive

GEZE IO 420

à Sabotage alarm à Closed à Locked à Closed and locked

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 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.

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 retriggering” is enabled.

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 if time switch is not enabled.

time switch (ZSU) If ZSU is active and one of the above-menti-

unlocked à Rising ank from input 1

short-term release (KZF) à Rising ank from input 2

time switch (ZSU) If ZSU message is enabled and ZSU was not

locked If KZF time has expired

unlocked à Rising ank from input 1

locked with enabled option time switch interruption

locked without enabled option time switch interruption

à Falling ank from input 1 à CAN command “lock” à BACnet command “lock” à Sabotage

oned release devices occurs

à CAN command “unlock” à BACnet command “unlock”

à CAN command “short-term release” à BACnet command “short-term release”

interrupted

If KZF interruptible is enabled and the door is closed again after opening. KZF is enabled for at least 2.5 seconds

à CAN command “unlock” à BACnet command “unlock”

à Falling ank from input 1 à CAN command “lock” à BACnet command “lock”

à 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 message “time switch” has to be enabled.

GEZE IO 420

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

Output

Tab. 3: Pin assignment module type “2-doors”

Lock feedback door #1

Door contact door #1

Lock feedback door #2

Door contact door #2

Electric strike fail safe door #1

Electric strike fail safe door #2

Can be congured for door #1 à Inactive

Can be congured for door #2 à Inactive

à Sabotage alarm à Closed à Locked à Closed and locked

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 In this state output 1 or 2 is disabled. Output 3 and 4 are enabled or disabled depending on the conguration.

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 retriggering is not possible in this mode.

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 if time switch is not enabled.

time switch (ZSU) If ZSU is active and one of the above-men-

unlocked à CAN command “unlock”

short-term release (KZF) à CAN command “short-term release”

time switch (ZSU) If ZSU message is enabled and if ZSU was

locked à If KZF time has expired

unlocked à CAN command “unlock”

locked with enabled option time switch interruption

locked without enabled option time switch interruption

à CAN command “lock” à BACnet command “lock” à Sabotage

tioned release devices occurs.

à BACnet command “unlock”

à BACnet command “short-term release”

not interrupted.

à If KZF interruptible is enabled and the

door is closed again after opening. The min. KZF time is 2.5 seconds.

à BACnet command “unlock” à CAN command “lock”

à BACnet command “lock”

à Sabotage à If time switch message is no longer

enabled

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

Output

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 In this state output 1, 2, 3 or 4 is disabled.

short-term release (KZF) In this state output 1, 2, 3 or 4 is enabled. KZF re-triggering is not possible in this mode.

time switch (ZSU) In this state output 1, 2, 3 or 4 is enabled.

Door contact door #1

Door contact door #2

Door contact door #3

Door contact door #4

Electric strike fail safe door #1

Electric strike fail safe door #2

Electric strike fail safe door #3

Electric strike fail safe door #4

GEZE IO 420

locked if time switch is not enabled.

time switch (ZSU) If ZSU is active and one of the above-men-

unlocked à CAN command “unlock”

short-term release (KZF) à CAN command “short-term release”

time switch (ZSU) If ZSU message is enabled and if ZSU was

locked If KZF time has expired

unlocked à CAN command “unlock”

locked with enabled option time switch interruption

locked without enabled option time switch interruption

à CAN command “lock” à BACnet command “lock” à Sabotage

tioned release devices occurs

à BACnet command “unlock”

à BACnet command “short-term release”

not interrupted

If KZF interruptible is enabled and the door is closed again after opening. The min. KZF time is 2.5 seconds.

à BACnet command “unlock” à CAN command “lock”.

à BACnet command “lock”

à Sabotage à If time switch message is no longer

enabled.

GEZE IO 420

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 communicates via the inputs/outputs rather than via RS485.

Connections Assignment/function description

Input

3 4

Output

1 2 3 4

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 enabled, output 3 is switched o again after 4 seconds.

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.

permanently open: Output 4 is enabled. If module type “automatic 4 sec” is enabled, output 4 is switched o again after 4 seconds.

night Output 1 is enabled. If module type “automatic 4 sec” is enabled, output 1 is switched o again after 4 seconds.

à Rising ank: change of state to “automatic” à Falling ank: change of state to “night”

à Rising ank: change of state to “permanently open” à Falling ank: no eect

Lock state Door contact Command to DCU “night” Command to DCU “shop closed” Command to DCU “automatic” Command to DCU “permanently open”

night à Falling ank input 1

shop closed à CAN command “close shop”

permanently open à The rising ank input 2

night à The falling ank input 1

automatic à The rising ank input 1

permanently open à The rising ank input 2

night à The falling ank input 1

shop closed à CAN command “close shop”

automatic à The rising ank input 1

shop closed à CAN command “close shop”

permanently open à The rising ank input 2

à CAN command “night” à BACnet command “night”

à BACnet command “close shop”

à CAN command “permanent open” à BACnet command “permanent open”

à CAN command “night” à BACnet command “night”

à CAN command “automatic” à BACnet command “automatic”

à CAN command “permanent open” à BACnet command “permanent open”

à CAN command “night” à BACnet command “night”

à BACnet command “close shop”

à CAN command “automatic” à BACnet command “automatic”

à BACnet command “close shop”

à CAN command “permanent open” à BACnet command “permanent open”

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

Output

Tab. 6: Pin assignment of module type “window”

Current state State changes to State changes with

stop all outputs are disabled.

closing Output 2 or 4 is enabled.

opening Output 1 or 3 is enabled.

Collective command “open windows” with rising ank. The falling ank has no function.

Collective command “close windows” with rising ank. The falling ank has no function.

Collective command “stop windows”.

Feedback “closed” for window 1 and 2. The contacts should be closed in series.

Relais_open_win1. This relay is enabled if window 1 is to be opened.

Relais_close_win1. This relay is enabled if window 1 is to be closed.

Relais_open_win2. This relay is enabled if window 2 is to be opened.

Relais_close_win2. This relay is enabled if window 2 is to be closed.

GEZE IO 420

Whether a stop is triggered by falling or rising ank can be congured.

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”

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”

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 respective switch or internal timer. In addition, inputs 3 and 4 can be congured for RWA or BMA.

Connections Assignment/function description

Input

Output

Tab. 7 Pin assignment module type “universal”

à Switch for relay 1:

1 2 3 4

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. à Switch for relay 2

à ZSU master 2 à Switch for relay 3

à ZSU master 3 à BMA (closer) à RWA (closer)

à Switch for relay 4 à ZSU master 4 à BMA (closer) à RWA (closer)

Output relay 1 Output relay 2 Output relay 3 Output relay 4

GEZE IO 420

State State changes to State changes with

o The corresponding output is disabled.

on The corresponding output is enabled.

time switch The corresponding output is enabled.

on à With rising ank of the corresponding

time switch If ZSU message is enabled and if ZSU was

o if ZSU is not enabled.

time switch à With the above-mentioned release

o à If the ZSU message is disabled.

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.

input, if this is congured as a switch. à BACnet command “on” à CAN command “on”

not interrupted.

à Falling ank of the corresponding

input, if this is congured as a switch. à BACnet command “o” à CAN command “o”

devices if the ZSU message is enabled.

à 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”.

–

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

Output

AL_locked (feedback)

1 2

1 2 3 4

à Release_AL (command, factory setting) à KZF_AL_IL (command), triggered with rising ank

à KZF_AL_IL (command, factory setting), triggered with rising ank à AL_closed (feedback) à BMA (evaluated as opener) à RWA (evaluated as opener)

à BMA (factory setting, opener) à RWA (opener) à IL_closed (feedback) à KZF_AL (command), triggered with rising ank

Release for IQ Lock EL

Day/night for IQ Lock EL

Feedback Relay active when AL is locked

Tab. 8: Pin assignment of module type “IQ lock”

5.8.1 Active leaf

Current state State changes to State changes with

night Outputs 1, 2 and 3 are disabled.

day Output 2 is enabled

released Output 3 is enabled.

short-term release Output 1 is enabled.

error The error can be acknowledged with

GEZE IO 420

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”

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”

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 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”

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 (shown as “night” in VAT 220): Output 4 is disabled.

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):

lock à BACnet command “lock”

unlock if ZSU is not enabled.

The error can be acknowledged with any command.

à CAN command “lock”

à The rising ank of input “release_IL” à BACnet command “unlock” à CAN command “unlock”

GEZE IO 420

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

X104 (red terminal strip)

GND supply

24 V DC supply

GEZE IO 420

Fig. 4: Connection example for the module type “RWS + KL 220”

GEZE IO 420

5.10 Module type “DCU1, 2 and 8”

“DCU 1, 2 and 8” are type identications of swing door and sliding door drive with DCU light (CAN interface). In this type of module, the IO 420 functions as gateway as in module type “RWS + KL”. Therefore, drives require DCU light so that the lifetime report is forwarded to IO 420 via Can. Active leaves and passive leaves can also be connected.

Gateway CAN BACnet

à Automatic drive transmits a lifetime message every second, which is transformed into the BACnet protocol

and forwarded on BACnet MS/TP level. à BACnet object multistate value 3 represents the current operating mode. à BACnet object multistate value 4 can change the operating mode. à The inputs and outputs must be used freely as in module type “universal”.

Setting in DCU

à CAN: The CAN address in DCU and IO 420 must be identical for both devices to be able to communicate with

one another via CAN. E.g. DCU-GF has CAN-Address 7 and DCU-SF has 8. Then you must set CAN addresses in

IO 420:

In „Buskonf.“ „konf.CAN“ „1.CAN-Adresse:“ muss die CAN-Adresse für DCU-GF eingetragen werden.

In „Buskonf.“ „konf.CAN“ „2.CAN-Adresse:“ soll die CAN-Adresse für DCU-SF eingetragen werden. à CAN-terminating resistor on the rst and last device must be activated.

Device Parameter Value DCU-GF Bus address 1 DCU-SF Bus address 2

IO 420

Buskonf./ 1.CAN-Adr 1 Buskonf./ 1.CAN-Adr 2

5.11 Module type “DCU6” (revolving door)

In this type of module, the IO 420 functions as gateway as in module type “DCU 1, 2 and 8”. Therefore, drives require DCU light so that the lifetime report is forwarded to IO 420 via Can. Active leaves and passive leaves can also be connected.

Gateway CAN BACnet

à Automatic drive transmits a lifetime message every second, which is transformed into the BACnet protocol

Setting in DCU

à CAN: The CAN address in DCU and IO 420 must be identical for both devices to be able to communicate with

one another via CAN. In “Buskonf.” “konf.CAN” “1.CAN-Adresse:” the CAN address of the revolving door drive

must be entered. à CAN-terminating resistor of both devices must be activated.

5.12 Module type “DCU128+RWS+KL”

à This type of module is a summary of “RSW+KL” and “DCU 1, 2 and 8”. TZ 320, DCU-GF and DCU-SF are con-

nected by CAN. Terminals 45 and 46 of TZ 320 are connected to the GEZE BUS of IO 420. Thus, the inputs and

outputs of IO 420 are used as terminal box for RWS.

Setting in DCU

à CAN address of DCU-GF and TZ320 must have the same CAN address. This address is entered in IO 420 under

“Buskonf.” “Konf. CAN” “CAN-Adr[DCU GF,TZ]“. à CAN-Address of DCU-SF is entered in IO 420 under “Buskonf.” “Konf. CAN” “CAN-Adr[DCU SF]”.

Device Parameter Value Parameter DCU-GF Bus address 1 Bus address DCU-SF Bus address 2 Bus address TZ 320 Bus address 1 Bus address

IO 420

Buskonf./ 1.CAN-Adr 1 Buskonf./ 2.CAN-Adr 2

6 Annex

6.1 EDE lists

6.1.1 1-door solution

Mandatory Optional

Key name / Object name

lock_state 1 3 1 N Y 3 close_state 1 3 2 N Y 4 Device_IO420 1 8 1 N N

Alarm_message 1 15 50 N N module_type 1 19 1 1 11 N Y 1

alarm_type 1 19 2 1 15 N Y 2 50 door_state 1 19 3 1 4 N Y 5 door_command 1 19 4 1 1 3 Y Y 6

6.1.2 2 door-solution

Mandatory Optional

GEZE IO 420

device

obj. inst.

object type

object

inst.

present-va-

lue-default

min-pre-

sent-value

max-pre-

sent-value

command-

able

supports

COV

state-text-

reference

notif.

class

Key name / Object name

door1_lock_state 1 3 1 N Y 3 door1_close_state 1 3 2 N Y 4 door2_lock_state 1 3 3 N N 3

door2_close_state 1 3 4 N N 4 Device_IO420 1 8 1 N Y

Alarm_message 1 15 50 N Y module_type 1 19 1 1 11 N Y 1 alarm_type 1 19 2 1 15 N Y 2 50 door1_state 1 19 3 1 4 N Y 5 door1_command 1 19 4 1 1 3 Y Y 6 door2_state 1 19 5 1 4 N Y 5 door2_command 1 19 6 1 1 3 Y Y 6

6.1.3 4 door-solution

Mandatory Optional

Key name / Object name

door1_close_state door2_close_state 1 3 2 N Y 4 door3_close_state 1 3 3 N N 4 door4_close_state 1 3 4 N N 4 Device_IO420 1 8 1 N Y Alarm_message 1 15 50 N Y module_type 1 19 1 11 N Y 1 alarm_type 1 19 2 1 15 N Y 2 50 door1_state 1 19 3 1 4 N Y 5 door1_command 1 19 4 1 1 3 Y Y 6 door2_state 1 19 5 1 4 N Y 5 door2_command 1 19 6 1 1 3 Y Y 6 door3_state 1 19 7 1 4 N Y 5 door3_command 1 19 8 1 1 3 Y Y 6 door4_state 1 19 9 1 4 N Y 5 door4_command 1 19 10 1 1 3 Y Y 6

device

obj. inst.

object type

object

inst.

present-va-

lue-default

min-pre-

sent-value

max-pre-

sent-value

command-

able

supports

COV

device

obj. inst.

object type

object

inst.

present-va-

lue-default

min-pre-

sent-value

max-pre-

sent-value

command-

able

supports

COV

1 3 1 N Y 4

state-text-

reference

notif.

class

state-text-

reference

notif.

class

GEZE IO 420

6.1.4 Module type automatic

Mandatory Optional

Key name / Object name

device

lock_state close_state 1 3 2 Device_IO420 1 8 1 Alarm_message 1 15 50 module_type 1 19 1 alarm_type 1 19 2 DCU_state 1 19 3 DCU_command 1 19 4 1 1 4 Y Y 61

1 3 1

6.1.5 Module type IQ lock EL + Aut

Mandatory Optional

Key name / Object name

obj. inst.

object type

object

inst.

present-va-

lue-default

min-present-

value

max-present-

value

command-

able

supports COV

state-text-

reference

notif.

class

1 11 N Y 1 1 15 N Y 2 50 1 5 N Y 51

N Y 3 N Y 4 N N N N

unlock_state_AL close_state_AL 1 3 2 unlock_state_IL 1 3 3 close_state_IL 1 3 4 Device_IO420 1 8 1 Alarm_message 1 15 50 module_type 1 19 1 alarm_type 1 19 2 ActiveLeaf_state 1 19 3 ActiveLeaf_command 1 19 4 1 1 4 Y Y 62 InactiveLeaf_state 1 19 5 InactiveLeaf_command 1 19 6 1 1 2 Y Y 82

6.1.6 Module type RWS

Mandatory Optional

Key name / Object name

lock_state close_state 1 3 2 Device_IO420 1 8 1 Alarm_message 1 15 50 module_type 1 19 1 alarm_type 1 19 2 TZ320_state 1 19 3 TZ320_command 1 19 4 1 1 4 Y Y 63

device

obj. inst.

object type

1 3 1

device

obj. inst.

object type

1 3 1

object

inst.

object

inst.

present-va-

lue-default

min-present-

value

max-present-

value

command-

able

supports COV

N Y 32 N Y 4 N N 32 N N 4 N Y

N Y 1 11 N Y 1 1 15 N Y 2 50 1 5 N Y 52

1 5 N Y 72

lue-default

min-present-

value

max-present-

value

command-

able

supports COV

N Y 3 N Y 4 N N

N N 1 11 N Y 1 1 15 N Y 23 50 1 11 N Y 53

state-text-

reference

notif.

class

state-text-

reference

notif.

class

6.1.7 Module type universal

Mandatory Optional

Key name / Object name

input1_state input2_state 1 3 2 input3_state 1 3 3 input4_state 1 3 4 Device_IO420 1 8 1 Alarm_message 1 15 50 module_type 1 19 1 alarm_type 1 19 2 output1_state 1 19 3 output1_command 1 19 4 1 1 2 Y Y 54 output2_state 1 19 5 output2_command 1 19 6 1 1 2 Y Y 54 output3_state 1 19 7 output3_command 1 19 8 1 1 2 Y Y 54 output4_state 1 19 9 output4_command 1 19 10 1 1 2 Y Y 54

device

obj. inst.

object type

1 3 1

object

inst.

present-va-

GEZE IO 420

lue-default

min-present-

value

max-present-

value

command-

able

supports

COV

state-text-

reference

notif.

class N Y 34 N Y 34 N N 34 N N 34 N Y N Y

1 11 N Y 1 1 15 N Y 2 50 1 3 N Y 44

1 3 N Y 44

6.1.8 Module type watchdog

Mandatory Optional

Key name / Object name

lock_state 1 3 1 close_state 1 3 2 Device_IO420 1 8 1 Alarm_message 1 15 50 module_type 1 19 1 alarm_type 1 19 2 watchdog_state 1 19 3 watchdog_command 1 19 4 1 1 3 Y Y 66

6.1.9 Module type window

Mandatory Optional

Key name / Object name

window1_close_state 1 3 1 window2_close_state 1 3 2 Device_IO420 1 8 1 Alarm_message 1 15 50 module_type 1 19 1 alarm_type 1 19 2 window1_state 1 19 3 window1_command 1 19 4 1 1 3 Y Y 55 window2_state 1 19 5 window2_command 1 19 6 1 1 3 Y Y 55

device

obj. inst.

object type

object

inst.

present-va-

lue-default

min-present-

value

max-present-

value

command-

able

supports COV

state-text-

reference

notif.

class

value

N Y 3 N Y 4 N N N N

max-present-

value

N Y 4 N Y 4 N N N N

command-able

supports COV

state-text-

reference

notif.

class

1 11 N Y 1 1 15 N Y 2 50 1 6 N Y 56

device

obj. inst.

object type

object

inst.

present-value-

default

min-present-

1 11 N Y 1 1 15 N Y 2 50 1 4 N Y 45

1 4 N Y 45

GEZE IO 420

6.1.10 Module type „DCU 1,2 and 8“ and „DUC 6“

mandatory optional

object-name

object-type

object-in-

stance

present-value-

default

Input1 Input2 3 2 Input3 3 3 Input4 3 4 Device_IO420 8 1 N N notication_class_obj 15 50 module_type 19 1 alarm_type 19 2 operating_mode 19 3 mode_command 19 4 1 1 7 Y N 85 lock_state 19 5 door_command 19 6 1 1 4 Y N 87 door_state 19 7 reduced_width 19 8 1 2 Y N 89 master_key 19 9 output1_command 19 10 1 1 3 Y N 91 alarm_dcu_1 19 11 1 31 N N 92 50 alarm_dcu_2 19 12 1 31 N N 93 50 alarm_dcu_3 19 13 1 31 N N 94 50 output2_command 19 14 1 1 3 91 output3_command 19 15 1 1 3 91 output4_command 19 15 1 1 3 91

3 1

N N N N

N 1 1 1

min-present-

value

max-present-

value

commanda-

ble

supports COV

N 83 N 83 N 83 N 83

13 N N 1 15 N N 2 50 14 N N 84

5 N N 86

5 N N 88

4 N N 90

state-text-

reference

notif-class

6.1.11 Module type “DCU 128+RWS+KL”

mandatory optional

object-name

object-type

lock_state_TZ door_state_TZ 3 2 door_state_DCU_GF 3 3 door_state_DCU_SF 3 4 Device_IO420 8 1 notication_class_obj 15 50 module_type 19 1 Alarm_TZ 19 2 operating_mode_DCU 19 3 mode_command 19 4 1 1 7 Y N 95 lock_state_DCU 19 5 door_command 19 6 1 1 4 Y N 87 mode_TZ 19 7 reduced_width 19 8 1 2 Y N 89 maintennance 19 9 emergency open 19 10 1 1 2 Y N 97 dcu_alarm1 19 11 1 31 N N 92 50 dcu_alarm2 19 12 1 31 N N 93 50 dcu_alarm3 19 13 1 31 N N 94 50

3 1

object-instance

present-value-

default

min-present-

value

max-present-

value

commanda-

ble

supports COV

state-text-

reference

notif-class

N N N N N N

13 N N 1

15 N N 6 50

14 N N 84

5 N N 86

5 N N 53

4 N N 96

N 3 N 4 N 4 N 4 N N

6.2 State text

GEZE IO 420

Watchdog

IQ lock 72

error

IQ lock El

error

IQ Aut inacti-

ve leaf error

IQ Aut active

leaf error

BACnet

disturbed

can/power

supply

disturbed

RTC distur-

bed-TZ

Comm. TT

disturbed

Comm. KL

disturbed

fault-TZ

relay fault-TZ exit opener

can distur-

bed

open-BUS

automatic_4sec windows universal rws _kl400

re alarm group

conict

tic_stat

burglary

group

conict

time switch

group

conict

sabotage

alarm

burglary

alarm

Text 3 Text 4 Text 5 Text 6 Text 7 Text 8 Text 9 Text 10 Text 11 Text 12 Text 13 Text 14 Text 15

Text 2 or

Active-Text

alarm

time switch

active

release

sabotage-TT sabotage-KL emergency

open-TT

sabotage-TZ emergency

door alarm-

release

hazard

alarm-TZ

open-TZ

DCU error

open

active

service mode alarm active active sluice passive sluice sluice busy

release

IQ lock error

release

pre-lock lock burglar-lock short-term

active

alarm active

alarm de-

layed

alarm sup-

pressed

open

release

short-term

release

watchdog

disabled

release

short-term

release

disable

watchdog

Inactive-Text

Ref. no Text 1 or

1 watchdog 1_door 2_doors 4_doors iq_ lock_el iq_lock_bus automa -

2 no alarm re alarm smoke heat

3 unlocked locked

4 open closed

5 unlock lock short-term

6 unlock lock short-term

23 no alarm emergency

32 locked unlocked

34 inac tive active

44 o on time switch

45 stopped opening closing window error

51 automatic night shop closed permanently

52 night day released shor t-term

53 unlock time switch

54 o on

enabled

55 stop open close

56 watchdog

61 automatic night shop closed permanently

62 night day release shor t-term

watchdog

63 no command unlock lock short-term

66 enable

72 unlock lock into unlock into lock IQ lock error

82 unlock lock

GEZE IO 420

RTC distur-

bed-TZ

DCU Type/

GF-SF incon-

volving_door

maintenance

due GF and

maintenance

due SF

maintenance

due GF

sistent

present

BACnet

disturbed

can/power

supply

automatic_4sec windows universal RWS_ KL400 DCU_1_2 DCU_6_re-

re alarm group

conict

tic_stat

burgalry

group

time switch

group

sabotage

alarm

burglary

alarm

active sluice passive sluice sluice busy power-o DCU not

disturbed

conict

smoke alarm

DCU disturbed heat and

DCU not

initialized

re alarm

active

RWS turn o

time switch

active

open

unknown

open

locked

contact

authorized

closed

GF- and SF-

master key

active

turn o/

unlocked

RWS/ unlo-

cked

permanently

open/ unlo-

cked

automatic/

unlocked

maintenance

due GF and

Text 3 Text 4 Text 5 Text 6 Text 7 Text 8 Text 9 Text 10 Text 11 Text 12 Text 13 Text 14 Text 15

Text 2 or

Active-Text

Text 1 or

Inactive-Text

# Refe-

rence

Number

alarm

watchdog 1_door 2_doors 4_doors iq_lock_el iq_lock_bus automa -

no alarm re alarm smoke heat

83 inac tive active

84 automatic night shop closed permanently

85 no command night shop close automatic permanently

contact

outside

inside

86 unlocked GF locked SF locked GF and SF

87 no command contact

88 not closed GF closed SF closed GF and SF

SF-master

key active

release(d)

unlocked

maintenance

due SF

winter mode

GF-master

key active

mode

key active

89 summer

90 no master

91 turn(ed) o turn(ed) on short time

maintenance

due GF

emergency

open active

tenance

required.

open inac tive

95 no command night/ locked shop close/

96 no main-

97 emergency

no alarm

15_DPS dis-

connected

46_Temp-

sens

(motor)

fault.- GF

14_MPS dis-

connected

45_Drive is

too hot-GF

13_SIS-GF

detective

active

12_Motor

fault-GF

no alarm 44_Stop is

11_Motor

short-GF

42_Emer-

gency lock

active

no_Alarm no_ Alarm

61_Battery

at.

29_SIO -SF

detective

control

unit-GF

28_Motor

relay-GF

27_SIO1/SIO2

active

no alarm no alarm 60_Err. in

26_Zero

position err.

alarm-SF

GEZE IO 420

no alarm no alarm

91_no

impluse

from enco-

der

unit defec-

tive.

err.-GF

41_Testing

SIO-GF

no alarm 10_Encoder

40_Perma-

nent actuati-

on KB

alarm

39_Perma-

nent actua-

tion KA

38_Permanent

actuation KI2/

PE3

37_Perma-

nent actuati-

on KI1

36_Internal

redundancy

fault/

no alarm no alarm no alarm 07_Fire alarm 08_Smoke

35_Phar-

machy/

Permanent

act.PE1

while ope -

ning

no alarm 25_Obstacle

no alarm no alarm 57_Smoke

23_Mecha-

nical fault

54_DPS

comm. err.

22_Mechanical

fault GF

unlocked/230V

failure

21_Door(SF)

missing

52_CAN err. 53_Manual

20_Door(GF)

missing

51_

brake/24V-SF

failure

19_SIS-SF

defective

DCU1-T30

expansion

Text 3 Text 4 Text 5 Text 6 Text 7 Text 8 Text 9 Text 10 Text 11 Text 12 Text 13 Text 14 Text 15

03_230V

failure

34_TPS

comm.

err.

Text 2 or

Active-Text

failure

cking door

system err.

Text 1 or

Inactive-Text

# Refe-

rence

Number

92 01_24V failure 02_12V

93 32_Sabotage 33_Interlo-

18_Bolt

signal not

correct

no alarm 50_Fault/

17_Err.

unlocking-GF

48_Excess

temperature-

GF(180deg)

Text16 Text17 Text18 Text19 Text20 Text21 Text22 Text23 Text24 Text25 Text26 Text27 Text28 Text29 Text30 Text31

# Refe-

(control) fault.-

rence

Number

92 16_Err.locking-

93 47_Tempsens

no alarm no alarm no alarm no alarm no alarm no alarm no alarm no alarm no alarm no alarm 90_control

79_Motor

relay-SF

temperature-SF

94 78_ Excess

GEZE IO 420

6.3 Service menu

Level 0 Level 1 Level 2 Level 3 Value range Factory setting

Select a module

Module conguration

Module type Watchdog

1-door solution (factory setting)

2-door solution Conf. output 3 disable

Conf. output 3 disable

Conf. output 4 disable

Conf. door 1 Conf. KZF 1 KZF 1duration

Conf. ZSU slave 1 ZSU slave size 1

Conf. ZSU interruption

Conf. output 4 disable

Conf. door 1 Conf. KZF 1 KZF 1duration

Conf. ZSU slave 1

Conf. ZSU interruption

Conf. door 2 Conf. KZF 2 KZF 2duration

Conf. ZSU slave 2 ZSU slave size 1

Conf. ZSU interruption

KZF 1abort KZF 1re-trigger

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

KZF 1abort ZSU slave size 1

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

KZF 2abort

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

1-door solution 2-door solution 4-door solution IQ lock EL + AUT Automatic stat Automatic 4 sec Window Universal RWS + KL400 DCU 1,2 and 8 DCU 6 DCU 128+RWS+KL

Alarm Door1 locked Door1 closed Door1 closed & locked

3~90 Yes/no Yes/no

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

Alarm Door1 locked Door1 closed Door1 closed & locked

3~90 Yes/no

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no no

3~90 Yes/no

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no no

1-door solution

disable

10 No No

No No No No No

disable

10 No

No No No No No

10 No

No No No No No

GEZE IO 420

4-door solution Conf. door 1 Conf. KZF 1 KZF 1duration

Conf. ZSU slave 1 ZSU slave size 1

Conf. ZSU interruption

Conf. door 2 Conf. KZF 2 KZF 2duration

Conf. ZSU slave 2 ZSU slave size 1

Conf. ZSU interruption

Conf. door 3 Conf. KZF 3 KZF 3duration

Conf. ZSU slave 3 ZSU slave size 1

Conf. ZSU interruption

Conf. door 4 Conf. KZF 4 KZF 4duration

Conf. ZSU slave 4 ZSU slave size 1

Conf. ZSU interruption

IQ lock EL + Aut Conf, inputs Input 1 AL unlocked

Conf. passive leaf IQ AUT

Conf. KZF 2 KZF1 duration

Conf. CP No CP

Automatic stat

KZF 1abort

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

KZF 2abort

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

KZF 3abort

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

KZF 4abort

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

Input 2 Release AL

Input 3 KZF AL and IL

Input 4 BMA

KZF1 abort

3~90 Yes/no

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

3~90 Yes/no

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

3~90 Yes/no

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

3~90 Yes/no

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

KZF AL and IL

AL closed BMA RWA

RWA IL closed KZF-AL (command)

No motor lock

3~90 Yes/no

One CP Two CPs DET short-circuited

10 No

No No No No No

10 No

No No No No No

10 No

No No No No No

10 No

No No No No No

Release AL

KZF AL and IL

BMA

IQ AUT

10 No

No CP

Automatic 4 sec

Window

GEZE IO 420

Universal Conf. relay 1 Conf. ZSU slave 1 ZSU slave size 1

Conf. ZSU interruption

Conf. relay 2 Conf. ZSU slave 2 ZSU slave size 1

Conf. ZSU interruption

Conf. relay 3 Conf. ZSU slave 3 ZSU slave size 1

Conf. ZSU interruption

Conf. relay 4 Conf. ZSU slave 4 ZSU slave size 1

Conf. ZSU interruption

Conf, inputs Input 1 Switch/ZSU master Switch

RWS + KL400

BusConf. Conf.BACnet MAC-Addr.

Device-ID Reboot BACnet Baud rate

Notication class

Conf.CAN auto. addr. as-

signm. 1st CAN-address:

2nd CAN-address: 3rd CAN-address:

(with 4-door sol.) 4th CAN-address:

(with 4-door sol.)

Conf.ZSU master ZSU master size 1 Enable ZSU1

ZSU1 start time ZSU1 start hour

ZSU1 end time ZSU1 end hour

ZSU1 weekday ZSU1 Sunday

ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5

Input 2 Switch/ZSU master Switch Input 3 Switch/BMA/RWA/

Input 4 Switch/BMA/RWA/

ZSU1 start minute

ZSU1 end minute

ZSU1 Monday ZSU1 Tuesday ZSU1 Wednesday ZSU1 Thursday ZSU1 Friday ZSU1 Saturday

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No

ZSU master

0~100 1 0~4194303 1 enter not enabled/ 9.6

KB/ 19.2 KB/ 38.4 KB/ 57.6 KB/ 76.8 KB/ 115.2 KB

1 ~ 90 50 enter

1~63 1 1~63 0 1~63 0

1~63 0

Yes/no No 0~23

0~59

0~23 0~59

Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no

No No No No No

Switch

76.8 KB

0 0

No No No No No No No

GEZE IO 420

ZSU master size 2 Enable ZSU2

ZSU2 start time ZSU2 start hour

ZSU2 end time ZSU2 end hour

ZSU2 Weekdays ZSU2 Sunday

ZSU master size 3 Enable ZSU3

ZSU3 start time ZSU3 start hour

ZSU3 end time ZSU3 end hour

ZSU3 Weekdays ZSU3 Sunday

ZSU master size 4 Enable ZSU4

ZSU4 start time ZSU4 start hour

ZSU4 end time ZSU4 end hour

ZSU4 Weekdays ZSU4 Sunday

ZSU master size 5 Enable ZSU5

ZSU5 start time ZSU5 start hour

ZSU5 end time ZSU5 end hour

ZSU5 Weekdays ZSU5 Sunday

Device conf. Date/time display

Change date Change year

Change time Hour

Conf. summer time Conf. language

Conf. log le

System info HW ver.:

Local time

Change month Change day

Minute Second

ZSU2 start minute

ZSU2 end minute

ZSU2 Monday ZSU2 Tuesday ZSU2 Wednesday ZSU2 Thursday ZSU2 Friday ZSU2 Saturday

ZSU3 start minute

ZSU3 end minute

ZSU3 Monday ZSU3 Tuesday ZSU3 Wednesday ZSU3 Thursday ZSU3 Friday ZSU3 Saturday

ZSU4 start minute

ZSU4 end minute

ZSU4 Monday ZSU4 Tuesday ZSU4 Wednesday ZSU4 Thursday ZSU4 Friday ZSU4 Saturday

ZSU5 start minute

ZSU5 end minute

ZSU5 Monday ZSU5 Tuesday ZSU5 Wednesday ZSU5 Thursday ZSU5 Friday ZSU5 Saturday

Yes/no No 0~23

0~59

0~23 0~59

Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No 0~23

0~59

0~23 0~59

Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No 0~23

0~59

0~23 0~59

Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no

Yes/no No 0~23

0~59 0~23

0~59

Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no Yes/no

10~99 1~12 1~31

0~23 0~59 0~59

Yes/no Yes German/English/

French Level 0 to level 2 Level 0

SW ver. : Ser.no. : Sys.err :

0 0

No No No No No No No

0 0

No No No No No No No

0 0

No No No No No No No

0 0

No No No No No No No

12 6 22

11 57 0

German

GEZE IO 420

Factory setting

Watchdog Conf. door 1 Conf. KZF 1 KZF1 duration 3~90 10

Alarm suppression 0~250 50

Alarm delay 0~250 100

Parameters SD card

Param. IO420 -> SD

Param. SD->IO420

BAC-Name IO420

-> SD BAC-Name SD-

>IO420

6.4 Passwords for BACnet

Password for DCC service in BACnet: GEZE Password for reinitialisation service (cold and warm start): GEZE-IO420

Reset parameter Reset BAC name Reset BAC description Reset all

KZF1 abort Yes/ No

KZF1 retrigger Yes/ No

7 Firmware update for IO 420

All settings are lost when the rmware is updated.

Backup

Back up the name le “IO420_V1.BAC” to the SD card.

Conguration le: Back up “IO420_V1.CON” to the SD card.

The backed-up data may no longer be compatible after rmware conversion, but they can be adapted manually. Further information on this subject can be found in the respective information sheet. The object descriptions cannot be backed up and must be entered again manually.

Firmware update

Firmware updates are provided by GEZE in electronic form.

Copy the .hex le to the directory “../FlashData/IO420”.

Open “IO420_Flasher.bat” using the text editor. If the les reference is “IO420_V1.hex”, it must be changed to “IO420_V1”. CORRECT: “..\Flasher\STM32\ProgSTM32Pfs.bat 11 ..\FlashData\IO420\IO420_V1”

Save le.

Switch o the voltage supply for the IO 420.

Connect the adapter cable (mat.no.: 130829) to the IO 420.

GEZE IO 420

Fig. 5: Programming adapter cable

Switch on the voltage supply for the IO 420.

Execute “IO420_Flasher.bat”.

If the following error message appears, proceed as follows:

Fig. 6: Error “wrong COM port”

Adapt COM port in le “IO420_Flasher.bat”.

WRONG: ..\Flasher\STM32\ProgSTM32Pfs.bat 11 ..\FlashData\IO420\IO420_V1 CORRECT ..\Flasher\STM32\ProgSTM32Pfs.bat 3 ..\FlashData\IO420\IO420_V1

GEZE IO 420

Fig. 7: COM port setting in the device manager

Execute “IO420_Flasher.bat” again. The update progress is displayed in the window. The process takes several minutes.

Fig. 8: Software update in progress.

Switch o the voltage supply, unplug the cable.

Re-boot IO 420.

After the rmware update the IO 420 must be reset to factory settings.

Germany

GEZE GmbH Niederlassung Süd-West Tel. +49 (0) 7152 203 594 E-Mail: leonberg.de@geze.com

GEZE GmbH Niederlassung Süd-Ost Tel. +49 (0) 7152 203 6440 E-Mail: muenchen.de@geze.com

GEZE GmbH Niederlassung Ost Tel. +49 (0) 7152 203 6840 E-Mail: berlin.de@geze.com

GEZE GmbH Niederlassung Mitte/Luxemburg Tel. +49 (0) 7152 203 6888 E-Mail: frankfurt.de@geze.com

GEZE GmbH Niederlassung West Tel. +49 (0) 7152 203 6770 E-Mail: duesseldorf.de@geze.com

GEZE GmbH Niederlassung Nord Tel. +49 (0) 7152 203 6600 E-Mail: hamburg.de@geze.com

GEZE Service GmbH Tel. +49 (0) 1802 923392 E-Mail: service-info.de@geze.com

Austria

GEZE Austria E-Mail: austria.at@geze.com www.geze.at

Baltic States

GEZE GmbH Baltic States oce E-Mail: oce-latvia@geze.com www.geze.com

Benelux

GEZE Benelux B.V. E-Mail: benelux.nl@geze.com www.geze.be www.geze.nl

Bulgaria

GEZE Bulgaria - Trade E-Mail: oce-bulgaria@geze.com www.geze.bg

China

GEZE Industries (Tianjin) Co., Ltd. E-Mail: chinasales@geze.com.cn www.geze.com.cn

GEZE Industries (Tianjin) Co., Ltd. Branch Oce Shanghai E-Mail: chinasales@geze.com.cn www.geze.com.cn

GEZE Industries (Tianjin) Co., Ltd. Branch Oce Guangzhou E-Mail: chinasales@geze.com.cn www.geze.com.cn

GEZE Industries (Tianjin) Co., Ltd. Branch Oce Beijing E-Mail: chinasales@geze.com.cn www.geze.com.cn

France

GEZE France S.A.R.L. E-Mail: france.fr@geze.com www.geze.fr

Hungary

GEZE Hungary Kft. E-Mail: oce-hungary@geze.com www.geze.hu

Iberia

GEZE Iberia S.R.L. E-Mail: info@geze.es www.geze.es

India

GEZE India Private Ltd. E-Mail: oce-india@geze.com www.geze.in

Italy

GEZE Italia S.r.l E-Mail: italia.it@geze.com www.geze.it

GEZE Engineering Roma S.r.l E-Mail: roma@geze.biz www.geze.it

Poland

GEZE Polska Sp.z o.o. E-Mail: geze.pl@geze.com www.geze.pl

Romania

GEZE Romania S.R.L. E-Mail: oce-romania@geze.com www.geze.ro

Russia

OOO GEZE RUS E-Mail: oce-russia@geze.com www.geze.ru

Scandinavia – Sweden

GEZE Scandinavia AB E-Mail: sverige.se@geze.com www.geze.se

Scandinavia – Norway

GEZE Scandinavia AB avd. Norge E-Mail: norge.se@geze.com

www.geze.no

Scandinavia – Denmark

GEZE Danmark E-Mail: danmark.se@geze.com www.geze.dk

Singapore

GEZE (Asia Pacic) Pte, Ltd. E-Mail: gezesea@geze.com.sg www.geze.com

South Africa

GEZE Distributors (Pty) Ltd. E-Mail: info@gezesa.co.za www.geze.co.za

Switzerland

GEZE Schweiz AG E-Mail: schweiz.ch@geze.com www.geze.ch

Turkey

GEZE Kapı ve Pencere Sistemleri E-Mail: oce-turkey@geze.com www.geze.com

Ukraine

LLC GEZE Ukraine E-Mail: oce-ukraine@geze.com www.geze.ua

United Arab Emirates/GCC

GEZE Middle East E-Mail: gezeme@geze.com www.geze.ae

United Kingdom

GEZE UK Ltd. E-Mail: info.uk@geze.com www.geze.com

GEZE GmbH

Reinhold-Vöster-Straße 21–29 71229 Leonberg Germany

Tel.: 0049 7152 203 0 Fax.: 0049 7152 203 310

www.geze.com

GEZE IO 420 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual