Comfort Home Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

UCM/Cbus2
 Moderated by: admin Page:    1  2  Next Page Last Page  
 New Topic   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Saturday Apr 5th, 2014 07:39 am
   
1st Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Cytech have developed a much improved version of the Cbus interface, called the UCM/Cbus2.

The manual can be downloaded from http://www.cytech.biz/ucmcbus2_manual.html

The new Comfort to C-Bus page on the website is here
http://www.cytech.biz/brochure/comfort-to-c-bus.html

The main changes are described here

UCM/Cbus2 Hardware


The UCM/CBUS2 is similar to recently produced UCM/CBUS hardware. It has a U2 EEPROM and the CBUS SIM Module is the ST7 version as shown in the photo above
Upgrading of old UCM/Cbus to UCM/CBUS2 is described later

Minimum Requirements
  1. Comfort firmware Version 7.xxx
  2. UCM/USB or ETH firmware version 7.xxx
  3. UCM/CBus2 Firmware 7.042 (Beta)
  4. Comfigurator 3.8.5 or above. Download from http://www.cytech.biz/comfigurator.html
New Features
  1. C-Bus lighting group addresses are not automatically mapped to the Counter numbers. Instead they can be mapped to Comfort Counters, Flags, Outputs,  and Virtual Inputs via Comfigurator. This enhances communications between C-Bus and Comfort. Virtual Inputs allow C-Bus motion sensors to act as alarm inputs. Mapping to Outputs allows Comfort Outputs to be controlled by Cbus. Mapping to Flags allows Comfort Flags to control Cbus. Flags can also link to other Comfort functions like Thermostats and Blinds.
  2. Comfort Physical Inputs can be mapped to Cbus Lighting Group Addresses. This allows Comfort Input status to provide feedback to Cbus Lighting groups, eg for Airconditioner and appliance status from Current sensors.
  3. The Group addresses can be imported from a.cbz file (which is an export file from the C-Bus Toolkit) making it easy to map to Comfort
  4. Trigger, Enable, Measurement Applications are also supported. Each of these applications can be mapped to appropriate Comfort registers.
  5. Built-in C-Bus Applications Security, Date/Time, and Zones can be enabled or disabled. Built-in applications are supported in Comfort without having to do any programming.
  6. The C-Bus Properties like SIM Firmware version, Cbus Network voltage, and SIM Options can be read from the UCM/CBus
  7. The Status Bar in Comfigurator shows the C-Bus status, eg Normal, C-bus not connected, EEPROM not installed, SIM Firmware too old, instead of having to see the UCM/Cbus LEDs
  8. Monitor Mode shows incoming traffic from C-Bus
  9. The Response Wizard creates actions to send to Cbus Lighting, Enable, Trigger Applications.

Last edited on Tuesday Dec 12th, 2017 05:56 am by



 Posted: Saturday Apr 5th, 2014 08:48 am
   
2nd Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Upgrading from UCM/Cbus1

It is possible to Upgrade to UCM/CBUS2 from the UCM/Cbus1 under the following conditions;
  1. The SIM Module is the ST7 version as shown in the above post. The older non-ST7 photo is shown below. if the SIM Module is the older type, a CBUS01 submodule can be purchased from Cytech or distributors.
  2. The U2 socket requires an  EEPROM for Cbus parameters. UCM/CBUS1 does NOT have an EEPROM as it is not required for UCM/CBUS1. A Microchip 24LC256 EEPROM can be purchased and inserted into the socket (with power off). If there is no U2 socket, then it is not uogradable and a new UCM/CBUS2 is required - DO NOT try to solder an IC socket or EEPROM into PCB, as this requires special soldering tools. Any attempt will probably damage the PCB as the IC holes are filled with solder
  3. If the UCM/Cbus has non-flashable firmware ie CBUS firmware < 5.100 then it is not upgradable. A new UCM/Cbus2 is required

The below photo shows the old non-ST7 SIM Module which is not suitable for UCM/CBUS2. A new CBUS01 module must be purchased

In the photo, the U2 socket is not present on the UCM Baseboard. This cannot be upgraded to UCM/CBUS2, and a new UCM/CBUS2 must be purchased.





To Upgrade a UCM/CBUS to UCM/CBUS2, you need to use Comfigurator 3.8.6 (beta).
Upgrade your UCM/CBUS to the latest firmware (7.045 or above)

See http://www.comfortforums.com/forum92/3400.html for instructions on how to upgrade firmware in general

