BACnet routers

Router1001-ARM-E(Type-C)

Transparently routes between BACnet MS/TP buses and BACnet/IP networks, connecting MS/TP DDCs or valve controllers to building Ethernet. Provides 1 Ethernet port, 1 serial port. Acquisition covers all serial and Ethernet protocols in the reviewed list. Existing explicit support for BACnet MS/TP is retained. Type-C power is optional; confirm the option when ordering.

Serial ports1

Ethernet ports1

Acquisition protocol coverageAll acquisition protocols for serial and Ethernet connections

Acquisition protocolsBACnet MS/TP

Forwarding protocolsBACnet/IP

Physical interfacesEthernet / RS485 / RS232

Built-in touchscreen—

HMI configuration—

USB Type-C powerSupported

4G connectivity—

WiFi—

LoRaWAN—

(Optional Type-C power)

Serial port: 1 fully isolated RS485/RS232 port.

Start using this model

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

Router1001-ARM-E(Type-C)

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
- BACnet MS/TP
03
Router1001-ARM-E(Type-C)
- Ethernet × 1
04
System-side forwarding
- BACnet/IP
05
Compatible system types
- BACnet building management 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

Capacity to confirm

Serial port: 1 fully isolated RS485/RS232 port.

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 groupROUTER1001

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 candidates2 models

Router1001-ARM-E
All serial and Ethernet acquisition protocols
Forwarding: BACnet/IP
Router1001-ARM-E(Type-C)
All serial and Ethernet acquisition protocols
Forwarding: BACnet/IP

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

BACnet network routing

Supports transparent routing between BACnet MS/TP buses and BACnet/IP networks to interconnect their devices.

Field connection interfaces

Provides Ethernet, RS485, RS232 interfaces for the field-device wiring arrangement.

Connections and integration

Acquisition covers all serial and Ethernet protocols in the reviewed list. Existing explicit support for BACnet MS/TP is retained. System-side interfaces: BACnet/IP. Configure the device roles and point mappings for the installation.

Model selection essentials

Model configuration: 1 Ethernet port.
This model supports USB Type-C power.

Current product specifications

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

Parameter	Specification
Total serial ports	1
Ethernet ports	1
Acquisition protocols	All serial and Ethernet protocols in the reviewed list; existing explicit support for BACnet MS/TP is retained
Forwarding protocols	BACnet/IP
Physical interfaces	Ethernet / RS485 / RS232
Type-C power	Supported

The serial/Ethernet acquisition scope above follows the model confirmation on 2026-10-02. Existing explicit protocol support and specialized interfaces are retained; verify actual hardware interfaces and communication roles separately.

Interface notes: Serial port: 1 fully isolated RS485/RS232 port.

Capabilities and options: (Optional Type-C power)

Model datasheets

File unavailable in this language

Selection checklist

Why this matches

Acquisition protocolsModbus RTU_UDP

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 / Point capacity / Device capacity / 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 / 4G connectivity / WiFi / LoRaWAN / HMI configuration / Built-in touchscreen / Product type

View parameter evidence

Acquisition protocols · Modbus RTU_UDPModel 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

Router1001-ARM-E(Type-C)

Start using this model

General commissioning guide

Field devices

Device-side acquisition