Thursday, 11 June 2026

2026- Car 4 New controller using PICO



Preparing the computer:

To enable the port for the user to be able to connect through it to the PICO.

sudo usermod -a -G dialout peterm

Next to Download the files for MQTT communication as Per:

https://randomnerdtutorials.com/raspberry-pi-pico-w-mqtt-micropython

Download and configure the files for Network configuration

https://randomnerdtutorials.com/raspberry-pi-pico-w-wi-fi-micropython/

Use the bit about Connecting your Pico board to your Wi-Fi network in writing the software.

Reading inputs:

https://randomnerdtutorials.com/raspberry-pi-pico-outputs-inputs-micropython/

pins 1,2,4,5,9 for inputs pin 1 is GPIO 0, etc.‘button = Pin(21, Pin.IN, Pin.PULL_UP)’ has pull up resistor.

I2C LCD display

https://randomnerdtutorials.com/raspberry-pi-pico-i2c-lcd-display-micropython/

pins 6 SDA GPIO 4

pin 7 SCL GPIO 5

Pin 8 gnd

Ran the I2C test program from randomnerd tutorials start and got this:

I2C SCANNER

i2c devices found: 1

I2C hexadecimal address: 0x27

MicroPython v1.28.0 on 2026-04-06; Raspberry Pi Pico 2 W with RP2350

Type "help()" for more information.

Hint: Change the file name to main.py and reboot the PICO

The Hello World program worked too, though only on two lines.

I will put that into my 1C version and test it again.

Have tested moving text program too.
---------------------
Building the System
---------------------

There are four parts.

1. Driving the display -- Done

2. Input of keypresses via GPIO

3. Wifi link to car

4. MQTT communications.

In this order I think.
So next step is to wire up the switches. All must have pullups so key goes to ground.
Built switches into controller, and it all worked. That’s part B done

Part C: From Randomnerd tutorials set up WiFi.

It connected but assigned a random IP address rather than the one set in the program.

Have set specified IP address. It works.

Now to figure out how to send MQTT data – Part D

Have added appropriate lines from MQTT sample I think.

Error as it cannot find ‘client’

It now seems that when it sends it wants 3 parts to send and I only have two.

When I broke the data into two parts it still didn’t work.

I am looking at what other references suggest for MQTT:

https://www.hivemq.com/blog/iot-reading-sensor-data-raspberry-pi-pico-w-micropython-mqtt-node-red/

2026-6-3

According to Subscriber I am subscribing to topic “rc-car”

In Publisher I have set topic to ‘Move’ or ‘turn’ and I get the error:

"Connection successful!

IP address: 192.168.4.4

Error connecting to MQTT: [Errno 104] ECONNRESET

Traceback (most recent call last):

File "<stdin>", line 132, in <module>

File "<stdin>", line 112, in connect_mqtt

File "umqtt/simple.py", line 73, in connect

File "ssl.py", line 1, in wrap_socket

File "ssl.py", line 1, in wrap_socket

OSError: [Errno 104] ECONNRESET"

I don’t know whether this is an error sending, with the Broker, or with the Subscriber.

Try correcting the Topic by creating in the publisher a variable called p_topic
Same error.

The thing that calls line 112 is:

client = MQTTClient(client_id=MQTT_CLIENT_ID,
server=MQTT_SERVER,
port=MQTT_PORT,
# user=MQTT_USER,
# password=MQTT_PASSWORD,
keepalive=MQTT_KEEPALIVE,
ssl=MQTT_SSL,
ssl_params=MQTT_SSL_PARAMS
)

Which breaks down to:

client = MQTTClient(client_id= rc-car-11,
server=192.168.4.1,
port=1883,
# user=MQTT_USER, [commented out]
# password=MQTT_PASSWORD, [commented out]
keepalive=7200,
ssl= True,
ssl_params='server_hostname': 'raspberrypi'
)

