M1DBH and enrollment process

[smm6321]

I've installed the m1kp1 with a m1pr at my front door. It's been up and running for about four weeks now. So, I got adventurous and decided to add a second keypad model m1kp2 with a m1pr attached, using the m1dbh just to make life simple. It's now about 30 to 35 hours later in reading all of the posts on this site related to keypad issues and trying the recommended solutions. I was hoping to not have to post this issue because it seems like such a simple solution, but I have a twist that seems to be unique from what I've read in other posts related to keypad issues. Hopefully this will be the last keypad post.

My keypads have the following hardware, boot, and firmware:

m1kp = hard .10, boot 3.0.14, firm 2.1.48

m1kp2 = hard 1.4, boot 3.0.14, firm 2.1.48

the M1G is using 4.5.24.0

My m1pr are less than 12 feet of wire away from their keypad hosts.

Any one of the three devices that I plug into the first port on the m1dbh will be recognized and enrolled properly by the controller. However, any device plugged into port two or three will not be recognized. I have tried to enrollment process from the first keypad and using Elk RP 1.6.22 with the same results. If I take the same three devices (mkkp1, m1kp2, and m1xin) and wire them in the power parallel, data serial method they are all recognized and the ohm out at 65. This to me proves that the wire runs from the keypad locations is correctly terminated (no mixed data lines) - right?

I've sent back the original m1dbh because I thought the second port was bad, since any device plugged in there failed to enroll. When the new m1dbh arrived I had hoped the cure had arrived with it - no such luck! I thought my Karma closet was pretty clean until I started this "simple" upgrade! I've attached a graphic of how I've linked the keypads to the m1dbh.

 

[brotsten]

I've installed the m1kp1 with a m1pr at my front door. It's been up and running for about four weeks now. So, I got adventurous and decided to add a second keypad model m1kp2 with a m1pr attached, using the m1dbh just to make life simple. It's now about 30 to 35 hours later in reading all of the posts on this site related to keypad issues and trying the recommended solutions. I was hoping to not have to post this issue because it seems like such a simple solution, but I have a twist that seems to be unique from what I've read in other posts related to keypad issues. Hopefully this will be the last keypad post.

My keypads have the following hardware, boot, and firmware:

m1kp = hard .10, boot 3.0.14, firm 2.1.48

m1kp2 = hard 1.4, boot 3.0.14, firm 2.1.48

the M1G is using 4.5.24.0

My m1pr are less than 12 feet of wire away from their keypad hosts.

Any one of the three devices that I plug into the first port on the m1dbh will be recognized and enrolled properly by the controller. However, any device plugged into port two or three will not be recognized. I have tried to enrollment process from the first keypad and using Elk RP 1.6.22 with the same results. If I take the same three devices (mkkp1, m1kp2, and m1xin) and wire them in the power parallel, data serial method they are all recognized and the ohm out at 65. This to me proves that the wire runs from the keypad locations is correctly terminated (no mixed data lines) - right?

I've sent back the original m1dbh because I thought the second port was bad, since any device plugged in there failed to enroll. When the new m1dbh arrived I had hoped the cure had arrived with it - no such luck! I thought my Karma closet was pretty clean until I started this "simple" upgrade! I've attached a graphic of how I've linked the keypads to the m1dbh.

Do you have the shorting plugs on the keypads for termination? They should all be removed if you are using a m1dbh.

Brian

 

[smm6321]

Do you have the shorting plugs on the keypads for termination? They should all be removed if you are using a m1dbh.

Brian

Brian,

Thanks for checking that detail. I forgot that is one of the things that I did verify on all three devices, only the controller has a jumper on JP3 and the terminator plug on the m1dbh. I even suspected the terminator plug was bad on the first m1dbh, but since I'm getting the exact same results on the replacement I've ruled that out.

Spencer

 

[Spanky]

smm6321,
It sounds like you are not returning the data A & B from the keypads to the next socket on the M1DBH. The Data A & B lines are getting to the first keypad, but without a return path to the M1DBH, the data will not be sent to the next keypad on the M1DBH.

With only the termination resistors at the M1 and the terminator plug on the M1DBH, measure the resistance across Data A & B with the power off on the M1. It should read about 65 ohms. If it reads 120 ohms the data path is not complete all the way to the terminating resistor on the M1DBH.