Search these docs, or ask Revo a question — answers link the pages they came from.
Werma 816 Beacon
The Werma 816 Beacon is a single-head RGB LED status beacon, Werma part 816.480.53 — not a tiered tower like the Werma 640. Revolution drives it over USB from the host so a schedule’s state is visible from across the room, not only on a screen.
At a glance
Section titled “At a glance”| Type | RGB LED beacon head (816.480.53) |
| Revolution control | Schedule state maps to a fixed colour; the driver sets the beacon to match |
| Configuration | COM port only — the colour mapping is not configurable |
Specifications
Section titled “Specifications”Werma’s datasheet for the USB variant (816.480.53) states:
| Diameter | 75 mm |
| Height | 97 mm |
| Protection category | IP65 |
| Working temperature | −20 °C to +50 °C |
| Power | 5 V DC via USB — no separate power supply |
The beacon head is an RGB LED unit capable of a wide range of colours; Revolution drives it with three fixed colours only (below), not the full range the LED supports.
How Revolution uses it
Section titled “How Revolution uses it”The beacon is a status indicator, not a scheduled instrument: there is no operation to call from a method. Unlike the Werma 640’s tier mapping, the colour for each state is fixed in the driver and not configurable:
| State | Colour |
|---|---|
| Running | Green |
| Paused | White |
| Error | Red |
| Idle (no state active) | Off |
When more than one state is active at once, Error takes precedence over Paused, which takes precedence over Running. The driver also re-sends the current colour every half-second as a keep-alive, so the beacon recovers its state after a brief power interruption without Revolution having to notice and resend it.
Integration
Section titled “Integration”Revolution talks to the 816 over USB, presented to the host as a serial port.
Prerequisites
Section titled “Prerequisites”- The beacon must be connected and its COM port known before the device is initialised.
If you need more of this instrument driven from a schedule — for example, a configurable colour mapping — get in touch; the driver is extended on demand.
Operations
These are available from a Run Device Operation step.
Raise Error
Makes this device report a failure on demand: the step fails with an error naming the device, and the operator is offered the usual error recovery choices. No command reaches the instrument and nothing moves, and the failure is raised in simulation as well as on a real system, so this is the step to use when rehearsing how a schedule handles a device failure.
Test Beacon Operation
Test the beacon by cycling its lamp states