Search filter
Filter
Reset- Installation drawing (1034)
- Product data sheet (926)
- Installation instructions (314)
- Tender texts (257)
- 3D model (175)
- Product scale drawing (163)
- Certificate (126)
- Declaration of conformity (108)
- Declarations of performance (90)
- Cable plan (76)
- Wiring diagram (46)
- Environmental declaration (43)
- Product brochure (38)
- User manual (37)
- Flyer/folder (33)
- Supplementary sheet (30)
- Declaration of incorporation (23)
- Type examination certificate (13)
- Inspection certificate (11)
- T&C / Data Protection (9)
- Software (6)
- Customer information (6)
- Supplier information (4)
- Errors/Measures (3)
- Safety analysis (2)
- Installation situation (1)
- Evaluation/comment (1)
3575 results found
myGEZE Control Building automation and control system General information • Hardware components • Software • myGEZE Control Configurator • Config-files • Commissioning a controller system 207493-01 12/2023 EN User manual myGEZE Control Contents … Introduction … Symbols and illustrations … Reference documents … 2 Safety … Safety notes … Intended use … 3 Functions and properties … Modular principle … Control unit components … Power supply (depending on the version) … Terminals … Standard control units … Distributor … 4 Installation … Equipment and configuration of the control unit … Space required for the bus terminals and components on the top hat rail (width) … 10 Layout of the terminals on the top hat rail … 11 Changing the module configuration/system state … 11 Approved type of installation / minimum distances … 12 Installation / removal … 13 Wiring … 14 … Connection of the control unit … 15 Mains connection … 15 … Connecting external components … 15 … Hardware description … 16 … myGEZE Control CPU MODULE 8191 … 16 … myGEZE Control CAN MASTER TERMINAL … 19 … myGEZE Control CAN connector … 21 … myGEZE Control KNX-System … 23 … myGEZE Control 8-channel digital input terminal … 28 … myGEZE Control potential distribution terminal 24 V DC … 30 … myGEZE Control potential distribution terminal … V DC … 31 … myGEZE Control output terminal 2-channel relay … 32 … myGEZE Control output terminal 4-channel relay … 34 … myGEZE Control power supply terminal … 36 … myGEZE Control coupler … 37 … myGEZE Control extension … 38 … myGEZE Control 2-port junction … 39 … myGEZE Control bus end cover … 40 … Terminal name with myGEZE Control assignment to Beckhoff … 40 Introduction myGEZE Control … System structure and system limits … 41 … Max. possible terminals in the template project … 41 … Technically possible order of terminals in the template project … 42 … System limits … 43 … Substations … 43 … Detached inputs and outputs with GEZE IO 420 … 44 … Determination of the necessary hardware components … 44 … Electrical wiring diagram … 44 … Licence model … 45 … Putting the software into operation … 46 … Basic information about Beckhoff and TwinCAT … 46 … myGEZE Control Configurator … 47 Introduction … 47 Overview … 47 Installation … 68 Updating … 68 Deinstallation … 68 … Preparations for a new controller … 69 Settings that are set with this image … 69 Preparations … 70 … Preparing an application for a project … 74 IP addresses and BACnet settings of the controller … 74 Loading a GEZE project … 75 Preparing TwinCAT project … 75 … Checking BACnet objects and generating BACnet-EDE file with TwinCAT … 83 Checking BACnet objects … 83 Generating BACnet-EDE file … 85 … Expanded BACnet settings in TwinCAT … 87 Assigning the BACnet device instance using the myGEZE Control Configurator … 87 Setting the BACnet UDP port … 88 Setting the BACnet Broadcast Management Device BBMD … 90 … CAN monitor application … 92 … Transportation and storage … 99 … Disposal … 100 10 Technical data … 101 11 List of figures … 102 … Introduction … myGEZE Control Introduction … Symbols and illustrations Warning notices In these instructions, warning notices are used to warn against material damage and injuries. Always read and observe these warning notices. Observe all the measures that are marked with the warning symbol and signal word. Warning symbol Warning Meaning DANGER Danger to persons. Non-compliance will result in death or serious injuries. WARNING Danger to persons. Non-compliance can result in death or serious injuries. CAUTION Danger to persons. Non-compliance can result in minor injuries. Further symbols and means of representation Important information and technical notes are highlighted to explain correct operation. Symbol Meaning means “important note” Information to prevent property damage, to understand or optimise the operation sequences. means "additional information" … Reference documents Type Description Name myGEZE Control-BACnet module types data points Material no. 207847 … Safety … myGEZE Control Safety … Safety notes The details in this description always refer to the factory standard configurations. Changes to the software configuration of the control unit can only be made by trained GEZE specialised personnel. No warranty claims may be made against the manufacturer or distributor of the control unit for damage that is due to interventions in the control unit which are not authorised by the manufacturer or its distributor. The details in these instructions must be observed when connecting components. Planning and calculation of the power network is to be done by an installer and has to be carried out in accordance with the statutory regulations (in Germany for example in accordance with MLAR). Before the system is released for operation, an insulation measurement of the system's line network must be performed and logged. Contact GEZE if support is needed for planning and system set-up. The information is subject to permanent technical development. It is possible that the descriptions and drawings shown do not always correspond to the current status. For this reason, the current information must always be obtained from the manufacturer. These instructions must be followed to ensure personal safety. Immediately resolve any system faults. Always keep the installation instructions on hand near the control unit (e.g. in a plastic sleeve directly on the front door) Obligations of the operator Secure workplace against unauthorised entry. Installation, commissioning and maintenance may only carried out by qualified personnel authorised by GEZE. If unauthorised changes are made to the system, GEZE cannot be made liable in any way whatsoever for any resulting damages. Only provide the control cabinet key to trained personnel. Electrical system Before working on the electrical system, interrupt the power supply (mains and rechargeable battery) and verify the safe isolation from supply. The connection to the mains voltage must be performed by a qualified electrician. The power connection and protective earth conductor test must be carried out in accordance with DIN VDE 0100-600. Work may only be carried out by a qualified electrician or a “qualified electrician for restricted work”. An on-site, 2-pole miniature circuit breaker with locking option is to be used as a line-side disconnecting device, in accordance with the permissible cable current load. Live parts are exposed after the system housing has been opened. The system must be disconnected from the supply voltage before any intervention in the control unit. The connecting terminals for system components in parts have a low voltage of ≤50 V. Only switch mains voltage on after connection of all the system components. Protect the control unit against unauthorised access and prevent the unit from being opened. Use only the cables specified on the cable plan provided. Cables must be shielded in compliance with the wiring diagram. Determine cable types (e.g. fire protection cable) and the required IP rating in agreement with the local official approval authority. Insulate wires that are not used. Secure loose cables with cable ties. … Safety myGEZE Control Maintenance A safety-related test with maintenance has to be carried out by a GEZE-authorised specialist as required. You will receive written verification about the check. Spare parts GEZE does not accept any warranty for combinations with third-party products. Use only original GEZE parts for repair and maintenance work. Regulations and standards Warranty claims require assembly, installation and service to be performed by a specialist company according to the manufacturer's specifications. The owner-operator and/or installer commissioned by the owner-operator must observe all relevant legal regulations and have been briefed on proper operation. Perform system maintenance according to legal regulations. Observe the maintenance specifications. Observe the latest versions of guidelines, standards and country-specific regulations, in particular: DIN VDE 0100-600 “Setting up low-voltage systems” DIN EN 60335-2-103 “Household and similar electrical appliances - Safety; Particular requirements for drives for gates, doors and windows” Accident prevention regulations, especially DGUV regulation … “Accident prevention regulation, principles of prevention” and DGUV regulation … “Accident prevention regulation, electrical installations and equipment” VDE 0815 “Installation cables and lines for remote and information processing systems” MLAR “Model Guideline for Line Systems” … Intended use The building automation and control system realises networking solutions. The networking control unit complies with recognised engineering practice and conforms to the applicable safety regulations. The system is designed solely for use in dry rooms. … Functions and properties … myGEZE Control Functions and properties myGEZE Control is the central controller system to which the field products can be connected. The building automation and control system is used for connecting control units for emergency exits, electric locks, automatic door systems, smoke and heat extraction systems and automatic window systems as well as devices from adjacent product groups for use in building management and physical security information management systems. Typical applications include: Using data concerning product statuses, events and error messages in other systems via BACnet/IP Operation of the connected field level devices via software applications the possibility of evaluating building management systems data For integration in building management systems, the field level devices must be connected via interface modules to a building automation controller, and the data that is needed for their integration must be provided via specific configuration files. If a housing has been commissioned from GEZE, then all units will be in a lockable housing made of painted steel sheet (RAL 7035) with a seal insert with an IP rating of IP 30. The housing dimensions depend on the version and equipment of the control unit. … Modular principle Hardware configuration The terminals are installed on a standard top hat rail (TS 35). The basic controller recognises the bus terminals connected to the system. These have to match the software configuration Software configuration The basic controller recognises the bus terminals connected to the system. These have to match the software configuration … Control unit components Power supply (depending on the version) 1x power supply ( … A-24 V DC) (standard equipment) 1x miniature circuit breaker B10 1x set of terminals for connection of the mains voltage 230 V AC 2x fuse terminals 24 V DC (4 A) for protection of the controller system + terminals Optional: Power supply (10 A-24 V DC) (special equipment for control cabinet size 4) Terminals Basic controller Powerful embedded PC / control unit with a switched Ethernet port which supports the BACnet protocol. Bus terminals for communication with GEZE bus: The terminal enables integration of the GEZE field products which have a GEZE bus connection in the terminal network. Up to … x GEZE bus terminals can be installed. … Functions and properties myGEZE Control Bus terminals for communication with KNX: … EIB/KNX bus terminals are required for connection of the GEZE window technology modules IQ box KNX. One for receiving, one for transmitting. The number of maximum possible group addresses in the application is only limited by the max. number of IQ box KNX that can be connected. Digital input terminals: For the detection of potential-free binary status signals from the products connected Digital output terminals: For switching binary control signals to the products connected Available as relay output Variants with … or … channels and normally open or change-over contact available Auxiliary terminals: As a connection point for e.g. reference potential or tapping 24V DC For internal functions e.g. refreshing bus signal or coupling terminals Bus end covers: Every assembly must be completed by a bus end cover fitted on the right-hand side. … Standard control units The following standard control units are available: myGEZE Control standard control units … 2 Control cabinet size W x H x D [mm] Mat. No. … 4 300 × 400 × 200 400 × 500 × 200 600 × 600 × 250 600 × 800 × 250 203991 203992 203993 203995 15 25 40 Spaces for additional terminals (in addition to the basic controller) 10 Extension options: Installation of a larger power supply is possible in the standard control unit size … in order to supply the components accordingly. … Distributor The distribution cabinet offers the option of distributing networking technology decentrally throughout the building. Multiple distributors can be positioned in a project, for instance locally on a door system or in another sub-distributor. The local cables can then be connected there. A bus connection is used for communication with the basic device. The following distributor is available: Standard distributor for myGEZE Control … 361 x 254 x 165 Size W x H x D [mm] Mat. No. Spaces for additional terminals (in addition to the basic controller or coupling terminal) 203996 10 The distribution cabinet can also be used for the installation of other / further electrical components e.g. installation of external input and output couplers. A distribution cabinet can also be used to install a basic device for small-scale applications. … Installation … myGEZE Control Installation Installation sequence (overview) Before starting work check the delivery slip to ensure the delivery is complete and correct (control unit size, terminals etc.). Later complaints will not be accepted. Have assistants hold the control cabinet while screwing in place. Check the equipment configuration of the control unit and adapt/supplement if necessary. Attach housing securely and keep easily accessible for servicing etc. Mark fixing holes. Select suitable fasteners for the substrate. Screw the control cabinet in place. Screw the control unit in place. Cut off the graduated nipples in accordance with the cable diameter. Route the cables through the graduated nipples into the control unit. Connect external components in accordance with wiring diagram. Connect mains power supply. Put the system into operation. … Equipment and configuration of the control unit Minimum and maximum equipment The minimum equipment comprises power supply, 1x basic controller, 1x bus terminal depending on the function to be performed and a bus end cover to protect the electrical contacts. The housing size depends on the number and layout of the bus terminals. The maximum layout can contain up to 40 terminals. Control cabinet size … must used in this case. … Installation myGEZE Control Space required for the bus terminals and components on the top hat rail (width) Controllers / terminals Basic controller 71 mm Bus terminals for communication with GEZE CAN-bus: 24 mm Bus terminals for communication with IQ box KNX: … x 12 mm + 1x 12 mm for couplers + 1x 12 mm for end terminals Digital input terminals: 12 mm Digital output terminals: 12 mm Auxiliary terminals: 12 mm Bus end covers: 6/12 mm Fig. 1: Mounted terminals Power supply (standard equipment) Fig. 2: Standard power supply The power supply is located on a separate top hat rail. 10 Installation myGEZE Control Layout of the terminals on the top hat rail It is imperative that the terminal layout on the top hat rail is observed. It is also precisely defined in the project-specific electric wiring diagram. For further information, see … Technically possible order of terminals in the template project, on page 42. Potential sequence: Place the terminals on the top hat rail in the following order directly next to each other (from left to right): Basic controller Input and output terminals Auxiliary terminals (if any) Bus terminals for communication with GEZE CAN-bus Coupler (if installed for KNX connection) Bus terminals for communication with KNX (if installed for KNX connection) Bus end terminal (if no internal couplers + KNX terminals installed) Changing the module configuration/system state If changes are made to the module configuration (number, type and order of the terminals), this must be adapted in the software configuration. If the hardware configuration does not match the software configuration, the system does not enter runtime mode after start and ramp-up phase. Depending on the false configuration, the system remains in configuration mode (blue status LED) or error (red status LED). A correct system state in run mode can be seen on the basis of the green status LED. Only connect or disconnect the terminals in a de-energised state. Switch the mains voltage off first. 11 Installation myGEZE Control Approved type of installation / minimum distances … . … Prescribed installation positions for temperatures up to 60°C Mount the embedded PC horizontally in the control cabinet on a carrier rail so that the heat is discharged optimally. The ventilation options are on the underside and top of the housing. This will ensure an optimum air flow vertically through the embedded PC. In addition, a clearance of at least 30 mm above and below the embedded PC is required to ensure sufficient ventilation. Fig. 3: Type of installation at temperatures up to 60°C. 12 Installation myGEZE Control Installation / removal … . … Installation and removal - lever release of the terminals The terminal modules are mounted on top hat rails (35 mm) in accordance with EN 60715. Installation Fig. 4: Installation Disassembly Fig. 5: Disassembly Each terminal is secured by a locking mechanism on the top hat rail which must be released for removal: Pull the terminal by its orange-coloured tabs approx. … cm down from the top hat rail. This automatically releases the top hat rail locking mechanism of this terminal and you can now pull the terminal out of the bus terminal block without having to apply a great deal of force. To do this, grip the unlocked terminal with your thumb and index finger at the top and bottom of the housing areas of the same time and pull it out of the bus terminal block. 13 Installation myGEZE Control Wiring Fig. 6: Wiring Up to eight terminal points make the connection of solid or finely stranded cables possible on the bus terminal. The terminal points use spring-loaded technology. Connect the cables as follows: Open a terminal point by pressing a screwdriver straight up to the stop into the square opening above the terminal point. Do not turn the screwdriver, move it back and forth, or lever it. Use a size … screwdriver. The wire can now be inserted without resistance into the round terminal opening. Reducing the pressure closes the terminal point automatically and causes it to hold the wire securely and permanently. Terminal housing Input terminal Cable cross-section (solid) Cable cross-section (finely stranded) Cable cross-section (single-core cable with wire end ferrule) Stripping length … mm² … mm² … mm² 8…9 mm 14 Installation myGEZE Control … Connection of the control unit Mains connection Once all the components have been connected and configured and the connections checked, the mains voltage can be connected by a qualified electrician. WARNING! Risk of fatal injury due to electric shock! Switch off the power feed and ensure it is not switched back on before connecting the power supply. Ensure the on-site power supply circuit is de-energised. Connect the 230 V AC on-site power supply circuit to the mains connection terminals of the SHEV control panel. Cable cross-section connection line: … mm² … mm² … 2 … L N PE … Connecting external components The external components may only be connected to the system in accordance with the enclosed electric circuit. The system must be de-energised by releasing the on-site disconnector before any connection work is performed. Ensure isolation from supply in the control cabinet. Basic controllers have a system-internal 1-second UPS to backup persistent data. In other words, when the power supply has been switched off, the system requires approx. … to … seconds before it is finally shutdown, depending on structure and thus capacity utilisation. The electrical installation must be carried out in accordance with the applicable regulations and guidelines. 15 Hardware description … myGEZE Control Hardware description … myGEZE Control CPU MODULE 8191 Fig. 7: myGEZE Control CPU MODULE 8191 Ethernet port Link/Act Ethernet RJ45 (switched) Link/Act Ethernet RJ45 (switched) Address selection switch/DIP switch The DIP switch can be used to set the IP address for the switched Ethernet interfaces X101/X102. Power LEDs Diagnosis of the power supply for embedded PC and terminal bus. Status of E-bus and K-bus communication. E-bus or K-bus Supply coupler Front flap (the battery compartment and microSD card slot are under this flap) Power supply for the battery-buffered clock for time and date. Power contact feed Power contacts, +24 V, … V, PE Power contacts for bus terminals. 16 Hardware description myGEZE Control The CPU 8191 is a control unit with a switched Ethernet port which supports the BACnet protocol. Either Ebus or K-bus terminals can be mounted side by side, the CPU 8191 recognises automatically during booting which system is connected. The control unit is programmed using TwinCAT … via the Ethernet interface. Diagnosis LEDs Display LED Meaning TC TwinCAT status-LED TwinCAT is in run mode (green) TwinCAT is in stop mode (red) TwinCAT is in config mode (blue) No function ex works. The LED can be configured for application-specific diagnostic messages. WD ERR Lights up red following switch-on. Software is being loaded. Goes out when everything is OK. Parameters can be set for the LED for application-specific diagnosis messages. Parameters can be set for the LED for application-specific diagnosis messages. Reset button You can activate config mode using the reset button. You can use this function if the PLC program unintentionally causes an error. You have to keep the reset button pressed for a longer time during the restart for this. Enable config mode as follows: Open the front flap. Switch off the embedded PC. Start the embedded PC and hold the reset button down until the ERR LED lights up red and then yellow. This puts the basic controller in config mode. You can no longer activate the device without a programming device with the software TwinCAT … in an appropriate version. Setting the IP address with DIP switches You can only use the DIP switches S101 to set the IP address for the switched Ethernet interfaces X101/ X102. The DIP switches have no meaning for the Ethernet interface X001. 17 Hardware description myGEZE Control Fig. 8: DIP switch S101, switches … to 10. Switch right-hand position: on “1”. Switch left-hand position: off “0”. You can edit the last byte of the IP address using DIP switches … to 8. The DIP switches take priority over the settings in the operating system. Changes are only applied after the embedded PC has been restarted. DIP switch S101 10 on and … off Meaning DHCP active. Default setting ex works. The DIP switches … to … then have no meaning. 10 off and … off DHCP inactive. By default, the fixed IP address … .1.xxx and the subnet mask … . … are used. The last byte of the IP address … .1.xxx is edited using DIP switches … to 8. The complete IP address is adopted from the operating system or the web interface (Beckhoff Device Manager) 10 off and … off … to … all on Example If you wish to set the IP address … .1. 67 for Ethernet interface X101/X102 with the DIP switches, you must configure the DIP switches as follows: DIP1 on DIP2 on DIP3 off DIP4 off DIP5 off DIP6 off DIP7 on DIP8 off DIP9 off DIP10 off The value for the last byte of the IP address then results from the DIP switches switched on. 20 + 21 + 26 = 67 Values for the individual DIP switches: Value DIP1 20 DIP2 21 DIP3 22 DIP4 23 DIP5 24 DIP6 25 DIP7 26 DIP8 27 18 Hardware description myGEZE Control … myGEZE Control CAN MASTER TERMINAL Fig. … : myGEZE Control CAN MASTER TERMINAL LED Run LED CAN Error LED CPU Error BUS connection The terminal makes it possible to integrate any CAN devices in the EtherCAT terminal system and can be used as a Master (EL6751) or Slave (EL6751-0010). In addition, general CAN messages can be sent and received without having to deal with CAN frames in the application program. As a CAN Master, the terminal makes it possible to integrate bus-capable GEZE product systems. Telegrams can be transmitted and received via a channel. Up to 63 devices can be connected to a terminal. The max. possible bus length varies depending on the wiring, number of devices, disrupting influences due to circumstances on site. Application Emergency exit system (EES) GEZE TZ 320, 321, 322 Automatic door drives DCU 1,2,6,8 (DCU light) Smoke and heat extraction system (SHEV) GEZE MBZ 300 19 Hardware description myGEZE Control LED displays The most important statuses of the terminal can be diagnosed quickly on the basis of the LEDs. LED RUN Colour green Meaning This LED indicates the operating status of the terminal: Status of the EtherCAT State Machine off Flashes with … Hz flashes at … Hz On Err red off flashes at … Hz flashes at 10 Hz On CPU Error red On flashes at 10 Hz INIT = Initialisation of the terminal; BOOTSTRAP = Function for firmware updates to the terminal Status of the EtherCAT State Machine PREOP = Function set for mailbox communication and deviating standard settings. Status of the EtherCAT State Machine SAFEOP = Check the channels of the Sync Manager and Distributed Clock. Outputs always remain in safe status. Status of the EtherCat State Machine OP = Normal operating status, mailbox and process data communication is possible. All configured bus devices fault-free (Box State=0), TwinCAT task or process is running. At least one Box State is not equal to zero (e.g. device not found, wrong configuration, device faulty). Configuration upload is carried out. CAN controller is Bus OFF. Physical CAN problem. Possible causes of fault e.g. no terminating resistor, bus cable too long, wrong Baud rate, node address assigned twice, wiring fault, short-circuit. Restart necessary. Fault in the processor of EL6751. Processor of EL6751 starts. 20 Hardware description myGEZE Control … myGEZE Control CAN connector Fig. 10 : myGEZE Control CAN connector The bus lines are connected to the bus terminal via a 9-pole D-sub connector for CAN with an integrated terminating resistor. Two cables can be connected to the connector. This is necessary if the bus terminal is NOT the end of a bus segment. In this case, the integrated switch for terminating resistor must be deactivated; OFF position. If the bus terminal designated as the first or last device on the bus segment, in other words forms one end of the bus, the integrated switch for terminating resistor must be activated: ON position. In this case, connection of a cable is only possible at the first connection (PIN 1,2,3). Terminal (X1) D-sub PIN (X2) Signal … - … 2 … 5 CAN GND CAN L CAN H CAN SHD Tab. 1: myGEZE Control CAN connector assignment 21 Hardware description myGEZE Control Fig. 11: myGEZE Control CAN connector connection illustration 22 Hardware description myGEZE Control … myGEZE Control KNX-System Fig. 12 : myGEZE Control KNX System myGEZE Control E-bus coupler myGEZE Control terminal KNX/EIB myGEZE Control bus end terminal A combination of these … terminals is necessary for KNX 1x myGEZE Control E-bus coupler 2x myGEZE Control terminal KNX/EIB 1x myGEZE Control bus end terminal Technically … EIB/KNX terminals are ALWAYS necessary. Is connected to a 2-wire KNX system (twisted pair) No configuration of this device in ETS necessary, terminal is a passive bus device. In larger ETS projects, it may be necessary to adjust the line coupler and filter. The … terminals can only be used once per controller. With this connection, 200 x IQ box KNX can be connected. Information for Wind alarm Wind value Rain alarm Safety is used by KNX and mapped on BACnet (once, not per IQ box KNX). 23 Hardware description myGEZE Control Structure Fig. 13: Structure bus terminals for communication with KNX Set Set EIB+ EIB+ Power contact +24 V EIBEIBPower contact … V Shield Shield This/these terminal(s) is/are required for communication with the GEZE IQ box KNX for connection of window drives. Two terminals are always needed. Connection to a myGEZE Control system must always be via a coupler module since it is a different internal communication technology. 24 Hardware description myGEZE Control LED displays Fig. 14: LED indicators KNX LED Run LED Set LED EIB-TXD LED EIB-RXD/Power LED Send LED Receive LED EIB Error 25 Hardware description myGEZE Control Example Fig. 15: Example structure for communication with KNX myGEZE Control Basic DI 8K.-DIGI-IN., 24 V DC Potential dist. TE. 16x 24VDC DO 4K.-REL.-OUT. 125 V DC myGEZE Control CAN Bus coupler myGEZE Control KNX Final terminal 26 Hardware description myGEZE Control LED displays Fig. 16: LED indicators KNX LED K-Bus Run LED Set LED EIB-TXD LED EIB-RXD/Power LED Send LED Receive LED Receive LED K-Bus Run Set EIB-TXD EIB-RXD / POWER SEND RECEIVE EIB ERROR Colour green Channel … Status and meaning on off flashes Lights up weak to strong: KBus communication OK None K-Bus communication K-Bus communication green green green green green red 27 Hardware description myGEZE Control … myGEZE Control 8-channel digital input terminal Fig. 17 : myGEZE Control 8-channel digital input terminal Designation Meaning INPUT … Input … INPUT … Input … INPUT … Input … INPUT … Input … INPUT … Input … INPUT … Input … INPUT … Input … INPUT … Input … Digital input terminal with eight inputs to detect binary control signals from the process level. Connection of non-bus-capable components to the GEZE building system. Eight channels that indicate their signal state through light emitting diodes. Up to ten digital inputs possible per basic controller. 28 Hardware description myGEZE Control LED displays Fig. 18: LED indicators KNX Signal-LED … Signal-LED … Signal-LED … Signal-LED … Signal-LED … Signal-LED … Signal-LED … Signal-LED … LED INPUT 1-8 Colour green Meaning off On Signal voltage “0“ (-3 V ... … V) Signal voltage “1“ (11 V...30 V) 29 Hardware description myGEZE Control … myGEZE Control potential distribution terminal 24 V DC Fig. 19 : myGEZE Control potential distribution terminal 24 V DC Power contact +24 V Power contact … V The potential distribution terminal makes 16 terminal points with 24 V potential available at the front at the terminal contacts. The 24 V power contact is connected to the terminal contacts at the front and is passed through to the adjacent terminal. The … V power contact is not connected to the terminal contacts at the front, it is passed through to the adjacent terminal. This allows the use of additional terminal blocks on the terminal strip to be reduced. 30 Hardware description myGEZE Control … myGEZE Control potential distribution terminal … V DC Fig. 20: myGEZE Control potential distribution terminal … V DC Power contact +24 V Power contact … V The potential distribution terminal makes 16 terminal points with … V potential available at the front at the terminal contacts. The … V power contact is connected to the terminal contacts at the front and is passed through to the adjacent terminal. The 24 V power contact is not connected to the terminal contacts at the front, it is passed through to the adjacent terminal. This allows the use of additional terminal blocks on the terminal strip to be reduced. 31 Hardware description myGEZE Control … myGEZE Control output terminal 2-channel relay Fig. 21 : myGEZE Control output terminal 2-channel relay LED relay … LED relay … Relay, … normally open contact Relay, … normally open contact Relay, … middle contact Relay, … middle contact Relay, … normally closed contact Relay, … normally closed contact PE (internally connected to terminal point 4) PE (internally connected to terminal point 4) Power contact PE 32 Hardware description myGEZE Control LED displays LED Relay 1, relay … Colour green Meaning off On Changeover contact between terminal points 2‑3 (channel 1) or 6‑7 (channel 2) closed. Changeover contact between terminal points 2‑1 (channel 1) or 6‑5 (channel 2) closed. The output terminal has two relays with one change-over contact each. The signal state of the EtherCAT terminal is indicated by light emitting diodes. The output terminal is equipped with potential-free contacts, the power contacts are not passed through. 33 Hardware description myGEZE Control … myGEZE Control output terminal 4-channel relay Fig. 22 : myGEZE Control output terminal 4-channel relay Signal LED … Signal LED … Signal LED … Signal LED … Relay, … normally open contact Relay, … normally open contact Relay, … normally open contact Relay, … normally open contact Relay, … normally open contact Relay, … normally open contact Relay, … normally open contact Relay, … normally open contact Power contact Power contact 34 Hardware description myGEZE Control LED displays LED Signal … - … Colour green Meaning off On Terminal points 1-2 (channel 1), 5-6 (channel 2), 3-4 (channel 3) or 7-8 (channel 4) not connected. Terminal points 1-2 (channel 1), 5-6 (channel 2), 3-4 (channel 3) or 7-8 (channel 4) connected. The output terminal has four relays with one single contact each. The relay contact can be used up to 125 V AC or 30 V DC. The signal state of the EtherCAT terminal is indicated by light emitting diodes. The output terminal is equipped with potential-free contacts. The power contacts are passed through. 35 Hardware description myGEZE Control … myGEZE Control power supply terminal Fig. 23: myGEZE Control power supply terminal Power LED (E-bus) Power LED (power contacts) Diagnostic LED (E-bus) Diagnostic LED (power contacts) Run LED 24 V feed Power contact … V feed Power contact PE Power contact The EL9410 power supply terminal serves to regenerate the E-bus via which the data exchange between EtherCAT coupler and terminals takes place. Every EtherCAT terminal requires a certain current from the E-bus. This current is supplied by the power supply of the respective EtherCAT coupler to the E-bus. It can be used with configurations with a large number of EtherCAT terminals to increase the power supply of the E-bus by … A. The power supply terminal has a diagnosis function which is displayed by LED and in the process image. 36 Hardware description myGEZE Control … myGEZE Control coupler Fig. 24: myGEZE Control coupler Link/Act In Signal input EtherCAT Link/Act Out Signal output EtherCAT Power LEDs E-bus Supply coupler Power contact feed Power contacts The EtherCAT coupler is the link between the EtherCAT protocol on field bus level and the EtherCAT terminals. The coupler converts the telegrams from the Ethernet 100BASE-TX- to the E-bus signal representation in a pass. A station is made up of a coupler and any number of EtherCAT terminals which are automatically detected and shown individually on the process image. The EtherCAT coupler has two RJ45 sockets. The coupler is connected to the network with the upper Ethernet interface, the lower socket is used for the optional connection of further EtherCAT devices in the same line. In addition, an EtherCAT junction or an EtherCAT extension can be used for the extension or to build up a line or star topology. 37 Hardware description myGEZE Control … myGEZE Control extension Fig. 25: myGEZE Control extension Run LED Signal output EtherCAT Link/Act In The EtherCAT extension is set at the end of an EtherCAT terminal line or an embedded PC of the CX series and offers the possibility of extending the EtherCAT network in line topology. The EtherCAT extension has an RJ45 socket which permits connection of an Ethernet cable with RJ45 connector and sets up a connection to a further EtherCAT line or to individual EtherCAT devices. The E-bus signals are converted to 100BASE-TX-Ethernet signal representation in a pass. The electronics are supplied via the E-bus. Parameter setting or configuration is not necessary. 38 Hardware description myGEZE Control … myGEZE Control 2-port junction Fig. 26: myGEZE Control 2-port junction Run LED EtherCAT junction … EtherCAT junction … The 2-port EtherCAT junction can be used in an EtherCAT terminal line at any point between the EtherCAT terminals and makes it possible to build up EtherCAT star topologies. The use of several EK1122 in one station allows a modular EtherCAT star hub to be realised. 39 Hardware description myGEZE Control … myGEZE Control bus end cover Fig. 27: myGEZE Control bus end cover Each bus station must be completed by an end cover on the right-hand side. Information (functional description, wiring diagram or explanation of the LED displays) about the individual terminals is available in the Beckhoff information system: https://infosys.beckhoff.com/index.htm … Terminal name with myGEZE Control assignment to Beckhoff The table below shows the correct assignment of the terminal names: Designation GEZE GmbH Designation Beckhoff Link myGEZE Control CPU MODULE 8191 myGEZE Control CAN MASTER TERMINAL myGEZE Control CAN connector CX8191 | Embedded-PC with BACnet/IP EL6751 | EtherCAT terminal www.beckhoff.com/CX8191 ZS1051-3000 | CANopen, bus interface connector BK1250 | Compact coupler between EtherCAT terminals and bus terminals KL6301 | Bus terminal, 1-channel communication interface, KNX/EIB KL9010 | End terminal EL1008 | EtherCAT terminal, 8-channel digital input EL9188 | Potential distribution terminal EL9189 | Potential distribution terminal EL2612 | EtherCAT terminal, 2channel relay output EL2624 | EtherCAT terminal, 4channel relay output EL9410 | Power supply terminal for E-bus regeneration with diagnosis function EK1100 | EtherCAT coupler EK1110 | EtherCAT extension EK1122 | 2-Port-EtherCAT junction EL9011 | End cover for E-bus contacts www.beckhoff.de/ZS1051-3000 myGEZE Control KNX-System myGEZE Control 8-channel digital input terminal myGEZE Control potential distribution terminal 24 V DC myGEZE Control potential distribution terminal … V DC myGEZE Control output terminal 2-channel relay myGEZE Control output terminal 4-channel relay myGEZE Control power supply terminal myGEZE Control coupler myGEZE Control extension myGEZE Control 2-port junction myGEZE Control bus end cover www.beckhoff.com/EL6751 www.beckhoff.de/BK1250 www.beckhoff.de/KL6301 www.beckhoff.de/KL9010 www.beckhoff.de/EL1008 www.beckhoff.de/EL9188 www.beckhoff.com/EL9189 www.beckhoff.com/EL2612 www.beckhoff.com/EL2624 www.beckhoff.com/EL9410 www.beckhoff.com/EK1100 www.beckhoff.com/EK1110 www.beckhoff.com/EK1122 www.beckhoff.com/EL9011 40 System structure and system limits … myGEZE Control System structure and system limits The software application created by GEZE has a defined number of max. possible terminals for each function. The maximum system structure for the software template is used to create a project-specific customer configuration. The software template prescribes a certain sequence for the different terminal types. This is necessary for functional reasons. A communication terminal, for example, does not forward certain potentials and signals in the terminal system. For this reason, it must not be inserted at the beginning of the terminal system. To set up the function of the controller system, different auxiliary terminals are necessary, which make voltage potentials available, feed the internal bus supply in larger systems or create transitions (couplers) for internal bus supplies. … Max. possible terminals in the template project … x basic device 10 x digital input 8-channel potential-free 10x digital relay output 2-channel change-over contact 10x digital relay output 4-channel normally open contact 5x CAN bus terminal 1x connection to KNX system comprising … terminals 41 System structure and system limits myGEZE Control … Technically possible order of terminals in the template project Basic device System structure starts with the basic device as controller. The controller serves all internal terminal bus systems incl. the necessary voltage and signal supplies. 8-channel digital input 1… 10 terminals One or more potential distribution terminals 24V DC or 0V DC are necessary for the potential supply of the inputs. These must be inserted in the connection. Potential distribution terminal 24V DC / 0V DC 1 … terminals Allows for tapping of the potential without additional terminal blocks or wiring work. 16 contacts can be tapped per terminal. Power supply terminals The power supply terminal serves to refresh the Ebus that handles the data exchange between the coupler and terminals. Each terminal requires a certain current from the E-bus. This current is fed into the E-bus by the power supply terminal or the controller. Also necessary for transmitting potential via contacts for output terminals. This terminal needs a supply with supply voltage. Output terminal 2-channel relay change-over contact Output terminal 4-channel relay normally open contact CAN master terminal This is a communication terminal. It must not be installed in order before I/O terminals. KNX system Comprising the … terminals in the K-bus system. Must always be installed at the end of the system. Power supply terminals: This terminal needs a supply with supply voltage. Always necessary upstream of the terminals 2K.-REL-OUTPUT (PE contact) Always between the terminals 2K.-REL-OUTPUT and 4K.-REL-OUTPUT (power contacts). Optional upstream of the terminals REL-OUTPUT or CAN terminal for refreshing the E-bus, if more than a total of 10 terminals are installed. 42 System structure and system limits myGEZE Control … System limits 200 GEZE product systems can be connected to one controller system. The product systems refer to the defined module types; see the attachment to the user manual 207846 BACnet Definition. This results on average – depending which products are connected – in approx. 3000 BACnet data points. The connection of MBZ300 control units is an exception. Here, the maximum number of 250 MBZ modules is the limit, independently of the number of MBZ systems these are distributed across. No other product system may be connected to this terminal. … Substations The system offers the possibility of building up a decentralised structure through substations. This makes it possible to reduce the cable connections to the connected product systems by building up substations locally with the corresponding terminal systems. The connection to the controller is by means of a passive connection with CAT-5 cable / RJ45 socket. The max. length between two stations is 100 m (100BASE-TX). It is possible to build up almost any substation structure through the necessary couplers. 200 substations at maximum can be connected to the basic controller system. A special version of the template software is necessary to compile the application. This must be requested through project processing. Fig. 28: Example of substation system structure Basic device 8-channel digital input + potential CAN master terminal 2-Port. junction CAT … – wiring, passive (length max. 100 m) To additional substations 8-channel digital input + potential Output terminal 2-channel relay change-over contact 43 System structure and system limits myGEZE Control … Detached inputs and outputs with GEZE IO 420 The system also offers the option of detecting digital inputs and outputs via the IO 420 interface module. This makes it possible to reduce the cable connections to the connected product systems by building up substations locally with the corresponding terminal systems. … digital inputs and outputs can be detected in a decentralised manner in this way via an IO 420. The IO 420 interface module is integrated into a CAN bus line like the other CAN bus capable devices. When completing the configuration, note that an IO 420 interface module will occupy … CAN addresses on the bus system. 1. CAN addr.: Input and output … + … 2. CAN addr.: Input and output … + … Fig. 29: Detached inputs and outputs with GEZE IO 420 Configuration of the inputs and outputs detected via the IO 420 is carried out in the same manner for the myGEZE Control Configurator as configuration of the input and output terminals. The IO 420 interface module must be configured accordingly using the ST220 programming device. Assigning the CAN addresses Module type: Universal Parameter setting for inputs … Determination of the necessary hardware components The necessary hardware components are determined by specification and joint development with the customer and user of the controller system. The system designs and system boundaries described in the previous chapters must be taken into consideration. The on-site circumstances of the project must be taken into account in the design. This affects possible installation positions, cable routes and the connection to existing building management infrastructures. … Electrical wiring diagram If ordered, you will receive the configured components in a control cabinet housing adapted to the quantity of terminals with all the necessary components such as power supply, fuses, terminal blocks etc. In this case, GEZE GmbH also provides an electrical wiring diagram. 44 System structure and system limits myGEZE Control … Licence model The controller system has licensing. The licence is linked to one controller system. Each controller has a system ID which ensures protection. The controller’s system ID has to be known for a licence to be issued. It can be determined using the TwinCAT tool with the system running. 1. 2. In TwinCAT, open the License tab in the opened project solution. The 36-digit system ID can be found under Order Information (Runtime) . This can be retrieved through marking and copying. Fig. 30: TwinCAT SystemID The necessary licence file is issued to the customer by GEZE GmbH through order placement. The encrypted licence file is loaded to the controller during the configuration process together with the configuring data. The controller checks the data and executes the program code accordingly. If there is no valid licence available, the controller goes into Stop mode following configuration. This mode is indicated by a red TC-LED. 45 Putting the software into operation … myGEZE Control Putting the software into operation … Basic information about Beckhoff and TwinCAT … The controller system is made up of hardware components and the programming environment TwinCAT … from Beckhoff Automation. The embedded PCs are programmed in accordance with the powerful IEC 61131-3 standard. The automation software TwinCAT … forms the basis for programming the embedded PC. The manual addresses users with basic knowledge of automation technology from Beckhoff Automation as well as application of the programming environment TwinCAT 3. Menu fields, user interfaces are only explained or shown in the application. More detailed information can be found in the Beckhoff Information System: https://infosys.beckhoff.com/index.htm under TwinCAT … Tools required TwinCAT version Build … Card reader or USB interface with card reader for Micro-SD cards myGEZE Control Configurator Version … .1 or higher For use for advanced configurations only with an administrator account CeRHost remote program from Beckhoff Automation File transfer program, such as WinSCP 46 Putting the software into operation myGEZE Control … myGEZE Control Configurator Introduction … . … System requirements Windows version 22H2 PowerShell Admin rights for installation Developer mode … . … System behaviour Some of the input fields have check correct content. Faulty content is signalled by a red border around the input field. As long as a field has a red border around it, a fault is pending and editing cannot proceed. In the following example, the IP address is configured in a non-valid range: Fig. 31: Example of non-valid input Overview … . … Header Fig. 32: Input screen header Screen name Import of configuration, licence, state text into the program Export of configuration, license, state text to local storage location or to the controller Language selection Selection of device overview / controller Other controller configurations: Calender, notification classes, state texts, scenes 47 Putting the software into operation myGEZE Control Fig. 33: Header in other screens Jumps to the last screen Screen name Selection of device overview / controller Other controller configurations: Calender, notification classes, state texts, scenes 48 Putting the software into operation myGEZE Control … . … Controller overview All the parameters for the controller are configured in the controller overview. These serve as unique identification for the controller system within the building automation network. The data are used for configuration of the controller and mapped in part to the respective properties of the BACnet device object. Fig. 34: Input screen The values marked by an * have to be stipulated if they are to be used in the further course for the definition of patterns. These fields are also subject to review. As long as the entry is not logical in structure, the field will have a red border around it. This field cannot be edited. The number of the licence file is shown here after data import. A licence file is necessary in the controller as authorisation for the application. The IP address of the controller is determined through these three input fields. Empty field data are not changed. (Standard … . … / … . … ) “ … . … ” DHCP is activated Data only relevant for X101/102 (TCCCATMP1). DIP switches 10 and … to OFF and … to … to ON . Object name Defines the technical address of the controller in the BACnet network. Permissible range: … to 4194302 49 Putting the software into operation myGEZE Control Location Description … . … Import A configuration that has already been generated can be imported to the program again later and further edited. For this, the program offers the possibility of importing the data from a folder directory or directly online from a connected controller. Independently of whether locally or via the controller, configuration, licence and state texts can be imported at the same time. Pattern variables in curly brackets { } are not saved and are thus not read in again. Select the required data types. Set whether the import is to be carried out from the controller or locally. Choose import and select the required files (csv and lic). Carry out selection of the files according to the required file types (step 1). If the configuration contains scenes, the state texts must be imported at the same time. Fig. 35: Import local Data import from a controller system takes place via ftp file transfer. This is protected by the entry of user and password. 50 Putting the software into operation Standard User name: Password: myGEZE Control geze 1863 Fig. 36: Import Controller Host IP address or host name of the target system User name System user, e.g. GEZE Password System password Test connection The connection to the target system can be checked with this. green = connection successful red = connection failed Import Data import is started 51 Putting the software into operation myGEZE Control The status of the import is shown by a dialogue field after the procedure has been completed: Fig. 37: Import successful Fig. 38: Import failed 52 Putting the software into operation myGEZE Control … . … Export A prepared configuration can be exported from the program. This can be into a folder directory (local) e.g. as data backup. This configuration can be loaded again later via the import function and further edited. Pattern variables in curvy brackets { } are not exported, only the result. With the controller setting the data are transmitted directly to a connected controller system. The same access data as for the import apply here. For a complete export to the controller, the licence must already have been imported. The export can be carried out locally and to a controller at the same time. To carry out export via controller a valid FTP link and the user data must be entered. In the case of export to the controller, a local copy is saved in the defaults folder at the same time. Configuration, licence and state texts can be exported at the same time on the controller. Locally, only configuration OR licence OR state can be exported. This is because a name must be provided to save the files. Fig. 39: Controller and local export 53 Putting the software into operation myGEZE Control … . … Functions … . … .1 Device overview All configured devices are shown here. Further devices can be added and removed. Fig. 40: Device overview empty Fig. 41: Device overview with content If the fields have a red border around them, the entry is not valid and must be adapted. 54 Putting the software into operation myGEZE Control Icons The device data can be edited Selected device is deleted Opens the overview of all data points (BACnet) of the device. With I/O the data points are also shown without BACnet link. … . … .2 Adding a device Devices are added in four steps. To do this, select Add devices. Adding always takes place for a certain device type. In other words, all the steps must be completed for this device type and the configuration saved before the next devices can be created. … . … . … Step … In the first step, specific patterns can be defined for the devices which are then used for the creating the devices. This makes it easier to add the devices, since this data is then predefined and does not have to be entered individually. Free text elements can be used for these patterns, or an automatism can be created by means of a variable specified in curly brackets. In the process, controller data already entered and data created in the further course (e.g. addressing, type) are used via these specifications in curly brackets. The defined patterns apply for all the elements that are generated in the next steps. Fig. 42: Adding devices – step … (default setting) 55 Putting the software into operation myGEZE Control Possible pattern fields Device name Free text field {controller-number} {controller-name} {controller-location} {device-type} {device-id} Device description Direct input Input from controller field Instance number Input from controller field Object name Input from controller field Location Device type selected in step … GEZE device ID, results automatically in step … Free text field {controller-number} {controller-name} {controller-location} {device-name} {device-type} {device-id} Project name see above see above see above see above Name generated in step … which results from this pattern see above see above Free text field {controller-number} {controller-name} {controller-location} {device-name} {device-type} {device-id} {object-id} Building description: see above see above see above see above see above see above see above ID of the individual data point stored in the system Free text field {controller-number} {controller-name} {controller-location} {device-name} {device-type} {device-id} {object-id} {object-name} see above see above see above see above see above see above see above see above Name generated in step … which results from this pattern 56 Putting the software into operation myGEZE Control Fig. 43: Example of pattern entered The variables which are possible or can be used are shown in the INFO box. 57 Putting the software into operation myGEZE Control … . … . … Step … In this step, device type, the number of devices to be created and the technical addressing are defined. The devices are then defined using this information together with the patterns prepared in step 1. The device configuration differs depending on the device type selected. The addresses are determined automatically according to a pre-existing definition. They can be adapted again later. During the final addition of one/several devices, this automatically receives an internal device ID. This is unique in the system and is numbered sequentially. The device ID can be changed manually. The operator is then responsible for the one-time assignment. Fig. 44: Adding devices – step … Editing steps Select device type Specify number Specify technical address Check device name pattern, device description pattern and adapt if necessary Add selection . Choose step 3. Add selection. Refresh view. Overview of devices added. User information 58 Putting the software into operation myGEZE Control Every CAN terminal can contain max. 63 devices. In total, max. 200 devices can be connected distributed among all CAN terminals. Device ID is a sequential number of the existing devices. Up to 9,999 devices be added. This value is necessary for calculation of the BACnet instance number. … . … . … Step … The patterns for the objects are defined in this step. The data entered in steps … and … are used for this. Editing steps Select created device type. Add object name. Use the slide switches ‘BACnet ’ to define which data points are to be forwarded to BACnet. If necessary, adapt the settings for notification class and state texts. Individual notification class objects and state texts can be assigned to the objects here. Following completion, change the next editing step by clicking . Fig. 45: Adding devices – step … This step must be carried out with all the device types created. During this editing step, object name and description are still shown with their pattern definition. The resulting name and description can only be shown in step 4! … . … . … Step … In this step, the number of configured devices per type with the entries made are shown. The data of the patterns entered are now shown resolved with the data generated. Changes/adaptations can be carried out here by opening and editing the individual devices. 59 Putting the software into operation myGEZE Control Fig. 46: Adding devices – step … Refresh view. Save current selection. Open device overview. Delete device. Edit devices. If an error has occurred during creation of the devices, the faulty device has a red border around it. 60 Putting the software into operation myGEZE Control Editing steps Check whether the devices have been created as entered in terms of quantity and data. Open the individual devices by clicking the button . If necessary or if a faulty configuration is shown at the device, click the button mode and adapt individual data records. to change to editing Faulty devices must be edited. Close editing mode. Refresh view. Save configuration. Saving the creation process is sufficient to save complete it. If the configured devices are to be used again later, the configuration must be exported. See chapter “Export”. Fig. 47: Editing devices – step … 61 Putting the software into operation … . … .3 … . … . … myGEZE Control Overview of further functions Calendar Fig. 48: Calendar function 62 Putting the software into operation myGEZE Control … . … . … Messages BACnet offers the possibility of sending alarms using different notification class objects. The notification class objects can be defined or adapted here. After they have been configured here, the notification objects can be used for the data objects of the devices. Fig. 49: Notification function (default) ID BACnet instance number Name BACnet object name Description BACnet description Ack necessary Settings for alarm confirmation by the recipient Priority Settings for the priorities of the alarm states Receiver address BACnet device instance (ID) of the receiver device Process ID Process number for transmitting the alarms / events 63 Putting the software into operation myGEZE Control Adding/editing notification Click the button A further notification class is created. The ID is counted up automatically first in a 10 pattern. Change to editing mode using and . Carry out settings. Saving takes place automatically here. Fig. 50: Edit reporting classes Explanatory notes: Ack necessary Priority State transition Receiver device Receiver process ID Determines the requirement for a confirmation of the received message depending on the state transition Determines the priority of a transmitted message depending on the state transition To_offNormal: Transition to signal status To_Normal: Return to idle status To_Fault: Transition to a fault status for the data point Specify a receiver based on the BACnet device ID of the receiver device Empty == no receiver defined Entry … . 4139302 possible Process number with which myGEZE Control transmits the messages to the receiver device These settings must be made in agreement with the system integrator of the receiver device if necessary. They usually determines how their system must receive the alarms / events. 64 Putting the software into operation myGEZE Control … . … . … State texts A state text is the definition of the state texts and levels of a digital data point. State texts are predefined and their number can be increased as required. Every digital data point can have one of these state texts assigned. Adding, editing and deleting work in the same way as in the previous chapters. Fig. 51: State texts function 65 Putting the software into operation myGEZE Control … . … . … Scene The system provides the possibility of defining functional scenes. With these scenes, switching functions which are to take place together can be grouped. A wide range of different commands with different functions can be compiled. These scenes can then be triggered directly via a group switch data point (multi-state value). In addition, an automatic time-dependent function can be stored by configuring a BACnet schedule. Adding, editing and deleting work in the same way as in the previous chapters. Fig. 52: Scene function ID Internal number Name Internal name Schedule name BACnet object name of the schedule Schedule description BACnet description of the schedule The decision can be taken here whether the schedule object is created Command name BACnet object name of the switch data point Command description BACnet description of the switch data point State texts Possible levels of the switch data point (defined under state texts) Definition of the switching actions of the individual switch objects 66 Putting the software into operation myGEZE Control Adding/editing scene Click the button A further scene class is created Change to editing mode using and . Carry out settings. Saving takes place automatically here. Adding/editing switching action Change to the settings: Button Input screen for the actions is opened Change to editing mode using and . Carry out settings. Save with Fig. 53: Configuration of actions Type Device type Device name Device name generated Project name BACnet data point name generated Selection possible from the switchable data points of the device Value Selectable value: Selection possible from the state texts or as unsigned number with multi-state objects 67 Putting the software into operation myGEZE Control Installation Carry out the following steps to install the myGEZE Control configurator: Download the latest version via the download link. Unpack the zip file. Execute PowerShell as administrator. In PowerShell, change to the folder in which the zip file was unpacked. Execute install.ps1 Updating No automatic updates are planned for the configurator. For updates, there is a new installation package that can be installed. Deinstallation Deinstallation is done using the Windows (De)installation Wizard. 68 Putting the software into operation myGEZE Control … Preparations for a new controller The embedded PC is commissioned via the upper controller Ethernet interface X001. Then the field bus interface and all connected devices/bus terminals are configured by TwinCAT 3. After parameter setting, the configuration is saved on the embedded PC. To get a controller ready for operation, several work steps are required concerning firmware version, access possibilities via interface, release and blocking of functions and accesses. These settings are saved in a predefined image file. To load this image to a new controller, note the following points. A computer system with card reader or USB port and a USB card reader for micro SD cards is necessary for this work step. Settings that are set with this image Firmware IP interfaces … Upper interface X001 Name EMAC1 IPv4 Address IPv4 Subnet Mask DHCP IPv4 Default Gateway … . … . … Disabled … . … Lower interface X101/102 Name IPv4 Address IPv4 Subnet Mask DHCP IPv4 Default Gateway TCCCATMP1 … . … . … Disabled … . … Project user Name PW GEZE 1863 Programming and diagnosis interface Interface for BACnetIP FTP Transmission possible as administrator and with project user and the respective password. Anonymous user is switched off. CeRHost Beckhoff-Device-Manager can be reached by administrator can be reached by administrator 69 Putting the software into operation myGEZE Control Preparations Here, the term hard disk stands for the drive that results when the SD card is inserted to the programming device. Disconnect the controller from the power supply. Remove the micro SD card and insert in a card reader at the PC. Copy the licence data from the directory \Hard Disk\TwinCAT\ … \Target\License and save as data backup. Mark and delete all files and folders from the main directory on the micro SD card (do not format the card). Unpack the zip file with the image files to any directory. Copy all image files to the root level of the micro SD card. Copy the licence files saved in step … back to the directory \Hard Disk\TwinCAT\ … \Target\License. Safely remove/eject the micro SD card at the PC, remove it from the card reader and insert it into the controller. Set the DIP switches on the controller as follows: Fig. 54: DIP switch S101, switches 1-10 DIP … to 8: DIP … and 10: ON OFF Connect the controller back to the power supply and boot it. Attention: The controller automatically carries out a second restart after startup if the firmware does not match that of the images. This then takes somewhat more time. Set the Ethernet interface of the computer system as follows: 70 Putting the software into operation myGEZE Control The two IP addresses shown are to be seen as an example as far as the setting in the host range (last part) is concerned. To avoid double assignments, an address between … ... 253 can be set here. Do not use the addresses … . … and … . … . The controller uses these addresses. Connect the computer with the programming interface X001 (top). In the computer system, open the TwinCAT menu on the Windows task bar. There, open Edit routes: Fig. 55: Edit route Click Add, enter … . … and press Enter : 71 Putting the software into operation myGEZE Control Fig. 56: Add route dialogue Under Address Info the radio button IP Address must be enabled, otherwise the route will not be added. Click Add Route. Check mark next to Secure ADS: User: GEZE PW: 1863 Click OK, click Close: 72 Putting the software into operation myGEZE Control If there is an x next to Connected after this, the route to the controller is available. Fig. 57: Example CX745FD0 The controller is prepared for programming/configuration with TwinCAT. 73 Putting the software into operation myGEZE Control … Preparing an application for a project An application is made up of … basic components and is prepared using the tools described in the previous chapters. Beckhoff TwinCAT … Hardware and software template myGEZE Control Configurator Project configuration Controller licence Software protection of the GEZE application All software parts must be prepared as described and then loaded into the controller. It is recommended to load in the order of editing, first the prepared project configuration comprising Configuration file State texts Licence file with the myGEZE Control Configurator to the controller. Then to edit the hardware and software template and activate it in the controller. This way the right configuration is used immediately when the software template is activated. Editing in reverse order is also possible, in this case another system restart must be carried out after the configuration has been transmitted. IP addresses and BACnet settings of the controller As described in the chapter Preparations for a new controller , the controller is assigned one IP address each for the interfaces through basic configuration. The settings for the lower interface X101/102, TCCCATMP1 can be made according to customer specification. This is done in the myGEZE Control Configurator program and is saved together with the BACnet device ID in the configuration file and transmitted to the controller. Fig. 58 : myGEZE Control Configurator IP address example Further BACnet parameters cannot be set using the configuration file. These have to be adapted directly in TwinCAT if needed. This can concern the UDP port used for BACnet communication, for example. For this, open the network settings under Advanced Settings under I/O in Device … (BACnetIP) . UDP Port and Network Number can be adapted to customer specification here. 74 Putting the software into operation myGEZE Control Fig. 59: Advanced settings Loading a GEZE project Load the configuration prepared with myGEZE Control Configurator and the licence to the controller. The advantage of loading this configuration to the controller before the TwinCAT project is that the controller then boots correctly directly after activation of the application If the step is not carried out until after activation, the controller goes into Stop mode since the licence is missing. Preparing TwinCAT project Create a folder for the project in the XAE directory. There is a free choice for the folder name. Use of a name that refers to the project is recommended. The order number and project name can be integrated, for example. Load the TwinCAT template project from the tnzip directory. The software template is available in the format ‘tnzip’, zipped with TwinCAT. This is available from GEZE GmbH in the respectively approved version. The project-specific configurations can be derived from this template. 75 Putting the software into operation myGEZE Control In TwinCAT, select File / Open / Open Solution from Archive Fig. 60: TcXaeShell_openProject 01 Select the directory path created previously and confirm “Select folder”. Fig. 61: TcXaeShell_openProject 02 76 Putting the software into operation myGEZE Control Select a customer project The template project contains the configured customer application and software that can be used to analyse the connected CAN devices during commissioning. This is explained again in section … . This must be selected in the TwinCAT Solution Explorer in order to edit the customer project. Fig. 62: Project selection_SolutionExplorer Change to the target hardware Use Choose Target System to select the hardware for which a route was prepared previously. Confirm information about changing the platform with Yes. Fig. 63: TcXaeShell_openProject 03 77 Putting the software into operation myGEZE Control Fig. 64: TcXaeShell_openProject 04 78 Putting the software into operation myGEZE Control … . … Checking GEZE software libraries … software libraries from GEZE GmbH are required for the correct processing of the program workflow. These are normally already implemented in the software. If any parts are missing, this will be indicated by TwinCAT. Open the library path in TwinCAT under the PLC application by double-clicking ‘References’: Fig. 65: TwinCAT references The GEZE libraries installed are shown in the editor window. Fig. 66: TwinCAT references faulty In the example shown, the library for myGEZELicensing is incorrect or missing. This is indicated by the wavy underline and the yellow exclamation mark. In this case, the correct version must then be installed using the tab ‘Library Repository ’. The necessary libraries are located in the PLC folder under …\Testprojekt\myGEZE_TemplateProject\SPS\_Libraries\geze gmbh In TwinCAT, double-click ‘Library Repository ’. Click the ‘Install’ button. Select library path. Select the missing library and install by clicking ‘Open’. 79 Putting the software into operation myGEZE Control Fig. 67: TwinCAT references Once all libraries have been installed correctly, the wavy underline and the yellow exclamation mark will disappear everywhere. Old libraries that are no longer needed can be removed by pressing the button ‘Uninstall ’. 80 Putting the software into operation myGEZE Control … . … Configuration/hardware structure Here, the configuration is adapted to the actual hardware structure. In the template project, all the terminals of the max. possible system structure are listed and initially disabled. Right-clicking the terminal and clicking the function ‘Disable’ again then enables the corresponding terminal. The icon was in front of the terminal before can no longer be seen when the terminal is active. Fig. 68: myGEZE_TcXaeShell_openProject For example: Fig. 69: myGEZE_TcXaeShell_openProject First terminal active, second terminal disabled. Fig. 70: myGEZE_TcXaeShell_openProject Save all Activate Configuration The project configuration thus prepared is transmitted to the controller and activated using the function ‘Activate Configuration’. For this, a route to the controller must have been set and the correct target hardware selected beforehand. 81 Putting the software into operation myGEZE Control Fig. 71: myGEZE_TcXaeShell_openProject Confirm prompt about restart with OK . Fig. 72: myGEZE_TcXaeShell_openProject 82 Putting the software into operation myGEZE Control … . … Configuring for controller system correct During program download and activation, the TC-LED on the controller as well as various other LEDs in the terminal system light up red. During the final startup procedure of the controller system, the WD (watchdog) LED flashes green. If the prepared and loaded configuration is correct, the two LEDs for TC and W must have light up with green continuous light after the start phase has been completed. No other LEDs may light up red in the upper area at the terminals. Fig. 73: myGEZE LED status … Checking BACnet objects and generating BACnet-EDE file with TwinCAT After configuration has been completed, the correct generation of the BACnet data points can be checked in the TwinCAT programming tool. For the data to be forwarded e.g. to a system integrator for the building management system, the required data can be exported from the system as a BACnet-EDE file according to the standard format prescribed by the BACnet Interest Group. Checking BACnet objects Before: Complete a scan in the sub-item “myGEZE Control (BACnet server)” in Dynamic Object Management. All created BACnet objects will be displayed. Export these to the EDE. If you do not complete the export, the EDE will remain empty. Open the settings for myGEZE Control BACnet server in TwinCAT in the path I/O / Device … (BACnetIP). 83 Putting the software into operation myGEZE Control Double-click to start the settings. To query the configuration generated, change to the Objects Online tab. In this window, all the configured data objects can be seen with their current status. This can be used to check whether all entries made have been implemented correctly. 84 Putting the software into operation myGEZE Control Generating BACnet-EDE file Open the settings for myGEZE Control BACnet server in TwinCAT in the path I/O / Device … (BACnetIP). Double-click to start the settings. To export a BACnet-EDE file, change to the Setting tab. An export is started by clicking Export . Specify the required storage location and file name in the dialogue window. The file type must be set to EDE files (*.csv). Initiate export with the Save button. Place a check mark next to ‘Use Online Data ’ and ‘Create Structured Keynames’ in the window that opens. 85 Putting the software into operation myGEZE Control Start export with the OK button Successful generation is indicated by the program. 86 Putting the software into operation myGEZE Control … Expanded BACnet settings in TwinCAT Assigning the BACnet device instance using the myGEZE Control Configurator The BACnet device instance (also known as the BACnet device ID, BACnet ID, BACnet device address) determines the address of the controller in the BACnet network. The BACnet device address is assigned during the configuration process using the myGEZE Control Configurator tool. See the Controller overview section. There, a parameter loaded into the controller alongside the GEZE device configuration is defined. To ensure these settings are also adopted from the configuration file, the setting parameter provided for this purpose in TwinCAT must be set to ‘0’. Open the settings for myGEZE Control BACnet server in TwinCAT in the path I/O / Device … (BACnetIP) Double click ‘myGEZE Control (BACnet server)’ to start the settings Switch to the Setting tab Check to ensure the parameter ‘BACnet ID’ is set to ‘0’, and if not then set it to ‘0’ Fig. 74: Setting_BACnet ID.PNG Save the configuration if necessary. The TwinCAT configuration must be activated again in the controller. See the section ‘Configuring an application’ 87 Putting the software into operation myGEZE Control Setting the BACnet UDP port BACnet uses communication with UDP (User Datagram Protocol). A communication port is assigned for this communication. For BACnet, this range is defined as 47808 … 47823. The default setting is UDP 47808. This setting can be adjusted within the defined range in TwinCAT based on the user specifications. Open the settings for myGEZE Control BACnet server in TwinCAT in the path I/O / Device … (BACnetIP) Double click ‘Device … (BACnet IP)’ to start the settings To configure UDP, change to the Settings tab Open the Parameter Network Settings under Advanced settings Fig. 75: Setting_BACnet UDP01 88 Putting the software into operation myGEZE Control Change the UDP port parameter in the input dialogue that opens, and click Save to save Fig. 76: Setting_BACnet UDP02 Save configuration. The TwinCAT configuration must be activated again in the controller. See the section ‘Configuring an application’ 89 Putting the software into operation myGEZE Control Setting the BACnet Broadcast Management Device BBMD If the controller can start communication with a BACnet system which is in another IP segment, configuration of a BACnet Broadcast Management Device BBMD is necessary. This configuration can be done in a corresponding Settings tab for the BACnet IP device. Only one system may be configured as BBMD per IP address segment. Otherwise this will lead to a flood of BACnet messages which will bring data communication to a standstill in a very short time and may also cause a heavy load or even communication failure on other devices. For this reason, the network administrator should be consulted before this function is used. Open the settings for myGEZE Control BACnet server in TwinCAT in the path I/O / Device … (BACnetIP). Double-click to start the settings. To configure BBMD, change to the BBMD tab. Activate the function ‘Enable BBMD ’. Click the Initial BDT field and then right-click Add Entry. Open/edit the entry and enter the required IP address of the BBMD partner in the ipAddr field. 90 Putting the software into operation myGEZE Control Several entries can be made here. Save configuration. The TwinCAT configuration must be activated again in the controller. See the section ‘Configuring an application’ 91 Putting the software into operation myGEZE Control … CAN monitor application In order to analyse the configured and used CAN terminals, an application has been created that can display the statuses of the CAN terminals and determine the GEZE devices connected to them. This application is included in the template project as another PLC program, and can be loaded into the controller system during commissioning. Each GEZE device transmits a lifetime telegram to the CAN bus at a cycle of … second. The telegram contains various information, such as the type, bus address, data content. The application evaluates the connected devices based on the content of this telegram. 1. Select CAN monitor project: Fig. 77: Project_selection_SolutionExplorer_CAN-Monitor 2. 3. Check the hardware and adjust to the project if necessary Activate configuration on the controller system 92 Putting the software into operation myGEZE Control Fig. 78: myGEZE_TcXaeShell_openProject08 Confirm prompt about restart with OK . Fig. 79: myGEZE_TcXaeShell_openProject09 The CAN monitor application uses an HMI visualisation function, for which a license is required. This license can be generated for limited time use by entering the random code displayed. There is an application in the CAN monitor that activates the LED for WD flashing red, to indicate that the customer project is not in the controller system. 93 Putting the software into operation myGEZE Control Analysis of CAN terminals and connected devices: A graphic indicator has been created for CAN monitoring. There is a program code behind this graphic that checks to ensure the configured CAN terminals are functioning correctly. The incoming CAN lifetime telegrams for the connected CAN devices are also recorded and evaluated. This information is used to create a graphic display of the CAN status. Accessing the CAN monitor graphic: The graphic can be accessed online in the controller system in two different ways. 1. Access directly from TwinCAT Double click the ‘V_CANMonitor’ graphic The graphic is opened in Editor. Fig. 80: Access_CAN-Monitoring 94 Putting the software into operation myGEZE Control Log into the controller to display the current status Fig. 81: TwinCAT_Log-in After login, the current status of the CAN terminals and connected devices will be displayed live. Fig. 82: CAN-Monitor-V_CAN side 95 Putting the software into operation myGEZE Control Explanatory notes Fig. 83: CAN-Monitor list This list shows a key for the connected devices. An ID in the lifetime telegram of the GEZE device can be used to differentiate between the product series of the devices indicated above. If a device cannot be clearly identified, it appears under type 3. Fig. 84: CAN-Monitor-Button_All.PNG This button deletes all lists of detected devices. They will then be automatically repopulated after the lifetime telegrams are received. Fig. 85: CAN-Monitor-Button_Export.PNG This button can be used to export the current display of connected GEZE devices. The list is saved automatically in the FTP file directory of the controller. An FTP client can be used to load the file with protected access for the user ‘GEZE’ and corresponding password from the controller. 96 Putting the software into operation myGEZE Control Fig. 86: CAN-Monitor-Device_List.PNG EtherCAT OK CAN terminal on the controller operating correctly CAN OK No fault on the CAN bus (such as a short circuit) Clear ListList of corresponding CAN terminals is deleted The detected CAN devices are displayed in the device list with their CAN addresses and type designations. The list can include up to 63 devices. No device was detected at points where a ‘0’ is entered. The list is populated based on the lifetime telegrams received from the devices. They may be received in different sequences, depending on the timing. The list is not sorted by address or type. The sequence of the list may be different each time it is cleared. 2. Display of the current status via a web browser The CAN monitor can also be displayed via a web browser. To do so, access the following link: https:// … . … /Tc3PlcHmiWeb/Port_851/Visu/canmonitor.htm The IP address can differ depending on the settings. 97 Putting the software into operation myGEZE Control Fig. 87: CAN-Monitor-Web-Browser.PNG The functions displayed correspond to those of the interface displayed in TwinCAT. Please note that this is an internal, unsecured web connection (http) without security mechanisms. Please confirm the security notification that may appear in your browser. Due to security guidelines on the device, it may be impossible to form an insecure connection. Please ensure that you load the customer application in the controller system once again and activate it after finishing work with the CAN monitor. Only then will the data and information be processed according to the project configuration. 98 Transportation and storage … myGEZE Control Transportation and storage Control unit Store removed control units in a safe place. Controllers / terminals At storage temperatures above 60 C, remove the battery from the embedded PC. Store the battery separate from the embedded PC in a dry environment at a temperature in the range of … °C to 30 °C. Presets such as the date and time are lost if the battery is removed. 99 Disposal … myGEZE Control Disposal All control unit components must be disposed of in accordance with the statutory regulations for hazardous waste. Rechargeable batteries contain highly toxic substances and therefore can only be disposed of at collection points prescribed by law. Information regarding the German Battery Directive (Applicable in Germany and in all other Member States of the European Union as well as in other European countries, together with the countries' own provisions for a separate waste battery collection system.) In accordance with the German Battery Directive, we are obliged to inform you of the following in connection with the sale of batteries or rechargeable batteries respectively in connection with the delivery of devices containing batteries or rechargeable batteries: Rechargeable batteries and batteries must not be disposed of with household waste. Disposal with household waste is expressly forbidden according to the German Battery Directive. As the end-consumer, you are legally obliged to return used batteries. Please dispose of batteries at a municipal collection point or in store. Batteries received from us can be returned to us by mail after use. The address is: GEZE GmbH, Wareneingang, Reinhold-Vöster-Str. 21–29, 71229 Leonberg. Batteries that contain hazardous substances are labelled with the symbol of a crossed-out rubbish bin. The chemical identifier of the harmful chemical, Cd for cadmium, Pb for lead, Hg for mercury, is located under the rubbish bin symbol. 100 Technical data 10 myGEZE Control Technical data Electrical data and connection values Operating voltage (primary) Frequency Protection 230 V AC -15 % to +10 %, (195 V AC to 253 V AC 50 Hz (47-63 Hz) 10 A Ambient conditions Ambient temperature range –5 to +40 °C Relative humidity 75 % (average value over the entire life span) 90 % (max. 96 h of continuous operation at +40 °C) Mechanical data Surface-mounted housing IP rating Painted sheet steel (RAL 7035) with lock insert (two-way key bit, … mm) IP 30, in compliance with EN 12101-10 environment class … Housing dimensions Depending on the unit equipment Max. power loss of the individual components: Component myGEZE Control CPU MODULE 8191 myGEZE Control CAN MASTER TERMINAL myGEZE Control CAN connector myGEZE Control ETHER CAT-COUPLER myGEZE Control EIB/KNX BUS TERMINAL myGEZE Control END TERMINAL myGEZE Control 8-channel digital input terminal myGEZE Control potential distribution terminal 24 V DC myGEZE Control potential distribution terminal … V DC myGEZE Control output terminal 2-channel relay myGEZE Control output terminal 4-channel relay myGEZE Control power supply terminal myGEZE Control coupler myGEZE Control extension myGEZE Control 2-port junction myGEZE Control bus end cover Max. power loss (in watts) … 2 … - Load 9W with UPS … 1 … 4 … - The power supply for the overall system is 24 VDC (-15 %/+20 %). The power losses may deviate slightly due to the tolerance. 101 List of figures 11 myGEZE Control List of figures Fig. 1: Mounted terminals … 10 Fig. 2: Standard power supply … 10 Fig. 3: Type of installation at temperatures up to 60°C … 12 Fig. 4: Installation … 13 Fig. 5: Disassembly … 13 Fig. 6: Wiring … 14 Fig. 7: myGEZE Control CPU MODULE 8191 … 16 Fig. 8: DIP switch S101, switches … to 10. … 18 Fig. … : myGEZE Control CAN MASTER TERMINAL … 19 Fig. 10 : myGEZE Control CAN connector … 21 Fig. 11: myGEZE Control CAN connector connection illustration … 22 Fig. 12 : myGEZE Control KNX System … 23 Fig. 13: Structure bus terminals for communication with KNX … 24 Fig. 14: LED indicators KNX … 25 Fig. 15: Example structure for communication with KNX … 26 Fig. 16: LED indicators KNX … 27 Fig. 17 : myGEZE Control 8-channel digital input terminal … 28 Fig. 18: LED indicators KNX … 29 Fig. 19 : myGEZE Control potential distribution terminal 24 V DC … 30 Fig. 20: myGEZE Control potential distribution terminal … V DC … 31 Fig. 21 : myGEZE Control output terminal 2-channel relay … 32 Fig. 22 : myGEZE Control output terminal 4-channel relay … 34 Fig. 23: myGEZE Control power supply terminal … 36 Fig. 24: myGEZE Control coupler … 37 Fig. 25: myGEZE Control extension … 38 Fig. 26: myGEZE Control 2-port junction … 39 Fig. 27: myGEZE Control bus end cover … 40 Fig. 28: Example of substation system structure … 43 Fig. 29: Detached inputs and outputs with GEZE IO 420 … 44 Fig. 30: TwinCAT SystemID … 45 Fig. 31: Example of non-valid input … 47 Fig. 32: Input screen header … 47 Fig. 33: Header in other screens … 48 Fig. 34: Input screen … 49 Fig. 35: Import local … 50 Fig. 36: Import Controller … 51 Fig. 37: Import successful … 52 Fig. 38: Import failed … 52 Fig. 39: Controller and local export … 53 Fig. 40: Device overview empty … 54 Fig. 41: Device overview with content … 54 Fig. 42: Adding devices – step … (default setting) … 55 Fig. 43: Example of pattern entered … 57 Fig. 44: Adding devices – step … 58 Fig. 45: Adding devices – step … 59 Fig. 46: Adding devices – step … 60 Fig. 47: Editing devices – step … 61 Fig. 48: Calendar function … 62 Fig. 49: Notification function (default) … 63 Fig. 50: Edit reporting classes … 64 Fig. 51: State texts function … 65 Fig. 52: Scene function … 66 Fig. 53: Configuration of actions … 67 Fig. 54: DIP switch S101, switches 1-10 … 70 Fig. 55: Edit route … 71 Fig. 56: Add route dialogue … 72 102 List of figures myGEZE Control Fig. 57: Example CX745FD0 … 73 Fig. 58 : myGEZE Control Configurator IP address example … 74 Fig. 59: Advanced settings … 75 Fig. 60: TcXaeShell_openProject 01 … 76 Fig. 61: TcXaeShell_openProject 02 … 76 Fig. 62: Project selection_SolutionExplorer … 77 Fig. 63: TcXaeShell_openProject 03 … 77 Fig. 64: TcXaeShell_openProject 04 … 78 Fig. 65: TwinCAT references … 79 Fig. 66: TwinCAT references faulty … 79 Fig. 67: TwinCAT references … 80 Fig. 68: myGEZE_TcXaeShell_openProject … 81 Fig. 69: myGEZE_TcXaeShell_openProject … 81 Fig. 70: myGEZE_TcXaeShell_openProject … 81 Fig. 71: myGEZE_TcXaeShell_openProject … 82 Fig. 72: myGEZE_TcXaeShell_openProject … 82 Fig. 73: myGEZE LED status … 83 Fig. 74: Setting_BACnet ID.PNG … 87 Fig. 75: Setting_BACnet UDP01 … 88 Fig. 76: Setting_BACnet UDP02 … 89 Fig. 77: Project_selection_SolutionExplorer_CAN-Monitor … 92 Fig. 78: myGEZE_TcXaeShell_openProject08 … 93 Fig. 79: myGEZE_TcXaeShell_openProject09 … 93 Fig. 80: Access_CAN-Monitoring … 94 Fig. 81: TwinCAT_Log-in … 95 Fig. 82: CAN-Monitor-V_CAN side … 95 Fig. 83: CAN-Monitor list … 96 Fig. 84: CAN-Monitor-Button_All.PNG … 96 Fig. 85: CAN-Monitor-Button_Export.PNG … 96 Fig. 86: CAN-Monitor-Device_List.PNG … 97 Fig. 87: CAN-Monitor-Web-Browser.PNG … 98 103 Germany GEZE GmbH Niederlassung Süd-West Tel. +49 (0) 7152 203 594 E-Mail: leonberg.de@geze.com Austria GEZE Austria E-Mail: austria.at@geze.com www.geze.at India GEZE India Private Ltd. E-Mail: office-india@geze.com www.geze.in Scandinavia – Sweden GEZE Scandinavia AB E-Mail: sverige.se@geze.com www.geze.se GEZE GmbH Niederlassung Süd-Ost Tel. +49 (0) 7152 203 6440 E-Mail: muenchen.de@geze.com Benelux GEZE Benelux B.V. E-Mail: benelux.nl@geze.com www.geze.be www.geze.nl Italy GEZE Italia S.r.l. Unipersonale E-Mail: italia.it@geze.com www.geze.it Scandinavia – Norway GEZE Scandinavia AB avd. Norge E-Mail: norge.se@geze.com www.geze.no GEZE GmbH Niederlassung Ost Tel. +49 (0) 7152 203 6840 E-Mail: berlin.de@geze.com Bulgaria GEZE Bulgaria - Trade E-Mail: office-bulgaria@geze.com www.geze.bg GEZE Engineering Roma S.r.l E-Mail: italia.it@geze.com www.geze.it Scandinavia – Denmark GEZE Danmark E-Mail: danmark.se@geze.com www.geze.dk Korea GEZE Korea Ltd. E-Mail: info.kr@geze.com www.geze.com Singapore GEZE (Asia Pacific) Pte, Ltd. E-Mail: gezesea@geze.com.sg www.geze.com Poland GEZE Polska Sp.z o.o. E-Mail: geze.pl@geze.com www.geze.pl South Africa GEZE South Africa (Pty) Ltd. E-Mail: info@gezesa.co.za www.geze.co.za Romania GEZE Romania S.R.L. E-Mail: office-romania@geze.com www.geze.ro Switzerland GEZE Schweiz AG E-Mail: schweiz.ch@geze.com www.geze.ch Russia OOO GEZE RUS E-Mail: office-russia@geze.com www.geze.ru Türkiye GEZE Kapı ve Pencere Sistemleri E-Mail: office-turkey@geze.com www.geze.com Scandinavia – Estonia GEZE Scandinavia AB eesti filial E-Mail: estonia@geze.com www.geze.ee Ukraine LLC GEZE Ukraine E-Mail: office-ukraine@geze.com www.geze.ua Scandinavia – Finland GEZE Scandinavia AB Filial Finland E-Mail: finland@geze.com www.geze.fi United Arab Emirates/GCC GEZE Middle East E-Mail: gezeme@geze.com www.geze.ae Scandinavia – Latvia GEZE Scandinavia AB Latvijas filiāle E-Mail: latvia@geze.com www.geze.lv United Kingdom GEZE UK Ltd. E-Mail: info.uk@geze.com www.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 China GEZE Industries (Tianjin) Co., Ltd. E-Mail: chinasales@geze.com.cn www.geze.com.cn GEZE Industries (Tianjin) Co., Ltd. Branch Office Shanghai E-Mail: chinasales@geze.com.cn www.geze.com.cn GEZE Industries (Tianjin) Co., Ltd. Branch Office Guangzhou E-Mail: chinasales@geze.com.cn www.geze.com.cn GEZE Industries (Tianjin) Co., Ltd. Branch Office 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: office-hungary@geze.com www.geze.hu Iberia GEZE Iberia S.R.L. E-Mail: info.es@geze.com www.geze.es GEZE GmbH Reinhold-Vöster-Straße 21–29 71229 Leonberg Germany Tel.: 0049 7152 203 … Fax.: 0049 7152 203 310 www.geze.com Scandinavia – Lithuania GEZE Scandinavia AB Filial Lietu. E-Mail: lithuania@geze.com www.geze.lt
Download (.PDF | 7 MB)
GC 339+ 203883-00 … v2 - … GC 339+ Translation of the original operating instructions for device version 0600 Contents Symbols and illustrations … Abbreviations … Product liability … 1 Safety … Intended use … Safety notes … Safety-conscious working … Environmentally conscious working … 2 Description … 3 Work to be done before installation … 4 Installation … 11 … Installing the drive … Safety sensor system … 10 … Installation without accessories … 11 Installation with ceiling installation kit … 12 Installation with mounting bracket … 14 Installation with weather hood … 15 Cabling … 16 … 6 Retrofit … 17 Commissioning … 17 … Protection area … 17 Settings … 19 Teach-in … 19 … Configuration possibilities … 20 … Settings … 21 … 10 Last installation steps … 24 Further installation situations … 25 … .1 … .2 … .3 … .4 … .5 … Scope of delivery … Using the LCD menu … 20 Display during normal function … 20 Menu navigation … 20 Changing ZIP code … 20 Changing and storing values … 21 Checking values using the remote control … 21 Presettings … 21 GC 339+ … Single leaf installation and separate activation … 25 Wall mounting … 27 11 12 13 14 Maintenance … 27 Fault messages and troubleshooting … 28 Technical data … 30 Accessories / spare parts … 31 … GC 339+ Symbols and illustrations Warning notices In these instructions, warning notices are used to warn against material damage and injuries. X Always read and observe these warning notices. X Observe all measures marked with the warning symbol and warning word. Explanation of symbols In these instructions, the following symbols are used for setting and configuration work: Symbol Explanation Press push button Press push button 2× 2x Turn push button Press and turn push button Abbreviations FR Escape and rescue routes IR Infrared IR Active infrared RAD Radar LCD Liquid Crystal Display Main closing edge / secondary closing edge Main closing edge / secondary closing edge Product liability In compliance with the liability of the manufacturer for his products as defined in the German “Product Liability Act”, compliance with the information contained in this brochure (product information and intended use, misuse, product performance, product maintenance, obligations to provide information and instructions) must be ensured. Failure to comply releases the manufacturer from his statutory liability. … GC 339+ Safety … Safety … Intended use The GC 339+ safety sensor may only be used to protect automatic sliding doors and curved sliding doors with GEZE drives. The minimum object size corresponds to the reference object CA according to DIN 18650 or 16005 both upright and lying down. The sensor can be used to secure automatic sliding doors against impact and trapping of the human body. GC 339 … Safety notes à The prescribed mounting, maintenance and repair work must be performed by personnel authorised by GEZE. Any attempts at repairs by unauthorised personnel cancel the factory guarantee. à The device may only be operated with safety extra-low voltage (SELV) with electrically protective separation. à The country-specific laws and regulations are to be observed during safety-related tests. à Make sure that the cover of the drive is fitted correctly and earthed. à If unauthorised changes are made to the system, GEZE cannot be held liable in any way whatsoever for any resulting damage, and the statement of approval for use in escape and rescue routes is no longer valid. à GEZE does not accept any warranty for combinations with third-party products. à Only original GEZE parts may be used for repair and maintenance work. à Observe the latest versions of guidelines, standards and country-specific regulations, in particular: à ASR A1.7 “Doors and gates” à DIN 18650 “Building hardware – Powered pedestrian doors” à DIN EN 16005 “Power operated pedestrian doorsets – Safety in use – Requirements and test methods” à Accident-prevention regulations, especially BGV A1 “General regulations” and BGV A2 “Electrical installations and equipment”. … Safety GC 339+ à The risk assessment and installation of the sensor and the door system in compliance with national and international regulations and door safety standards are the responsibility of the door manufacturer. à The manufacturer cannot accept any responsibility for defective installation or setting of the sensor. à Before leaving the installation, test the sensor for correct function. à Any uses of the device other than those described in this manual do not correspond to the approved purpose and cannot be guaranteed by the manufacturer. … Safety-conscious working à à à à à à à à à … Secure workplace against unauthorised entry. Watch the swivelling range of long system parts. Secure the cover/drive panels against falling. Attach safety stickers to glass leaves. Danger of injury with opened drive. Hair, clothing, cables, etc. can be drawn in by rotating parts. Danger of injury caused by unsecured crushing, impact, drawing-in or shearing spots. Danger of injury due to glass breakage. Danger of injury due to sharp edges in the drive. Danger of injury by freely moving parts during installation. Environmentally conscious working à When disposing of the door system, separate the different materials and have them recycled. … GC 339+ … Description Description The GC 339+ safety sensor has an infrared field for protection. The mutual influence of several sensor systems with hazardous effect is not possible. Unintentional stop signals are possible where detectors are mounted next to one another, since their infrared measuring ranges overlap and each sensor could activate the other. This influence is kept to a minimum by different frequency settings. Variant GC 339+ Black 203858 According to RAL 203859 … Description … 2 … 4 … GC 339+ Cover Setting push button (grey) Button for setting the angle of the IR curtain (red) IR lens (transmitter) … 6 … 8 IR lens (interface) Width adjustment of the IR curtain LCD Main connector GC 339+ Work to be done before installation … Scope of delivery … Work to be done before installation … Installing the drive X Make sure that the cover of the drive is fitted correctly and earthed. … Work to be done before installation … GC 339+ Safety sensor system One combined detector per passage direction is installed on automatic sliding doors. The GC 339+ safety sensor may be required in addition for larger opening widths. For escape and rescue routes: à use protective door leaf if necessary. Heed standards. GC 363+ R GC 339+ GC 363+ R GC 339+ GC 363+ R GC 363+ SF 10 GC 339+ Installation … Installation … Installation without accessories Avoid extreme vibrations. Do not cover the sensor. X Keep away from fluorescent lamps. X Keep away from moving objects. X Avoid highly reflective objects in the infrared range. X Keep a distance of at least 150 mm away from lights, signs or hot air curtains. X X … … 11 Installation … GC 339+ Installation with ceiling installation kit … 68 × 293 m m Ceiling installation kit … 3 12 53 × 244 m m Ceiling installation kit, short GC 339+ Installation … 1 … 4 click … 1 click … click 13 Installation … GC 339+ Installation with mounting bracket … DIN 7981 … × ½“ … 1 … 14 GC 339+ … Installation Installation with weather hood … 2 … 2 … 15 Installation … GC 339+ Cabling X Heed wiring diagrams for the sliding door drives. GC 339+ … GC 339+ BK 110 mA RD … 2 COM + or SIS1 … GND … 24Vsw … GND … 24Vsw SIS2 12 SIS2 PK 11 SIS1 PK … GND … GND BU … 24Vsw … 24Vsw BU 10 TST 10 TST YE YE … 2 IR curtain Test When activated, the output of the GC 339+ is opened (GND applied to the SIO input). X Set the type of contact for SIO … and SIS … to “normally closed contact”. X Test the sensor with GND. For compliance with EN 16005 and DIN 18650, the test output of the door control must be wired and the sensor tested. 16 GC 339+ … Retrofit Retrofit GC 339+ GC 339 BN 110 mA GN … 2 COM + or SIS1 … GND … 24Vsw GY 11 SIS1 PK … BU RD … GND 24Vsw 10 TST WH … GND … 24Vsw SIS2 12 SIS2 … GND … 24Vsw 10 TST BK 110 mA RD … 2 COM + or SIS1 … GND … 24Vsw … GND … 24Vsw SIS2 12 SIS2 PK 11 SIS1 PK … GND … GND BU … 24Vsw … 24Vsw BU 10 TST 10 TST YE YE YE … Commissioning … Protection area The position of the IR curtain in relation to the door can be checked using a spot finder. 17 Commissioning X Activate … visible spots.* GC 339+ X Adjust the tilt angle of the active Yellow LED is flashing infrared detector. on spot finder : Alignment correct. max. … cm 2x max. 20 cm * Visibility depends on the environmental conditions. à Test the width of the required area using a piece of paper (DIN A4), since the spot finder detects over the whole emission area. 18 GC 339+ Commissioning X Testing the emission area. à The “IR: width” parameter must be set identically (see chapter 8). à The complete NSK of the door must be covered. X Set additional IR:Width parameters. Standard-conform sensor setting according to DIN 18650 / EN 16005 Installation height Detection width DIN 18650 / EN 16005 … m … m … m … m … m … m … m … m … m / … m … m / … m … Settings X … Configure the sensor using LCD or remote control (see chapters … and 8). Teach-in X X Before starting teach-in, move out of the infrared field. Before leaving the installation, test the correct sensor installation. 19 Configuration possibilities GC 339+ Teach-in … sec. Teach-in with door movement + … Configuration possibilities … Using the LCD menu … .1 Display during normal function Opening impulse Protection … .2 XXXX Enter password, if set Back 20 … Image shown negative Set contrast = active exit Menu navigation Password … .3 … sec. Changing ZIP code English Deutsch Français Back More Back More Pre-setting GC 339+ … .4 Settings Changing and storing values IR:Immunity IR:Immunity <2.8m … .5 >2.8m … IR:Immunity >2.8m … Checking values using the remote control LCD + … 8 Settings … Presettings X uni Choose the following default settings or configure the settings yourself (see chapter 7). STANDARD: Standard inside and outside installations Pre-setting DIFFICULT ENVIRONMENTS: Difficult installations due to environment or weather Pre-setting SHOPPING STREET: Installations in narrow pedestrian areas Pre-setting Standard … Critical cond. Shopping street 21 22 + IR: Presence time IR: Number IR: Width Back / Continue ADVANCED menu More / Back 15 sec. … 30 sec. … Minimum value for DIN 18650: … min Minimum value for EN 16005: 30 sec. Motion service mode … B normal Critical . … 2 … high < … m Shopping street3 … 3 … 1 … 6 … 8 highest … 5 not compliant with DIN 18650 / EN 16005 higher Outside high To ensure compliance with EN 16005 and DIN 18650, the values … and … must be selected for an installation height of … m or more. … 7 … 2 min. … min. 10 min. 20 min. 60 min. … infinite Service mode = no presence detector for 15 minutes (during maintenance). This value does not permit conformity of the door system with EN 16005 and DIN 18650. … min. … Use different frequencies for sensors which have been installed next to or above one another. Inside normal Factory settings Increased immunity filter + … curtain Increased immunity filter + diversion = movement and presence Not permitted for FR doors! > … m … In addition, always use a screwdriver to set the arrows for field width on the detector. … A IR: Frequency Standard … 1 low … 0 IR: Immunity Default comfort settings Back More BASIC menu Settings GC 339+ … 3 … 1/2 Protection and opening The last 10 errors and day display Displays the spots which trigger detection Signal amplitude at curtain … Signal amplitude at curtain … Error log IR: Spot view IR: C1 ENERG IR: C2 ENERG 3/3 Individual ID number 2/3 ID # 1/3 All parameter values in zipped format (code) In the event of any faults, inform the service employee responsible of this ZIP code. 2/2 … 6 … 8 … ADMIN LANGUAGE RC PASSWORD Reset log OPERATING TIME POWER SUPPLY Full reset … Enter code for administration mode Language of the LCD menu Password for LED and remote control (0000 = no password) Deletes all stored errors Time since 1st voltage activation Power supply at the plug Partial reset (outputs are not reset) 1/2: 1. Sensor in chain of 2; 2/2 2. Sensor in chain of … 1/3: 1st in chain of 3; 2/3 2nd in chain of 3; 3/3 3rd in chain of … (0) Presence detector to protection input (1) Presence detector to protection or opening input Normally Normally Normally Normally open contact closed contact closed contact open contact Normally Normally Normally Normally closed contact open contact closed contact open contact … Reset to factory settings. Off Protection … ZIP DIAGNOSIS menu More / Back Factory Reset Smart Daisy Chain Redirection IR: Output ADVANCED menu GC 339+ Settings 23 Last installation steps … GC 339+ Last installation steps X … 24 Before leaving the installation, check the sensor for correct function. GC 339+ Further installation situations 10 Further installation situations … Single leaf installation and separate activation Installation height * Distance between detector and main closing edge Max. leaf width* Detection width DIN 18650/EN 16005 2000 … 1150 2000 2200 100 1350 2200 2500 250 1650 2500 3000 500 1900 2500 / 3000 3500 750 2150 2500 / 3000 When only one GC 339+ detector is used. If necessary, a GC 339+ with a different frequency is required for further protection. 25 Further installation situations GC 339+ … 2 … 4 … 6 … 2 … 4 … 6 26 Distance Main closing edge Installation height Protection; … m height according to DIN 18650 / EN 16005 Leaf width Detection width GC 339+ … Maintenance Wall mounting According to DIN 18650/EN 16005, the distance between the inner active infrared detectors must not exceed 200 mm. In the case of other dimensions, please contact the sales department first. 11 Installation height a (in mm) Max. reveal depth b (in mm) 2000 2200 2500 3000 3500 395 420 455 515 580 Maintenance X X The visual parts must be cleaned at least once a year. Do not use aggressive cleaning agents or chemicals. 27 Fault messages and troubleshooting 12 GC 339+ Fault messages and troubleshooting LCD display Effect Cause Elimination E1 The ORANGE LED flashes … x The sensor has detected an internal error. X E2 The ORANGE LED flashes … x The power supply is too low or too high. X E4 The ORANGE LED flashes … x The sensor is receiving too little IR energy. X E5 The ORANGE LED flashes … x The sensor is receiving too much IR energy. External elements are interfering with the sensor. X E8 The ORANGE LED flashes … x The IR energy transmitter is defective. X – The ORANGE LED is on The sensor has a memory problem. X – The RED LED flashes quickly after teach-in with door movement The sensor senses the door during teach-in with door movement. X 28 Switch the power supply off and on. X Replace the sensor if the ORANGE LED continues to flash. Check the power supply (in the LCD diagnosis menu). X Check the wiring. Reduce the IR angle. Increase the IR immunity filter (values > … m). X Disable … curtain. X Slightly increase the IR angle. X Check for interfering elements and eliminate if necessary (e.g. lamps or earthing of the drive housing) X Reduce the IR immunity filter to 1, … or 3. Replace the sensor. Switch the power supply off and on. X Replace the sensor if the ORANGE LED lights up again. Check the angle of the IR curtains. X Start teach-in with door movement. Move out of the detection area for this. GC 339+ Fault messages and troubleshooting LCD display Effect Cause Elimination – The RED LED lights up sporadically The sensor is vibrating. X The sensor senses the door. X Elements in the environment are interfering with the sensor. X Check whether the sensor has been fixed in place correctly. X Check the position of cable and cover. Increase IR immunity filter to 3. X Select default setting … and 3. – The LED and the LCD display are off X – The responses of the door and the LED do not correlate X – The LCD display or remote control are not responding. Start teach-in with door movement and change the IR angle. Switch the power supply off and on. X Check the wiring. X The sensor is protected by a password. Check initial configuration. Check the wiring. X Enter the access code. Forgotten the access code? X Switch the power supply on and off during the 1st minute after switch-on to unlock the sensor. 29 Technical data 13 GC 339+ Technical data Power supply 12 V to 24 V, AC ±10%; 12 V to 30 V, DC ±10% Power consumption < … W Installation height … m to … m Temperature range –25 °C to +55 °C, … to 95% relative humidity, non-condensing Protection class IP54 according to EN 60529 Detection mode Presence Typical response time: < 200 ms (max. 500 ms) Technology Active infrared control with background evaluation Spot: … cm x … cm (type) Number of light beams: max. 24 per curtain Number of curtains: … Output Semiconductor relay (standard) (potential-free, polarity-free) Max. switching current: 100 mA Max. switching voltage: 42 V, AC/DC Holdtime: … to … s Test input Signal voltage: Low: < … V, high: > 10 V (max. 30 V) Response time to test query: < … ms (type) Interference influences < 70 dB Type-tested by German Technical supervisory association EC type approval certificate number 44 205 13089625 This product must be disposed of separately from general domestic waste. 30 GC 339+ 14 Accessories / spare parts Accessories / spare parts Material no. Ceiling bracket 153568 Ceiling installation kit 151253 (black) 151254 (white) Ceiling installation kit (short) 200682 Weather hood 158250 Curved adapter 151540 Remote control 100061 31 Accessories / spare parts GC 339+ Material no. Spot finder 112321 Cover 203864 (black) 203866 (according to RAL) IR window 203867 Replacement cable … m 203868 32 GC 339+ Accessories / spare parts 33 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 – Lithuania / Latvia / Estonia E-Mail: baltic-states@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: office-bulgaria@geze.com www.geze.bg China GEZE Industries (Tianjin) Co., Ltd. E-Mail: chinasales@geze.com.cn www.geze.com.cn Romania GEZE Romania S.R.L. E-Mail: office-romania@geze.com www.geze.ro GEZE Industries (Tianjin) Co., Ltd. Branch Office Shanghai E-Mail: chinasales@geze.com.cn www.geze.com.cn Russia OOO GEZE RUS E-Mail: office-russia@geze.com www.geze.ru GEZE Industries (Tianjin) Co., Ltd. Branch Office Guangzhou E-Mail: chinasales@geze.com.cn www.geze.com.cn Scandinavia – Sweden GEZE Scandinavia AB E-Mail: sverige.se@geze.com www.geze.se GEZE Industries (Tianjin) Co., Ltd. Branch Office Beijing E-Mail: chinasales@geze.com.cn www.geze.com.cn Scandinavia – Norway GEZE Scandinavia AB avd. Norge E-Mail: norge.se@geze.com www.geze.no France GEZE France S.A.R.L. E-Mail: france.fr@geze.com www.geze.fr Scandinavia – Denmark GEZE Danmark E-Mail: danmark.se@geze.com www.geze.dk Hungary GEZE Hungary Kft. E-Mail: office-hungary@geze.com www.geze.hu Singapore GEZE (Asia Pacific) Pte, Ltd. E-Mail: gezesea@geze.com.sg www.geze.com Iberia GEZE Iberia S.R.L. E-Mail: info.es@geze.com www.geze.es South Africa GEZE South Africa (Pty) Ltd. E-Mail: info@gezesa.co.za www.geze.co.za India GEZE India Private Ltd. E-Mail: office-india@geze.com www.geze.in Switzerland GEZE Schweiz AG E-Mail: schweiz.ch@geze.com www.geze.ch Italy GEZE Italia S.r.l. Unipersonale E-Mail: italia.it@geze.com www.geze.it Turkey GEZE Kapı ve Pencere Sistemleri E-Mail: office-turkey@geze.com www.geze.com GEZE Engineering Roma S.r.l E-Mail: italia.it@geze.com www.geze.it Ukraine LLC GEZE Ukraine E-Mail: office-ukraine@geze.com www.geze.ua Korea GEZE Korea Ltd. E-Mail: info.kr@geze.com www.geze.com Poland GEZE Polska Sp.z o.o. E-Mail: geze.pl@geze.com www.geze.pl GEZE GmbH Reinhold-Vöster-Straße 21–29 71229 Leonberg Germany Tel.: 0049 7152 203 … Fax: 0049 7152 203 310 www.geze.com 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
Download (.PDF | 3 MB)