Wednesday, 27 May 2026

Useless British engineering - bathroom extractor fans. Grrr.

The extractor fan in the downstairs toilet next to the utility room has failed - yet again. The damned thing has only been in existence for about 9 years and it's already killed 3 fans. 

Firstly I installed a (British) Ventaxia brand fan which lasted perhaps 3 years, by which time it was past its official 2 year warranty. Quite how watertight that claimed immunity beyond 2 years would be if I tested it legally would remain to be seen but I had a life to live, so I thought I'd simply replace it and move on. 

So I then bought a different (British) brand (I forget the name), only to find that when I removed the cover to connect it up, it had the exact same electronics. I simply swapped the boards over, to minimise the effort and damage that otherwise occur when replacing the entire assembly.

Of course, that failed after another 3 years, so I bought a different (British) brand again - Xpelair this time. And of course, 3 years later - yep, it's failed. This time it started to cut in and out and lost the ability to do a timed run-on.

I ordered yet another (British?) brand - this time it claimed a 5 year warranty and 40,000h life. This is the  Tornado ST100PR with PIR sensor and timer. at £102 a pop. 4th time lucky??


By way of a sanity check, 24/7 operation for 5 years would suggest 43,800 hours, although it's not going to be running flat out 24/7. 
That arrived this afternoon. 

But what about the old POS? 

What was wrong with it? There's not a lot on these things, so let's take a closer look. This model has a run-out timer but no humidity sensor, so the PCB only occupies about half of the available space. Today's versions are different again - although they look superficially the same on the outside, they are "continuous running" ie they tick over constantly and ramp up when triggered by the light input, a humidity sensor or (in some brands) a PIR sensor. That's annoying when fitted in your bedroom en suite. I assume this is due to some change in the planning regulations.


There's a large dropper resistor that appears to be 110R - and has failed open circuit. It's in series with the motor, so is one obvious reason the thing doesn't work.


There's some evidence of overheating on the top side of the board and underneath that discolouration are a load of 68k resistors:


Turns out that there is a pin header with a jumper that allows the motor to be run either directly across the mains or through that resistor, ie a high / low speed selector. Indeed the PCB ident says so, although the handbook is so utterly crap it doesn't mention that at all. There's talk of a setting for "bathroom or kitchen" which we can only guess is referring to this option - but why the actual fuck would you want to say so in the user instructions??? The dickhead who wrote the instructions knows what he meant but as the rest of us aren't psychic yet, it's it chocolate teapot territory.

Rant over. But what it means is that you can move the jumper to the "high speed" position and the motor runs again, albeit at the higher (noisier) setting. 

And of course, that isn't the end of the story. There's no time delay at initial turn-on and the fan turns off almost immediately after turning the light switch off ie no run-on delay, which is supposed to be set at the default 15 minute mark.


And of course you can snip out the duff resistor, as it serves no purpose now.


There's some surface mount stuff on the bottom of the (single sided) PCB:


The circuit is fairly simple, as you might expect / hope. 
  • Half wave rectifier with resistive dropper and zener to regulate the rail for the IC. 
  • That IC looks like a double opamp or comparator (same pinouts are generally used for both).
  • Tiny triac (that SOT-223 device).
  • Voltage sense input (when the light is turned on).
  • That large 2-3W resistor in series with the motor for 2-speed control (shorted out by the jumper link for high speed).
There aren't many components that can be responsible for setting delays other than capacitors - and there are only 2 on there whole board that could be fulfilling that role. It's these shitty "Chang" branded things and although they seem to measure as having the right capacitance, I assume their ESR has gone through the roof. 


I simply can't be arsed to measure them. Instead I simply replaced them with some similarly crap Chinesium caps I got from Aliexpress. "Swpeet" indeed!


There.


And sure enough it works ok-ish now. It's still destined to be replaced by the Tornado when I get round to it but at least the reason for its failure is fairly clear. To summarise - seems these boys employ interns who have all the design expertise of a sixth former. What an utter shit show.

More foolery and frustration with Claude Code in Probe Basic Lathe - and salvation!

 Since adding my "Lathe cycles" panel and macros, the main screen has ended up dropping off the bottom of the screen, leaving the bottom row of buttons only partially visible. These include the ESTOP reset button and the POWER enable button, both of which are rather useful if you plan to operate the machine.

It also affects the cycles screen:


Claude has made a complete arse of himself trying to fix this. Must have spent a couple of hours on this so far to no effect. It seems that the "CYCLES" button is screwing up the other elements on the screen.

On the "Probe Basic for Linuxcnc Control" Facebook group, I asked Chris Polanski (PBL author) if he had any suggestions:

