SNE1050x Model - Metasys - LIT-12013352 - M4-SNE10500-0 - M4-SNE10501-0 - M4-SNE11000-0 - M4-SNE11001-0 - M4-SNE110L0-0 - M4-SNE110L1-0 - M4-SNE22000-0 - M4-SNE22001-0 - Supervisory Device - SNE10 Network Engine - SNE11 Network Engine - SNE22 Network Engine - SNE Supervisory Network Engine - 12.0

SNE Commissioning Guide
Product
Network Engines > Network Engines > SNE Supervisory Network Engine
Network Engines > Network Integration Engines > SNE22 Network Engine
Network Engines > Network Integration Engines > SNE10 Network Engine
Network Engines > Network Integration Engines > SNE11 Network Engine
Document type
Commissioning Guide
Document number
LIT-12013352
Version
12.0
Revision date
2022-12-12
Product status
Active

The SNE1050x models:

  • succeed the NAE35 Series of network engines. For details about how to migrate an NAE35 to an SNE1050x model, see NAE to SNE migration and Migrating NAE to SNE.

  • support one RS485 field bus and one LonWorks network into a Metasys system network. The field bus can be the legacy N2 Bus or a BACnet MS/TP trunk with up to 50 equipment controllers. The LonWorks network is integrated with the addition of a USB LonWorks adapter and supports up to 127 LonWorks devices.

  • support up to two vendor integrations, including Modbus, M-Bus, KNX, MQTT, OPC UA, Zettler MXSpeak, and C•CURE/victor

  • monitor and control up to 50 BACnet IP or BACnet/SC devices over Ethernet at the supervisory level

  • serve as a Site Director supervising a maximum of two additional network engines, which can be SNC or SNE1050x model engines only

  • support a Domain Name Server (DNS) for resolving SNE names on the building network, but does not support NETBIOS name resolution