https://www.comfortforums.com/ Sun, 09 Aug 2026 02:49:58 +0000 MyBB https://www.comfortforums.com/thread-5409.html Sun, 11 Dec 2022 08:07:57 -0500 ]]> https://www.comfortforums.com/thread-5409.html
The Samsung system is 2 x multi split systems, one with 3 indoor units and one with 2 indoor units. The two outdoor condensers (one per system) are each fitted with Samsung MIM-B19N modbus cards, wired in a star configuration to the UCM modbus.

Firstly, you need to configure the UCM modbus to operate at 9600bps.
Secondly, you need to configure all the indoor units to \'enable central control\' - something tech support had to help with; unit you have done this the Modbus card in the condenser reports E604 error message.

You have to calculate the address of each modbus element, details are in the Samsung manual, but in short:
The first unit is 0, second unit is 1, third unit is 2 etc.
You use a multiplier, but for my config the addresses are as per the attached image. You can see how one system (modbus slave 1) has the 2 indoor units and the second system (modbus slave 2) has the 3 indoor units.

I have used responses to set all the units on, off, and at particular modes and set points etc. Touch wood (it\'s only day 2) it\'s all working a dream! Another lovely and simple integration!

  2022-12-11.jpg (Size: 92.89 KB / Downloads: 10) ]]>
The Samsung system is 2 x multi split systems, one with 3 indoor units and one with 2 indoor units. The two outdoor condensers (one per system) are each fitted with Samsung MIM-B19N modbus cards, wired in a star configuration to the UCM modbus.

Firstly, you need to configure the UCM modbus to operate at 9600bps.
Secondly, you need to configure all the indoor units to \'enable central control\' - something tech support had to help with; unit you have done this the Modbus card in the condenser reports E604 error message.

You have to calculate the address of each modbus element, details are in the Samsung manual, but in short:
The first unit is 0, second unit is 1, third unit is 2 etc.
You use a multiplier, but for my config the addresses are as per the attached image. You can see how one system (modbus slave 1) has the 2 indoor units and the second system (modbus slave 2) has the 3 indoor units.

I have used responses to set all the units on, off, and at particular modes and set points etc. Touch wood (it\'s only day 2) it\'s all working a dream! Another lovely and simple integration!

  2022-12-11.jpg (Size: 92.89 KB / Downloads: 10) ]]> https://www.comfortforums.com/thread-5393.html Sat, 24 Sep 2022 22:47:43 -0400 ]]> https://www.comfortforums.com/thread-5393.html

This means that multiple modbus slave registers can be polled in one command. For example in the above screenshot example on the 1st line, Modbus address 0 Discrete Input  and mapped to Flag 21.  No of Registers = 5 means that  5 sequential Modbus registers are mapped to 5 sequential Flags.
eg

1. Modbus address 0 -> Flag 21
2. Modbus address 1 > Flag 22
3. Modbus address 2 > Flag 23
4. Modbus Address 3 > Flag 24
5. Modbus Adress 4 > Flag 25

These modbus addresses must be the same type eg Discrete Inputs
This allows the Modbus Master to poll the slave very fast and reduces the number of Modbus to Comfort Table entries. The above example required 5 entries before, but nopw only requires 1 entry in Modbus to Comfort
]]>

This means that multiple modbus slave registers can be polled in one command. For example in the above screenshot example on the 1st line, Modbus address 0 Discrete Input  and mapped to Flag 21.  No of Registers = 5 means that  5 sequential Modbus registers are mapped to 5 sequential Flags.
eg

1. Modbus address 0 -> Flag 21
2. Modbus address 1 > Flag 22
3. Modbus address 2 > Flag 23
4. Modbus Address 3 > Flag 24
5. Modbus Adress 4 > Flag 25

These modbus addresses must be the same type eg Discrete Inputs
This allows the Modbus Master to poll the slave very fast and reduces the number of Modbus to Comfort Table entries. The above example required 5 entries before, but nopw only requires 1 entry in Modbus to Comfort
]]> https://www.comfortforums.com/thread-4893.html Thu, 17 May 2018 17:12:47 -0400 ]]> https://www.comfortforums.com/thread-4893.html I have bought UCM Modbus RS485. 
Can I add the ETH03 to convert Modbus TCP?



]]> I have bought UCM Modbus RS485. 
Can I add the ETH03 to convert Modbus TCP?



]]> https://www.comfortforums.com/thread-4848.html Sat, 27 Jan 2018 08:00:02 -0500 ]]> https://www.comfortforums.com/thread-4848.html

