Related Manuals for HMS Networks Intesis INKNXMBM1000200
Summary of Contents for HMS Networks Intesis INKNXMBM1000200
- Page 1 ENGLISH Modbus RTU Client to KNX TP Gateway USER MANUAL Version 1.0 Publication date 2023-02-16...
- Page 2 The information in this document shall therefore not be construed as a commitment on the part of HMS Networks and is subject to change without notice. HMS Networks makes no commitment to update or keep current the information in this document.
-
Page 3: Table Of Contents
Modbus RTU Client to KNX TP Gateway Table of Contents 1. Description and Order Codes ..................... 1 2. General Information ........................ 2 2.1. Intended Use of the User Manual ..................2 2.2. General Safety Information ....................2 2.3. Admonition Messages and Symbols ..................2 3. -
Page 4: Description And Order Codes
Description and Order Codes Modbus RTU Client to KNX TP Gateway 1. Description and Order Codes Modbus RTU Client to KNX TP Gateway ORDER CODE LEGACY ORDER CODE INKNXMBM1000200 INKNXMBM1000100 USER MANUAL Version 1.0 Page 1 of 20... -
Page 5: General Information
Modbus RTU Client to KNX TP Gateway General Information 2. General Information 2.1. Intended Use of the User Manual This manual contains the main features of this Intesis gateway and the instructions for its appropriate installation, configuration, and operation. The contents of this manual should be brought to the attention of any person who installs, configures, or operates this gateway or any associated equipment. - Page 6 Admonition Messages and Symbols Modbus RTU Client to KNX TP Gateway NOTE Additional information which may facilitate installation and/or operation. Helpful advice and suggestions. NOTICE Remarkable Information. USER MANUAL Version 1.0 Page 3 of 20...
-
Page 7: Overview
Overview 3. Overview 3.1. Inside the Package Items included: • Intesis INKNXMBM1000200 protocol translator gateway • KSN label • Installation sheet 3.2. Gateway Main Features • Accredited with the main certifications for electronic equipment, including the official KNX certification. To know more, check the website's Technical Documentation section. -
Page 8: Gateway Capacity
Gateway Capacity Modbus RTU Client to KNX TP Gateway 3.4. Gateway Capacity Element 100 version Modbus interface Maximum number of Modbus 100 (see note below) server devices supported Type of Modbus server devices Those supporting Modbus protocol supported communication over RTU (EIA-485) Modbus addresses range 1 to 255 Maximum number of Modbus... -
Page 9: Hardware
Modbus RTU Client to KNX TP Gateway Hardware 4. Hardware 4.1. Mounting IMPORTANT Before mounting, please ensure that the chosen installation place preserves the gateway from direct solar radiation, water, high relative humidity, or dust. IMPORTANT Ensure the gateway has sufficient clearances for all connections when mounted. NOTE Mount the gateway over a DIN rail, preferably inside a grounded metallic industrial cabinet. -
Page 10: Connection Procedure And Dip Switch Setting
Connection Procedure and DIP Switch Setting Modbus RTU Client to KNX TP Gateway 4.2. Connection Procedure and DIP Switch Setting CAUTION Before connecting the gateway, disconnect the KNX bus from its power supply. Use this DIP switch to configure the EIA-485 port: •... -
Page 11: Led Indicators
Modbus RTU Client to KNX TP Gateway LED Indicators 4.3. LED Indicators There are two LEDs below the DIP switch. LED ID and color Pattern Description KNX programming mode Programming mode disabled Steady On Programming mode enabled Flashing To locate the device Power/Modbus activity No power Steady On... -
Page 12: Push Button
Push Button Modbus RTU Client to KNX TP Gateway 4.4. Push Button This button activates the gateway's programming mode, which is needed for some ETS download variants: • Download All: It downloads the Individual Address, the Application Program, the Parameters, and the Group addresses. -
Page 13: Technical Specifications
Modbus RTU Client to KNX TP Gateway Technical Specifications 4.5. Technical Specifications • Front side: PC (UL 94 V-0) • Back side: PPO (UL 94 V-0) • Net dimensions (DxWxH): 32x36x92 mm Enclosure Colors: • Front side: light grey. RAL 7035 •... -
Page 14: Communication Interfaces
Communication Interfaces Modbus RTU Client to KNX TP Gateway 5. Communication Interfaces 5.1. KNX Interface This Intesis gateway continuously checks the status of the KNX bus. The behavior of each signal point is defined by the flags you set in the ETS configuration tool. This means, for instance, that when the communication is restored after a blackout, the gateway will retransmit the status of all the KNX groups marked as Transmit (T) and the update groups marked as Update (U). -
Page 15: Knx Points Definition
Modbus RTU Client to KNX TP Gateway Modbus Interface Code Name Meaning Gateway path The gateway could not allocate an internal communication path from the input to the output port for unavailable processing the request. Example: The gateway is misconfigured or overloaded Gateway target device The target device does not respond. - Page 16 Modbus Interface Modbus RTU Client to KNX TP Gateway Feature Description One of the following Modbus data coding formats can be used: • 16/32/48/64 bits unsigned • 16/32/48/64 bits signed (one's complement - C1) Data coding format • 16/32/48/64 bits signed (two's complement - C2) •...
-
Page 17: Configuration
Modbus RTU Client to KNX TP Gateway Configuration 6. Configuration 6.1. Prerequisites For this integration, you will need: • The items supplied by HMS Networks: – The Intesis gateway – The gateway documentation – The gateway ETS database • An ETS5 license (version 5.7.7 onwards). -
Page 18: General Configuration Tab
General Configuration Tab Modbus RTU Client to KNX TP Gateway 6.3. General Configuration Tab Access this tab to configure the Modbus connection parameters and the total number of signals to map. Figure 3. General configuration tab • Read on Init Delay: Determines the time in seconds to wait before all values are uploaded to the KNX network. IMPORTANT This setting applies only to objects with the Read on Init flag enabled. - Page 19 Modbus RTU Client to KNX TP Gateway General Configuration Tab NOTE ETS creates a tab for each device. – Number of signals: Defines the number of Modbus signals to integrate. Once a signal is defined, ETS automatically creates one or two KNX objects, depending on the selected function. When selecting both write and read functions, ETS creates two objects (one status object and one command object);...
-
Page 20: Device Tab
Device Tab Modbus RTU Client to KNX TP Gateway 6.4. Device Tab On the top side of this window, you can see the device information: • Device Name • Device Server Address • Device Signals Amount: Indicates the number of signals to integrate from the Modbus server device to the KNX system. -
Page 21: Intesis Modbus Device Manager Dca
Modbus RTU Client to KNX TP Gateway Intesis Modbus Device Manager DCA 6.5. Intesis Modbus Device Manager DCA NOTE The DCA Tab is a product-specific app and it is not available for ETS demo versions. You can download it from the KNX shop: look for Intesis Modbus Device Manager. If you have any questions about how to activate the DCA, read this article. - Page 22 Intesis Modbus Device Manager DCA Modbus RTU Client to KNX TP Gateway Figure 6. Import window Edit devices • Click the Replace icon to replace that device with a template. • Click the Delete icon to delete that device. Figure 7. Edit devices from the DCA main menu Update the firmware •...
-
Page 23: Sending The Configuration To The Gateway
Modbus RTU Client to KNX TP Gateway Sending the Configuration to the Gateway NOTE The firmware download speed depends on the APDU capacity of the interface you are using and the current bus traffic. The higher the APDU number, the higher the download speed. 6.6.
Need help?
Do you have a question about the Intesis INKNXMBM1000200 and is the answer not in the manual?
Questions and answers