This is a 2 step process. First upgrade to the latest cbus1 firmware 7.045, and then upgrade to UCM/CBUS2 firmware

In the Modules Tab, right click on the UCM/Cbus and select "Check for Firmware Upgrades"





This upgrades to the latest UCM/Cbus firmware 7.045 (or later) which is allowed to be upgraded to UCM/CBUS2


Download the UCM/Cbus2 firmware 7.045  (Beta) from http://www.cytech.biz/ucmcbus2_firmware.html
Unzip the zip file into a .cbf file

Right Click on the UCM/CBUS as shown above, and select "Upgrade Firmware from Local File" Browse to the folder where the cbf file is saved and select the cbf file.
The UCM/CBUS1 firmware will be upgraded to UCM/CBUS2.

UCM/CBUS2 can also be "downgraded" to UCM/CBUS1 if required

Note that older ucm/cbus firmware < 7.041 cannot be upgraded directly to UCM/Cbus2 without upgrading to the latest UCM/Cbus1 firmware first.

You should see the UCM/Cbus2 firmware 7.042 as shown




If the UCM is still shown as UCM/CBUS and not UCM/CBUS2, reset Comfort and scan again. Comfort may use the last scanned value of the UCM

Click on the Cbus UCM on the left pane. You should see the Cbus configurator screen as shown below. This means you have successfully upgraded to UCM/Cbus2

If the UCM/Cbus PCB does not have the U2 EEPROM or the CBUS SIM Module is not the ST7 version, the ERR (D4) Red LED on the UCM/CBus PCB will flash continuously and the Status line in the UCM/Cbus2 Comfigurator will show
"EEPROM missing/faulty" or
"CBUS module is lower than V5. Replace CBUS submodule"


IMPORTANT
The C-Bus actions in the cclx file are automatically converted to a new format for UCM/CBUS2, as the formats of the commands in Comfort are not compatible. WRITE to COMFORT now so that the new action formats are updated to Comfort. Save the upgraded cclx  file under a new name so that the old cclx file can be retrieved if you wish to downgrade back to UCM/CBUS1




Built-in Cbus Applications
Clocks/Timekeeping, Security and Zones boxes are shown.
Check to enable the built-in Application and uncheck to disable it.

Clocks and Timekeeping: if enabled, Comfort acts as a Time Master on C-Bus. Comfort time is synchronised to Cbus according to Cbus Time Master rules. Comfort is a secondary Time master on C-Bus. If disabled, Comfort Time is not set to C-Bus and vice versa.

Security: If checked, this enables the C-Bus security application. Security messages are sent and received between Comfort and C-Bus. This requires a C-Bus device which implements the Security Application eg C-Touch mark 2 or C-Gate. If UCM/Cbus does not receive an acknowledgement from Cbus when sending Security Messages, it will automatically disable the Security application so as to avoid retransmits on C-Bus. However if C-Bus sends a Security message to Comfort, this automatically enables the Security Application.

see http://www.comfortforums.com/view_topic.php?id=2262&forum_id=11&jump_to=9184#p9184 for information about C-Touch to Comfort

Zones: This sends zone information on C-Bus Custom Application 01 (which was implemented in UCM/CBUS1). This is not necessary as C-Touch Mark 2 shows zone information on the Sealed and Unsealed function. Do not Enable this application as it will cause unneccesary messages on Cbus. It may be removed in the future.


UCM/CBUS Properties
This shows the properties of the CBUS SIM, Click on "Read Properties" on the CBus menu bar to read the properties from UCM/CBUS. These are READ-ONLY properties, for information only

Unit Adddress: This is the Unit Address on C-Bus. It can be changed by the C-Bus toolkit
CBus SIM Version: This shows the SIM firmware version. ST7 should be 5.04.00 or above. If the SIM version is less than 5, the Status bar will show "SIM Version is less than v5" and the ERROR LED will flash continuously
Network Voltage: This is the voltage on C-Bus.
SIM Options: These are the options set on C-Bus Interface. These are for information only.

Last edited on Tuesday Jun 21st, 2016 06:40 am by



 Posted: Saturday Apr 5th, 2014 10:43 am
   
3rd Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Import from Cbus
This allows .cbz files created by C-Bus Toolkit to be imported. The cbus group addresses are imported into the Lighting, Enable, Trigger, and Measurement Application tables accordingly

Note:
Comfigurator up to 3.8.7 does not separate the different C-Bus networks. Instead ot reads  the group addresses from multiple networks in the cbz file and causes duplicate group addresses. To workaround, please delete networks from the project if there are more than 1 network