Chris Polanski
your new tab widget is forcing it most likely
  • Reply
  • Share
Murray Edington
Yes, that seems like the cause but I'm at a loss how to fix it. It's almost as if the "cycles" tab has a carriage return (so it occupies 2 lines) that has forced the panel below it to move down. Annoyingly, everything else seems to be working nicely but it would be nice to see all of the bottom buttons, rather than just a glimpse of their tops. Could you point me in a general direction to look at?
  • Reply
  • Share
Chris Polanski
Murray Edington you need to watch your widget sizings and make sure they aren't causing the push down.. need to carefully resize everything so nothing is static or if its static it needs to be within the size constraints.
Chris Polanski
fun isn't it! lol
  • Reply
  • Share
Chris Polanski
How did you install? The reason is the updated font isn't installed but it should have been if apt install was used. I'd that's the case let me know.
  • Reply
  • Share
  • Edited
Murray Edington
Chris Polanski I followed the step-by-step process on your github. Then configured it for my setup, using the previous ini, hal etc files. This was a complete new install on a clean SSD, starting from the iso image at the top of the page.. https://kcjengr.github.io/.../probe_basic_trixie_apt...
KCJENGR.GITHUB.IO
Probe Basic Trixie APT Develop Install — ProbeBasic documentation

Probe Basic Trixie APT Develop Install — ProbeBasic documentation

  • Reply
  • Share
  • Remove Preview
  • Edited
Murray Edington
It's all working now but for some reason the bottom of the screen is off the display. The JOG/OFFSET/MDI buttons are no longer aligned with the MAIN/FILE/OFFSETS etc buttons by the same amount. Somehow, adding the cycles button has pushed content down. Any suggestions what to do? It was fine in the initial (SIM) installation before I messed it up.
Incidentally, the S WORD, MAX RPM & SF/MIN values all show 4 decimal places, which doesn't make sense. G94 & G95 values arguably the same?
May be an image of text that says 'FLE MACHИE ETTISES MIEA TOO.S ECUT HELP TLESNG BKE DAUNFER PAERG Grosve nHPEK3ИE CFILUSE Graave iameter 0.000 Greovez MACHINESTATUS STATUS:G7 0.000 Speed 100 RPM 2000 Feed 0.05 6лa6a Dianeter JOG 0 Iuu PereelNate ИAm 0.6MИ FILE 0.3MM OFFSETS TOLCHDFF CYCLESTART TDOL TABLE O.лMm STOP GROOVE PROBING 0.05MM FEED HOLD SETTINCS AXIS CLEAR 054 WORK G7 DIAMETER STATUS 0.02MM MACHINE SINGLE BLOCK CYCLES XDIA OTG FLOOD -0.000 RADIUS G96 DELETE -0.000 MIST NAN AUTO G97 à°¹ా REFX 0.000 EREAK SWORD 1000.0000 ИИ/M 0.000 BOTOZER 0.0000 DRO MAX 0% 695 F/REV 500. 0000 SPINOLE 0.0000 FEED MM/N RPM 137'
  • Reply
  • Share
  • Edited
Chris Polanski
Murray Edington all of the folders contain updated ui files, the subroutines ä are also updated and new and are needed, the easiest thing is move your custom ini/hal files into a copy of the SIM config
  • Reply
  • Share
Murray Edington
Chris Polanski That's encouraging. I can tell you already that the sim looks fine. When you say specific files, which do you mean - ini, hal, lathe macros, userui? Which ones should I be moving, to be clear? I think you are saying userui.
  • Reply
  • Share
  • Edited
Chris Polanski
ah.. you ned to move your specific files into the new config folder. the issue is your using the outdated user ui files which have not ben updated for the new licensed font. thats why the onyl items not displaying correctly are coming from your config folder files.
as a test, run the sim and if it displays correctly that definitely your problem
  • Reply
  • Share
  • Edited
Murray Edington
Debian 13 Trixie ✓
python3-probe-basic 1.0.1-53.dev from the trixie-dev repository ✓
python3-qtpyvcp 6.0.3-32.dev from the trixie-dev repository ✓
This is the trixie-dev channel (the development version for Trixie), installed via APT as the guide describes.
BTW, it's all running OK now, although I can confirm that homing without the linear encoders connected results in a rapid runaway (no damage - caught by the limit switch).
  • Reply
  • Share
  • Edited
Murray Edington
Chris Polanski let me know if you want any logs or run anything.
  • Reply
  • Share
Chris Polanski
Murray Edington ok. Let me see why the font isn't being installed
  • Reply
  • Share

It continued:

