Difference between revisions of "KNX"
| Line 39: | Line 39: | ||
== Simple example == | == Simple example == | ||
| + | [[File:CM5-KNX-Sample.gif]] | ||
| + | |||
== KNX commands reference == | == KNX commands reference == | ||
Revision as of 01:54, 28 April 2015
Contents
KNX module installation and activation
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 on line L3. Run line command to check if KNX module is already activated.
| >line L1: DK Master U00/G00 myID:0B |
The trace above corresponds to the activated KNX module. Otherwise special activation string should be provided. To get activation string contact CoolAutomation and specify a serial number of the CoolMasterNet device where KNX module has to be activated. Once activation string is provided by CoolAutomation it should be entered as a regular command.
| >@=1A52330B97FD78A88091543F26488FF8 OK, Boot Required! |
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.
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).
