Johnson Control M4-SNE10502-0 Supervisory Network Engine Instruction Manual

Johnson Control M4-SNE10502-0 Supervisory Network Engine

Product information

Specifications

• Product Name: Automation station SNE Supervisory Network Engine SNE
• Protocol: BACnet/SC
• Efficient management of facilities and energy consumption
• Multiple integration interfaces
• BTL certified with AMEV-B certification
• Property-wide management of notifications and events

Product Usage Instructions

Functionality

• The automation station SNE Supervisory Network Engine (SNE) is designed to efficiently manage facilities and energy consumption.
• It provides numerous integration interfaces, allowing seamless integration with various systems.

Models

The automation station SNE Supervisory Network Engine (SNE) is available in the following models:

• M4-SNE10502-0
• M4-SNE11002-0
• M4-SNE22002-0

Type

• The automation station SNE Supervisory Network Engine (SNE) is a versatile product that can be used in various applications, including building automation, energy management, and facility monitoring.

Description

• The automation station SNE Supervisory Network Engine (SNE) is a powerful device that enables efficient management of facilities and energy consumption.

• It is designed to provide comprehensive control and monitoring capabilities, ensuring optimal performance and energy efficiency.

FAQ

Q: What is the purpose of the automation station SNE Supervisory Network Engine (SNE)?

• A: The SNE is designed to efficiently manage facilities and energy consumption. It provides comprehensive control and monitoring capabilities.

Q: Is the SNE compatible with other systems?

• A: Yes, the SNE supports numerous integration interfaces, allowing seamless integration with various systems.

Q: What certifications does the SNE have?

• A: The SNE is BTL certified with AMEV-B certification, ensuring its compliance with industry standards.

Efficient management of systems and energy consumption

overview

• The SNE (Supervisory Network Engine) automation station equips the extended Metasys® building automation system with the latest technologies for IT security and energy efficiency.
• Communication and data transfer between operator stations, servers, and automation units in the building automation network takes place either via the globally standardized communication standard BACnet® or via web services. In addition to BACnet IP, the latest standard BACnet/SC is also supported.

Performance characteristics

• Listed and certified as BACnet® Building Controller (B-BC) according to DIN EN ISO 16484-5
• BTL certified with AMEV-B certificate
• Use of different fieldbus protocols such as BACnet MS/TP, BACnet/SC, BACnet/IP, Modbus RTU, LonWorks® or the Metasys® N2 bus, as well as the integration of remote field
• Support for IT and Internet standards such as HTTPS and Secure Boot to prevent malware from manipulating the boot process and circumventing security mechanisms when the SNE boots
• Property-wide management of messages and events
• Advanced integration options for fire alarm systems, lighting, and security systems

Numerous integration interfaces

• In addition to the BACnet/IP, BACnet/SC and BACnet MS/TP or Metasys® N2 bus, every SNE always also has direct integration interfaces for Modbus, KNX IP, OPC UA, MQTT, M-Bus, LonWorks® and the most important ones Tyco product brands, such as the victor® video management system, the Cure® access control system and the Zettler® and Simplex® fire alarm panels.
• In addition, integrations for the Cree® SmartCast® and Molex® lighting controls are always available in every SNE.
• The automation station is BTL-listed and has the AMEV-B certificate.

Features

• With this combination of different technologies, heating, ventilation, and air conditioning systems, lighting, and security systems throughout the property can be monitored, regulated, and controlled via the same automation station.
• This follows today’s requirements for smart buildings and the requirement for operational and energetic efficiency of real estate.
• Regardless of the integration into an overall system, direct interaction with an SNE automation station can take place using encrypted communication (HTTPS with TLS 1.2).
• The functions for monitoring, controlling, and optimizing building operations are immediately available. In addition, important building data can be monitored in the online trend.

Network Overview

functionality

• As a BACnet® station, the Metasys® Supervisory Network Engine SNE connects the most diverse field levels with room and field controllers or bus and BSK modules to the network of the management level. Up to 5000 objects at the fieldbus level can be processed.
• BACnet/IP, BACnet MS/TP, or BACnet/SC are used as hardware layers. The SNE automation station can be used as a BACnet® client and BACnet® server at the same time and supports functions such as data sharing, alarming (intrinsic alarming (object’s reporting)), scheduling, trending device management, and network management.
• For remote and local operation, a user interface with a web server is integrated into the SNE, which, in addition to the BACnet® protocol, supports the standard IT protocols, services, and formats of the Internet as well as dynamic IP assignment (DHCP/DNS). This means that all computers connected via a web browser can be provided with formatted overviews, data, and dynamic system graphics for configuration, operation, monitoring, and diagnosis.

Models

• Supports 1 local fieldbus (RS-485) Max. number of devices: 60.
• Examples: BACnet/IP integration: 50
• BACnet/SC integration: 50
• BACnet MS/TP integration: 50

M4-SNE11002-0|

• Supports 1 local fieldbus (RS-485) Max. number of devices: 150.
• Examples: BACnet/IP integration: 100
• BACnet/SC integration: 100
• BACnet MS/TP integration: 100

Mch-SNE22002-0|

• Supports 2 local fieldbuses (RS-485) Max. number of devices: 600.
• Examples: BACnet/IP integration: 200
• BACnet/SC integration: 150
• BACnet MS/TP integration: 100

The maximum permissible number of devices depends on the communication protocol (here BACnet® as an example) and is always calculated over everything, i.e. H. via Fieldbus, Ethernet, router, USB adapter, and all integrations.

• © 11.2023
• DB_K005_610_039
• Technical changes reserved.www.johnsoncontrols.de

References

• johnsoncontrols.de

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>