ST Cloud Control to BACnet MS/TP or IP or Modbus RTU and TCP - 8 devices
Item number INSTCMBG0080000
Intesis ST Cloud Control is a bidirectional cloud-based solution to monitor and control any BACnet or Modbus device, whether from a web-based dashboard or an end-user-oriented app. The solution allows the integration of up to 8 devices, with up to 12 widgets per device. Widgets can be shared/split between the devices connected to the same gateway.
ST Cloud Control is a cloud-based system for remote control and monitoring of BACnet/Modbus devices.
The gateway supports both BACnet/IP and BACnet MS/TP protocols.
Both Modbus TCP and Modbus RTU can be supported simultaneously by the gateway.
The gateway's interface consists of easy-to-use, end-user-oriented, auto-generated web dashboards.
Another available control method is via a native app developed for both Android and iOS platforms.
Updating is really simple, as the delivery of updates is automatic.
Once the gateway is installed, it is configured using the PC-based Intesis MAPS configuration tool.
Configuration can be carried out through the gateway's IP (Console) port.
Take the complexity out of the integration process: Create your project with a predefined template, configure the needed parameters, enable the desired signals, and check the communication between the gateway and the system.
KNX to Modbus TCP & RTU - 250 points
Integrate any KNX device or installation with a Modbus BMS or any Modbus TCP or Modbus RTU controller. This integration aims to make KNX communication objects and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
KNX to Modbus TCP & RTU - 1200 points
Integrate any KNX device or installation with a Modbus BMS or any Modbus TCP or Modbus RTU controller. This integration aims to make KNX communication objects and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
BACnet/IP & MS/TP to Modbus TCP & RTU - 3000 points
Integrate any BACnet MS/TP or BACnet/IP server device with a Modbus BMS or any Modbus TCP or RTU controller. This integration aims to make BACnet objects, data, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
BACnet/IP & MS/TP to KNX - 600 points
Integrate any BACnet MS/TP or BACnet/IP server device with any KNX device or system. This integration aims to make BACnet objects data and resources accessible from a KNX system as if they were a part of the KNX system and vice versa.
Replaced by: IN701KNX1000000
Designed for the integration of any KNX device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aimed to make KNX communication objects and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa. Please refer to the new product reference for further details.
DALI to Modbus TCP - 1 DALI channel
Integrate any DALI/DALI-2 driver and DALI-2 light sensor or occupancy sensor with a Modbus BMS or any Modbus TCP controller. This integration aims to make DALI devices and their data and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and viceversa.
ST Cloud Control to BACnet MS/TP or IP or Modbus RTU and TCP - 8 devices
Intesis ST Cloud Control is a bidirectional cloud-based solution to monitor and control any BACnet or Modbus device, whether from a web-based dashboard or an end-user-oriented app. The solution allows the integration of up to 8 devices, with up to 12 widgets per device. Widgets can be shared/split between the devices connected to the same gateway.
Replaced by: IN7004851K20000
Designed for the integration of any Modbus RTU or TCP server device, or both simultaneously, with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make Modbus signals and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa. Please refer to the new product reference for further details.
BACnet/IP & MS/TP to Modbus TCP & RTU - 250 points
Integrate any BACnet MS/TP or BACnet/IP server device with a Modbus BMS or any Modbus TCP or RTU controller. This integration aims to make BACnet objects, data, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
M-BUS to Modbus TCP & RTU - 60 devices
Integrate any M-Bus device with a Modbus BMS or any Modbus TCP or Modbus RTU controller. This integration aims to make M-Bus devices, their registers, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
Replaced by: IN7004852500000
Designed for the integration of any Modbus RTU or TCP server device, or both simultaneously, with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make Modbus signals and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa. Please refer to the new product reference for further details.
LonWorks TP/FT-10 to BACnet/IP & MS/TP - 100 points
Integrate any LON device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make LON devices, their network variables (SNVT), and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
Modbus TCP & RTU to KNX - 3000 points
Integrate any Modbus RTU or TCP server device, or both simultaneously, with any KNX device or system. This integration aims to make Modbus register data and resources accessible from a KNX system as if they were a part of the KNX system and vice versa.
M-BUS to KNX - 120 devices
Integrate any M-Bus device with any KNX device or system. This integration aims to make M-Bus devices, their registers, and resources accessible from a KNX system as if they were a part of the KNX system and vice versa.
Replaced by: IN7004853K00000
Designed for the integration of any Modbus RTU or TCP server device, or both simultaneously, with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make Modbus signals and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa. Please refer to the new product reference for further details.
KNX to Modbus TCP & RTU - 3000 points
Integrate any KNX device or installation with a Modbus BMS or any Modbus TCP or Modbus RTU controller. This integration aims to make KNX communication objects and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
Modbus TCP & RTU to BACnet/IP & MS/TP - 100 points
Integrate any Modbus RTU or TCP server device, or both simultaneously, with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make Modbus signals and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
Replaced by: IN701KNX6000000
Designed for the integration of any KNX device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aimed to make KNX communication objects and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa. Please refer to the new product reference for further details.
LonWorks TP/FT-10 to BACnet/IP & MS/TP - 600 points
Integrate any LON device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make LON devices, their network variables (SNVT), and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
M-BUS to Modbus TCP & RTU - 20 devices
Integrate any M-Bus device with a Modbus BMS or any Modbus TCP or Modbus RTU controller. This integration aims to make M-Bus devices, their registers, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
Replaced by: IN701KNX1K20000
Designed for the integration of any KNX device or installation with a Modbus BMS or any Modbus TCP/RTU controller. This integration aimed to make KNX communication objects and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa. Please refer to the new product reference for further details.
KNX to BACnet/IP & MS/TP - 3000 points
Integrate any KNX device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make KNX communication objects and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
KNX to BACnet/IP & MS/TP - 1200 points
Integrate any KNX device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make KNX communication objects and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
Replaced by: IN703DAL0640000
Designed for the integration of any DALI/DALI-2 driver and sensors with a Modbus BMS or any Modbus TCP or Modbus RTU controller. This integration aimed to make DALI devices and their data and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system. Please refer to the new product reference for further details.
M-BUS to Modbus TCP - 50 devices
Integrate any M-Bus device with a Modbus TCP BMS or controller. This integration aims to make M-Bus devices, their registers, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
DALI to BACnet/IP- 2 DALI channels
Integrate any DALI/DALI-2 driver and DALI-2 light or occupancy sensor with a BACnet/IP BMS or controller. This integration aims to make DALI devices and their data and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
Replaced by: IN701KNX1000000
Designed for the integration of any KNX device or installation with a Modbus BMS or any Modbus TCP/RTU controller. This integration aimed to make KNX communication objects and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa. Please refer to the new product reference for further details.
LonWorks TP/FT-10 to BACnet/IP & MS/TP - 1200 points
Integrate any LON device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make LON devices, their network variables (SNVT), and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
EtherNet/IP to BACnet/IP & MS/TP - 1200 points
The Intesis BACnet-EtherNet/IP gateway allows you to seamlessly interconnect PLC/BMS systems and their connected devices between BACnet/IP and MS/TP control systems and EtherNet/IP networks. The gateway's BACnet side acts as a BACnet server and the EtherNet/IP side as an EtherNet/IP adapter and is configured via the Intesis MAPS configuration tool.
Replaced by: IN704DAL1280000
Designed for the integration of any DALI/DALI-2 driver and sensors with a Modbus BMS or any Modbus TCP controller. This integration aimed to make DALI devices and their data and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system. Please refer to the new product reference for further details.
OCPP to Modbus TCP & RTU - Up to 20 chargers
Configure this gateway as a Modbus RTU/TCP - OCPP protocol translator or move a step further with its OCPP Central System mode, which allows the gateway and the BMS to substitute the Central System of the OCPP installation and get all the potential of the Modbus-based BMS.
LonWorks TP/FT-10 to BACnet/IP & MS/TP - 3000 points
Integrate any LON device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make LON devices, their network variables (SNVT), and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
DALI to BACnet/IP or BACnet MS/TP - 1 DALI channel
Integrate any DALI/DALI-2 driver and DALI-2 input devices like light or occupancy sensors with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make DALI devices and their data and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
KNX to BACnet/IP & MS/TP - 600 points
Integrate any KNX device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make KNX communication objects and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
LonWorks TP/FT-10 to BACnet/IP & MS/TP - 250 points
Integrate any LON device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make LON devices, their network variables (SNVT), and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
BACnet/IP & MS/TP to ASCII IP & Serial - 1200 points
Integrate any BACnet MS/TP or BACnet/IP server device with an ASCII BMS or any ASCII IP or ASCII serial controller. This integration aims to make BACnet objects, data, and resources accessible from an ASCII-based control system or device as if they were a part of the ASCII system and vice versa.
Replaced by: IN7004853K00000
Designed for the integration of any BACnet MS/TP or BACnet/IP server device with an ASCII BMS or any ASCII IP or ASCII serial controller. This integration aimed to make BACnet objects, data, and resources accessible from an ASCII-based control system or device as if they were a part of the ASCII system and vice versa. Please refer to the new product reference for further details.
KNX to ASCII IP & ASCII Serial - 600 points
Integrate any KNX device or installation with an ASCII BMS or any ASCII IP or ASCII serial controller. This integration aims to make KNX communication objects and resources accessible from an ASCII-based control system or device as if they were a part of the ASCII system and vice versa.
BACnet/IP & MS/TP to Modbus TCP & RTU - 100 points
Integrate any BACnet MS/TP or BACnet/IP server device with a Modbus BMS or any Modbus TCP or RTU controller. This integration aims to make BACnet objects, data, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
BACnet/IP & MS/TP to KNX - 1200 points
Integrate any BACnet MS/TP or BACnet/IP server device with any KNX device or system. This integration aims to make BACnet objects data and resources accessible from a KNX system as if they were a part of the KNX system and vice versa.
KNX to BACnet/IP & MS/TP - 100 points
Integrate any KNX device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aims to make KNX communication objects and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
Replaced by: IN701KNX6000000
Designed for the integration of BACnet MS/TP or BACnet/IP server devices with any KNX device or system. This integration aimed to make BACnet objects data and resources accessible from a KNX system as if they were a part of the KNX system and vice versa. Please refer to the new product reference for further details.
KNX to ASCII IP & ASCII Serial - 250 points
Integrate any KNX device or installation with an ASCII BMS or any ASCII IP or ASCII serial controller. This integration aims to make KNX communication objects and resources accessible from an ASCII-based control system or device as if they were a part of the ASCII system and vice versa.
M-BUS to Modbus TCP & RTU - 120 devices
Integrate any M-Bus device with a Modbus BMS or any Modbus TCP or Modbus RTU controller. This integration aims to make M-Bus devices, their registers, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
M-BUS to Modbus TCP - 20 devices
Integrate any M-Bus device with a Modbus TCP BMS or controller. This integration aims to make M-Bus devices, their registers, and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa.
Replaced by: IN701KNX2500000
Designed for the integration of any KNX device or installation with a Modbus BMS or any Modbus TCP/RTU controller. This integration aimed to make KNX communication objects and resources accessible from a Modbus-based control system or device as if they were a part of the Modbus system and vice versa. Please refer to the new product reference for further details.
Replaced by: IN701KNX1000000
Designed for the integration of BACnet MS/TP or BACnet/IP server devices with any KNX device or system. This integration aimed to make BACnet objects data and resources accessible from a KNX system as if they were a part of the KNX system and vice versa. Please refer to the new product reference for further details.
KNX to ASCII IP & ASCII Serial - 1200 points
Integrate any KNX device or installation with an ASCII BMS or any ASCII IP or ASCII serial controller. This integration aims to make KNX communication objects and resources accessible from an ASCII-based control system or device as if they were a part of the ASCII system and vice versa.
M-BUS to BACnet/IP & MS/TP - 120 devices
Integrate any M-Bus device with a BACnet BMS or any BACnet IP or BACnet MS/TP controller. This integration aims to make M-Bus devices, their registers, and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa.
Replaced by: IN701KNX1K20000
Designed for the integration of any KNX device or installation with a BACnet BMS or any BACnet/IP or BACnet MS/TP controller. This integration aimed to make KNX communication objects and resources accessible from a BACnet-based control system or device as if they were a part of the BACnet system and vice versa. Please refer to the new product reference for further details.
Training from HMS Academy reduces the total cost and time of your project and gives improved quality and efficiency of the solution.
HMS offers trainings related to products, technologies and more. This could be in the form of an onsite training, online training or by running one of our E-learning sessions.
Technical Services from HMS helps customers with any type of assistance needed in addition to the products bought from HMS. The Technical Services page offers a list of all services we provide.
The services are provided by HMS’ global team of skilled and experienced engineers who work together with you, providing various services.
Typical activities are project planning, setting up evaluation demos, creating and validating product configurations, providing guidance during field trials, and more.
Technical Services from HMS helps customers with any type of assistance needed in addition to the products bought from HMS. The Technical Services page offers a list of all services we provide.
The services are provided by HMS’ global team of skilled and experienced engineers who work together with you, providing various services.
Typical activities are project planning, setting up evaluation demos, creating and validating product configurations, providing guidance during field trials, and more.
