GEZE IO 420 Скачать руководство пользователя страница 5

  

GEZE IO 420

GEZE IO 420

9

 

 

8

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

Parameter setting GEZE IO 420

The first time parameters are set for the IO 420, the GEZE service terminal ST 220 should always be used. Once 

entered, the configuration file 

“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 profile to another IO 420 with the same firmware. 

     

If the LED for microSD card is flashing, 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 configuration file is modified 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 notification class object.

8.VALUE_UTC_OFFSET(0~780)

=

60;

UTC time offset in minutes; amount shown without sign (e.g. EN = 60 min.)

9.SIGN_UTC_OFFSET(1:-/0:+)   

=

1;

Sign for UTC offset.

1 : negative offset

0: positive offset  

Offset = [UTC] - [local time], which is why Germany has a negative value.

10.CONF_OUTPUT3(0~4)

11.CONF_OUTPUT4(0~4)

=

=

0;

0;

Configuration 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 (electric strike)

6: RWA (electric strike)

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

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~15)

=

10;

1: Watchdog

2: One-door solution

3: Two-door solution

4: Four-door solution

5: IQ Lock EL + AUT

6: IQ Lock 72 + AUT (from software version 

2)

7: Automatic stat.

8: Automatic 4Sec

9: Window

10: Universal

11: RWS + KL400

12: DCU 1, 2 or 8

13: DCU 6 revolving door

14: DCU 1, 2 or 8 + RWS + KL400

15: MBZ300 smoke and heat extraction 

system

33.LOGFILE_LEVEL(0~2)

=

0;

0: Level 0. No protocol is written in the log file 

1: Level 1. Alarm messages are written in the log file

2: Level 2. Alarm messages and actions are written in the log file

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

Specification of “hours” 0-23; specification of “minutes” 0-59

44.ZSUMASTER1_END_HH(0~23)   

45.ZSUMASTER1_END_MM(0~59)   

=

=

0;

0;

End time “ZSU master group 1”

Specification of “hours” 0-23; specification 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 configuration “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”

Specification of “hours” 0-23; specification of “minutes” 0-59

56.ZSUMASTER2_END_HH(0~23)   

57.ZSUMASTER2_END_MM(0~59)   

=

=

0;

0;

End time “ZSU master group 2”

Specification of “hours” 0-23; specification 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 configuration “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”

Specification of “hours” 0-23; specification of “minutes” 0-59

68.ZSUMASTER3_END_HH(0~23)   

69.ZSUMASTER3_END_MM(0~59)   

=

=

0;

0;

End time “ZSU master group 3”

Specification of “hours” 0-23; specification 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

8

 

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

=xxxyyy;       

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

Der Titelteil einschließlich dem 

„=“ 

Zeichen darf nicht geändert werden. Das 

„=“

 fungiert hier als Trennzeichen 

zwischen Titel und BACnet-Namen. Der Namen der einzelnen BACnet-Objekte darf geändert werden. Hierbei gilt 

zu beachten, dass die Zeile mit einem Semikolon „;“ endet und der Name nicht mehr als 32 Zeichen enthält. Die 

Verwendung von Sonderzeichen ist nicht erlaubt, ausgenommen Leerzeichen, Unterstrich, Bindestrich, Punkt 

und Komma.

Parametrierung GEZE IO 420

Die erste Parametrierung des IO 420 sollte grundsätzlich mit Hilfe des GEZE Serviceterminals ST 220 erfolgen. Ein-

mal eingestellt kann die Konfigurationsdatei 

„IO420_V1.CON“

 

auf eine microSD-Card kopiert und gegebenenfalls 

am PC weiter angepasst werden. Das so erstellte Profil kann dann mittels microSD-Card auf ein anderes IO 420 

mit gleicher Firmware geladen werden. 

     

Wenn die LED für microSD-Card blinkt, darf die microSD-Card nicht aus dem Slot herausgenommen werden. 

Zum Entfernen und Einstecken der microSD-Card das IO 420 spannungslos schalten. 