As per suggestion, used the supplied simple.py file and still had the same error. I notice that the config
file contains a few items and they are duplicated throughout the program, so I tried changing the
program to just call them there, and that didn’t work: Invalid sysntax on one statement, so now I am
looking into the use of config files in micropython:

https://forums.raspberrypi.com/viewtopic.php?t=340983

https://stackoverflow.com/questions/5055042/whats-the-best-practice-using-a-settings

config-file-in-python – This refers to YAML and JSON and complicated data storage.

https://www.youtube.com/watch?v=g599FlcKgxA

2026-6-6 Lets learn about Micropython
https://www.mclibre.org/descargar/docs/revistas/hackspace-books/hackspace-get-started

-with-micropython-on-pico-01-202101.pdf Pretty good, if simple, for hardware connectivity and

data file stuff. Downloaded.

https://docs.micropython.org/en/latest/rp2/quickref.html

https://www.raspberrypi.com/documentation/microcontrollers/micropython.html

Look at Wiki and Forums later. From Wiki to ‘discussions’

Https://docs.micropython.org/en/latest/library/rp2.html - Not useful for current problem

AND ABOUT CONFIG FILES:

https://stackoverflow.com/questions/5055042/whats-the-best-practice-using-a-

settingsconfig-file-in-python too complex – discusses YAML and other complicated means.

https://docs.python.org/3/library/configparser.html configparser part of a program.

Took wifi stuff out of config file and put in program. It now connects, but doesn’t like

name ‘Topic’ – not defined.

Used p_topic – it worked for forward.

Check out all other motions.

Used for all. All work well, bit slow to respond. Need better off switch.

Fixed intermittent display, rotated socket on pin to Vsys on board for a better connection.

Have added state flag for turns so that turn button alternates on and off.

---------------------------------------------------------

#
#  RC Controller using Raspberry Pi Pico and MQTT   --- VERSION C

# this is a conversion from the Arduino software for the Wemos Microcontroller to Micropython for the R-Pi PICO

# PArt A -This is a test of the Display using I2C
# Part B - added input to GPIO pins, displayed
# Part C - Adding Wifi connection as per https://randomnerdtutorials.com/raspberry-pi-pico-w-wi-fi-micropython/

# 2026-5-10  working from  randomnerdtutorials.com/raspberry-pi-pico-i2c-lcd-display-micropython
#  For I2C display, use pin 6 for SDA, pin 7 for SCL, and pin 8 for GND now need 5v.

# ------------------------------

vers = "vn:1.C"

#Setting up I2C for LCD and MQTT
from machine import SoftI2C, Pin
from lcd_api import LcdApi
from pico_i2c_lcd import I2cLcd
from umqtt.simple import MQTTClient
import config
import network
from time import sleep


# set GPIO pins
button0 = Pin(0, Pin.IN, Pin.PULL_UP)   # forward
button1 = Pin(1, Pin.IN, Pin.PULL_UP)   # back
button2 = Pin(2, Pin.IN, Pin.PULL_UP)   # left
button3 = Pin(3, Pin.IN, Pin.PULL_UP)   # right
button4 = Pin(6, Pin.IN, Pin.PULL_UP)   # stop

# part D set up MQTT parameters
# in config.py
p_topic = "rc-car"

# Part C Wifi from  https://randomnerdtutorials.com/raspberry-pi-pico-w-wi-fi-micropython/
wifi_ssid = "rc-car"
wifi_password = 'Ashmeads'

# Static IP configuration
static_ip = '192.168.4.4'  # Replace with your desired static IP
subnet_mask = '255.255.255.0'
gateway_ip = '192.168.4.254'
dns_server = '8.8.8.8'

turn_state = False

# Init Wi-Fi Interface
def initialize_wifi(wifi_ssid, wifi_password):
    wlan = network.WLAN(network.STA_IF)
    wlan.active(True)

