Remote control · Commercial PV
Energy Integration Engineering supports the technical integration of remote control and communication interfaces in commercial PV projects — from the link to the grid operator and direct marketer through to how the setpoints are executed at plant level.
Typical starting point: the remote-control link is in place, but setpoints don't arrive, are processed incorrectly, or the test run with the grid operator fails.
Context
As soon as a generation plant needs to be controllable from the outside, an interface to third parties is created. The grid operator sets requirements for active power and, in some cases, reactive power; the direct marketer needs data and controllability. Both run over the same technical chain: network link, remote terminal unit (RTU) or gateway, plant controller, inverters.
The remote-control layer itself only transports and translates. The actual reconciliation of setpoints with the measured values at the grid connection point is handled by the EZA controller (plant controller). Both layers are tightly coupled: a cleanly received signal is worthless if its unit, scaling or sign is interpreted differently by the controller.
Below that sits the physical communication layer — router, VPN, gateway, bus and network paths. If this layer is unstable, it shows up externally as an apparent control problem. How to isolate such faults is described on the page about troubleshooting plant communication.
System architecture
Active and reactive power requirements, dispatch calls, schedules, fault notifications and feedback.
Remote terminal unit, protocol converter, router, VPN tunnel and processing of the external signals.
Processing of setpoints, reconciliation with the measured values at the grid connection point, distribution to the generation units.
Execution of the setpoints, response speed, limits and feedback of the actual state.
The plant's actual behavior, measured exactly where the grid operator evaluates it.
Meters, transducers, transmitters — the basis for every control loop and every feedback signal.
Operating data, alarming and traceability of what actually happened.
Actual values and status information sent back to the grid operator and direct marketer.
Router, cellular, fixed link, VPN — the path over which the signals travel in the first place.
The chain only works in both directions: setpoints must arrive and be executed, and actual values must be reported back correctly. A fault in either direction often only surfaces during the test run with the grid operator.
Grid connection
An external setpoint is only correct once it is measurably effective at the grid connection point.
Fault patterns
In practice these fault patterns rarely occur in isolation. A configuration error and an unstable connection often overlap, so the symptom appears sporadic and every party points to a different trade. Energy Integration Engineering isolates the cause across the full chain, independent of manufacturer — from the network link through to execution at the inverter.
The plant does not respond to external commands. The fault can sit in the gateway, the data-point mapping, the controller processing, or the network link. Only once the signal path from the external input to the inverter has been traced can the cause be clearly assigned to a specific layer.
External setpoints are sent but never reach the plant. The VPN connection, router, firewall rules, addressing, or gateway configuration can be responsible. The root cause is usually at the network access layer, yet it presents externally as a control problem.
Signals arrive but are not correctly executed by the controller. Data-point mapping, scaling, units and sign are involved. The fault sits at the interface between remote control and plant control — see also EZA controller.
The gateway cannot be reached from outside. Causes lie in IP configuration, routing, cellular connectivity, or the firewall. Often the plant runs flawlessly locally, and the fault only shows up via remote access.
The connection drops sporadically. Poor cellular signal quality, router reboots, VPN tunnel timeouts, or an overloaded link can be responsible. Unstable remote links look externally like faulty control or missing setpoints.
The link to the direct marketer is established, but data-point lists or control signals are incomplete or unreliable. The gateway, data points and controller-side execution are involved. Without end-to-end alignment, the interface stays unreliable.
The test run with the grid operator ends without a clear cause. Multiple layers can be involved: connectivity, signal processing, controller behavior and feedback of actual values. A cross-device analysis replaces swapping components on suspicion.
The first step is a short description of the plant, the systems involved and the current fault pattern. Based on that, you get a factual initial assessment of where the cause most likely lies and how it can be isolated.
Discuss a technical issueCommissioning
Network paths, addressing, ports, timeouts and stability across every device involved.
Trace every data point from the external interface through to the inverter.
Apply commands step by step and measure the execution at each intermediate stage.
Check and correct routers, subnets, routing, firewall rules and VPN setup.
Setpoint processing, limits, deadbands and defined behavior when the remote link fails.
Cross-check between metering, controller, monitoring and the values reported externally.
Technical clarification of data-point lists, test runs and feedback.
Coordination of all parties involved, including the on-site electrical contractor.
Plant certificates and formal conformity assessments are issued exclusively by accredited certification bodies. Energy Integration Engineering supports technical integration, commissioning and troubleshooting so that the plant demonstrably behaves as the project requirements demand.
Direct marketing
For the link to a direct marketer, what matters here is purely technical: a reliable data connection, an agreed data-point list, transmission of the measured values and — depending on the contract — the ability to influence feed-in via control signals.
In practice this means: configuring the gateway and network link, clearly mapping data points between marketer, controller and plant, verifying scaling and units, testing control signals through to the inverter, and defining fallback behavior if the connection drops.
Usually several parties are involved at once: the marketer, the grid operator, the manufacturers of the control and communication equipment, and the on-site electrical contractor. A key part of the work is to steer this coordination technically, rather than letting it bounce back and forth between the parties.
Independence
Energy Integration Engineering does not sell remote terminal units, controllers or monitoring products, and is not tied to any manufacturer. That is exactly the precondition for investigating a fault across system boundaries without ruling out a component in advance.
The focus is on methodology: fully trace the signal path, verify data points and scaling, follow setpoints through to execution, and clearly assign the cause to a specific layer.
Remote analysis
Via VPN or an existing remote access, gateway and controller configuration, router settings and network paths, data-point mappings, log and event data, received setpoints, measurement series and monitoring can all be evaluated. In many projects that's enough to identify the cause and either implement the fix directly or guide it precisely.
Physical work explicitly remains with qualified personnel on site: wiring, connection and transducer checks, electrical measurements and switching operations. Remote analysis prepares such site visits precisely rather than replacing them. The collaboration process is described on the homepage.
Who this is for
When the deadline for the remote-control tests is set and the link isn't running cleanly yet.
When a remote-control link with external commands is required for the first time.
When dispatch calls aren't being executed on an existing plant, or the connection fails sporadically.
When commands from the grid operator or direct marketer aren't arriving reliably.
When the plant hardware is in place but the signal processing doesn't come together.
When several parties are involved and an independent technical assessment is missing.
The first step is a short description of the plant, the systems involved and the current fault pattern. Based on that, you get a factual initial assessment of whether and how the problem can be isolated and solved.
Discuss a projectFAQ
More services at a glance: Services offered by Energy Integration Engineering.
