Powered the M1G up for the first time today. It's mounted in the can, but the can is not in the wall yet. I want to bench test as much as I can before putting it in the wall. I started out with very few things wired up. No input zones, no outut zones. The only thing attached is an M1DBH with one M1KPB keypad attached to the M1DBH at J1. The terminating RJ45 jack is in J2 on the M1DBH. JP3 is jumpered on the main board. JP2 is not jumpered on the keypad. The only other things attached to the M1G are the ethernet adapter, the battery, the main power supply, and the phone line connection (which isn't plugged in on the other end yet).
When I power up, the LED's on the M1G look good -- power LED on steady, status LED blinking once per second. However, I got nothin' at the keypad. No lights, no sounds, no nothin'.
I shut it down, disconnected the keypad from the M1DBH, and disconnected the M1DBH from the M1G. I rewired the keypad to connect it directly to the M1G, jumpered JP2 on the keypad and powered up again. This time, instant reaction at the keypad. After a few seconds, it complained about output 2. I figured out that I needed to put a resistor across output 2 since I hadn't hooked up the siren yet. Shut it down, put in the resistor, powered it back up, everything works fine.
So, I know the keypad works and I know the M1G works and that it can communicate with a device on the data bus. So the problem must be in the M1DBH or the wiring attached to it. I checked all of the wiring to make sure it was connected correctly, and it looked good. I checked end to end continuity on all the wires and plugs. No problems.
So where do I go from here? Am I missing something in the installation/startup process? I have another keypad. Should I connect it to the M1G along with the M1DBH/keypad, remove the JP3 jumper on the M1G, and install the JP2 jumper on the homerun'ed keypad? Will that give me access to any diagnostic info?
I have the Elk RP software but haven't installed it yet. The ethernet adapter looks like it is working. It's blinking, and the switch it is connected to shows a connection. Should I go that route to help troubleshoot the M1DBH/keypad problem?
Thanks,
Ira
When I power up, the LED's on the M1G look good -- power LED on steady, status LED blinking once per second. However, I got nothin' at the keypad. No lights, no sounds, no nothin'.
I shut it down, disconnected the keypad from the M1DBH, and disconnected the M1DBH from the M1G. I rewired the keypad to connect it directly to the M1G, jumpered JP2 on the keypad and powered up again. This time, instant reaction at the keypad. After a few seconds, it complained about output 2. I figured out that I needed to put a resistor across output 2 since I hadn't hooked up the siren yet. Shut it down, put in the resistor, powered it back up, everything works fine.
So, I know the keypad works and I know the M1G works and that it can communicate with a device on the data bus. So the problem must be in the M1DBH or the wiring attached to it. I checked all of the wiring to make sure it was connected correctly, and it looked good. I checked end to end continuity on all the wires and plugs. No problems.
So where do I go from here? Am I missing something in the installation/startup process? I have another keypad. Should I connect it to the M1G along with the M1DBH/keypad, remove the JP3 jumper on the M1G, and install the JP2 jumper on the homerun'ed keypad? Will that give me access to any diagnostic info?
I have the Elk RP software but haven't installed it yet. The ethernet adapter looks like it is working. It's blinking, and the switch it is connected to shows a connection. Should I go that route to help troubleshoot the M1DBH/keypad problem?
Thanks,
Ira