Enercon Wind Turbines

Purpose

The purpose of this plugin is to read from Enercon Wind Turbines, via OPC XML DA.

Configuration of the Ardexa Edge Device

Ensure you have read a copy of the manufacturer's operating and safety manual. Please review the manual for safety instructions. Ardexa uses the Enercon OPC DA XML server to read live and historical data. The XML Server uses a SOAP-based web server to provide access to the data. It is available from a default TCP Port 6010 on the IP address for which the XML Server is located. Ardexa needs to know the IP address of the OPC XML DA server for the plant. Once the Ardexa edge device is installed on the plant's network, verify that it can "ping" the XML Server using the following command in the REMOTE SHELL (replace the IP address with the IP address of your XML Server):

ping -c 1 192.168.1.2

Also, check that the TCP Port for XML Server is open. You can do this using the REMOTE SHELL, using the nmap command as follows. You can also use curl to check you get a valid XML response.

nmap -sS -p 6010 192.168.1.2

At the Wind park, Enercon usually sets up the Ardexa devices in the following way. Use the ifconfig or ip a command to check the interfaces.

1. LAN A: Internet with an IP address allocated by DHCP

2. LAN B: Direct connection to the OPC server, via a static IP address provided by the plant technicians

The static address needs to be applied to the interface LAN B above. Please check the correct interface since it is possible that the interfaces may appear to be swapped. The OPC server address is almost always located at IP address 192.168.1.2/29. To check which interface is being used for Internet access, run the route command. It will respond with something like...

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1     0.0.0.0         UG    203    0        0 enp2s0
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.0.0     0.0.0.0         255.255.255.0   U     203    0        0 enp2s0
192.168.1.0     0.0.0.0         255.255.255.248 U     0      0        0 enp1s0

The Iface column in the line with Destination default tells you which interface is used for Internet access. Please don't forget to send to Ardexa:

1. Clear photographs of the installation

2. The IP address of the OPC DA XML Server

3. The IP address for the Ardexa edge device (to talk to the OPC Server)

4. The quantity and model numbers of all wind turbines at the park

Important Note on Missing Controllers

Sometimes a message may appear when doing a discover that details missing controller(s). This will appear as follows...

WARNING: The controller: Wecshad, for plant Plant1 is not supported. Please contact Ardexa
WARNING: The controller: Wecshad, for plant Plant2 is not supported. Please contact Ardexa
WARNING: The controller: Wecshad, for plant Plant3 is not supported. Please contact Ardexa
WARNING: The controller: Wecshad, for plant Plant4 is not supported. Please contact Ardexa
WARNING: The controller: Wecshad, for plant Plant5 is not supported. Please contact Ardexa
WARNING: The controller: Wecshad, for plant Plant6 is not supported. Please contact Ardexa

This means that there are controllers at the plant for which Ardexa has no documentation. These controllers will not be collected. Ardexa must be given the latest documentation on how to read these controllers. In these cases, it is important that the owner or operator of the plant supply Ardexa with the updated documentation for the plant, so these controllers can be read.

Usage

Enercon wind farm data can be analysed online and control values can be transmitted to the wind farm without having to use the Enercon SCADA Remote software. This Ardexa plugin will read the Enercon data in real time, and send it to the Ardexa cloud. Almost all Enercon data is recorded at no less than 1 minute intervals, and stored historically for usually no more than 12 hours. The following controllers are recognised: Wecstd, T40, T44a, T44b, T48a, T66, T70a, T70b, T82a1, T82a2, T101a1, T101a2, T126a1, T126a2, T126a3, Tep3c021, Tep3c022, Tep4c011, Tep4c012. If you have controllers different to these, then notify Ardexa. The plugin will read 4 different types of datasets: live, logbook, 1m, 10m. The following scenarios are recommended to be configured as four separate scenarios:

Dataset Name    Description                                 Collection Frequency
----------------------------------------------------------------------------------
10m             Turbine values sent to the "wind10m" table  5 minutes
1m              Turbine values sent to the "wind1m" table   30 seconds
live            Live values sent to the "windlive" table    30 seconds
logbook         Events sent to the "logbook" table          1 minute

Ardexa will only send data to the cloud if the timestamp of the last read has changed. Also note that the Dataset names listed above are pre-allocated based on turbine serial number and cannot be changed.

Arguments

• IP Address This is the IP address of the OPC XML DA server (Mandatory) ..something like: 192.168.1.2

• Dataset This is either all, live, logbook, 1m, 10m.

• Port The TCP Port to talk to the OPC XML server, with a default of 6010

Debug Commands

There are also some debug commands that can be run from the REMOTE SHELL. If the port is different than 6010, then use the option --port, For example:

enercon_opcxml browse 192.168.1.2 "Loc/Wec" --port 1410

These are the browse commands to the query the XML tree. Examples...

enercon_opcxml browse 192.168.1.2 ""
enercon_opcxml browse 192.168.1.2 "Loc"
enercon_opcxml browse 192.168.1.2 "Loc/Wec"
enercon_opcxml browse 192.168.1.2 "Loc/Wec/Plant1"
enercon_opcxml browse 192.168.1.2 "Loc/Wec/Plant1/P"

To read a particular end point value, then use the following command.

enercon_opcxml read 192.168.1.10 "Loc/Wec/Plant1/P"

To see the different controller types:

enercon_opcxml browse 192.168.1.2 "Loc/Wec/Plant1/Log"