# Connect to your network
    wlan.connect(wifi_ssid, wifi_password)

# Wait for Wi-Fi connection
    connection_timeout = 10
    while connection_timeout > 0:
        if wlan.status() >= 3:
            break
        connection_timeout -= 1
        print('Waiting for Wi-Fi connection...')
        sleep(1)

# Set static IP address
    wlan.ifconfig((static_ip, subnet_mask, gateway_ip, dns_server))

# Check if connection is successful
    if wlan.status() != 3:
        raise RuntimeError('Failed to establish a network connection')
    else:
        print('Connection successful!')
        network_info = wlan.ifconfig()
        print('IP address:', network_info[0])
    return True


#   start test A here

# Rui Santos & Sara Santos - Random Nerd Tutorials
# Complete project details at https://RandomNerdTutorials.com/raspberry-pi-pico-i2c-lcd-display-micropython/


# Define the LCD I2C address and dimensions
I2C_ADDR = 0x27
I2C_NUM_ROWS = 4
I2C_NUM_COLS = 20

# Initialize I2C and LCD objects
i2c = SoftI2C(sda=Pin(4), scl=Pin(5), freq=400000)
lcd = I2cLcd(i2c, I2C_ADDR, I2C_NUM_ROWS, I2C_NUM_COLS)

def connect_mqtt():
    try:
        client = MQTTClient(client_id=config.mqtt_client_id,
                            server= config.mqtt_server,
                            port= config.mqtt_port,
#                            user=MQTT_USER,
#                            password=MQTT_PASSWORD,
                            keepalive=  config.mqtt_keepalive,
#                            ssl=MQTT_SSL,
#                            ssl_params=MQTT_SSL_PARAMS
                            )
        client.connect()
        return client
    except Exception as e:
        print('Error connecting to MQTT:', e)
        raise  # Re-raise the exception to see the full traceback

def send_MQTT(p_topic, message):
        client.publish(p_topic, message)
        lcd.move_to(4, 4)
        lcd.putstr(message)
        sleep(0.2)

try:
    lcd.move_to(12, 0)
    lcd.putstr(vers)
    sleep(0.2)
    if not initialize_wifi(wifi_ssid, wifi_password):
        print('Error connecting to the network... exiting program')
    else:
        # Connect to MQTT broker, start MQTT client
        client = connect_mqtt()
    
    while True:
        # check each GPIO input
        lcd.clear()
        if ( button0.value() == False):
            message = "move/forward"

            send_MQTT(p_topic, message)

        elif ( button1.value() == False):
            message = "move/backwards"

            send_MQTT(p_topic, message)

        elif ( button2.value() == False):
            if (turn_state == False):
                message = "turn/motorleft/on"
                turn_state = True
                print( message, turn_state)
                send_MQTT(p_topic, message)
            else:
                message = "turn/motorleft/off"
                turn_state = False
                print ( message, turn_state)
                send_MQTT(p_topic, message)

        elif ( button3.value() == False):
            if (turn_state == False):
                message = "turn/motorright/on"
                turn_state = True
                print( message, turn_state)
                send_MQTT(p_topic, message)
            else:
                message = "turn/motorright/off"
                turn_state = False
                print ( message, turn_state)
                send_MQTT(p_topic, message)

        elif ( button4.value() == False):
            message = "stop"
            send_MQTT(p_topic, message)

        else:
            lcd.move_to(5, 2)
            lcd.putstr("done loop")
#            sleep(1)



except KeyboardInterrupt:
    # Turn off the display when the code is interrupted by the user
    print("Keyboard interrupt")
    lcd.backlight_off()
    lcd.display_off()

VTOL flying wing drone concept

 11 June 2026.

This morning I saw a picture of a skunkworks flying wing drone built in collaboration with a Californian company. I can't find it again. It looked like it had a round orifice in the centre. It made me wonder. 

