Any Glow Worm Experts?

[Quizmonster]

(I refer to plumbers, not entomologists!)
Our Glow Worm hxi is playing up at the moment. It simply switches off for no apparent reason and shows a red light with "Fault 12" in the window. At the same time, it makes a repeated whooshing sound.The manual states that Fault 12 is (quote) a "User interface connection fault; Check wiring between mainboard and user interface."
We switch it off and, when switching it back on a few minures later, it generally happily starts working again! Our tame plumber has never met this fault before, so we're all a bit puzzled. Any ideas?

[cleggie]

here you go

http://www.glow-worm.co.uk/trade/service/fault-finding-codes/subsites/betacom-a-range-10-232581.en_gb.html

[Quizmonster]

Thanks for that, Cleggie, but it doesn't really tell me much more than my quote from the User Manual in the OP.

[sandyRoe]

I'm sorry I can't help. I did think this was going to be a question that would stump the most recondite of ABers.

[Quizmonster]

Sorry to disappoint you, Sandy. Might've been interesting, given that I know nothing about the little twinklers either!

[The Builder]

QM .......... a can of worms .............. Boiler fault codes sometimes help point you in the right direction. They do often result from another fault somewhere else, which affects something different ........... which affects etc etc

The code suggests a bad electrical connection between the user buttons and the circuit board (PCB). That's easy to look at and check.

In reality, though, even a sensor fault somewhere, or a short circuit in an entirely separate gubbins can throw up (random) codes.

Glowworm engineers are excellent. I would contact Glowworm and arrange a visit. Anyone else would be swapping out everything you could think of to try and find it. Could cost more than Glowworm.

[Quizmonster]

Thanks for that advice, TB. Our usual plumber, for the past thirty years, is a personal friend and familiar with our Glow Worm, but he has certainly never come across this particular fault before. I don't believe he would just "change everything bit by bit" to find the actual fault.
He came on Monday at 4.30 pm again and actually experienced the fault in action. As we have done ourselves, he switched it off and back on again after a few minutes...it's still running perfectly as I write this at 11.30 am on Thursday!
I'd just leave it as is, but am somewhat concerned about the result if it happened when there was no one here!
Cheers, anyway.