+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Support (https://www.comfortforums.com/forum-2.html)
+--- Forum: Problems & Troubleshooting (https://www.comfortforums.com/forum-36.html)
+--- Thread: Corrupted config - cannot add new logic without Comfort going crazy (/thread-1868.html)
- palmlodge - 06-05-2010
I\'ve got a config I want to make some changes to , but whatever I do it doesnt function when uploaded
When I initiate certain responses, Comfort can go crazy (beeps, alerts, comms error) or resets itself saying \"security off\".
If I go back to my 020610 config (from a few days ago) all is well. I\'ve tried Comfigurator v2 and v3 but both give me problems when I update, I\'ve only added a few simple responses that trigger RIO outputs.
Can I send my configs to Cytech for you to take a look at them to figure out if and why there is corruption ? This is holding me up introducing some major new logic.
Thanks
- slychiu - 06-06-2010
Yes, please send to support@cytech.biz
- palmlodge - 06-06-2010
Done.
I\'ve tried pulliing all power to comfort (not just a reset).
When triggering the new responses, mostly it will reset itself and not actually perform the response (which triggers outputs on the RIO). I can see no relay activity to which they are connected to - but works in the previous config (which had a small test response setup)
- ident - 06-07-2010
Palmlodge
Your config of 5 June, 050610a.ccl has Responses that cause endless loops
eg
BBSB-Cleardown calls BBSB-1-OFF which calls BBSB-Cleardown
The Responses call each other and the stack overflows, resulting in unpredictable behaviour, eventually in system reset.
Be careful about Responses which call themselves in the chain, just like in high level languages
Luckily you are able to transfer a new config. If the offending response gets activated after reset eg by a zone Response when the zone is ON, then the system will keep on resetting endlessly without giving you the opportunity to write a new config
- palmlodge - 06-07-2010
Well, that was monumentally stupid of me. BBSB-Cleardown should have called BBSB-OFF not BBSB-1-OFF
Thanks ;-)