Contact monitoring and stop management
Understand site conditions. Manage stop requests remotely.
Monitor alarm signals from solar power equipment and manage stop requests, release of stop requests and scheduled operations through a web interface. The system supports on-site fault response and everyday work by the responsible operator.
The system is currently being validated on a test panel. Each installation requires a review of equipment signals and operating procedures, followed by on-site connection and operational checks.
Screen example: status and schedules at a glance
This simplified illustration highlights key elements of the actual screen layout. All equipment details, states and times are fictional; the example is not interactive. English labels are illustrative and do not indicate availability of an English product interface.
1Monitoring and control devices
Gateway: running
Controller: control activity confirmed
Last checked: 09:00 (example)
2Current status
Alarm inputs: normal
Stop request: held
A stop request may remain held even after input signals return to normal.
3Stop and release schedule
Illustrative day: schedule and history (Japan time)
Schedules execute only when the required conditions are met. Acceptance and execution results must be checked separately.
- Check device activity.Read the status and last-confirmed time. A green indicator does not mean the equipment is generating electricity.
- Separate inputs from stop requests.A stop request may remain held even when alarm inputs return to normal.
- Check both plans and results.Alongside scheduled times, review history for executed, held or unexecuted operations.
System overview: connecting the site and the operator
On-site devices handle alarm monitoring and contact control. The web interface provides access to status, remote operations and schedules.
At the site: monitoring, control and schedule execution
- Solar equipmentPCS, OVGR and related equipmentProvides alarm signals / receives stop requests
- On-site controllerPLC and stop-contact circuitDetects alarms / issues and holds stop requests
- Communication gatewayConnects the controller and serverStores schedules / sends timed commands
↕Communication gateway ↔ Server
Communication link: status, commands and results
Remote access: review, operations and notifications
- ServerManages status, schedules and historySends email notifications as configured
- Operator’s computer or smartphoneReviews status through the web interfaceOperations and schedules depend on permissions
During communication loss:local alarm monitoring and stop holding continue if the on-site controller and contact circuits remain operational. Stored schedules require the controller, gateway, their connection, correct time and other execution conditions. New remote operations and current status checks require communication with the server.
Core functions
Alarm monitoring and stop requests
Contact inputs monitor alarm signals from the ground overvoltage relay (OVGR) and power conditioning system (PCS, or solar inverter). The on-site controller issues a stop request when it detects an alarm. A return to normal input signals does not automatically release that request.
Remote operations and paired schedules
Authorized operators can request an immediate stop or release a stop request from a computer or smartphone. Stop and release times can be scheduled together, with the requester, reason and execution result recorded in the operation history.
Status, email notifications and history
View contact states, monitoring and control device status, and the last confirmation time. Depending on notification settings, emails and history records cover alarms, operation results, held or unexecuted schedules, and communication loss and recovery.
Operator confirmation before resuming after a fault
An alarm holds the stop request and places a scheduled release on hold. Normal input signals alone do not release the stop request or resume the schedule.
1. Review the situation
The responsible operator checks site conditions and the sequence of alarm and recovery events.
2. Resume before the scheduled time
The operator confirms recovery and resumes the schedule. This action alone does not release the stop request.
3. Release only when conditions are met
The stop request is released at the scheduled time only if the execution conditions are met. A new alarm or another event requiring confirmation places the schedule on hold again. If it remains on hold at the scheduled time, the stop request remains in place.
On-site control and communication
Local alarm response
Alarm monitoring and stop holding continue during a loss of server communication, provided the on-site controller and its input and stop-contact circuits remain operational.
Locally stored schedules
Previously stored schedules can execute without server communication when the controller, communication gateway, connection between them, correct time and other execution conditions are available. This does not mean the system operates without power. Expired operations are not automatically executed late after recovery.
Communication for remote access
New remote operations, new schedules and current status checks require communication. Stored result notifications may arrive late after communication is restored.
Equipment compatibility and monitoring scope
The intended applications primarily include central and older distributed PCS units operated with manual output-curtailment procedures. Contact specifications, polarity, wiring and operating conditions must be checked for each model. Equipment requiring a separate start contact after release of a stop request needs an individual assessment.
Contact states and command results are not measurements of actual generation or inverter operation. Validation to date covers contact behavior, schedules and notifications on a test panel. Operational verification with an actual PCS remains to be completed.
Current measurement, generation measurement and daytime low-generation alerts require separate assessment of measurement equipment, specifications and budget. They are not included in the contact-monitoring and stop-management functions described here.
Planning an installation
1. Tell us about your equipment and workflow
We review the PCS manufacturer and model, alarm signals to monitor, existing stop procedure, desired schedule and site connectivity.
2. Define connections and required functions
Together with the responsible electrical engineer, we review contact specifications, wiring, stop and release conditions, notification recipients and any additional measurement needs.
3. Verify on site and prepare for operation
Check the connection to the equipment, actual stop and release behavior, notifications and history, then establish operating procedures. Compatibility and costs are assessed for each installation.