• For UCM/Modbus-ETH03 configured as Master, connecting to a Modbus Slave device, the IP address of the UCM/Modbus may need to be specifically allowed to connect to the Slave. There may be a setting on the Slave device to allow certain IP addresses, or all IP addresses to connect. If the UCM/Modbus is not able to connect, then in Comfort Server Manager, the IP address of the UCM/Modbus will be Idle, instead of Busy when it is connected.
  

]]>

• For UCM/Modbus-ETH03 configured as Master, connecting to a Modbus Slave device, the IP address of the UCM/Modbus may need to be specifically allowed to connect to the Slave. There may be a setting on the Slave device to allow certain IP addresses, or all IP addresses to connect. If the UCM/Modbus is not able to connect, then in Comfort Server Manager, the IP address of the UCM/Modbus will be Idle, instead of Busy when it is connected.
  

]]> https://www.comfortforums.com/thread-4845.html Sun, 21 Jan 2018 02:23:07 -0500 ]]> https://www.comfortforums.com/thread-4845.html
This is probably due to a [color=\"#ff0000\"]very old UCM firmware[/color] (UCM/USB or UCM/ETH03) for the UCM used to program the system. The old UCM firmware is not able to support new features in Comfort or Comfigurator, and thus needs to be upgraded

The UCM firmware should be upgraded to the latest, by right clicking on the UCM under Modules and selecting \"Check for Firmware Upgrades\"




You will be asked to press F0 on the keypad to enable Engineer Mode

If you see that message, please press F0 on the keypad.  This is a protection against unauthorised upgrade.
This will allow the firmware upgrade to start

]]>
This is probably due to a [color=\"#ff0000\"]very old UCM firmware[/color] (UCM/USB or UCM/ETH03) for the UCM used to program the system. The old UCM firmware is not able to support new features in Comfort or Comfigurator, and thus needs to be upgraded

The UCM firmware should be upgraded to the latest, by right clicking on the UCM under Modules and selecting \"Check for Firmware Upgrades\"




You will be asked to press F0 on the keypad to enable Engineer Mode

If you see that message, please press F0 on the keypad.  This is a protection against unauthorised upgrade.
This will allow the firmware upgrade to start

]]> https://www.comfortforums.com/thread-4669.html Thu, 30 Mar 2017 13:08:17 -0400 ]]> https://www.comfortforums.com/thread-4669.html
In this mode, third party devices and software are able to control Comfort by sending commands and getting responses.  UCM/Modbus is a Slave and the Modbus device is Master. In Comfigurator, the Modbus Master/Slave is set to Server/Slave. The Modbus ID field applies to the UCM/Modbus Modbus ID as a Slave.
The following Modbus functions are supported

Function Code  Function                        Parameters
1                       Read Coils                      Read from starting address, no of addresses
2                       Read Discrete Inputs     Read from starting address, no of addresses
3                       Read Holding Registers  Read from starting address, no of addresses
4                       Read Input Registers     Read from starting address, no of addresses
5                       Write Single Coil            Write from Address, Value
6                       Write Holding Register   Write from Address, Value


Write Multiple Coils and Write Multiple Holding Registers are not supported


When Modbus Slave is selected, the screen below should be seen in the Modbus Server Tab
This is a convenient lookup reference table which shows the Modbus Addresses  in Decimal and Hexadecimal format of all the Comfort events and registers that are exposed to Modbus.






Each of the items above is a Category that can be expanded by selecting the item


Zones/Inputs
Comfort Zones/Inputs are mapped to Modbus discrete Inputs





Outputs
Comfort Outputs are mapped to Modbus Coils



Flags
Comfort Flags are mapped to Modbus Discrete Inputs




Bypass Inputs
Bypass Inputs are mapped to Modbus Coils.




Counters
Comfort Counters are mapped to Modbus Holding Registers




Sensors
Comfort sensors are mapped to Modbus Holding Regsters




