don't know if this is weird

[v1rtu0s1ty]

More information I can share. I went to the status and look at the volts. All my sensors are running an average of 7.3. The disabled zones are around 13.3 something.

EDIT: I also measured each sensors at the end of the connection(in M1 and XIN) using my meter set at 200k. All sensors showed 2.2 which I guess corresponds to the 2.2k resistor I installed.

 

[Steve]

is there anything I need to jumper on the XIN card? It's terminated to the M1DBH and I have a terminator on the M1DBH.

Are you saying the XIN is attached to the DBH and the XIN has the terminator jumpered and the terminating plug is in the last slot in the DBH? Is the M1 jumpered (J3)? If the M1 itself is terminated and the DBH is terminated, then the XIN should not be. Only 2 terminations on the bus.

I don't recall anything that I did something in XIN. I used it as is when it came from the box. So, I don't think it's jumpered.

I have the RJ45 terminator on the DBH.
I have J3 jumpered in M1 too.

Ok, well I read that line "It's terminated to the M1DBH" as the XIN was terminated. On the XIN is Jumper J1, by default it is on position 1&2 which is what you want. 2&3 engages the terminator which you don't want.

 

[v1rtu0s1ty]

I just went there now and saw the 3 pins. It says NO and YES. I don't have any jumper there at all. Looks like I need to put a jumper in 1 & 2 for NO. Am I correct?

 

[v1rtu0s1ty]

Hi Steve,

I turned off the system. I placed the jumper in 1&2 which was previously empty. I turned on the system and the announcement for the sensors connected to the XIN got played again, but not the rules that are connected to the M1.

 

[BraveSirRobbin]

Hi Steve,

I turned off the system. I placed the jumper in 1&2 which was previously empty. I turned on the system and the announcement for the sensors connected to the XIN got played again, but not the rules that are connected to the M1.

I'm no expert on this, but I believe what you are seeing is the way the XIN inputs get scanned. When "any" zone on an XIN changes state to either a voltage "above" the upper threshold for an eol fault (I think it's something like 8) or a voltage "below" the lower threshold for an eol fault (I think is't something like 3) ALL inputs to the XIN will get scanned. If no zone changes state like this, then a scan of the XIN boards is initiated around every 30 seconds.

I think what is happening is that something is changing state on power up, and while the XIN is getting power, it's initiating a scan, thus causing the announcements.

The Elk main board zones don't get scanned like the XIN expansion boards. I can't explain the "why" your zones are changing state, only that I can explain "why" your XIN rules are getting triggered and not the main board's.

 

[v1rtu0s1ty]

Thanks BSR. Actually, Amy mimicked my setup and earlier and it wasn't happening on her setup. She asked me to export the account in the RP. I already sent to her the exported data. Hopefully, she will find something.

 

[v1rtu0s1ty]

Amy imported my configuration to their system and found the same issue. However, they told me that it is a known and reproducible condition. There is a work around though. This is what they sent to me.

WHENEVER SYSTEM START UP OCCURS
THEN TURN OUTPUT 100 ON (this can be any unused output)

Then modify your current rules adding the AND statement shown in bold.

WHENEVER Zone 17 (Zn 17) BECOMES NOT SECURE
AND OUTPUT 100 IS OFF
THEN ANNOUNCE Zone 17 (Zn 17)

 

[rfdesq]

Sounds like a firmware update is in order.

 

[v1rtu0s1ty]

ok folks, I tried out the rules that Amy gave to me and it worked. I turned OFF/ON M1G and I didn't hear the announcements anymore.

However, when I open a window that has a window contact, it doesn't execute the rule anymore. What I want is for M1 to execute the rule when a window becomes NOT SECURE in DISARM mode.

The rule that was previously working was

WHENEVER LivingRoom Window(Zone1) becomes NOT SECURE
Speak LivingRoom Window(Zone1)

However, with this rule, it won't prevent the system from saying all the rules during bootup.

 

[v1rtu0s1ty]

Thanks David for the fix.

You should add duration of 7 seconds so that it turns it back off.

This did it:

WHENEVER SYSTEM START UP OCCURS
THEN TURN OUTPUT 100 ON FOR 7 SECONDS