Comfort Security System

I have Comfort handling security and CBUS handling lights.
All works well,I have a CBUS PAC that I use to monitor movement in the house, alarms status and so on.

Currently the logic to do that takes a lot of resources because I monitor a lot of GA (about 20) in Application 1 (Comfort changes GA in App when a zone is unsealed). So I have about 20 "once" statements that does fancy stuff if movement is detected. This works well, but takes a lot of resources from the PAC, and if other activities are activated or a scene with a lot of GA is activated, the unit crashes.



I am trying to find an easier way of checking if there is any movement (unsealed zones), then monitor the GA's and I would like to stop the monitoring module immediately when the zones have been sealed. This way the resources will only be used when there is actual movement rather than all the time.

I have tried using “Zone Not Ready” in the Security Application, but that tells me which GA is unsealed, and does not change back to a meaning full value like zero when all zones are sealed. So it shows when there is an open door or movement, but does not indicate when there is no movement or open door. In other words, it indicates the start of the process, but I have no way of detecting the end of the process.


What makes this difficult is the fact that Toolkit does not show security application messages, so I cannot see which activities are fired from Comfort, and what sequence they are fired to figure out what the best way of doing this will be.

Any ideas guys?

 

The Diagnostic Utility is your friend.

http://www2.clipsal.com/cis/technical/downloads/commissioning_tools#Diagnosticutility

 

I have version 1.4, and it did not show GA as they change in security (not all of them). Has this changed in the new version?

 

Sorry Duncan, I was not looking at the right places. What I have noted as well is tht I had the new version as well, it was just installed in another directory "Diagmostic Utility", where else the old version was installed in "CBus Diagnostic".

But yes, the tool shows all messages.

And I was able to change the logic to only check all conditions only when a zone is unsealed, which might be movement or door open and stop once the zone is sealed again (no movement and door closed). This has reduced resouces used by the PAC by a big margin.

 

GA's ON

PICED now supports scenes in LOGIC.... this means that as well as using your scenes as a marco for output levels.... you can have scenes that are used to monitor GA levels. you create the scene the exact same way...

the difference being that logic now allows you to code to the "scenes current level" itself.

example being

20 once statements , etc etc etc .......

as opposed to alternative of

putting the 20 "monitored" GA's into a "scene_monitored" then using the logic or statement wizard to write whichever of the following combinations you require instead of many once statements.

once (GetSceneMinLevel("scene_monitored") > 0%) { All Groups On ? } then
begin
SetLightingState("Group 26", OFF);
end;

once (GetSceneMaxLevel("scene_monitored") = 0%) { All Groups Off ? } then
begin
SetLightingState("Group 26", OFF);
end;

once (GetSceneMaxLevel("scene_monitored") > 0%) { Any Groups On ? } then
begin
SetLightingState("Group 26", OFF);
end;

once (GetSceneMinLevel("scene_monitored") = 0%) { Any Groups Off ? } then
begin
SetLightingState("Group 26", OFF);
end;

 

Thanks Coppo,

I have looked at GetSceneMaxLevel, and I have not considered using that in this case. Interesting, very insteresting. I can see a lot of other Interesting uses.

Thanks again.