Hi Gary,
I’d be extremely surprised if the on-board WiFi has packed in, as IIRC you only replaced your old Pi2 board with a new Pi3 one in June.
I take it you
did end up using the Pi3B+ you said you had bought? If so, (without supporting info or screenshots), my ‘best guess’ is that whilst trying to correct the fault reported in your initial post above, you may have inadvertently downloaded the older 20180520 version of the software from
https://pilotaware.lode.co.uk by mistake and copied this onto your card. It would be fairly easy to do this as the links to both versions are close together on the downloads page - and as I have said before, 20180520 definitely won’t work on your Pi3B+.
If you aren’t able to see the WiFi hotspot when you boot up your PAW, you can’t of course get screenshots, which is why Ian is suggesting connecting your PilotAware directly to a monitor (or TV) using a standard ‘TV’ HDMI cable. (The HDMI port is on the side of the PilotAware, next to the Power Connector.) This will let you watch the progress as the PAW boots up, so you can see if any faults are reported. If all is OK, you will see a rainbow ‘splash screen’ when you first power up the PAW, then a load of typed reporting lines, (lots of which will report ‘OK’ in green) and finally the Raspberry Pi ‘login’ prompt will appear. (at this point you don’t need to do anything - the PAW will run automatically and the WiFi Hotspot should appear on your phone or tablet very shortly afterwards.)
You are already aware of the fact that the red LED inside the end of the PAW case is the Power LED and should be constantly ‘on’. The adjacent green LED is the ‘Drive Access Light’, which should only be on while the PAW is booting or writing software to the card, so being ‘off’ is fairly normal.
We first need to check that you have loaded the correct software, which the HDMI ‘monitor’ should prove (or disprove) then we can go on to try to determine the original problem.
Let us know how you get on.
Best Regards
Peter