Could you create a flying wing drone with a propeller assembly in the middle of each wing, which when the drone was airborne, would swivel to a vertical orientation to provide propulsion forward. 


3 options: 
1] When the fan is oriented to the vertical to provide forward motion, there are two semicircular holes in the wing 

2] When the fan is oriented to the vertical, the semicircular open area is filled in  flush with the rest of the wing. this will reduce the effectiveness of the propeller.

3] When the fan is oriented to the vertical, the semicircular areas are filled in with  airfoil shaped hardware that comes out of the wing fore and aft to help provide lift. 

Would the propeller have to be modified to work best  when providing forward motion because of the wing impeding the airflow. 

These are all my ideas to date. I have not copied them from anywhere, except that Gemini AI provided the picture. 


Sunday, 26 April 2026

3D printing via USB [Serial]

 My printer does it. It did before I rebuilt my Kubuntu system. As it is now Cura does not recognize a USB connected printer. 

With the printer switched on lsusb gives me:

Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics CH340 serial converter

So I am looking for the ch340 driver. I think this is what I had to do last time.

I have found:

https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/linux

I need to relearn how to drive #make to get this installed.


Friday, 20 March 2026

2026 - Car 4 update.

 March 20. It was working today so I tried it out. I have done a few things to it since last I tried it. Last time things were held on with elastic bands, and it went very fast with the new batteries and threw them off, so it was dragging them behind!  Today It eventually turned over and broke the R-Pi posts that I had 3D printed.  Left/Right were also interchanged, and it didn't respond very quickly to the commands. I think I'll have to take out some delays. 

I have printed some battery holders, and also posts for the Raspberry Pi. See pictures.




These batteries are 16560  types, more powerful than the previous, and I have also changed the connectors to  xxxx  throughout all my batteries for interchangeability. You can just see the clips in purple  around the batteries.

Also now that the Raspberry Pi is attached to the frame, I could put the original car body back on with a bit of work. This of course is just cosmetic except that I have attached batteries on the underside of the body. 



I have decided to find some small screws to hold the Raspberry Pi zero in place through the pads that I printed for the pillars.

I edited the Subscriber.py to reduce the delays in the processing from 1 second to 0.1 seconds, and the car responds a great deal faster. I am very pleased. It means that the delay was not in the controller. 

A thing to try is to make the forward/backward motion half speed on the first push and then full speed. 

I am also going to try and build a controller using the Raspberry Pi PICO microcontroller.   I need to fix my 20x4 display:  https://www.ebay.co.uk/itm/267217818274?_skw=LCD+Display+20x4&itmmeta=01KMWPNF5JM6KA5FGFK4V8BXYH&hash=item3e376c52a2:g:xncAAOSw8E9i4RFk&itmprp=enc%3AAQALAAAA8GfYFPkwiKCW4ZNSs2u11xAq6P9ME%2BsprdHEOG6zvRM01NwhAgbFR5tYrpFVk2UOM270zFDLeIKMmxX%2FppzMv44kFuKN67qGgeDCzbrFuYLUqQwKYiWDYmR4T2IypX8dqwBcVnZ%2FMOEv8pQoEa4jaVGBcRtsTMNYQtzqAj5DTzPqo5S4oxccE5WAD2RNo5QTntnRlFNNM1q9SR3tw8FYHFErsFTIYdKQ%2Fp9sFw5zfoTg0dOmrdN1i09LuxIz7bMgDIbZIe5nfp1zD%2BWDcmnp8M%2FXWqtfp60VriylnO%2F8d0rWsjl4Ij8hX4bPHPVDbGHL%2BA%3D%3D%7Ctkp%3ABFBM-PLVlqdn

30/3/26 Starting to convert my Arduino C software for the Wemos to Micropython for the PICO
https://randomnerdtutorials.com/raspberry-pi-pico-w-mqtt-micropython/

