Random Console Beeping and the 333 error

[rs691919]

I've seen several threads regarding this issue, but I wanted to revive the topic to see if anyone has a solution. I started getting the Button 333 message along with random beeps at one of my keypads throughout the day last weekend. I'm an end user, so my technical knowledge is limited, though I have a lot of experience (12 years now) with the Omni system, and I've done all of the automation programming myself.

I have an Omni II Pro board with two keypads (one in mudroom, one in bedroom) and a wireless receiver which is connected to a single glass break sensor in the dining room. All other occupancy sensors, motion sensors, glass break, and door sensors are hard-wired. Keypad 1 started beeping randomly and turning off the console beeps last weekend. I've done a ton of troubleshooting to no avail so far.

1) I tried resetting RAM and warm reset at the panel, but that did nothing
2) I had a spare keypad which my integrator gave me, and I swapped that out but the beeps continued on the new keypad (address 1).
3) I changed the address on the mudroom keypad to 3, but then the beeps and 333 message came up on keypad 2!
4) I disconnected the black wire on the wireless receiver at the suggestion of my integrator and the beeps seem to have stopped (after an hour thus far). HOWEVER, then the console beep menu (off: 0, on: 1) keeps popping up and then the system keeps randomly displaying Beeper off (See attached pic). This is turning the beeper off on keypad 1 but keeps them on keypad 2.

All this suggests to me that the problem is either at the panel or the wireless receiver, since the message is being set to the first keypad address (keypad 1 before keypad 2, keypad 2 before keypad 3). Now that the black wire (and sorry, I don't know what the black wire is!) on the wireless receiver is disconnected, the problem is ALMOST fixed -- but now it's turning the beeper off completely on keypad 1. Any thoughts would be appreciated!! Thank you in advance.

 

[pete_c]

Looking at an old thread see this:

HAI console issue

Not sure if my panel needs to be replaced or if I was unlucky enough to have a console go bad kind of quick. Anyway one of my consoles periodically beeps 3 times and display Button 333. I cleared out the code restarted the system and also reset RAM on my system. It is only happening at one...

cocoontech.com

Tighten up the data cables on both sides of the console might fix it. I have noticed that over time my OmnPro 2 terminal screws get loose on their own.

 

[rs691919]

Tighten up the data cables on both sides of the console might fix it. I have noticed that over time my OmnPro 2 terminal screws get loose on their own.

I tried that. Didn't do anything different unfortunately.

 

[pete_c]

Maybe there is a hardware problem with the console. Try a replacement console?

 

[rs691919]

Maybe there is a hardware problem with the console. Try a replacement console?

Switched the console out and the error still occurred. Changed the console address to 3, and the panel started sending the error to console 2 (in the master bedroom). So it would seem the error is at the panel or something to do with the wireless receiver.

 

[pete_c]

Disconnect the wireless receiver next.

 

[Oznavad]

I seem to be having the same problems, starting a few weeks ago. One (of 2 consoles, 2 touchscreens) console beeps at random times. When I look at the console after it beeps it is on random screens, most often Energy Cost screen. Now I am getting random ALL ON and ALL OFF commands sent to my 30 or so HAI switches, once or twice per day.
Just set up a log event for ALL ON command to see if that shows anything.
I moved the swapped the beeping console to second console location, where it continued to beep at the new location. So I thought it was a bad console and have that one disconnected. Still have the randomw lighting command going on with the console disconnected.
Going to check terminals on the panel. Any other suggestions would be great.

 

[ano]

I'm not an expert on this, but the Omni uses RS-232 and RS-485 buses to communicate with the outside world. The UPB transceiver uses RS-232 and the keypads are on the RS-485 bus, but these two buses are controlled together. As it gets old, its possible crystal that controls these transceivers has drifted slow or fast. If this happens it could cause errors with keypads and the UPB transceiver. I don't have a Omni board in front of me, but if it uses these clocks, maybe see if you can replace it. They are sometimes a silver metal box with 3 or 4 pins. And easy possible fix. Just a guess.