Galaxy Keypads Beep

[sasa]

Hi mate, do you have a phone line connected to the panel ?

Yes. Remote access is OFF. Line Volts is supervised.

The panel is connected on analog phone terminal of PBX.

Something is strange about this connection. When we connect the analog phone instead of the control panel and make a call outside PBX, the phone number which is displayed on receiving phone doesn't match the phone number of the phone which make a call, but matches to the number of one other phone connected to PBX.

Also suspicioos matter is a fact that mysterious beeping started after PBX was introduced in the object (still under construction).

Regards. Sasa

[Gopher]

Yes. Remote access is OFF. Line Volts is supervised.

The panel is connected on analog phone terminal of PBX.

Something is strange about this connection. When we connect the analog phone instead of the control panel and make a call outside PBX, the phone number which is displayed on receiving phone doesn't match the phone number of the phone which make a call, but matches to the number of one other phone connected to PBX.

Also suspicioos matter is a fact that mysterious beeping started after PBX was introduced in the object (still under construction).

Regards. Sasa

Sounds like they mucked about with the phone lines and and have cross wired somewhere.

[sasa]

Hi, I am back.

James was right. As soon as we programmed the panel with the new data in which the keypad has e/e horn restricted only to used group, beeping stopped.

We have one keypad in security guard room which must indicate if the alarm occures in any sensor in any group.

That keypad still beeps.

Another strange problem is now present. When we download the log, the last event logged happened 02.07.2008.

Seems like the panel no longer log events.

Why is that so?

[james.wilson]

it might be set to only log so many events between set events, is it some tme since some groups were armed? if you arm the relevant group id bet it will start logging again. THis is to prevent some faults filling the log. It can be disabled.

And me.... right..... who would ever of thought it lol

Your keypad thats still beeping will be due to a group, you will need to naqrrow down what group it is. And might be worth disabling the log limit on a temp basis

[sasa]

Our panel programmer discovered that the panel logs events and the log can be seen on the keypads, but connected PC for unknown reason download only the part of the log (until 2.7.2008.). Before he has gone on vacation (2 weeks ago) he had turned off the simulated keypad on PC. Now he doesn't remember how he did that and can't turn it on again. The simulated keypad is on the PC screen, but it is not functional. Probably that's why the log can't be downloaded.

How to turn the simulated keypad on?

[james.wilson]

the log will be being downloaded but your filters may not be showing it. You cant disbale the virtual keypad.

[sasa]

the log will be being downloaded but your filters may not be showing it. You cant disbale the virtual keypad.

The virtual keypad start functioning for unknown reason.

All groups were set and unset one by one.

The group which might cause problems is not find yet.

[sasa]

the log will be being downloaded but your filters may not be showing it.

You were right again. The log filters restricted the log download.

Also thanks a lot for solving the beeping mystery. It seems that the entry zone 1022 caused beeping because this zone was open all the time and the panel automaticaly omitted it, but signal audio warning all the time ??? After the "O" parameter of that zone was checked and in 2 days unchecked, beeping stopped.

We may be wrong about this explanation, will see in the time to come... For now everything seems to be O.K.