Reply To: Setting Counter Causes System Reset

M1 Support Forum Setting Counter Causes System Reset Reply To: Setting Counter Causes System Reset

#5106
Jeff

Also tried:

WHENEVER NoMotion_B (Counter 10) CHANGES TO A VALUE LESS THAN 1

THEN SET TestCntr (Counter 12) TO 60

The reason I did this, is becuase I have a similar rule elsewhere that works just fine?!? Thought maybe the set-to value might be the issue. Still, it cause the Elk to reset.

Here’s the other weird thing: Even if I don’t change the programming, when I connect or do a “check for conflicts” ElkRP reports there are conflicts in the Rules & Texts. There nothing in the Texts. If Select All, and Send checked items to system it behaves as expected. But, on re-connection, ElkRP reports a conflict Rules & Texts (even though there were no changes. “View Difference for selected Items” reports “[Selected Item] cannot be compared.”

I then tried to Receive All, but that scrambled my new rules with some old rules that I had deleted. Cleared all rules and counters, Sent All. Then, Sent All from a back-up of my account but that results in same issues above.

 

 

Scroll to Top