Learn
The Learn button is another way to enter new Cbus group addresses if the cbz file is not available.
When the Learn mode is active, any cbus group  address received by UCM/CBUS will be added to the Lighting, Measurement, Enable, or Trigger tables

The screenshot below shows the Lighting Table when populated



Each Lighting Group address is listed with its name as extracted from the cbz file. The cbus group name can also be edited in the right pane.

A Lighting Group address may be mapped to the following Comfort Registers;
Counter, Flag, Virtual Input, Output, Output Toggle, Output Pulse by clicking the Register Type handle on the right pane.


Map to Counter
Select a Comfort Counter to map to the Cbus Lighting group address.
This synchronises the group address with the Counter so that the counter has the same value 0 to 255 as the Cbus device. When the cbus value changes, it also triggers a Counter Response. This can be used to get Cbus trigger something on Comfort using the codes
If Last UCM Counter = 0  then
   do ThisResponse
Else
   do that Response
Endif

That means that if the cbus group is off, it triggers ThisResponse, if other values it triggers another Response

The counter value can be used to monitor the  state of the mapped cbus group address for the Comfort control menu or for the smart phone apps.

Changing the Counter value in Comfort will also set the Cbus device at the group address to the new value. This allows a simple way to control a Cbus dimmer,
eg
"Set Counter  NN =128"  will dim the mapped group address to 50%
"Set Counter NN = 255 " will turn on the device at mapped group address
"Set Counter NN = 0" will turn off the device at mapped group address

Note that changing counter values in Comfort does not trigger the Counter Response as that would be a circular action.

For advanced linkage, the same counter may also be mapped to another device eg Zwave or KNX so that the KNX device can be linked to Cbus via the counter

Map to Flag
Select a Comfort Flag to map to the Cbus Lighting group address. This synchronises the flag with the state of the Cbus device. There are only 2 states to a Flag; on and off. If the device is Off, the flag becomes Off, and if the cbus device has level 1 to 255, that will turn on the mapped flag. This is suitable for cbus relays.
Mapping to flags allows the cbus On/off device to be controlled by setting or clearing the flag, and the state of the cbus device to be monitored by means of the flag

However there are no Flag Responses, unlike the situation with Counters. The cbus device cannot trigger Responses by mapping to a flag.

The same flag may be mapped to other devices eg Comfort Thermostat or blinds function or other external devices. This will be a very powerful way to link devices in future

Map to Virtual Input
This allows a lighting Group Address to be mapped to a Comfort Input/Zone to be used as an alarm input. The Virtual Input can be any Comfort Input on the Controller, LEMs or Slaves. An input mapped as Virtual Input will no longer work as a physical input, ie the physical input is ignored. A virtual Input will have On and Off Response, its Zone Type and entry path settings will still be applicable, ie it will act exactly like a physical input. Virtual Inputs can also be on an input which is not present on any Slave or LEM, ie the zones may go up to 32 (ie with 1 slave) but Virtual Inputs can be on inputs 33 onwards which do not have a real slave or LEM.

Map to Output
A lighting group address can be mapped to a Comfort Output to synchronise the output to the Lighting device. This means that turning on the lighting group turns on the output and vice versa. Turning on the output in Comfort will also cause the lighting group to turn on, ie it is a 2 way mapping

Map to Output Toggle
This also maps an Output to a lighting group address. Every change of state of the lighting device causes the Output to be toggled. However this is one way only as the output change is not sent to the cbus group. Instead a Physical Input can be mapped to the cbus group to provide feedback. The application is for Cbus to control a Comfort TWS lighting module. The cbus device toggles the output and the Input from the TWS gives the feedback to the lighting switch.

Map to Output Pulse
This is another way to map an Lighting group address to an output. Every change of state of the Cbus device causes the Output to Pulse on for 1 second. The state of the output is not sent back to Cbus. Instead a Physical Input can be mapped to the cbus group to provide feedback.  The application is for C-Bus to control an airconditoning system (eg Daikin, Mitsubishi etc) by the manufacturers Interface card.

Test Buttons
For each Cbus group address in the list there is an On and Off test button on the right pane. This tests the ucm/cbus2 by sending On or Off commands to the group address

Last edited on Tuesday May 6th, 2014 04:28 pm by ident



 Posted: Saturday Apr 5th, 2014 01:29 pm
   
4th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Trigger Application

In the Trigger Application table, each Trigger address is mapped to a Comfort Counter


Mapping a Trigger group to a Comfort counter causes the Trigger group and Counter to be synchronised

