A conventional four-pair copper Ethernet channel reaches only about 100 metres, and a solar or wind site spans kilometres, not a single cabinet. Use EMC-hardened copper, ETHERLINE® for Ethernet and UNITRONIC® for fieldbus, inside the inverter or nacelle cabinet, and switch to HITRONIC® fibre for the inverter-block-to-block or turbine-to-turbine link and the long backbone run back to the SCADA room. Fibre carries the distance, and because its optical transmission medium is not susceptible to conducted or radiated interference, it sidesteps the electrical-noise problem along the run.
This piece moves from the component, covered in the first two weeks of this series, to the network that ties every inverter, turbine and control room together across a site. It gives SCADA integrators and EPC contractors a way to think about a utility-scale solar plant or a wind farm in three tiers: the local run inside an inverter or nacelle cabinet, the inverter-block-to-block or turbine-to-turbine link, and the long backbone run back to the control room. ETHERLINE®, UNITRONIC® and HITRONIC® are the physical layer under the site's automation, not the automation itself.
This is written for SCADA and control system engineers, EPC contractors responsible for plant-wide communications installation, and O&M engineers troubleshooting comms dropouts across a solar plant or a wind farm, across Vietnam, Thailand, the Philippines and Indonesia. It applies at the plant network design stage, when copper-versus-fibre, node count and backbone distance are being specified alongside the power cable schedule, and again at the fault-diagnosis stage, when a remote node keeps dropping off SCADA.
Why does copper Ethernet run out of reach on a solar or wind site?
A conventional four-pair copper Ethernet channel is specified to about 100 metres, a limit a utility-scale solar plant or a wind farm crosses before the first cable run even leaves the inverter or nacelle cabinet. A solar site can carry dozens of identical inverter or combiner box nodes, and a wind site dozens of identical turbine nodes; keeping the specification consistent across every one of them is a different problem from specifying a single cabinet.
Communication cable on a renewable site is also routed alongside power cable more often than not, exposed to UV and rodent risk that indoor-rated cable rarely sees. And when a SCADA reading drops at a specific inverter or turbine, the fault could be the cable, the connector or the software layer, and testing each node to find out adds cost and downtime. LAPP already publishes on PROFINET cable selection and on choosing Cat-rated industrial Ethernet patch cords; both are protocol- and cable-selection guides for a single cabinet or machine, not for a network that spans kilometres.
The cost of a dropped node is not just the diagnosis. On a wind or solar site, confirming whether a fault is the cable, the connector or the software layer can mean a site visit to a turbine or an inverter block that sits well past the cabinet door. A network specified to reject the fault in the first place is cheaper than one diagnosed after the fact.
What protects a communication link from inverter and generator EMI?
Inside an inverter or nacelle cabinet, the short run sits close to the noise source: an inverter switching at high frequency, a generator, or a variable-frequency drive. EMC-hardened copper, ETHERLINE® for Ethernet and UNITRONIC® for fieldbus, does that run, built to reject the conducted and radiated interference a standard cable would pick up as dropped SCADA packets. Our EMC guide for plant teams covers the fundamentals this piece builds on.
A shielded cable that stops short of full shield continuity can reopen the EMI gap it was specified to close, and a shielded run is only as good as its weakest connection point. Our piece on shielded data cables for EMI hotspots on the plant floor works through the same continuity problem in a general industrial setting. On a solar or wind site the stakes are higher, because a dropped node sits further away and is harder to reach and diagnose.
The same continuity discipline applies whether the run is Ethernet or fieldbus. UNITRONIC® fieldbus cable inside the cabinet needs the same shield-to-connector continuity as ETHERLINE® Ethernet cable does. A mixed installation, some runs fieldbus, some Ethernet, on the same site should not treat one protocol's shielding as an afterthought because the other protocol is the primary focus that day.
This piece draws two clear boundaries. SCADA software configuration, PLC programming and RTU setup stay with the automation integrator; LAPP supplies the physical layer the automation runs on, not the automation itself. Protocol-level questions for a single cabinet are answered by the PROFINET selection guide and the patch cord guide linked above, not repeated here.
How do you build a fibre backbone between inverter blocks or turbines?
Between inverter blocks on a solar site, or between turbines on a wind site, and on the long haul back to the SCADA room, copper runs out of reach and HITRONIC® fibre carries the distance instead. Because the optical transmission medium is not susceptible to conducted or radiated EMI, it sidesteps the electrical-noise problem entirely along the backbone run, not only at the cabinet.
Because a solar plant or a wind farm rarely stops growing at its first phase, the backbone topology is worth specifying for the site's planned footprint, not only its current one. Adding an inverter block or a turbine string later should mean extending the fibre run, not re-specifying the backbone that already exists.
The backbone is where the site scales: one inverter block or one turbine failing to report should not risk the rest of the network, so the fibre topology and node count get specified against the site layout, not assumed from a smaller plant. For exact fibre counts, bend-radius ratings and connector types, the product specifications are the source of record, rather than a general claim here. This piece sits inside our broader renewable energy connectivity guide for solar, wind and storage, which walks through the same component-level choices from a different angle.
A fibre backbone specified this way also changes how a fault gets isolated. If a single inverter block or turbine drops off SCADA, the fault trace narrows to that segment rather than casting doubt on the whole network. That's because the copper-to-fibre transition and the backbone topology were specified as separate, known quantities in the first place, not assembled ad hoc as the site grew.
Talk to Our Engineers
None of this requires guessing at a rating. Cable and connector selection for the backbone and the cabinet run alike is confirmed against the datasheet for the specific ETHERLINE®, UNITRONIC® or HITRONIC® series involved, the same discipline the rest of this series applies to connectors and harnesses.
If you are specifying the communication network for a new solar plant, a wind farm, or a repowering programme, our connectivity specialists can help you match the copper-to-fibre transition to your site's layout. Tell us the node count and the backbone distance, and we will point you to the right ETHERLINE®, UNITRONIC® and HITRONIC® specification rather than a generic part.
Reach our connectivity specialists via the LAPP SEA enquiry page and flag the wind and renewable energy channel.
