Grego

Thanks, much appreciated. Re compromised fob, I was given a bunch of fob's by an awesome bloke... so I can always program another one Thank you. Yes, I had looked at that. I am one of those people that has a keypad phobia and feels more at home with the GUI. Sad I know But I will give the keypad a go and see what happens.

I have successfully installed my FX100+ system, and have a Mk7 prox pad which I'd like to use with fobs. I have read the manual and am a little bit confused on the setup. Here's what the setup looks like in the RSS software. I am a little unsure on a few areas. Under access control, which Menu Option would I choose? In the manual entry (below) it appears to say that when a user is using a fob they shouldn't have a PIN? I am unsure if I have placed the fob tag number in the correct location? Here's the fob I am trying to get working... As this is my first fob setup I have no doubt I am missing something simple. Appreciate any feedback.

Thanks Stuart. I'll leave in on 2... which makes it easier for my wife, and easier for me

Below from the manual... level 2 does exactly what is required - set and unset. Anything else I use a manager code.

I ended up changing the level (42.1.User code.2) for the user from 3 to 2 and the issue has gone away.

The system does set and unset, it just gives that message when unset. Occasionally we also see a message BOOT-UP, but the OMIT ZONES happens each time the system is unset.

Recently completed install of a Honeywell FX100+ system. Everything has gone reasonable well, thanks in a large part to feedback from the experts on this forum. When arriving home and un-setting the system, my wife follows the usual enter PIN and press ENT. Upon pressing ENT my wife sees the message below on the keypad. Is there a way to stop this message from appearing? Want to make my wife's experience really straight forward.

Give me suggestions and I can go from there.

Turns out I had the Program Outputs Polarity (53.3) the wrong way around, it needed positive polarity and not negative. I also set Mode 53.2 to LATCH, which I assume is the default setting. So the siren appears to be working, both in bell test and a full set test. I am planning on replacing the external siren/strobe... so perhaps the professionals on here could recommend a suitable domestic siren/strobe.

Did a walk test, and a full set test, and the external siren/strobe didn't fire? So I figure there's something I need to turn on for the opt ports to work?

Thanks for the tips on bus devices and power down Stuart... much appreciated.

Have completed all the wiring and programming following the Galaxy Flex Installer Manual. All rio's and zones appear to be working. Did a full set test, which seemed to work ok. Upon reentering the home and doing an unset the following message came up on the keypad... Not sure if that is an issue? Was surprised to see the message? Pressed esc to get back to the standard banner. Also wanted to ask... is there any suggestions on doing a realistic intruder test (opening a door that is set as intruder) to see if the alarm activates? I want to try and do a test without the external siren/bell going off (neighbours might not like it). Mind you, I am thinking I do want to be sure the bell and strobe actually work.

End up going into engineer mode and then exited which checks the tampers and modules, it found the missing keypad and prompted me to press * to remove the two associated items. Looks good now, no issues.

Yes, you are correct. I temporarily attached a spare MK7 prox pad I had, and the system appears to be looking for it. I'll need to work out how to remove it?

Hi James. I ended up following THIS video which helped me at the tag correctly. Seems to be ok for now. I will reboot the panel later today and see what happens.