sirocco Posted February 27, 2009 Author Share Posted February 27, 2009 Thanks for the quick response. Another thing which has been baffling me is programming keytags. I programmed two users with keytags (obtained from different sources) Both keytags looked identical,both presented OK to the keyprox and a healthy string of digits appeared followed by two beeps. However when I tried to set the alarm only one will initiate the setting proc and unset ok. The other gives one beep then nothing. I am guessing that the one of these that doesn't work is not compatable with the Honeywell Galaxy system even tho it looks identical and is recognised and able to be programmed in. Is there any way of identifying which keytags will work with a G2-20 other than trial and error? Link to comment Share on other sites More sharing options...
goncall Posted February 27, 2009 Share Posted February 27, 2009 Thanks for the quick response.Another thing which has been baffling me is programming keytags. I programmed two users with keytags (obtained from different sources) Both keytags looked identical,both presented OK to the keyprox and a healthy string of digits appeared followed by two beeps. However when I tried to set the alarm only one will initiate the setting proc and unset ok. The other gives one beep then nothing. I am guessing that the one of these that doesn't work is not compatable with the Honeywell Galaxy system even tho it looks identical and is recognised and able to be programmed in. Is there any way of identifying which keytags will work with a G2-20 other than trial and error? i presume they both progd the same,tho ive had problems too does the prox tag num start with 00 or 0 ive had to try a few times before it accepts it Link to comment Share on other sites More sharing options...
Guest old-hand Posted February 27, 2009 Share Posted February 27, 2009 Thanks for the quick response.Another thing which has been baffling me is programming keytags. I programmed two users with keytags (obtained from different sources) Both keytags looked identical,both presented OK to the keyprox and a healthy string of digits appeared followed by two beeps. However when I tried to set the alarm only one will initiate the setting proc and unset ok. The other gives one beep then nothing. I am guessing that the one of these that doesn't work is not compatable with the Honeywell Galaxy system even tho it looks identical and is recognised and able to be programmed in. Is there any way of identifying which keytags will work with a G2-20 other than trial and error? If it bleeps on presenting its a valid "tag" Check the programming. Link to comment Share on other sites More sharing options...
goncall Posted February 27, 2009 Share Posted February 27, 2009 If it bleeps on presenting its a valid "tag"Check the programming. no its doesnt,if its just one quick beep,it means its a prox tag not a programmed prox tag Link to comment Share on other sites More sharing options...
sirocco Posted February 27, 2009 Author Share Posted February 27, 2009 no its doesnt,if its just one quick beep,it means its a prox tag not a programmed prox tag So whats the difference? Can you make a proxtag into a programmed prox tag or is this set at manufacture? Link to comment Share on other sites More sharing options...
goncall Posted February 27, 2009 Share Posted February 27, 2009 So whats the difference? Can you make a proxtag into a programmed prox tag or is this set at manufacture? only by programming it again,sometimes the keypad doesnt read it correctly even tho you see the number go in..delete it and try again.. Link to comment Share on other sites More sharing options...
Guest RJBsec Posted February 27, 2009 Share Posted February 27, 2009 When you set the keypad to accept the code you can inadvertently add a digit. Go back into the programming mode and delete the existing tag number then programme it again. Remember too that to set with the tag you need to hold it there for several seconds, if you don't it will beep but not start to set. Link to comment Share on other sites More sharing options...
goncall Posted February 27, 2009 Share Posted February 27, 2009 When you set the keypad to accept the code you can inadvertently add a digit.Go back into the programming mode and delete the existing tag number then programme it again. Remember too that to set with the tag you need to hold it there for several seconds, if you don't it will beep but not start to set. agreed again,but ive always been told set the system with code unset with fob,i remember the early proxs caused probs setting and unsetting with fob only,i always tell customers code set fob unset..tho i know a few say fob set/unset...any thoughts? Link to comment Share on other sites More sharing options...
Guest RJBsec Posted February 27, 2009 Share Posted February 27, 2009 any thoughts? Never had any problems with the tags so just tell them to use them in and out. Link to comment Share on other sites More sharing options...
goncall Posted February 27, 2009 Share Posted February 27, 2009 Never had any problems with the tags so just tell them to use them in and out. only had probs on early 60's/500's not accepting fobs unsetting that had set the system,tho honeywell state code set/fob unset.. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.