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.

Wednesday, 9 April 2025

2025-Car4

 from the previous version I have copied some bits off to reuse. 

Basically to do with starting the subscriber. 

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


Fing shows RPi at 192.168.1.26

Had to change keygen, but then able to login via ssh.

sudo raspi-config to expand filessystem, and reboot.


https://raspberrytips.com/access-point-setup-raspberry-pi/ 


**sudo apt update, 

**sudo apt-get install firmware-zd1211.

**and nmtui to configure Ethernet IP and Wifi 

Ethernet   192.168.1.9/ 24    GW=192.168.1.1 ??? 

** Wifi  rc-car Ashmeads  Access Point 192.168.4.1/24  GW 192.168.4.254


Some of the commands I will need after re-initialising

/home/peterm/mqtt/subscriber.py

added in sudo nano /lib/systemd/system/subscriber.service


sudo apt-get install python3-pip


sudo apt install python3-paho-mqtt


Rebooted, and systemctl status for mosquitto and Subscriber.service showed both running. 


sudo systemctl enable mosquitto   started Mosquitto. 


Tried to connect via WiFi with controller, Eventually it said "Attempting MQTT' 

but nothing happened. 


How do I tell if AP mode is done and DHCP is set? 


https://raspberrytips.com/access-point-setup-raspberry-pi/    This looks pretty good. I shall run through it as If I hadn't already tried. 


Set country GB


sudo nmcli con add con-name hotspot ifname wlan0 type wifi ssid "rc-car"


sudo nmcli con modify hotspot wifi-sec.key-mgmt wpa-psk

sudo nmcli con modify hotspot wifi-sec.psk "Ashmeads"


sudo nmcli con modify hotspot 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared

Looks like it is nearly there,  journalctl | grep wifi


26/6/2025  Just discovered :
https://forums.raspberrypi.com/viewtopic.php?t=289311

The answers suggested here might just work. 

Have copied the text for subscriber.service from here,


[Unit]
Description=MQTT Subscription Service
After=multi-user.target

[Service]
Type=idle
ExecStart=/usr/bin/python3 /home/pi/mqtt/subscription.py

[Install]
WantedBy=multi-user.target

----------------------------
Changed the path to suit and name to subscriber.py. 

27/6/2025
from https://randomnerdtutorials.com/how-to-install-mosquitto-broker-on-raspberry-pi/

have edited 
/lib/systemd/system/subscriber.service
/etc/mosquitto/mosquitto.conf to allow anonymous connections
and checked  /home/peterm/pi/mqtt/subscriber.py


How to do it, and check it,

https://raspberrytips.com/access-point-setup-raspberry-pi/

Found a command that shows that dhcp is not installed. 
service --status-all
[ note - Mosquitto and Subscriber were not running either]

from this site shows how to do it:
https://raspberrytips.com/dhcp-server-on-raspberry-pi/

How to install and set up dnsmasq. 
Seems to work.

no, tablet doesn't connect, but wemos does. 
not quite, no log from subscriber, or reaction on LEDs.

sudo systemctl status subscriber
 showed that it failed because it could not find the file name. I had the wrong path, so I simplified it to /home/peterm/mqtt.'files'  and then edited the subscriber.service file. 

same problem with test file path in subscriber.py

Now I have the error: 
 subscriber.service - MQTT Subscription Service
    Loaded: loaded (/lib/systemd/system/subscriber.service; enabled; preset: enabled)
    Active: failed (Result: exit-code) since Sun 2025-06-29 16:00:21 BST; 6s ago
  Duration: 2.839s
   Process: 1004 ExecStart=/usr/bin/python3 /home/peterm/mqtt/subscriber.py (code=exited, status=1/FAILURE)
  Main PID: 1004 (code=exited, status=1/FAILURE)
       CPU: 2.604s

