Jump to content
Security Installer Community

Recommended Posts

Just ensure the address is set to an available slot (rotary dial on the keypad PCB) connect and enter / exit engineering to find the keypad.  Use diagnostic menu 61.1.2 to view current keypad addresses. Normally setting the new keypad to rotary position 1 will be fine as an existing keypad will be at 0.

Thank you.

 

Is it just connected in parallel with existing keypads?

Is this one connecting via RF. Is that an option? Keypad RF?? If this is the case, I would I add it? I can easily add a power supply to it.

 

Other than the engineer code, do I need to know anything else before connecting it?

 

Edited by ashs

Yes, parallel connection on the rs485 bus. A to A and B to B.  You don't get an RF keypad.  You do get the SelfMon VMOD module, which gives a keypad via browser on your WiFI.

  • 1 month later...

I finally got around to adding the keypad.

 

I'm getting all flashing asterisks on the display and the indicator LED is flashing.

 

I have the address selector set to 3. I have checked and the other keypads are set to 0, 1, and 2.

 

When I check in engineer mode it shows keypads 0,1,2 and 3 and all are showing 100% comms.

 

Is there anything else I should set? Do I need to 'tell' the system that a keypad has been added?

 

It's just connected in parallel with a short cable to an existing keypad on the other side of a wall. All of the other keypads are working fine still.

It seems too much time has passed to make an edit so here it is again.

 

Correction to the above:

 

The new keypad address is set to '3'.

 

The existing keypads are set to 0, 1 and 2.

In menu 60, when I check the keypad comms, keypads 0,2 and 3 show up as 100%.

 

The exisiting 0,1, and 2 keypads are all functioning correctly, however. Just the new '3' keypad is non-functional.

 

Is there something that needs to be set to correctly recognise all keypads?

The keypad that is now set to 1 was originally set to 3 and I changed it so that I could have the new keypad be '3' as it made more sense from a location point of view.

 

It seems as if the Galaxy hasn't picked up the address change from 3 to 1 of the existing keypad and is not detecting the new keypad now that it is set to 3.

Does that make sense?

1 hour ago, ashs said:

It seems too much time has passed to make an edit so here it is again.

 

Correction to the above:

 

The new keypad address is set to '3'.

 

The existing keypads are set to 0, 1 and 2.

In menu 60, when I check the keypad comms, keypads 0,2 and 3 show up as 100%.

 

The exisiting 0,1, and 2 keypads are all functioning correctly, however. Just the new '3' keypad is non-functional.

 

Is there something that needs to be set to correctly recognise all keypads?

The keypad that is now set to 1 was originally set to 3 and I changed it so that I could have the new keypad be '3' as it made more sense from a location point of view.

 

It seems as if the Galaxy hasn't picked up the address change from 3 to 1 of the existing keypad and is not detecting the new keypad now that it is set to 3.

Does that make sense?

To start with 

 

Swap one keypad with one of the others without changing the address, do it pulling off the plug rather than undoing the wiring 

 

Did the fault move with the keypad? Or does it start working?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.