M1 doc not matching RP and panel behavior for M1TWI and M1ZTS?

m1u

New Member
I'm bench testing an Elk M1 panel, getting ready to swap it in place
of my old panel, and I've run into a few puzzles where the panel, RP,
and the manual don't quite agree. One puzzle involves the M1TWI, and
the others involve temperature sensing. Any help or advice would be
greatly appreciated!

First, the documentation for the M1TWI (talk listen in) says that the
M1's OUT7/OUT8/OUT9 are used as triggers and have to be dedicated to
this TWI board. The wiring diagram makes use of those three OUT's, so
that makes sense. In order to use the M1TWI, I check the appropriate
box to enable it in RP. But then RP puts up a notice saying "if
enabled/using TWA, out 7/8/9/10 will be used as trigger. I don't have
the M1TWA... that seems to be a different talk-listen-in board perhaps
with additional capabilities? Its manual shows OUT10 being wired in
as well.

Can the M1 board can tell if I have TWI or TWA? What is the status of
my M1's OUT10 in my TWI installation: is it going to get energized as
part of the listen-in feature, so I can't use it for anything else?
It is lost to me because checking the box reserved it for TWA use, so
should just tape up the unconnected OUT10 wire and not use it?

Then, the temperature related questions:

1. I know the M1KP2 keypad (unlike the old KP1) lacks a built in
temperature sensor, but I thought that you could hang a temp sensor
like the M1ZTS off its built in zone input. However, the RP software
will not let me configure the type of that zone to be the 33=temp
sensor, complaining that only zones 1-160 can do that, and the keypad
zone was assigned a number like 193. Is that true, or am I missing
some way around this?

2. I have an M1XIN expander card to add 16 zones, so I have 32
regular zones, 1 through 32. I hooked a temp sensor (mine happens to
be M1ZTSR, which I think is the same as M1ZTS other than having the
sensor on a longer cable) up to zone 14 on the main board. RP let me
set the zone definition to "33=temperature" (and fast loop), and temp
sensing works fine. I can inspect the temperature by using the keypad,
navigating right to it via the automation menu . However, when I
tried to do the same thing using zone 17, it did not work: RP set it
up as type 33 just fine, but when I navigate the menus on the keypad
it does not find that temp sensor to display! Reading the M1 install
manual in detail, I see a note on page 6 saying:

NOTE: M1ZTS Temperature Sensors may only be connected to the first 16 zones

That matches what I see, but not what the RP software said earlier
about zones 1-160... Is the manual right and RP wrong, and all temp
sensors need to be collected into 1-16, or is there a work around so I
can put temp sensors on my M1XIN?

One more question now that I'm thinking some zone numbers are
different than other zone numbers: Once the system is installed, as I
add sensors over time I'm sure I'll just add them at the end, i.e. if
I use up 25 zones, my next sensor goes on 26. But since I'm getting
started now, I can put anything anywhere (other than any temp sensing
limitation). Any advice on organizing things? For example, would you
put all the doors on zone 1, 2, 3 etc, then motions as a group, then
glass break as a group etc? I'm not asking about organizing wires,
I'm thinking more from the point of view of the user at the
keypad... does it ever matter what zone number is assigned to
something as far as how system status is presented, so some orderings
are more convenient? Or am I free to pretty much randomly set up the
zones in any order?

Thanks.
 
1. ZTS's only to the board, there's a workaround using Dallas 1-wire and the KPAM, but that's a different animal.
2. First 16 zones onboard for ZTS's, as stated in the manual, not any expanders.

I generally zone a panel out starting with doors, then windows, then powered devices by groups (PIR's, GBD's, etc.) and I also group like partition zones together. Only variable is when this isn't possible, such as 2W fire or ZTS's and analog inputs.
 
Back
Top