Search filter

MBZ 300

Smoke and heat extraction control panel for smoke and heat extraction drives with a total current consumption of … A to 72 A

Terms & Conditions for software 2019

… software §1 Definitions … . “Software” is to be understood comprehensively and, in addition to embedded software, also includes other standard software which GEZE provides to the customer as independent software, in particular mobile apps. … . “Embedded software” includes firmware, i.e. programs which are permanently installed in GEZE systems and control, regulate and monitor these (e.g. an intelligent door control unit), as well as software which is permanently stored on a certain hardware and is delivered together with it, such as the GEZE cockpit. … . “Approved systems” are door, window and safety systems which, in addition to GEZE systems, may also contain systems and/or components from third-party manufacturers and which are either expressly approved for use with GEZE software or intended for use in accordance with their intended purpose (the intended purpose may result from the individual contract, the product description and/or the documentation as part of a project planning). … . “GEZE Products” is the generic term used for GEZE systems, software and other delivery items of GEZE (e.g. cockpit hardware). … . “Third-party products” include third-party software (e.g. operating systems, databases) and other products from third-party manufacturers (e.g. PCs, laptops) which GEZE supplies to the customer as independent merchandise or integrated in GEZE’s own products. … . “Open source software” are programs which are offered to the general public under Open Source license conditions and which, in particular, permit the comprehensive, “free” use of the program. The freedom from license fees and the openly accessible source code are essential prerequisites for this free usability. … . These General Terms and Conditions (hereinafter referred to as the “Software GTCs”) apply exclusively to business transactions, namely to the delivery and licensing of standard software and – if agreed – to the provision of services relating to the installation, configuration and commissioning of the software. … . The provision of services that go beyond the delivery and licensing as well as the installation, configuration and commissioning of the software (refer to § … below), such as the adaptation of the software to the special needs of the customer, the creation of specific interfaces to already existing programs of the customer, the integration of the software into the building management system and into the interdisciplinary building automation, requires the conclusion of a separate agreement. The software is permanently supported and/or serviced on the basis of a separate service contract, if the customer has commissioned us to do so. … . The software is provided to the customer either as independent application software, for integration into own or third-party programs (e.g. a building management system) or as embedded software, e.g. integrated into GEZE systems in the field of door, window and safety technology.If GEZE provides the customer with the software preinstalled on a piece of hardware, the following provisions of these Software GTCs (e.g. regarding liability for defects) shall also apply correspondingly to the (purchase) provision of the hardware, insofar as these Software GTCs or the respective individual contract do not provide for any deviating regulations. … . For the download of mobile apps from a third party provider for use on mobile devices, for example via the Apple AppStore (for iOS devices) or the Google Play Store (for Android devices), the corresponding conditions of the respective App Store operating company apply in addition to these Software GTCs, in particular the prevailing Apple or Google App Store conditions. If an independent contractual relationship is established between the customer and the App Store operating company, this shall not be affected by these Software GTCs; the Software GTCs shall only apply as a supplement and insofar as they do not contradict the App Store conditions. … . The current version of the Software GTCs shall also apply to all future contracts for the delivery and licensing of software and the provision of accompanying services between GEZE and the customer, even if these are is not explicitly referred to again. … . The type and scope of the licences acquired by the customer and the agreed services as well as the amount of the remuneration shall be determined by the individual contract, in particular by the offer and the order confirmation by GEZE. In the event of contradictions, the customer-specific conditions in the individual contract shall take precedence over these Software GTCs. The customerʼs general terms and conditions shall not apply even if GEZE provides software to the customer without contradicting these conditions. … . For third-party software and other third-party products which GEZE supplies to the customer as independent merchandises and which GEZE separately identifies and mentions their prices in its offers, the contractual and licensing conditions of the respective manufacturer or supplier of the third-party product shall be applicable in the absence of other agreements. These may contain regulations deviating from these Software GTCs regarding the granting of rights of use as well as warranty and liability. GEZE will draw the customerʼs attention to the manufacturerʼs or supplierʼs contract and licence conditions when concluding the contract. If there are loopholes in the contractual and licensing conditions applicable to third-party products, the provisions of these Software GTCs shall apply accordingly. … . For open source software supplied by GEZE to the customer, the contract and licence conditions applicable to the open source software shall apply with priority. In addition, the licence conditions in these Software GTCs shall apply accordingly. The individual open source software components including the applicable open source license conditions (in full text) are listed in detail within the software (e.g. in a Readme file). Upon request, GEZE will also provide the … customer with the applicable open source license conditions outside the software. Within its area of responsibility, the customer shall ensure compliance with the open source license conditions applicable to the open source software. §3 Dates and deadlines; scope of delivery and functions … . The software shall be made available to the customer in the current version at the time of delivery and it is either integrated into a GEZE system, pre-installed on the hardware or provided in the electronic format. Unless otherwise agreed upon, the customer shall not be entitled to the provision of the source code of the software; the only exception to this shall be open source programs whose license conditions expressly intend the provision of the source code. If the software is provided to the customer exclusively in object code, the rights of use granted for the software shall also relate exclusively to the use of the software in object code. If this is necessary to operate the software, the customer shall receive a user manual in printed or electronic format (e.g. as integrated online help) in German and English together with the software. … . The scope of functions and services of the software shall be conclusively derived from the individual contract, the product description as well as the user manual. The software can and may be used for control and use only together with GEZE systems and other approved systems. GEZE assumes no responsibility for the usability and operability of the software for controlling or for its use together with other systems that are not approved by GEZE. GEZE reserves the right to make changes and improvements to the supplied GEZE products as part of technical development or due to changed legal requirements, provided that these do not impair the usability of the GEZE products for the contractually intended purpose. This also applies to changes and improvements which are made after the GEZE product has been handed over to the customer. GEZE further reserves the right to collect and use (non-personal) system data (refer to § … . All copyrights and other protective rights to the software (including all new versions) are exclusively owned by GEZE in relation to the customer. The customer receives only the simple usage rights for the software described in §§ … . Unless otherwise regulated in the individual contract, GEZE shall grant the customer the non-exclusive, unlimited usage rights and to utilise the software (including any customer-specific adaptations and/or extensions) for the customerʼs own purposes agreed upon or presupposed by both contractual partners, subject to a condition precedent and subject to full payment of the agreed remuneration. The special rules in § 14 below shall apply with priority to the provision of software for temporary use (e.g. as part of a subscription model). … . The customer may use the software for the agreed type and number of licenses (e.g. released systems, authorised users). The type and scope of the usage rights granted or the scope of the contents of the licences are specified in detail in GEZEʼs offer or order confirmation. If necessary for use in accordance with the contract, the customer shall be entitled to reproduce the software and make a necessary backup copy, which shall be marked as such by the customer. Copyright and other property right notices within the provided software may not be altered or removed by the customer. … . If the customer acquires the software as an external sales partner of GEZE (e.g. as a specialist planner or system integrator) for the purpose of resale, the customer shall be entitled to resell the software in the ordinary course of business in its own name and on its own account to end customers and to grant them usage rights for the software. The sales partner shall be the sole contractual partner and contact person of the end customer. The sales partner is not authorised to represent GEZE in legal transactions. The sales partner is not permitted to grant its end customers other or more extensive rights to the software those granted to it as far as the software is concerned. In particular, the end customerʼs usage rights also refers to the use of the software exclusively in connection with GEZE systems or other released systems. Furthermore, the sales partner shall not make any contractual promises to the end customer that go beyond or deviate from the agreed quality of the software according to the individual contract and these Software GTCs. … . The customer shall only be entitled to integrate the software into its own or third-party programmes (e.g. a building management system) with the prior written consent of GEZE. Such integration shall take place exclusively via the interfaces provided by GEZE for this purpose. The customer is solely responsible for the compatibility and interoperability of the software with other programs. If GEZE agrees to integrate the software into another program, the customer shall be entitled to distribute the software as part of this superordinate program to end customers and to grant them usage rights, whereby the usage rights granted to the end customer for the software may not exceed the rights granted to the customer; § … . Sub-licensing for a limited period of time, leasing or other forms of temporary transfer of the software to third parties, use in SaaS, outsourcing or computer centre operations or any other use of the software by or for third parties against payment or free of charge require the prior written consent of GEZE. Third parties also include companies affiliated with the customer under company law. … . The customer is not entitled to translate, edit or rework the software beyond the scope permitted by law – in particular the scope regulated by § 69d UrhG (Copyright Act). The decompilation of the software to achieve interoperability of the software with other programs is permissible only within the mandatory limits of § 69e UrhG and if GEZE does not voluntarily provide the necessary information and documents within a reasonable period despite a written request by the customer. … . In the case of the provision of software for demonstration, pilot or test purposes, the customerʼs rights of use shall be limited to such actions that serve to determine the condition of the software and its suitability for the customerʼs purposes. Any further acts of use, in particular the productive operation or the preparation of the productive operation, shall be prohibited without the express consent of GEZE, as shall the creation of copies (including backup copies), the processing and decompilation of the software. The customer is aware that the software provided for pilot or test purposes may be prototypes, beta versions or the like, the accuracy and stability of … which has not yet been fully tested for all purposes under productive operating conditions – there are therefore no claims against GEZE for liability for defects (unless GEZE has deliberately caused a defect or fraudulently concealed it). If a specific test period has been agreed, the customer must completely and irretrievably delete the software after its expiry and confirm this deletion in writing to GEZE upon request. … . After installation of a new version of the software, which is made available to the customer e.g. within the scope of subsequent performance or other services, the usage rights for the previous program version shall become void. … . The customer may transfer the software acquired by GEZE for permanent use to a third party under final abandonment only for its own use. In any case, the transfer of the software requires the prior written consent of GEZE. GEZE will give its consent if the customer submits a written declaration by the third party wherein the third party undertakes to GEZE to comply with the licence conditions applicable to the software, and if the customer assures GEZE in writing that it has transferred all original copies of the software to the third party to the extent of the resale and has deleted all copies made by it. The provision in § … shall apply with priority in case of forwarding of embedded software. … . Any use of the software together with systems other than those released by GEZE and any other use of the software beyond the limits agreed in this § … requires the prior written consent of GEZE. If the use takes place without this consent, GEZE shall invoice the customer for the remuneration incurred for the further use in accordance with its respectively valid price model (also retroactively). In addition, the right to demand claims for damages shall remain reserved. The customer is obliged to notify GEZE in advance of any change affecting his right of use or the agreed remuneration (e.g. imminent sub-licensing). §5 Embedded software … . If the software is integrated into the customerʼs system and made available as a fixed component of hardware supplied by GEZE (e.g. cockpit hardware) or a GEZE system in the field of door, window or safety technology (e.g. control software), the customer may use the software only together with this GEZE product. The use of the software for or together with another product or system requires the prior written consent of GEZE. … . The customer shall only pass on the embedded software and the usage rights for the software to third parties together with the GEZE product in which the software is integrated or for which it is intended. In all other cases, the software may only be passed on to third parties and the transfer or granting of usage rights to third parties with the prior written consent of GEZE. In the event of a permissible transfer of the software, the customer may not retain any copies of the software. … shall also apply to embedded software. §6 Provision of updates … . GEZE reserves the right, e.g., to provide software updates and import them in the GEZE products as a part of service or maintenance works on GEZE products, e.g., if it appears necessary in light of the existing or suspected security loopholes or other risks or is recommended for the optimisation of the GEZE products concerned. The customer already agrees to the import of such updates. If the customer itself is not the owner of the GEZE product concerned, the customer shall obtain the consent of the respective owner. Essential functional limitations are not associated with such updates. … . Unless explicitly stated otherwise in the contract (e.g., service contract) concluded with the customer, the customer has no claim to the provision and installation of regular updates. Furthermore, GEZE is not obliged to regularly check whether the manufacturers of third-party software, which GEZE has supplied as independent merchandise or integrated in GEZE’s own products, have published or provided updates to their products. Statutorily mandatory claims of the customer remain unaffected by the above clause. … . If GEZE provides the customer with updates of the software outside the framework of an existing service contract and without any other remuneration being due for this, these updates are not subject to any independent liability for defects. Legally mandatory claims (e.g., for intentional breaches of duty) and any claims for defects of the customer related to the originally acquired software status remain unaffected, i.e. due to provision of a free update, the customer does not lose any rights in this respect. If GEZE provides the customer with free updates to the software, this does not lead to a restart of limitation periods. §7 Provision of services; cooperation; acceptance … . If GEZE also provides services such as the installation, configuration and commissioning of the software provided (“software-related services”), the scope and quality of the services shall be governed exclusively by the individual contract and the documents confirmed as binding by GEZE. Further customer specifications must first be confirmed in writing by GEZE. Unless expressly agreed otherwise in the individual contract, software adaptations based on source code and customer-specific interface adaptations do not form part of the scope of services. The reference to technical standards serves only to explain or describe performance and in no way constitutes the acceptance of a warranty. … . If the provision of software-related services is agreed in the individual contract, GEZE shall take over the configuration as well as the subsequent installation and commissioning of the software at the customer in accordance with the documentation created (e.g. in a functional specification) in the absence of deviating agreements. The customer shall immediately check any documentation created and provided by GEZE to ensure that the settings described therein fully meet his needs and requirements. If the customer discovers defects, gaps or contradictions during the inspection, he shall inform GEZE immediately and GEZE shall supplement and/or correct the documentation accordingly; otherwise the customer shall release the documentation. The documentation shall be deemed to have been released if the customer does not submit written complaints to GEZE within … - The customer shall ensure that its employees have the necessary qualifications and decision-making powers to provide the cooperation services. - Insofar as this is necessary for the provision of services, the customer shall provide complete and consistent data, information and documents as well as the necessary IT and other infrastructure and shall participate in tests and acceptance tests. - The customer shall create all conditions that are necessary for the proper provision of services in its sphere of operation. In particular, the customer shall grant GEZE access to its systems that need to be connected to the extent necessary. - The customer shall ensure the provision and licensing of required third-party products (hardware, software, databases, etc.) required for the provision of the contractual services. The customer shall be responsible to ensure the proper operation and availability of the third-party products (including any necessary access and processing rights of GEZE), if necessary by means of licence and service contracts with the manufacturers or suppliers of the thirdparty products. - The provision of materials and technical cooperation services must be provided by the customer such that the agreed services can be performed by GEZE without delay and interruption. The customer shall coordinate third party services related to GEZEʼs services in such a way that they do not cause delays, waiting times and/or additional expenses to GEZE. productive use of the software and work results, i.e. has not only put the software into operation for pure test purposes. §8 Remuneration and payment conditions … . In accordance with the following paragraphs, GEZE guarantees that the software supplied and used by the customer in accordance with the contract (including GEZE hardware, if applicable, on which the software is stored) and the work performed or the work results provided (hereinafter collectively referred to as the “contractual objects”) comply with the product or service description and that their use by the customer in accordance with the contract does not conflict with any rights of third parties. … . GEZE guarantees that the contractual objects have the characteristics and functionalities described in the product or service description (e.g. in the offer or in the documentation). The customer can assert claims only due to defects that are reproducible or can be described comprehensibly by the customer. Functional impairments resulting, for example, from improper operation of the software by the customer, from the customerʼs system environment, from a change of operating system (including updates) or from other circumstances in the customerʼs area of risk are not considered to be defects. … . If GEZE provides services according to the customerʼs specifications or adapts components of third parties or of the customer at the customer’s request or integrates them into its own software or GEZE products or connects them with these products, GEZE shall not assume any responsibility for the technical and legal properties of these third-party components or the consequences of the implementation of the customerʼs specifications. - The customer shall observe the applicable technical system requirements for the software, including, for example, regular updating of operating systems and other system and security software, provided these have been supplied to the customer by GEZE. The additional expenses and waiting times of GEZE resulting from the omitted, delayed or improper fulfilment of cooperation obligations shall be invoiced to the customer based on the actual efforts and expenses. This shall also apply in the event that necessary provisions by the customer do not meet GEZEʼs requirements or the customer does not comply with the technical system requirements and this results in additional expenditure. Further claims of GEZE due to improper cooperation shall remain unaffected. … attempts at subsequent performance per defect) or is refused by GEZE, the customer may withdraw from the contract or reduce the remuneration. Due to the complexity of the software, more than … . GEZE warrants that the software provided to the customer is free from third-party property rights and indemnifies the customer against third-party claims based on property rights infringements in accordance with the following provisions. … . If third parties assert claims against the customer arising from the infringement of their property rights as a result of the contractual use of the software by the customer, the customer shall inform GEZE of this immediately in writing and with comprehensive details. GEZE is entitled, but not obliged, to settle the dispute with the third party independently in and out of court. If GEZE makes use of this right, the customer shall support GEZE to an appropriate extent free of charge. The customer shall not acknowledge the claims of the third party on its own initiative. … . If the software has a defect in title at the time of transfer of risk, GEZE shall provide the customer with a legally flawless option to use the software. Alternatively, GEZE may also exchange the affected software for equivalent software if this is reasonable for the customer. If an infringement of third-party property rights and/or a legal dispute with the third party over corresponding claims can be eliminated or avoided by the customer using a more recent software version provided by GEZE, the customer is obliged to take over and use this version within the scope of its duty to minimise damage, unless the customer can prove that the use of the more recent version is unreasonable. … . In particular, GEZE shall not be liable if claims of a third party based on alleged or actual infringements of property rights are based on the fact that the software was modified by the customer or used together with systems not approved by GEZE or in violation of the other contractually agreed conditions of use or for purposes other than those contractually agreed. § 11 Liability … . If GEZE provides the customer with software or renders services without any remuneration, e.g. a free update of the software or during a free test phase, GEZE shall only be liable for intentional and grossly negligent breaches of duty. … . GEZEʼs confidential information especially includes the software in all forms of code and expression including the user manual and other documentations as applicable. The customer is prohibited from obtaining confidential information from GEZE through reverse engineering. Reverse engineering is defined as all activities, including monitoring, testing, inspecting and dismantling the software with the goal of obtaining confidential information. The applicability of mandatory copyright law regulations shall remain unaffected. … . If the customer consents to being named as a reference customer, GEZE may include the name of the customer in a reference list for its own advertising purposes and use the customerʼs company names, brands and logos in printed publications and online, in particular on the GEZE website. § 14 Special rules for temporary software licensing … . If the contractual partners agree on a temporary transfer and use of the software by the customer (e.g. within the framework of a subscription model), this is a rental agreement (in the case of free use, a loan agreement), for which the following special rules shall be applicable with priority over the other provisions of these Software GTCs. If software is made available to the customer via the Internet for online use in the form of Software as a Service or a Cloud solution, further specific conditions (e.g. regarding owed availability) arising from the individual contract or from a service level agreement (SLA) shall apply in addition to these Software GTCs. … . Upon conclusion of a contract for the temporary use of software, the Customer shall be granted a non-exclusive, non-transferable and non-sublicensable right to use the software for its own purposes during the term of the contract; otherwise §§ … . In case of considerable defects in the software provided for temporary use, the customer shall be entitled to terminate the contract for good cause instead of withdrawing from the contract after the failure of subsequent performance or repair, insofar as the customer cannot reasonably be expected to adhere to the contract due to such defect. Otherwise, §§ … and 10 shall apply accordingly to the liability for defects in quality and title of the software. GEZE shall only be liable for defects in the software already existing at the time of conclusion of the contract, deviating from the legal regulation of § 536a of the BGB (German Civil Code), if GEZE is responsible for such defects. … . Unless otherwise agreed, the contractual partners may terminate contracts for the temporary use of software with a notice period of … . The customerʼs right to use the software shall automatically terminate upon termination of the contract. The customer is obliged to completely and permanently delete all copies of the software and to return all data carriers, documentation and other documents provided. At GEZEʼs request, the customer shall confirm the complete and final deletion of the software in writing. § 15 Final provisions … . An export of the software by the customer may be subject to national and international regulations of Export Control Law. In the event of resale or other export, the customer shall be responsible for compliance with any export requirements (e.g. obtaining official permits) and shall bear the associated costs. The customer shall indemnify GEZE against all costs and damages in connection with culpable violations of export control regulations by the customer. … . If individual provisions of these Software GTCs or the individual contract are or become invalid, or if the contract contains a loophole, this shall not affect the validity of the remaining provisions. The 7

