Skip to content

Revised telegrams 0x0004, 14, 16 and 18 #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Sbried wants to merge 1 commit into
base: main
Choose a base branch
from
+115 −114
Open

Revised telegrams 0x0004, 14, 16 and 18 #139

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions static/data/telegram_metadata.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"0x0001": {
"name": "ELECTRONICS-MODULE PRODUCTION INFORMATION BLOCK",
"name": "Electronics-Module Production Information Block",
"usedIn": "Various controllers, thermostats and boilers",
"description": "This block contains production information of the *electronics module* hardware (e.g. ACU-LO, ACU-MH, HRV_CU, ...).",
"class": "Const",
Expand All @@ -10,7 +10,7 @@
"type": "info"
},
"0x0002": {
"name": "MODULE IDENTIFICATION BLOCK",
"name": "Module Identification Block",
"usedIn": "Various controllers, thermostats and boilers",
"description": "This block is used to universally identify the module on the bus when a bus data logger is connected. **Note: Distribution**: ``BROADCAST-ON-POWER-UP``: Only valid for bus members, which could change the content of the constants during the runtime of the EMS system and do not require a reset of the system (e.g. iCom).",
"class": "Const",
Expand Down Expand Up @@ -388,10 +388,11 @@
"0x0004" : {
"name" : "Boiler Identification Block",
"usedIn" : "tbd",
"description" : "In this block a definition of the boiler is given. The information is used for external devices which need information about the possibilities of the boiler. **Important**: Values in this block cannot be changed via the bus! **Note: EMSType** - ``EMS1.0-AND-EMS2.0``: I0-1, I2, I3.0-3.2, I3.5, I3.6, I3.7, I4, I5, I7, I8, I9, I10, I12, I18-19, I22, I23, I24, I25-26, I27, I28, I29, I30, I31, I32 - ``EMS1.0``: all other indexes",
"description" : "In this block a definition of the boiler is given. The information is used for external devices which need information about the possibilities of the boiler. **Important**: Values in this block cannot be changed via the bus! **Note: EMSType** - ``EMS1.0-AND-EMS2.0``: offset 0-1, offset 2, offset 3.0-3.2, offset 3.5, offset 3.6, offset 3.7, offset 4, offset 5, offset 7, offset 8, offset 9, offset 10, offset 12, offset 18-19, offset 22, offset 23, offset 24, offset 25-26, offset 27, offset 28, offset 29, offset 30, offset 31, offset 32 - ``EMS1.0``: all other indexes",
"class" : "Const",
"emsCategory" : "EMS1.0 and EMS2.0: detail in bus variable description",
"distribution" : "BROADCAST-ON-POWER-UP, UNICAST-ON-REQUEST",
"notes" : "",
"type" : "info"
},
"0x0018" : {
Expand All @@ -401,6 +402,7 @@
"class" : "Monitor",
"emsCategory" : "EMS1.0 and EMS2.0: detail in bus variable description",
"distribution" : "BROADCAST-ON-POWER-UP; distribution duration = 10s; timeout = 240s, UNICAST-ON-CHANGE, BROADCAST-PERIODICALLY, UNICAST-ON-REQUEST",
"notes" : "",
"type" : "info"
},
"0x0016" : {
Expand All @@ -415,7 +417,7 @@
"0x0014" : {
"name" : "EMS Simulated System Time",
"usedIn" : "tbd",
"description" : "This block contains the simulated system time of the EMS. The simulated system time is a relative time, which starts counting after the first power up and is incremented each minute as long as the power is available. This timer is stored in EEPROM once an hour. This timer is to be used as a reference for the relative time, if this is stored in the locking and blocking error register and in the maintenance request register, i.e. if no absolute time from DT6 is available. **Note: Distribution** Legacy products (EMS1.0) only implemented ``UNICAST-ON-REQUEST``. For backwards compatibility, in this case an HMI needs to request DT20 to reflect the runtime of the system. New products shall support distribution ``BROADCAST-PERIODICALLY`` with a periodicity of *one hour*.",
"description" : "This block contains the simulated system time of the EMS. The simulated system time is a relative time, which starts counting after the first power up and is incremented each minute as long as the power is available. This timer is stored in EEPROM once an hour. This timer is to be used as a reference for the relative time, if this is stored in the locking and blocking error register and in the maintenance request register, i.e. if no absolute time from telegram 6 is available. **Note: Distribution** Legacy products (EMS1.0) only implemented ``UNICAST-ON-REQUEST``. For backwards compatibility, in this case an HMI needs to request telegram 20 to reflect the runtime of the system. New products shall support distribution ``BROADCAST-PERIODICALLY`` with a periodicity of *one hour*.",
"class" : "Monitor",
"emsCategory" : "EMS1.0 and EMS2.0: detail in bus variable description",
"distribution" : "BROADCAST-ON-CHANGE; distribution duration = 3600s, UNICAST-ON-REQUEST, BROADCAST-PERIODICALLY",
Expand Down
Loading