Difference between revisions of "The Barbican"

From Open Source Controls Wiki
Jump to navigation Jump to search
Line 34: Line 34:
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.  It is the same setup entirely, so the only difference could be the polarity is reversed on the RS485 line.
File:MicronicsBarbi2.PNG|However, the second meter provided incorrectly formed responses and will require further investigation.  It is the same setup entirely, so the only difference could be the polarity is reversed on the RS485 line. FIXED: The GND for the RS485 was into the wrong terminal. When corrected, the data matched heat meter display.
</gallery>
</gallery>



Revision as of 17:48, 21 September 2022

https://www.barbican.org.uk/

Designs

barbican_discussion.json Monitoring Architecture
all_lorawan.json All LoRaWAN 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
heatweb_barbican_graph1.json Graph 1

Drawings

CHW_Art_Gallery_-_Temporary_Heat_Meter_Locations

Barbicanschem1.png

Temperature Data

Barbigraph1.PNG

Heat Meters

U1000MKII_WM_Issue_1.1


See Micronics Heat Meters for information on how to connect Micronics Heat Meters.


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.

Csvfiles1.PNG Csvfiles2.PNG

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.

Savetodropbox.png

Time Series Data Visualisation Using InfluxDB and Grafana

Barbigraf1.png


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.


Bdash1.PNG


Sections in Heating and Cooling can be expanded.


Bdash2.PNG