Security/Keypad commands
Key arm security and Autoarm security commands to Comfort are mapped to Holding Registers




]]>
In this mode, third party devices and software are able to control Comfort by sending commands and getting responses.  UCM/Modbus is a Slave and the Modbus device is Master. In Comfigurator, the Modbus Master/Slave is set to Server/Slave. The Modbus ID field applies to the UCM/Modbus Modbus ID as a Slave.
The following Modbus functions are supported

Function Code  Function                        Parameters
1                       Read Coils                      Read from starting address, no of addresses
2                       Read Discrete Inputs     Read from starting address, no of addresses
3                       Read Holding Registers  Read from starting address, no of addresses
4                       Read Input Registers     Read from starting address, no of addresses
5                       Write Single Coil            Write from Address, Value
6                       Write Holding Register   Write from Address, Value


Write Multiple Coils and Write Multiple Holding Registers are not supported


When Modbus Slave is selected, the screen below should be seen in the Modbus Server Tab
This is a convenient lookup reference table which shows the Modbus Addresses  in Decimal and Hexadecimal format of all the Comfort events and registers that are exposed to Modbus.






Each of the items above is a Category that can be expanded by selecting the item


Zones/Inputs
Comfort Zones/Inputs are mapped to Modbus discrete Inputs





Outputs
Comfort Outputs are mapped to Modbus Coils



Flags
Comfort Flags are mapped to Modbus Discrete Inputs




Bypass Inputs
Bypass Inputs are mapped to Modbus Coils.




Counters
Comfort Counters are mapped to Modbus Holding Registers




Sensors
Comfort sensors are mapped to Modbus Holding Regsters




Security/Keypad commands
Key arm security and Autoarm security commands to Comfort are mapped to Holding Registers




]]> https://www.comfortforums.com/thread-4668.html Thu, 30 Mar 2017 12:51:44 -0400 ]]> https://www.comfortforums.com/thread-4668.html This shows the Modbus communications in both Transmit and receive directions.
It works for Modbus Master and Modbus Slave modes

Lines beginning with > show Transmit data ie transmit from UCM/Modbus to Modbus
Line beginning with < show Receive data ie receive from Modbus to UCM/Modbus

This is esepcailly useful in TCP mode as the IP addresses and port must be entered correctly for master and slave in order for communications to be successful

The information is raw modbus data. Refer to the Modbus standard documentation for the meaning of the data.

Modbus TCP and Modbus RTU have slightly different message structure. The example below is for TCP



To turn on Modbus Monitor, click on the Modbus Monitor Tab. To leave the Modbus Monitor, select another tab.


UCM/Modbus as Modbus Master will continually poll the Modbus Slave to which it is connected according to the Modbus to Comfort Table. Each modbus address will be polled in turn - when the slave address replies, the next Modbus address is polled, until the end of the table when it starts again from the top of the table

Note that in Modbus Monitor in Master Mode, the polling rate is slightly slower about 300 ms in order to avoid overflowing the monitor buffer

UCM/Modbus in Slave Mode replies only to a Poll from the Modbus Master which is connected to the UCM/Modbus.




]]> This shows the Modbus communications in both Transmit and receive directions.
It works for Modbus Master and Modbus Slave modes

Lines beginning with > show Transmit data ie transmit from UCM/Modbus to Modbus
Line beginning with < show Receive data ie receive from Modbus to UCM/Modbus

This is esepcailly useful in TCP mode as the IP addresses and port must be entered correctly for master and slave in order for communications to be successful

The information is raw modbus data. Refer to the Modbus standard documentation for the meaning of the data.

Modbus TCP and Modbus RTU have slightly different message structure. The example below is for TCP



To turn on Modbus Monitor, click on the Modbus Monitor Tab. To leave the Modbus Monitor, select another tab.


UCM/Modbus as Modbus Master will continually poll the Modbus Slave to which it is connected according to the Modbus to Comfort Table. Each modbus address will be polled in turn - when the slave address replies, the next Modbus address is polled, until the end of the table when it starts again from the top of the table

Note that in Modbus Monitor in Master Mode, the polling rate is slightly slower about 300 ms in order to avoid overflowing the monitor buffer

UCM/Modbus in Slave Mode replies only to a Poll from the Modbus Master which is connected to the UCM/Modbus.




]]> https://www.comfortforums.com/thread-4641.html Sat, 25 Feb 2017 08:57:32 -0500 ]]> https://www.comfortforums.com/thread-4641.html
For Modbus Master Mode, Alarm to Modbus mapping did not work

