Metasys N2 - Knowledge Base

Overview of Johnson Controls Metasys N2 protocol for building automation — variants, point counts, device addressing, and common integration pitfalls.

Categories:

What Metasys N2 Is

Metasys N2 is a proprietary serial protocol developed by Johnson Controls for building automation controllers. It is commonly encountered when integrating legacy Johnson Controls equipment into modern BACnet or Modbus supervisory systems via a protocol gateway. N2 communicates over RS-485 at 9600 baud (default).

Core Concepts

ConceptDescription
N2 BusRS-485 serial bus connecting controllers to a supervisory device
Device AddressSequential node address on the N2 bus (typically 11–18 for VAVs)
Point CountNumber of data points per device — varies by device type
AV MappingN2 data maps to BACnet Analog Value (AV) objects; binary N2 data does not map cleanly to BACnet Binary types
VMA Node_TypeRequired field for N2Open configurations — identifies the device profile

Protocol Variants

VariantUse CaseKey Difference
Standard N2Straightforward serial integrationSimple addressing and point mapping
N2OpenExtended controllers with VMA profilesRequires VMA Node_Type field in configuration
Facility ExplorerJohnson Controls FX seriesDifferent configuration requirements than Standard N2 or N2Open

[!WARNING] The #1 recurring support issue is N2 variant misidentification. Standard N2, N2Open, and Facility Explorer each require different gateway configurations. A single intake question prevents a full configuration rework.

Common Device Point Counts

Device TypeTypical PointsNotes
VAV Type A77Largest point count per unit
VAV Type B56Mid-range
VAV Type C38Smallest

[!NOTE] Mixed VAV installations require one configuration per device type, not a single consolidated config. Calculate total point counts across all device types to validate the gateway’s point count tier (250 / 500 / 1000) before deployment.

Integration Prerequisites

  1. Confirm the N2 variant — Standard N2, N2Open, or Facility Explorer.
  2. Collect all bus addresses before configuration starts.
  3. Identify device types and point counts for each address.
  4. VMA Node_Type (if N2Open) — required for correct driver mapping.
  5. Validate point count tier — total points across all devices must fit within the gateway tier.

Common Problems

  • Variant misidentification — assuming Standard N2 when the site uses N2Open or Facility Explorer requires a complete configuration rebuild.
  • Point count tier exceeded — a 500-point tier is insufficient for 8+ device installations (e.g., 522 total points). Validate at time of sale.
  • Mixed VAV types treated as one config — each device type (77/56/38 points) needs a separate configuration section.
  • N2 timeout errors during commissioning — typically caused by wiring, termination, or addressing issues, not configuration errors.
  • Post-deployment scaling errors — data accuracy issues after long gaps between configuration and commissioning.

Tools & Diagnostics

ToolTypeDescription
System Configuration Tool (SCT)ConfigurationJohnson Controls’ proprietary tool for configuring Metasys N2 controllers and programming VMA devices.
Metasys LauncherManagementCentral management UI for Metasys BMS systems — device browsing, point inspection, and scheduling.

Need more help?

If this page does not resolve the issue, contact Chipkin support with the product model, protocol details, and any diagnostics you have already captured.

Open Chipkin Support