Safety
Rules that can't be skipped.
These rules run at the site, inside the Rotorloop Connector, before any change reaches a controller. The app can't bypass them, and neither can we.
- Read-only by defaultRotorloop reads everything but changes nothing until an admin allows it for a specific point.
- Safe limitsEach adjustable point has a lowest and highest allowed value. Anything outside is refused.
- Every hold endsEach change has an end time. Control returns to the building's own schedule automatically, even after a restart or an internet outage.
- Never life-safetyFire alarm, smoke control and emergency points are never written. This can't be turned on.
- Equipment protectionA minimum wait between changes, and minimum on/off times so compressors and motors aren't cycled rapidly.
- Polite priorityOn BACnet, Rotorloop writes at an operator priority and never at the priorities reserved for life safety. Releasing a hold hands control straight back.
- Outbound-only connectionNo inbound firewall ports, and controllers are never exposed to the internet. Each Connector's credential can be revoked instantly.
- RolesViewers look, operators adjust within limits, admins decide limits. Only owners can grant admin rights.
- Every change recordedWho asked for what, from where, and whether the equipment accepted it — including changes that were refused.
- Each organization isolatedYour sites, people and history are visible only to your organization.
Your responsibility
Rotorloop works alongside your controls contractor
Rotorloop doesn't change the programming or sequences in your controllers. It reads values and adjusts targets you've allowed. Connect it with the building owner's permission, and ideally with your controls contractor involved. Start read-only.