| Posted: Friday Jan 10th, 2014 02:06 am |
|
1st Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
The firmware 7.047 beta changes are
Known Issues
- After updating Keypad LCD words using keys *1, Scanning of UCMs by Comfigurator will detect UCM #1 as HDL. This is an old bug
- RC01 Keypad buttons (0-9, *, #) cause the keypad to have a long beep, and are not able to work as keypad
- Sending SMS to Comfort with UCM/GSM will reply "Unknown command" if there is no control Menu Feedback, even though the control is performed correctly
Bugs Fixed
- Night Time Flag did not work. Night Time flag is set by Sunset and Cleared by Sunrise according to the Sunrise/Sunset times for each city
New Features- When system is being armed, the F key will cancel the arming, similar to the * key. Previously, the F key while arming produced a long beep
- New keypad keys supported in Comfort protocol. This is for support for new Wizcomfort software to be released
- User flags has been increased from 64 to 256 ie 0 to 255
Please download from http://www.cytech.biz/comfort_ultra_firmware.html?category_id=101 for those who are affected by the Night Time flag issue
Last edited on Friday Aug 29th, 2014 07:35 am by ident
|
| Posted: Saturday Jan 11th, 2014 05:08 am |
|
2nd Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
This is an explanation of the assignment of user flags to Night Time flag
Iif you assign, eg Flag 64 to Night Time Flag, then the Night time flag state is copied to Flag 64. By checking Flag64 you can know if it is Night, ie after sunset and before sunrise as set in Sunrise/Sunset Time
the ccommand F?nn in Comfigurator Monitor IO also returns the state of the flag
eg
> F?40 (40 is 64 in hexadecimal)
< F?4001 means Flag 64 on
<F?4000 means Flag 64 off
At sunset, the UCM will report
<FL4001
ie Flag 64 =1
At sunrise
<FL4000
is flag 64 = 0
The next Comfigurator 3.8 will have a setting for this flag assignment
In the meantime, go to Location 374 to assign a flag number to Night Flag
eg Location 374 = 64 assigns Flag 64 to Night Time flag
|
| Posted: Thursday Jan 16th, 2014 01:07 am |
|
3rd Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Ult 7.047 is now released
|
| Posted: Thursday Jan 16th, 2014 04:51 pm |
|
4th Post |
juwi_uk
Member
back to top
|
Interestingly I had installed the beta version via local file upgrade but today in Comfigurator even though I had "7.047" (beta) already installed it still wanted me to upgrade to "7.047" again. Are they different in some way as I'm sure I've never had this issue with Betas turning Live in the past?
|
| Posted: Friday Jan 17th, 2014 01:02 am |
|
5th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Comfigurator would not know if the installed version is beta or not
It should compare the firmware version with the latest on the server
I have not encountered that. Check for updates said "ULT 7.047 is the latest"
|
| Posted: Friday Jan 17th, 2014 07:34 am |
|
6th Post |
juwi_uk
Member
back to top
|
It definitely did it for sure. After starting Comfigurator and logging in I first upgraded my GSM4 firmware and the system rescanned as usual. I then clicked on the "Controller" node and it listed:- Comfort Version = 7.047
- Latest Version = 7.046
I did a Check for firmware updates and it brought up the dialog box asking me if i wanted to upgrade to 7.047! I downloaded and upgraded the firmware and all was well after that with future checks.
I don't particularly care as pretty minor but was strange observation so thought I'd feed back.
Julian
|
| Posted: Friday Jan 17th, 2014 07:37 am |
|
7th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
strange
Perhaps the internet connection was bad at that time, and the correct version info was not obtained in Comfigurator?
|
| Posted: Wednesday Feb 26th, 2014 04:43 pm |
|
8th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Bug in Firmware 7.047
- RC01 Keypad buttons (0-9, *, #) cause the keypad to have a long beep, and are not able to work as keypad
|
| Posted: Tuesday Mar 4th, 2014 03:02 am |
|
9th Post |
Home
Comfort Distributors
| Joined: | Wednesday Jul 12th, 2006 |
| Location: | United Kingdom |
| Posts: | 771 |
| Status: |
Offline
|
back to top
|
I have just been upgrading any units in our stores.
It does appear that by adding items at random and then scanning Comfigurator sometimes uses the values it already has its as though it does not refresh the screen.
So for example removing one UCM that had just been upgraded to 7.028 and then replacing it (same ID) with another older version UCM, comfigurator appeared to scan but still came up with 7.028.. I had to reset the main board and then re-scan
|
| Posted: Tuesday Mar 4th, 2014 04:27 pm |
|
10th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
Firmware 7.050 (Released) has the following changes;
Bugs
Actions Add counter, Add counter give wrong answer from 7.039
Bugs Fixed
- Fixed Bug RC01 Keypad digits 0 to 9,#, * causes long beep on keypad
New Features- Keypad Panic and Keypad fire will show in the Event Log with RS485 ID. Before, keypad fire and panic in event log had no id
- Timer action if timer value is 0, then timer count is taken from Last Action Value so the timer count can be loaded from a parameter like a counter
- Added Play new, Play saved and erase saved messages for user mode
Last edited on Wednesday Nov 2nd, 2016 04:16 pm by
|
| Posted: Tuesday Apr 22nd, 2014 04:22 pm |
|
11th Post |
srooks
UCM Pi Users
| Joined: | Tuesday Feb 26th, 2008 |
| Location: | |
| Posts: | 51 |
| Status: |
Offline
|
back to top
|
- Timer action if timer value is 0, then timer count is taken from Last Action Value so the timer count can be loaded from a parameter like a counter
What's the best way to convert a KT03 slider value (say with a minute scale) into a seconds value for a timer, using this new feature?
Thx,
|
| Posted: Tuesday Apr 22nd, 2014 05:19 pm |
|
12th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
A KT03 slider is mapped to a Counter
so you can program as follows, assuming counter 2
Get Counter Counter002
Do Response XXX After 0 Seconds Using Timer01
This will take the value from counter 2 which came from the slider and use it as the delay before the Response XXX
|
| Posted: Tuesday Apr 22nd, 2014 11:45 pm |
|
13th Post |
srooks
UCM Pi Users
| Joined: | Tuesday Feb 26th, 2008 |
| Location: | |
| Posts: | 51 |
| Status: |
Offline
|
back to top
|
What about scaling. What's the best way of converting a slider with a range of 1-10 into seconds (60 - 600)? A KT03 slider can only have values of 0 to 255.
Thanks!
|
| Posted: Wednesday Apr 23rd, 2014 11:30 am |
|
14th Post |
ident
Administrator
| Joined: | Wednesday Aug 9th, 2006 |
| Location: | Singapore |
| Posts: | 3493 |
| Status: |
Offline
|
back to top
|
You can use the Multiply action
eg
Get Counter Counter002
Multiply Immediate 60
Set Counter002
Do Responsex After 0 Seconds Using Timer01
counters have range of up to 65535
|
|