User manual MBZ 300 configuration software

… Software Program for configuring RWA systems comprising components from the MBZ 300 series made by GEZE GmbH Software version …  MBZ 300 Configuration Software Table of contents … Software installation … Notes on the software … 21 MBZ 300 Configuration Software  … MBZ 300 Configuration Software … Settings by software and VdS … Sequence for commissioning and configuration by software … 49 The control unit is not shown correctly in the software (modules missing etc.) … 49 The software cannot be started completely. / The software „crashes“ during loading of the control unit … 50 MBZ 300 Configuration Software … About this document About this document This user manual describes the the operation of the GEZE-MBZ 300 Configuration Software. … Software installation MBZ 300 Configuration Software After MBZ 300 software training you are registered in the user list. You then receive the software and licence via the GEZE customer portal. Please make sure you always work with the latest software. Please go to the GEZE customer portal: www.geze-partnerlogin.de Please install the software on a laptop which is used to commission the MBZ 300: àà You need administrator rights for installation àà Install the program in a file with writing rights for the user àà Make sure that the driver is also installed. (If this is not done automatically, the driver can be installed later from the directory „...\Programme\GEZE\MBZ300\Driver“ when an MBZ 300 control unit is installed.) … .1 View licence This level does not have to be cleared. After installation the software is automatically in the view level. The following possibilities are available: àà Display of system or module status àà Display of the log entries àà Setting of the charging current on the basis of the battery capacity àà When a weather module is installed: Setting of the type of peripherals connected and selection of wind speed àà Setting of the system time … MBZ 300 Configuration Software General information The following appears: … .2 Reading out the activation code (alternative without control unit connected) In the Windows start menu there is a shortcut to an external authorisation tool which can be used for authorisation without starting the program and connected to the control unit. Path for pre-installed software installation: START -> All programs -> GEZE -> MBZ 300 -> Authorisation Here, the activation code for a new licence can be read out. In addition, if an older program version was licensed this tool can transmit the existing PC „licence key“ to newly installed software by clicking the „Authorisation“ button. … .3 Requesting licence key Please go to the GEZE customer portal as a registered software user: www.geze-partnerlogin.de There, you can enter the activation code and request the key under „Authorisation“. It can be marked using the mouse, for example, copied to the clipboard using <strg>+<c> and then pasted using <strg>+<v>. Your contact responsible will send you the suitable licence key by email as soon as possible. If you have any questions, please contact MBZ300@geze.com. … Notes on the software Always use the latest configuration software together with the latest firmware! Update the firmware as required. Please note the two different program versions: àà „Individual control unit“ àà „Networked control unit“ (see „Firmware update“ and „Procedure for configuration of a control unit“) … .1 MBZ 300 Configuration Software What happens after the system has been connected via USB As soon as the system has been connected to the PC, the settings and the current system configuration are read out. Depending on the size of the system, this procedure can take a few seconds. The software is ready when the info-area of the main window (bottom left) displays „Startup OK“: Please always operate the laptop on battery power to ensure the electrical isolation between the mains of the control unit and the power supply of the laptop. The program has to be terminated before the USB connection cable between the PC and MBZ300 is removed. … MBZ 300 Configuration Software … .4 General information Menu functions A wide range of different software functions can be executed via the menu in the header. Navigation is by left mouse click, analogue to familiar programs. File Load configuration... A saved configuration (*.EMB) is loaded to the software interface. It is not yet written into the system. XX Please check the settings after loading. XX The following settings are not saved in the file and must be adapted manually àà PM: àà Size of the battery àà Number of PMEs àà WM: àà Sensors àà Wind thresholds àà CM: àà Maintenance time àà Time àà Password See „System configuration“ for how to write the configuration into the system The current configuration is saved in a file (*.EMB) on the PC. Like „Save configuration...“ but under a new file name. see „Authorisation“ Protect the system by means of a password. Page set-up. Documentation of the system acceptance protocol/check list. XX Save configuration... Save configuration as ... Authorisation... Set Password of the selected device... Printer settings... Printer preview selected device... Printer preview of all devices... Print the configuration of the selected device... Print the configuration of all devices... Generate a PDF of the selected device configuration... Generate a PDF containing all device configurations... Exit Note: In order to get all current status entries in the PDF as well, click in all modules (status page) before generation / printing to ensure the current status displays are requested. Terminates the program … General information MBZ 300 Configuration Software System configuration Load default configuration of the directly The system configuration is reset to factory settings. The self-teaching connected control unit... function is re-activated. Refer also to „ „Buttons“ on the interface“ Note: All the settings are lost! Write configuration permanently to the devices Load configuration from the device The configuration in the software interface is transmitted to the system. Refer also to „ „Buttons“ on the interface“ Reads the existing configuration out of the system and displays it in the software interface. If a configuration in the software interface is not saved it is lost. Reboot the directly connected device... Reboots the connected system. It is necessary to reboot the system when all the required changes have been written into the system and a check on system behaviour is to be made. = equivalent to: switching the control unit voltage-free for at least 30 seconds (without rechargeable battery). … .5 „Buttons“ on the interface As an alternative to items from the header menu, some functions are available as buttons. The functions of the button are described below. „Clear“ The system configuration is reset to factory settings. Refer also to „System configuration“. Note: All the settings are lost! „Save to CM“ The configuration in the software interface is transmitted to the system. Refer also to „System configuration“. „Undo“ Changes to the configuration in the software interface are reversed. Note: This only affects the current view on the PC, not the control unit. For this, the configuration has to be re-transmitted to the control unit. Whether or not a property can be modified depends on the user level. 10 MBZ 300 Configuration Software … MBZ 300 Configuration Software Firmware update Carry out the firmware update using the „Update“ program. You will find the program in the Start menu. Please proceed as follows: XX Connect the control unit via USB XX Start Update program. Path for pre-installed software installation: START -> All programs -> GEZE -> MBZ 300 -> Update -> Update The Update program contains the following: àà Intermediate saving of the configuration àà Updating of all firmware statuses of the modules installed XX 12 àà Loading of the configuration which has been saved intermediately Starting of the software „Individual control unit“. The following settings are not saved intermediately and must be adapted manually: àà PM: Battery size and number of PMEs àà WM: Sensors and wind thresholds àà CM: Maintenance time and time àà Password MBZ 300 Configuration Software … Preparation of an individual control unit [1] Ensure the system is voltage-free (no 230V connection, no battery) [2] Insert further modules if appropriate XX [3] Check wiring between the modules àà Power supply àà Bus cable (NEVER connect or disconnect when the control unit is switched on!) àà Ensure that the cables are fitted correctly. àà Connect drives, push buttons etc. (can also be done later) àà Make sure that all line monitoring devices are connected properly XX [4] Activate the 230V supply XX [5] Connect the rechargeable battery XX [6] Keep the reset push button on the CM pressed for 20s (until all modules are flashing - not longer!). This ensures the modules are addressed correctly. This process is essential when the hardware (modules and order) has been changed. XX [7] Connect USB cable to CM and connect to the laptop. XX [8] Start the software „Individual control unit“ (please make sure you always use the current version (see „Software installation“). XX [9] Check the firmware version of the control unit to make sure it is up-to-date. XX [10] Carry out firmware update if necessary (see „Firmware update“) XX [11] Load the default settings (see „System configuration“) Standard groups (alarm / ventilation / weather groups) are formed along module settings through the selflearning function (connection of modules) or default loading. Caution: all previous settings are deleted! XX [12] Adapt battery size and number of PMEs (see „Battery settings“). XX [13] Set the individual configuration: à If new modules are added or the order is changed, the settings must be adjusted manually directly in the software. à If the hardware has not changed, you can load an already saved *.EMB-file. Prerequisite is a suitable (same) hardware configuration! Please check the settings (see Section … .4) and go to the next step. XX [14] Transmit to the control unit. XX [15] Reboot the directly connected control unit. XX [16] Check settings. XX [17] Test functions (please note interactions with GLT, BMA, relaying!). XX [18] Save central configuration as *.EMB and *.PDF and archive for the project. XX [19] In the control unit, note that the configuration has been adapted by software (user, date and rough description – print out PDF and enclose if appropriate). XX [20] Terminate software, then remove USB cable. XX XX … Several control units networked via CAN (see „CAN parameters“) The procedure is in addition to / instead of the above-described points as follows: Set up the USB connection to each individual control unit and start the software „Individual control unit“ every time. XX [12a]: For every individual control unit with CM CAN parameters set the address and the number of control units. XX Transmit to the control unit XX Reboot the directly connected control unit XX It is advisable to mark the control units according to their addresses XX [12b]: At this point at the latest, make sure that the CAN cables incl. terminator jumper are correctly connected between the control units XX Establish a USB connection to any control unit XX Open the „Networked control units“ software XX zu [13]: Set the configurations and particularly comprehensive functions now and transmit to the control units. XX zu [18]: Save the configuration file as *.EMB (several files) and *.PDF. 13 Control system … MBZ 300 Configuration Software Control system The individual setting possibilities for the various modules are described below. The standard value is always in bold type. … RealTime_Log - control unit The program displays the entries in the „RealTime_Log“ memory. This lists events which have had at least alarm or error status. Various selection possibilities can be used to set which events and messages are to be recorded. The setting does not represent a filter of the view, rather it specifies what is actually to be saved. Granularity: Fine (everything) All events are saved e.g. including ventilation control Information Alarm Error All messages are saved Alarm and error messages are saved Error messages are saved Note: The granularity settings must be written into the system for the changes to take effect Read all available entries Empty textbox Save textbox content... Empty the devices log All the messages available for the control unit are read. Caution: This can take a very long time! Only deletes the display on the software interface. Saves the contents of the fault memory in a file. (.TXT) Deletes the fault memory of the control unit. The log is a circular buffer (the oldest data are overwritten) with sufficient capacity (depending on granularity). Tip: Use the log memory for trouble shooting and for functional test (granularity „Fine“). 14 MBZ 300 Configuration Software … MBZ 300 Configuration Software Properties – PM Akkuüberwachung [•] Fault indication Fault indication is outputted via the malfunction LED or e.g. via the signal relay with corresponding parameter settings. [] Battery control deactivated No reaction in the event of a malfunction. [] Fault indication and windows close A fault indication is outputted and all drive modules are actuated to CLOSE. [] Fault indication and windows open A fault indication is outputted and all drive modules are actuated to OPEN. [] Deep discharge protection In battery operation, the control unit does not operate until the rechargeable battery is completely discharged (deep discharge), it is switched off before this point in order to protect the rechargeable battery (this deep discharge protection triggers at around … V) e.g. if the power failure can last for longer than 72 h. Note: Fault display on the PM is still active. Desired charging characteristic [•] Temperature-guided [] Constant The charging voltage is adapted depending on the temperature. Should always be used. The charging voltage is independent of the ambient temperature. Mains power failure [•] [] [] Energy-saving mode Close all windows Allow venting Ventilation signals are suppressed, weather sensors are not evaluated All drive modules are actuated to CLOSE in the event of a power failure. Ventilation is allowed. The back-up time is shortened by ventilation movements in battery operation. Battery settings Number of connected PMEs 0..2 (Standard: 0) Adaptation of the number of PMEs if any changes have been made to the power supply If the system has been extended by further power supplies, a corresponding number of PME modules have also been added. This number must be configured here (range 0..2) so that fault evaluation works correctly. 16 MBZ 300 Configuration Software Battery type: PM - Power module … Ah 10 Ah 12 Ah 17 Ah 24 Ah 38 Ah The corresponding battery type must be set After the default values have been loaded, this setting must always be checked and adapted if necessary! CAUTION If the battery type is set incorrectly this can lead to excessively high charging current. Excessively high charging current can damage the rechargeable battery. The rechargeable battery will become very hot: Risk of explosion! The parameters must always be checked following a software update on a control unit. 17 CM - Control module MBZ 300 Configuration Software … Power RWA Close-Button Power Push button status 18 Minimum value Standard value Maximum value 22 V 25,3 V 28 V 900 µA (standby) 1250 µA (standby) 3000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 1250 µA (standby) 3000 µA (standby) Depending on the switched status NA (not actuated), OPEN, CLOSE or STOP MBZ 300 Configuration Software … .2 MBZ 300 Configuration Software Automatic step control [] Use mechanism Interval time: When this option is activated the drives are only actuated in the „OPEN“ direction for the time step set. This function must be combined with the ventilation push button function „self-locking“. This has no influence on the RWA function. … will automatically reset the control unit. MBZ 300 Configuration Software CM - Control module àà The fire alarm system function covers resetting the alarm status and CLOSING the drives. àà If „Emergency-close and detector line reset“ is activated in combination with the fire alarm function, the smoke detector lines are switched voltage-free for the time set under „Smoke detector reset period“ (see CM „Operating parameters“) when the fire alarm signal is no longer received. … .2 MBZ 300 Configuration Software Maintenance Next maintenance The date for the next routine system maintenance check can be set here using a date selection list. Signalling: [•] Note: There is no date set as standard. [] [] [] [] CM fault LED flashing Any maintenance due is signalled by the fault LED flashing on the CM. CM fault LED flashes and Maintenance due is signalled by the fault LED flashing on the messaging relay is set CM and by the messaging relay being switched. Ventilation open blocked on When maintenance is due, ventilation movement in the all DMs OPEN direction is blocked on all DMs. Flashing + ventilation open Maintenance due is signalled by the fault LED on the CM flasblocked hing and ventilation movement in the OPEN direction being blocked on all DMs. Flashing + relay + ventilation Maintenance due is signalled by the fault LED on the CM flasopen blocked hing, by the messaging relay being switched and ventilation movement in the OPEN direction being blocked on all DMs. Note: GEZE recommends variant … line error smoke detector line 2. Common fault of the network system The system-wide issue of faults is activated. Faults are shown on all RWA buttons in the network system (all control unit modules and control units networked via CAN). Note: àà When the collective fault is activated, the LED setting „Fault“ in the CM and SM properties is set to „Alternative functions“ and the drop-down menu is deactivated. Caution: àà When the collective fault is subsequently deactivated the function of the LED must be restored manually. (see „LEDs“ in CM and SM) [] Use relay for signalling too The messaging relays of all CM and SM are switched in the event of collective fault. Note: àà Changeover contact NC/NO is inverted! àà When the relays are activated, the setting „Trigger messaging relay for:“ in CM and SM is set to „Never“ and the dropdown menu is deactivated. Caution: àà When „Use relay for signalling too“ is subsequently deactivated, the settings must be restored manually. 22 MBZ 300 Configuration Software CM - Control module àà With the MBZ 300, post cycle control means CLOSE briefly every … Purpose MBZ 300 Configuration Software àà Actuation of 24V drives for RWA and/or ventilation purposes. àà Evaluation of ventilation signals and status contacts. àà Monitoring of the drive cable (see MBZ 300 installation instructions). … V (with load) 0,8 V 1V 3V Depending on the switched status NA (not actuated), L_L_OPEN, L_L_CLOSE or L_L_ STOP Concerns the signal inputs: Depending on the switched status NA (not actuated), E_A_ OPEN (status contact 1) or E_A_CLOSE (status contact 2) Counts how often the line has been switched open and closed MBZ 300 Configuration Software DM - Drive module … .2 MBZ 300 Configuration Software Automatic step control [] Interval time Use mechanism When this option is activated the drives are actuated in the „OPEN“ direction for the time step set. This function must be combined with the ventilation push button function „self-locking“. This has no influence on the RWA function. 0..120 s Movement interval of the interval time. (Standard: … sec = permanent operation Restoring a switAfter a higher priority signal has dropped, the drive line is returned to the status of a ched status of lower pending. lower priority signal again. priority Example: A ventilation signal OPEN is pending due to a temperature sensor, the windows are open. A higher priority ventilation signal CLOSE transmitted by a weather station closes the windows. If the ventilation signal of the weather station drops further and the ventilation signal of the temperature sensor is still pending, the windows open again. Emergency-open for wind directions (for SHEV according to EN 12101-2) Specifies the evaluated wind directions for which the system actuates the drive line of the DM in the event of an alarm. [x] [x] [x] [x] [x] [x] [x] [x] 26 N NO O SO S SW W NW The wind direction is evaluated according to VdS 3122. In the event of an alarm and a wind direction during which the windows should not be opened, the windows close if they have been opened by ventilation. This function guarantees a wind direction dependent actuation of SHEVs (natural smoke and heat exhaust ventilators) in the event of an alarm according to EN 12101-2. MBZ 300 Configuration Software DM - Drive module This function is only possible when a weather module is available and the wind direction sensor (wind direction finder) is connected. (see „WM - Weather module“) … .8 Status contacts The status contacts of DM and DME are not available in the PC software … . 28 MBZ 300 Configuration Software MBZ 300 Configuration Software DM - Drive module 29 DME drive module - extended version MBZ 300 Configuration Software … Properties - DME and configuration possibilities (Partner level) Cf. DM: „Configuration possibilities“ 30 MBZ 300 Configuration Software 10 SM Sensor module SM Sensor module … Power RWA Close-Button Power Push button status Minimum value Standard value Maximum value 22 V 25,3 V 28 V 900 µA (standby) 1250 µA (standby) 3000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 1250 µA (standby) 3000 µA (standby) Depending on the switched status NA (not actuated), OPEN, CLOSE or STOP 31 SM Sensor module MBZ 300 Configuration Software … .1 Vent switch function In the standard configuration the push button input of the sensor module in a venting group is linked with all the drive modules in this smoke zone. This venting group has a higher priority than the push buttons connected directly to the drive modules (= central push button for the smoke zone). Other venting group assignment (see „Venting groups“). Function setting Behaviour with button OPEN pressed [] Note: Always select OPEN and / or CLOSE in addition. Without this definition the push button continues to be in self-locking mode. Dead-man [] [•] Behaviour with button CLOSE Stop by pressed open The DMs switch to "open" If "CLOSE" is not set to In biased-off direction: Reas long as the button is biased-off, the DMs switch to lease the push button pressed. If the button is the "close" direction of travel released, the DMs switch off permanently. If only one is active, the other again. is in self-locking mode STOP [] close If "OPEN" is not set to The DMs switch to "close" as = both push buttons at the biased-off, the DMs switch long as the button is pressed. same time to the "open" direction of If the button is released, the travel permanently. DMs switch off again. Self-locking Modules switch permaModules switch permanently Press both push buttons at nently to "open" direction to "close" direction of travel. the same time of travel. [] Start/stop Modules switch permanent- Modules switch permanently If both directions are actiopen push ly to „open“ direction of to „close“ direction of travel. vated: button travel. Pressing the button Stop = Press both push butagain switches the lines off tons at the same time Stop = Press the same button again (stop). again [] Start/stop Modules switch permanent- Modules switch permanently close push ly to „open“ direction of to „close“ direction of travel. button travel. Pressing the button again Stop = Press both push but- switches the lines off again tons at the same time (stop). Note: If the function „stop through same push button“ is desired: Check OPEN and CLOSE so that the ventilation push button function makes sense. „Permanently“ means the set „drive line switch-off time“ at maximum 32 MBZ 300 Configuration Software SM Sensor module … will automatically reset the control unit. 33 SM Sensor module MBZ 300 Configuration Software àà The fire alarm system function covers resetting the alarm status and CLOSING the drives. àà If „Emergency-close and detector line reset“ is activated in combination with the fire alarm function, the smoke detector lines are switched voltage-free for the time set under „Smoke detector reset period“ (see „Operating parameters“) when the fire alarm signal is no longer received. … .10 LEDs The function of the LEDs on the RWA button are shown here. If „alternative function“ is selected, the display of the LEDs depends on the special system functions set. 34 MBZ 300 Configuration Software 11 WM - Weather module … MBZ 300 Configuration Software Properties – WM If a weather module is installed, a weather group is automatically generated which contains all the DMs in the control unit. (see „Weather groups“) … .2 Wind speed (for ventilation) Specifies the threshold for the wind speed from which the windows are closed in the ventilation case. [] high threshold value 0,0..20,0 m/s (Standard: 6,0 m/s) [] medium threshold value 0,0..20,0 m/s (Standard: 4,0 m/s) [•] lower threshold value 0,0..20,0 m/s (Standard: 2,0 m/s) The threshold values can also be freely set. The default setting is „lower threshold value“ in order to guarantee maximum possible protection from wind damage. 36 MBZ 300 Configuration Software ERM relay module … Minimum value 22 V Standard value Maximum value NA 25,3 V 28 V Counts how often the relays have been switched. 37 ERM relay module MBZ 300 Configuration Software … .1 General relay configuration Ventilation and weather groups, smoke zone and faults can be signalled at the same time by a relay. It must be noted that the signalling of smoke zones takes priority over ventilation/weather groups. àà If the function of a relay is redefined by software, the relay remains in its current switched position until a switching signal occurs. This means that an incorrect state can be displayed before this first switching takes place. àà With multiple assignment of a relay please note that the functions are prioritised automatically (alarm signal > ventilation / weather > fault). … No additional function No collective fault function is assigned to the relay. Collective fault of all DMs on selected control units Collective fault of all SMs on selected control units Collective fault of all DMs+SMs on selected control units Collective fault of all PMs on selected control units Collective fault of all DMs+PMs on selected control units Collective fault of all SMs+PMs on selected control units Collective fault of all SMs+PMs+DMs on selected control units Faults of all drive modules at selected control units are displayed. Faults of all sensor modules* at selected control units are displayed. Faults of all drive and sensor modules* at selected control units are displayed. Faults of all power modules at selected control units are displayed. Faults of all drive and power modules at selected control units are displayed. Faults of all sensor* and power modules at selected control units are displayed. Faults of all sensor*, drive and power modules at selected control units are displayed. Control unit 0control unit x (in the case of control units networked via CAN) * The „SM sensor modules“ include the control module. For a collective fault to be outputted, at least one control unit must be selected, even if it is a single control unit. The collective fault can be assigned to a relay as a single or additional function. The additional function has a lower priority than the display of smoke zones, ventilation and weather groups. This means: If a collective fault is parameterised for a relay which displays the actuation of a smoke zone, for example, resetting the smoke zone switches the relay off even if a fault is still pending. 38 MBZ 300 Configuration Software ERM relay module … .4 Signalling ventilation signals (venting groups) As soon as a relay module is integrated in a control unit, additional configuration possibilities appear in the venting groups. Here, the statuses of the ventilation can be assigned to the relays. „Open“, „Close“ and „Stop“ are available for each relay. If parameters are set for a relay to display Open or Close, then Open or Close is active until there is either a change in direction of movement or a „Stop“ signal is issued. The stop signal is only pending when the system is stopped manually, i.e. àà Stop by pressing the Open/Close push buttons at the same time, àà Stop by active function „Start/Stop Open/Close push button“ or àà Stop by active biased-off function 39 ERM relay module MBZ 300 Configuration Software àà Automatic switch-off by the drive is not registered as „Stop“. àà Important note: This is an indicator of ventilation signals – not window statuses! Only the vent switch signals are shown. The opening of windows by alarm or closing by alarm resetting is not shown. àà Tip: A real window position can only be mapped by end position contacts (e.g. Reed contacts). … .5 Signalling of weather groups The signalling of weather groups takes place analogue to the smoke zones. 40 MBZ 300 Configuration Software 13 Smoke zones Smoke zones The term smoke zone (or „alarm group“) is used in the context of the MBZ 300 for a group which is activated by specific alarm signals. … Smoke zone details The smoke zones can be formed flexibly. 41 Smoke zones MBZ 300 Configuration Software … .6 Description A text describing the smoke zone can be entered. 42 MBZ 300 Configuration Software 14 Venting groups Venting groups … .2 Drive lines Here you can select which drive lines are assigned to this venting group. 43 Venting groups MBZ 300 Configuration Software … .4 Description A text describing the venting group can be entered. 44 MBZ 300 Configuration Software 15 Weather groups Weather groups The weather group is only applicable for ventilation. … .4 Description A text describing the weather group can be entered. 45 Higher-order smoke zones / venting groups / weather groups 16 MBZ 300 Configuration Software Higher-order smoke zones / venting groups / weather groups Example: If several control units are networked via CAN, higher-order groups are available. Here, inputs and drive lines from several control units can be summarised in groups. (See chapter „Smoke zones“ / „Venting groups“ / „Weather groups“) CAUTION: An input signal (detector line, venting line or weather signal) may only occur in a maximum of one group! Multiple use is not possible, otherwise behaviour is not predictable. Please check the local groups for the individual control units and delete if necessary! 46 MBZ 300 Configuration Software 17 General information … Settings by software and VdS General information Some settings which can be made by software lead to the VdS certificate no longer being valid in the broadest sense, since monitoring functions which represent requirements according to VdS can be switched off specifically through configuration. Please consider this when carrying out customised configuration of the MBZ 300. Settings affected: àà VdS post cycle control àà Line monitoring of the detector lines (deactivation of fault evaluation) … Cabling: Several smoke zones, networking and inter-control unit functions CAN networking allows smoke zones to be defined where individual or several control units are assigned to several functional sections, in other words: the installation site of the control unit and the detector and drives may be distributed in different areas. This local distribution may lead to the basic requirement according to the guideline for circuit systems (MLAR) for monitoring the emergency power control unit no longer being given. If this is the case, suitable compensatory measures must be taken (e.g. E30 cabling). 18 Testing the system The configured MBZ 300 must be tested in such a way that neither people nor the technical equipment are endangered. Please confirm the commissioning / functional test and regular maintenance testing in the test log (GEZE material number 102060 (GB)). 47 FAQs 19 MBZ 300 Configuration Software FAQs … Sequence for commissioning and configuration by software see „Procedure for configuration of a control unit“ … .2 The control unit is not shown correctly in the software (modules missing etc.) XX XX XX XX XX XX Keep the reset push button on the CM pressed for 20s (until all modules are flashing - not longer!). This ensures the modules are addressed correctly. This process is essential when the hardware (modules and order) has been changed. Connect USB cable to CM and connect to the laptop. Start the software „Individual control unit“ (please make sure you always use the current version (see Software installation) Check the firmware version of the control unit to make sure it is up-to-date Carry out firmware update if necessary (see „Firmware update“) Load the default settings (see System configuration) CAUTION: all previous settings are deleted! XX XX XX Adapt battery size and number of PMEs (see Battery settg) Set the individual configuration Transmit to the control unit … .3 The software cannot be started completely. / The software „crashes“ during loading of the control unit. XX XX XX XX XX Terminate the program using the task manager if necessary. Remove the USB cable Check the USB cable and the USB connection. If the cable or connection is faulty the connection cannot be established properly and the software cannot load the configuration completely. Please also check your computer load capacity and the assignment of the correct driver (re-assign if necessary see „Software installation“). Reboot the software and connect the USB cable again. … Does the module sequence matter? The software allows numerous different settings; nevertheless we recommend setting up the modules as closely as possible to standard configuration (better overview): àà A new smoke zone begins with CM / SM àà Do not set SM at the end àà WM in last position … Trouble shooting where several control units are in one CAN network XX XX 48 „Divide and rule“: Only connect the local with the nearest control unit (check CAN clamps!). àà terminate this section àà disconnect all other CAN connections àà open the „networked control units“ software àà check whether both control units are available The points must be repeated accordingly for the other sections. MBZ 300 Configuration Software FAQs … min for a total of Drive lines switch-off time = X (Stan30 min: dard: 300s) 120s Follow-up time limit OPEN for ventilati- 3s CLOSE - OPEN on = Y (e.g. 40s) Drive lines switch-off time = X (Standard: 300s) Automatic step control = Z (e.g. 10s) CLOSE (reset) OPEN CLOSE X (300s) X (300s) Y (40s X (300s) every time Z (10s) 49 Meaning of the log entries 20 MBZ 300 Configuration Software Meaning of the log entries see „RealTime_Log - control unit“ All possible log entries are listed here. During operation, only a limited selection of these will actually occur. The list also includes the logging level from which this type of message can occur. The logging levels are classified as follows. A lower (or finer) logging level automatically includes the higher-order logging level entries. In other words: Error entries are always included in the log when this is set to alarm. Here are the possible logging levels in order from the lowest to the highest. LOG_FINE LOG_INFO LOG_ALARM LOG_ERROR %d SM %d The finest logging level: almost everything is logged. This provides a precise overview of the processes in the system, but the high memory requirements mean that the log does not extend far into the past. Somewhat more details are reported about switching processes in the system. Faults and alarm states and their triggering are reported. Only faults and errors are recorded. stands for any number, this is usually the module ID which this log entry refers to SM_0 is the CM. CM and SM are equated here. Log entry Bus Fault Exception, System HALT! CAN Main: CANSendMsg() Error! CAN XmitQueue: Error %d! CAN: buff emptied! Granularity LOG_ERROR LOG_ERROR LOG_ERROR LOG_ERROR CAN: kfg fkt mismatch! LOG_ERROR CAN: MBOX_CAN buffer full LOG_ERROR CAN: mbusb, buffer processing problem! LOG_ERROR CAN: mbusb, eval_cmd LOG_ERROR buffer problem! CAN: mbusb, timeout! LOG_ERROR CAN: Modbus commu- LOG_ERROR nication failure %d! CAN: rec array overflow! LOG_ERROR CAN: rec queue full! LOG_ERROR CAN: reception while processing! LOG_ERROR canf_mbm_writeread(): LOG_ERROR resending... canf_mbm_writeread(): LOG_ERROR too many resends! 50 Fault pattern A fault occurred during access to the system bus. The CAN interface of this control unit could not send a message. This control unit could not transmit a CAN message Attempt is being made to transmit something that isn't there. A command has not been received completely. The control unit cannot keep up with transmission. Note Hardware fault? Replace CM. Check the CAN module Check the CAN module Reboot CM Is compensated. Has the CAN system been configured properly, are there any "meaningless" rules? Buffer is overflowing during remote servicing If one of the control units of a control unit via CAN. does not react, reboot this and start the configuration process again. This control unit does not understand a com- Do all the control units mand that came via CAN. have the same firmware version? A message on the CAN has not been answered Loose wire? Terminators inserted on the CAN modules? CAN cannot be read properly. CAN module OK? Can only occur when someone actively interferes with data transfer. Do all the control unit have the same firmware version, what else is attached to the CAN cable? Too many different commands have been sent Has the CAN system been to this control unit. configured properly, are there any "meaningless" rules? Unknown data were received during CAN Do all the control units command processing. have the same firmware version? A message is being sent again. Is not really a fault in the strict sense, since it is compensated. If it occurs often, however, it is a sign that there is something wrong with the CAN. A message has been repeated too often wit- Is a control unit switched hout an answer being received. off, disconnected? (Cable?) MBZ 300 Configuration Software Meaning of the log entries canf_xmit_konf(): CAN- LOG_ERROR SendMsg timeout! canfi_eval_cmd, requesting resend... LOG_ERROR canfi_mbusb_received(): MBOX_CAN error %d! CANSendMsgQ(): Queue full! Clock Source failure (Clock Security System)!!! CM IWDG-RESET!!! LOG_ERROR cmb.msg[0]: %d LOG_ERROR Creating autoKonfig, eepCfg ver.> 3... LOG_INFO Creating autoKonfig... LOG_INFO DM %d: Alarm AUF DM %d: ALARM bei deaktiviertem DG! LOG_ALARM LOG_ALARM LOG_ERROR LOG_ERROR LOG_ERROR DM %d: Alarm reset bei LOG_ALARM deaktiviertem DG! DM %d: Alarm reset, DG LOG_ALARM spannungslos DM %d: Alarm ZU LOG_ALARM DM %d: ALARM, DG aktiviert DM %d: ALARM, DG aktiviert DM %d: ALARM, HM freigegeben DM %d: ALARM, HM freigegeben LOG_ALARM DM %d: Alarm-Reset LOG_LOG_ ALARM DM %d: AUF DM %d: AUF (LZM) LOG_INFO LOG_INFO DM %d: AUF (LZM) LOG_INFO DM %d: Auto-ZU DM %d: HM aktiviert LOG_INFO LOG_INFO LOG_ALARM LOG_ALARM LOG_ALARM A message could not be sent in time, possible Should not occur, if it data loss. happens during a storage process - repeat this. The command has not been received comple- Is not really a fault in the tely and is being requested again. strict sense, since it is compensated. If it occurs often, however, it is a sign that there is something wrong with the CAN. An unexpected error has occurred during Check the CAN module reception of a CAN message. This control unit could not send a CAN message due to buffer status. The clock is faulty. Check the CAN module Hardware fault? Replace CM. If the system "crashes" or the watchdog thinks Should not occur. Firmthis is the case, it triggers a reboot. ware update, otherwise replace DM. This unknown message has been received. Do all the control units have the same firmware version? After the start an unknown configuration was ... found in the EEPROM, a new configuration which matches the modules found is being created and used. After the start a new configuration which ... matches the modules found is being created and used. This DM is opening due to an RWA case. ... Alarm was/was to be triggered at this DM, but The pressure gas actusince the pressure gas actuator was deactiva- ator should have been ted this did not work. activated. The alarm status of a DM has been reset. But Switch the pressure gas the pressure gas actuator connected to the actuator on. DM is still deactivated. The alarm status of a DM has been reset. But Connect the pressure gas the pressure gas actuator connected to the actuator to the power DM is still voltage-free. supply. This DM is being emergency-closed due to an ... RWA case. The pressure gas actuator on this DM has been ... activated. This DM activates the pressure gas actuator. Analogue to opening a window. The magnetic clamp on this DM has been ... released (i.e. voltage supply interrupted) The alarm status of a DM has been reset. But Switch the pressure gas the pressure gas actuator connected to the actuator on. DM is still deactivated. With this DM the alarm status has been can... celled, it is open and can be moved closed by the ventilation. This DM is now opening. ... If this DM is not permitted to open further ... and its maximum open running time has been reached (follow-up time limit). If this DM is not permitted to open further ... and its maximum open running time has been reached (follow-up time limit). A DM closes automatically. ... This DM was activated due to an RWA case. ... 51 Meaning of the log entries MBZ 300 Configuration Software DM %d: HMinit AUF DM %d: ist schon AUF LOG_INFO LOG_FINE DM %d: ist schon ZU LOG_FINE DM %d: Linie spannungslos LOG_FINE DM %d: LT AUF LOG_FINE DM %d: LT STOP LOG_FINE DM %d: LT ZU LOG_FINE DM %d: LZMinit ZU DM %d: LZM-Stop LOG_FINE LOG_INFO DM %d: no key LOG_FINE DM %d: NOTAUF LOG_ALARM DM %d: STOP DM %d: ZU DM%d-PWR-Supply Error %d, Value 403: %d Eeprom was erased... LOG_INFO LOG_INFO LOG_ERROR LOG_INFO Funktion existiert nicht LOG_ERROR ID %d ! 52 A timer has been started for this DM. If this DM is not permitted to open further and its maximum open running time has been reached This DM is already closed and is thus not closing again. The voltage supply for the DM drive line has been switched off (after the drive line switchoff time has expired!) The push button of the DM has registered pressure on the Open push button. The push button of the DM has registered pressure on the Stop push button. The push button of the DM has registered pressure on the Close push button. The running time mode closes the DM. The running time mode has "Stop pressed" on one DM. The push button of the DM has registered a push button being released. The DM moves the motor into the emergencyopen position due to an RWA case. This DM is now stopping. This DM is now closing. The voltage supply to the DM is not OK. Indicates that the log entries found are faulty and the log thus had to be deleted. This can happen if a configuration from a too recent configuration program is used by firmware that is too old. The configuration requires that functions which are not available in the firmware should be used. The CPU has jumped to a position where it is not allowed to land. No communication was possible with y of x modules in one cycle. ... ... ... ... ... ... ... ... ... ... ... ... ... Measure voltage, eliminate fault, or DM faulty. This can happen when power supply and rechargeable battery both fail and the voltage suddenly drops severely. In other words when there is not sufficient voltage available during log writing. CM Firmware update. Hard Fault Exception System HALT! IOM Poll Error %d/%d missing LOG_ERROR IOM %d: couldn't reset selector! IOM %d: couldn't set selector! Loading Eeprom Konfig... mbf_querysystem(): konfig present, %d IOM's are missing! Mem Manage Exception, System HALT! LOG_ERROR If this occurs often the DM is faulty. Fault in the CM firmware or hardware fault. If this occurs sporadically it is not a problem, since it is compensated, but if it occurs permanently one or more module(s) is(are) faulty. Replace DM LOG_ERROR If this occurs often the DM is faulty. Replace DM LOG_INFO NMI Exception LOG_ERROR PM Poll Error LOG_ERROR After the start the configuration was loaded ... from the EEPROM and is being used. Modules in the control unit have been recon- Re-establish the default nected or disconnected since the last start-up. configuration and address/ configure correctly. Fault in memory management: Poor firmware memory faulty, VdS entries available? No access to the clock. Hardware fault? Replace CM. Communication with the PM not possible via Hardware fault? Replace the Modbus. PM/CM? LOG_ERROR LOG_ERROR LOG_ERROR MBZ 300 Configuration Software Meaning of the log entries PM(E): Akkufehler LOG_ERROR The PM is missing a rechargeable battery. PM(E): Netzfehler LOG_ERROR PM(E): OK LOG_INFO PM/IOM Poll ok! LOG_ERROR PM: Netz und Akku fehlt LOG_ERROR RTC count lost!!! Semaphore deadlock: %s, err: %d LOG_ERROR LOG_ERROR SM %d LED Stoerung: %d LOG_ERROR SM %d: Alarm-Reset LOG_ALARM SM %d: BMZ an RM1 NOT_ZU SM %d: BMZ an RM2 NOT_ZU SM %d: BMZ an RM2 NOT_ZU SM %d: Linienfehler Handmelder! SM %d: Linienfehler Not-Zu! SM %d: Linienfehler RM1! SM %d: Linienfehler RM2! SM %d: LT AUF LOG_ALARM SM %d: LT STOP LOG_INFO SM %d: LT ZU LOG_INFO SM %d: no key LOG_INFO SM %d: NOT_AUF HSE LOG_ALARM The PM or the control unit is no longer drawing current from the power supply. The PM has mains power and rechargeable battery again. (This message can of course only occur if one of these elements was missing.) Only occurs in conjunction with IOM Poll Error %d/%d missing and means that the PM was OK in this context. A fault has occurred on the SM but there is no reaction on account of the energy-saving mode. The CM no longer has the current time. A resource of the CM operating system could not be released, as a result the CAN system can no longer function, for example. Signals that the fault LED has been set at this DM, this can be caused by a lot of reasons. If it occurs in conjunction with "Stoerung DM %d: %d", for example, "Stoerung DM %d: %d" is the triggering element. It can also be a problem with the detector line of the SM, however. In the default configuration, setting the fault LED automatically switches the messaging relay. Reset has been pressed and the alarm status reset on this SM. Emergency-CLOSE was triggered with smoke detector line … line fault was detected on this SM. An open pressure on the vent switch was detected on this SM. A stop pressure on the vent switch was detected on this SM. A closed pressure on the vent switch was detected on this SM. A release, in other words no push button pressure in the actual sense, was detected on the vent switch of this SM. Emergency-open with the RWA button was detected on this SM. LOG_ALARM LOG_ALARM LOG_ERROR LOG_ERROR LOG_ERROR LOG_ERROR LOG_INFO Check the rechargeable battery + cables, use the configuration software to check whether PMEs and battery capacity have been set properly. If this does not help, replace the PMEs or the PM on the basis of the values shown on the PM status page. Check power supply, PM. ... No error Desired behaviour... Synchronise with the PC. Rebooting the CM can eliminate the problem. If "Stoerung DM %d: %d" was logged first, please see this point, otherwise check line fault (test adapter?), if the test is negative replace the SM. ... ... ... ... Check the cable, if test negative replace the SM. Check the cable, if test negative replace the SM. Check the cable, if test negative replace the SM. Check the cable, if test negative replace the SM. ... ... ... ... ... 53 Meaning of the log entries MBZ 300 Configuration Software SM %d: NOT_AUF RM LOG_ALARM Emergency-open with one of the smoke detector lines was triggered on this SM. Emergency-close was detected on this SM. Emergency-close was detected on this SM. The reset tester was detected on this SM. The self-test routines (VdS) have established a fault. ... SM %d: NOT_ZU SM %d: NOT_ZU (res) SM%d: Mreset STL: >>> RAM Error (March C- Run-time check) STL: Abnormal Clock Test routine termination STL: Class B variable error (clock test) STL: Clock Source failure (Run-time) STL: Control Flow Error (main loop) STL: Control Flow error in RAM-Test-ISR STL: Run-time FLASH CRC Error STL: Run-time FLASH CRC OK, %d cycles STL: SRAM-Check OK, %d cycles STL: Stack overflow LOG_ALARM LOG_ALARM LOG_INFO LOG_ERROR LOG_ERROR The self-test routines (VdS) have established a fault. Hardware fault? Replace CM. LOG_ERROR Hardware fault? Replace CM. Hardware fault? Replace CM. Hardware fault? Replace CM. Hardware fault? Replace CM. Hardware fault? Replace CM. ... LOG_ERROR The self-test routines (VdS) have established a fault. The self-test routines (VdS) have established a fault on the clock. The self-test routines (VdS) have established a fault. The self-test routines (VdS) have established a fault. The self-test routines (VdS) have established a fault in the flash. The self-test routine flash check (VdS) has been carried out successfully x times. The self-test routine flash check (VdS) has been carried out successfully x times. The self-test routines (VdS) caused a fault. STL: Start-up CPU Test Failure STL: TOO MANY REBOOT FAILURES, LOCKING UP!!! Stoerung bei PF DM %d: %d LOG_ERROR The CPU is no longer working properly LOG_ERROR For some reason the CM has rebooted very often, a fault has been established. LOG_ERROR Stoerung bei PF SM %d: %d LOG_ERROR Stoerung DM %d: %d LOG_ERROR A fault has occurred on the DM but there is no reaction on account of the energy-saving mode. A fault has occurred on the SM but there is no reaction on account of the energy-saving mode. Indicates a fault on this DM, usually a detector line fault, with some old DMs there was another fault here which made this occur briefly, but it was not a fault. Testmode initiated... LOG_ERROR LOG_ERROR LOG_ERROR LOG_ERROR LOG_ERROR LOG_FINE LOG_FINE Testmode: KonfigTask LOG_ERROR abgebrochen... TimerEvent %d: loest LOG_FINE aus Usage Fault Exception, LOG_ERROR System HALT 54 WM %d: kein Regen LOG_INFO WM %d: REGEN WM %d: WIND LOG_INFO LOG_INFO WM %d: WIND T%d LOG_INFO This is not CM firmware in the actual sense. There is only a test program in the CM. This is not CM firmware in the actual sense. There is only a test program in the CM. If a timer triggers a subsequent action. The bits did not make sense to the CPU. A WM has recognised that it has stopped raining. A WM has detected rain. A WM has detected wind from a certain direction. Shows that the WM has detected wind. ... ... ... Hardware fault? Replace CM. ... Hardware fault? Replace CM. Hardware fault, replace CM. Hardware fault? Replace CM. Desired behaviour... Desired behaviour... If a line fault can be excluded and the fault only occurs briefly, we recommend a DM firmware update. If neither of these approaches was successful, the DM affected should be replaced. Firmware update with the boot loader. Firmware update with the boot loader. ... Firmware OK? Flash again? Hardware fault? Replace CM. ... ... ... ... MBZ 300 Configuration Software WM %d: Wind unterhalb Schwelle WM %d: WRG fehlt! Meaning of the log entries LOG_INFO LOG_ERROR The wind has fallen under the threshold on ... one of the WMs. There is a wind direction finder configured in a Is the sensor/WM, cable WM but the WM cannot detect it. working? WM / test sensor => replace. 55 Germany GEZE Sonderkonstruktionen GmbH Planken

User manual MBZ 300 configuration software

… software Configuration program for the RWA system comprising components of the MBZ 300 series Software version … 153427-01 EN User manual  MBZ 300 Configuration software Contents … Software installation … Notes on the software … 22 MBZ 300 Configuration software  … MBZ 300 Configuration software … Settings by software and VdS … Sequence for commissioning and configuration by software … 51 The control unit is not shown correctly in the software (modules missing etc.) … 51 The software cannot be started completely. / The software “crashes” during loading of the control unit … 52 MBZ 300 Configuration software … About this document About this document This user manual describes operation of the GEZE MBZ 300 configuration software. … Runtime and the Visual C 2008 redistribution package. These packages are installed automatically by the installer package if they are not already in the system. Connector type Mini-B Acrobat Reader for displaying the help file and the configuration data export in PDF format Compatibility table: Version of configuration software … Software installation MBZ 300 Configuration software After MBZ 300 software training you are registered in the user list. You then receive the software and licence via the GEZE customer portal. Please make sure you always work with the latest software. You will find the latest software at the GEZE customer portal: www.geze-partnerlogin.de. Please install the software on a laptop which is used for commissioning the MBZ 300: àà you need administrator rights for installation. àà Install the program in a folder with writing rights for the user àà Make sure that the driver is also installed. (If this is not done automatically, the driver can be installed later from the directory “...\Programme\GEZE\MBZ300\Driver” when an MBZ 300 control unit is connected.) … .1 View licence This level does not have to be cleared. After installation the software is automatically in the view level. The following possibilities are available: àà Display of system or module status àà Display log entries àà Setting of the charging current on the basis of the battery capacity àà When a weather module is installed: Setting of the type of peripherals connected + wind speed àà Setting of the system time … MBZ 300 Configuration software … .2 General information Request licence key As a registered software user, go to the GEZE customer portal: www.geze-partnerlogin.de. There, click “Authorisation”, enter the activation code and request the key. Your contact responsible will send you the suitable licence key by mail as soon as possible. You can highlight the key e.g. with the mouse, copy it to the clipboard using <strg>+<c> and paste it to the respective field using <strg>+<v>. If you have any questions, please contact MBZ300@geze.com. … .3 Entering a licence key If the authorisation window has been closed in the meantime, request it again as described above. Enter the licence key in the “Licence key” field. After you have clicked “Authorisation” the extended functionality will be available. 90 days before the licence expires, the following window will appear as a reminder when you start the software: … Notes on the software For existing, configured MBZ 300 control units GEZE recommends that you continue to use the configuration software version … . A firmware update is not required here. For new installations always use the latest configuration software together with the latest firmware. Update the firmware as required (see the chapters “Firmware update” and “Procedure for configuration of a control unit”). MBZ 300 control units that have been configured using configuration software version … are reset to the factory settings by the firmware update and use of the configuration software … .1 What happens after the system has been connected via USB As soon as the system has been connected to the PC, the settings and the current system configuration are read out. Depending on the size of the system, this procedure can take a few seconds. The software is ready when the info-area of the main window (bottom left) displays “System loading OK”: The program has to be terminated before the USB connection cable between the PC and MBZ 300 is removed. … .3 MBZ 300 Configuration software Navigation bar All the modules connected in the system are displayed in a tree view, and from the basic licence onwards the groups are listed: The properties of each module can be reached by clicking the symbol on the left of the respective module. … .4 Menu functions A wide range of different software functions can be executed via the menu in the header. Navigation is by left mouse click, analogue to familiar programs. File … MBZ 300 Configuration software General information Load configuration... A saved configuration (*.MBZ) is loaded to the software interface. It is not yet written into the system. XX Check settings after loading. XX Adapt the following settings manually, since these are not saved in the file. àà PM: àà Size of the battery àà Number of PMEs àà WM: àà Sensors àà Wind thresholds àà CM: àà Maintenance time àà Time Save configuration... àà Password See the chapter “System configuration” for how to write the configuration in the system. The current configuration is saved in a file (*.MBZ) on the PC. Save configuration as ... Like “Save configuration...” but under a new file name. Authorisation... See the chapter “Authorisation” Set password of the selected control unit Remove password of the selected control unit selected control unit was changed by... Preview selected control unit... Preview all control units... Generate a PDF of the selected control unit configuration... Generate a PDF containing all control unit configurations... Exit Protect the system by means of a password. Delete the system password Display of hard drive ID and date of the last change XX Terminates the program. System configuration Load default configuration of the directly The system configuration is reset to factory settings. The self-teaching funcconnected control unit... tion is re-activated. Refer also to the chapter ““Buttons” on the interface” Note: All the settings are lost! (The data memory of the control module is deleted). Write settings permanently to the control The configuration on the software interface is transmitted to the control unit unit. Refer also to the chapter ““Buttons” on the interface”. Load configuration from the control unit Reads the existing configuration out of the system and displays it on the software interface. If a configuration on the software interface is not saved it is lost. Reboot the directly connected device... Reboots the connected system. It is necessary to reboot the system when all the required changes have been written into the system and a check on system behaviour is to be made. = equivalent to: switching the control unit voltage-free for at least 30 seconds (without rechargeable battery). … General information MBZ 300 Configuration software Language The following languages can be selected: àà German àà English àà French àà Turkish àà Chinese Help Help (in German or English) is started directly from the software, the respective PDF document is saved in the software project directory. The help file with the specific language is automatically loaded with the Acrobat Reader. About … .5 “Buttons” on the interface As an alternative to items from the header menu, some functions are available as buttons. The functions of the buttons is described below. “Clear” The control unit configuration is reset to factory settings. Refer also to the chapter “System configuration”. Note: All the settings are lost! “Save to CM” The configuration on the software interface is transmitted to the control unit. Refer also to the chapter “System configuration”. “Undo” Changes to the configuration on the software interface are reversed. Note: This only affects the current view on the PC, not the control unit. For this, the configuration has to be re-transmitted to the control unit. Whether or not a property can be modified depends on the user level. 10 MBZ 300 Configuration software … MBZ 300 Configuration software Firmware update Please note the compatible PC software and firmware versions (see chapter … ). Before updating a control unit that has already been configured, please check whether the required functions are available / realised in the same way in the other firmware Changing the firmware to an earlier version is possible and works in the same way as an update. Carry out the firmware update using the “Update” program. You will find the program in the Start menu. Please proceed as follows: XX Connect the control unit via USB. XX Start the update program. Path for pre-installed software installation: START -> All programs -> GEZE -> MBZ 300 -> Update -> Update The update program contains the following: àà Intermediate saving of the configuration àà Updating of all firmware statuses of the modules installed XX 12 àà Loading of the configuration which has been saved intermediately Start the software “Individual control unit”. The following settings are not saved intermediately and must be adapted manually: àà PM: Battery size and number of PMEs àà WM: Sensors and wind thresholds àà CM: Maintenance time and time àà Password MBZ 300 Configuration software … [1] Ensure the system is voltage-free (no 230 V connection, no rechargeable battery). [2] Insert further modules if appropriate. [3] Check cabling between the modules. àà Power supply àà Bus cable (Caution: NEVER connect or disconnect with the control unit switched on!) àà Ensure that the cables are fitted correctly. àà Connect drives, push buttons etc. (can also be done later) àà Make sure that all line monitoring devices are connected properly [4] Activate 230 V supply. [5] Connect rechargeable battery. [6] Keep the reset push button on the CM pressed for 20 s (until all modules are flashing - not longer!). This ensures the modules are addressed correctly. This process is essential when the hardware (modules and order) has been changed. [7] Connect USB cable to CM and connect to the laptop. [8] Start software. Select access to single directly connected or all interconnected control units. Make sure that you always use the latest version (see the chapter “Software installation”). [9] (Only for initial start-up) Check firmware version of the control unit to make sure it is up-to-date. [10] (Only for initial start-up or when necessary) Carry out firmware update if appropriate (see the chapter “Firmware update”). [11] (Only for initial start-up or when necessary) Load default settings (see the chapter “System configuration”). Standard groups (alarm / ventilation / weather groups) are formed along module settings through the self-learning function (connection of modules) or default loading. Caution: all previous settings are deleted! [12] Adapt battery size and number of PMEs (see the chapter “Rechargeable battery settings”). [13] Set individual configuration (either directly or by loading a saved *.MBZ file with the same module set-up). [14] Transmit to the control unit. [15] Reboot the directly connected control unit. [16] Check settings. [17] Test functions (please note interactions with building managment system, BMA, relaying!) [18] Save central configuration as *.MBZ and *.PDF and archive for the project. [19] In the control unit, note that the configuration has been adapted by software (user, date and rough description – print out PDF and enclose if appropriate). [20] Terminate software, then remove USB cable Several control units networked via CAN For this, establish the USB connection to each individual control unit and start the software each time (refer also to the chapter “CAN parameters”). The procedure is in addition to / instead of the above points as follows: XX [12a]: Set the address and number of control units for each individual control unit under CM CAN parameters. XX Transmit to the control unit. XX Reboot the directly connected control unit. XX It is advisable to mark the control units according to their addresses. XX [12b]: At this point at the latest, make sure that the CAN cables incl. terminator jumper are correctly connected between the control units XX Establish a USB connection to any control unit. XX Open the “Networked control units” software. XX Re [13]: Set the configurations and comprehensive functions in particular now and transmit to the control units. XX Re [18]: Save the configuration file as *.MBZ (several files) and *.PDF. 13 Control unit … MBZ 300 Configuration software Control unit The individual adjustment options for the various modules are described below. The standard value is always in bold type. … RealTime_Log - control unit The program displays the entries in the “RealTime_Log” memory. This lists events which have had at least alarm or fault status. Various selection possibilities can be used to set which events and messages are to be recorded. The setting does not represent a filter of the view, rather it specifies what is actually to be saved. Granularity: Note: Fine (everything) All events are saved e.g. including ventilation control Information All messages are saved Alarm Alarm and fault messages are saved Fault Fault messages are saved The granularity settings must be written into the system for the changes to take effect. read all available entries Empty text box All the messages available for the control unit are read. Please note: This can take a very long time! Only deletes the display on the software interface. Save text box content... Saves the fault memory to a file (.TXT). Empty the control unit Deletes the fault memory of the control unit. The log is a circular buffer (the oldest data are overwritten) with sufficient capacity (depending on granularity). Tip: Use the log memory for trouble shooting and for functional test (granularity “Fine”). Refer also to the chapter “Meaning of the log entries”. Info: The log memory is large enough to comprise around 1500 entries. The setting is irrelevant. 14 Last control unit changes The date and the drive serial number of the computer which made the most recent change are displayed here. The drive serial number is part of the authorisation key. Text for information and comments of this control unit A text describing the control unit can be entered, e.g. what work a service technician has most recently done on the control unit. MBZ 300 Configuration software … .2 MBZ 300 Configuration software Minimum value Standard value approx. 24 V (depending on … Properties – PM Rechargeable battery control [•] Fault message [] Rechargeable battery control deactivated [] [] 16 Fault message and windows CLOSE Fault message and windows OPEN A fault message is outputted via the fault LED or e.g. via the messaging relay with corresponding parameter settings. No reaction in the event of a fault. For ventilation application only or operation without rechargeable battery A fault message is outputted and all drive modules are actuated to CLOSE. A fault message is outputted and all drive modules are actuated to OPEN. MBZ 300 Configuration software [] PM - Power module Rechargeable battery protection In battery operation the control unit does not run with all modules until the rechargeable battery is completely discharged (deep discharge). All modules apart from the PM are switched off beforehand to protect the rechargeable battery (this protection triggers at approx. … Ah 10 Ah 12 Ah (default) 17 Ah 24 Ah 38 Ah The corresponding rechargeable battery type must be set After the default values have been loaded, this setting must always be checked and adapted if necessary! ATTENTION If the rechargeable battery type is set incorrectly this can lead to excessively high charging current. Excessively high charging current can damage the rechargeable battery. The rechargeable battery will become very hot: Risk of explosion! The parameters must always be checked following a software update on a control unit. 17 CM - Control module MBZ 300 Configuration software … V 28 V 900 µA (standby) 1250 µA (standby) 3000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 1250 µA (standby) 3000 µA (standby) Depending on the switched status NA (not actuated), OPEN, CLOSE or STOP MBZ 300 Configuration software … .2 MBZ 300 Configuration software Interval mechanism [] Use mechanism Interval time: When this option is activated the drives are only actuated in the “OPEN” direction for the time step set. This has no influence on the RWA function. If actuation is in the “CLOSE” direction, the motor line is active over the whole drive line switch-off time. Note: If biased-off is deactivated. The drive line switch-off time of the controlled DMs is automatically set to 300 s so that it is possible to close the window under any circumstances. … are thus activated. An alarm is triggered in the event of a line break or short-circuit on detector line 1. MBZ 300 Configuration software … .9 Messaging relay Selection of the message which leads to the messaging relay switching. trigger in case of: Never Rechargeable battery fault Mains voltage fault Control unit fault No reaction. Note: Should be set if the relay is used to report expiry of maintenance time. The closer contact is closed when the rechargeable battery monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The closer contact is closed when the mains voltage monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The messaging relay switches in the event of a fault within the control unit group (concerns faults on modules of the control unit). Closer is closed in the fault-free status. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). 21 CM - Control module MBZ 300 Configuration software Common alarm of the group General alarm (default) Restricted group alarm Delayed group alarm Impulse for alarm reset The messaging relay switches following a common fault. The closer contact is closed in the fault-free status. When a common fault has been eliminated, the fault status is reset after a delay of 60 s. The fault status is reset immediately on the control unit where the fault occurred. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). The messaging relay switches when there is an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! If all alarm groups are deleted, the setting “Never” will appear after the next charging cycle. The messaging relay switches on for 300 s in the event of an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! The messaging relay switches on after a … .1 System Time: synchronize 22 Set the system time. (No distinction is made between summer and winter time) The system time can be compared with the time on the PC connected by pressing the “synchronize” button. Please make sure that the PC time is correct. MBZ 300 Configuration software CM - Control module The system time is used for the time stamp for messages in the RealTime log. Note: If the system is too different, a warning window will appear when the software is started. … s) Smoke detector recovery time 0...1000 ms after smoke detector reset (standard: 500 ms) Smoke detectors are reset by switching off the supply voltage to the detector for the period set here. The detector line evaluation is deactivated for the time given here following reset of a smoke detector line. During the smoke detector reset no detector line evaluation takes place, including on the RWA button lines. 23 DM - Drive module [] MBZ 300 Configuration software Common fault of the network system (with CAN network) The system-wide output of faults is activated. Faults are shown on all RWA buttons in the network system (all control unit modules and control units networked via CAN). Note: àà When the common fault is activated, the LED setting “Fault” in the CM and SM properties is set to “Alternative functions” and the drop-down menu is deactivated. Please note: àà When the common fault is subsequently deactivated the function of the LED must be restored manually. (-> see the chapters “LEDs” on CM and SM) … Electrical properties Max. drive current: 10 A Input switching voltage: 24 V DC OK ! MBZ300 DM 24 MBZ 300 Configuration software … .2 Module status text The current operating mode is displayed here. The current status and faults are displayed, as described in the installation instructions. 25 DM - Drive module MBZ 300 Configuration software … s, second time = 10 s, third time = 15 s etc.). If actuation is in the “CLOSE” direction, the motor line is active over the whole drive line switch-off time. 26 MBZ 300 Configuration software … s = Permanent operation [] Restoring a switched After a higher priority signal has dropped, the drive line is returned to the status of a pendstatus of lower ing lower priority signal again. priority Example: A ventilation signal OPEN is pending due to a temperature sensor, the windows are open. A higher priority ventilation signal CLOSE transmitted by a weather station closes the windows. If the ventilation signal of the weather station drops further and the ventilation signal of the temperature sensor is still pending, the windows open again. 27 DM - Drive module MBZ 300 Configuration software Note: It is not possible to use motor lines with different modes of operation in one joint alarm group. However, new alarm groups with the same sensor lines and different motor lines can be formed, so that only the same modes of operation are always present in one group. … s) 10..3600 s (standard: 300 s) Voltage-free phase during changeover. Note: àà The switch-on delay serves to map delayed sequence control. Maximum operating period for a drive line following a switching command. This time applies for ventilation OPEN and CLOSE but not for an alarm. The drive line switch-off time for RESET-CLOSE cannot be set. MBZ 300 Configuration software … .8 Status contacts The drive module has two inputs for which parameters can be set and at which status contacts can be connected. The type of contact can be selected: àà Closer contact àà Opener contact How to process the pending status contacts is set under this menu item. Status contact 1: Selection Not available End position status CLOSE End position status flashes CLOSE Disable input OPEN Disable input CLOSE Disable input OPEN CLOSE Switch ERM Function The status contact is ignored. The “CLOSE” end position is indicated by the green LED on the vent switch. During closing movement the LED is dark. The yellow LED “Window OPEN” on the RWA button is switched off permanently. As “End position status CLOSE”. The yellow LED “Window OPEN” on the RWA button is switched off permanently. The specific LED flashes during closing movement. Movement “OPEN” is blocked. Movement “CLOSE” is blocked. Movement in the “OPEN” and in the “CLOSE” direction is blocked. If an ERM is used, this input appears in the ERM properties for selection of the relay. If this input is active (contact closed), the selected relay is switched. 29 DM - Drive module Status contact 2: MBZ 300 Configuration software Not available The status contact is ignored. End position status OPEN The “OPEN” end position is indicated by the red LED on the vent switch. During opening movement the LED is dark. The yellow LED “Window OPEN” on the RWA button is switched on permanently. End position status flash- As “End position status OPEN” es OPEN The yellow LED “Window OPEN” on the RWA button is switched on permanently. The specific LED flashes during opening movement. Disable input OPEN Disable input CLOSE Disable input OPEN CLOSE Switch ERM Movement “OPEN” is blocked. Movement “CLOSE” is blocked. Movement in the “OPEN” and in the “CLOSE” direction is blocked. If an ERM is used, this input appears in the ERM properties for selection of the relay. If this input is active (contact closed), the selected relay is switched. Using the end position statuses The end position statuses are used as a clear indicator of end positions on the vent switch and RWA button. End position contacts must be available on the window / from the drive. Special features with only one end position status: If only one of the end position statuses is used, only the respective LED on the vent switch reacts to the status. The other LED behaves as in operation without end position statuses. àà When “end position status OPEN” or “end position status CLOSE” is selected, the respective selection is automatically set to “alternative function” and the drop-down menu is deactivated. àà Please note: If a different selection is made afterwards, the respective LED function must be set manually to “standard function”. Using the disable inputs Use of the status contacts as disable inputs temporarily blocks movement in order to avoid collisions between windows and shade systems, for example. The inputs are active both in ventilation and alarm mode. (However, please refer to the special features of alarm mode.) As long as a disable input is active, no movement takes place in the respective direction. When the input disable has been deactivated, movement begins automatically. Special features of alarm mode: If a disable input is not disabled until after an alarm has been triggered, it is ignored. This is to avoid a broken cable occurring in an alarm case preventing the window opening. The connection of the disable input to a relay which is actuated by the control unit in the event of an alarm is not possible since disabling would be too late due to the switching time of the status input relay. Special features of hold-open magnet mode: In hold-open magnet mode only “Disable input OPEN” has a function. Since the hold-open magnet transmits “OPEN” permanently in idling status and is switched off in the event of an alarm, the disable input disables switchoff in this case. Otherwise the function corresponds to the behaviour in standard motor mode. Influence on times: Drive line switch-off time: Switch-on and changeover delay: Runtime: Ventilation duration: Interval mechanism: Is restarted after every release. Is restarted after release. Is interrupted after disable. Is restarted after disable as long as necessary until a release is available when the time expires. Interval time is not interrupted by disable. Special features for power failure “Close all windows”: If the disable input is disabled, closing movement remains disabled despite subsequent release until mains power is restored. When disable input OPEN, CLOSE or OPEN CLOSE is selected, “Disable mode active” appears in the operating mode menu. In the runtime menu the line “Disable inputs will be ignored in the emergency-OPEN case after ...sec” is released for setting. 30 MBZ 300 Configuration software ATTENTION DME drive module - extended version Please make sure when using the disable inputs (particularly for sequence control) that you use the switching contacts correctly and proceed with corresponding care during testing. The reliability of the RWA system must be safeguarded. There is a residual risk: if the disable input is not cleared in the alarm case the windows cannot be opened. If for sequence control a time is set after which the disable inputs are ignored, collisions can occur between e.g. windows and shade systems. The system must be coordinated with the fire protection planner responsible. Ignore disable inputs The disabling of emergency-OPEN movement by a faulty contact in the event of an alarm should be avoided, or if release is given after a delay in the alarm case you can set that the disable input can be overridden after a certain time here and the movement is still started. [] Disable inputs are ignored in emergency-OPEN cases after: 0...999 s (standard: … Properties - DME and configuration possibilities (partner level) See the chapter “DM drive module/configuration possibilities” 31 SM Sensor module 10 MBZ 300 Configuration software SM Sensor module … V 1250 µA (standby) Maximum value 28 V 3000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 2550 µA (standby) 6000 µA (standby) 1000 µA (standby) 1250 µA (standby) 3000 µA (standby) Depending on the switched status NA (not actuated), OPEN, CLOSE or STOP MBZ 300 Configuration software SM Sensor module … .1 Vent switch function In the standard configuration the push button input of the control module in the first ventilation group is linked with all drive modules in the system. This ventilation group has a higher priority than the push buttons connected directly to the drive modules (= central push button for the whole control unit). Other ventilation group assignment (see the chapter “Ventilation groups”). Function setting Behaviour with button OPEN pressed [] Note: Biased-off (switch function) [] [] [•] OPEN CLOSE Locking [] [] Stop function same button Stop function both buttons Behaviour with button CLOSE pressed The default setting is OPEN and CLOSE The interval mechanism is then deactivated. The DMs switch to “OPEN” as If “CLOSE” is not set to bilong as the button is pressed. If ased-off, the DMs switch to the button is released, the DMs the “CLOSE” direction of travel switch off again. permanently. If “OPEN” is not set to biased-off, The DMs switch to “CLOSE” as the DMs switch to the “OPEN” long as the button is pressed. If direction of travel permanently. the button is released, the DMs switch off again. Modules switch permanently to “OPEN” direction of travel. Modules switch permanently to “OPEN” direction of travel. Modules switch permanently to “CLOSE” direction of travel. Modules switch permanently to “CLOSE” direction of travel. Stop by In biased-off direction: Release the push button If only one is active, the other is in self-locking mode: STOP = both push buttons at the same time Pressing the same push button again Pressing both buttons again “Permanently” means the set “drive line switch-off time” is at maximum. 33 SM Sensor module MBZ 300 Configuration software … are thus activated. An alarm is triggered in the event of a line break or short-circuit on detector line 1. MBZ 300 Configuration software SM Sensor module … .9 Messaging relay Selection of the message which leads to the messaging relay switching. trigger in case of: Never Rechargeable battery fault Mains voltage fault Control unit fault No reaction. Note: Should be set if the relay is used to report expiry of maintenance time. The closer contact is closed when the rechargeable battery monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The closer contact is closed when the mains voltage monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The messaging relay switches in the event of a fault within the control unit group (concerns faults on modules of the control unit). Closer is closed in the fault-free status. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). 35 WM - Weather module MBZ 300 Configuration software Common alarm of the group General alarm (default) Restricted group alarm Delayed group alarm Impulse for alarm reset The messaging relay switches following a common fault. The closer contact is closed in the fault-free status. When a common fault has been eliminated, the fault status is reset after a delay of 60 s. The fault status is reset immediately on the control unit where the fault occurred. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). The messaging relay switches when there is an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! If all alarm groups are deleted, the setting “Never” will appear after the next charging cycle. The messaging relay switches on for 300 s in the event of an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! The messaging relay switches on after a … A, SELV WM 36 MBZ 300 Configuration software WM - Weather module … Status – WM The following is displayed under the weather module tab: àà the evaluated current wind direction àà the evaluated main wind direction (average over 10 min!) The control unit only reacts depending on the wind direction when the red arrow is visible (depending on DM settings -> see the chapter “Emergency-OPEN for wind directions (for SHEV according to EN 12101-2)”) The position of the wind vane can be adjusted correctly by activating the “wind direction diagnostics”. The averaging of main wind direction is still active – it is necessary to wait for this average for a test. àà Rain / no rain àà Current wind speed and set threshold. àà Module status text The current operating mode is displayed here. The current status and faults are displayed, as described in the installation instructions. 37 WM - Weather module MBZ 300 Configuration software … .3 Delay values (for ventilation) Is used to delay the switching reaction to wind e.g. constant opening and closing is avoided in gusty wind conditions. Wind switch-on delay Wind switch-off delay 0...254 s (standard: 20 s) 0...3600 s (standard: 1200 s) Notes on testing: Depending on the sensors connected there can be a changeover delay time. Rain sensors in particular have a pre-set drying time which may vary depending on the rain duration/intensity. 38 MBZ 300 Configuration software ERM relay module … A, SELV OK ! MBZ300 ERM 39 ERM relay module MBZ 300 Configuration software … .3 Module status text The current operating mode is displayed here. The current status and faults are displayed, as described in the installation instructions. 40 MBZ 300 Configuration software ERM relay module … .1 General relay configuration Signals from ventilation and weather groups, fire sections as well as faults can be signalled at the same time by one relay. It must be noted that the signalling of fire sections takes priority over ventilation/weather groups. àà If the function of a relay is redefined by software, the relay remains in its current switched position until a switching signal occurs. This means that an incorrect status can be displayed before this first switching takes place. àà The relays are bi-stable. In other words, the status remains even if there is a drop in voltage. àà With multiple assignment of a relay please note that the functions are prioritised automatically (alarm signal > ventilation / weather > fault).. 41 ERM relay module MBZ 300 Configuration software … .4 Alarm relay configuration (fire sections) As soon as a relay module is integrated in a control unit, additional configuration possibilities appear in the fire sections. 42 MBZ 300 Configuration software ERM relay module Here, selection can be made of the relays which are to be switched when an alarm occurs for this fire section. A relay can also be assigned to different fire sections. In higher-order fire sections relay modules are available for all control units. With the aid of higher-order fire sections the alarm of another control unit can be displayed on a relay module, for example. PLEASE NOTE: A multiply assigned relay is switched off as soon as one of the fire sections is reset, even if other fire sections are still actuated. … s. àà Tip: A real window position can only be mapped by end position contacts (e.g. reed-contacts) 43 Fire sections MBZ 300 Configuration software … Fire sections Add Edit Delete 44 Fire sections are added by clicking this button. The fire section to be edited must be selected from the list. When this button is clicked, the program jumps to the view of the fire section selected. The fire section to be deleted is selected from the list and deleted by clicking the button. MBZ 300 Configuration software Fire sections … .3 Drive lines Here you can select which drive lines are assigned to this fire section. 45 Fire sections MBZ 300 Configuration software … .6 Description A text describing the fire section can be entered. 46 MBZ 300 Configuration software 14 Ventilation groups Ventilation groups … Details of ventilation group The ventilation groups can be formed flexibly. 47 Ventilation groups MBZ 300 Configuration software … .4 Description A text describing the ventilation group can be entered. 48 MBZ 300 Configuration software 15 Weather groups Weather groups The weather group is only valid for the ventilation function. … .4 Description A text describing the weather group can be entered. 49 Higher-order fire section / ventilation groups / weather groups 16 MBZ 300 Configuration software Higher-order fire section / ventilation groups / weather groups Example: If several control units are networked via CAN, higher-order groups are available. Here, inputs and drive lines from several control units can be summarised in groups. (see the chapters “Fire sections” / “Ventilation groups” / “Weather groups”) PLEASE NOTE: An input signal (detector line, ventilation line or weather signal) may only occur in a maximum of one group! Multiple use is not possible otherwise behaviour is not predictable. Please check the local groups for the individual control units and delete if necessary! 17 General information … Settings by software and VdS Some settings which can be made by software lead to the VdS certificate no longer being valid in the broadest sense, since monitoring functions which represent requirements according to VdS can be switched off specifically through configuration. Please consider this when carrying out customised configuration of the MBZ 300. Examples of settings concerned: àà VdS post cycle control àà Line monitoring of the detector lines (deactivation of fault evaluation) àà Start-up delay àà Alarm CLOSE … Cabling: Several fire sections, networking and inter-control unit functions CAN networking allows fire sections to be defined where individual or several control units are assigned to several functional sections, in other words: the installation site of the control unit and the detector and drives may be distributed in different areas. This local distribution may lead to the basic requirement according to the guideline for 50 MBZ 300 Configuration software Testing the system circuit systems (MLAR) for monitoring the emergency power control unit no longer being given. If this is the case, suitable compensatory measures must be taken (e.g. E 30 cabling). 18 Testing the system The configured MBZ 300 must be tested in such a way that neither people or the technical equipment are endangered. Please confirm the commissioning / functional test and regular maintenance testing in the test log (GEZE material number 133761 (DE)). 19 FAQs … Sequence for commissioning and configuration by software see the chapter “Procedure for configuration of a control unit” … .2 The control unit is not shown correctly in the software (modules missing etc.) XX XX XX XX XX XX Keep the reset push button on the CM pressed for 20 s (until all modules are flashing - not longer!). This ensures the modules are addressed correctly. This process is essential when the hardware (modules and order) has been changed. Connect USB cable to CM and connect to the laptop. Start the software “Individual control unit” (please make sure you always use the latest version (see the chapter “Software installation).) Check the firmware version of the control unit to make sure it is up-to-date Carry out firmware update if necessary (see the chapter “Firmware update”) Load default settings (see the chapter “System configuration”) PLEASE NOTE: All previous settings are deleted! XX XX XX Adapt rechargeable battery size and number of PMEs (see the chapter “Rechargeable battery settings”). Set the individual configuration Transmit to the control unit … .3 The software cannot be started completely. / The software “crashes” during loading of the control unit. XX XX XX XX XX Terminate the program using the task manager if necessary. Remove the USB cable Check the USB cable and the USB connection. If the cable or connection is faulty the connection cannot be established properly and the software cannot load the configuration completely. Check the capacity utilisation of your computer and the assignment of the correct driver (assign again if necessary -> see the chapter “Software installation”). Reboot the software and connect the USB cable again. … Does the module sequence matter? The software allows numerous different settings; nevertheless we recommend setting up the modules as closely as possible to standard configuration (better overview): àà A new fire section begins with CM / SM àà Do not set SM at the end àà WM in last position àà ERM does not have any restrictions but should also be set at the end for reasons of clarity. àà If there is a DM attached on the left-hand side of the respective SM, the DM fault is not indicated on the SM. 51 Meaning of the log entries MBZ 300 Configuration software … General trouble shooting Use the different displays to find the faulty spot: àà LED code on the module (see MBZ 300 installation instructions) àà Log file àà Status pages of the modules with: àà States and current values (target value comparison with this document) àà Fault display àà Measurement of the various outputs and inputs and comparison with the display in the PC software … Trouble shooting where several control units are in one CAN network XX XX “Divide and rule”: Only connect the local with the nearest control unit (check CAN terminals!). àà Terminate this section. àà Disconnect all other CAN connections. àà Open the “networked control units” software. àà Check whether both control units are available. The points must be repeated accordingly for the other sections. … s CLOSE - OPEN 120 s X (300 s) Y (40 s) X (300 s) Z each time (10 s) Meaning of the log entries See the chapter “RealTime_Log - control unit”. All possible log entries are listed here. During operation, only a limited selection of these will actually occur. The list also includes the logging level from which this type of message can occur. The logging levels are classified as follows. A lower (or finer) logging level automatically includes the higher-order logging level entries. This means that error entries are always included in the log when this is set to alarm. Here are the possible logging levels in order from the lowest to the highest. LOG_FINE LOG_INFO LOG_ALARM LOG_ERROR %d SM %d 52 The finest logging level: everything is logged. This provides a precise overview of the processes in the system, but the high memory requirements mean that the log does not extend far into the past. The switching processes are entered in the log. Faults and alarm states and their triggering are reported. Only errors are recorded. Stands for any number, this is usually the module ID which this log entry refers to. SM_0 is the CM. CM and SM are equated here. MBZ 300 Configuration software Log entry Bus Fault Exception, System HALT! CAN Main: CANSendMsg() Error! CAN XmitQueue: Error %d! CAN: buff emptyed! Meaning of the log entries Granularity LOG_ERROR CAN: kfg fkt mismatch! LOG_ERROR Fault pattern A fault occurred during access to the system bus. The CAN interface of this control unit could not send a message. This control unit could not transmit a CAN message Attempt is being made to transmit something that isn't there. A command has not been received completely. CAN: MBOX_CAN buffer LOG_ERROR full The control unit cannot keep up with transmission. CAN: mbusb, buffer processing problem! LOG_ERROR Buffer is overflowing during remote servicing of a control unit via CAN. CAN: mbusb, eval_cmd LOG_ERROR buffer problem! This control unit does not understand a command that came via CAN. CAN: Modbus commu- LOG_ERROR nication failure %d! CAN: rec array overflow! LOG_ERROR CAN cannot be read properly. LOG_ERROR LOG_ERROR LOG_ERROR CAN: rec queue full! LOG_ERROR CAN: reception while processing! LOG_ERROR canf_mbm_writeread(): LOG_ERROR too many resends! canf_xmit_konf(): LOG_ERROR CANSendMsg timeout! canfi_eval_cmd, requesting resend... LOG_ERROR canfi_mbusb_received(): MBOX_CAN error %d! CANSendMsgQ(): Queue full! Clock Source failure (Clock Security System)!!! CM IWDG-RESET!!! LOG_ERROR Creating autoKonfig, eepCfg ver.> 3... LOG_INFO Creating autoKonfig... LOG_INFO LOG_ERROR LOG_ERROR LOG_ERROR Note Hardware fault? Replace CM. Check the CAN module Check the CAN module Reboot CM Is compensated automatically. Has the CAN system been configured properly, are there any “meaningless” rules? If one of the control units does not react, reboot this and start the configuration process again. Do all the control units have the same firmware version? CAN module OK? Can only occur when someone actively interferes with data transfer. Do all the control unit have the same firmware version, what else is attached to the CAN cable? Too many different commands have been sent Has the CAN system been to this control unit. configured properly, are there any “meaningless” rules? Unknown data were received during CAN Do all the control units command processing. have the same firmware version? A message has been repeated too often with- Is a control unit switched out an answer being received. off, disconnected? (Cable?) A message could not be sent in time, possible Should not occur. If it does data loss. occur during a saving process - repeat this. The command has not been received comIs not really a fault in the pletely and is being requested again. strict sense, since it is compensated. If it occurs often, however, it is a sign that there is something wrong with the CAN-bus. An unexpected error has occurred during Check the CAN module reception of a CAN message. This control unit could not send a CAN message due to buffer status. The clock is faulty. Check the CAN module Hardware fault? Replace CM. If the system “crashes” or the watchdog thinks Should not occur. Firmthis is the case, it triggers a reboot. ware update, otherwise replace CM. After the start an unknown configuration was ... found in the EEPROM, a new configuration which matches the modules found is being created and used. After the start a new configuration which ... matches the modules found is being created and used. 53 Meaning of the log entries DM %d: Alarm AUF DM %d: ALARM bei deaktiviertem DG! MBZ 300 Configuration software LOG_ALARM LOG_ALARM DM %d: Alarm reset bei LOG_ALARM deaktiviertem DG! DM %d: Alarm reset, DG spannungslos LOG_ALARM DM %d: Alarm ZU LOG_ALARM DM %d: ALARM, DG aktiviert DM %d: ALARM, HM freigegeben DM %d: Alarm-Reset LOG_ALARM DM %d: ALARM, Überschreiben des Sperrkontakts DM %d: AUF DM %d: AUF (LZM) LOG_ALARM DM %d: Auto-ZU DM %d: Fenster ist offen DM %d: Fenster ist geschlossen LOG_INFO LOG_INFO DM %d: HM aktiviert LOG_INFO DM %d: HMinit AUF DM %d: ist schon AUF LOG_INFO LOG_FINE DM %d: ist schon ZU LOG_FINE DM %d: Linie spannungslos LOG_FINE DM %d: LT AUF LOG_FINE DM %d: LT STOP LOG_FINE DM %d: LT ZU LOG_FINE DM %d: LZMinit ZU DM %d: LZM-Stop LOG_FINE LOG_INFO DM %d: no key LOG_FINE DM %d: NOTAUF LOG_ALARM LOG_ALARM LOG_ALARM LOG_INFO LOG_INFO LOG_INFO DM %d: STOP LOG_INFO DM %d: STOP durch LOG_INFO Sperrkontakt DM %d: Sperrkontakt … has been activated in OPEN direction ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... MBZ 300 Configuration software DM %d: Sperrkontakt … has been deactivated in CLOSE and OPEN direction This DM is now closing. Indicates that the log entries found are faulty and the log thus had to be deleted. This can happen if a configuration from a too recent configuration program is used by firmware that is too old. The configuration requires that functions which are not available in the firmware should be used. The CPU has jumped to a position where it is not allowed to land. No communication was possible with y of x modules in one cycle. ... ... ... ... ... ... ... ... ... ... ... ... This can happen when power supply and rechargeable battery both fail and the voltage suddenly drops severely. In other words when there is not sufficient voltage available during log writing. CM Firmware update. Fault in the CM firmware or hardware fault. If this occurs sporadically it is not a problem, since it is compensated, but if it occurs permanently one or more module(s) is(are) faulty. ... After the start the configuration was loaded from the EEPROM and is being used. Modules in the control unit have been recon- Re-establish the default nected or disconnected since the last start-up. configuration and address/ configure correctly. Fault in memory management: Corrupt firmware, memory faulty, VDS self-test entries available? Replace CM. No access to the clock. Hardware fault? Replace CM. Communication with the PM not possible via Hardware fault? Replace the Modbus. PM/CM? 55 Meaning of the log entries PM(E): Akkufehler MBZ 300 Configuration software LOG_ERROR PME1 angeschlossen, LOG_ERROR aber nicht konfiguriert PME2 angeschlossen, LOG_ERROR aber nicht konfiguriert PM(E): Netzfehler LOG_ERROR PM(E): OK LOG_INFO PM/IOM Poll ok! LOG_ERROR PM: Netz und Akku fehlt LOG_ERROR RTC count lost!!! Semaphore deadlock: %s, err: %d LOG_ERROR LOG_ERROR SM %d: NOT_AUF BMZ1 LOG_ALARM SM %d: NOT_AUF BMZ2 LOG_ALARM SM %d: NOT_AUF RM1 LOG_ALARM SM %d: NOT_AUF RM2 LOG_ALARM 56 SM %d LED Stoerung: %d LOG_ERROR SM %d: Alarm-Reset LOG_ALARM SM %d: BMZ an RM1 NOT_ZU SM %d: BMZ an RM2 NOT_ZU SM %d: Linienfehler Handmelder! SM %d: Linienfehler Not-ZU! SM %d: Linienfehler RM1! LOG_ALARM LOG_ALARM LOG_ERROR LOG_ERROR LOG_ERROR The PM is missing a rechargeable battery. Check the rechargeable battery + cables, use the configuration software to check whether PMEs and battery capacity have been set properly. If this does not help, replace the PMEs or the PM on the basis of the values shown on the PM status page. There is a PME1 available in the control unit Start configuration softbut it has not been configured. ware and set the correct number of PMEs. There is a PME2 available in the control unit Start configuration softbut it has not been configured. ware and set the correct number of PMEs. The PM or the control unit is no longer drawing Check power supply, PM. current from the power supply. The PM has mains current and rechargeable ... battery again. (This message can of course only occur if one of these elements was missing.) Only occurs in combination with IOM Poll Error Not an error %d/%d missing and means that the PM was OK in this context. A fault has occurred on the SM but there is Desired behaviour... no reaction on account of the energy-saving mode. The CM no longer has the current time. Synchronise with the PC. A resource of the CM operating system could Rebooting the CM can not be released, as a result the CAN system can eliminate the problem. no longer function, for example. Reset has been triggered with the CIE1 at this ... SM. Reset has been triggered with the CIE2 at this ... SM. Reset has been detector line … on this SM negative replace the SM. MBZ 300 Configuration software Meaning of the log entries SM %d: Linienfehler RM2! SM %d: LT AUF LOG_ERROR A line fault has been detected on detector line … LOG_ALARM SM %d: NOT_AUF Reset LOG_ERROR Failure SM %d: NOT_ZU LOG_ALARM SM %d: NOT_ZU (res) LOG_ALARM SM%d: Mreset LOG_INFO STL: >>> RAM Error (March C- Run-time check) STL: Abnormal Clock Test routine termination STL: Class B variable error (clock test) STL: Clock Source failure (Run-time) STL: Control Flow Error (main loop) STL: Control Flow error in RAM-Test-ISR STL: Run-time FLASH CRC Error STL: Run-time FLASH CRC OK, %d cycles STL: SRAM-Check OK, %d cycles STL: Stack overflow LOG_ERROR LOG_ERROR The self-test routines (VDS) have established a fault. The self-test routines (VdS) have established a fault on the clock. The self-test routines (VDS) have established a fault. The self-test routines (VDS) have established a fault. The self-test routines (VDS) have established a fault in the flash. The self-test routine flash check (VDS) has been carried out successfully x times. The self-test routine flash check (VDS) has been carried out successfully x times. The self-test routines (VDS) caused a fault. STL: Start-up CPU Test Failure STL: TOO MANY REBOOT FAILURES, LOCKING UP!!! Stoerung bei PF DM %d: %d LOG_ERROR The CPU is no longer working properly LOG_ERROR For some reason the CM has rebooted very often, a fault has been established. LOG_ERROR Stoerung bei PF SM %d: %d LOG_ERROR A fault has occurred on the DM but there is no reaction on account of the energy-saving mode. A fault has occurred on the SM but there is no reaction on account of the energy-saving mode. LOG_ERROR LOG_ERROR LOG_ERROR LOG_ERROR LOG_FINE LOG_FINE ... ... ... ... Check the cable, if test negative replace the SM. ... ... ... Hardware fault? Replace CM. ... Hardware fault? Replace CM. Hardware fault replace CM. Hardware fault? Replace CM. Desired behaviour... Desired behaviour... 57 Meaning of the log entries MBZ 300 Configuration software Stoerung DM %d: %d LOG_ERROR Indicates a fault on this DM, usually a detector line fault, with some old DMs there was another fault here which made this occur briefly, but it was not actually a fault. Stoerung ERM %d: %d LOG_ERROR Testmode initiated... LOG_ERROR Indicates a fault of the system voltage on this ERM This is not CM firmware in the actual sense. There is only a test program in the CM. This is not CM firmware in the actual sense. There is only a test program in the CM. The bits did not make sense to the CPU. Testmode: KonfigTask LOG_ERROR abgebrochen... Usage Fault Exception, LOG_ERROR System HALT WM %d: kein Regen LOG_INFO WM %d: REGEN WM %d: WIND LOG_INFO LOG_INFO WM %d: WIND T%d WM %d: Wind unterhalb Schwelle WM %d: WRG fehlt! LOG_INFO LOG_INFO LOG_ERROR A WM has recognised that it has stopped raining. A WM has detected rain. A WM has detected wind from a certain direction. Shows that the WM has detected wind. The wind has fallen under the threshold on one of the WMs. There is a wind direction finder configured in a WM but the WM cannot detect it. If a line fault can be excluded and the fault only occurs briefly, we recommend a DM firmware update. If neither of these approaches was successful, the DM affected should be replaced. Firmware update with the boot loader. Firmware update with the boot loader. Firmware OK? Flash again? Hardware fault? Replace CM. ... ... ... ... ... Is the sensor/WM, cable working? WM / test sensor => replace. If you have any support requests, always submit the “Error log” of the configuration SW with your request. You will find the “ErrorLog.txt” in the licence key directory. 58 MBZ 300 Configuration software Meaning of the log entries 59 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 Hungary GEZE Hungary Kft. E-Mail: office-hungary@geze.com www.geze.hu Scandinavia – Denmark GEZE Danmark E-Mail: danmark.se@geze.com www.geze.dk Baltic States GEZE GmbH Baltic States office E-Mail: office-latvia@geze.com www.geze.com Iberia GEZE Iberia S.R.L. E-Mail: info@geze.es www.geze.es Singapore GEZE (Asia Pacific) Pte, Ltd. E-Mail: gezesea@geze.com.sg www.geze.com Benelux GEZE Benelux B.V. E-Mail: benelux.nl@geze.com www.geze.be www.geze.nl India GEZE India Private Ltd. E-Mail: office-india@geze.com www.geze.in South Africa GEZE South Africa (Pty) Ltd. E-Mail: info@gezesa.co.za www.geze.co.za Italy GEZE Italia S.r.l E-Mail: italia.it@geze.com www.geze.it Switzerland GEZE Schweiz AG E-Mail: schweiz.ch@geze.com www.geze.ch GEZE Engineering Roma S.r.l E-Mail: roma@geze.biz www.geze.it Turkey GEZE Kapı ve Pencere Sistemleri E-Mail: office-turkey@geze.com www.geze.com 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 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 GEZE GmbH Reinhold-Vöster-Straße 21–29 71229 Leonberg Germany Tel.: 0049 7152 203