Bei der Modifizierung der Konfigurationsdatei am PC sind folgende Punkte zu beachten:

 

à

Der Parametername einschließlich dem „=“ Zeichen darf nicht geändert werden. Das „=“ fungiert hier als 

Trennzeichen zwischen Titelteil und Wert. 

 

à

Der Parameter-Wert darf nur Zahlen enthalten.

 

à

Die in den Klammern Angegebenen min./max. Werte beachten. 

Parametername 

Wert Beschreibung

0.CAN_ADDR1(0~63)

=

1;

CAN-Adresse für Tür #1

1.CAN_ADDR2(0~63)

=

0;

CAN-Adresse für Tür #2

2.CAN_ADDR3(0~63)

=

0;

CAN-Adresse für Tür #3

3.CAN_ADDR4(0~63)

=

0;

CAN-Adresse für Tür #4

4.BACNET_MACADR(0~127)

=

1;

BACnet MAC-Adresse

5.BACNET_DEVICEID(1~4194303) 

=

1;

BACnet DEVICE -ID

6.BACNET_BAUDRATE(0~6)       

=

5;

0 = nicht aktiv  

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;

Instanznummer des Notification class object.

8.VALUE_UTC_OFFSET(0~780)

=

60;

UTC-Zeit offset in Minuten; Betragswert ohne Vorzeichen; (z. B. DE = 60 Min.)

9.SIGN_UTC_OFFSET(1:-/0:+)   

=

1;

Vorzeichen für UTC-Offset.

1 : negativer Offset

0: positiver Offset  

Offset = [UTC] - [local time], daher hat Deutschland einen negativen Wert.

10.CONF_OUTPUT3(0~4)

11.CONF_OUTPUT4(0~4)

=

=

0;

0;

Konfiguration von Ausgang 3 und 4 bei Türlösung
0: Ausgang inaktiv

1: Alarm

2: Verriegelt

3: Geschlossen

4: Verriegelt und Geschlossen.

12.INPUT1_TYPE(0~10)

13.INPUT2_TYPE(0~10)

14.INPUT3_TYPE(0~12)

15.INPUT4_TYPE(0~12)

=

=

=

=

10;

10;

10;

10;

Der gültige Wertbereich für den jeweiligen Eingang ist je nach Modultyp anders.  

Die folgende Liste dient zu Entschlüsselung der Nummern. Die Änderung der 

Eingänge muss über das GEZE Serviceterminal ST 220 erfolgen.
0: inaktiv

1: Gangflügel entriegelt

2: Gangflügel-entriegeln (Befehl)

3: KZF-GF und SF (Befehle)

4: Gangflügel geschlossen

5: BMA (Öffner)

6: RWA (Öffner)

7: Standflügel geschlossen

8: KZF-GF (Befehl)

9: ZSU-Master

10: Schalter-Funktion

11: BMA für Universalmodul (Schließer)

12: RWA für Universalmodul (Schließer)

16.KZF1_ABORT(0/1)

=

0;

0: Kurzzeitfreigabe Tür  #1 ist nicht unterbrechbar

1: Kurzzeitfreigabe Tür  #1 ist unterbrechbar

17.KZF1_AFTERTRG(0/1)

=

0;

0: Kurzzeitfreigabe Tür  #1 kann nicht nachgetriggert werden

1: Kurzzeitfreigabe Tür  #1 kann nachgetriggert werden

18.KZF1_TIME(3~30)

=

10;

Kurzzeitfreigabezeit Tür  #1 (3 bis 30 Sekunden)   

19.KZF2_ABORT(0/1)

=

0;

0: Kurzzeitfreigabe Tür  #2 ist nicht unterbrechbar

1: Kurzzeitfreigabe Tür  #2 ist unterbrechbar

Содержание IO 420

Страница 1: ...IO 420 164898 04 EN User manual IO 420 161864 03 DE Benutzerhandbuch...

Страница 2: ...iese Warnhinweise immer X Befolgen Sie alle Ma nahmen die mit dem Warnsymbol und Warnwort gekennzeichnet sind Warnsymbol Warnwort Bedeutung VORSICHT Informationen zur Vermeidung von Sachsch den zum Ve...

