What counts in service
- Faults with the tracker number instead of a collective message
- Clear responsibility: who is notified when
- Quiet during planned work without missing critical messages
- Remote commands only with permission and a record
What Feldmelder does here
- The portal reports deviations from the target angle, trackers that went offline, motor and drive-sync faults, wind sensor faults and unacknowledged commands.
- A fault at one tracker reaches the portal with the tracker number; the other rows keep following the sun.
- If nobody acknowledges an alarm, the portal escalates to the next contact; maintenance windows mute non-critical messages.
- Commands from the portal (safety position, automatic, maintenance) are signed and valid for two minutes only; the box rejects forged commands.
- Maintenance mode holds the rows where they are for the chosen duration – for work in the field, for example – and returns to automatic afterwards.
- REST API with tokens and scopes (read only or acknowledge alarms) and CSV export of the measurements.
- Portal and messages in German, English and Turkish.
A sequence in the field
Before working on a row you put the plant into maintenance mode and create a maintenance window. After the duration the controller returns to automatic; every command is logged with person and time.
Scope
- No work-order planning or spare-parts management in the portal.
- Other controllers are not connected; Feldmelder monitors plants with a Feldmelder box.
How we work: every function of the box, the tracker control unit (TCU) and the portal is covered by automated tests. Field installations start with a pilot project and acceptance criteria agreed beforehand. The live demo shows an example plant with example data.