If a trigger group changes its value, the same value is updated to the mapped counter. The Counter  Response for the counter is triggered. The value of the counter is accessed by action "If Last UCM Counter"

eg
Counter Response:

If Last UCM Counter = 1 Then
    do ResponseA
else
  If Last UCM counter = 2 Then
   doResponseB
 If Last UCM Counter=3 Then
  do ResponseC
....

Endif

Changing a Counter value also sends the counter value to the mapped trigger group



 Posted: Saturday Apr 5th, 2014 01:32 pm
   
5th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Enable Application

Each Enable application address can be mapped to a Comfort Counter




Mapping an Enable group to a Comfort counter causes the Enable group and Counter to be synchronised

If an enable group changes its value, the same value is updated to the mapped counter. The Counter  Response for the counter is triggered. The value of the counter is accessed by action "If Last UCM Counter"



 Posted: Saturday Apr 5th, 2014 01:57 pm
   
6th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Measurement Application

In the Measurement application, each Device ID and Channel can be mapped to a Comfort Sensor 0 to 31. Select a sensor name from the dropdown list



When the measurement device channel changes its value, the value is sent to the mapped Sensor. The measurement value in cbus is a signed floating point value and can take on a very large range of values with many decimal places.
Comfort sensors are signed 16 bit fixed point numbers in the range -32768 to +32768 so there is a disparity between the range of Cbus measurement values and Comfort sensor values. Comfort sensors are for practical real world applications like temperature, energy, etc.
In order to convert the Cbus measurement values into the range which can be accepted by Sensors, a Scaling Factor is used

Go to the Scaling Table


The Measurement Application values include a Unit code which tells what type of unit it is, eg unit 0 = deg C, 1 = Amps, 2 = Angle etc. These unit codes are listed numerically in the table above.
For each Unit code, it is possible to specify a Scaling factor for Comfort to multiply to the Cbus measurement value so that the final value is within the range -32768 to + 32767 which can be stored in the Comfort sensor

For example Unit code 0 (deg C) has a default scaling factor of 1. There is no need to do any scaling on the temperature values as it would not exceed the range -32767 to 32768 degrees. Any decimal part of the measurement would be lost

For Unit code 1 (Amps), if the measurement value is  typically 1 to 999 milli-amps ie 0.001 to 0.999 Amps, the value of 0 would be saved to the sensor which would be useless. Hence a scaling factor of 1000 is used to scale to value to 1 to 999 which can be saved in the sensor.

The scaling factors have default values but can be changed


How the sensor value is used in Comfort depends on the the requirement. For example, the temperature from Cbus can be used in the Comfort Thermostat function, or the current can be used for energy display and logic in Comfort

Currently the mapping is only 1 way, ie Sensor values are not sent to C-Bus. We are looking for feedback to see if this would be useful to implement




 Posted: Saturday Apr 5th, 2014 02:05 pm
   
7th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Physical Inputs to Cbus

This allows a Comfort Input to send its status to a C-Bus lighting Group address



For each Comfort Input or Zone, assign a Lighting Group address as shown above

Any change in the Input will send the state to the mapped lighting group

This allows cbus switches to see the state of the mapped input. It is extremely useful when C-Bus controls airconditioning, lighting or other equipment on Comfort where the status is monitored by Current sensors or relay contacts

The same Lighting group addresses may also be mapped to Comfort Output Pulse, Output toggle or Counters in the Lighting Application table

Note that Virtual Inputs should not be mapped to Group addresses in this table (as Virtual Inputs are not physical)



 Posted: Saturday Apr 5th, 2014 02:17 pm
   
8th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Cbus Menu Bar



Import from Cbus
Browse to select a cbz file to import the cbus group addresses of supported applications

Write To EEPROM
After configuring the mappings, write to UCM/CBUS2 EEPROM. This resets the UCM/Cbus2 and initialises the module.  Be warned that Writing to Comfort does not do a write to EEPROM for UCM/CBUS2.

Read From EEPROM
This reads the UCM/CBUS2 data into the cbus2 configuration tables

Read Properties
This reads the UCM/CBUS2 properties into the Properties tables

Reset to Default
This resets all the information in the UCM/Cbus tables. It does not write the defaulted data to UCM/CBUS2, but a prompt will pop up asking if you would like to write to eeprom

Learn
This puts the UCM/CBUS2 into Learn Mode.
Any Cbus message which is received is entered into the applicable table for the supported applications, ie Lighting, Trigger, Enable, Measurement.



 Posted: Saturday Apr 5th, 2014 02:45 pm
   
