In-built System IO : Security Armed Level Name

[Josh]

I am using a PAC to do the logic and have Cytech's Comfort alarm panel connected to CBUS.

Comfort has 4 alarm levels, that is OFF,Day,Night, and Away. When I tested GetStringIBSystemIO("Security Armed Level Name", armLevel) with the alarm panel in DAY mode, I got "disarmed" which is not entirely accurate, should this be the case? Or am I doing something wrong (again)?

[Josh]

I am using a PAC to do the logic and have Cytech's Comfort alarm panel connected to CBUS.

When I tested GetIntIBSystemIO("Security Armed Level") it returns 0, no matter what the current Alarm Level is. Is this function not PAC supported?

[NickD]

Both of the above make it sound like the PAC is not receiving the bus messages from the Comfort... can you see anything in, say the Application log of Toolkit, or the LOG in PICED when running this project?

Nick

[Josh]

Originally Posted by NickD

Both of the above make it sound like the PAC is not receiving the bus messages from the Comfort... can you see anything in, say the Application log of Toolkit, or the LOG in PICED when running this project?

I can see messages in Application 208 in both (Toolkit and PICED logs) and I use GetBoolIBSystemIO("Security Zone Secure",ZoneName) for motion controlled GAs and they behave as expected.

[NickD]

Can you extract and post the messages you see in the PICED log?
Specifically where it should be changing the armed mode.

Nick

[Josh]

Originally Posted by NickD

Can you extract and post the messages you see in the PICED log?
Specifically where it should be changing the armed mode.

Here is the extract disguised as code ....

09/02/2010 05:14:11 PM  C-Bus Rx : Ramp Comfort Zone Status, Scullery Movement Off over 4s
09/02/2010 05:14:25 PM  C-Bus Rx : Security Application : Zone 7 Sealed
09/02/2010 05:14:25 PM  C-Bus Rx : Ramp Comfort Zone Status, Patio Outside Doors Off over 4s
09/02/2010 05:14:27 PM  C-Bus Rx : Security Application : Zone 19 Unsealed
09/02/2010 05:14:27 PM  C-Bus Rx : Ramp Comfort Zone Status, Scullery Movement On over 4s
09/02/2010 05:14:36 PM  C-Bus Rx : Security Application : Exit delay started
09/02/2010 05:14:36 PM  C-Bus Rx : Security Application : Arm Ready
09/02/2010 05:14:39 PM  C-Bus Rx : Security Application : Zone 19 Sealed
09/02/2010 05:14:39 PM  C-Bus Rx : Ramp Comfort Zone Status, Scullery Movement Off over 4s
09/02/2010 05:14:40 PM  C-Bus Rx : Set AlarmSystemMode to Day Mode
09/02/2010 05:14:40 PM  C-Bus Rx : Security Application : System Arm State : Armed
09/02/2010 05:14:58 PM  C-Bus Rx : Set AlarmSystemMode to OFF Mode

Josh

[Ingo]

I see the same on my system. Running PICED 4.7.2 with the latest Comfort firmware on all components (UCM/CBus and Main firmware). Output in the log also shows system being armed correctly but the built-in system io variable stays on 0.

My workaround was to set a CBus group, from the Comfort side, to either On or Off depending on the Armed level. It uses 4 CBus groups but it works every time.

Ingo

[Josh]

Originally Posted by Ingo

My workaround was to set a CBus group, from the Comfort side, to either On or Off depending on the Armed level. It uses 4 CBus groups but it works every time.

Ingo,

I have a work-around, one GA (50 OFF, 100 DayMode, 150 Night Mode, 200 Away Mode, 250 Vacation) which Comfort setup at arming/disarming. I found out a couple days ago that with some power failures PACS initialises and the status of the GA is unknown (Zero/OFF), to which I had to setup another workaround, that is ask Comfort to set the GA again at PACS initialise which works, but I hate the fact that I am doing a work-around of a work-around, hence why am trying to get the right method working.

Maybe we have faulty units?

Josh

[NickD]

Hi Josh.

I don't think it's faulty units... I suspect it's more a case of the subtlties of how the security application works.

The "Armed Level" is actually the level that the slave device has requested, whereas the "Armed State" is what the master device (the panel) has actually done in response to this request.

Unfortunately the log doesn't give exact details of the messages, and who sent what..

Now that the protocols have all been made public, the latest version of the Diagnostic Utility (you can download it here) has more or less the same level of information as our internal tools, and shows and decodes the full message from the bus.

Could I trouble you to download it and post another log?

Nick

[Josh]

Originally Posted by NickD

Unfortunately the log doesn't give exact details of the messages, and who sent what..

Now that the protocols have all been made public, the latest version of the Diagnostic Utility (you can download it here) has more or less the same level of information as our internal tools, and shows and decodes the full message from the bus.

NickD,

I have CBus Diagnostic Utility v 2.0.0.0. Any settings I need to change or would the Basic Mode do?

Josh