Comfort Firmware 7.040

[ident]

Comfort Ultra 2 firmware 7.040 has been released
Instructions for upgrading Comfort Firmware can be found at http://www.comfortforums.com/forum92/3400.html

The changes from 7.032 are
Known Bugs

1. Record Greeting Message [b]by voice menu does not work
   [/b]
2. Keypad hardkeys message does not work
3. Actions Add counter, Add counter give wrong answer from 7.039

Actions

1. added action 73,31 get gsm network strength  get_gsmnetworkstrength
2. Add action 189 for blinds cntrol
3. Added action 155 to send customised messages to UCM/GSM4
4. Added action 73,31 get gsm network strength 0 to 4 to allow program to check network strength
5. Fixed bug action 73,30 get  last security mode did not work

GSM

1. Comfort scanning of UCM can know if UCM has EEPROM. This allows Comfort to know if GSM4 has eeprom installed so GSM4 can be treated as old GSM
2. GSM  for SMS control menu command, delay 4 seconds before replying with status to alow status to be updated in case of slow updates eg Zwave
3. Support Phone Permits for each phone index used by UCM/GSM
4. For gsm if sms command not permitted, reply \"not permitted\" to verified phone by sms
5. Record sms receive in event log when SMS command from UCM/GSM is arm or disarm, not when caller id verified
6. For GSM fixed  bug - reset when  control group > 6
7. For GSM  \"Invalid Command\" reply to gsm not gsm4
8. UCM/GSM alarm sms messages removed the alarm number before the alarm name (except for SPC firmware where this is needed for UCM/CMS)
9. Send Time-stamp (24 hours format) to UCM/GSM SMS before alarm message
10. For UCM/GSM when user sends SMS command to  GSM, when sms caller id accepted, add to event log \"SMS Phone N OK\" Requires myma37 (or kate37). Requuires sentence upgrade only as no new words were added
11. For UCM/GSM if arm and disarm command is received by SMS, will reply state of security mode (security off, away mmode, night mode, day mode, vacation mode).  If the system is already in the same security mode, the reply will send the current security mode also.
12. Added action 155 to send customised messages to UCM/GSM4

Zwave

1. Support UCM/Zwave3 polling  when needed by GSM and control menu and CM command from App, not from KT03 yet
2. Support UCM/Zwave polling Zwave nodes enable/disable, when control menu or app requires zwave status, end polling of Zwave when exit from control menu or keypad or phone menu

Bugs Fixed

1. Fixed BUG from 7.031 when disarm during tamper active, causes low battery report instead of tamper trouble report
2. Voice menu for Select  Phone 2 for CMS was not heard - This is an old bug
3. Action 74 and 141 fixed bug in OPT, SPC and CODE (from 26/1/13) 7.010 Do Response does not return to do next action.Bug did not affect Ultra firmware
4. Fix BUG for CMS user number reporting for user numbers > 128 eg KP=240 were not reported correct. Arm by Keypad  number  240 is  reported wrongly  as user 0B2 to CMS
5. Fixed BUG from 6/2/12 action 149, 0, constant did not work
6. Fixed Bug Vocab upgrade failed at Sentence Upgrade. Repeat Sentence Upgrade will work. Now sentence upgrade after vocab completed will halt for refresh but will continue
7. Fix BUG when module lost comms but not lost power (by disconnect KAKB and not 12V) and is connected again so id becomes good, comms is restored by the module does not report its id information so u? reports FFFFFF and comfigurator has status still as \"not found\" for the module that has recovered.
8. Fixed BUG  from 6.020   reminder enable for reminders 9 to 16 same as Reminder enable 1 to 8 and Time Program enables for 9 to 16 same as 1 to 8
9. fixed BUG from 6.020 erase_eeprom did not work. UCM erase eeprom on Comfort by pressing download button did not  erase whole eeprom
10. Fix Bug If ucm is  zwave ie replaced with another ucm without reset of comfort, Comfort thinks the UCM is still zwave
11. Fix BUG voice menu control group select wrong group cause jump to wrong menu!
12. Fixed bug when zone from on > trouble > Off does not report zone off. Cause problem in soft EOL for no EOL setting
13. Fixed bug action 73,30 get  last security mode did not work

Functions

1. Functions are supported in Comfigurator 3.7.x
2. Implement function Thermostat
3. Implement function Blinds

BS8243 (UK Alarm)