6/4/26  Noticed that test.log shows problems:
2025-09-20 18:13:34,165 STOP!
2025-09-20 18:13:49,012 on_message part: connected Wemos-
2025-09-20 18:13:49,014 Fallen out of If-elif sequence
2025-09-20 18:15:15,482 on_message part: connected Wemos-
2025-09-20 18:15:15,486 Fallen out of If-elif sequence
2025-09-20 18:22:58,195 on_message part: connected Wemos-
2025-09-20 18:22:58,197 Fallen out of If-elif sequence
2025-09-20 18:40:49,234 on_message part: connected Wemos-
2025-09-20 18:40:49,235 Fallen out of If-elif sequence

Need to investigate, but meanwhile reduced sleep to 10msec. 

9/4/26   investigating micropython code for PICO

https://www.electroniclinic.com/raspberry-pi-pico-rp2040-programming-in-micropython-with-examples/     Check out some examples. Digital input, and display. 

display example
https://how2electronics.com/ir-thermometer-with-mlx90614-raspberry-pi-pico/

MQTT  
https://randomnerdtutorials.com/raspberry-pi-pico-w-mqtt-micropython/


Needs to put stuff on PICO - Trying to follow:
https://microcontrollerslab.com/getting-started-raspberry-pi-pico-thonny-ide/

see: https://madsmaddad.blogspot.com/2026/06/2026-car-4-new-controller-using-pico.html

Friday, 6 February 2026

Where are wind towers made?

 Answers from Gemini. They will surprise you.

where are the blades for a generator in a wind farm made?

Because wind turbine blades are massive—some reaching over 100 meters (330 feet) in length—they are rarely shipped across oceans. Instead, they are manufactured in specialized regional hubs located near major wind farm developments or deep-water ports.

As of 2026, wind turbine blade manufacturing is concentrated in several key global regions:

1. The Global Leaders

  • China: By far the world's largest producer. Companies like Goldwind, Envision, and Mingyang operate massive factories, particularly in provinces like Fujian and Guangdong. China currently holds over 50% of the global market share for blade production.

  • Europe: A pioneer in wind tech, with major hubs in Denmark (Vestas), Germany (Nordex/Siemens Gamesa), and Spain.

    • United Kingdom: The Siemens Gamesa factory in Hull is a major global player, recently unveiling world-first recyclable blades for offshore wind farms like Sofia and Dogger Bank.

  • United States: Focuses heavily on domestic supply. Vestas has a massive manufacturing footprint in Colorado (Windsor and Brighton), while GE Vernova operates facilities across the country to serve the North American market.


2. Emerging & Specialized Hubs

  • India: A growing hub for both domestic use and export, with companies like Suzlon and Winergy based in Pune and Aurangabad.

  • Brazil: Recently became a significant player in South America, with GE and Goldwind establishing local manufacturing to bypass high import taxes.

  • Poland: A new frontier for offshore wind, with Vestas opening a flagship blade factory in Szczecin (scheduled for 2026) to support Baltic Sea projects.


3. Why are they made there?

