Wind Turbine Data Missing

This troubleshooting guide will lead you through a series of checks to isolate and solve the most frequent causes for data gaps for wind parks.

Introduction

Wind park data flow

1. A measurement is taken in the wind turbine, creating a data sample.

2. The data sample is stored in the wind park's data server.

3. The Ardexa Device access the data server trough the wind park's network.

4. The Ardexa Device stores a local copy of the data sample.

5. The Ardexa Device uploads the sample to the Ardexa Platform.

6. The sample is then available in the Ardexa Platform and API.

The data server is often managed by the wind turbine manufacturer (OEM), such as Vestas, Nordex, Enercon or other, and closely related to the SCADA. The interfaces used to access the data server may vary on a case-by-case basis.

Wind park network topology

From the perspective of the wind park network there are commonly two layout options: type "X" and type "Y". Understanding it's components and differences is critical to effectively identify and isolate potential issues.

The wind park's local network topology may vary on a case-by-case basis.

Type "Y" topology

Type "Y" topology uses the park's network to access both data server and the internet.

Type "X" topology

Type "X" topology uses two different subnets, one accessing the park's network and the other the internet, usually through a dedicated router.

Edge and Cloud connections

Ardexa offers two main methods for implementing site connections, Edge Devices and Cloud Devices. Understanding it's differences is critical to effectively identify and isolate potential issues.

Edge devices are deployed on the edge. A physical device is installed on-site to collect and upload the data.

Cloud devices are deployed in the cloud. A virtual machine connects through VPN to the site's network to collect and upload the data.

Prerequisites

1. Date and time of the ongoing data loss incident.

2. Cross-check the data gap with on-site modifications and incidents.

3. Contact the site's IT services provider

4. Acquire the site's network layout information

5. Contact the data server service provider

6. Acquire data server network settings and requirements

7. Acquire Ardexa Edge Device network settings

8. (If applicable) Acquire VPN connection details

Troubleshooting

Step 1: is the Ardexa Device connected via VPN?

✅Yes - Continue to step 2

❌No - Continue to step 6

Step 2: is the VPN up on-site?

The VPN might be set up by the site's IT services provider or by the OEM, such as Vestas PlantVPN. Clarify the VPN service provider before proceeding.

✅Yes - Continue to step 3

❌No - Contact VPN service provider

Step 3: is the VPN up in Ardexa?

✅Yes - Continue to step 6

❌No - Continue to step 4

Step 4: are the VPN type and credentials up-to-date?

Ensure there are no discrepancies on the VPN type and credentials in use and those set up on-site. VPN connections are occasionally updated and their credentials modified.

Ensure your VPN services provider notifies your organization before modifying the VPN to avoid data gaps.

✅Yes - Contact the Ardexa Support Team

❌No - Acquire and set up the updated VPN configuration and credentials

Step 5: is the Ardexa Edge Device offline?

✅Yes - Refer to the Offline Device troubleshooting guide

❌No - Continue to step 6

Step 6: navigate to machine plugins. Is data available on discovery?

✅Yes - Continue to step 7

❌No - Continue to step 8

Step 7: inspect the sample's timestamp. Is it recent?

✅Yes - Contact the Ardexa Support Team

❌No - There are no new data samples available in the data server. Contact the data server service provider, turbine OEM and double check for ongoing on-site issues.

Step 8: inspect the discovery output. Is there an error message?

✅Yes - Continue to step 10

❌No - Continue to step 9

Step 9: is the equipment suffering any unexpected incident?

Unexpected incidents, such as unscheduled wind turbine maintenance may cause data flow to stop, as no new data is generated by the equipment. Verify the equipment status before proceeding.

✅Yes - Wait for the equipment to return to normal operation

❌No - Contact the Ardexa Support Team

Step 10: is there a credentials mismatch?

Ensure the credentials of the data server configured in Ardexa are up-to-date.

✅Yes - Update data server credentials

❌No - Continue to step 11

Step 11: is there a connection timeout?

✅Yes - Continue to step 12

❌No - In case of a different error message, contact the Ardexa Support Team

Step 12: is the data server up?

Data server might be down for maintenance, ongoing work or unexpected circumstances.

✅Yes - Continue to step 13

❌No - Contact data server services provider

Step 13: is the data server IP address and interface port reachable by the Ardexa Device?

Reaching the data server can be accomplished by pinging the data server's IP address. Note that if ICMP is disabled in the network, ping won't work.

Reaching the data server interface port can be accomplished with commands such as nmap, netcat or telnet.

✅Yes - Contact the Ardexa Support Team

❌No - Continue to step 14

Step 14: is traffic allowed between the Ardexa Device and the data server IP address and interface port?

✅Yes - Continue to step 15

❌No - Contact the site's IT services provider. Ensure traffic is allowed between the Ardexa Device and the data server IP address and interface port.

Step 15: do the Ardexa Device network settings match the data server network requirements?

Some data servers may only accept connections from specific IP addresses or subnets.

✅Yes - Continue to step 16

❌No - Ensure the data server network requirements are met, such as potential IP NAT rules.

Step 17: is the interface set up in the data server?

Interfaces such as ODBC and OPCUA must be specifically enabled by the data server services provider.

✅Yes - Continue to step 18

❌No - Contact data server services provider to enable interface.

Step 18: (if applicable) is the connection of the Ardexa Device whitelisted by the data server?

✅Yes - Contact the Ardexa Support Team

❌No - Contact data server services provider to whitelist connection.

➖N/A - Contact the Ardexa Support Team.