1. Implemented Status > Outputs for BS8243 including Confirmed and Unconfirmed alarms, Panic, Inhibit, Set/Unset, Tamper. These assigned outputs are automaticallly turned on and off according to BS8243 for use in Redcare monitored systems
2. Implemented notification delay (30 seconds ) and deviation from entry path requirements of BS8243 - 2010
3. Disabled flashing of RED/GREEN OUTPUTS in status > Outputs when there is trouble or alarm to reduce output commands on the Comfort Bus
4. For BS8243 security outputs, disarm  clears tamper alarm output when all tampers cleared, instead of when tamper input  is restored  . This means that if SEM has comms failure when armed cause tamper alarm, and is restored, disarm will clear the tamper

Security/Alarm

1. Keypad buttons - if arm keys are pressed, end menu
2. If keypad disarns system during alarm, dont go to user menu, say thank you goodbye, dont play  alarm history after disarm. only play alarm history if in alarm.  Alarm history confusing to (some) users
3. Tamper alarm if security is off, the external SIREN is not turned on  EN50131-1 Table 7 does not permit Tamper to sound external bellbox if system is not armed
4. If ignore line cut is enabled, and line cut is detected, set  LOCAL relay  so local phone can access. No need to set Nondetector alarm for Line Cut =0. Before if doorbell used when no phone line , must NOT ignore line cut so local phone can be used. To prevent alarm set nondetector alarm = 0. Now can ignore linecut and use local phone
5. Implemented Soft EOL, Triple EOL settings for zones. Need Comfigurator 3.7.5 and above

General Improvements

1. Implemented Serial Number function for Comfort and other UCMs with firmware 7.020 and above
2. Implemented compare of  IVS info in flash memory and in DSP so that KP * 1 willl not start if the compare is wrong and keep repeating if IVS or flash is corrupted
3. Flags and Counters are nonvolatile ie when reset will not be cleared to 0
4. Improvements in firmware upgrade
5. Changed operation for u? Will get id type, firmware and revision from its own memory instead of polling the ID unless the ID is not polled or has comms failure. Fixed bug where pollling for zwave id returns 00000 which means UCM is not a  zwave id
6. Change cold start date to 29/8/2013

[mikegriff]

Where you say
Flags and Counters are nonvolatile ie when reset will not be cleared to 0

if a counter is on 64
Then it sets it to 255
i.e.
=0 = 0
>0 = 255

Is this intentional?

I would prefer it was left at 64

Mike

[ident]

The counter should stay at the value it had before reset, it should not change to 255
Please verify this

[mikegriff]

I will check tomorrow for you
But if I restart/ reboot the main CPU the counters I had which were over >0 are all set to 255

I can tell this because I have a nice brand new KT03 on my desk.
As I am program it, I am often reloading a new Config file to comfort.
I see my home screen on the KT03 showing 4 counters which are set at 64, 16, 2 ,1
all of these as Comfort reboots change to 255

Mike

[mikegriff]

Or is it just on my KT03 the Counters are changed?
I will check tomorrow
Mike

[mikegriff]

Definitely the counters are set to 255 if they are not 0 in the main unit, which the KY03 obviously follows.
It happens after
the reboot
after security off message
then there is a beep and the counters set to 255
Hope this helps
Mike

[ident]

Please note  the bugs found in 7.040
Known Bugs

1. Record Greeting Message does not work
2. Keypad hardkeys messages do not work. this may affect KNX and other 3rd party systems that send Keypad keys to Comfort
   

[ident]

if a counter is on 64 Then it sets it to 255 i.e. =0 = 0 >0 = 255

There is nothing that changes the Counter to 255 at reset

What are the counters mapped to, Cbus? If so then the Cbus is setting the counters to 255 when the UCM/CBus initialised. Cbus sends it on/off state to counters when it initialises


Test by setting a counter which is not assigned to Cbus group address
The Events > Counters page has a Show status button that will show the value of any counter

[mikegriff]

Hi ident
I don\'t understand your logic
(please note this does not mean I disagree\'
I honestly don\'t understand the logic)

Cbus on this counter is either
0
64
128
192
there is no logic to set it to 255
i.e. it is never set to on by cbus

I have assumed that the 255 only comes from Comfort via the KT03

When you say Mapped do you mean a counter address that doesn\'t have an active cbus unit on that address
There is no technical mapping
Call cbus addresses alter all counters

I will check more for you tomorrow
Mike

[ident]

At reset the reply to  Status request to Cbus gives a status of  0 or 255 for all group addresses which are present. This status reply is only capable of giving off or ON status
Hence if the state of the cbus is 64 or 128 then the status becomes 255

It is not due to KT03