Jun 29 16:00:20 raspberrypi python3[1004]:     import RPi.GPIO as GPIO
Jun 29 16:00:20 raspberrypi python3[1004]:   File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 927, in <module>
Jun 29 16:00:20 raspberrypi python3[1004]:     RPI_INFO = _get_rpi_info()
Jun 29 16:00:20 raspberrypi python3[1004]:                ^^^^^^^^^^^^^^^
Jun 29 16:00:20 raspberrypi python3[1004]:   File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 428, in _get_rpi_info
Jun 29 16:00:20 raspberrypi python3[1004]:     raise NotImplementedError(
Jun 29 16:00:20 raspberrypi python3[1004]: NotImplementedError: This module does not understand old-style revision codes
Jun 29 16:00:21 raspberrypi systemd[1]: subscriber.service: Main process exited, code=exited, status=1/FAILURE
Jun 29 16:00:21 raspberrypi systemd[1]: subscriber.service: Failed with result 'exit-code'.
Jun 29 16:00:21 raspberrypi systemd[1]: subscriber.service: Consumed 2.604s CPU time.
~

So I have to find out how it has changed. 

2025-07-03   A Fix? 

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

No, it wants an environment set up.   But according to 'pip3  list' I have Rpi-lgpio version 0.6 installed. 

It needs to be hacked to set the Pi revision according to the new schema. 

I think this is how I have to do it:
https://rpi-lgpio.readthedocs.io/en/latest/differences.html

cat /proc/cpuinfo  gives
HArdware : BCM2835
Revision : 000f
Model B Rev 2

Going into Python3 and  'from RPi import GPIO'  Gives and error due to old style codes. 

14/7/25 
Found this: about using gpiozero as new module built into OS.

https://raspberrytips.com/raspberry-pi-gpio-pins/    which leads to this:

https://raspberrytips.com/gpio-zero-guide-raspberry-pi/

edited subscriber.py to remove import statement

Now have this error:

peterm@raspberrypi:~ $ sudo systemctl status subscriber
× subscriber.service - MQTT Subscription Service
    Loaded: loaded (/lib/systemd/system/subscriber.service; enabled; preset: enabled)
    Active: failed (Result: exit-code) since Wed 2025-07-16 21:12:58 BST; 3min 55s ago
  Duration: 1d 19h 12min 10.815s
  Main PID: 375 (code=exited, status=1/FAILURE)
       CPU: 2.463s

Jul 16 21:12:57 raspberrypi python3[375]:     return socket.create_connection(addr, timeout=self._>
Jul 16 21:12:57 raspberrypi python3[375]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^>
Jul 16 21:12:57 raspberrypi python3[375]:   File "/usr/lib/python3.11/socket.py", line 851, in cre>
Jul 16 21:12:57 raspberrypi python3[375]:     raise exceptions[0]
Jul 16 21:12:57 raspberrypi python3[375]:   File "/usr/lib/python3.11/socket.py", line 836, in cre>
Jul 16 21:12:57 raspberrypi python3[375]:     sock.connect(sa)
Jul 16 21:12:57 raspberrypi python3[375]: TimeoutError: timed out
Jul 16 21:12:58 raspberrypi systemd[1]: subscriber.service: Main process exited, code=exited, stat>
Jul 16 21:12:58 raspberrypi systemd[1]: subscriber.service: Failed with result 'exit-code'.
Jul 16 21:12:58 raspberrypi systemd[1]: subscriber.service: Consumed 2.463s CPU time.


2025-07-18  Major changes to subscriber.py GPIO handling as per
https://raspberrytips.com/raspberry-pi-gpio-pinout/

Problem setting up socket causes failure...
Changed socket IP address to 127.0.0.1 and this now seems OK.

Next problem: is in assigning GPIO pins to values .
An example gives 'from gpiozero import LED', and works with it.
I tried 'from gpiozero import MFWD' and it didn't like it, so what values can I use? 
from:   https://gpiozero.readthedocs.io/en/latest/api_output.html
Para   15.1.16 Motor should do it. 

Yes,  two calls to motor with different pins for forward and turn.

Having got this far I have discovered that there is a new book out on 'Simple Electronics with GPIO Zero' that explains all that i have fought through.

However the main loop keeps falling out. I need to find out why.


2025-Sept 18 
After Much trying I used Github CoPilot to debug the while loop on the Arduino software. 

While (condition) ;
{                                   -- should not have a semicolon. 

It should be While (condition 
{
.
.
.
}

It also changed some of the values from Left or right  to turn/left., and forward or backwards to Move/forwards...

I left those and changed the Raspberry Pi Python to match, and it now works.

On the wemos the left and right turns have a second push to turn off the turn mode. I need to change the Subscriber to recognise and act on these. 
This means add another couple of elif statements to the on_message function  calling turn stop functions that also have to be added. 


2026-01-24 
The software drives the test circuitry OK. But nothing moves on the car. Voltage gets to the driver board. 
I have discovered that the chip on the board is an TA6586. and it is driven as shown: 
https://components101.com/ics/ta6586-bi-directional-dc-motor-driver

The two inputs on the IC match to the R-Pi forward/backward lines, and are directly connected to the R-Pi. 

Is it a case of teh battery does not have enough oomph for it? 
















Thursday, 26 December 2024

RP 2040 a prime candidate for FORTH

 It seems to me that the Raspberry Pi RP 2040 is a proper candidate for the FORTH programming language.   I am not alone as somebody has already done some versions of the language.

https://wellys.com/posts/rp2040_forth/

https://github.com/kristianwiklund/rp2040-forth

https://hackaday.io/page/11525-multicore-forth-execution-with-multitasking-on-the-rp2040  

(ZeptoForth)

https://wiki.forth-ev.de/doku.php/en:pfw:assemblers_rp2040-assembler

I'll look into these. Then I'll see if I can put an MQTT publisher on one. 

The version of FORTH that I used back in '79-80.

https://www.forth.com/wp-content/uploads/2017/04/microFORTH_on_RCA_COSMAC_05_text.pdf

https://www.forth.com/wp-content/uploads/2017/04/microFORTH_on_RCA_COSMAC_05_source.pdf



Tuesday, 21 May 2024

Lets get car-4 working again ( May 2024) - Still trying April '25

April 9, 2025 - I am stopping this blog, because there seems to be something wrong and the R=Pi keeps restarting the Wifi. In doing this I have made an error. See next writeup -'2025-car4'

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


December 10, 2024: 

Here are two good pages about setting up MQTT and getting Publisher/broker and subscriber working. 

https://bytebeam.io/blog/getting-started-with-mqtt-on-raspberry-pi-using-python/ - Probably better

 as my Subscriber is written in Python. July 2023 Everything except how to set it up to start at boot.

[ MArch21 2025 - disappeared]


https://diyi0t.com/microcontroller-to-raspberry-pi-wifi-mqtt-communication/  

*** Excellent step-by-step setting up publisher, Broker and subscriber, except for autostart subscriber.

Now I need to find out how to get a  python Subscriber to start at boot.  

This link gives me the best help on what I want to do. 

https://www.codementor.io/@ufuksfk/how-to-run-a-python-script-in-linux-with-systemd-1nh2x3hi0e

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

Subscriber service now starts, but path to file is now

/home/peterm/pi/mqtt.  The peterm is added because the Pi now needs a user and that is peterm. PW is carr0t# 


14/12/24 Trying to get AP configured, but failing

https://themakermedic.com/posts/Pi-AP-Mode/ after configuring, tablet cannot find the SSID. 

Will look at this one tomorrow:

https://www.raspberryconnect.com/projects/65-raspberrypi-hotspot-accesspoints/168-raspberry-pi-hotspot-access-point-dhcpcd-method


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


Alternatively using crontab:

https://tutorials-raspberrypi.com/control-raspberry-pi-robots-via-infrared-remote-control-part-3/

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

Here is the earlier post about it.

https://www.blogger.com/blog/post/edit/preview/5415560036905179298/8810457589872963960


GPIO PIN            Wire colour 

                                  Car                             Test Rig

6                            White                            Pale yellow

12                          Orange                          White

18                         Red                                Blue

19                        Yellow                            Orange

23                        Green                             Yellow

Now I can swap R-Pis and see if there is a problem with the car one. 

swapped boards, and test rig ran the same, except that after analog left, left LED kept flickering and I couldn't stop it. Another software fault.

Also Red forward LED on at startup. 

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

23/8/2024 

HAve rebuilt software using latest RaspIOS and it is different. 

Looking at this to try and figure out how to configure it.

https://bytebeam.io/blog/getting-started-with-mqtt-on-raspberry-pi-using-python/

Problem installing Paho-mqtt. Need to look into it. 

12/10/24 working through this. Got through the update of Setting up Python dependencies and installing MQTT Python Libraries  

NOW! I remember, On boot I have to start the subscriber program.  I'll look in a previous writeup and see if I described the process. 


This goes quickly but gives instructions on how to enable the subscriber. and set the broker to run in the background. 

https://www.youtube.com/watch?v=za-IIZ1xVbA



22/10/24  https://forums.raspberrypi.com/viewtopic.php?t=318784  this gives some good advice for simplifying subscriber.

23/11/24 Useful commands  https://linuxhandbook.com/systemctl-commands/

https://randomnerdtutorials.com/how-to-install-mosquitto-broker-on-raspberry-pi/

https://randomnerdtutorials.com/testing-mosquitto-broker-and-client-on-raspbbery-pi/

https://pimylifeup.com/raspberry-pi-mosquitto-mqtt-server/

https://tutorials-raspberrypi.com/raspberry-pi-mqtt-broker-client-wireless-communication/?utm_content=cmp-true            [ this one needs some editing and explanations.]

 What I am missing is "sudo python mqtt_subscriber.py"  and what I need is to know how to enable this in startup. 

Useful from Pimylifeup:  sudo systemctl status mosquitto

Starting subscriber at login:

https://linustechtips.com/topic/1465144-run-python-scripts-on-startup/

Few ways,

 

Create a bat file and put it in the startup folder.  The bat file would look something similar to this

python3 [path to run]

Or however you run a python script on your computer in command prompt.  Confirm that it runs your python script and then put in your startup folder and it will run at login.

 

Other options, go to task scheduler.

Create a new task

Add a new trigger; selecting on startup (I can't remember you might need to click the run even if user isn't logged in...can't remember exactly when that triggers).  You could also do on login


EVEN Better:

https://www.howtogeek.com/687970/how-to-run-a-linux-program-at-startup-with-systemd/


=======================================================================

starting from scratch.


2025-1-4 image imaged onto 16Gb card. Set the userID and wifi parameters.

Fing shows RPi at 192.168.1.26

Had to change keygen, but then able to login via ssh.

sudo raspi-config to expand filessystem, and reboot.


sudo apt update, 

sudo apt-get install firmware-zd1211.

and nmtui to configure Ethernet IP and Wifi 

Ethernet   192.168.1.9/ 24    GW=192.168.1.31

Wifi  rc-car Ashmeads  Access Point 192.168.4.1/32  GW 192.168.4.255


 sudo reboot  

on ip .9 - good

check ifconfig

OK. 


Now see above to set up MQTT


https://diyi0t.com/microcontroller-to-raspberry-pi-wifi-mqtt-communication/ 

See Broker setup

Installation doesn't like reference to Raspian. 

Looks like it needs a DNA specified in IP config.   Back to nmtui.  No effect.

Found 

https://stevessmarthomeguide.com/install-mosquitto-raspberry-pi/


Which includes some setup that the others haven't even if it has not been updated for Raspbios 'Bookworm'.


But problem here too:

Resolving repo.mosquitto.org (repo.mosquitto.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘repo.mosquitto.org’

None of the solutions seem to work because 

sudo systemctl status systemd-resolved.service  could not be found. 


More work needed here: Tomorrow. 


28/3/2025


sudo systemctl enable mosquitto   started Mosquitto. 

To make it run automatically on boot?  It does. 


See link above about how to set up Subscriber service. 


/home/peterm/mqtt/subscriber.py

added in sudo nano /lib/systemd/system/subscriber.service


error on systemctl start.   It needed paho.mqtt


Think I needed this but not sure:

sudo apt-get install python3-pip


apt install python3-paho-mqtt


Rebooted, and systemctl status for mosquitto and Subscriber.service showed both running. 


Tried to connect via WiFi with controller, Eventually it said "Attempting MQTT' 

but nothing happened. 


How do I tell if AP mode is done and DHCP is set? 


https://raspberrytips.com/access-point-setup-raspberry-pi/    This looks pretty good. I shall run through it as If I hadn't already tried. 


Set country GB


sudo nmcli con add con-name hotspot ifname wlan0 type wifi ssid "rc-car"


sudo nmcli con modify hotspot wifi-sec.key-mgmt wpa-psk

sudo nmcli con modify hotspot wifi-sec.psk "Ashmeads"


sudo nmcli con modify hotspot 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared

Looks like it is nearly there,  journalctl | grep wifi shows continually starting wifi