curious.bio/smart-energy-monitor
4
0
Fork 0
Code Issues 6 Pull requests Packages Projects Releases Activity
smart-energy-monitor/software/firmware/energy-monitor/README.md

6.4 KiB
Raw Blame History

Energy Monitor

Our energy monitor is based on the openenergymonitor.org project (Licence GNU GPL V3).

It uses our HelTec Wireless Stick. This - of course - can be replaced by a cheaper ESP32 module.

Power Measurement is done by a SCT013 clamp (100A:50mA).

Build the hardware

Used materials

  • ESP32 module (e.g. Heltec Wireless Stick)
  • 3 x SCT-013-100 (100 A), see: http://openenergymonitor.org/emon/node/156
  • 6 x 10 kOhm Resistors 1/4 W
  • 1 x 22 Ohm Resistor 1/4 W (TODO: I am using a 47 Ohm Resistor to be replaced)
  • 3 x 10 uF Elko 10 V
  • 3 x 3,5 mm audio jack connector

PinOut

PinOut

We use A1, A2 and A3 because they are free (most ADCs are already used on the HelTec Board)

Sensors

The SCT-013 sensors are small current transformers (SCT). They have a ferromagnetic core that can be opened and in which we can enclose our conductor. This conductor is the primary winding and the secondary winding is fixed in the sensor and can have 2000 turns. This gives us a ratio of 1:2000 as an example.

When AC current flows through the conductor, a magnetic flux is generated in the ferromagnetic core, which in turn generates an electric current in the secondary winding.

I could not meassure "small" power consumptions (like a LED lamp or a light stripe, as the magnetix flux in the ferromagnet core seems to be too small).

clamp on wire

I was able to measure high loads (like a heater the can be switched between 1 kW and 2 kW).

heater

Make sure the clamp is always positioned towards the consumer, otherwise it does not work. There is a small arrow on the case.

point the clamp

Attention: I could not measure any meaningful values on the "cable". I had to go to the wire.

cable

Breadboard

Let's start with a simple breadboard layout.

Breadboard Photo of breadboard

To understand this, have a look at this plan:

Plan

R1 & R2 are a voltage divider that provides the 1.65 V source. We use 10 kΩ for mains powered monitors. If we want to run on batteries, we have to choose differnt ones (like 470 kΩ resistors to keep the power consumption to a minimum).

Capacitor C1 has a low reactance - a few hundred ohms - and provides a path for the alternating current to bypass the resistor. A value of 10 μF is suitable.

R3 is the burden resistor. Ideal burden would be 19 Ω. As this is not a common value, you could choose 18 Ω or 22 Ω (I am still using a 47 Ω restistor, that has to be replaced).

See the Fritzing file for details.

Code

Print to serial out

Start with a simple code that just prints the values. The code is quite simple, as we can use the existing EmonLib libary V1.1.0 by OpenEnergyMonitor.

Check out the small amount of code to print the values to serial out. This piece of code is based on on Thomas Edlinger's code for Edi's Tech Lab.

The only interesting part is this line:

  emon1.current(current1Pin, 8);  // Pin and Calibration

The calibration value "8" was done with a Fluke multimeter (and maybe a not so ideal burden resistor).

The code just prints the current power consumption to serial out:

16:28:18.915 -> 2853.16 Watt  -  12.41 Ampere
16:28:19.998 -> 2854.63 Watt  -  12.41 Ampere
16:28:21.119 -> 2850.93 Watt  -  12.40 Ampere
16:28:22.207 -> 1702.19 Watt  -  7.40 Ampere
16:28:23.289 -> 400.62 Watt  -  1.74 Ampere
16:28:24.367 -> 94.42 Watt  -  0.41 Ampere

Post to MQTT

Boot up MQTT

First, boot your local server infrastructure:

docker-compose --file software/container/docker-compose.yml up

Credentials

To connect to your Wifi and access your MQTT server you have to add this to an environment header file:

// Replace with your network credentials
#define secrect_ssid "Guest"
#define secret_password "guestguest"
#define mqtt_server "192.168.2.103"
#define mqtt_port 1883
#define mqtt_prefix "/iot-platform/energy-monitor/test-device"

The mqtt_server in tis example posts to my local IP adress. The Wifi network is a Guest network I just created for this test.

The mqtt_prefix should be different per device, as this is the topic prefix used to identify the device.

Testing

You can subscribe to your local MQTT server and subscribe to all or just the interesting topics:

mosquitto_sub -h localhost -t '#' -p 1883 #all
mosquitto_sub -h localhost -t '/iot-platform/energy-monitor/test-device/ampere' -p 1883 #current
mosquitto_sub -h localhost -t '/iot-platform/energy-monitor/test-device/watt' -p 1883 #power

Interesting code blocks

Posting to MQTT is quite simple. After setting up Wifi and connection to the MQTT server, it's just a few lines of code:

  client.publish(concat(mqttPrefix, "/watt"), powerArray);
  client.publish(concat(mqttPrefix, "/ampere"), irmsArray);

Have a look at the complete example.

Simulator

If you just need random inputs (without using the actual hardware), you can simply modify my short shell script.

Links