Murray Edington
Chris Polanski ah well, it kept me busy for a few hours and I learnt about stuff I never knew I wanted to. I will now focus on stuff I'm a bit better at, which isn't software. I agree about the buttock clenching nature of the Pugh macros. Having a backplot to visualise what is to be expected before you press the button feels like an entirely sensible approach. I'm looking forward to trying out your conversational stuff which looks truly wonderful.
  • Reply
  • Share
Chris Polanski
Murray Edington these completely replace those, no longer needed, they are less useful than the ones built here with no preview and direct run which to me is horrible and dangerous. best to output a gcode file and be able to see the plot incase you have a bad entry. unless of course you are infallible and like to roll the dice everytime you push that button..lol
  • Reply
  • Share
  • Edited
Chris Polanski
Murray Edington whats an AP's cycles?
Murray Edington
Chris Polanski I should ideally be able to take a vanilla PBL install and simply(?) add in the lathe cycles and little else. I have to say your true conversational preview looks absolutely wonderful. Having that as well as AP's cycles will offer all options in addition to gcode from CAM programs. Looking forward to seeing that - any idea when it will be ready for testing?
Chris Polanski
Murray Edington if you edited the probe basic core ui file you will need to remove/reinstall pb epr the docs, your ui user files you can do whatever you want too those should not affect the core files just be sure when you open editvcp to do your editing, that if you are using ai you tell it to leave the system wide probe absic install files alone.
Murray Edington
Chris Polanski yes, I was planning to revert to the original files, now that I've figured out what was messing up the button positions. Presumably that means the user .ui file(s)? Where's the best place to get unmolested originals? Can I just grab them from the initial PBL sim folders?
Chris Polanski
Murray Edington i would undo any other changes you may have made because it should not do what you have going on there. something is broken and if you are playing with ai for these edits it may have gone into some of the core files trying to fix what is broken and that should never be done because it will overwrite on update all edits should be specifically in the user ui files only!
Murray Edington
That appears to have almost fixed it. Still a couple of alignment issues but getting there....
May be an image of sea bird and text that says 'FLE MACHИE SETTISES EW TOOS KECUT HEL HELF 6H FNC215 DAUFER FAENG nHPEK3ИE И BedRadias 15.000 FinishZ EBSORSE ENIJASE 0.000 MACHINE G18 0.000 FiiehZ Taper TaperAagia 0.00 100 MaxRPM FeedRat Rate 2000 0.15 DepthoCut DapthoCu 1.000 FiniahDiemeter JOG FILE 0 OFFSETS uu CYCLESTART RUN TURNING 0.5MM PROBING RELOMO PON SETTINCS AXIS HOLD CLEARP G7 DIAMETER WORK 0.05MИ STATUS MACHINE BLOCK XDIA DTG RADIUS 3.100 BLOCK DELETE NAH -0.000 AUTO သောရ GOTD030 G97 0.000 FOWER REFX 0.000 SWORD 1000.0000 00:00:00 ИИ/ JOG 0.000 E-STOP 0.0000 MAX 695 F/REN BOTOHOME 500,0000 0.0000 သ SM/MIN 0.0000 MM/N RPN REVERSE STOP FORWARD'
  • Reply
  • Share
  • Edited

And then there is this:

Admin
Top contributor
  
Here is some preview of the Build tab and what it does, it allows the saving and loading of created geometry without having to re-enter everything, this allows the user to open previous builds and have those settings repopulate for easy viewing and editing and updating. it also allows users to store presets for various material types as templates with tool/speeds/feed/step-overs etc for rough and finishing which is super handy. everything about this conversational has been design with helping the job shop lathe operator to be able to quickly create/make/change programs for turning work without needing to get bogged down in cad/cam. Even though I am the guy creating this, I am super jazzed by the progress and functionality which as most of you will understand is a really great feeling and typically means something wonderful is coming together. I have a few odds and ends left before i start working on packaging. for those who have older machines maybe not running linuxcnc but still on maybe the older controls be it Fanuc or Siemens or whatever.. I have created a super simple single file parameters post processor configuration which allows users to simply map out their command code structure which then gets read in for gcode output making this a truly universal conversational package not just for probe basic but for any machine controller output type! super pumped!!
See less

This latest work from ChrisP knocks Andy Pugh's macros into a cocked hat, as they say. I can safely say the best course of action is for me to quietly put all this Claude Code / lathe macros to the side and await his update. At least that saves me having to f*ck about any further with something I don't understand, using an "agent" who knows only a little bit more than me!

Useless British engineering - bathroom extractor fans. Grrr.

The extractor fan in the downstairs toilet next to the utility room has failed - yet again. The damned thing has only been in existence for ...