Please upgrade the firmware. In Modules Tab, select UCM/Modbus on the left pane and right click, then select Check for Upgrades\"
]]>
For Modbus Master Mode, Alarm to Modbus mapping did not work

Please upgrade the firmware. In Modules Tab, select UCM/Modbus on the left pane and right click, then select Check for Upgrades\"
]]> https://www.comfortforums.com/thread-4616.html Tue, 31 Jan 2017 10:07:14 -0500 ]]> https://www.comfortforums.com/thread-4616.html https://www.cytech.biz/product_details.php?item_id=470

Also please refer to the topics below for basic instructions

UCM/Modbus Programming
http://www.comfortforums.com/forum133/4614.html

UCM/Modbus as Master
http://www.comfortforums.com/forum133/4615.html
]]> https://www.cytech.biz/product_details.php?item_id=470

Also please refer to the topics below for basic instructions

UCM/Modbus Programming
http://www.comfortforums.com/forum133/4614.html

UCM/Modbus as Master
http://www.comfortforums.com/forum133/4615.html
]]> https://www.comfortforums.com/thread-4615.html Tue, 31 Jan 2017 09:48:53 -0500 ]]> https://www.comfortforums.com/thread-4615.html




If Modbus Interface is TCP, then the Comfort Server Manager link will be shown



Tabs: Modbus to Comfort, Alarm to Modbus, Monitor Mode can be seen

[size=\"3\"]Modbus to Comfort
[/size]This is applicable for UCM/Modbus as Master only, not as Slave.
In this tab, the Modbus addresses are defined and mapped to Comfort registers (Counters, Flags, Sensors, Outputs, Arm Security, Panic, Bypass Zones). Up to 256 Modbus addresses can be mapped to Comfort




 A Typical  Modbus to Comfort screen is shown above. Press Add Modbus Element to add another element




Select the Modbus Element Type from

• Discrete Input
• Coil
• Input Register
• Holding Register

Discrete Input



Modbus Discrete Inputs are 1 bit (on/off) registers that can be mapped to Counters, Virtual Inputs, Flags, Outputs, Output Toggle, Output Pulse, Arm Security, Panic, Bypass Zone

Coil



Modbus Coils are 1 bit (on/off) registers that can be mapped to Counter, Physical Input, Counter, Flag , Sensor

Input Register



Modbus Input Registers are 16-bit registers that can be mapped to Counters, Sensors, Flags, Outputs, Virtual Inputs, arm security, panic, bypass zone. Modbus Input registers are read only, and cannot be changed by the maped counter and sensor.

Holding Register



Modbus Holding Registers 16-bit registers can be mapped to Counters, Physical Input, Flag, Sensors, Modbus Holding registers are read/write registers and can be changed by the mapped counter and sensor.


Modbus Register Number
After selecting the Modbus element (Coil, Discrete Input, Input Register, Holding Register), enter the Modbus Address in Decimal or Hexadecimal notation (depending on the setting in Properties). Modbus Registers have a range from 0 to FFFF Hexadecimal or 0 to 65535 in Decimal.






Avoid entering the same Register number for the same Modbus element type, eg Coil 1000 is entered in the table it should not be duplicated in any of the tables to avoid conflict. Every Modbus device will have a table showing the Modbus element and address and the function related to  it, so that other Modbus devices acting as Master can read and/or write to the correct Register.

Number of Registers




This means that multiple modbus slave registers can be polled in one command. For example in the above screenshot example on the 1st line, Modbus address 0 Discrete Input  and mapped to Flag 21.  No of Registers = 5 means that  5 sequential Modbus registers are mapped to 5 sequential Flags.
eg

1. Modbus address 0 -> Flag 21
2. Modbus address 1 > Flag 22
3. Modbus address 2 > Flag 23
4. Modbus Address 3 > Flag 24
5. Modbus Adress 4 > Flag 25

These modbus addresses must be the same type eg Discrete Inputs
This allows the Modbus Master to poll the slave very fast and reduces the number of Modbus to Comfort Table entries. The above example required 5 entries before, but nopw only requires 1 entry in Modbus to Comfort
]]>




