Problem with M1xin install

Today I installed a second m1dbh in a remote (away from M1 panel) area about 70+/-Ft. from the M1. Then I attached a new m1xin to the new m1dbh. The address of the m1xin was set to 13, zones 193-208. I jumpered JP1 = no. The m1xin is plugged into the first position of the new m1dbh and the terminator is in the next position. The m1xin enrolled without any problem. I defined zones 193 and 195 as Burglar Perimeter Instant and Normally Closed. Shorted each of them with a wire.

When I watch them on the Current Status page of Elkrp they are both toggleing from normal (Short (-)) to violated (open (+)). I rechecked my work for loose connections etc. without finding anything.

Also the DB led on the m1xin is flashing at about a rate of a second.

Anyone have a idea what I have done wrong? And what does the status of the leds on m1xin mean?

I think the LED status is silkscreened right in the circuit board.

gatchel said:

I think the LED status is silkscreened right in the circuit board.

Click to expand...

Your right. It is flashing 1 = ok.

Where is the first DBH? Are they both connected directly to the controller? Both DBH have their terminator plugs in first unused position and all devices have no terminator... If you only had 1 DBH thern you prbably had J3 on the controller on. I think if you add a second DBH to the control you need to remove J3 (each DBH will be considered an end and be terminated). With only the 1 DBH, the control itself was an end.

You can check resistance across Data A and B at the control, it should be around 65-70 ohms +- 10 or so.

Ok, I powered down and recabled. Right now I am back to where I was this morning but with the new m1xin plugged into J7 of the orginal m1dbh. The new m1dbh is disconnected. Config is M1 to m1dbh (all orginal) and new m1xin plugged as above. The second (new) m1dbh is out of the picture and so is its cable, etc.

Same problem. Shorted 193 and 195 toggle back and forth from normal to violated. No pattern to the time that they are violated or normal. Going to make another cable from m1xin to m1dbh. Thats the only thing left I can think of.

Well, new cable installed still failing.. Don't know what else to try.

Do you by chance have a M1ZTS temperature sensor connected to one of those zones and defined as something other than temperature?

Also, try connecting the M1XIN directly to the M1 data bus and see if that changes the operation.

Spanky said:

Do you by chance have a M1ZTS temperature sensor connected to one of those zones and defined as something other than temperature?

Also, try connecting the M1XIN directly to the M1 data bus and see if that changes the operation.

Click to expand...

I do not have a M1ZTS.

I connected the m1xin directly to the m1 data bus and changed JP1 to yes. It is still doing the same thing. Zones toggle back and forth from normal to violated.

If I need a replacement do I call Elk or the dealer?

YAHOO! It's fixed!

Elk tech support is great.

Story is the Keypads do something with the address’s 193 to 208. They had me change the m1xin’s address to 12 instead of 13 and everything works as advertised.

Good news!

this old thread helped me out - I had crossed A&B along the way in my chain of devices. After correcting that and re-polling the bus my recalcitrant M1XIN came around and decided to start talking.