rotorloop

Building & industrial control

Every machine, one loop.

Rotorloop connects to the control systems a building already has, whoever made them. The people who run it get one clear app to watch and safely adjust equipment, from a phone or a desk.

Try the live demo Book a walkthrough

The live demo is the full app on a simulated building. No sign-up.

  • ConnectsBACnet/IP, BACnet MS/TP and Modbus. Most building and plant equipment speaks one of them.
  • InstallsOne small Connector on a computer at the site. It only dials out.
  • ProtectsRead-only until you allow changes. Every change ends on its own.
  • Remembers90 days of history for every reading, charted in the app.
Try it: a simulated building · runs in your browserLive

6 rooms

  • Main Lobby · 69.6°
  • Office · 71.2°
  • 1st Floor South · 71.9°
  • Dining Room · 68.6°
  • Shul · 74.1°
  • Gym · 63.6°

Shul

RTU 17A · Cooling, stage 2

Pick a room, drag the ring or use the arrow keys, choose how long, then Set. Rooms here warm and cool much faster than real ones.Same colors, hold times and wording as the real app.
01 — The problem

Three systems, three logins, one person on call.

A typical building runs its rooftop units on one controller, its split systems on a VRF central controller and its boiler plant on a third. Each has its own web page behind its own IP address, password and layout. Changing one room for an event means remembering which screen, which login, and which unit serves that room.

Today illustration

http://10.20.0.14/login.htmNot secure
Rooftop unit controller
UserPassword
https://10.20.0.30:8443/Certificate error
Building supervisor
Username••••••••
http://10.20.1.7/index.cgiNot secure
VRF central controller
Login IDPassword

The addresses are made up. The pattern is common.

With Rotorloop one list

Your buildingOnline
  • ShulRTU 17A · Cooling, stage 2BACNET74.1°
  • OfficeIndoor unit 3-04 · Fan onlyVRF GATEWAY71.2°
  • Boiler 1Supply water 146° · Burner onMODBUSOK
  • GymRTU 11 · Heating, stage 2BACNET63.6°
  • Main power meter14.6 kW nowMODBUSOK

Every room and machine in one place, under the names your staff already use.

02 — What you can do

The everyday jobs, without the vendor screens.

See each screen in the product tour →

Rooms

See every room at a glance

Each room is shaded by how far it is from its target, with what its unit is doing right now.

4°+ belowon target4°+ above
Holds

Change it for a while

Set the gym to 66° for three hours. It goes back to its schedule by itself, even if the site's internet drops in between.

Held until 4:30 PM
Equipment

Every machine, not only rooms

Boilers, meters, pumps and fans, with readings, faults and offline devices flagged, plus the controls an admin has allowed.

OK 1 fault Offline
Access

The right people, the right buttons

Viewers look. Operators make changes within limits. Admins decide which points can change, how far, and for how long.

Activity

A record of every change

Who asked for what, when, and whether the equipment accepted it, including the changes that were refused and why.

Trends

See what happened overnight

A chart for every reading, from 6 hours to 30 days, with the target drawn in. Rotorloop keeps 90 days of history.

03 — How it connects

A small Connector on site. Nothing exposed to the internet.

The Rotorloop Connector runs on a computer already on the building network. It talks to your controllers in their own protocol and dials out to Rotorloop. You don't open any firewall ports, and no controller is put on the internet.

How Rotorloop connects On the building network, BACnet and Modbus controllers talk to the Rotorloop Connector. The Connector sends data outbound only, encrypted, through the site firewall to the Rotorloop cloud at app.rotorloop.com, which your team uses from a phone or desktop. ON SITE · BUILDING NETWORK BACnet/IP controllers UDP 47808 BACnet MS/TP controllers through a BACnet router Modbus TCP devices TCP 502 Modbus RTU devices through a Modbus gateway ON A SITE PC OR SERVER Rotorloop Connector Reads and writes equipment Enforces the safety rules Ends holds on time, even offline Read-only until you allow changes FIREWALL · NO INBOUND PORTS OUTBOUND ONLY ENCRYPTED · 443 Rotorloop app.rotorloop.com Access and roles Activity log Live updates Your team Phone Desktop Any browser How Rotorloop connects On the building network, BACnet and Modbus controllers talk to the Rotorloop Connector. The Connector sends data outbound only, encrypted, through the site firewall to the Rotorloop cloud, which your team uses from a phone or desktop. ON SITE · BUILDING NETWORK BACnet/IP UDP 47808 BACnet MS/TP via a router Modbus TCP TCP 502 Modbus RTU via a gateway Rotorloop Connector Reads and writes equipment Enforces the safety rules Ends holds on time, even offline Read-only until you allow changes FIREWALL · NO INBOUND PORTS OUTBOUND ONLY ENCRYPTED · 443 Rotorloop app.rotorloop.com · access, roles, activity Your team Phone, desktop, any browser
If the internet drops

The building keeps running on its own controls. Holds still end on time, because the timer lives on site.

Your controllers stay in charge

Rotorloop sits on top of your schedules and logic. When a hold ends, control goes straight back to them.

Install

One command on a Windows or Linux computer at the site. It starts with the computer and finds BACnet equipment by itself. Connector guide →

04 — Safety

Built to be trusted with real equipment.

A control app can damage equipment or make a building unsafe if it's careless. These rules are checked at the site, before anything reaches a controller, and an admin can't switch them off.

  1. Read-only until you say otherwiseNothing can be changed until an admin allows it, point by point.
  2. Limits on every pointOut-of-range values are refused before they're sent.
  3. Every change has an end timeHolds last 12 hours at most, then control goes back to the building.
  4. Never life-safety systemsFire, smoke and emergency points are never written.
  5. Only what can be handed backIf control can't be cleanly returned, the point stays read-only.
  6. Gentle on equipmentMinimum on and off times protect compressors and pumps from rapid cycling.

All safety rules, in detail →

05 — Systems

A few protocols. Dozens of brands.

Most building and plant equipment speaks BACnet or Modbus, directly or through the maker's own gateway. Rotorloop speaks both, so it all lands in the same list.

Native

BACnet/IP, BACnet MS/TP through a router, Modbus TCP, and Modbus RTU through a gateway.

Native

Building systems that share points over BACnet/IP: Niagara, Metasys, Desigo, Trane Tracer, Carrier i-Vu, Distech, Delta, KMC, Alerton, Automated Logic.

Through a gateway

VRF and split systems from Mitsubishi Electric, Daikin, LG, Samsung, Fujitsu and Toshiba. Also DALI, LonWorks and KNX.

The full list of systems and how each connects →

06 — Who it's for

Buildings with more than one control system.

And the people who end up as the go-between for all of them.

Schools & yeshivas

Calendars that never sit still

Events, late sessions and holidays on top of a fixed schedule.

 Houses of worship

Big rooms, used in bursts

Ready for the service, without anyone at the controller.

 Offices & multi-tenant

After-hours requests

A change for one floor, with a record of who asked.

 Light industrial

Plant equipment in one list

Boilers, compressors and meters, watched from anywhere.
07 — Take the controls

Try the whole app on a building of our own.

The live demo is the Rotorloop app itself, running on a simulated school with nine rooftop units, a boiler, a hot-water pump and a power meter. Drag a room's dial, look inside a rooftop unit while it cools or heats, and scroll back through a month of trends. It all runs in your browser, so nothing you do there touches real equipment.

Open the live demoTake the product tour

Running a building with more than one control system?

See Rotorloop with your own systems in mind.

Try the live demoBook a walkthrough