Difference between revisions of "The Barbican"
Tag: Reverted |
|||
| (14 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
==Designs== | ==Designs== | ||
<iframe key="wiki" align="right" width="100%" height="1150" level="" path="/gojs/samples/wiring24.html?cid=barbican_discussion.json&height=800px" /> | |||
<iframe key="wiki" align="right" width="100%" height="1150" level="" path="/gojs/samples/ | |||
<pre class="wikidiagrams"> | <pre class="wikidiagrams"> | ||
barbican_discussion.json Monitoring Architecture | barbican_discussion.json Monitoring Architecture | ||
barbican_meter_locations.json Heat Meter and Sensor Locations | barbican_meter_locations.json Heat Meter and Sensor Locations | ||
meter_installation.json Principles of calculating flow rates from temperatures | meter_installation.json Principles of calculating flow rates from temperatures | ||
barbican_wiring_1.json Wiring | barbican_wiring_1.json Wiring 1 | ||
</pre> | </pre> | ||
| Line 28: | Line 20: | ||
== Temperature Data == | == Temperature Data == | ||
==Heat Meters== | ==Heat Meters== | ||
| Line 40: | Line 32: | ||
File:Micronics2.png|A Node-RED flow has been created to read Micronics meters via Modbus (or any other Modbus device). This has been pasted into the controllers, containing all the registers and descriptions, and deployed. | File:Micronics2.png|A Node-RED flow has been created to read Micronics meters via Modbus (or any other Modbus device). This has been pasted into the controllers, containing all the registers and descriptions, and deployed. | ||
File:MicronicsBarbi1.PNG|The first Micronics heat meter provided data immediately as expected, matching values on the screen. This can be viewed in the Node-RED software in the debug window, where one can inspect the data telegrams being sent and received. [1, 3 ...] represents device 1, function code 3 (read register). The response should also start with [1, 3 ...] | File:MicronicsBarbi1.PNG|The first Micronics heat meter provided data immediately as expected, matching values on the screen. This can be viewed in the Node-RED software in the debug window, where one can inspect the data telegrams being sent and received. [1, 3 ...] represents device 1, function code 3 (read register). The response should also start with [1, 3 ...] | ||
File:MicronicsBarbi2.PNG|However, the second meter provided incorrectly formed responses and will require further investigation. | File:MicronicsBarbi2.PNG|However, the second meter provided incorrectly formed responses and will require further investigation. FIXED: The GND for the RS485 was into the wrong terminal. When corrected, the data matched heat meter display. | ||
</gallery> | </gallery> | ||
| Line 60: | Line 52: | ||
== Time Series Data Visualisation Using InfluxDB and Grafana == | == Time Series Data Visualisation Using InfluxDB and Grafana == | ||
<gallery heights="250" widths="400"> | <gallery heights="250" widths="400"> | ||
| Line 76: | Line 63: | ||
Grafana includes organisation, role and user management, making it straightforward to setup a dedicated client portal with dashboards customised to best show the data and allow analysis. A light theme has been used. | Grafana includes organisation, role and user management, making it straightforward to setup a dedicated client portal with dashboards customised to best show the data and allow analysis. A light theme has been used. | ||
Sections in Heating and Cooling can be expanded. | Sections in Heating and Cooling can be expanded. | ||
Latest revision as of 19:42, 3 February 2023
Designs
barbican_discussion.json Monitoring Architecture barbican_meter_locations.json Heat Meter and Sensor Locations meter_installation.json Principles of calculating flow rates from temperatures barbican_wiring_1.json Wiring 1
Drawings
CHW_Art_Gallery_-_Temporary_Heat_Meter_Locations
Temperature Data
Heat Meters
See Micronics Heat Meters for information on how to connect Micronics Heat Meters.
A Node-RED flow has been created to read Micronics meters via Modbus (or any other Modbus device). This has been pasted into the controllers, containing all the registers and descriptions, and deployed.
The first Micronics heat meter provided data immediately as expected, matching values on the screen. This can be viewed in the Node-RED software in the debug window, where one can inspect the data telegrams being sent and received. [1, 3 ...] represents device 1, function code 3 (read register). The response should also start with [1, 3 ...]
However, the second meter provided incorrectly formed responses and will require further investigation. FIXED: The GND for the RS485 was into the wrong terminal. When corrected, the data matched heat meter display.
Data Storage Locally and to Dropbox
Data subscribed to is stored on the server locally into csv files.
A file browser utility is included on this wiki with a user account setup to provide simple access to stored CSV files.
Every day these files are sent to Dropbox, and then can optionally be purged from the server.
We are currently storing all /dat/ incoming MQTT data, fed from field trials. This will ensure we retain long-term records of all operational data, from all field trials, down to 1 second resolution. It will be a lot of data, but Dropbox has more than enough room.
Time Series Data Visualisation Using InfluxDB and Grafana
Data is fetched from an InfluxDB database using the FLEX query language.
Data is then post-processed, renaming fields.
Data is further processed based on type to apply colours and units
Client Dashboard
Grafana includes organisation, role and user management, making it straightforward to setup a dedicated client portal with dashboards customised to best show the data and allow analysis. A light theme has been used.
Sections in Heating and Cooling can be expanded.