The Barbican

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

Temperature Data

Heat Meters

U1000MKII_WM_Issue_1.1

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. It is the same setup entirely, so the only difference could be the polarity is reversed on the RS485 line.

Data Storage via Dropbox

Data subscribed to is stored on the server locally into csv files. Every day these files are sent to Dropbox, and then 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.

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