Intesis (HMS Networks)
Protocol Gateways: KNX to BACnet, Modbus, DAIKIN, Mitsubishi, Samsung and 40+ HVAC Brands
Intesis (Barcelona, Spain, founded 2000, part of HMS Networks AB since 2018) is the world's leading specialist manufacturer of building automation protocol gateways, with the most comprehensive range of KNX integration modules for HVAC equipment of any single vendor. Intesis gateways connect KNX TP to BACnet/IP, BACnet MS/TP, Modbus RTU, Modbus TCP, OPC UA, and directly to the proprietary protocols of Daikin, Mitsubishi, Samsung, LG, Toshiba, Fujitsu, and 40+ other HVAC equipment manufacturers — enabling KNX control of VRF and split systems that would otherwise be inaccessible to building automation.
Ruolo nei nostri quadri
Come utilizziamo Intesis (HMS Networks)
IN701KNX BACnet gateway: the IN701KNX (1,000 signals version) or IN701KNX300000 (advanced, 3,000 signals) bridges BACnet/IP and BACnet MS/TP to KNX TP. As a BACnet/IP server: exposes KNX group addresses as BACnet objects (Analog Value, Binary Value, Multi-State Value) to any BACnet client (Siemens Desigo CC, Schneider EcoStruxure, Niagara Framework). As a KNX device: receives BACnet writes and forwards as KNX telegrams, reads KNX group address values and publishes as BACnet COV notifications. Configuration via IntesisBox MAPS software (free, Windows): signal table with BACnet object → KNX group address mapping, DPT assignment, and scaling. No programming required — pure configuration. ETS6: no ETS application program for IN701KNX; individual address assigned via MAPS → KNX bus. HVAC-specific gateways: Intesis manufactures dedicated gateways for every major VRF brand — using the manufacturer's proprietary service protocol on the equipment side, KNX TP on the building automation side. Examples: INMBSKNX000100 (Mitsubishi Heavy VRF to KNX, M-NET protocol, controls up to 32 indoor units): each indoor unit maps to KNX DPT objects for on/off, mode (heating/cooling/fan/auto), setpoint (DPT 9.001), fan speed (DPT 5.001), vane direction. INDKN001R000 (Daikin VRF to KNX, D-III Net protocol): similar objects, supports Daikin Intelligent Touch Controller override status. INSAMKNX (Samsung NASA to KNX): NASA (Network Air conditioning System Architecture) — Samsung's proprietary VRF protocol — translated to KNX. These gateways eliminate the need for custom CODESYS or Home Assistant drivers for HVAC integration, providing a certified, supported integration path for building automation projects. Modbus to KNX gateways: the IN70xKNX Modbus RTU/TCP to KNX family supports bidirectional translation between Modbus registers and KNX group addresses. Configuration in MAPS: Modbus register address (holding register 4xxxx, input register 3xxxx, coil 0xxxx) → KNX group address, DPT, scaling (e.g., Modbus register 400001 value 2500 / 10 = 250.0°C → KNX DPT 9.001). Poll interval: configurable per signal (1s-3600s). For energy meter integration: Carlo Gavazzi EM340 (Modbus RTU, 9600 baud) → Intesis Modbus-to-KNX → KNX group address for total active power (DPT 9.001) and energy import (DPT 12.001 4-byte counter). Alternative to WAGO 750-893 CODESYS approach for projects where programming expertise is limited. Integration in KNX panel: Intesis gateways are DIN-rail devices (4-6 modules wide). They require separate 24V DC auxiliary power (from panel SMPS, not from KNX bus). In panel layout: mount Intesis gateway adjacent to KNX line coupler or IP router in the panel. Cable routing: KNX bus cable (YCYM 2×0.8mm²) → KNX terminal on Intesis; RS-485 cable (YCYM 2×0.8mm² or screened twisted pair) → RS-485 terminal for Modbus RTU (observe A/B polarity: A=non-inverting, B=inverting). Ethernet: Cat5e or Cat6 cable to LAN switch — same VLAN as KNX IP Router. Label both KNX and RS-485 cable ends at gateway terminal with permanent labels showing signal names from MAPS configuration.
Intesis gateways sit at the intersection of KNX and every other building protocol — BACnet/IP for BMS integration, Modbus RTU for energy meters and HVAC controllers, and proprietary protocols for 40+ VRF brands. They convert KNX group address commands to HVAC setpoints and read HVAC status back to KNX for display and BMS reporting. No programming required: MAPS configuration tables replace CODESYS or Home Assistant scripting.
Utilizzato in questi tipi di progetto
Prodotti Intesis (HMS Networks)
Componenti chiave che installiamo
IN701KNX BACnet/IP to KNX gateway (1,000 signals)
Bridges BACnet/IP and BACnet MS/TP to KNX TP. Exposes KNX group addresses as BACnet objects (Analog Value, Binary Value, Multi-State Value) to any BACnet client. Configured via IntesisBox MAPS software (free, Windows) — signal table maps BACnet objects to KNX group addresses with DPT and scaling. No ETS6 application program required; KNX individual address assigned from MAPS. DIN-rail, 24V DC auxiliary power. Supports up to 1,000 signal mappings.
INMBSKNX Mitsubishi VRF to KNX gateway (32 indoor units)
Connects Mitsubishi Heavy Industries VRF systems (M-NET RS-485 protocol) to KNX TP. Controls up to 32 indoor units — each unit mapped to KNX DPT objects: on/off (DPT 1.001), mode heating/cooling/fan/auto (DPT 20.105), setpoint (DPT 9.001), fan speed (DPT 5.001), vane direction. Configured in IntesisBox MAPS; no CODESYS programming. DIN-rail, 24V DC auxiliary power. RS-485 cable to M-NET service bus on outdoor unit controller.
INDKN001R000 Daikin VRF to KNX gateway (D-III Net)
Connects Daikin VRF systems (D-III Net proprietary protocol) to KNX TP. Supports Daikin Intelligent Touch Controller override status. Each indoor unit maps to KNX objects for on/off, mode, setpoint, and fan speed. Configured via IntesisBox MAPS software. Eliminates custom Home Assistant or CODESYS Daikin drivers — provides a certified, manufacturer-supported KNX integration path for Daikin VRF installations.
IN70xKNX Modbus RTU/TCP to KNX gateway (1,000 signals)
Bidirectional translation between Modbus registers and KNX group addresses. Modbus register address (holding 4xxxx, input 3xxxx, coil 0xxxx) mapped to KNX group address with DPT and scaling in MAPS. Poll interval configurable per signal (1s-3600s). Used for energy meter integration: Carlo Gavazzi EM340 Modbus RTU → KNX DPT 9.001 active power and DPT 12.001 energy counter. Alternative to WAGO 750-893 CODESYS for projects without PLC programming expertise.
INSAMKNX Samsung NASA VRF to KNX gateway
Translates Samsung NASA (Network Air conditioning System Architecture) — Samsung's proprietary VRF RS-485 protocol — to KNX TP. Controls Samsung VRF indoor units from KNX room controller keypads and touch panels. Each indoor unit mapped to KNX objects for on/off, mode, setpoint, fan speed. Configured via IntesisBox MAPS. DIN-rail, 24V DC auxiliary power. Used in retail, hotel, and commercial office projects with Samsung VRF and KNX room automation.
Intesis (HMS Networks) — FAQ
Does Intesis IN701KNX require ETS6 to configure KNX group addresses?
No. The IN701KNX does not have an ETS6 application program — it is not programmed in ETS6 in the traditional sense. The KNX individual address is assigned from ETS6 (standard ETS6 'Write Individual Address' function, 1 minute), but all group address mapping is done in IntesisBox MAPS software via a signal configuration table. ETS6 does not need to know about the individual group addresses that IN701KNX reads or writes — those are purely within the MAPS configuration. The gateway appears in the KNX topology only as a device with an individual address; its group address usage is opaque to ETS6. For projects where the KNX engineer needs full visibility of all group addresses in ETS6, document the IN701KNX signal table in the project appendix separately.
Can one Intesis gateway replace a KNX IP router?
No. An Intesis KNX gateway (IN701KNX, Modbus gateway, etc.) is a KNX device that sits on a KNX TP line and communicates on that line. It does NOT replace a KNX IP router, which bridges KNXnet/IP (LAN) to KNX TP bus for programming and multi-line routing. You need both: a KNX IP Router (e.g., Weinzierl 770, MDT KNX IP Router) for ETS6 programming access, KNXnet/IP routing, and device downloads; and an Intesis gateway on the same KNX TP line for protocol translation. The IN701KNX has its own Ethernet port (for MAPS configuration and BACnet/IP server) — this is separate from the KNX TP bus connection, and separate from the KNX IP Router's Ethernet connection.
Which Intesis gateway should I use for Mitsubishi Electric City Multi VRF integration with KNX?
For Mitsubishi Electric City Multi (M-Series VRF): use the INMBSKNX000100 (M-NET to KNX, controls 1-32 indoor units). M-NET is Mitsubishi's proprietary RS-485 service bus running at 9600 baud on a daisy-chained 2-wire cable from the outdoor unit controller. The INMBSKNX connects to M-NET via an RS-485 terminal and to KNX TP via bus terminal. Configuration in MAPS: assign each indoor unit (M-NET address 1-32) to a KNX address block — each unit gets 8-10 KNX objects (on/off, mode, setpoint, fan speed, operation status, filter alarm). Total: 32 units × 10 objects = 320 KNX group addresses. Note: for Mitsubishi Heavy Industries VRF (different product line), use INMHIKNX (MHI K-control protocol) — different gateway, same configuration approach.
Serve un quadro con componenti Intesis (HMS Networks)?
Selezioniamo, acquistiamo, assembliamo e certifichiamo. Prima consulenza gratuita.
Richiedi una consulenza →