| Posted: Saturday Sep 27th, 2014 06:37 am |
|
1st Post |
admin
Administrator
| Joined: | Saturday Mar 3rd, 2007 |
| Location: | Singapore |
| Posts: | 1200 |
| Status: |
Offline
|
back to top
|
Comfigurator 3.9.2 has been released
The changes from 3.8.10 are
Known Bugs
- Slave Low battery message in Comfigurator alert text field shows Door station ID instead of Slave ID
- Keypad Broadcast Enable action does not allow "All Keypads" to be specified in the action
- Cbus2 Configurator - it is possible to add groups beyond 254
- When upgrading UCM/ETH or UCM/USB firmware of the UCM which is directly connected to Comfigurator, and the upgrade is cancelled by pressing the Cancel button, the upgrade cannot be restarted due to errors. However if the upgrade is stopped due to other errors eg network time out or reply errors, the UCM upgrade can be restarted.
- In Velbus Response wizard, sending commands to VMB1RYNO, VMB4RYNO, VMB1DMI are incorrect.
Note that these bugs may not be due to 3.9.2, ie they were from previous versions
Bugs Fixed- Lutron commands for use in General and Universal UCM had error when more than 1 control Unit is specified
- In Cbus2 Configurator, Read Properties for Cbus did not show the correct value of Resend Sim Options
- Sound types Tone 1 and Tone 2 limits has been changed 151 to 2400 Hz
- When doing Firmware Upgrade of KT03 by UCM, the PC is prevented from going to sleep to allow the upgrade to complete
- Upgrading Firmware and Writing to KT03 via UCM/ETH03 used to have an error when the PC does to sleep due to the long duration of these operations to KT03. The PC is prevented from going to sleep in the new version
New Features- Graphical References for Responses
- Help has Link to App Conversion Utility for the Comfort iOS/android apps
- New Action 190 - wait for Timer (requires Comfort Firmware 7.063)
- New Action 156 - Keypad backlight on/off (requires Comfort Firmware 7.061)
The new features will be described in more detail next
Last edited on Saturday Oct 18th, 2014 12:40 pm by
|
| Posted: Saturday Sep 27th, 2014 06:56 am |
|
2nd Post |
admin
Administrator
| Joined: | Saturday Mar 3rd, 2007 |
| Location: | Singapore |
| Posts: | 1200 |
| Status: |
Offline
|
back to top
|
Graph References
Right Click on any Response and select "Graph References"
This opens a new window which shows the connections between the Responses and what triggered it as well as what other responses are activated by it
This helps to troubleshoot and debug the programming of Comfort
Cursor over a Node to see Tooltip
Double-click Response Node to make it the Target Response.
A Response node is shown with the lamp icon. Note that only a Response can be a target
Double Click the Target Response (in blue) to Edit the Response
Select a Response from the Responses page to change the Target Response
The boxes are colour coded as follows: the Target Response is in Blue, other Responses are in Green, and other events, ie not Responses like zones, time programs, outputs etc are in White. This helps to identify other Responses which can become the new target by double-clicking on it,
|
| Posted: Saturday Sep 27th, 2014 06:58 am |
|
3rd Post |
| Posted: Saturday Sep 27th, 2014 06:59 am |
|
4th Post |
admin
Administrator
| Joined: | Saturday Mar 3rd, 2007 |
| Location: | Singapore |
| Posts: | 1200 |
| Status: |
Offline
|
back to top
|
New Actions
Action 190 - Wait for Timer
eg, the following Response will switch on the Corridor Lights, wait 10 minutes, switch off the corridor Lights, switch on the Landing Lights, wait 5 minutes, then switch off the Landing Lights. This requires Comfort Firmware 7.063
Response example:
Do CorridorLightsOn
Wait 600 Seconds Using Timer01
Do CorridorLightsOff
Do LandingLightsOn
Wait 300 Seconds Using Timer01
Do LandingLightsOff
Before the new action was introduced, this sequence would require 3 Responses, ie
1st Response:
Do CorridorLightsOn
Do 2ndResponse after 600 Seconds Using Timer01
2ndResponse:
Do CorridorLightsOff
Do LandingLightsOn
Do 3rdResponse after 300 seconds Using Timer01
3rdResponse:
Do LandingLightsOff
Thus, this new action simplifies the programming of delays in Responses.
Note that the Wait for Timer action will not block any other Responses from working during the delay. For example a zone response will be activated if the zone is opened during any of the delays between the actions
Action 156 - Keypad Backlight On/Off
This requires Comfort Firmware 7.061
This turns on the backlight of any individual Keypad or all keypads. One use of this is to turn on the keypad backlight when motion is detected in the area at night, when lights are switched off
Last edited on Sunday Nov 23rd, 2014 10:57 am by
|
|
