Phantom rule

[cheekymonkey]

Phantom rule or ghost within the m1?
 
Got a strange situation and was wondering if anyone had struck it or had a solution to fixing it.
 
A long time ago I ran the power for my M1EXP via a relay on an M1RB and wrote some rules to operate the output so the n/c connections would open for 10 sec then close them.
 
Later on I discovered what was causing my problems so I disabled the rule.  The panel has been upgraded a couple of times and somewhere along the way the rules disappeared so I assumed I'd deleted them.  I recently tried to use the particular output in my watering setup but whenever the output is activated it only operates for 10 sec then deactivates.  
 
I've search through the rules but cant find any mention of the output other than the one I typed, I've backed up the config and the factory reset the panel before restoring the config only to see the erroneous operation return.  I've removed the output from my watering rules and when I activate it via the web interface it activates for 10 sec.
 
With 56% of my rule space used I'm loathed to have to reset the panel re enter the config manually.
 
I'd love to be able to examine the mdb file but it seems to be protected, any help or ideas would be welcomed.

 

[Del91574]

Have you pulled a fresh copy of the panel in and not write it to the DB you already have?
 
If you keep pulling it in on top of your existing DB, you might have some options checked in RP that either ignore, receive or delete the item, depending on the radio box originally checked.
 
That would be my first item to look into, then the next would be to close and export the entire DB file from RP altogether (for all accounts in your RP) and blow RP completely out of the PC and reload. From that point you can resync the DB files, but after you pull a fresh copy of the system in to see if it exists in the DB file you have in RP or the panel's DB itself.
 
Possibly lay in a blank DB and then test the output, then lay in your DB.
 
From that point, if all that fails, I don't see a clear cut option to run a repair if the DB may be corrupted, so a call to Brad and the guys might be in order.

 

[cheekymonkey]

Thanks for your ideas, they are some things I hadn't thought of.
 
Creating a fresh account and re-importing the the M1 config didnt show any diff.
 
Creating a fresh account in another DB I had then reimporting then re-sending didnt help
 
Creating a fresh account with only a user and the access code in it then sending it to the M1 restored the output functionality to what is expected, damn.

I am only a home user and thought since the rearrangements of their web site Elk would only respond to dealers and installers.

 

[Del91574]

Keep the DB section of RP and then blow it out and reinstall, might be worth a shot....eliminates a RP issue and means the DB might have corruption or there's a buried rule somewhere.
 
You close the DB and then export to removable media, then import it. Make sure you have the PW for the DB.

 

[cheekymonkey]

Finally managed to find some time and nut this out.  Ended up loading a blank account into the M1 and slowly adding various parts of the config until I notice the issue re-occur.
 
Turns out the problem was in the "Globals" G29-G42 (Special) tab.  Somehow "Two-Way Listen-in Enable" was selected, I don't have a M1TWA so would have never selected it, interestingly the warning that is displayed mentions outputs 7,8,9 & 10 and my problem was with output 10 , yet I did also have something on output 9 and it worked fine.
 
Thanks for your hints and tips