Siemens Gamesa Wind Turbines

Purpose

This plugin will read from the Siemens Gamesa Wind Turbines via the ODBC Server

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 Siemens Gamesa Historian to read live and historical data. The Historian uses a Microsoft SQL Server to store the data. It is available from TCP Port 1433 on the IP address for which the Siemens Gamesa Historian server is located. Access to the data is via userid and password to a specific database. Once the Ardexa edge device is installed on the plant's network, verify that it can "ping" the Siemens Gamesa Historian using the following command in the REMOTE SHELL (replace the IP address with the IP address of the Historian Server):

ping -c 1 192.168.1.2

Also, check that the TCP Port for the Siemens Gamesa Historian is open. You can do this using the REMOTE SHELL, using the nmap command as follows.

nmap -sS -p 1433 192.168.1.2

Generally speaking, most firewalls are stateful. This means that once you allow outgoing connections, the firewall will recognise responses coming back from the Internet and let them pass despite the fact that there is no explicit rule to allow incoming data. Some older Siemens Gamesa installations may require additional rules to allow the Ardexa machine to work correctly. So be aware that;

• The firewall may not be stateful and therefore explicit incoming rules need to be created to allow replies to come back through the firewall (5671/tcp, 53/udp)

• DNS uses UDP which is not a "connection orientated" protocol and while modern routers handle it just fine. Some Gamesa sites might be old enough to require explicit rules to allow DNS.

Please don't forget to send to Ardexa:

1. Clear photographs of the installation

2. The IP address of the Siemens Gamesa Historian

3. The userid of the Siemens Gamesa Historian

4. The password of the Siemens Gamesa Historian

5. The database name, if it is different to WpsHistory

6. The port of the Siemens Gamesa Historian, if it is different to 1433.

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

Usage

The Linux driver to read the Microsoft SQL Server is automatically installed and configured when this plugin is installed. This Ardexa plugin will read the Siemens Gamesa data, via the Historian, in real time, and send it to the Ardexa cloud. Siemens Gamesa Historian data is recorded at various intervals, and stored historically for (usually) the life of the system. Selected data is collected from the Historian. The plugin will send most of the data to the wind10m table. Logbook (event) data will be sent to the logbook table, and some daily summary data will be sent to the winddaily table. It is recommended that only 1 scenario be implemented, with a frequency of 5 minutes. This will collect all the relevant data. Ardexa will only send data to the cloud if the timestamp of the last read has changed. Ardexa is able to send all historical data to the cloud, if required. The discover verb is be used to display the contents of the database. It needs only 1 argument, the configuration file (see below). Run a discover to see all the data. It will also show the data and time on SQL Server and compare it to the Ardexa device. Pay particular attention to these, since at times the Siemens Gamesa Historian time may not be synced. All date and times are in UTC. Also; please note that there is a difference in the amount of variables between the discover and log events. This has been done to reduce those variables that have NULL entries.

Arguments

• Configuration YAML A configuration YAML file must be included which can contain up to 6 items of information. An example of which is:

    ip_address: 192.168.1.10
    user: {whatever}
    passwd: {whatever}
    db_name: WpsHistory
    driver: FreeTDS
    port: 1433

• The db_name, driver and/or port maybe excluded and the default values will be used as follows:

    db_name: WpsHistory
    driver: ODBC Driver 17 for SQL Server
    port: 1433

• The port is optional. It will default to 1433

• If db_name is optional. If it is not defined, it will default to: WpsHistory

• the user and passwd items MUST be supplied by the client

• The driver is the software driver to use to connect to the database. For MSSQL installations greater than Version 2000, remove the driver entry and it will default to ODBC Driver 17 for SQL Server. For all other installations, include the line driver: FreeTDS