pyronix enforcer - panel unresponsive

enforcer panel, self installed, worked perfectly 18th months. have 2x wireless entry arming station pads at different doors. entered through one of these today , attempted to use tag (failed) then code (also failed) then external and internal sounders went off with an alarm from the nearest PIR (which I must have triggered as the entry time expired) . walked to main panel and disarmed. head ringing from noise! Fault report on main panel "485 wzm" indicating comms issue.

into engineers menu - wireless diagnostics - reporting that BOTH (??) wireless keypads no signal.
whilst pondering on what to do, the engineers menu on the panel has now become non-responsive:
the usual engineers menu chime is occurring about every 10 - 20 minutes rather than the usual.
pressing A to exit does nothing
pressing NO is moving through the top level menu intermittently /randomly perhaps 30 minutes per item - trying to make my way to the exit option but not succeeding, currently stuck at "engineer tests 5.13"

apart from waiting to see if I can ever get the panel to respond or to see if it has some watchdog timer that will make it reboot itself, it seems to me like a CPU is stuck in a loop somewhere, making me think I need to power it down and back up again.

if I kill mains to the panel, and take the panel case off to remove the battery in order to full power down the panel, should I expect the external bell (wireless deltabell) to go off due to loss of comms with the panel, do I need a ladder and ear defenders ready?

Check panel psu ? Does it feel hot ? I've had 2 panel switchmode psu's melt the outer psu casing and failed !
Also does the internal battery pack feel hot ? These may be the issue

no heat on the panel case on the outside, no electrical smells, no obvious power related symptoms. not had the lid off yet mind.
after about 2 hrs of seemingly stuck in an infinite loop panel seems to have reset itself. After which, I got about ten "wiring fault" alerts in the app, plus the original alert for the "burglary", so the comms module finally got its act back together. 485 error is still there. tomorrow a.m. when I can take the risk with noise, I'll try and get into engineer menu to silence the system then go from there.

default the panel on the pins if you know how to do it, we had one like this from a take over from Banham (not clean start) its not in the engineers manual.

Would A ...remove front , check psu ....you will know if there is a problem as the casing will be melted
B Totally down power battery and mains , leave 1 minute and re power ..see if that cures it !

did a full power down mains and batt. no issues with the psu inside case. left off for a good hour (not on purpose, just happened to be lunch time). after power up, system is working as expected again. I have no explanation for why it went loopy... is it feasible that this kind of system just needs a reboot once in a while? (it had been running for a good year or more without being touched).

been running diagnostics, I get battery low from some sensors sometimes (but not everytime) and the front door wireless panel seems subjectively a little slow to wake on entry , so I will change some batteries, but I can't see how that would have made the main panel lose its marbles.

Hi, did the alarm go off after a full shutdown? No e is doing the same thing, just frozen screen. Thanks

Did the external sounder go off with the mains and battery dissed?

If not you also have a problem out there, better get that ladder ready.

Paulie147 said:

Hi, did the alarm go off after a full shutdown? No e is doing the same thing, just frozen screen. Thanks

Click to expand...

no the alarm didn't go off. I did manage to check that the bell supervision option was unset before shutting down.

system has been completely stable since. 4 weeks ago the panel told me to change batteries in one PIR , and that is the first one I've changed - so I am not convinced that it was battery levels at the time of the issue either.

the only explanation I can think of is that the system was just in need of a reboot. like a pc been running for too long needing its memory cleared.