Chapters
Table of Contents
Related Manuals for GEZE myGEZE Control
Summary of Contents for GEZE myGEZE Control
- Page 1 Control EN User manual Building automation and control system General information • Hardware components • Software • myGEZE Control Configurator • Config-files • Commissioning a controller system 207493-01 12/2023...
-
Page 2: Table Of Contents
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 0 V DC ...................31 myGEZE Control output terminal 2-channel relay ......................32 myGEZE Control output terminal 4-channel relay ......................34... - Page 3 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...
-
Page 4: Introduction
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 se- quences. means "additional information" 1.2 Reference documents Type Name Material no. Description myGEZE Control-BACnet module types data points 207847... -
Page 5: Safety
The details in this description always refer to the factory standard configurations. Changes to the software con- figuration 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. -
Page 6: Intended Use
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. -
Page 7: Functions And Properties
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 ver- sion and equipment of the control unit. -
Page 8: Standard Control Units
2 EIB/KNX bus terminals are required for connection of the GEZE window technology mod- ules 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. -
Page 9: Installation
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. -
Page 10: Space Required For The Bus Terminals And Components On The Top Hat Rail (Width)
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: ... -
Page 11: Layout Of The Terminals On The Top Hat Rail
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) ... -
Page 12: Approved Type Of Installation / Minimum Distances
Installation myGEZE Control Approved type of installation / minimum distances 4.1.4.1 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 verti- cally through the embedded PC. -
Page 13: Installation / Removal
Installation myGEZE Control Installation / removal 4.1.5.1 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. -
Page 14: Wiring
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. -
Page 15: Connection Of The Control Unit
Installation myGEZE Control 4.2 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! ... -
Page 16: Hardware Description
Hardware description myGEZE Control Hardware description 5.1 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. - Page 17 Hardware description myGEZE Control The CPU 8191 is a control unit with a switched Ethernet port which supports the BACnet protocol. Either E- bus or K-bus terminals can be mounted side by side, the CPU 8191 recognises automatically during booting which system is connected.
-
Page 18: Fig. 8: Dip Switch S101, Switches 1 To 10
Hardware description myGEZE Control Fig. 8: DIP switch S101, switches 1 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 1 to 8. The DIP switches take priority over the set- tings in the operating system. -
Page 19: Mygeze Control Can Master Terminal
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. - Page 20 Hardware description myGEZE Control LED displays The most important statuses of the terminal can be diagnosed quickly on the basis of the LEDs. Colour Meaning green This LED indicates the operating status of the terminal: Status of the EtherCAT State Machine INIT = Initialisation of the terminal;...
-
Page 21: Mygeze Control Can Connector
Control 5.3 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 termi- nating resistor. Two cables can be connected to the connector. This is necessary if the bus terminal is NOT the end of a bus segment. -
Page 22: Fig. 11: Mygeze Control Can Connector Connection Illustration
Hardware description myGEZE Control Fig. 11: myGEZE Control CAN connector connection illustration... -
Page 23: Mygeze Control Knx-System
Hardware description myGEZE Control 5.4 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 4 terminals is necessary for KNX 1x myGEZE Control E-bus coupler ... -
Page 24: Fig. 13: Structure Bus Terminals For Communication With Knx
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. -
Page 25: Fig. 14: Led Indicators Knx
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... -
Page 26: Fig. 15: Example Structure For Communication With Knx
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... -
Page 27: Fig. 16: Led Indicators Knx
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 Col- Chan- Status and meaning flashes K-Bus Run green Lights up weak to strong: K-... -
Page 28: Mygeze Control 8-Channel Digital Input Terminal
Hardware description myGEZE Control 5.5 myGEZE Control 8-channel digital input terminal Fig. 17 : myGEZE Control 8-channel digital input terminal Designation Meaning INPUT 1 Input 1 INPUT 2 Input 2 INPUT 3 Input 3 INPUT 4 Input 4 INPUT 5... -
Page 29: Fig. 18: Led Indicators Knx
Hardware description myGEZE Control LED displays Fig. 18: LED indicators KNX Signal-LED 1 Signal-LED 2 Signal-LED 3 Signal-LED 4 Signal-LED 5 Signal-LED 6 Signal-LED 7 Signal-LED 8 Col- Meaning INPUT 1-8 green Signal voltage “0“ (-3 V ... 5 V) -
Page 30: Mygeze Control Potential Distribution Terminal 24 V Dc
Hardware description myGEZE Control 5.6 myGEZE Control potential distribution terminal 24 V DC Fig. 19 : myGEZE Control potential distribution terminal 24 V DC Power contact +24 V Power contact 0 V The potential distribution terminal makes 16 terminal points with 24 V potential available at the front at the ter- minal contacts. -
Page 31: Mygeze Control Potential Distribution Terminal 0 V Dc
Hardware description myGEZE Control 5.7 myGEZE Control potential distribution terminal 0 V DC Fig. 20: myGEZE Control potential distribution terminal 0 V DC Power contact +24 V Power contact 0 V The potential distribution terminal makes 16 terminal points with 0 V potential available at the front at the ter- minal contacts. -
Page 32: Mygeze Control Output Terminal 2-Channel Relay
Hardware description myGEZE Control 5.8 myGEZE Control output terminal 2-channel relay Fig. 21 : myGEZE Control output terminal 2-channel relay LED relay 1 LED relay 2 Relay, 1 normally open contact Relay, 2 normally open contact Relay, 1 middle contact... - Page 33 Hardware description myGEZE Control LED displays Col- Meaning Relay 1, green Changeover contact between terminal points 2‑3 (channel 1) or 6‑7 (channel 2) relay 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 termi- nal is indicated by light emitting diodes.
-
Page 34: Mygeze Control Output Terminal 4-Channel Relay
Hardware description myGEZE Control 5.9 myGEZE Control output terminal 4-channel relay Fig. 22 : myGEZE Control output terminal 4-channel relay Signal LED 1 Signal LED 2 Signal LED 3 Signal LED 4 Relay, 1 normally open contact Relay, 2 normally open contact... - Page 35 Hardware description myGEZE Control LED displays Col- Meaning Signal 1 - 4 green Terminal points 1-2 (channel 1), 5-6 (channel 2), 3-4 (channel 3) or 7-8 (chan- nel 4) not connected. Terminal points 1-2 (channel 1), 5-6 (channel 2), 3-4 (channel 3) or 7-8 (chan- nel 4) connected.
-
Page 36: Mygeze Control Power Supply Terminal
Hardware description myGEZE Control 5.10 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 0 V feed... -
Page 37: Mygeze Control Coupler
Hardware description myGEZE Control 5.11 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. -
Page 38: Mygeze Control Extension
Hardware description myGEZE Control 5.12 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. -
Page 39: Mygeze Control 2-Port Junction
Hardware description myGEZE Control 5.13 myGEZE Control 2-port junction Fig. 26: myGEZE Control 2-port junction Run LED EtherCAT junction 1 EtherCAT junction 2 The 2-port EtherCAT junction can be used in an EtherCAT terminal line at any point between the EtherCAT ter- minals and makes it possible to build up EtherCAT star topologies. -
Page 40: Mygeze Control Bus End Cover
Information (functional description, wiring diagram or explanation of the LED displays) about the individual ter- minals is available in the Beckhoff information system: https://infosys.beckhoff.com/index.htm 5.15 Terminal name with myGEZE Control assignment to Beckhoff The table below shows the correct assignment of the terminal names: Designation GEZE GmbH... -
Page 41: System Structure And System Limits
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 configu- ration. -
Page 42: Technically Possible Order Of Terminals In The Template Project
System structure and system limits myGEZE Control 6.2 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. -
Page 43: System Limits
Control 6.3 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. -
Page 44: 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. -
Page 45: Licence Model
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 config- uring data. -
Page 46: Putting The Software Into Operation
TwinCAT version Build 4024.35 Card reader or USB interface with card reader for Micro-SD cards myGEZE Control Configurator Version 1.1.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 ... -
Page 47: Mygeze Control Configurator
Putting the software into operation myGEZE Control 7.2 myGEZE Control Configurator Introduction 7.2.1.1 System requirements Windows version 22H2 PowerShell Admin rights for installation Developer mode 7.2.1.2 System behaviour Some of the input fields have check correct content. -
Page 48: Fig. 33: Header In Other Screens
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... -
Page 49: Fig. 34: Input Screen
Putting the software into operation myGEZE Control 7.2.2.2 Controller overview All the parameters for the controller are configured in the controller overview. These serve as unique identifica- tion 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. -
Page 50: Fig. 35: Import Local
Putting the software into operation myGEZE Control Location Description 7.2.2.3 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. -
Page 51: Fig. 36: Import Controller
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... -
Page 52: Fig. 37: Import Successful
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... -
Page 53: Fig. 39: Controller And Local Export
Putting the software into operation myGEZE Control 7.2.2.4 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. -
Page 54: Fig. 40: Device Overview Empty
Putting the software into operation myGEZE Control 7.2.2.5 Functions 7.2.2.5.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. -
Page 55: Fig. 42: Adding Devices - Step 1 (Default Setting)
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. - Page 56 Object name Input from controller field Location {controller-location} Input from controller field {device-type} Device type selected in step 2 {device-id} GEZE device ID, results automatically in step 2 Device description Free text field see above {controller-number} see above {controller-name} see above...
-
Page 57: Fig. 43: Example Of Pattern Entered
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. -
Page 58: Fig. 44: Adding Devices - Step 2
Putting the software into operation myGEZE Control 7.2.2.5.2.2 Step 2 In this step, device type, the number of devices to be created and the technical addressing are defined. The de- vices are then defined using this information together with the patterns prepared in step 1. -
Page 59: Fig. 45: Adding Devices - Step 3.1
Putting the software into operation myGEZE Control Every CAN terminal can contain max. 63 devices. In total, max. 200 devices can be connected dis- tributed 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. -
Page 60: Fig. 46: Adding Devices - Step 4
Putting the software into operation myGEZE Control Fig. 46: Adding devices – step 4 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. -
Page 61: Fig. 47: Editing Devices - Step 4
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 to change to editing mode and adapt individual data records. -
Page 62: Fig. 48: Calendar Function
Putting the software into operation myGEZE Control 7.2.2.5.3 Overview of further functions 7.2.2.5.3.1 Calendar Fig. 48: Calendar function... -
Page 63: Fig. 49: Notification Function (Default)
Putting the software into operation myGEZE Control 7.2.2.5.3.2 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 notifi- cation objects can be used for the data objects of the devices. -
Page 64: Fig. 50: Edit Reporting Classes
Empty == no receiver defined Receiver device Entry 1 …. 4139302 possible Process number with which myGEZE Control transmits the messages Receiver process ID to the receiver device These settings must be made in agreement with the system integrator of the receiver device if nec-... -
Page 65: Fig. 51: State Texts Function
Putting the software into operation myGEZE Control 7.2.2.5.3.3 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. -
Page 66: Fig. 52: Scene Function
Putting the software into operation myGEZE Control 7.2.2.5.3.4 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 differ- ent commands with different functions can be compiled. -
Page 67: Fig. 53: Configuration Of Actions
Putting the software into operation myGEZE Control Adding/editing scene Click the button A further scene class is created Change to editing mode using Carry out settings. Saving takes place automatically here. Adding/editing switching action Change to the settings: Button ... -
Page 68: Installation
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. -
Page 69: Preparations For A New Controller
Putting the software into operation myGEZE Control 7.3 Preparations for a new controller The embedded PC is commissioned via the upper controller Ethernet interface X001. Then the field bus inter- face and all connected devices/bus terminals are configured by TwinCAT 3. After parameter setting, the config- uration is saved on the embedded PC. -
Page 70: Preparations
Putting the software into operation myGEZE Control Preparations hard disk Here, the term stands for the drive that results when the SD card is inserted to the pro- gramming device. Disconnect the controller from the power supply. Remove the micro SD card and insert in a card reader at the PC. -
Page 71: Fig. 55: Edit Route
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 con- cerned. To avoid double assignments, an address between 4 ... 253 can be set here. -
Page 72: Fig. 56: Add Route Dialogue
Putting the software into operation myGEZE Control Fig. 56: Add route dialogue Address Info IP Address Under the radio button must be enabled, otherwise the route will not be added. Click Add Route. Check mark next to Secure ADS: User: GEZE... -
Page 73: Fig. 57: Example Cx745Fd0
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. -
Page 74: Preparing An Application For A Project
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. -
Page 75: Loading A Geze Project
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. -
Page 76: Fig. 60: Tcxaeshell_Openproject 01
Putting the software into operation myGEZE Control File / Open / Open Solution from Archive In TwinCAT, select Fig. 60: TcXaeShell_openProject 01 Select the directory path created previously and confirm “Select folder”. Fig. 61: TcXaeShell_openProject 02... -
Page 77: Fig. 62: Project Selection_Solutionexplorer
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 ana- lyse the connected CAN devices during commissioning. This is explained again in section 7.7. -
Page 78: Fig. 64: Tcxaeshell_Openproject 04
Putting the software into operation myGEZE Control Fig. 64: TcXaeShell_openProject 04... -
Page 79: Fig. 65: Twincat References
7.4.3.1 Checking GEZE software libraries 3 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 Twin- CAT. -
Page 80: Fig. 67: Twincat References
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 disap- pear everywhere. Uninstall Old libraries that are no longer needed can be removed by pressing the button ‘... -
Page 81: Fig. 68: Mygeze_Tcxaeshell_Openproject
Putting the software into operation myGEZE Control 7.4.3.2 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. Disable Right-clicking the terminal and clicking the function ‘... -
Page 82: Fig. 71: Mygeze_Tcxaeshell_Openproject
Putting the software into operation myGEZE Control Fig. 71: myGEZE_TcXaeShell_openProject Confirm prompt about restart with Fig. 72: myGEZE_TcXaeShell_openProject... -
Page 83: Checking Bacnet Objects And Generating Bacnet-Ede File With Twincat
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 3 (BACnetIP). - Page 84 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...
-
Page 85: Generating Bacnet-Ede File
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 3 (BACnetIP). Double-click to start the settings. Export An export is started by clicking To export a BACnet-EDE file, change to the Setting tab. - Page 86 Putting the software into operation myGEZE Control Start export with the OK button Successful generation is indicated by the program.
-
Page 87: Expanded Bacnet Settings In Twincat
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 3 (BACnetIP) Double click ‘myGEZE Control (BACnet server)’ to start the settings Switch to the Setting tab Check to ensure the parameter ‘BACnet ID’... -
Page 88: Setting The Bacnet Udp Port
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 3 (BACnetIP) Double click ‘Device 3 (BACnet IP)’ to start the settings... -
Page 89: Fig. 76: Setting_Bacnet Udp02
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. Configur- The TwinCAT configuration must be activated again in the controller. See the section ‘... -
Page 90: Setting The Bacnet Broadcast Management Device Bbmd
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 3 (BACnetIP). Double-click to start the settings. - Page 91 Putting the software into operation myGEZE Control Several entries can be made here. Save configuration. Configur- The TwinCAT configuration must be activated again in the controller. See the section ‘ ing an application ’...
-
Page 92: Can Monitor Application
This application is included in the template project as another PLC program, and can be loaded into the control- ler system during commissioning. Each GEZE device transmits a lifetime telegram to the CAN bus at a cycle of 1 second. The telegram contains var- ious information, such as the type, bus address, data content. -
Page 93: Fig. 78: Mygeze_Tcxaeshell_Openproject08
Putting the software into operation myGEZE Control Fig. 78: myGEZE_TcXaeShell_openProject08 Confirm prompt about restart with 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. -
Page 94: Fig. 80: Access_Can-Monitoring
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 function- ing correctly. -
Page 95: Fig. 81: Twincat_Log-In
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... -
Page 96: Fig. 83: Can-Monitor List
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. -
Page 97: Fig. 86: Can-Monitor-Device_List.png
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 List List of corresponding CAN terminals is deleted The detected CAN devices are displayed in the device list with their CAN addresses and type designations. -
Page 98: Fig. 87: Can-Monitor-Web-Browser.png
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. -
Page 99: Transportation And Storage
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 0 °C to 30 °C. -
Page 100: Disposal
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. -
Page 101: Technical Data
Control END TERMINAL myGEZE Control 8-channel digital input terminal myGEZE Control potential distribution terminal 24 V myGEZE Control potential distribution terminal 0 V DC myGEZE Control output terminal 2-channel relay myGEZE Control output terminal 4-channel relay myGEZE Control power supply terminal... -
Page 102: List Of Figures
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 0 V DC ....................31 Fig. - Page 103 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.
- Page 104 Email: leonberg.de@geze.com GEZE GmbH Baltic States – Iberia Scandinavia – Norway Niederlassung Süd-Ost Lithuania / Latvia / Estonia GEZE Iberia S.R.L. GEZE Scandinavia AB avd. Norge Tel. +49 (0) 7152 203 6440 Email: baltic-states@geze.com Email: info.es@geze.com Email: norge.se@geze.com Email: muenchen.de@geze.com www.geze.es...
Need help?
Do you have a question about the myGEZE Control and is the answer not in the manual?
Questions and answers