9th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

The following diagrams illustrate the linkage between Cbus group addresses and Comfort Registers



Lighting object is mapped to Counter or Flag
The connection is two way so the lighting object state is updated to the Comfort counter or Flag and changes in the counter or flag are also sent to the mapped group address.
In the case of Flags, only off and on values are maintained, while for Counters the values are 0 to 255
Counters and Flags can also be linked to 3rd party objects and appliances like Zwave and KNX or Comfort thermostatr and blinds functions




Lighting Object is mapped to  Comfort Output.
This synchronises the output with the lighting object so the cbus object can control the output on or off and changes in the output state controlled by comfort also update the object status.




Lighting Group is mapped to Output Toggle or Output Pulse (1-way)
In this case the output status is not sent to C-Bus. Instead Comfort Phyicsal Input can be mapped to the Lighting group to send status
This is useful when C-Bus controls airconditionng or two way lighting via Comfort where the status is provided by Comfort current sensor or external relays




 Posted: Saturday Apr 5th, 2014 02:47 pm
   
10th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Reposted from juwi UK

Would it not be possible to solder on a eeprom socket at U2 as well if you didn't have one already fitted and you were good with a soldering iron, or does it imply other issues with the base board if this is missing? Just sounds a shame to have to trash an otherwise perfectly usable UCM baseboard and shame you cant re-flash to another purpose (I.e. UCM general)?

It is possible to solder an 8 pin socket and the J3 shunt if the UCM/Cbus is very old

It is also possible to continue using the old  UCM/Cbus, it is not necessary to upgrade it if it is serving the original purpose


Looks like J4 in the above picture, not J3?
Sorry you are right J4 is the header needed



 Posted: Sunday Apr 6th, 2014 12:06 pm
   
11th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Sending Commands to Cbus

There are 2 ways to send commands to Cbus; the Direct and Indirect method

Direct Commands to Cbus

In Response Wizard, select UCM > Cbus2



The CBus Action window appears



Select the application, eg 56 for Lighting
Select the Group Address

A dropdown list of C-Bus Lighting commands  are shown


Select the command

If the command is to go through Remote Network Bridges enter the bridge numbers in the list separated by commas as shown




Press OK to confirm the C-Bus Action

You can add more Cbus actions to be sent to C-Bus in the  same Response. Sequential C-Bus commands are concatenated together automatically.

Indirect Commands to C-Bus
Indirect commands can be sent to C-Bus by means of the Comfort Registers that are mapped to C-Bus Group addresses. This is a useful new feature in UCM/CBUS2
For example, if Lighting Group Address 5 is mapped to Counter 1, changing Counter 1 to 0 will switch off Lighting Group 5, changing Counter 1 to 255 will switch on Lighting group, and putting a value of 1 to 254 into the counter will dim the Group to the same level
If a lighting Group is mapped to a Flag which has states on and off, then setting the flag will turn on the Lighting Group and clearing the flag will switch off the Lighting Group
If a lighting group is linked to Output (but not Output Pulse or Output Toggle), then turning on the Output wiil turn on the Lighting Group and turning off the Output will switch off the Lighting Group






 Posted: Monday Apr 7th, 2014 03:51 pm
   
12th Post
Home
Comfort Distributors
 

Joined: Wednesday Jul 12th, 2006
Location: United Kingdom
Posts: 558
Status: 
Offline

  back to top

Fantastic
Cannot wait to try this out....

Can I purchase a CBUS2 now or do I have to purchase the 1 and then upgrade? 

As a cautionary note - the submodule - should this be the same numbering/lettering as the main board i.e.
UCM/CBUS2CBUS2 daughter board (or sub board) 



 Posted: Monday Apr 7th, 2014 05:54 pm
   
13th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

You can purchase a UCM/CBUS1 and upgrade. The distributors will not have UCM/Cbus2 yet

The submodule has its own part number CBUS01



 Posted: Monday Apr 7th, 2014 07:36 pm
   
14th Post
Howser
Member
 

Joined: Monday May 22nd, 2006
Location: Pretoria, South Africa
Posts: 194
Status: 
Offline

  back to top

I upgraded my UCM/CBus1  today and played a bit with the Cbus2 features, so far it looks pretty cool. 



 Posted: Tuesday Apr 8th, 2014 01:23 am
   
15th Post
Howser
Member
 

Joined: Monday May 22nd, 2006
Location: Pretoria, South Africa
Posts: 194
Status: 
Offline

  back to top

