BACnet gateways

BAC2000-ARM-E

Converts field-controller and meter data into BACnet interfaces for point-list-based integration with building management systems. Provides 2 Ethernet ports, 512-point capacity. Acquisition covers more than 500 protocols; check the driver against each connected device.

Ethernet ports2

Acquisition protocol coverageAll acquisition protocols for serial and Ethernet connections

Forwarding protocolsBACnet/IP / OPC UA

Physical interfacesEthernet

Point capacity512

Built-in touchscreen—

HMI configuration—

USB Type-C power—

4G connectivity—

WiFi—

LoRaWAN—

Model notes · Supported acquisition protocols: more than 500 protocols.

Start using this model

Review the model documents, then prepare the files needed for connection and commissioning.

BAC2000-ARM-E

No related files are listed in this language. Contact technical support to confirm the documents you need.

General commissioning guide

Connection, point mapping, live-value checks and troubleshooting.

View general steps Confirm required files

Connection and configuration preparation

Review how devices connect, then prepare the field point list and supporting files.

01
Field devices
- Confirm the driver against the device brand, full model and communication documentation
02
Device-side acquisition
- All listed acquisition protocols for serial and Ethernet
03
BAC2000-ARM-E
- Ethernet × 2
04
System-side forwarding
- BACnet/IP
- OPC UA
05
Compatible system types
- BACnet building management system
- OPC system

Arrows show connection order. Check model wiring instructions and the project point list for terminals, port assignments and read/write directions.

Communication roles

Acquisition side: Not specified in the records; verify against the field device and supervisory system
Forwarding side: Not specified in the records; verify against the field device and supervisory system

Recorded capacity

512 points

Check before connecting

Check the device brand, model, driver version and interface. Use the wiring diagram to confirm terminals and port assignments.
Prepare a point list with addresses or objects, data types, byte order, units and read/write permissions.
Confirm the role at each end and the device address, serial settings, or IP address and port.
Check point count, device count and physical port count separately, then confirm capacity for the actual data volume.

Files for configuration

Model documentsNo dedicated file listed
Request
User manualNo dedicated file listed
Request
Wiring diagramNo dedicated file listed
Request
Configuration tools and supporting filesNo dedicated file listed
Request

Statuses reflect files associated in the current language. Contact technical support with this model to confirm other supporting resources.

How to choose within a series

Match device-side protocols and the host system first, then check ports, wireless connections and capacity. Candidates below use confirmed model specifications.

Current model groupBAC2000

You need multiple serial and Ethernet protocols

Check models confirmed to cover all acquisition protocols for serial and Ethernet connections. Check protocol scope and physical port counts separately. Confirm dedicated CAN, KNX TP and 2-wire MBus connections for the specific model.

Confirmed candidates1 models

BAC2000-ARM-E
All serial and Ethernet acquisition protocols
Forwarding: BACnet/IP / OPC UA

View full group specifications

The device protocol is fixed

Check each model’s listed acquisition protocols and the required host-system protocol. A model suffix alone does not establish equivalent acquisition capability.

Confirmed candidates1 models

BAC2000-Lite-E
Listed acquisition protocols: Modbus TCP
Forwarding: BACnet/IP / OPC UA

View full group specifications

This guidance narrows the candidates. Confirm communication roles, read/write direction, the point list, wiring and model-specific resources before final selection.

“Unconfirmed” means documentation does not establish a value; it does not mean zero or unsupported.

Overview & technical information Selection checklist FAQ (1)Related content

Product overview

Key functions

COV and cross-subnet access

Supports COV subscriptions and BBMD cross-subnet access for change notifications and BACnet network integration.

BACnet alarms and events

Provides BACnet alarm and event functions for monitoring objects configured from the field point list.

Scripts and triggers

Use JS scripts and triggers for required control logic alongside the configured communication points.

Point-list configuration

Configure acquisition and forwarding mappings from the field point list, then upload the project for supervisory-system access.

Connections and integration

System-side interfaces: BACnet/IP, OPC UA. Configure the documented acquisition protocols so supervisory systems can access field data through these interfaces.

Typical applications

Lighting-device connectivity and management; Field-meter data integration.

Model selection essentials

Model configuration: 2 Ethernet ports, 512 points.

Current product specifications

Specifications are sourced from the supplied 2026 product catalog. Unspecified values remain unconfirmed.

Parameter	Specification
Ethernet ports	2
Point capacity	512
Forwarding protocols	OPC UA / BACnet/IP
Physical interfaces	Ethernet

Model notes: Supported acquisition protocols: more than 500 protocols.

Model datasheets

File unavailable in this language

Selection checklist

Why this matches

Acquisition protocolsModbus RTU_TCP

Confirm before selecting

Protocol compatibility is the first step. Check the device model, communication roles, point count and wiring. Capabilities that are not documented require confirmation.

Not yet documented：Acquisition roles / Output roles / Device capacity / Serial ports / RS485 ports / RS232 ports / CAN ports / KNX TP ports / Two-wire MBus ports / DI digital inputs / DO digital outputs / AI analog inputs / AO analog outputs / USB Type-C power / 4G connectivity / WiFi / LoRaWAN / HMI configuration / Built-in touchscreen / Product type

View parameter evidence

Acquisition protocols · Modbus RTU_TCPModel rule confirmation (2026-10-02) · 2026-10-02

Continue filtering and comparing

Related FAQs

Find configuration and usage guidance linked to this content. Refer to documentation for the exact model and version.

What does X mean, and how do acquisition and forwarding protocols differ?

X denotes the acquisition-side protocols. Also check forwarding protocols, communication roles, physical interface types and port counts.

Read the full answer

BAC2000-ARM-E

Start using this model

General commissioning guide

Field devices

Device-side acquisition

BAC2000-ARM-E

System-side forwarding

Compatible system types

Communication roles

Recorded capacity

Check before connecting

Files for configuration

How to choose within a series

You need multiple serial and Ethernet protocols

The device protocol is fixed

Product overview

Key functions

COV and cross-subnet access

BACnet alarms and events

Scripts and triggers

Point-list configuration

Connections and integration

Typical applications

Model selection essentials

Current product specifications

Model datasheets

Selection checklist

Related FAQs

Related content

BAC2004-ARM-E

BAC1002-MBus

BAC2004-Lite

Your next connection starts here.