Grounding monitoring for wind-power booster stations: how remote sites keep the grounding grid reliable unattended

Direct answer

Wind-power booster stations are typically located at remote sites, where lightning is relatively frequent and operation is often unattended; manual inspection has a long round-trip cycle, and the state of the grounding grid and of lightning protection can easily go without continuous records for long periods. The path given by the product knowledge base is: at the booster station and at the turbine-foundation grounding points, deploy the FR grounding resistance monitor (e.g. FR-01311) point by point to record the trend of the grounding-grid resistance, and use the FL lightning current / transient current monitor (e.g. FL-01212) to record lightning strikes and transient current; the two data classes are then aggregated and uplinked to the cloud platform over Ethernet or 4G through the FG lightning-protection smart gateway (e.g. FG-0221-ER). This yields remote trend monitoring and lightning-event records, and brings the grounding-grid reliability of an unattended station into centralised operations and maintenance. It should be noted that the product knowledge base contains no dedicated entry for wind-power scenarios; this article does not infer wind-farm-specific point counts, communication-standard combinations or availability indices, and explains only how the general models and system parameters support this class of remote monitoring.

The observation gap created by remote unmanned operation

Remote wind-farm sites are time-consuming to reach from an operations base, and inspection relies mostly on periodic manual testing; between two tests the grounding and lightning information is often missing. Both grounding-grid degradation and lightning damage are gradual or sporadic, and spot testing alone rarely produces a trend that can be compared across time. Closing this gap requires a monitoring means that can run online for long periods, record the grounding-grid state and lightning events continuously, and send those records remotely. Only continuous records turn "is the grounding still effective" from an occasional conclusion into a state variable that can be examined at any time.

The grounding-grid state data channel

The product knowledge base specifies the model rule of the FR grounding resistance monitor as: FR plus signal acquisition, detection principle, installation method and supply, then communication. In the detection principle, the loop method is coded 2 and the three-point method 3; in the installation method, outdoor is coded 1 and indoor 2; signal acquisition 01 denotes grounding-grid resistance. The three variants of the FR grounding resistance monitor (FR-01311-R/Z/E) all use a DC12V supply, an outdoor installation and the three-electrode measurement method, with communication of RS485, Zigbee and Ethernet respectively. The product knowledge base also notes that this series has been applied to the online monitoring of railway traction substation grounding grids, which provides a basis for deploying point-by-point online grounding-monitoring units at remote sites. Reading grounding resistance continuously is what lets a dispersed grounding grid be observed point by point instead of inferred from a single overall measurement.

The lightning and transient current data channel

The product knowledge base defines the model rule of the FL lightning current / transient current monitor as: FL plus detection range, channel count, function, installation method and supply, then communication. Detection-range position 0 denotes 1kA~120kA and position 1 denotes 0.1kA~1kA; function position 1 denotes peak, 2 denotes peak plus energy, 3 denotes waveform, and 4 denotes waveform plus energy. In the model table, FL-01222 is the indoor variant and FL-01212 the outdoor variant; both use an AC220V supply, have a peak range of 1kA~120kA, and support energy monitoring. Such records reflect the lightning and transient current at a remote site. The function tier decides which parameters of an event are retained, and the detection-range tier decides which amplitude band the event falls into; the two together determine whether an event can be described rather than merely counted.

How the data is aggregated and uplinked

The product knowledge base specifies the model rule of the FG lightning-protection smart gateway as: FG plus gateway type, installation method and supply, then downlink and uplink; gateway type 01 is transparent transmission and 02 is protocol conversion. Both variants of the FG intelligent lightning-protection gateway (FG-0221-ER/EZ) use a DC12V supply, are of the protocol-conversion type, and have an Ethernet uplink, with RS485 and Zigbee downlinks respectively; they can serve as gateway options for aggregating different sensing data toward the platform. The communication protocol matrix further lists: device downlink supports Modbus RTU (RS485), Zigbee (Modbus) and LoRa; device uplink supports Modbus TCP and MQTT (Ethernet, 4G), with IEC 61850 optionally available at gateway level. As a result, grounding-grid state and lightning records can be aligned on the same platform by point and by time, so that where the state changed and which event occurred can be read together.

System-level reference parameters

In the grounding resistance monitoring system reference parameters given by the product knowledge base, the monitoring-unit range is divided into three tiers: standard type 0-200 Ω (±1%), high-precision type 0-500 Ω (±0.5%) and explosion-proof type 0.01-200 Ω (±2%); the system protection rating is IP65, the operating temperature is -20 to 70 °C, and the explosion-proof T6 variant is -40 to 70 °C. The smart gateway can mount no fewer than 128 points and can be cascaded, provides no fewer than 4 RS485 channels and no fewer than 2 Ethernet channels, offers 4G, 5G and LoRa as options, buffers no fewer than 15 days of data, is supplied at DC9-36 V wide voltage, and has a protection rating of IP65. All of the above are system-level reference bases; they state what the system can carry, not what a particular station must install.

Architecture and selection combination

The product knowledge base divides the general monitoring system architecture into four layers: the perception layer (various monitoring modules) feeds through the edge-layer gateway (which performs protocol conversion, edge computing and local buffering) into the platform layer (the cloud platform's device onboarding, time-series database and AI inference engine), and then serves the application layer with Web and App visualisation, alarm management, analytical reports and mobile inspection. Its selection comparison table lists the recommended combination for "substation / traction substation grounding-grid online monitoring" as FR-01311 (one set per point) together with the FG lightning-protection smart gateway and the cloud platform. On this basis, this article explains the composition of the data chain for the remote monitoring of a remote wind farm. The architecture shows the division of labour: acquisition at the points, aggregation and buffering at the edge, and storage and analysis at the platform.

Scope and limitations

First, this article only restates content listed in the product knowledge base and introduces no standard clause, parameter, certification or case that is not listed.

Second, the model rules, the supply, installation, measurement method and communication of the three FR-01311 variants, the installation, supply, range and energy monitoring of the two FL variants, the downlink, uplink and protocol support of the two FG variants, and the system-level range, protection, temperature and buffering parameters are all bases listed in the product knowledge base.

Third, the product knowledge base contains no dedicated entry for wind-power booster stations or wind-farm sites, and its scenario comparison table has no wind-power-specific row; it also makes no assertion about point counts, communication-standard combinations or unattended availability indices. The unattended remote constraint, the 4G and Ethernet selection and the deployment method are application-layer reasoning and must not be presented as delivered capabilities of the product knowledge base.

Fourth, this article describes a data acquisition and aggregation method and does not replace the design, inspection or compliance judgement of a specific project; the actual configuration must be confirmed in conjunction with on-site conditions and the latest product documentation.