CalPlug Quarterly Research Report Template

YOUR REPORT TITLE / PROJECT NAME

YOUR NAME
SUBMISSION DATE
QUARTER FOR SUBMISSION
UNITS/DESIGN UNITS TAKEN

Abstract:
What this section should look like: The abstract section is an overview of all of the
other sections. Think of this as an at-a-glance review of the report. It should
contain elements of each section and paint a picture of the work that was done.
Abbreviated Sample: In CalPlug this quarter I was the leader of a team developing a
WiFi Internet of things (IoT) load controller for pool pump control. As a group we
designed and coded the firmware and a simple application to demonstrate the
function of the prototype device. My portion of the project was specifically related
to firmware design. By the end of the quarter we showed this device could control
loads and measure the power of connected devices. In the next quarter we seek to
develop a web based controller application and an integrated command and control
system.

Background/Introduction:
What this section should look like: In this section you discuss why you did what you
did. What is the larger purpose of your work? What is the motivation to do what
you did? Why does anyone care? What prerequisite knowledge needs to be
introduced to the audience to make sense of your work? Please feel free to cite
sources. Make sure to define all acronyms and discuss technical terms properly.
Abbreviated Sample: The internet of things (IoT) is a growing field [1]. Load
controllers that operate at a long distance in residential applications are becoming
more commonplace. A load controller for pool pump applications is something that
is currently not on the market. Pool pumps are a significant residential electrical
load. Control of electrical loads in times where power production is reduced or
demand is increased to the point where it impinges upon generation is referred to
as demand response. Control of pool pumps provides the ability to create a new
method of demand response. The system we built this quarter is a demonstration
proof-of-concept device used to show how this system would work. MUCH MORE
CAN/SHOULD BE SAID.

Materials and Methods / Development Process:

/Materials and Methods is typically used for research
reports, but in some cases for build projects
Development Process may be more appropriate both
specify the materials and methods used. Please refer to
other research papers to see more details on how this
section is crafted.
What this section should look like: In this section you would discuss what you did
and how you did it. Please discuss how tests or evaluations were performed, but do
not discuss results in detail. In discussing what you have done in your projects, DO
NOT GIVE A PLAY-BY-PLAY STORY OF YOUR WORK! DO NOT DISCUSS YOUR FAILURES
IN DEPTH! Research naturally goes down dead end paths, please summarize the
successes of your projects and do not dwell on the failures. Unless there is
something to say here, avoid discussing failures or extraneous details in depth.
Failures generally mean something did not work properly, and unless this fail point
is positively identified, knowing a failure occurred and took up your time is pointless
to discuss. If you solved a non-trivial failure in a creative way, this is a great point
to discuss. Please discuss your work at a technical level as to what you
accomplished and how you accomplished it. Please be reasonably specific with the
equipment that was used and how it was used. Please be sure to discuss both your
individual parts as well as the accomplishments of your group. Use the inclusive
we (as opposed to I) liberally. Please use figures liberally in your document. Refer
to these figures in your document, and bold the marker. Please write in an
academic style with as little reference to yourself as possible (I) given the context of
what you are discussing this is not a diary entry or a travelogue, it is scientifically
worded academic writing. Avoid use of contractions or colloquial phrases.
Abbreviated Sample: For our load controller we developed a proof of concept
hardware demonstration system based on the Expressif 8266 chipset as a part of a
NodeMCU demo board. For current sensing we used an Allegro ACS712 current
sensor we connected to the analog input of an Arduino Uno board. This board
features the Atmel ATMEGA 328 microcontroller. The control logic outputs are used
to drive three relays (Crydom DC60S3) that are connected to loads. We followed UL
(underwriters laboratories) and NEC (national electrical code) for device assembly.
The firmware was written using the Arduino IDE development environment. My role
in the project was the development of the firmware. The software side was written
in Processing 3.0. In Figure 1, we represent a system diagram of our project.
Initially Python was intended for the user interface for device control but due to the

state of the pre-existing software libraries, Processing was used in place of Python.
MORE DETAILS SHOULD FOLLOW ABOUT
DEVICE DESIGN AND CONSTRUCTION.

Testing Results and

Discussion:

Figure 1: Please use figures liberally

in your report. These should be high
quality images or drawings. Please
avoid hand sketches CAD /draw these
up. Please refer to your figures in the
text.

What this section should look like: In this

section you should discuss the results of
any tests or evaluations in addition to a
discussion of your project. Typically
testing results (or experimental results)
are presented in a dedicated section. Results can be included with your discussion
if this section is short. Typically you just need to describe the results. Discussion of
these results and their relevance to the project can be discussed in the discussion
section. In the discussion section, please describe how the results of your
experiments and/or the results of your experiments relate to the project as a whole
or to the wider concepts mentioned in your introduction. Please draw in the
relevance of your current work and the future parts of your project. You can in the
end of this section mention what you have personally learned or got out of the
project, but please be brief here.
Abbreviated Sample: Our load tests
showed system stability in all functional
modes in addition to load measurement
capability up to 20 Amps. In Figure 2,
we present a graph showing the measured
DAQ value versus nominal current. Our
message encryption system was stable in
all modes of operation. We have achieved
all stated goals of the project thru the
Figure 2: Please use figures liberally
development of a functional prototype.
in your report. These should be high
Next quarter we plan to extend our
quality images or drawings. Please
firmware to permit integration with other
avoid hand sketches CAD /draw these
up. Please refer to your figures in the
sensors and actuators so the developed
text. For graphs, please clearly label
device can be expanded into a unit of an
axes and make sure the graph clearly
integrated command and control system.
During the course of this project I developed a clear understanding of how IoT
communication scheme can be used to control IoT edge devices. I also gained
experience in firmware coding with Arduino Uno boards. MUCH MORE CAN BE SAID
HERE.

Conclusion:
What this section should look like: In this section you should review what was

said in your report. This should review the highlights of your report thus far.
You can include some further reaching points or draw connections here as
well to close your report. This section should generally be brief.
Abbreviated Sample: During past quarter we developed a load controller

intended to control pool pumps via WiFi. In addition to development of the

hardware and firmware portion of the device, we also demonstrated a
sample user interface using Processing 3.0. We also integrated encryption to
allow secure commands and responses to be transferred to and from the
device. Initial tests showed acceptable device stability and accurate power
measurement. In the future we intend to expand the user interface into an
integrated command and control system. The work on this project we have
performed for CalPlug can be used to develop a line of controllers that can be
used for effective demand response. The potential impact on the California
economy can be substantial with a capability of saving over an estimated 10
MWh annually in peak load conditions [2].

References:
What this section should look like: In this section please include any citations.
Please follow a standard bibliographical format and be consistent.
Abbreviated Sample:
[1] Mazhelis, Oleksiy, et al. "Internet-of-things market, value networks, and business models: State of the
art report." University of JYVSKYL, DEPARTMENT OF COMPUTER SCIENCE AND INFORMATION
SYSTEMS, Technical Reports TR-39 (2013): 13-14.
[2] Albadi, Mohamed H., and E. F. El-Saadany. "A summary of demand response in electricity
markets." Electric power systems research 78.11 (2008): 1989-1996.