NETx Multi Protocol Server

The NETx Multi Protocol Server uses the same server core as the NETx BMS Platform. The configuration and management of the various interfaces and the logic engine is the same as with the NETx BMS Platform.

  • Interfaces to various protocols and technologies (KNX, BACnet, Modbus, OPC and many more
  • Application-specific interfaces to hotel management (Fidelio/Opera, Protel, Infor, charPMS, WINHMS) and to control door access systems (VingCard, Kaba, Salto)
  • Logic engine for further control functions (LUA scripts/graphic function block programming)
  • OPC DA/UA server and BACnet/IP server
  • oBIX and MQTT

Functions

Multi-protocol gateway
  • Data and information are exchanged bidirectionally between different protocols and technologies
  • Automatic conversion rules come into effect for different data types
  • The integrated logic engine can also be converted manually.
Logic Engine

LUA Script based scripting engine

  • Contains a graphic tool for programming function blocks (xLogic Editor)
  • More control functionality within the field devices or required control functions that are distributed across devices with different technologies
  • Logic engine can read and write data points, perform mathematical operations and calculations, send notifications such as e-mails or messages via social media and much more.
  • Complex control functions such as PID control or drivers for communication protocols can be implemented
  • Ready-to-use logic functions are already included
  • Creation of virtual data points for user-specific virtual structures - these data points are only available in the server and can be used like physical data points.

Interfaces

KNX
  • Easy import from the ETS with the NETx BMS App Secure
  • Import of all group addresses and automatic assignment to KNXnet/IP routers and interfaces
  • Detection of IP addresses of KNXnet/IP routers and interfaces
  • Import of all ETS views (building and structure view, topology including devices, communication objects and their data points)
  • Support of the KNX IP security standard
  • Support of all standardized KNX data points
  • Non-standardized DPTs can be added
  • Uses KNXnet/IP tunneling protocol: any KNXnet/IP router and/or interface can be used
  • KNXnet/IP routing available
OPC

Management level

  • OPC interface for OPC clients from third-party manufacturers, e.g. visualizations from third-party providers

Field/automation level

  • OPC DA interface for the integration of data points from third party OPC servers, e.g. fire alarm systems
  • Cluster Explorer for easy import
  • Central aggregation of data from various sub-servers in the NETx BMS Platform
BACnet

Management level

  • BACnet/IP server interface for BACnet clients from third-party manufacturers
  • Assignment of different data points (e.g. KNX, Modbus, SNMP, Fidelio/Opera, VingCard, ...) to BACnet objects
  • Supports COV subscription
  • Automatic or manual selection of object types
  • Configuration of read/write or read-only access possible

Field/automation level

  • Uses the BACnet/IP protocol to integrate any BACnet/IP device
  • Other BACnet media (e.g. BACnet MS/TP devices) can be integrated via BACnet/IP routers
  • BACnet Explorer for the automatic detection of devices and objects without the functions required for external tools
  • Several BACnet priorities can be used at the same time
  • Supports confirmed/unconfirmed COV subscription, unsolicited COV notification and device query
  • Supports BBMD
  • Supports proprietary BACnet objects
  • Further information can be found under BACnet PIC Statement
Modbus
  • Supports Modbus/TCP protocol for the integration of Modbus/TCP devices
  • Supports Modbus/RTU via Modbus/TCP gateways or via IP-to-RS485 converter (native Modbus/RTU via TCP or UDP)
  • Manufacturer-specific configuration possible
SNMP
  • Support for SNMP v1, v2 and v3
  • Query of SNMP objects via their OIDs
  • Writing of SNMP objects
  • Supports SNMP traps
  • SNMP device monitoring
oBIX and other web service interfaces for IoT
  • oBIX 1.1 interface supports HTTP binding and XML coding
  • Supports HTTPS (TLS 1.2) and HTTP basic authentication
  • Support for oBIX clocks
  • Corresponds to the KNX Web Services, which offer the possibility of using the NETx BMS Platform as a standard-compliant KNX Web Service Gateway
MQTT
  • MQTT interface for communication with one or more MQTT brokers
  • Support of TLS security
  • Publish/Subscribe to MQTT Topics
Hotel management systems

Fidelio/Opera

  • Certified interface with the following functions: guest in/out/guest data updates when changing rooms, guest messages can be edited online / on request, room equipment / cleaning status / do not disturb
  • Combination of data from different systems possible, e.g. B. Hotel management and door lock systems
  • For Opera PMS V5 or higher, Fidelio Suite 8.8 or higher, Fidelio FO 6.20, Fidelio Suite 7.13

Infor

  • Infor Hospitality Management Solution (HMS ™) - cloud-based hotel management system

Protel

  • Protel interface for the NETx BMS Platform
Communication with door locking systems

VingCard

  • Events that can be retrieved from the VisiOnline server software: guest entrance (including card number), staff entrance, open inside, bolt thrown, bolt released. All events are available as data points in the NETx BMS Platform and can be further processed with other technologies such as KNX, BACnet, Modbus, SNMP, Fidelio/Opera, ...

Kaba door locks

  • Information is exchanged with the NETx BMS Platform via the Kaba software (Web Service Client) using Web Service Requests.

Salto door locks

  • The Salto software (TCP client) sends TCP/IP packets to the NETx BMS Platform (TCP server).
HTTP servers and other web service gateways
  • For the integration of web content from HTTP servers. The NETx BMS Platform acts as an HTTP client.
Additional interfaces
  • Via hardware gateways: DALI, DMX, EnOcean, M-Bus
  • Own interfaces via LUA scripting and C# .NET API
  • Customer-specific interfaces on request

Components

MP Server and Studio
  • Server: main component - communicates with the devices, stores or processes data point values and provides building management functions
  • Studio: user interface for configuring and managing the data points
Logic Editor

This Windows-based software is used to create logics for the core server with graphical programming.

System requirements
  • Can be installed and executed on any device with a Windows system (from Windows embedded boxes to large Windows server systems, VMWARE, VirtualBox, Hyper-V, ...) or cloud-based environment (Microsoft Azure, ...) must be installed.
  • Hardware requirements depend on: number of data points and the implemented building management functions (visualization clients, number of defined alarms, logic definitions, ...)
  • Minimum requirement: 1.8 GHz Quad-Core, 8GB RAM, 64 GB hard disk space, Windows 10 or Windows Server 2016 (or higher)