Comfort Firmware 5.195 to 5.199

[ident]

[size=\"3\"]NOTE: Version 5.199 replaces 5.195 Beta (See later post in this topic)

Version 5.195 (7 June 2010)[/size]
This firmware is a pre-release version, which means it has been tested by Cytech but is being made availablle for further user testing prior to release.

Vocabulary
Vocabulary version 31, minimum vocabulary 30
Actions

1. Allow the action \"Reminder message on Keypad and Door station\" to work on  UCM ID. Requires Comfigurator 3.2.1
2. Announce Zone Action  - fixed bug if a zone has no words assigned and the zone is restored, the zone number without \"OFF\" will be announced, so zone on and off are both announced, which sounds like a zone double trigger. Now zone restored  will announce \"OFF\"  (offword) only without zone number  Less confusing  than announcing zone number without off when restored.
3. Action Toggle Output fixed BUG - returned wrong value
4. Skip Announcement action 23 will prevent zone announcements on zone OFF and  ON responses,. Action 23 did not prevent action 1  from working

Vocabulary Upgrade Improvements

1. Improved Vocabulary Upgrade process so that Comfort only polls the UCM requesting the Vocabulary Upgrade so that other Modules cannot interfere with the process. Fixed problem when when a Slave is connected and addressed, the Vocabulary upgrade process may not start. Also eliminated occasional errors during Vocabulary Upgrade
2. During Vocabulary Upgrade, an error will report VP00NN where NN is a report code
3. Works best with UCM 5.212 which also improves the Vocabulary upgrade process but will improve vocab upgrade evenwith older UCMs. It is recommended to upgrade to 5.195 before doing any Vocab upgrade
   

Bug Fixes

1. Announce zone action  fixed bug if a zone has no words assigned and the zone is restored, the zone number without \"OFF\" will be announced, so zone on and off are both announced, which sounds like a zone double trigger. Now zone restored  will announce \"OFF\"  (offword) only without zone number  Less confusing  than announcing zone number without off when restored.
2. Action Toggle Output fixed BUG - returned wrong value
3. Fixed BUG CMS phone type was allowed to be entered in Phones 3 to 8
4. If multiple Trouble alarms exist, Comfort keeps the correct record and announcement of remaining troubles along with the parameter eg zone trouble, RS485 ID and user number for each
5. Fixed BUG endless loop if LCD data not found in any sector after vocab upgrade. System will hang and not start rs485 communications or reset system continuously
6. Fixed Bug Z? could  work for lem03
7. Fixed Bug where UCM query for user flags F? Invalid flag number returns reply of state 0 instead of no reply which caused Wizcomfort to be very slow when querying nomexistent flags
8. Fixed BUG clear answering machine bypass clear Call screening feature as well

UCM Support

1. Fixed Bug Z? could  work for lem03
2. UCM  C?NN Will reply 0 if counter number NN is invalid
3. Allow UCM u? to discover the modules connected to Comfort even if the modules are not selected in Modules and Settings, so Comfigurator can Scan for modules when the number of Modules is 0
4. Fixed Bug where UCM query for user flags F? Invalid flag number returns reply of state 0 instead of no reply which caused Wizcomfort to be very slow when querying nomexistent flags
5. Support keypad volume for UCMs
6. When Vocabulary Upgrade fails, UCM will report an error code in VP00NN

New Features

1. Virtual Input zone setting . Virtual Inputs are like disabled physical zones but can be triggered by KNX PIRs (future UCM/KNX feature). Requires Comfigurator 3.2.1
2. Improvements
3. When  showalarms box (for EN50131) in Modules & Settimgs > Configuration Flags is checked, doorbell and Reminder ring is heard on Keypads. These could not be heard on the keypads before.
4. F8 for Keypad to Keypad intercom can work When  showalarms box (for EN50131) in Modules & Settimgs > Configuration Flags is checked
5. Voice Protection (against Lost Voice)  when  Comfort supply voltage drops below a safe point. This stops all voice activity, until Comfort is reset - this was implemented in 5.194. Now an increase in supply voltage will automatically reset Comfort so its voice can be restored without  a manual reset.
6. Keypad announcements can be queued up for 3 announcements. This may have the effect of several announcements heard close together after arming or disarming.
7. When system is reset, ensure that keypads always get the correct status of leds, and do not miss out.
8. When system is reset, keypads will not miss complete or partial announcement of \"Security Off\"
9. Skip announce action 23 will prevent zone announcements on zone OFF and  ON responses,. Action 23 did not prevent action 1  from working
10. Supports new key F shortcut codes for message menus on the new KT03
11. If sensor register value is unchanged dont broadcast sensor command.
12. Change of date and time is now recorded  in the event log with user number. Before, the user number was not recorded.

Known Issues

1. When an LCD Keypad is removed from the Comfort bus, and  reconnected when there is a Trouble condition, the LCD display is blank while  the keypad LEDs show the correct status. The display is corrected when the Trouble alarm condition is cleared.
2. A wrong code or duress code on the Wizcomfort keypapd , or a UCM software application  emulating a keypad causes the UCM to log out
3. the u? or Scan command reports a KP, DP, RIO or SCS module which does not support the Identify command as not present
4. Invalid RS485 login is accepted
5. Portugal Ring Detection does not detect correct number of rings
6. When KP firmware 5.013 with old Atmel EEPROM is reset, the keypad does not get the correct vocabulary version
7. Duress Code logs out UCM
8. [img]file:///C:/DOCUME%7E1/LUYUNG%7E1/LOCALS%7E1/Temp/moz-screenshot.png[/img] When Keypad is removed from the Comfort bus, AND there is TROUBLE and  then reconnected, the LCD display is blank until Comfort is reset This is because Comfort broadcasts the LED status to KP but KP does not know the trouble condition so it is blank
9. U? From UCM - if ID is old type that does not reply to this query, then Comfort  does not reply to UCM u? Query so Scan of system with old modules will show no module.
   
   
   

[juwi_uk]

Hi

I seem to have discovered a problem with the u? command

u?41 and u?51 commands sent via the ComfortClient or via Comfigurator etc dont get a reply back from the UCM.

Other \"u\" commands seem to be fine;  just these 2 not responding.

Is this a bug?

u?41 is Keypad 1.

Julian

 

 

 

[juwi_uk]

OK this is incorrect,  it\'s not the UCM firmware but the Comfort firmware 5.195 that is causing the issue;  Ingo has tested it and confirmed by rolling back.

Unfortunately I cant change the Thread topic so maybe the website admin can for me.

Julian

 

[slychiu]

That is correct, it is a minor bug in 5.195

Before 5.195, the u? command used to return the firmware version only if the module was already programmed in Number of Modules in Comfigurator. Hence a Scan of Modules only found what was already configured in number of Modules

If the module is not present, u?NNFFFF was returned, where NN is the module ID
If the module is present but its firmware was too old to respond to the query, the reply was u?NN0000 ie all zeros

If the Comfort firmware is too old to support the u? query, there is no reply

In 5.195, this was changed so that u? would work even if the Module is present but not configued in modules and setings, so that a Scan of modules would show all modules connected to the system.

However, this caused modules whose firmware is older to not report for the u? command
Your KP and RIO firmware are the older type which do not respond with the firmware, instead of reporting 0000, has no reply

[Ingo]

Just to be clear: On 5.195 the Keypads stopped responding but they respond on 5.183. If you do a module scan it now shows you have NO keypads installed. On 5.183 it shows all the keypads but with \'unknown\' version due to the older keypad firmware.

I have also found another problem with 5.195. When using the Client to enter a Duress code, by sending KDxx commands, it is supposed to give a keypad beep and then wait for another duress code entry before the system is disarmed.

In the case of 5.195 it immediately logs the current user out and doesn\'t trigger the Duress condition. The system is also left in the armed state. On 5.183 the behaviour is correct. Below is the log entries we have.

2010/06/10 09:01:19,App,KD**,Key(0-9)
2010/06/10 09:01:19,Com,OK,OK Received
2010/06/10 09:01:19,App,KD**,Key(0-9)
2010/06/10 09:01:19,Com,OK,OK Received
2010/06/10 09:01:20,App,KD**,Key(0-9)
2010/06/10 09:01:20,Com,OK,OK Received
2010/06/10 09:01:20,App,KD**,Key(0-9)
2010/06/10 09:01:20,Com,OK,OK Received
2010/06/10 09:01:21,App,KD**,Key-Hash
2010/06/10 09:01:21,Com,OK,OK Received
2010/06/10 09:01:23,Com,LU00,User Logged Off
2010/06/10 09:01:23,Com,BP04,Long Beep (error)

Regards,
Ingo

[slychiu]

The effect  will be to show no keypads in the Scan results if the versions are too old. We are looking at a solution to thus, as well as your new finding, thanks

[slychiu]

The issues you highlighted wil  be fixed in the next version
Thanks for the feedback again

[juwi_uk]

Chiu,

What sort of timescales are you thinking for this next release?

Julian

 

[slychiu]

We should have a version for testing next week. The issues have been identified

[juwi_uk]

That\'s good.

I ran a scan from Comfigurator on my live system (that I upgraded to this firmware last weekend) and it doesnt find my Zwave UCM either.  That one definately used to show it\'s firmware version so I\'m a little perplexed as why this one has stopped reporting too.

My Smartfit card has too but that I guess is old enough to match your description of the issue with older cards.

Julian