Tallbloke Posted February 10, 2005 Posted February 10, 2005 I've been fitting Galaxy 60s for //.National Installer.// and have come across something weird when programming the prox tokens. I go through the usual routine, but when it gets to the stage whereby I press two keys* simultaneously, wait for the bleep, release the keys then offer the fob up I'm hitting a bit of a snag. The last two panels I've done have been 60s. The first one accepted the fob for the manager ok but subsequent fobs would only go in if I held the keys down with one hand AND offered the fob up with the other at the same time. Subsequently, they both wouldn't recognize the fobs on entry. I'd left the keypad access on 'always' until it was practical to program and distribute the fobs. I checked the programming and it looked ok - users had a small 'm' denoting they (should) have a valid fob. Keypad access was 'except entry'. I believe the //.National Installer.// versions come pre-programmed for DD243:2002. Maybe when temporarily using code entry I'm making a change that I don't know about, resulting in unresponsive fobs? I used to have Galaxy manuals but destroyed them when I left engineering thinking I'd never need them again. D'oh! I have have a rolled-up copy of a Gardner catalogue to hit myself with if I'm missing something obvious. Any ideas? Paul. * Exact procedure withheld on a public forum.
Guest Posted February 10, 2005 Posted February 10, 2005 I've been fitting Galaxy 60s for //.National Installer.// and have come across something weird when programming the prox tokens. I go through the usual routine, but when it gets to the stage whereby I press two keys* simultaneously, wait for the bleep, release the keys then offer the fob up I'm hitting a bit of a snag. The last two panels I've done have been 60s. The first one accepted the fob for the manager ok but subsequent fobs would only go in if I held the keys down with one hand AND offered the fob up with the other at the same time. Subsequently, they both wouldn't recognize the fobs on entry. I'd left the keypad access on 'always' until it was practical to program and distribute the fobs. I checked the programming and it looked ok - users had a small 'm' denoting they (should) have a valid fob. Keypad access was 'except entry'.I believe the //.National Installer.// versions come pre-programmed for DD243:2002. Maybe when temporarily using code entry I'm making a change that I don't know about, resulting in unresponsive fobs? I used to have Galaxy manuals but destroyed them when I left engineering thinking I'd never need them again. D'oh! I have have a rolled-up copy of a Gardner catalogue to hit myself with if I'm missing something obvious. Any ideas? Paul. * Exact procedure withheld on a public forum. 40012[/snapback] you should do it the latter way..press the two keys together then show the fob and let go of the two keys then you will see the no's going in..the problem you have is the except entry keypad function..this disables the code from unsetting on entry,tho it will unset the system after it has timed out..have you assigned the fobs to that rkp and prog'd as timed set
norman Posted February 11, 2005 Posted February 11, 2005 Press A and 1 together for a second let go and present the fob. then menu 12 timed set. Nothing is foolproof to a sufficiently talented fool.
Nova-Security Posted February 11, 2005 Posted February 11, 2005 You are changing to a different user to enter another fob ? www.nova-security.co.uk www.nsiapproved.co.uk No PMs please unless i know you or you are using this board with your proper name.
Tallbloke Posted February 11, 2005 Author Posted February 11, 2005 Yes, I'm changing to a different user for each fob and enabling 12 = timed set. Maybe I should do as Norman says and not wait for the beep. Keep 'em coming.
Nova-Security Posted February 11, 2005 Posted February 11, 2005 Press the keys (A + 1) and present the fob, i have never waited for a beep. www.nova-security.co.uk www.nsiapproved.co.uk No PMs please unless i know you or you are using this board with your proper name.
Brian c Posted February 11, 2005 Posted February 11, 2005 Press the keys (A + 1) and present the fob, i have never waited for a beep. 40097[/snapback] yup same here. only beeps when keys are pressed and , i think, when fob's presented. If you don't know......ask.
logical Posted February 12, 2005 Posted February 12, 2005 yup same here. only beeps when keys are pressed and , i think, when fob's presented. 40122[/snapback] theey can be wierd these fobs anyway i must pogram at least 20 or so over the phone each week and i have problems with at least one each week like this.could be 4.36 software which is(was) an //.National Installer.// special.they head all sorts of bugs wityh that one (hence 4.37) .thats what ive found mostly Trade Member
norman Posted February 12, 2005 Posted February 12, 2005 I never mentioned beep! Nothing is foolproof to a sufficiently talented fool.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.