Elk M1G Odd Problem

[apostolakisl]

So it has been several days now and here is what I have found. First off, no more random arming of the alarm or opening of garage doors. But here is something I can't explain. I set the system to email me when the counter goes to zero. I would expect to get one email, but every time I initiate the rule, I get either one, two, or even three emails reporting that the counter went to zero. Typically the emails come 2 minutes apart. What the heck?

 

[fcwilt]

So it has been several days now and here is what I have found. First off, no more random arming of the alarm or opening of garage doors. But here is something I can't explain. I set the system to email me when the counter goes to zero. I would expect to get one email, but every time I initiate the rule, I get either one, two, or even three emails reporting that the counter went to zero. Typically the emails come 2 minutes apart. What the heck?

I cannot tell you what is happening but I did have a vague memory of having problems with counters and 0. Perhaps you have found the problem, multiple triggers when reaching 0.

How about creating a test rule that emails on 1 rather then 0? Then you will know if it is an issue with emailing or counting to 0.

 

[signal15]

When you turn the output on at 1 to trip the garage door, it turns on for a second or so, then off. Create a rule that says when that output turns off, to send the email.

 

[apostolakisl]

OK I got some answers on this from elk.

The counters do cycle. They do not quit at zero, they go to 65535 and continue to count down and after about 18 hours hit zero again (if the counter was set to subract one per second). You should put a line in that says "and the counter is not zero then subtract one" Then the counter will count down to zero and stop until the next time it gets triggered.

I am sure this is how those random events were happening.

 

[fcwilt]

OK I got some answers on this from elk.

The counters do cycle. They do not quit at zero, they go to 65535 and continue to count down and after about 18 hours hit zero again (if the counter was set to subract one per second). You should put a line in that says "and the counter is not zero then subtract one" Then the counter will count down to zero and stop until the next time it gets triggered.

I am sure this is how those random events were happening.

Good to know - thanks for the posting.