Posted: Monday Jun 7th, 2010 02:07 pm |
|
1st Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
NOTE: Version 5.199 replaces 5.195 Beta (See later post in this topic)
Version 5.195 (7 June 2010)
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- Allow the action "Reminder message on Keypad and Door station" to work on UCM ID. Requires Comfigurator 3.2.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.
- Action Toggle Output fixed BUG - returned wrong value
- 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- 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
- During Vocabulary Upgrade, an error will report VP00NN where NN is a report code
- 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- 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.
- Action Toggle Output fixed BUG - returned wrong value
- Fixed BUG CMS phone type was allowed to be entered in Phones 3 to 8
- 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
- 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
- Fixed Bug Z? could work for lem03
- 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
- Fixed BUG clear answering machine bypass clear Call screening feature as well
UCM Support- Fixed Bug Z? could work for lem03
- UCM C?NN Will reply 0 if counter number NN is invalid
- 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
- 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
- Support keypad volume for UCMs
- When Vocabulary Upgrade fails, UCM will report an error code in VP00NN
New Features
- 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
- Improvements
- 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.
- F8 for Keypad to Keypad intercom can work When showalarms box (for EN50131) in Modules & Settimgs > Configuration Flags is checked
- 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.
- Keypad announcements can be queued up for 3 announcements. This may have the effect of several announcements heard close together after arming or disarming.
- When system is reset, ensure that keypads always get the correct status of leds, and do not miss out.
- When system is reset, keypads will not miss complete or partial announcement of "Security Off"
- Skip announce action 23 will prevent zone announcements on zone OFF and ON responses,. Action 23 did not prevent action 1 from working
- Supports new key F shortcut codes for message menus on the new KT03
- If sensor register value is unchanged dont broadcast sensor command.
- Change of date and time is now recorded in the event log with user number. Before, the user number was not recorded.
Known Issues- 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.
- A wrong code or duress code on the Wizcomfort keypapd , or a UCM software application emulating a keypad causes the UCM to log out
- the u? or Scan command reports a KP, DP, RIO or SCS module which does not support the Identify command as not present
- Invalid RS485 login is accepted
- Portugal Ring Detection does not detect correct number of rings
- When KP firmware 5.013 with old Atmel EEPROM is reset, the keypad does not get the correct vocabulary version
- Duress Code logs out UCM
- 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
- 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.
Last edited on Tuesday Jul 6th, 2010 04:42 am by
|
Posted: Wednesday Jun 9th, 2010 06:34 pm |
|
2nd Post |
juwi_uk
Member
back to top
|
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
|
Posted: Wednesday Jun 9th, 2010 06:54 pm |
|
3rd Post |
juwi_uk
Member
back to top
|
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
Last edited on Saturday Jun 12th, 2010 07:32 am by juwi_uk
|
Posted: Thursday Jun 10th, 2010 03:46 am |
|
4th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
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
|
Posted: Thursday Jun 10th, 2010 07:22 am |
|
5th Post |
Ingo
UCM Pi Users
Joined: | Sunday Jan 21st, 2007 |
Location: | South Africa |
Posts: | 557 |
Status: |
Offline
|
back to top
|
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
|
Posted: Thursday Jun 10th, 2010 08:22 am |
|
6th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
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
|
Posted: Friday Jun 11th, 2010 07:57 am |
|
7th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
The issues you highlighted wil be fixed in the next version
Thanks for the feedback again
|
Posted: Friday Jun 11th, 2010 08:10 am |
|
8th Post |
juwi_uk
Member
back to top
|
Chiu,
What sort of timescales are you thinking for this next release?
Julian
|
Posted: Friday Jun 11th, 2010 08:21 am |
|
9th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
We should have a version for testing next week. The issues have been identified
|
Posted: Friday Jun 11th, 2010 08:16 pm |
|
10th Post |
juwi_uk
Member
back to top
|
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
Last edited on Friday Jun 11th, 2010 08:18 pm by juwi_uk
|
Posted: Saturday Jun 12th, 2010 03:29 am |
|
11th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
Does the scan consistently fail to see the UCM/Zwave? What version is the UCM/Zwave?
|
Posted: Saturday Jun 12th, 2010 07:29 am |
|
12th Post |
juwi_uk
Member
back to top
|
Yep it consistently fails. Appears that u?12 and u?13 are not responding which are my Zwave and Smartfit UCM's respectively. The zwave UCM is flashed to the current (latest) firmware.
> LI****
> UL000003
> V?
> v?
> U?
> u?11
> u?12
> u?13
> u?14
> u?15
> u?16
> u?17
> u?18
> LI
< LU01
< LR0111
< DL00000305FF22D7
< V?FE05C322200100
< v?05FF1E010103FFFF
< U?0A05D411
< u?110A05D4
< u?14FFFFFF
< u?15FFFFFF
< u?16FFFFFF
< u?17FFFFFF
< u?18FFFFFF
< LU00
Last edited on Saturday Jun 12th, 2010 07:30 am by juwi_uk
|
Posted: Saturday Jun 12th, 2010 05:09 pm |
|
13th Post |
juwi_uk
Member
back to top
|
Chiu,
It didnt find the new GSM/UCM I've just purchased either. Surely that should have the latest firmware and be found. Says 5.163 on the flash chip.
Julian
|
Posted: Saturday Jun 12th, 2010 06:04 pm |
|
14th Post |
juwi_uk
Member
back to top
|
Sorry, my mistake it did find the UCM/GSM it just didnt set the version.
|
Posted: Sunday Jun 13th, 2010 05:45 am |
|
15th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
The UCM firmware required to report the firmware version is 5.168, so as your UCM/GSM is 5.163 it will report 0000
We shall shortly be releasing updated firmware to all ucm types which will be abble to report the firmware version
|
Posted: Tuesday Jul 6th, 2010 04:41 am |
|
16th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
ULT 5.199 fixes the bugs found in the beta version 5.195 in this thread
Changes
- Allow delay of 300 ms after any reset command on Rs485 bus to allow modules to be reset and wake up.
- Fixed Portugal Answering number of rings problem after 5.173 caused problem
- Fixed BUG for invalid login accepted by RS485 in 5.186 (Firmware Not Released)
- Fix bug where u? query id whose firmware does not support this query. CM does not reply to UCM. when null reply received , reply to querying id 0000 if id exists Tested on old KP and DP which dont support 7DH command. They do NOT reply at all to 7DH or to any commands they dont recognise instead of replying with NULL message.
- Fixed Bug from 5.195 UCM Keypad eg Wizcomfort wrong code or Duress code entered, it logged out UCM
- Fixed Bug from 5.195 when KP comes on line when there is trouble , LCD is blank until trouble condition changes
- Implement received unknown command reply for for module ids which do not recognise command, to handle new commands which are not suported bny modules with older firmware
Known Issues- If a trouble condition occurs followed by 2nd trouble condition, then the 2nd trouble is cleared, when sign in the 2nd trouble condition is still announced until both troubles are cleared. From 5.188
- SCS 9 to 15 temperature could not be reported (old problem)
Attachment: ULT5_199.zip (Downloaded 13 times) Last edited on Tuesday Aug 24th, 2010 02:57 am by slychiu
|
Posted: Sunday Jul 25th, 2010 08:28 am |
|
17th Post |
juwi_uk
Member
back to top
|
I've noticed that point 2. in the New Features section of the fix list at the start of this thread just says "improvements"; in what though?
|
Posted: Sunday Jul 25th, 2010 02:08 pm |
|
18th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
Not sure, cant have been important
I think these have been described in later 5.199
|
|