|
|
| (4 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | The KNX functionality of CoolMasterNet is fully described in: [http://coolautomation.com/lib/doc/manual/KNX-guidelines.pdf KNX Module User Guidelines (PDF)] | + | The KNX functionality of CoolMasterNet (ETS Integration Guidelines) is fully described in: [https://coolautomation.com/wp-content/uploads/sites/2/2021/01/KNX_ETS-Integration-Guidelines_CMNET.pdf KNX Guidelines for CoolMasterNet (PDF)] |
| − | | |
| − | == KNX module installation and activation ==
| |
| − | [[File:CM5-drawing-3D-angle-KNX.gif]]<br>
| |
| − | Physical connection of CoolMasterNet to KNX bus (TP physical layer) is made with "CoolAutomation KNX extension module", further referenced as KNX module. KNX module can be pre-installed inside CoolMasterNet body by CoolAutomation or can be purchased later and installed by customer itself. Once KNX module is installed it should be activated. Run '''line''' command to check if KNX module is already activated.
| |
| − | {{Terminal |
| |
| − | 1=>'''line'''<br>
| |
| − | L1: DK Master U00/G00 myID:0B<br>
| |
| − | Tx:2/2 Rx:2/2 TO:0/0 CS:0/0 Col:0/0 NAK:0/0<br>
| |
| − | L2: Unused<br>
| |
| − | Tx:0/0 Rx:0/0 TO:0/0 CS:0/0 Col:0/0 NAK:0/0<br>
| |
| − | <span style="color:#FF8080">
| |
| − | L3: KNX Physical Address:Not Assigned<br>
| |
| − | </span>
| |
| − | Tx:0/0 Rx:0/0 TO:0/0 CS:0/0 Col:0/0 NAK:0/0<br>
| |
| − | L4: Unused<br>
| |
| − | Tx:0/0 Rx:0/0 TO:0/0 CS:0/0 Col:0/0 NAK:0/0<br>
| |
| − | L5: Unused<br>
| |
| − | Tx:0/0 Rx:0/0 TO:0/0 CS:0/0 Col:0/0 NAK:0/0<br>
| |
| − | L6: Unused<br>
| |
| − | Tx:0/0 Rx:0/0 TO:0/0 CS:0/0 Col:0/0 NAK:0/0<br>
| |
| − | L7: Unused<br>
| |
| − | Tx:0/0 Rx:0/0 TO:0/0 CS:0/0 Col:0/0 NAK:0/0<br>
| |
| − | OK<br>
| |
| − | }}
| |
| − | | |
| − | The trace above corresponds to the activated KNX module. Otherwise, below activation command is required.
| |
| − | {{Terminal |
| |
| − | 1=>'''line type L3 KNX'''<br>
| |
| − | OK, Boot Required!<br>
| |
| − | }}
| |
| − | | |
| − | Now KNX module is ready for operation and can be connected to KNX bus. Mind the polarity - it is essential for KNX bus.
| |
| − | | |
| − | == KNX group address concept ==
| |
| − | KNX bus is usually implemented as a decentralized system. Decentralized management is implemented within the devices, they are communicating directly to each other without recourse to hierarchy or network supervisory.
| |
| − | The communication between KNX communication objects (sensors and actuators) is made with telegrams sent to group addresses. The group addressing is based on the exchange of data coded with common rules between communication objects. Actuators can listen to several group addresses. Sensors however can only send one group address per telegram.<br>
| |
| − | When setting the group address via ETS, it can be selected as a “2-level” (main group/ subgroup) or “3-level” structure (main group/middle group/subgroup). The level structure can be changed in the project properties of each individual project. The group address 0/0/0 is reserved for so-called broadcast messages (telegrams to all available bus devices).<br>
| |
| − | [[File:KNX-GA-MainSub.gif]]<br><br>
| |
| − | [[File:KNX-GA-MainMidSub.gif]]
| |
| − | | |
| − | == Simple example ==
| |
| − | [[File:CM5-KNX-Sample2.gif]]
| |
| − | <br>
| |
| − | A simple installation shown above consists of a common KNX panel, CoolMasterNet with KNX module and power supply. This is a most simple but yet comprehensive example of the CoolMasterNet KNX based system. In real world installation can include a dozens of panels and a lot of other devices, but still integration principle will be the same.
| |
| − | <br>
| |
| − | * First, ETS should be used to create group addresses for communication objects provided by KNX panel. Let's assume following group addresses were created:
| |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | ! Object Name
| |
| − | ! Object Function
| |
| − | ! Group Address
| |
| − | ! R/W
| |
| − | ! Data Type
| |
| − | |-
| |
| − | | Switch object A
| |
| − | | Push button 1
| |
| − | ! style="text-align:center;" | 1/0/1
| |
| − | | style="text-align:center;" | W
| |
| − | | 1 bit {1.001} DPT_Switch
| |
| − | |-
| |
| − | |-
| |
| − | | Setpoint Temperature Output
| |
| − | | Control
| |
| − | ! style="text-align:center;" | 1/0/4
| |
| − | | style="text-align:center;" | W
| |
| − | | 2 bytes float {9.001} DPT_Value_Temp
| |
| − | |-
| |
| − | |-
| |
| − | | Setpoint Temperature Input
| |
| − | | Presentation
| |
| − | ! style="text-align:center;" | 1/0/5
| |
| − | | style="text-align:center;" | R
| |
| − | | 2 bytes float {9.001} DPT_Value_Temp
| |
| − | |-
| |
| − | |}
| |
| − | | |
| − | * Next, Indoor Units list should be retrieved from CoolMasterNet:{{Terminal |
| |
| − | 1=>'''ls'''<br>
| |
| − | '''<span style="color:#8080FF">L1.001</span>''' OFF 26C 28C Top Heat OK # 0<br>
| |
| − | '''<span style="color:#8080FF">L1.002</span>''' OFF 24C 24C Med Heat OK # 0<br>
| |
| − | }}
| |
| − | In this example KNX panel will control Indoor Unit L1.001
| |
| − | | |
| − | * Finally, communication objects have to be linked with CoolMasterNet functions.
| |
| − | | |
| − | Link Push button 1, it's group address is 1/0/1, with Indoor Unit L1.001 onoff function:{{Terminal |
| |
| − | 1=>'''knx group <span style="color:#80FF80">1/0/1</span> onoff <span style="color:#FF8080"><</span> <span style="color:#8080FF">L1.001</span>'''<br>
| |
| − | OK
| |
| − | }}
| |
| − | | |
| − | Link Setpoint Temperature Control (up/down buttons), it's group address is 1/0/4, with Indoor Unit L1.001 Setpoint (ST) configuration function:{{Terminal |
| |
| − | 1=>'''knx group <span style="color:#80FF80">1/0/4</span> ST <span style="color:#FF8080"><</span> <span style="color:#8080FF">L1.001</span>'''<br>
| |
| − | OK
| |
| − | }}
| |
| − | | |
| − | Link Setpoint Temperature Presentation (group address 1/0/5) with Indoor Unit L1.001 Setpoint (ST) feedback function. This time telegram will be sent from CoolMasterNet to KNX panel, that's why we put <span style="color:#FF8080">'''>'''</span> instead of <span style="color:#FF8080">'''<'''</span> like in previous commands.
| |
| − | {{Terminal |
| |
| − | 1=>'''knx group <span style="color:#80FF80">1/0/5</span> ST <span style="color:#FF8080">></span> <span style="color:#8080FF">L1.001</span>'''<br>
| |
| − | OK
| |
| − | }}
| |
| − | | |
| − | Read overall linkage status:{{Terminal |
| |
| − | 1=>'''knx group'''<br>
| |
| − | G000:'''<span style="color:#80FF80">1/0/1</span>''' [ On/Off ] <span style="color:#FF8080">'''<'''</span> '''<span style="color:#8080FF">L1.001</span>'''<br>
| |
| − | G001:'''<span style="color:#80FF80">1/0/3</span>''' [ Set temperature ] <span style="color:#FF8080">'''<'''</span> '''<span style="color:#8080FF">L1.001</span>'''<br>
| |
| − | G002:'''<span style="color:#80FF80">1/0/4</span>''' [ Set temperature ] <span style="color:#FF8080">'''>'''</span> '''<span style="color:#8080FF">L1.001</span>'''<br>
| |
| − | OK
| |
| − | }}
| |
| | <br> | | <br> |
| | + | The KNX functionality of CooLinkHub and CooLinkBridge is fully described in: [https://coolautomation.com/wp-content/uploads/sites/2/2020/02/cool-KNX-guidelines.pdf KNX Guidelines for CooLinkHub and CooLinkBridge (PDF)] |