The location of a blade factory is determined by three "Logistical Laws":

  1. Coastal Access: For offshore wind, blades are so large they cannot be moved by road. Factories must be built directly on "Green Ports" where blades can be slid straight onto specialized installation vessels.

  2. Material Supply: Factories need to be near suppliers of carbon fiber, fiberglass, and balsa wood (used for the blade's core).

  3. Local Content Requirements: Many governments require wind farm developers to use locally-made components to create jobs, which forces manufacturers to build plants in the country where the wind farm is located.

How they are made

Blades aren't "machined" like car parts; they are "baked." Layers of fiberglass and carbon fiber are laid by hand into a giant mold, vacuum-sealed with resin, and cured in a large oven.

Note: While the blades are made in these specialized factories, the generator (the part that actually makes electricity) is housed in the "nacelle"—the box at the top of the tower—which is often manufactured in separate facilities entirely.


Where are the generators manufactured?

While blades are manufactured near the coast because of their awkward size, generators are essentially high-tech electrical engines. They are smaller, denser, and can be shipped more easily. As a result, they are typically made in established industrial heartlands where there is a deep history of electrical engineering.

Here is where the world’s wind turbine generators are manufactured as of 2026:

1. Europe: The Engineering Hubs

European manufacturers lead the high-efficiency and offshore markets.

  • Germany: The "capital" of wind generators. Vestas has a major generator factory in Travemünde, and Siemens Gamesa operates a massive assembly plant in Cuxhaven where generators are integrated into the turbine heads (nacelles).

  • Poland: A rising powerhouse for GE Vernova. Generators (specifically the W88 models) are manufactured in Wroclaw, while steam turbines are made in Elblag.

  • France: GE Vernova manufactures many of its high-tech offshore generators in Belfort and Nantes.

2. China: The High-Volume Leader

China produces the highest volume of generators globally, serving both its massive domestic market and international exports.

  • Tianjin: This is a critical global node. Vestas operates a major generator factory here, and it is the primary production base for Chinese giants like Goldwind and Envision.

  • Jiangsu Province: Most Chinese turbine components are concentrated in industrial clusters around Wuxi and Jiangyin, where specialized electrical firms act as sub-contractors for the big brands.

3. India: The Emerging Alternative

India has become a global export hub for wind components, often used as a "China-plus-one" strategy by western firms.

  • Pune & Chennai: Suzlon, one of the world's most vertically integrated companies, manufactures its own generators in Pune.

  • Tamil Nadu: Many international firms have set up manufacturing here due to the proximity to major ports and a highly skilled electrical engineering workforce.

4. United States: Domestic Assembly

While many raw generator components are imported, the US focus is on "Nacelle Assembly"—the process of putting the generator, gearbox, and electronics into the turbine housing.

  • Colorado: Vestas has a major assembly facility in Brighton.

  • New York: GE Vernova (headquartered in Schenectady) performs significant R&D and assembly work for onshore generators in the Northeast.


Why aren't they made "locally" like blades?

  • The "Weight vs. Size" Factor: A blade is light but 100 meters long (impossible for many roads). A generator is "only" the size of a small truck but weighs 100+ tons. It’s easier to put a 100-ton block on a heavy-duty train or ship than it is to navigate a 100-meter flexible blade through a city.

  • Expertise: Making a generator requires precision copper winding and advanced magnetics (often using Rare Earth elements). This requires specialized factories that have existed for decades, whereas a blade factory can be set up relatively quickly near a new port.

Would you like to know more about the "Rare Earth" minerals that go into these generators, or perhaps how the gearbox works alongside them?


Where are the components for the towers made?


Wind turbine towers are the "backbone" of the farm, and as of 2026, their manufacturing is a massive global operation. Because a single tower section can weigh over 80 tons and have a diameter of 4 to 6 meters, they are typically made in heavy-duty steel fabrication plants with direct access to rail or sea.

Here is where the tower components are manufactured:

1. China: The Global Hub

China produces the majority of the world's steel towers.

  • Key Regions: Manufacturing is concentrated in the Jiangsu and Zhejiang provinces.

  • Top Companies: CS Wind (the world’s largest tower manufacturer) has several massive plants in China, alongside domestic giants like Taisun and Dajin Heavy Industry.

  • Offshore Focus: Factories in Guangdong and Fujian specialize in "monopiles"—the massive steel tubes driven into the seabed for offshore farms.

2. Europe: Leading in "Green Steel"

Europe is the leader in high-tech and sustainable tower production.

  • Spain: A major European hub. GRI Renewable Industries operates several plants across Spain (like the one in Seville) that supply both onshore and offshore projects.

  • Denmark & Germany: Vestas and Siemens Gamesa have localized tower production. Germany's KGW Schweriner is a major specialist in tubular steel towers.

  • Poland: A rapidly growing hub. In 2024–2025, major new facilities opened in Szczecin and Gdańsk to supply the booming Baltic Sea offshore market.

  • United Kingdom: While many towers were historically imported, the UK has increased domestic production in places like Campbeltown, Scotland, to meet local content requirements.

3. North America: Expanding Domestic Capacity

The U.S. has seen a massive surge in tower manufacturing recently due to tax incentives (like the Inflation Reduction Act).

  • United States:

    • Pueblo, Colorado: Home to the world’s largest wind tower manufacturing plant, operated by CS Wind (formerly Vestas).

    • North Dakota & Iowa: Marmen/Welcon and Broadwind Energy operate large plants here to serve the windy "Great Plains" region.

    • East Coast: As of 2026, new facilities like those by US Forged Rings are coming online to produce 100% "Made in USA" towers for the growing offshore market.

  • Canada: Marmen operates one of North America's largest facilities in Trois-Rivières, Quebec.

4. India & Vietnam: The Export Specialists

  • Vietnam: CS Wind has a massive base here, which serves as a primary export hub for projects in the U.S. and Southeast Asia.

  • India: Companies like Suzlon and CuBuilt Engineers manufacture towers in industrial clusters in Gujarat and Tamil Nadu.


What are they actually made of?

While the majority are Tubular Steel Towers (large steel cylinders bolted together), new technologies are emerging to solve the "too big for the road" problem:

  • Hybrid Towers: The bottom half is made of pre-cast concrete (poured on-site or in a nearby yard), and the top half is steel.

  • Lattice Towers: Similar to electrical pylons, these are made of bolted steel beams. They are common in India and parts of Germany because the components are easier to transport.

  • Wood: In Sweden, companies like Modvion have begun producing laminated wood towers, which are carbon-neutral and easier to move in sections.

Fun Fact: The massive bolts and "flanges" (the rings that allow tower sections to be bolted together) are often made in specialized forging plants. For offshore turbines, these flanges can be up to 12 meters in diameter—as wide as a four-story building!


 look up which specific factory supplied a wind farm near Dorset, England

In Dorset, the story of wind turbine blades is a mix of "what could have been" and high-tech recycling.

Because Dorset is a highly protected landscape (Jurassic Coast, AONB), there are very few large-scale wind farms actually in the county. However, there are two notable projects—one built and one cancelled—with very specific blade origins:

1. Alaska Wind Farm (Masters Quarry, near Wareham)

This is the most significant wind farm in Dorset, which became fully operational in early 2024.

  • The Blades: These were sourced from Belgium.

  • The Story: Interestingly, these are refurbished Vestas V80 turbines. To make the project economically viable after a 20-year planning battle, the developer used high-quality "second-hand" turbines that were decommissioned from a site in Europe, refurbished to "as-new" condition, and shipped to Dorset.

  • Manufacturer: Originally manufactured by Vestas (likely in their Danish or German plants before being refurbished).

2. Navitus Bay (The "Almost" Farm)

This was a massive offshore wind farm proposed off the Dorset and Isle of Wight coast that was famously refused planning permission in 2015.

  • The Factory: Had it been built, the blades would have been made at the MHI Vestas factory in Newport, Isle of Wight.

  • Impact: This factory is just across the water from Dorset and remains one of the most advanced blade manufacturing sites in the world. Even though the Dorset project didn't happen, that factory currently produces the 100m+ V236 blades for other major UK offshore projects like Dogger Bank.


Other Local "Micro" Turbines

For the smaller, single turbines you might see on Dorset farms (like Rogershill Farm in Bere Regis):

  • Manufacturer: These are often Vestas V39 or EWT models.

  • Origin: Most mid-sized turbine blades in the UK are imported from Denmark or The Netherlands, as the UK's domestic manufacturing (like the Siemens Gamesa plant in Hull) focuses almost exclusively on the "giant" blades for offshore use.