SNC series network control engines - Metasys - LIT-12013296 - M4-SNC16120-0 - M4-SNC16120-04 - M4-SNC16121-0 - M4-SNC16121-04 - M4-SNC25150-0 - M4-SNC25150-04 - M4-SNC25151-0 - M4-SNC25151-04 - M4-SNE10500-0 - M4-SNE10501-0 - M4-SNE10502-0 - M4-SNE11000-0 - M4-SNE11001-0 - M4-SNE11002-0 - M4-SNE110L0-0 - M4-SNE110L1-0 - M4-SNE22000-0 - M4-SNE22001-0 - M4-SNE22002-0 - Supervisory Device - 13.0

NAE85/M4-SNE/M4-SNC Product Bulletin
Document type
Product Bulletin
Document number
LIT-12013296
Version
13.0
Revision date
2024-08-26
Product status
Active

The following table contains a brief comparison of the features of the SNC models.

Note: The SNC is not an exact drop-in replacement for the NCE series network engines.
Note: Each device counts towards the overall limit of the SNC. For example, you cannot have 50 MS/TP devices and 50 BACnet/IP devices connected to an SNC25151-xx
Table 1. SNC series Network Control Engines details
Features SNC2515x-0

SNC2515x-0H

SNC25152-0G 1

SNC25152-0HG1

SNC2515x-04

SNC2515x-04H

 SNC1612x-0

SNC1612x-0H

SNC1612x-04

SNC1612x-04H

Succeeds NCE25 Series NCE25 Series NCE25 Series NCE25 Series
Onboard inputs and outputs
  • 40 total onboard I/O: 14 UI, 11 BI, 4 CO, 4 AO, 7 BO
  • Supports SA Bus expansion
  • 28 total onboard I/O: 10 UI, 6 BI, 4 CO, 4 AO, 4 BO
  • Supports SA Bus expansion
Communication interfaces
  • 1 Ethernet port: SNC25150-0, SNC25150-04, SNC16120-0, SNC16120-04, SNC25152-0, SNC25152-04, SNC25152-0H, SNC25152-04H, SNC16122-0, SNC16122-04, SNC16122-0H, and SNC16122-04H 2
  • 2 Ethernet ports: SNC25151-0, SNC25151-0H, SNC25151-04, SNC25151-04H, SNC16121-0, SNC16121-0H, SNC16121-04, SNC16121-04H
  • 1 RS-485 port
  • 2 USB ports for connecting external integration adapters 3
Maximum allowed devices across all integrations. For example, MS/TP+IP. Includes VND integrations and devices brought in through routers. 96 4 60 4
BACnet/IP maximum trunks 4 5 2 2 2 2
BACnet/IP maximum devices per trunk 50 4 50 4
BACnet/SC maximum trunks 5 1 1 1 1
BACnet/SC maximum devices per trunk 50 4 50 4
BACnet MS/TP maximum trunks 1 1 1 1
BACnet MS/TP maximum devices per trunk (Johnson Controls devices only) 50 4 50 4
BACnet MS/TP maximum devices per trunk (with 3rd party) 50 4 50 4
N2 maximum trunks 1 1 1 1
Mapped N2 devices per trunk 50 4 50 4
LON maximum devices per trunk 64 4 60 4
LON maximum trunks 1 1 1 1
Remote Field Bus maximum trunks 6 3 3 3 3
Remote Field Bus maximum Johnson Controls Devices per bus 32 4 32 4
Remote Field Bus maximum devices per bus (with 3rd party devices) 16 4 16 4
Maximum objects in device 7 2500 2500 2500 2500
Supported type of parent server
  • ADS
  • ADX
  • ADS-Lite
  • OAS
Supported integration drivers
  • BACnet/SC
  • BACnet/IP
    • Simplex® Fire Alarm Control Unit (FACU)
    • Cree® SmartCast® Lighting Control
    • Molex® Lighting Control
  • BACnet MS/TP
  • N2 Bus
  • LonWorks® with USB to LON adapter
  • Modbus: Modbus TCP/IP on Ethernet and Modbus Remote Terminal Unit on RS-485
  • KNX IP
  • M-Bus
  • Tyco® C•CURE® 9000 and victor® Video Management
  • Zettler® Fire Panel with USB to RS-232 adapter
  • OPC Unified Architecture (OPC UA)
  • MQ Telemetry Transport (MQTT)
Operating System Wind River® Linux LTS 19 (LTS=long-term support)
Microprocessor NXP i.MX6 DualLite processor
Memory 2 GB of DDR3 RAM and 16 GB of eMMC Flash
User Interface Metasys UI, starting at Release 13.0
1 The letter G in a model's product code indicates that the model is the Buy American version.
2 Second Ethernet port available with use of the ACC-USBETH-0 adapter.
3 Only the supported USB integration adapters function with the SNC. Other integration adapters that are not supported cannot function with the SNC.
4 Two Ethernet device connections include one integral Ethernet port and one external Ethernet port with the addition of ACC-USBETH-0 adapter. The second BACnet/ IP trunk is supported only at Release 13.0 and later.
5 Direct Ethernet connection only. USB to Ethernet adapter does not support BACnet/SC at this time.
6 The SNC requires Release 11.0 or higher to support the Remote Field Bus integration.
7 Suggested object limit for performance considerations.