If Modbus Interface is TCP, then the Comfort Server Manager link will be shown



Tabs: Modbus to Comfort, Alarm to Modbus, Monitor Mode can be seen

[size=\"3\"]Modbus to Comfort
[/size]This is applicable for UCM/Modbus as Master only, not as Slave.
In this tab, the Modbus addresses are defined and mapped to Comfort registers (Counters, Flags, Sensors, Outputs, Arm Security, Panic, Bypass Zones). Up to 256 Modbus addresses can be mapped to Comfort




 A Typical  Modbus to Comfort screen is shown above. Press Add Modbus Element to add another element




Select the Modbus Element Type from

• Discrete Input
• Coil
• Input Register
• Holding Register

Discrete Input



Modbus Discrete Inputs are 1 bit (on/off) registers that can be mapped to Counters, Virtual Inputs, Flags, Outputs, Output Toggle, Output Pulse, Arm Security, Panic, Bypass Zone

Coil



Modbus Coils are 1 bit (on/off) registers that can be mapped to Counter, Physical Input, Counter, Flag , Sensor

Input Register



Modbus Input Registers are 16-bit registers that can be mapped to Counters, Sensors, Flags, Outputs, Virtual Inputs, arm security, panic, bypass zone. Modbus Input registers are read only, and cannot be changed by the maped counter and sensor.

Holding Register



Modbus Holding Registers 16-bit registers can be mapped to Counters, Physical Input, Flag, Sensors, Modbus Holding registers are read/write registers and can be changed by the mapped counter and sensor.


Modbus Register Number
After selecting the Modbus element (Coil, Discrete Input, Input Register, Holding Register), enter the Modbus Address in Decimal or Hexadecimal notation (depending on the setting in Properties). Modbus Registers have a range from 0 to FFFF Hexadecimal or 0 to 65535 in Decimal.






Avoid entering the same Register number for the same Modbus element type, eg Coil 1000 is entered in the table it should not be duplicated in any of the tables to avoid conflict. Every Modbus device will have a table showing the Modbus element and address and the function related to  it, so that other Modbus devices acting as Master can read and/or write to the correct Register.

Number of Registers




This means that multiple modbus slave registers can be polled in one command. For example in the above screenshot example on the 1st line, Modbus address 0 Discrete Input  and mapped to Flag 21.  No of Registers = 5 means that  5 sequential Modbus registers are mapped to 5 sequential Flags.
eg

1. Modbus address 0 -> Flag 21
2. Modbus address 1 > Flag 22
3. Modbus address 2 > Flag 23
4. Modbus Address 3 > Flag 24
5. Modbus Adress 4 > Flag 25

These modbus addresses must be the same type eg Discrete Inputs
This allows the Modbus Master to poll the slave very fast and reduces the number of Modbus to Comfort Table entries. The above example required 5 entries before, but nopw only requires 1 entry in Modbus to Comfort
]]> https://www.comfortforums.com/thread-4614.html Tue, 31 Jan 2017 09:03:58 -0500 ]]> https://www.comfortforums.com/thread-4614.html https://www.cytech.biz/comfigurator.html
A UCM/USB or UCM/Ethernet is required to connect to the computer running Comfigurator.
Run Comfigurator, go to the Modules Tab and right-click on UCMs folder symbol as shown below.


“Scan for All Modules” or “Scan for UCMs” will automatically detect all UCMs including the UCM/Modbus if the ID is set correctly without any conflict with other UCMs.
“Add UCM” allows you to manually add a UCM/Modbus if not currently connected to Comfort, i.e. when doing programming off-line.




The scan results should discover a UCM/Modbus as shown below



