M1KP works, M1KP2 doesn't. WTF?!?

[miamicanes]

Well, I just made an interesting discovery. My M1KP keypad (id=1) works from both keypad locations I've wired (with or without termination jumper, doesn't seem to matter), but my M1KP2 keypad (id=2, set by holding key while powering up and manually setting id) doesn't work from either location (with or without termination jumper).

When I power up the system with the M1KP2 attached, here's what appears on its screen:

KP Addr-> 2
K.P. ver 1.2.1.48, (quickly changes to "Lost. Comm.")

Any idea what could cause THIS to happen?

 

[lugnut]

Well, I just made an interesting discovery. My M1KP keypad (id=1) works from both keypad locations I've wired (with or without termination jumper, doesn't seem to matter), but my M1KP2 keypad (id=2, set by holding key while powering up and manually setting id) doesn't work from either location (with or without termination jumper).

When I power up the system with the M1KP2 attached, here's what appears on its screen:

KP Addr-> 2
K.P. ver 1.2.1.48, (quickly changes to "Lost. Comm.")

Any idea what could cause THIS to happen?

Enroll the 2nd keypad (the one with the comm error) via the first keypad (the one that is working).

 

[miamicanes]

Nevermind. I decided to try re-enrolling the modules after setting the M1KP to id=2 (using the KP2 to enter the access code and launch the enrollment). This time it worked. I'd swear, though, that last night I tried the exact same thing (but with the KP2 set to 2, and the M1KP set to 1, using the M1KP to enter the access code and enroll the keypads) and it didn't work. Weird.

(EDIT: whoops, I guess you had the same idea and posted your reply while I was writing mine)