Страница 3: ...0 erf llt folgende Normen DIN EN 61000 6 2 2005 entsprechend VDE 0839 Teil 6 2 M rz 2006 DIN EN 61000 6 6 2007 A1 2011 entsprechend VDE 0839 Teil 6 3 September 2011 3 Produkt bersicht Montagehinweise...

Страница 4: ...microSD Card gelesen oder geschrieben wird LED 2 gelb LED leuchtet wenn CP Kondensatorplatine angeschlossen ist LED 3 rot LED blinkt bei St rung LED 4 gr n LED blinkt im normalen Betrieb LED 5 gr n LE...

Страница 5: ...SDAY 0 1 40 ZSUMASTER1_FRIDAY 0 1 41 ZSUMASTER1_SATURDAY 0 1 0 0 0 0 0 0 0 Day configuration ZSU master group 1 0 as ZSU master group 1 inactive on this day of the week 1 as ZSU master group 1 active...

Страница 6: ..._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...

Страница 7: ...longer enabled Time switch interruption If time switch interruptible is enabled in the IO 420 configuration the time switch state can be interrupted using the lock command The state then changes to l...

Страница 8: ...atic 4 sec is enabled output 3 is switched off again after 4 seconds night falling flank input 1 CAN command night BACnet command night shop closed CAN command close shop BACnet command close shop per...

Страница 9: ...Die Verwendung von Sonderzeichen ist nicht erlaubt ausgenommen Leerzeichen Unterstrich Bindestrich Punkt und Komma 4 Parametrierung GEZE IO 420 Die erste Parametrierung des IO 420 sollte grunds tzlich...

Страница 10: ...rminal 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 configuration for the fi...

Страница 11: ...e 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...

Страница 12: ...sind folgende Punkte zu beachten Der Parametername einschlie lich dem Zeichen darf nicht ge ndert werden Das fungiert hier als Trennzeichen zwischen Titelteil und Wert Der Parameter Wert darf nur Zah...

Страница 13: ...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...

Страница 14: ...d 1 19 4 1 1 3 Y Y 66 6 1 9 module type window Mandatory Optional Keyname Objectname device obj Inst object type object inst present value default min present value max present value command able supp...

Страница 15: ...N 4 door_state_DCU_SF 3 4 N N 4 Device_IO420 8 1 N N notification_class_obj 15 50 N N module_type 19 1 1 13 N N 1 Alarm_TZ 19 2 1 15 N N 6 50 operating_mode_DCU 19 3 1 14 N N 84 mode_command 19 4 1 1...

Страница 16: ...alarm de layed alarm active 61 automatic night shop close permanently open 62 night day release short time release 63 no command unlock lock short time release 66 enable watchdog disable watchdog shor...

Страница 17: ...unlocked 230V failure 54_DPS comm err unknown error unknown error 57_Smoke alarm SF unknown error unknown error 60_Err in control unit GF 61_Battery flat no error 94 78_Excess temperature SF 79_Motor...

Страница 18: ...4 sec Window Universal Conf relay 1 Conf ZSU slave 1 ZSU slave size 1 ZSU slave size 2 ZSU slave size 3 ZSU slave size 4 ZSU slave size 5 Yes no Yes no Yes no Yes no Yes no No No No No No Conf ZSU int...

Страница 19: ...on 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 file to the directory Flas...

Страница 20: ...2Pfs bat 11 FlashData IO420 IO420_V1 RICHTIG Flasher STM32 ProgSTM32Pfs bat 3 FlashData IO420 IO420_V1 GEZE IO 420 35 Abb 7 COM Port Einstellung im Ger te Manager X Datei IO420_Flasher bat erneut ausf...

Страница 21: ...nce fr geze com www geze fr Hungary GEZE Hungary Kft E Mail office hungary geze com www geze hu Iberia GEZE Iberia S R L E Mail info es geze com www geze es India GEZE India Private Ltd E Mail office...

Отзывы: