EnergyMonitoring.md

Energy Monitoring

By using the monitoring MCU on the elastic node you can measure the power the elastic node consumes during an experiment. You should be familiar with the the WriteOwnProgramGuide.

Main MCU

Example

In the monitoring example each second one led more blinks. After that all turn off and the experiment starts again. This happens 3 times and than the experiment is stopped.

You can upload the code for the main MCU as usual with

$ bazel run //app/examples:monitoringExample_upload --platforms=@AvrToolchain//platforms:ElasticNode_v4

To check if everything works see 'Get results' underneath.

Inclusion in own code

Everything explained in this section can be found implemented in the monitoring example.

The code for the main MCU needs the inclusion

#include "ElasticNodeMiddleware/ElasticNodeMiddlewareMonitoring.h"

and the dependency in bazel

"@ElasticNodeMiddleware//:ElasticNodeMiddlewareMonitoringLib",

A slave must be initialized at the beginning of the code:

IIC_slave_init(MY_IIC_ADDRESS);

MCU running states

There are different mcu running states, these are captured when reading the measurement result to connect each measurement with a state of the experiment. Therefore you need to declare a uint8_t:

uint8_t state_of_the_mcu;

For easy use it is recommended to define your own running states with a typdef like in the monitoring example. There are 16 different states possible, whereby the sleep mode should always be 0 and the end of measurement 15:

typedef enum {
    SLEEP_MODE = 0,
    OWN_STATE_1 = 1,
    //possible states from 2 to 14
    END_MEASUREMENT = 15,
} mcu_running_state;

When the state is changed to 'SLEEP_MODE' the sending of measurement data is paused until it is changed to another state. The 'END_MEASUREMENT' state stops the sending of measurement data completely.

Now you can change the state to the corresponding state of your experiment:

elasticnode_monitoring_change_running_state(OWN_STATE_1, &state_of_the_mcu);

Sample rate

Warning: The sample rate change functinality is experimental for now and in the realease v1.0.0 of the elastic node monitoring not actived.

You can define how often a measurement should take place.

You can change the sample rate like this at any time:

elasticnode_monitoring_change_sample_rate(CURRENT_SAMPLE_TIME_10ms);

The possible sample rates are defined in ElasticNodeMiddlewareMonitoring.h. The default is 80ms.

Monitoring MCU

The code used in this section is located in the ElasticNodeMonitoring repository, which can just be cloned.

The code for the monitoring MCU usually does not change. For uploading code to the monitoring MCU you need to connect the programmer to it. The connections are labeled here. The platform changes to 'ElasticNode_v4_monitor' as it is another type of MCU.

$ bazel run //app:measurement_upload --platforms=@AvrToolchain//platforms:ElasticNode_v4_monitor

Get results

You need to set the serial port to your elastic node and programmer and the path to your data folder in the config.py in the scripts folder. The micro-USB as well as the programmer should be connected to the monitoring MCU. Now you can run the python script with

$ bazel run captureMeasurement argument

Table of arguments:

argument	function
capture	the output is written in a .csv file in the data folder
print	prints the current output to the console
live	draws a graph of the power consumption
debug	writes debug output in hex to the console
reset	resets the monitoring MCU