[font=\"Times New Roman, serif\"][size=\"3\"]Click on the Modbus UCM on the left pane. This brings up the Modbus Configurator as shown below;

[/size][/font]




[size=\"3\"]UCM Properties[/size]
ID                   1 to max for UCM RS485 ID
Name              as in Modules> UCM
Type               Modbus (subtype 27)
Version           UCM/Modbus firmware version eg 7.096

[size=\"3\"]UCM/Modbus Properties
[/size]Interface           
RTU(RS485)  or TCP

Baud Rate         
2400, 4800, 9600, 19200, 38400, 76800 (Modbus RTU Only)

Parity                 
Even, Odd, None (Modbus RTU Only)

Master/Slave
Master or Slave. Master will communicate with Modbus Slave.   Slave will communicate with Modbus Master.

Modbus Slave ID 
1 to 247. Modbus ID of Slave when UCM is Master, or Modbus ID of  UCM/Modbus UCM when UCM/Modbus is Slave

Notes on Master/Slave
In general, if Comfort is controlling another Modbus device, UCM/Modbus should be a Master, and the other device should be a Slave. If another device is controling Comfort, then UCM/Modbus should be a Slave and the other device a Master. Modbus Software with GUI functions are normally Masters. One master can be in the same Modbus network with many Modbus Slaves.

For UCM/Modbus as Slave, Modbus to Comfort and Alarm To Modbus Tabs are not applicable. See the section on UCM/Modbus as Server/Slave in this manual. UCM/Modbus can either be Master or Slave at any one time.

[size=\"3\"]Display Settings[/size]
Modbus Address Display Format:    Hexadecimal or Decimal
This determines the Modbus Addresses are displayed in Hexadecimal or Decimal format

]]> https://www.cytech.biz/comfigurator.html
A UCM/USB or UCM/Ethernet is required to connect to the computer running Comfigurator.
Run Comfigurator, go to the Modules Tab and right-click on UCMs folder symbol as shown below.


“Scan for All Modules” or “Scan for UCMs” will automatically detect all UCMs including the UCM/Modbus if the ID is set correctly without any conflict with other UCMs.
“Add UCM” allows you to manually add a UCM/Modbus if not currently connected to Comfort, i.e. when doing programming off-line.




The scan results should discover a UCM/Modbus as shown below



[font=\"Times New Roman, serif\"][size=\"3\"]Click on the Modbus UCM on the left pane. This brings up the Modbus Configurator as shown below;

[/size][/font]




[size=\"3\"]UCM Properties[/size]
ID                   1 to max for UCM RS485 ID
Name              as in Modules> UCM
Type               Modbus (subtype 27)
Version           UCM/Modbus firmware version eg 7.096

[size=\"3\"]UCM/Modbus Properties
[/size]Interface           
RTU(RS485)  or TCP

Baud Rate         
2400, 4800, 9600, 19200, 38400, 76800 (Modbus RTU Only)

Parity                 
Even, Odd, None (Modbus RTU Only)

Master/Slave
Master or Slave. Master will communicate with Modbus Slave.   Slave will communicate with Modbus Master.

Modbus Slave ID 
1 to 247. Modbus ID of Slave when UCM is Master, or Modbus ID of  UCM/Modbus UCM when UCM/Modbus is Slave

Notes on Master/Slave
In general, if Comfort is controlling another Modbus device, UCM/Modbus should be a Master, and the other device should be a Slave. If another device is controling Comfort, then UCM/Modbus should be a Slave and the other device a Master. Modbus Software with GUI functions are normally Masters. One master can be in the same Modbus network with many Modbus Slaves.

For UCM/Modbus as Slave, Modbus to Comfort and Alarm To Modbus Tabs are not applicable. See the section on UCM/Modbus as Server/Slave in this manual. UCM/Modbus can either be Master or Slave at any one time.

[size=\"3\"]Display Settings[/size]
Modbus Address Display Format:    Hexadecimal or Decimal
This determines the Modbus Addresses are displayed in Hexadecimal or Decimal format

]]> https://www.comfortforums.com/thread-4565.html Sat, 26 Nov 2016 05:54:17 -0500 ]]> https://www.comfortforums.com/thread-4565.html

Cytech\'s new UCM/Modbus allows Modbus devices to be interfaced to Cytech\'s Comfort system. The UCM/Modbus can be programmed as Client/Master or Server/Slave on  Modbus. Master mode is for Comfort to control other Modbus Slave products, and Slave mode is for  other Modbus devices and software to control Comfort. Both modes are capable of 2- way communications, ie Comfort to Modbus and Modbus to Comfort

Modbus over RS485 (Modbus/RTU) and Modbus over IP are possible by plugging in the RS485 or ETH03 Ethernet submodule onto the UCM/Modbus baseboard.
The UCM/Modbus can work with other Comfort modules including Intelligent  Remote Input/Output Modules (IRIO), Temperature Sensor Module (TSM01), Hotel I/O (HIO) as well as 3rd party systems on the Comfort Bus including C-Bus, KNX etcPlease visit the UCM/Modbus website at https://www.cytech.biz/brochure/ucm-modbus.html

Specifications

• Configurable as Master or Slave  on Modbus
• Implements Modbus/RTU by RS485  and Modbus/TCP using plug in sub-modules RS485 or ETH03 respectively. RS232 is also possible for Modbus RTU
  
• Comfort (CM9000), UCM/Logic, LGX01 Logic Engine can act as the central controller for UCM/Modbus
• In /Master Mode: 256 Modbus addresses in Modbus to Comfort
• For Modbus/RTU, baud rate selectable from 1200, 2400, 4800, 9600, 19200, 38400, 76800 bps. Parity None, Even or Odd
• As  Modbus Master, Comfort Counters, Flags, Sensors, Inputs, Outputs, security commands and alarm conditions can be accessed (read/write) by a Modbus Master
• As Modbus Slave, Comfort Counters, Flags, Sensors, Inputs, Outputs, Alarm conditions can be accessed via Modbus Registers
• Modbus Monitor mode shows the receive abd transmit communications between UCM/Modbus and Modbus. It works for RTU and TCP interfaces, as well as Master and Slave
  

Minimum System Requirements

• Comfort Ultra/OPT or UCM/Logic or LGX01 Firmware 7.116 or above can act as controllers.
  
• UCM/Modbus firmware 7.103 or above
• Comfigurator 3.11.12 or above

Part Numbers

• UCM/Modbus-485 with Rs485 Interface
• UCM/Modbus-ETH with Ethernet Interface

The UCM/Modbus manual and Firmware can be downloaded from https://www.cytech.biz/product_details.php?item_id=470


]]>

Cytech\'s new UCM/Modbus allows Modbus devices to be interfaced to Cytech\'s Comfort system. The UCM/Modbus can be programmed as Client/Master or Server/Slave on  Modbus. Master mode is for Comfort to control other Modbus Slave products, and Slave mode is for  other Modbus devices and software to control Comfort. Both modes are capable of 2- way communications, ie Comfort to Modbus and Modbus to Comfort

Modbus over RS485 (Modbus/RTU) and Modbus over IP are possible by plugging in the RS485 or ETH03 Ethernet submodule onto the UCM/Modbus baseboard.
The UCM/Modbus can work with other Comfort modules including Intelligent  Remote Input/Output Modules (IRIO), Temperature Sensor Module (TSM01), Hotel I/O (HIO) as well as 3rd party systems on the Comfort Bus including C-Bus, KNX etcPlease visit the UCM/Modbus website at https://www.cytech.biz/brochure/ucm-modbus.html

Specifications

• Configurable as Master or Slave  on Modbus
• Implements Modbus/RTU by RS485  and Modbus/TCP using plug in sub-modules RS485 or ETH03 respectively. RS232 is also possible for Modbus RTU
  
• Comfort (CM9000), UCM/Logic, LGX01 Logic Engine can act as the central controller for UCM/Modbus
• In /Master Mode: 256 Modbus addresses in Modbus to Comfort
• For Modbus/RTU, baud rate selectable from 1200, 2400, 4800, 9600, 19200, 38400, 76800 bps. Parity None, Even or Odd
• As  Modbus Master, Comfort Counters, Flags, Sensors, Inputs, Outputs, security commands and alarm conditions can be accessed (read/write) by a Modbus Master
• As Modbus Slave, Comfort Counters, Flags, Sensors, Inputs, Outputs, Alarm conditions can be accessed via Modbus Registers
• Modbus Monitor mode shows the receive abd transmit communications between UCM/Modbus and Modbus. It works for RTU and TCP interfaces, as well as Master and Slave
  

Minimum System Requirements

• Comfort Ultra/OPT or UCM/Logic or LGX01 Firmware 7.116 or above can act as controllers.
  
• UCM/Modbus firmware 7.103 or above
• Comfigurator 3.11.12 or above

Part Numbers

• UCM/Modbus-485 with Rs485 Interface
• UCM/Modbus-ETH with Ethernet Interface

The UCM/Modbus manual and Firmware can be downloaded from https://www.cytech.biz/product_details.php?item_id=470


]]>