van ordinaire wrote: ↑27 Jan 2018, 01:29
Why should low brake fluid light be a fail - when the most likely cause of it, i.e. low brake fluid, isn't? Nor do I agree with Jim that it should be, simply because the level drops in normal use & will have triggered the warning light long before the low pad light comes on.
Why have a brake fluid level warning light at all if you're just going to ignore it ?

Nobody should be driving around with a low brake fluid warning light lit and I completely agree with the MOT failing on this. Who would knowingly go into an MOT with a brake fluid warning light lit anyway ? Top up the fluid first, it's not that hard!

Not doing so would be akin to knowingly going to the test with faulty indicator lights and being annoyed about getting a fail.
In all the cars I've owned I've never had a low brake fluid light as a result of pad wear so I'm skeptical that this is a real problem. (In fact I've never had to top up the level on any dot4 car I've owned, period)
Yes the level will drop slightly as the pistons move out to follow up worn pads but I'm sure this will be accounted for in the minimum/maximum levels in the reservoir. Also, if the brake fluid is being changed on a 2 yearly schedule as it should be, the level will be reset to the correct level with the current level of pad wear, so you would need an awful lot of pad wear in 2 years to reduce the level enough to light the warning. (If it is even possible at all) And if the fluid isn't being changed every 2 years, why not ?
So I just can't agree that its "normal" for the brake fluid level light to come on due to pad wear and that it should be ignored to the extent of passing an MOT.
I've only had one car that had a CEL come on on its own, it was entirely random, might just flash on, might stay on for the rest of the journey - but meant absolutely nothing! The corresponding warning on a lot of yanks simply advises the driver to "service engine soon" - why should that be a fail?
I agree about the generic "check engine" light - this shouldn't be an automatic fail because there are 101 reasons why it might be lit and the majority of them are not safety or emissions related! The only way it should be a fail would be if they connected a diagnostic tool to find out what the fault was and it was one of an approved list of faults that could be cause for failure, such as a misfire fault code etc. (Although an emissions test should already pick up that kind of fault)
They don't do that in the UK (right ?) but interestingly they do exactly this in the US, especially California. In fact the whole reason standardised OBD-II exists on cars is because California made it mandatory for vehicles after the mid 90's to have it - and the purpose of it was to allow the emissions performance of the car to be tested in their MOT by directly querying the on-board ECU for any signs of emissions related faults - if the car is reporting things like misfires, catalytic converter faults etc, it's a fail! They also do a tailpipe test on top of this, but fault codes alone are enough cause for failure.
Only later did OBD-II grow to be more than a tool for the California testing body to test the emissions of vehicles...