Version 4.1.0 Piced & Application 208

[ident]

After reviewing the messages sent to Cbus when the system is armed, eg in the example below

17:10:23 Rx : 0512D0007A80011E<CR>
17:10:23 Rx : = Local Network, Source Unit 18, Security, Security: System Fully Armed

it appears that Comfort sends either a fully armed or disarmed message and does not send eg Away Mode, Night Mode, Day Mode etc
This has always been the case so the new Securirty system I/O in Piced should not have made any difference

It is possible for Comfort to send values (new firmware)
0512D0007A80011E<CR>
01 = Away Mode

0512D0007A80021D<CR>
02 = Night Mode

0512D0007A80031C<CR>
03 = Day Mode

0512D0007A80041B<CR>
04 = Vacation Mode

However we dont know if Piced will interpret this correctly as this is optional information. Does anyone have any knowledge of this?

[ident]

It is possible for Comfort to send values (new firmware)

0512D0007A80011E<CR>
01 = Away Mode

0512D0007A80021D<CR>
02 = Night Mode

0512D0007A80031C<CR>
03 = Day Mode

0512D0007A80041B<CR>
04 = Vacation Mode

You can test the  [color=\"#ff0000\"]beta [/color]firmware Cbus 5.203 which implements the above function and let us know if PiCed System I/O can determine the Security Mode, go to http://www.comfortforums.com/view_topic.php?id=1752&forum_id=85

[Ingo]

I had a quick look and it seems still not to work. Below is the output from my Diagnostic Utility. There is however a change in the output, it now states the system is armed in a \'special state\'

According to the Clipsal guys, the \"Arm System\" message is the key to get this working. Please check http://www.cbusforums.com/forums/showthread.php?t=3931&page=2 as well.


07:17:46  Rx : 0512D0000A92334A<CR>
07:17:46  Rx :  = Local Network, Source Unit 18, Security, Security: Arm Not Ready : Zone 51 Not Sealed
07:17:47  Rx : 0512D0000A8A3352<CR>
07:17:47  Rx :  = Local Network, Source Unit 18, Security, Security: Zone 51 Isolated
07:17:47  Rx : 0512D0000A8A3550<CR>
07:17:47  Rx :  = Local Network, Source Unit 18, Security, Security: Zone 53 Isolated
07:17:47  Rx : 0512D0000A8A364F<CR>
07:17:47  Rx :  = Local Network, Source Unit 18, Security, Security: Zone 54 Isolated
07:17:47  Rx : 0512D0000A8A374E<CR>
07:17:47  Rx :  = Local Network, Source Unit 18, Security, Security: Zone 55 Isolated
07:17:48  Rx : 0512D0000A92007D<CR>
07:17:48  Rx :  = Local Network, Source Unit 18, Security, Security: Arm Ready
07:17:48  Rx : 0512D00009818F<CR>
07:17:48  Rx :  = Local Network, Source Unit 18, Security, Security: Exit Delay Started
07:18:01  Rx : 0512D0007A80031C<CR>
07:18:01  Rx :  = Local Network, Source Unit 18, Security, Security: System Armed State special

[ident]

From what NickD in the CBus forum says and what we can see from the log, Comfort is giving the correct messages

07:18:01  Rx : 0512D0007A80031C<CR>
07:18:01  Rx :  = Local Network, Source Unit 18, Security, Security: System Armed State special


means that Comfort is armed to Day Mode (value 3)

The log is exactly what I had indicated for armed to Day Mode output in my earlier post
0512D0007A80031C<CR>
(03 = Day Mode )

It appears that Comfort was armed by keypad. If Comfort was armed by Piced to Day mode then it would know that the \"special mode\" is Day Mode

[Ingo]

I tend to disagree. Arming with Day Mode with whichever method shouldn\'t make a difference. To test this theory I armed my system using PICED, and using the system IO function \'Arm System to Day Mode\'. It had the exact same results as arming from the keypad. No indication on PICED of what level the system is armed at. It could be something on the PICED side as well but the first thing is that the Arm System *request*, as NickD refers, is not seen on the CBus side. Can we not include this message when Comfort arms from the keypad?

From the CBus forum: ....

This should still be treated by the PAC as \"Armed\".. in the absence of the \"Arm System\" message described earlier, it treats any arm code that\'s not equal to disarmed as an \"Armed\" state.

Another thing came to light by doing this test, when arming to Day Mode via PICED, it fails to arm if ANY of the zones are open. I wonder if there is a \'force-arm\' function in PICED that can be used, as far as I can tell there are none.

This puts us at a bit of a disadvantage, with ComfortClient, and any software that sends either the m! or M! command, you can choose to force-arm with open zones or not. Especially in Day Mode, I like to be at home, with some open zones and still have some protection. How would that be accomplished via PICED or is that another thread that needs to be started?

Ingo

[ident]

Nick is actually referring to the Arm System Command ($A2, followed by security mode = 01 for Away, 02 for Night, 03 for Day, 04 for Vacation mode) which is issued by a Cbus device to the security system to arm itself. It is not meant to be sent by the security system.
When Comfort is armed, it sends the System Armed status ($80, followed by armed mode) to Cbus

Issuing the command Arm to Day Mode from System IO should be sending the Arm System Command (or Request) to the Bus, otherwise Comfort would not know to arm the system to Day mode. Why the message is not seen is a question for Piced

[Ingo]

So am I correct in assuming that when Comfort is armed via the keypad, PICED will never know to what mode it was armed to?

As for the problem why PICED doesn\'t \'see\' it\'s own \"Arm System\" message, that\'s something Clipsal needs to look at.

[ident]

All Cbus devices should be able to know what mode Comfort is armed to regardless of whether it is armed by keypad or Ctouch. Comfort reports System armed to C-Bus with the security mode 1,2,3, or 4. It is a problem with C-Touch that it does not show Day Mode, Night Mode or Away mode according to the security mode reported


See our post in the Cbus Forum http://www.cbusforums.com/forums/showthr...#post29807