20,919,685 Total Points 24,106 Total Sites 1,390 Datacenter Megawatts Monitored 23,382 Cell Towers 69,500 Racks Monitored 56,753 HVAC Units Monitored 31,322 UPS Units Monitored 24,788 Generators Monitored 1.39 Utility Gw Monitored 20,919,685 Total Points 24,106 Total Sites 1,390 Datacenter Megawatts Monitored 23,382 Cell Towers 69,500 Racks Monitored 56,753 HVAC Units Monitored 31,322 UPS Units Monitored 24,788 Generators Monitored 1.39 Utility Gw Monitored 20,919,685 Total Points 24,106 Total Sites 1,390 Datacenter Megawatts Monitored 23,382 Cell Towers 69,500 Racks Monitored 56,753 HVAC Units Monitored 31,322 UPS Units Monitored 24,788 Generators Monitored 1.39 Utility Gw Monitored

What Industrial Protocols Does an IoT Platform Need to Support?

An industrial IoT platform needs to support the specific communication protocols used by the devices already deployed in the operational environment it is connecting to — which in most real facilities means a combination of legacy serial protocols, modern Ethernet-based protocols, IT network protocols, and in some cases newer IoT messaging standards. The most commonly required protocols across industrial and commercial infrastructure include Modbus RTU, Modbus TCP, BACnet MS/TP, BACnet IP, DNP3, SNMP, OPC UA, and MQTT. Mango by Radix IoT supports 30+ data source types, including approximately 20 industrial and IoT communication protocols natively, covering the full range of devices found in data centers, energy operations, telecom infrastructure, healthcare facilities, and commercial real estate properties.

Why Protocol Support is the Most Important Technical Specification

When evaluating an industrial IoT platform, protocol support is the specification that most directly determines whether the platform can do its job in a real operational environment. Marketing materials routinely describe platforms as supporting ‘all major industrial protocols’ — a claim that is technically true if the platform supports three or four of the most common ones, but operationally meaningless for facilities that use the full breadth of industrial communication standards.

The consequences of selecting a platform with insufficient protocol support emerge during deployment, not during evaluation — when the power meters in a facility use a Modbus register map that the platform’s driver does not handle correctly, or the generator controllers use a proprietary protocol variant that requires custom development.

The Major Protocol Families in Industrial Environments

Modbus is the most widely deployed industrial protocol in the world — present in virtually every category of industrial and commercial equipment. BACnet was developed specifically for building automation and is the dominant protocol in HVAC and facility control applications. DNP3 is widely used in utility and energy applications. SNMP is the standard for network equipment monitoring. OPC UA is the modern successor to the original OPC standards. MQTT is a lightweight messaging protocol widely adopted in newer IoT device categories.

A monitoring platform that supports a few of the most common protocols can claim broad compatibility in marketing materials while leaving significant gaps in real operational environments.

Protocol Support Depth Versus Breadth

Having a driver for a protocol is necessary but not sufficient. What matters operationally is the depth of that support — how completely the driver implements the protocol specification, how well it handles the variations and edge cases introduced by different manufacturers’ implementations, and how reliably it performs at the polling rates and data volumes required in production deployments.

This depth of implementation is developed through production deployments over time. A platform that has been connecting to industrial devices in real operational environments for many years has encountered and resolved edge cases that a newer platform has not yet seen.

Radix IoT Angle

Mango by Radix IoT has developed and maintained protocol drivers across 30+ data source types, including approximately 20 industrial and IoT communication protocols over more than 15 years of production deployments. This protocol library reflects real operational experience — not just specification compliance — across the full range of device types and manufacturer implementations found in these environments. New protocol support is added as operationally significant standards emerge, and existing drivers are maintained and updated as device firmware and protocol implementations evolve.

Common questions

What is the difference between Modbus RTU and Modbus TCP?

Modbus RTU operates over serial communication interfaces — RS-232 or RS-485 — and is common in older equipment and devices designed for direct wiring. Modbus TCP operates over standard Ethernet networks using TCP/IP and is used in newer devices designed for networked environments. Many facilities have both variants present simultaneously.

Does an IoT monitoring platform need to support both BACnet IP and BACnet MS/TP?

In most real facility environments, yes. BACnet MS/TP operates over RS-485 serial networks and is common in field-level devices installed before Ethernet connectivity was standard. BACnet IP operates over standard Ethernet and is used in newer devices and BMS servers.

What protocols are most important for data center monitoring?

Data center monitoring typically requires Modbus TCP and RTU for power meters and environmental sensors, BACnet for building management and HVAC systems, SNMP for network equipment and UPS systems, and in some cases proprietary protocols for specific manufacturer equipment.

How does MQTT fit alongside traditional industrial protocols in an IoT platform?

MQTT is a publish-subscribe messaging protocol designed for lightweight communication in constrained or unreliable network environments. In most industrial deployments, MQTT coexists with traditional polling-based protocols like Modbus and BACnet rather than replacing them.

What should operations teams ask vendors about protocol support during a platform evaluation?

The most important questions are: which specific protocol variants are supported — RTU versus TCP, MS/TP versus IP; how are manufacturer-specific register maps and implementation variations handled; what is the process for adding support for a protocol or device type not currently in the driver library.

See how Mango by Radix IoT connects to the specific protocols and devices in your operational environment. Review our full compatibility list or talk to our team about the equipment in your facility.

Talk to Our Team Explore Mango

Related questions

What is the Difference Between a BMS and an IoT Platform for Commercial Buildings?

A BMS is a facility-specific control platform for a single building; an industrial IoT platform is a vendor-agnostic connectivity layer that spans buildings and sites.

How is Mango by Radix IoT Priced, and How Does Subscription-Based Pricing Work for Large Multi-Site Deployments?

Mango by Radix IoT is priced on a per-unit subscription basis — no upfront implementation fee, no hardware lock-in, with implementation and support included.

What Should Operations Leaders Look for When Evaluating an Industrial IoT Platform?

Operations leaders evaluating an industrial IoT platform should assess protocol coverage, multi-site scalability, alarm configurability, track record, and TCO.

We honored your browser’s Global Privacy Control signal — optional cookies are off and nothing is tracked.