User manual MBZ 300 configuration software

… software Configuration program for the RWA system comprising components of the MBZ 300 series Software version … 153427-02 EN User manual  MBZ 300 Configuration software Contents … Software installation … Notes on the software … 22 MBZ 300 Configuration software  … MBZ 300 Configuration software 12 ERM relay module … Settings by software and VdS … Sequence for commissioning and configuration by software … 52 The control unit is not shown correctly in the software (modules missing etc.) … 52 The software cannot be started completely. / The software “crashes” during loading of the control unit … 53 MBZ 300 Configuration software  … MBZ 300 Configuration software About this document This user manual describes operation of the GEZE MBZ 300 configuration software. … Runtime and the Visual C 2008 redistribution package. These packages are installed automatically by the installer package if they are not already in the system. Connector type Mini-B Acrobat Reader for displaying the help file and the configuration data export in PDF format Compatibility table: Version of configuration software … MBZ 300 Configuration software … Software installation General information After MBZ 300 software training you are registered in the user list. Please make sure you always work with the latest software. You will find the latest software at the GEZE customer portal: www.geze-partnerlogin.de or on the GEZE website geze.de in the MBZ 300 product area under Downloads/Software. Please install the software on a laptop which is used for commissioning the MBZ 300: àà you need administrator rights for installation. àà Install the program in a folder with writing rights for the user àà Make sure that the driver is also installed. (If this is not done automatically, the driver can be installed later from the directory “...\Programme\GEZE\MBZ300\Driver” when an MBZ 300 control unit is connected.) … .1 View licence This level does not have to be cleared. After installation the software is automatically in the view level. The following possibilities are available: àà Display of system or module status àà Display log entries àà Setting of the charging current on the basis of the battery capacity àà When a weather module is installed: Setting of the type of peripherals connected + wind speed + delay values àà Setting of the system time … .2 MBZ 300 Configuration software Request licence key As a registered software user, go to the GEZE customer portal: www.geze-partnerlogin.de. There, click “Authorisation”, enter the activation code and request the key. Your contact responsible will send you the suitable licence key by mail as soon as possible. You can highlight the key e.g. with the mouse, copy it to the clipboard using <strg>+<c> and paste it to the respective field using <strg>+<v>. Alternatively to the portal, a new licence can also be requested by mail. To do this, please send the activation key to MBZ300@geze.com. If you have any questions, please contact MBZ300@geze.com. … .3 Entering a licence key If the authorisation window has been closed in the meantime, request it again as described above. Enter the licence key in the “Licence key” field. After you have clicked “Authorisation” the extended functionality will be available. 90 days before the licence expires, the following window will appear as a reminder when you start the software: … Notes on the software A firmware update is not necessary for existing configured MBZ 300 control units. For new installations always use the latest configuration software together with the latest firmware. Update the firmware as required (see the chapters “Firmware update” and “Procedure for configuration of a control unit”). MBZ 300 control units are reset to the factory settings by the firmware update. … .1 What happens after the system has been connected via USB As soon as the system has been connected to the PC, the settings and the current system configuration are read out. Depending on the size of the system, this procedure can take a few seconds. The software is ready when the info-area of the main window (bottom left) displays “System loading OK”: The program has to be terminated before the USB connection cable between the PC and MBZ 300 is removed. … MBZ 300 Configuration software … .4 Menu functions A wide range of different software functions can be executed via the menu in the header. Navigation is by left mouse click, analogue to familiar programs. File … General information MBZ 300 Configuration software Load configuration... A saved configuration (*.MBZ) is loaded to the software interface. It is not yet written into the system. XX Check settings after loading. XX Adapt the following settings manually, since these are not saved in the file. àà PM: àà Size of the battery àà Number of PMEs àà WM: àà Sensors àà Wind thresholds àà CM: àà Maintenance time àà Time Save configuration... àà Password See the chapter “System configuration” for how to write the configuration in the system. The current configuration is saved in a file (*.MBZ) on the PC. Save configuration as ... Like “Save configuration...” but under a new file name. Authorisation... See the chapter “Authorisation” Set password of the selected control unit Remove password of the selected control unit selected control unit was changed by... Preview selected control unit... Preview all control units... Generate a PDF of the selected control unit configuration... Generate a PDF containing all control unit configurations... Exit Protect the system by means of a password. Delete the system password Display of hard drive ID and date of the last change XX Terminates the program. System configuration Load default configuration of the directly The system configuration is reset to factory settings. The self-teaching funcconnected control unit... tion is re-activated. Refer also to the chapter ““Buttons” on the interface” Note: All the settings are lost! (The data memory of the control module is deleted). Write settings permanently to the control The configuration on the software interface is transmitted to the control unit unit. Refer also to the chapter ““Buttons” on the interface”. Load configuration from the control unit Reads the existing configuration out of the system and displays it on the software interface. If a configuration on the software interface is not saved it is lost. Reboot the directly connected device... Reboots the connected system. It is necessary to reboot the system when all the required changes have been written into the system and a check on system behaviour is to be made. = equivalent to: switching the control unit voltage-free for at least 30 seconds (without rechargeable battery). 10 MBZ 300 Configuration software General information Language The following languages can be selected: àà German àà English àà French àà Turkish àà Chinese Help Help (in German or English) is started directly from the software, the respective PDF document is saved in the software project directory. The help file with the specific language is automatically loaded with the Acrobat Reader. About … .5 “Buttons” on the interface As an alternative to items from the header menu, some functions are available as buttons. The functions of the buttons is described below. “Clear” The control unit configuration is reset to factory settings. Refer also to the chapter “System configuration”. Note: All the settings are lost! “Save to CM” The configuration on the software interface is transmitted to the control unit. Refer also to the chapter “System configuration”. “Undo” Changes to the configuration on the software interface are reversed. Note: This only affects the current view on the PC, not the control unit. For this, the configuration has to be re-transmitted to the control unit. Whether or not a property can be modified depends on the user level. 11 General information … .6 MBZ 300 Configuration software EMU (emulator) The emulator is used to simulate system set-up when the PC is no longer connected to an MBZ 300 control unit. To simulate the system set-up, the various modules are added to a list in descending order. The modules can be moved in the list by drag-and-drop. Then the system set-up is loaded to the configuration program, where the settings can be made. PM, CM, DM, SM, DME, WM, ERM Adds the corresponding module to the list. System separation Allows a new control unit to be started in the list in order to map several control units connected via CAN-bus. (This function only becomes effected when the “Networked control units” program version is used.) Delete selection Deletes the module selected in the list Delete all Apply to SW config Deletes all the modules from the list Loads the list as system set-up into the configuration program. When configuration has been completed it can be saved (*.MBZ) in order to be exported to an actually existing control unit locally at a later date. The configuration file of an actually existing system can also be loaded into an identical, emulated system. The configuration can only be loaded to an identical control unit (same module sequence). The set-up must be known. Tip: Always save the *.PDF file in addition to the configuration file (*.MBZ). XX 12 Please check the settings on the real control unit! The following settings are not saved in the *.MBZ file and must be adapted manually: àà PM: Battery size and number of PMEs àà WM: Sensors and wind thresholds àà CM: Maintenance time and time àà Password MBZ 300 Configuration software … General information Firmware update Please note the compatible PC software and firmware versions (see chapter … ). Before updating a control unit that has already been configured, please check whether the required functions are available / realised in the same way in the other firmware Changing the firmware to an earlier version is possible and works in the same way as an update. Carry out the firmware update using the “Update” program. You will find the program in the Start menu. Please proceed as follows: XX Connect the control unit via USB. XX Save the configuration as .mbz file and as .pdf export. XX Start the update program. Path for pre-installed software installation: START -> All programs -> GEZE -> MBZ 300 -> Update -> Update The update program contains the following: àà Updating of all firmware statuses of the modules installed XX XX àà Delete the EEPROM memory (optional) Start the software “Individual control unit”. Load the saved configuration or restore the configuration. The following settings must be adapted manually: àà PM: Battery size and number of PMEs àà WM: Sensors and wind thresholds àà CM: Maintenance time and time àà Password 13 Procedure for configuration of a control unit … MBZ 300 Configuration software Procedure for configuration of a control unit Please note the following steps when commissioning or modifying an MBZ 300: … [1] Ensure the system is voltage-free (no 230 V connection, no rechargeable battery). [2] Insert further modules if appropriate. [3] Check cabling between the modules. àà Power supply àà Bus cable (Caution: NEVER connect or disconnect with the control unit switched on!) àà Ensure that the cables are fitted correctly. àà Connect drives, push buttons etc. (can also be done later) àà Make sure that all line monitoring devices are connected properly [4] Activate 230 V supply. [5] Connect rechargeable battery. [6] Keep the reset push button on the CM pressed for 20 s (until all modules are flashing - not longer!). This ensures the modules are addressed correctly. This process is essential when the hardware (modules and order) has been changed. [7] Connect USB cable to CM and connect to the laptop. [8] Start software. Select access to single directly connected or all interconnected control units. Make sure that you always use the latest version (see the chapter “Software installation”). [9] (Only for initial start-up) Check firmware version of the control unit to make sure it is up-to-date. [10] (Only for initial start-up or when necessary) Carry out firmware update if appropriate (see the chapter “Firmware update”). [11] (Only for initial start-up or when necessary) Load default settings (see the chapter “System configuration”). Standard groups (alarm / ventilation / weather groups) are formed along module settings through the self-learning function (connection of modules) or default loading. Caution: all previous settings are deleted! [12] Adapt battery size and number of PMEs (see the chapter “Rechargeable battery settings”). [13] Set individual configuration (either directly or by loading a saved *.MBZ file with the same module set-up). [14] Transmit to the control unit. [15] Reboot the directly connected control unit. [16] Check settings. [17] Test functions (please note interactions with building managment system, BMA, relaying!) [18] Save central configuration as *.MBZ and *.PDF and archive for the project. [19] In the control unit, note that the configuration has been adapted by software (user, date and rough description – print out PDF and enclose if appropriate). [20] Terminate software, then remove USB cable Several control units networked via CAN For this, establish the USB connection to each individual control unit and start the software each time (refer also to the chapter “CAN parameters”). The procedure is in addition to / instead of the above points as follows: XX [12a]: Set the address and number of control units for each individual control unit under CM CAN parameters. XX Transmit to the control unit. XX Reboot the directly connected control unit. XX It is advisable to mark the control units according to their addresses. XX [12b]: At this point at the latest, make sure that the CAN cables incl. terminator jumper are correctly connected between the control units XX Establish a USB connection to any control unit. XX Open the “Networked control units” software. XX Re [13]: Set the configurations and comprehensive functions in particular now and transmit to the control units. XX Re [18]: Save the configuration file as *.MBZ (several files) and *.PDF. 14 MBZ 300 Configuration software … RealTime_Log - control unit The program displays the entries in the “RealTime_Log” memory. This lists events which have had at least alarm or fault status. Various selection possibilities can be used to set which events and messages are to be recorded. The setting does not represent a filter of the view, rather it specifies what is actually to be saved. Granularity: Note: Fine (everything) All events are saved e.g. including ventilation control Information All messages are saved Alarm Alarm and fault messages are saved Fault Fault messages are saved The granularity settings must be written into the system for the changes to take effect. read all available entries Empty text box All the messages available for the control unit are read. Please note: This can take a very long time! Only deletes the display on the software interface. Save text box content... Saves the fault memory to a file (.TXT). Empty the control unit Deletes the fault memory of the control unit. The log is a circular buffer (the oldest data are overwritten) with sufficient capacity (depending on granularity). Tip: Use the log memory for trouble shooting and for functional test (granularity “Fine”). Refer also to the chapter “Meaning of the log entries”. Info: The log memory is large enough to comprise around 1500 entries. The setting is irrelevant. Last control unit changes The date and the drive serial number of the computer which made the most recent change are displayed here. The drive serial number is part of the authorisation key. Text for information and comments of this control unit A text describing the control unit can be entered, e.g. what work a service technician has most recently done on the control unit. 15 PM - Power module … Purpose MBZ 300 Configuration software àà Provision of a non-interrupted power supply. àà Battery charging. àà Provision of secondary voltages. … Status - PM The current status can be compared with the target value table shown below in order to evaluate the status 16 MBZ 300 Configuration software … Properties – PM Rechargeable battery control [•] Fault message [] Rechargeable battery control deactivated [] [] Fault message and windows CLOSE Fault message and windows OPEN A fault message is outputted via the fault LED or e.g. via the messaging relay with corresponding parameter settings. No reaction in the event of a fault. For ventilation application only or operation without rechargeable battery A fault message is outputted and all drive modules are actuated to CLOSE. A fault message is outputted and all drive modules are actuated to OPEN. 17 PM - Power module [] MBZ 300 Configuration software Rechargeable battery protection In battery operation the control unit does not run with all modules until the rechargeable battery is completely discharged (deep discharge). All modules apart from the PM are switched off beforehand to protect the rechargeable battery (this protection triggers at approx. … Ah (default) 10 Ah 12 Ah 17 Ah 24 Ah 38 Ah The corresponding rechargeable battery type must be set After the default values have been loaded, this setting must always be checked and adapted if necessary! ATTENTION 18 If the rechargeable battery type is set incorrectly this can lead to excessively high charging current. Excessively high charging current can damage the rechargeable battery. The rechargeable battery will become very hot: Risk of explosion! The parameters must always be checked following a software update on a control unit. MBZ 300 Configuration software CM - Control module … .2 MBZ 300 Configuration software Module status text The current operating mode is displayed here. The current status and faults are displayed, as described in the installation instructions. … .1 Vent switch function In the standard configuration the push button input of the control module in the first ventilation group is linked with all drive modules in the system. This ventilation group has a higher priority than the push buttons connected directly to the drive modules (= central push button for the whole control unit). Other ventilation group assignment (see the chapter “Ventilation groups”). Function setting Behaviour with button OPEN pressed [] Note: [•] Biased-off (switch function) [] OPEN [] CLOSE Locking [] [] Stop function same button Stop function both buttons Behaviour with button CLOSE pressed The default setting is OPEN and CLOSE The interval mechanism is then deactivated. The DMs switch to “OPEN” as If “CLOSE” is not set to bilong as the button is pressed. If ased-off, the DMs switch to the button is released, the DMs the “CLOSE” direction of travel switch off again. permanently. If “OPEN” is not set to biased-off, The DMs switch to “CLOSE” as the DMs switch to the “OPEN” long as the button is pressed. If direction of travel permanently. the button is released, the DMs switch off again. Modules switch permanently to “OPEN” direction of travel. Modules switch permanently to “OPEN” direction of travel. Modules switch permanently to “CLOSE” direction of travel. Modules switch permanently to “CLOSE” direction of travel. Stop by In biased-off direction: Release the push button If only one is active, the other is in self-locking mode: STOP = both push buttons at the same time Pressing the same push button again Pressing both buttons again “Permanently” means the set “drive line switch-off time” is at maximum. 20 MBZ 300 Configuration software … .7 MBZ 300 Configuration software Detector line … .9 Messaging relay Selection of the message which leads to the messaging relay switching. trigger in case of: Never Rechargeable battery fault Mains voltage fault Control unit fault 22 No reaction. Note: Should be set if the relay is used to report expiry of maintenance time. The closer contact is closed when the rechargeable battery monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The closer contact is closed when the mains voltage monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The messaging relay switches in the event of a fault within the control unit group (concerns faults on modules of the control unit). Closer is closed in the fault-free status. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). MBZ 300 Configuration software CM - Control module Common alarm of the group General alarm (default) Restricted group alarm Delayed group alarm Impulse for alarm reset The messaging relay switches following a common fault. The closer contact is closed in the fault-free status. When a common fault has been eliminated, the fault status is reset after a delay of 60 s. The fault status is reset immediately on the control unit where the fault occurred. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). The messaging relay switches when there is an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! If all alarm groups are deleted, the setting “Never” will appear after the next charging cycle. The messaging relay switches on for 300 s in the event of an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! The messaging relay switches on after a … .1 System Time: synchronize Set the system time. (No distinction is made between summer and winter time) The system time can be compared with the time on the PC connected by pressing the “synchronize” button. Please make sure that the PC time is correct. 23 CM - Control module MBZ 300 Configuration software The system time is used for the time stamp for messages in the RealTime log. Note: If the system is too different, a warning window will appear when the software is started. … s) Smoke detector recovery time 0...1000 ms after smoke detector reset (standard: 500 ms) Smoke detectors are reset by switching off the supply voltage to the detector for the period set here. The detector line evaluation is deactivated for the time given here following reset of a smoke detector line. During the smoke detector reset no detector line evaluation takes place, including on the RWA button lines. 24 MBZ 300 Configuration software [] Common fault of the network system (with CAN network) CM - Control module The system-wide output of faults is activated. Faults are shown on all RWA buttons in the network system (all control unit modules and control units networked via CAN). Note: àà When the common fault is activated, the LED setting “Fault” in the CM and SM properties is set to “Alternative functions” and the drop-down menu is deactivated. Please note: àà When the common fault is subsequently deactivated the function of the LED must be restored manually. (-> see the chapters “LEDs” on CM and SM) [] [] Reset suppression when alarm is queued Short-circuit monitoring drive lines The reset function via FT4 push button is disabled as long as an alarm e.g. fire alarm system is queued. The drive lines are energised constantly for short-circuit monitoring. A short-circuit is detected by the monitoring of the DM fuse. Please note: àà The vent switch function must be set to latching. Dead man, automatic step and limiting the run time all disable shortcircuit monitoring with windows opened. … Purpose MBZ 300 Configuration software àà Activation of 24V drives for RWA and/or ventilation purposes. àà Evaluation of ventilation signals and status contacts. àà Monitoring of the drive cable (see MBZ 300 installation instructions). … V 1V 3V Depending on the switched status NA (not actuated), L_L_OPEN, L_L_CLOSE or L_L_ STOP Concerns the signal inputs: Depending on the switched status NA (not actuated), E_A_ OPEN (status contact 1) or E_A_CLOSE (status contact 2) MBZ 300 Configuration software DM - Drive module Number of cycles Counts how often the line has been switched open and closed Input 1: When the configured input … .1 Vent switch function (partner level) In the standard configuration the push button input of the drive module in a ventilation group is linked this drive module itself. Other ventilation group assignment -> see the chapter “Ventilation groups”. Function setting Behaviour with button OPEN pressed Behaviour with button CLOSE Stop by pressed [] Biased-off (switch function) Note: The default setting is OPEN and CLOSE The interval mechanism is then disabled. [] OPEN [] CLOSE The DMs switch to “OPEN” as long as the button is pressed. If the button is released, the DMs switch off again. If “OPEN” is not set to biased-off, the DMs switch to the “OPEN” direction of travel permanently*. If “CLOSE” is not set to biIn biased-off direction: Reased-off, the DMs switch to lease the push button the “CLOSE” direction of travel permanently*. If only one is active, the other is in self-locking mode: STOP The DMs switch to “CLOSE” as = both push buttons at the long as the button is pressed. same time If the button is released, the DMs switch off again. 27 DM - Drive module [•] MBZ 300 Configuration software Locking Modules switch permanently* to “CLOSE” direction of travel. [] Modules switch permanently* Pressing the same push to “CLOSE” direction of travel. button again [] Modules switch permanently* to “OPEN” direction of travel. Stop function Modules switch permanentsame button ly* to “OPEN” direction of travel. Stop function both buttons Pressing both buttons again *) “permanently” means the set “drive line switch-off time” at the most … .3 Mode of operation [•] Standard motor [] Hold-open magnet operation This mode is designated for standard 24V drives on ventilation flaps and windows. The change in direction is achieved by reversing the polarity of the supply voltage. The drive lines are only supplied (for the duration of the drive line switch-off time) when an OPEN or CLOSE signal is pending. In the event of an alarm, post cycle control is also active unless it has been deactivated. This mode is designated for the connection of hold-open magnets. The module only reacts to alarm commands. The LED “Window OPEN” on the module and on any vent switch connected (without function!) lights up red in idling status. The LED indicator “Window OPEN” on the fire button is not active. Note: àà In hold-open magnet mode of operation the maximum current must be taken into account (30% of the power supply). The rechargeable battery running time must be calculated separately. When current is permanently tapped, a back-up time of 72 h can no longer be achieved. Mixed designs (drives and hold-open magnets) must be given special attention. àà This setting requires the alarm direction of travel “Emergency-OPEN”. IMPORTANT: àà If a DM with hold-open magnet mode is connected to a control unit, the LED indicator “Window OPEN” is not active on the fire buttons connected. We recommend using separate control units for standard drives and hold-open magnets. Note: The vent switch function, interval mechanism, restoring a switched status for a lower priority, runtime and ventilation duration are disabled Idling status: Alarm status: 28 Drive line actuated (“OPEN”) Drive line off MBZ 300 Configuration software [] DM - Drive module Pressure gas genera- This mode is designated for the connection of pressure gas generators. The module only tor operation reacts to alarm commands. Note: àà If “Impulse duration” = … .6 MBZ 300 Configuration software 0..10 s (standard: … .8 Status contacts The drive module has two inputs for which parameters can be set and at which status contacts can be connected. The type of contact can be selected: àà Closer contact àà Opener contact How to process the pending status contacts is set under this menu item. 30 MBZ 300 Configuration software Status contact 1: Selection Not available End position status CLOSE End position status flashes CLOSE Status contact 2: DM - Drive module Function The status contact is ignored. The “CLOSE” end position is indicated by the green LED on the vent switch. During closing movement the LED is dark. The yellow LED “Window OPEN” on the RWA button is switched off permanently. As “End position status CLOSE”. The yellow LED “Window OPEN” on the RWA button is switched off permanently. The specific LED flashes during closing movement. Disable input OPEN Disable input CLOSE Disable input OPEN CLOSE Switch ERM Movement “OPEN” is blocked. Disable input OPEN Disable input CLOSE Disable input OPEN CLOSE Switch ERM Movement “OPEN” is blocked. Movement “CLOSE” is blocked. Movement in the “OPEN” and in the “CLOSE” direction is blocked. If an ERM is used, this input appears in the ERM properties for selection of the relay. If this input is active (contact closed), the selected relay is switched. Not available The status contact is ignored. End position status OPEN The “OPEN” end position is indicated by the red LED on the vent switch. During opening movement the LED is dark. The yellow LED “Window OPEN” on the RWA button is switched on permanently. End position status flash- As “End position status OPEN” es OPEN The yellow LED “Window OPEN” on the RWA button is switched on permanently. The specific LED flashes during opening movement. Movement “CLOSE” is blocked. Movement in the “OPEN” and in the “CLOSE” direction is blocked. If an ERM is used, this input appears in the ERM properties for selection of the relay. If this input is active (contact closed), the selected relay is switched. Using the end position statuses The end position statuses are used as a clear indicator of end positions on the vent switch and RWA button. End position contacts must be available on the window / from the drive. Special features with only one end position status: If only one of the end position statuses is used, only the respective LED on the vent switch reacts to the status. The other LED behaves as in operation without end position statuses. àà When “end position status OPEN” or “end position status CLOSE” is selected, the respective selection is automatically set to “alternative function” and the drop-down menu is deactivated. àà Please note: If a different selection is made afterwards, the respective LED function must be set manually to “standard function”. Using the disable inputs Use of the status contacts as disable inputs temporarily blocks movement in order to avoid collisions between windows and shade systems, for example. The inputs are active both in ventilation and alarm mode. (However, please refer to the special features of alarm mode.) As long as a disable input is active, no movement takes place in the respective direction. When the input disable has been deactivated, movement begins automatically. Special features of alarm mode: If a disable input is not disabled until after an alarm has been triggered, it is ignored. This is to avoid a broken cable occurring in an alarm case preventing the window opening. 31 DM - Drive module MBZ 300 Configuration software The connection of the disable input to a relay which is actuated by the control unit in the event of an alarm is not possible since disabling would be too late due to the switching time of the status input relay. Special features of hold-open magnet mode: In hold-open magnet mode only “Disable input OPEN” has a function. Since the hold-open magnet transmits “OPEN” permanently in idling status and is switched off in the event of an alarm, the disable input disables switchoff in this case. Otherwise the function corresponds to the behaviour in standard motor mode. Influence on times: Drive line switch-off time: Switch-on and changeover delay: Runtime: Ventilation duration: Interval mechanism: Is restarted after every release. Is restarted after release. Is interrupted after disable. Is restarted after disable as long as necessary until a release is available when the time expires. Interval time is not interrupted by disable. Special features for power failure “Close all windows”: If the disable input is disabled, closing movement remains disabled despite subsequent release until mains power is restored. When disable input OPEN, CLOSE or OPEN CLOSE is selected, “Disable mode active” appears in the operating mode menu. In the runtime menu the line “Disable inputs will be ignored in the emergency-OPEN case after ...sec” is released for setting. ATTENTION Please make sure when using the disable inputs (particularly for sequence control) that you use the switching contacts correctly and proceed with corresponding care during testing. The reliability of the RWA system must be safeguarded. There is a residual risk: if the disable input is not cleared in the alarm case the windows cannot be opened. If for sequence control a time is set after which the disable inputs are ignored, collisions can occur between e.g. windows and shade systems. The system must be coordinated with the fire protection planner responsible. Ignore disable inputs The disabling of emergency-OPEN movement by a faulty contact in the event of an alarm should be avoided, or if release is given after a delay in the alarm case you can set that the disable input can be overridden after a certain time here and the movement is still started. [] Disable inputs are ignored in emergency-OPEN cases after: 0...999 s (standard: … s = never (remain disabled) Special features: If a disabled disable input is ignored during emergency-OPEN and remains disabled following reset, it is immediately ignored the next time an alarm is given. Note: If the reset direction is blocked, it behaves in the same way as ventilation in the “CLOSE” direction. The behaviour during automatic CLOSE and disable input in the “CLOSE” direction is identical to ventilation in the “CLOSE” direction. 32 MBZ 300 Configuration software DME drive module - extended version … A, SELV Reset 33 SM Sensor module MBZ 300 Configuration software … Properties – SM In the standard configuration the SM forms a new fire section. All the following DMs (up to the next SM) are assigned to this fire section. For other fire section assignment see the chapter “Fire sections”. 34 MBZ 300 Configuration software SM Sensor module … s, second time = 10 s, third time = 15 s etc.) 35 SM Sensor module MBZ 300 Configuration software … are thus activated. An alarm is triggered in the event of a line break or short-circuit on detector line 2. MBZ 300 Configuration software SM Sensor module … .9 Messaging relay Selection of the message which leads to the messaging relay switching. trigger in case of: Never Rechargeable battery fault Mains voltage fault Control unit fault Common alarm of the group No reaction. Note: Should be set if the relay is used to report expiry of maintenance time. The closer contact is closed when the rechargeable battery monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The closer contact is closed when the mains voltage monitoring is in fault-free status. If the mains voltage fails, the relay is switched off after a delay. See the chapter “PM mains failure” The messaging relay switches in the event of a fault within the control unit group (concerns faults on modules of the control unit). Closer is closed in the fault-free status. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). The messaging relay switches following a common fault. The closer contact is closed in the fault-free status. When a common fault has been eliminated, the fault status is reset after a delay of 60 s. The fault status is reset immediately on the control unit where the fault occurred. If the mains voltage fails, the relay is switched off after a delay (see the chapter “PM mains failure”). 37 SM Sensor module MBZ 300 Configuration software General alarm (default) Restricted group alarm Delayed group alarm Impulse for alarm reset The messaging relay switches when there is an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! If all alarm groups are deleted, the setting “Never” will appear after the next charging cycle. The messaging relay switches on for 300 s in the event of an alarm within the group (fire section). The closer is closed in the alarm status. Note: Changeover contact NC/NO is inverted! The messaging relay switches on after a … .10 LEDs The function of the LEDs on the RWA button are shown here. If “alternative function” is selected, the display of the LEDs depends on the special system functions set. 38 MBZ 300 Configuration software 11 WM - Weather module WM - Weather module … Status – WM The following is displayed under the weather module tab: àà the evaluated current wind direction àà the evaluated main wind direction (average over 10 min!) The control unit only reacts depending on the wind direction when the red arrow is visible (depending on DM settings -> see the chapter “Emergency-OPEN for wind directions (for SHEV according to EN 12101-2)”) The position of the wind vane can be adjusted correctly by activating the “wind direction diagnostics”. The averaging of main wind direction is still active – it is necessary to wait for this average for a test. àà Rain / no rain àà Current wind speed and set threshold. àà Module status text The current operating mode is displayed here. The current status and faults are displayed, as described in the installation instructions. 39 WM - Weather module MBZ 300 Configuration software … .3 Delay values (for ventilation) Is used to delay the switching reaction to wind e.g. constant opening and closing is avoided in gusty wind conditions. Wind switch-on delay Wind switch-off delay 0...254 s (standard: 20 s) 0...3600 s (standard: 1200 s) Notes on testing: Depending on the sensors connected there can be a changeover delay time. Rain sensors in particular have a pre-set drying time which may vary depending on the rain duration/intensity. 40 MBZ 300 Configuration software WM - Weather module … m/s The messaging relay switches when the wind direction sensor has detected the “Main wind direction”. Note: The setting is deactivated if no wind direction sensor has been selected. The closer is closed in the alarm status. Note: Either “Wind” or “Main wind direction” can be detected. The messaging relay is switched off in rechargeable battery operation. 41 ERM relay module 12 MBZ 300 Configuration software ERM relay module … .3 Module status text The current operating mode is displayed here. The current status and faults are displayed, as described in the installation instructions. 42 MBZ 300 Configuration software ERM relay module … .1 General relay configuration Signals from ventilation and weather groups, fire sections as well as faults can be signalled at one relay. àà If the function of a relay is redefined by software, the relay remains in its current switched position until a switching signal occurs. This means that an incorrect status can be displayed before this first switching takes place. àà The relays are bi-stable. In other words, the status remains even if there is a drop in voltage. 43 ERM relay module MBZ 300 Configuration software … .4 Alarm relay configuration (fire sections) As soon as a relay module is integrated in a control unit, additional configuration possibilities appear in the fire sections. Here, selection can be made of the relays which are to be switched when an alarm occurs for this fire section. A relay can also be assigned to different fire sections. In higher-order fire sections relay modules are available for all control units. With the aid of higher-order fire sections the alarm of another control unit can be displayed on a relay module, for example. 44 MBZ 300 Configuration software ERM relay module PLEASE NOTE: A multiply assigned relay is switched off as soon as one of the fire sections is reset, even if other fire sections are still actuated. … s. àà Tip: A real window position can only be mapped by end position contacts (e.g. reed-contacts) 45 ERM relay module MBZ 300 Configuration software … .6 Signalling of weather signals As soon as a relay module is integrated in a control unit, additional configuration possibilities appear in the weather groups. Here, the statuses of the weather signals can be assigned to the relays. If a relay parameters are set for the display of “Wind” and/or “Rain”, it is active in “Wind” and/or “Rain” until the weather signal(s) is no longer pending. If the weather group is active, the ERM relay switches. 46 MBZ 300 Configuration software 13 Fire sections Fire sections The term fire section (or “alarm group”) is used in the context of the MBZ 300 for a group which is activated by specific alarm signals. … Fire section details The fire sections can be formed flexibly. 47 Ventilation groups MBZ 300 Configuration software … Ventilation groups Add Edit Delete 48 Ventilation groups are added by clicking this button. The ventilation group to be edited must be selected from the list. When this button is clicked, the program jumps to the view of the ventilation group selected. The ventilation group to be deleted is selected from the list and deleted by clicking the button. MBZ 300 Configuration software Ventilation groups … .4 Description A text describing the ventilation group can be entered. 49 Weather groups 15 MBZ 300 Configuration software Weather groups The weather group is only valid for the ventilation function. … .4 Description A text describing the weather group can be entered. 50 MBZ 300 Configuration software 16 Higher-order fire section / ventilation groups / weather groups Higher-order fire section / ventilation groups / weather groups Example: If several control units are networked via CAN, higher-order groups are available. Here, inputs and drive lines from several control units can be summarised in groups. (see the chapters “Fire sections” / “Ventilation groups” / “Weather groups”) PLEASE NOTE: An input signal (detector line, ventilation line or weather signal) may only occur in a maximum of one group! Multiple use is not possible otherwise behaviour is not predictable. Please check the local groups for the individual control units and delete if necessary! 51 General information 17 MBZ 300 Configuration software General information … Settings by software and VdS Please note: Some settings which can be made by software lead to the VdS certificate no longer being valid, since monitoring functions which represent requirements according to VdS can be switched off specifically through configuration. Settings affected: àà Disable post cycle control àà Lockout function enabled àà Disable line monitoring of the alarm lines àà Start-up delay (note specified smoke and heat extraction system opening time) àà Disable inputs are ignored in emergency open after > … Sequence for commissioning and configuration by software see the chapter “Procedure for configuration of a control unit” … .2 The control unit is not shown correctly in the software (modules missing etc.) XX XX XX XX XX XX Keep the reset push button on the CM pressed for 20 s (until all modules are flashing - not longer!). This ensures the modules are addressed correctly. This process is essential when the hardware (modules and order) has been changed. Connect USB cable to CM and connect to the laptop. Start the software “Individual control unit” (please make sure you always use the latest version (see the chapter “Software installation).) Check the firmware version of the control unit to make sure it is up-to-date Carry out firmware update if necessary (see the chapter “Firmware update”) Load default settings (see the chapter “System configuration”) PLEASE NOTE: All previous settings are deleted! XX XX XX 52 Adapt rechargeable battery size and number of PMEs (see the chapter “Rechargeable battery settings”). Set the individual configuration Transmit to the control unit MBZ 300 Configuration software FAQs … .3 The software cannot be started completely. / The software “crashes” during loading of the control unit. XX XX XX XX XX Terminate the program using the task manager if necessary. Remove the USB cable Check the USB cable and the USB connection. If the cable or connection is faulty the connection cannot be established properly and the software cannot load the configuration completely. Check the capacity utilisation of your computer and the assignment of the correct driver (assign again if necessary -> see the chapter “Software installation”). Reboot the software and connect the USB cable again. … Does the module sequence matter? The software allows numerous different settings; nevertheless we recommend setting up the modules as closely as possible to standard configuration (better overview): àà A new fire section begins with CM / SM àà Do not set SM at the end àà WM in last position àà ERM does not have any restrictions but should also be set at the end for reasons of clarity. àà If there is a DM attached on the left-hand side of the respective SM, the DM fault is not indicated on the SM. … General trouble shooting Use the different displays to find the faulty spot: àà LED code on the module (see MBZ 300 installation instructions) àà Log file àà Status pages of the modules with: àà States and current values (target value comparison with this document) àà Fault display àà Measurement of the various outputs and inputs and comparison with the display in the PC software … Trouble shooting where several control units are in one CAN network XX XX “Divide and rule”: Only connect the local with the nearest control unit (check CAN terminals!). àà Terminate this section. àà Disconnect all other CAN connections. àà Open the “networked control units” software. àà Check whether both control units are available. The points must be repeated accordingly for the other sections. … s CLOSE - OPEN 120 s X (300 s) Y (40 s) X (300 s) Z each time (10 s) 53 Meaning of the log entries 20 MBZ 300 Configuration software Meaning of the log entries See the chapter “RealTime_Log - control unit”. All possible log entries are listed here. During operation, only a limited selection of these will actually occur. The list also includes the logging level from which this type of message can occur. The logging levels are classified as follows. A lower (or finer) logging level automatically includes the higher-order logging level entries. This means that error entries are always included in the log when this is set to alarm. Here are the possible logging levels in order from the lowest to the highest. LOG_FINE LOG_INFO LOG_ALARM LOG_ERROR %d SM %d The finest logging level: everything is logged. This provides a precise overview of the processes in the system, but the high memory requirements mean that the log does not extend far into the past. The switching processes are entered in the log. Faults and alarm states and their triggering are reported. Only errors are recorded. Stands for any number, this is usually the module ID which this log entry refers to. SM_0 is the CM. CM and SM are equated here. Log entry Bus Fault Exception, System HALT! CAN Main: CANSendMsg() Error! CAN XmitQueue: Error %d! CAN: buff emptyed! Granularity LOG_ERROR CAN: kfg fkt mismatch! LOG_ERROR Fault pattern A fault occurred during access to the system bus. The CAN interface of this control unit could not send a message. This control unit could not transmit a CAN message Attempt is being made to transmit something that isn't there. A command has not been received completely. CAN: MBOX_CAN buffer LOG_ERROR full The control unit cannot keep up with transmission. CAN: mbusb, buffer processing problem! LOG_ERROR Buffer is overflowing during remote servicing of a control unit via CAN. CAN: mbusb, eval_cmd LOG_ERROR buffer problem! This control unit does not understand a command that came via CAN. CAN: Modbus commu- LOG_ERROR nication failure %d! CAN: rec array overflow! LOG_ERROR CAN cannot be read properly. LOG_ERROR LOG_ERROR LOG_ERROR CAN: rec queue full! LOG_ERROR CAN: reception while processing! LOG_ERROR canf_mbm_writeread(): LOG_ERROR too many resends! canf_xmit_konf(): LOG_ERROR CANSendMsg timeout! canfi_eval_cmd, requesting resend... 54 LOG_ERROR Can only occur when someone actively interferes with data transfer. Note Hardware fault? Replace CM. Check the CAN module Check the CAN module Reboot CM Is compensated automatically. Has the CAN system been configured properly, are there any “meaningless” rules? If one of the control units does not react, reboot this and start the configuration process again. Do all the control units have the same firmware version? CAN module OK? Do all the control unit have the same firmware version, what else is attached to the CAN cable? Too many different commands have been sent Has the CAN system been to this control unit. configured properly, are there any “meaningless” rules? Unknown data were received during CAN Do all the control units command processing. have the same firmware version? A message has been repeated too often with- Is a control unit switched out an answer being received. off, disconnected? (Cable?) A message could not be sent in time, possible Should not occur. If it does data loss. occur during a saving process - repeat this. The command has not been received comIs not really a fault in the pletely and is being requested again. strict sense, since it is compensated. If it occurs often, however, it is a sign that there is something wrong with the CAN-bus. MBZ 300 Configuration software Meaning of the log entries canfi_mbusb_received(): MBOX_CAN error %d! CANSendMsgQ(): Queue full! Clock Source failure (Clock Security System)!!! CM IWDG-RESET!!! LOG_ERROR An unexpected error has occurred during reception of a CAN message. Check the CAN module LOG_ERROR This control unit could not send a CAN message due to buffer status. The clock is faulty. Check the CAN module Creating autoKonfig, eepCfg ver.> 3... LOG_INFO Creating autoKonfig... LOG_INFO DM %d: Alarm AUF DM %d: ALARM bei deaktiviertem DG! LOG_ALARM LOG_ALARM LOG_ERROR LOG_ERROR DM %d: Alarm reset bei LOG_ALARM deaktiviertem DG! DM %d: Alarm reset, DG spannungslos LOG_ALARM DM %d: Alarm ZU LOG_ALARM DM %d: ALARM, DG aktiviert DM %d: ALARM, HM freigegeben DM %d: Alarm-Reset LOG_ALARM DM %d: ALARM, Überschreiben des Sperrkontakts DM %d: AUF DM %d: AUF (LZM) LOG_ALARM DM %d: Auto-ZU DM %d: Fenster ist offen DM %d: Fenster ist geschlossen LOG_INFO LOG_INFO DM %d: HM aktiviert LOG_INFO DM %d: HMinit AUF DM %d: ist schon AUF LOG_INFO LOG_FINE DM %d: ist schon ZU LOG_FINE DM %d: Linie spannungslos LOG_FINE LOG_ALARM LOG_ALARM LOG_INFO LOG_INFO LOG_INFO Hardware fault? Replace CM. If the system “crashes” or the watchdog thinks Should not occur. Firmthis is the case, it triggers a reboot. ware update, otherwise replace CM. After the start an unknown configuration was ... found in the EEPROM, a new configuration which matches the modules found is being created and used. After the start a new configuration which ... matches the modules found is being created and used. This DM is opening due to an RWA case. ... Alarm was/was to be triggered at this DM, but The pressure gas genersince the pressure gas generator was deactiator should have been vated this did not work. (See “DM operating activated. mode”) The alarm status of a DM has been reset but Switch the pressure gas the pressure gas generator connected to the generator on. DM is still deactivated. (See DM operating mode) The alarm status of a DM has been reset but Connect the pressure gas the pressure gas generator connected to the generator to the power DM is without voltage. supply. This DM is being emergency-CLOSED due to ... an RWA case. This DM activates the pressure gas generator. Analogue to opening a window. The hold-open magnet on this DM has been ... released (i.e. voltage supply interrupted) With this DM the alarm status has been can... celled, it is “OPEN” and can be closed by the ventilation. The block contact is ignored in the alarm case ... after the time set. This DM is now opening. If this DM is not permitted to open further and its maximum OPEN runtime has been reached (follow-up time restriction). A DM closes automatically. This window of the DM motor line is open ... ... This window of the DM motor line is closed. The drive line switch-off time has expired completely in the CLOSE direction The hold-open magnet of this DM has been activated due to an RWA case. A timer has been started for this DM. If this DM is not permitted to open further and its maximum OPEN runtime time has been reached. The hold-open magnet of this DM has been activated due to an RWA case. . The voltage supply for the DM drive line has been switched off (after the drive line switchoff time has expired!) ... ... ... ... ... ... ... ... 55 Meaning of the log entries MBZ 300 Configuration software DM %d: LT AUF LOG_FINE DM %d: LT STOP LOG_FINE DM %d: LT ZU LOG_FINE DM %d: LZMinit ZU DM %d: LZM-Stop LOG_FINE LOG_INFO DM %d: no key LOG_FINE DM %d: NOTAUF LOG_ALARM DM %d: STOP DM %d: STOP durch Sperrkontakt DM %d: Sperrkontakt … has been deactivated in CLOSE and OPEN direction This DM is now closing. Indicates that the log entries found are faulty and the log thus had to be deleted. This can happen if a configuration from a too recent configuration program is used by firmware that is too old. The configuration requires that functions which are not available in the firmware should be used. The CPU has jumped to a position where it is not allowed to land. No communication was possible with y of x modules in one cycle. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... This can happen when power supply and rechargeable battery both fail and the voltage suddenly drops severely. In other words when there is not sufficient voltage available during log writing. CM Firmware update. Fault in the CM firmware or hardware fault. If this occurs sporadically it is not a problem, since it is compensated, but if it occurs permanently one or more module(s) is(are) faulty. MBZ 300 Configuration software Meaning of the log entries Loading Eeprom Konfig... mbf_querysystem(): konfig present, %d IOM's are missing! Mem Manage Exception, System HALT! LOG_INFO NMI Exception LOG_ERROR PM Poll Error LOG_ERROR PM(E): Akkufehler LOG_ERROR LOG_ERROR LOG_ERROR PME1 angeschlossen, LOG_ERROR aber nicht konfiguriert PME2 angeschlossen, LOG_ERROR aber nicht konfiguriert PM(E): Netzfehler LOG_ERROR PM(E): OK LOG_INFO PM/IOM Poll ok! LOG_ERROR PM: Netz und Akku fehlt LOG_ERROR RTC count lost!!! Semaphore deadlock: %s, err: %d LOG_ERROR LOG_ERROR SM %d: NOT_AUF BMZ1 LOG_ALARM SM %d: NOT_AUF BMZ2 LOG_ALARM SM %d: NOT_AUF RM1 LOG_ALARM SM %d: NOT_AUF RM2 LOG_ALARM SM %d LED Stoerung: %d LOG_ERROR SM %d: Alarm-Reset LOG_ALARM SM %d: BMZ an RM1 NOT_ZU LOG_ALARM After the start the configuration was loaded ... from the EEPROM and is being used. Modules in the control unit have been recon- Re-establish the default nected or disconnected since the last start-up. configuration and address/ configure correctly. Fault in memory management: Corrupt firmware, memory faulty, VDS self-test entries available? Replace CM. No access to the clock. Hardware fault? Replace CM. Communication with the PM not possible via Hardware fault? Replace the Modbus. PM/CM? The PM is missing a rechargeable battery. Check the rechargeable battery + cables, use the configuration software to check whether PMEs and battery capacity have been set properly. If this does not help, replace the PMEs or the PM on the basis of the values shown on the PM status page. There is a PME1 available in the control unit Start configuration softbut it has not been configured. ware and set the correct number of PMEs. There is a PME2 available in the control unit Start configuration softbut it has not been configured. ware and set the correct number of PMEs. The PM or the control unit is no longer drawing Check power supply, PM. current from the power supply. The PM has mains current and rechargeable ... battery again. (This message can of course only occur if one of these elements was missing.) Only occurs in combination with IOM Poll Error Not an error %d/%d missing and means that the PM was OK in this context. A fault has occurred on the SM but there is Desired behaviour... no reaction on account of the energy-saving mode. The CM no longer has the current time. Synchronise with the PC. A resource of the CM operating system could Rebooting the CM can not be released, as a result the CAN system can eliminate the problem. no longer function, for example. Reset has been triggered with the CIE1 at this ... SM. Reset has been triggered with the CIE2 at this ... SM. Reset has been detector line … ... at this SM. 57 Meaning of the log entries MBZ 300 Configuration software SM %d: BMZ an RM2 NOT_ZU SM %d: Linienfehler Handmelder! SM %d: Linienfehler Not-ZU! SM %d: Linienfehler RM1! SM %d: Linienfehler RM2! SM %d: LT AUF LOG_ALARM Reset has been triggered with detector line … LOG_ALARM SM %d: NOT_AUF Reset LOG_ERROR Failure SM %d: NOT_ZU LOG_ALARM 58 SM %d: NOT_ZU (res) LOG_ALARM SM%d: Mreset LOG_INFO STL: >>> RAM Error (March C- Run-time check) STL: Abnormal Clock Test routine termination STL: Class B variable error (clock test) STL: Clock Source failure (Run-time) STL: Control Flow Error (main loop) STL: Control Flow error in RAM-Test-ISR STL: Run-time FLASH CRC Error STL: Run-time FLASH CRC OK, %d cycles STL: SRAM-Check OK, %d cycles STL: Stack overflow LOG_ERROR LOG_ERROR The self-test routines (VDS) have established a fault. The self-test routines (VdS) have established a fault on the clock. The self-test routines (VDS) have established a fault. The self-test routines (VDS) have established a fault. The self-test routines (VDS) have established a fault in the flash. The self-test routine flash check (VDS) has been carried out successfully x times. The self-test routine flash check (VDS) has been carried out successfully x times. The self-test routines (VDS) caused a fault. STL: Start-up CPU Test Failure STL: TOO MANY REBOOT FAILURES, LOCKING UP!!! LOG_ERROR The CPU is no longer working properly LOG_ERROR For some reason the CM has rebooted very often, a fault has been established. LOG_ERROR LOG_ERROR LOG_ERROR LOG_ERROR LOG_FINE LOG_FINE Check the cable, if test negative replace the SM. Check the cable, if test negative replace the SM. Check the cable, if test negative replace the SM. Check the cable, if test negative replace the SM. ... ... ... ... ... Check the cable, if test negative replace the SM. ... ... ... Hardware fault? Replace CM. ... Hardware fault? Replace CM. Hardware fault replace CM. Hardware fault? Replace CM. MBZ 300 Configuration software Meaning of the log entries Stoerung bei PF DM %d: %d LOG_ERROR Stoerung bei PF SM %d: %d LOG_ERROR Stoerung DM %d: %d LOG_ERROR Stoerung ERM %d: %d LOG_ERROR Testmode initiated... LOG_ERROR Testmode: KonfigTask LOG_ERROR abgebrochen... Usage Fault Exception, LOG_ERROR System HALT WM %d: kein Regen LOG_INFO WM %d: REGEN WM %d: WIND LOG_INFO LOG_INFO WM %d: WIND T%d WM %d: Wind unterhalb Schwelle WM %d: WRG fehlt! LOG_INFO LOG_INFO LOG_ERROR A fault has occurred on the DM but there is no reaction on account of the energy-saving mode. A fault has occurred on the SM but there is no reaction on account of the energy-saving mode. Indicates a fault on this DM, usually a detector line fault, with some old DMs there was another fault here which made this occur briefly, but it was not actually a fault. Indicates a fault of the system voltage on this ERM This is not CM firmware in the actual sense. There is only a test program in the CM. This is not CM firmware in the actual sense. There is only a test program in the CM. The bits did not make sense to the CPU. A WM has recognised that it has stopped raining. A WM has detected rain. A WM has detected wind from a certain direction. Shows that the WM has detected wind. The wind has fallen under the threshold on one of the WMs. There is a wind direction finder configured in a WM but the WM cannot detect it. Desired behaviour... Desired behaviour... If a line fault can be excluded and the fault only occurs briefly, we recommend a DM firmware update. If neither of these approaches was successful, the DM affected should be replaced. Firmware update with the boot loader. Firmware update with the boot loader. Firmware OK? Flash again? Hardware fault? Replace CM. ... ... ... ... ... Is the sensor/WM, cable working? WM / test sensor => replace. If you have any support requests, always submit the “Error log” of the configuration SW with your request. You will find the “ErrorLog.txt” in the licence key directory. 59 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 Hungary GEZE Hungary Kft. E-Mail: office-hungary@geze.com www.geze.hu Scandinavia – Sweden GEZE Scandinavia AB E-Mail: sverige.se@geze.com www.geze.se Baltic States – Lithuania / Latvia / Estonia E-Mail: baltic-states@geze.com Iberia GEZE Iberia S.R.L. E-Mail: info.es@geze.com www.geze.es Scandinavia – Norway GEZE Scandinavia AB avd. Norge E-Mail: norge.se@geze.com www.geze.no Benelux GEZE Benelux B.V. E-Mail: benelux.nl@geze.com www.geze.be www.geze.nl India GEZE India Private Ltd. E-Mail: office-india@geze.com www.geze.in Scandinavia – Denmark GEZE Danmark E-Mail: danmark.se@geze.com www.geze.dk Bulgaria GEZE Bulgaria - Trade E-Mail: office-bulgaria@geze.com www.geze.bg Italy GEZE Italia S.r.l E-Mail: italia.it@geze.com www.geze.it Singapore GEZE (Asia Pacific) Pte, Ltd. E-Mail: gezesea@geze.com.sg www.geze.com China GEZE Industries (Tianjin) Co., Ltd. E-Mail: chinasales@geze.com.cn www.geze.com.cn GEZE Engineering Roma S.r.l E-Mail: italia.it@geze.com www.geze.it South Africa GEZE South Africa (Pty) Ltd. E-Mail: info@gezesa.co.za www.geze.co.za 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 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 Romania GEZE Romania S.R.L. E-Mail: office-romania@geze.com www.geze.ro Russia OOO GEZE RUS E-Mail: office-russia@geze.com www.geze.ru Switzerland GEZE Schweiz AG E-Mail: schweiz.ch@geze.com www.geze.ch Turkey GEZE Kapı ve Pencere Sistemleri E-Mail: office-turkey@geze.com www.geze.com Ukraine LLC GEZE Ukraine E-Mail: office-ukraine@geze.com www.geze.ua United Arab Emirates/GCC GEZE Middle East E-Mail: gezeme@geze.com www.geze.ae United Kingdom GEZE UK Ltd. E-Mail: info.uk@geze.com www.geze.com GEZE GmbH Reinhold-Vöster-Straße 21–29 71229 Leonberg Germany Tel.: 0049 7152 203

GEZEthermic software version

MBZ 300 PC software

MBZ 300 PC Software

Software KNX Product Database IQ box KNX

GC 403 WDS

Wind direction sensor for use with the MBZ 301 control panel