I like the fact that the Lighting Tab, as well as Trigger and Enable have Group Address and Name displayed in the listed properties. It is possible to have the same in the Physical Inputs?



 Posted: Tuesday Apr 8th, 2014 03:48 pm
   
16th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Thanks, good suggestion. It will be implemented in a future version, nit the next 3.8.6 which is already beiing tested

Last edited on Friday Apr 11th, 2014 12:54 pm by ident



 Posted: Friday Apr 11th, 2014 01:06 pm
   
17th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

UCM/CBUS2 firmware 7.045 (Beta) can be downloaded from http://www.cytech.biz/ucmcbus2_firmware.html

The changes are;
  1. Fixed Bug - Measurement Application from Cbus was converted to 0  value when Comfort is armed
  2. Fixed Bug - Response wizard to cbus2 may not work for some UCM IDs eg 8
  3. Monitor Mode in Cbus 2 may causes wrong behaviour in other UCMs especially  Zwave
  4. Removed the Custom Zones Application 01 as it is not needed anymore and causes  unneccessary traffic in Cbus. The Security Application Zone Sealed/Unsealed Group handles the display of zone status. The Properties Checkbox in Comfigurator for Cbus2 Zones Application shall be removed.
  5. The Security Application is now automatically enabled if there is a unit that supports in in the C-Bus network, eg C-Touch or C-Gate and disabled if there is not. The Properties Checkbox in Comfigurator for Cbus2 Security Application shall be removed.
  6. Fixed Bug - Dimming cbus by pressing and holding a CBus button to full brightness of 255 or minimum level of 01 did not send the values 255 or 01 to the counter. hence the counter was loaded with the previous level
Many thanks to Ingo for testing the firmware in his extensive C-Bus setup

Last edited on Friday Apr 11th, 2014 03:11 pm by ident



 Posted: Friday Apr 11th, 2014 03:58 pm
   
18th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

Comfigurator 3.8.6 Beta has the following changes for UCM/CBUS configuration. UCM/CBUS 2 firmware 7.045 should be used with this software version.
  1. In Cbus2 Properties, the Custom Applications Zones and Security Checkboxes have been removed. The Zones Custom Application 01 has been removed in UCM/Cbus2 v7.045 as it is not useful and causes additional traffic in Cbus. The Security Application Sealed/Unsealed Zones function provides the function of displaying the state of the zones. The Security Application Checkbox has been removed. in UCM/Cbus2 v7.045, the Security Application is automatically enabled when there is a C-Bus device capable of supporting it eg C-Touch or C-Gate
  2. In each Cbus Application Table, the menu buttons Add, Delete and Learn have been added. "Add " adds a Cbus Group address to the table manually. This is another alternative to importing the cbus network information from the .cbz file and Learn Mode. The Delete button allows a Cbus group address to be removed from the table
  3. In the Monitor window, the buttons "Clear" and "Copy to Clipboard" have been added. Copy to Clipboard can be used to save data for analysis later.

Known Bugs
  1. Response Wizard for sending to Trigger and Enable applications are wrong

Last edited on Saturday Apr 12th, 2014 12:29 pm by ident



 Posted: Saturday Apr 12th, 2014 12:11 am
   
19th Post
Howser
Member
 

Joined: Monday May 22nd, 2006
Location: Pretoria, South Africa
Posts: 194
Status: 
Offline

  back to top

ident wrote: Comfigurator 3.8.6 Beta has the following changes for UCM/CBUS configuration. UCM/CBUS 2 firmware 7.045 should be used with this software version.
  1. In Cbus2 Properties, the Custom Applications Zones and Security Checkboxes have been removed. The Zones Custom Application 01 has been removed in UCM/Cbus2 v7.045 as it is not useful and causes additional traffic in Cbus. The Security Application Sealed/Unsealed Zones function provides the function of displaying the state of the zones. The Security Application Checkbox has been removed. in UCM/Cbus2 v7.045, the Security Application is automatically enabled when there is a C-Bus device capable of supporting it eg C-Touch or C-Gate

The security Application is enabled when there is a PAC, right?



 Posted: Saturday Apr 12th, 2014 06:47 am
   
20th Post
ident
Administrator


Joined: Wednesday Aug 9th, 2006
Location: Singapore
Posts: 3497
Status: 
Offline

  back to top

I am not sure of the PAC
If it worked with the old UCM/CBus on the security application, then it supports the security application



 Current time is 12:23 pmPage:    1  2  Next Page Last Page  
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems