Welcome to MODEL Software BBMonitor

I have stopped work on this project -- the original description follows this explanation:
This is the email that I sent to https://sense.com/

Congratulations on your development.
I know it will work.
In fact, I have done what you have done.
With one minor difference - you completed yours !!

Having spent 13 years off and on with this concept (more off than on). I am relieved to see completion. I have ordered your sense system with solar and expect delivery within a day.

In 2004 I was developing substation controls and an engineer (John Richards) came to me and said the company was being required by the PUC to do an audit of equipment in people's homes and he imagined a computer hanging off transformers that analyzed the signatures of the different equipment and logged the times and amps of each. As it turned out we didn't have to do an audit. He has retired since. But his idea stuck with me. I started with an amp clamp and voltage transformer tied to a PC stereo sound card. At 44100 Hz, I could get 735 samples per cycle. I Used the previous cycle as base line to look for changes in amps, volts, reactance, peak location, area and additional cycles to track peak and decay amps and reactance changes. I was recognizing lamps turning on and off, and I was excited to recognize my fax machine when it started up. About 2 seconds later realized I needed to filter out the carriage return / line feeds from my log. I know you've been there. I see you are using an 1GHz ARM processor. I'll bet that is a Raspberry PI under the cover. My Pi is setting near my desk connected to a Analog Devices 4 channel ADC with a driver that I can't get to load. I have 3 sets of split coil current amps. All of them too bulky to fit in my control panel. Two sets cost more than your entire product.

You came from voice recognition -- I meandered through bird song recognition:
http://www.modelsw.com/Android/BirdingViaMic/BirdingViaMic.php

I am going to take you up on your statement:
We welcome any and all feedback, just drop us a note

I suspect I am going to need you in a month or two. I ordered a solar system with a battery backup for 4-20 amp circuits. Two years and 4 months, one PUC testimony, and one PUC complaint later (see attached email) the utility "welcomed" me. I have signed the contract. In the meantime the battery is in its third configuration. But installation is still not scheduled. (I think early adaptor might be the phrase used.) This is a link to the owner's manual: https://www.google.com/search?q=Powerwall+2_AC_Owners_Manual_E.pdf&ie=utf-8&oe=utf-8 Page 9 is an overly simplified schematic.

I would like to see you in 3 phase and heavy industrial analysis and I know you will get there. I recommend the Rogowski coil because of its ability to handle overcurrent, but you will have to integrate it.

If I can help you in any way, I will be glad to.
Thank you, best wishes and Congratulations !!

Gerard Gilliland
gerardg@modelsw.com

BBMonitor: Monitor energy usage and build Energy Profiles.

• Home - MODEL Software Home page.
• Main - BBMonitor Home page (this page).
  The name BBMonitor is short for Big Brother Monitor. (George Orwell 1984 -- Big Brother is watching you.) Although this has negative connotations, if connected at the local power meter, it monitors electrical usage and reports back to you and thus allows you to be more energy conscious. If connected at a transformer, it could be used by local utilities to better predict area usage and would be more accurate than a "survey". It may have wider applications such as predictive maintenance testing of in-service motors, generators, and other reactive or resitive loads.

• Define - Define a profile.
  The profile has been saved during the Monitor process. Define is really clearifying the profile by renaming and extending the description of it and optionally building an XML file of it and viewing the profile. First, you should rename the event or group of events. When an event occurs and a profile can not be found to match it, a new profile will be created. The temporary name will consist of zUnknown plus the EstimatedWatts plus Res if resistive, Ind if inductive, Cap if capacitive, or Cpx if complex (typical of solid state devices), plus On if an increase in Amps occurred or Off if a decrease plus a number to make it unique. For example: zUnknown256ResOn619. When you rename it you can follow the recommended list in the table tblNamingConventions. For example: a 250 watt resitive lamp could be named "LmpRes250On". Or you could be more creative: "Reading Lamp in the Study turned On". The Off event profile from Steady State is typically not similar enough to the same event turning On. Thus there are typically pairs with On in one name and Off in another. To Define the wave, select the WaveName from a dropdown. The WaveFilePath (the binary data file where the event was captured or recorded) should be correct but can be changed if that file has been moved or renamed. A Description can be added. The event can be excluded from the log if desired but the watts associated with the event will still be included in the TotalWatts. An example of excluding an event is Printer Print Line. You would want to know a printer was turned on and began printing but not when each new line was printed. NominalWatts (found on the product package or literature) can be entered. An Update button will update the text fields. The Export button will build an XML file and post the link on the bottom of the Define page. Clicking on the link allows you to see the event graphically or numerically. A third section allows you to delete an event or group of events. If you are not comfortable with these you can test the name with a select statement in the FreeformQuery before you rename or delete events. Once you delete an event it is gone. However when the event occurs again if it can't find a match it will create a new profile and save the binary file and record its location in the WaveFilePath. You can delete the binary file where the event was recorded but then you can't "Define" the event. However, the profile will continue to be recognized even without the associated binary file when that event occurs.
• Monitor - Monitor energy usage.
  This is the heart of the process. It sits in an internal loop monitoring the amps each cycle. If amps change by a defined amount (slightly higher than noise), then an analysis begins. It then compares the just recorded amps, watts, amps decay, reactance, peak amps, and peak location over several cycles with the profiles that have been previously been saved. If a match is found it is logged, else the unknown event is given a name and this new event is logged and stored along with the existing profiles. Click on the Run button to start the monitor process. Click the Stop button to end the process. In the table tblChannelCriteria The MinStart, MaxStart, and Adjust columns contain the criteria that limit the records being analyzed. The larger the number of Records (as compared to other rows), the less efficient the process it. That is, the monitor has to look through more records to chose the profile. The fewer the number of Records the more efficient the process is up to a point where no records are returned. Then the process fails to chose a profile and must create a new one. The Adj column shows the number of times the analysis is tightened (when negative) to narrow the number of Records or loosened (when positive) to widen the number of records in the profiles being compared. The ClearCriteria button clears the Records and Adj columns. Clearing the Records and Adj columns does not have anything to do with the analysis of profiles. But smaller numbers in these columns will help you see the results if you decide to change MinStart, MaxStart, or Adjust.
• View Log - BBLog, Usage, Hourly, Plot and Realtime reports.
  BBLog shows the Date and Time, Event, State (On/Off), Leg, InterDecay, EstimatedWatts, TotalWatts, Confidence, and Efficiency. InterDecay is a flag that if 1 this event interupted the previous. That is, the previous event did not have time to decay to stable watts before this event occurred. This can be normal if the two events are tied together such as a power on followed by a fan start. Or it can be abnormal if the events randomly occur. The Leg shows which physical power leg the event occurred on: 1, 2 (each 120 Volt) or 3 if both (240 volt). Confidence (percent) is how comfortable the monitor program is in selecting the correct event. Efficiency (percent) is how many records were analyzed to narrow down the selection to the correct event.
  The Usage report converts Watts and TotalWatts to WattHours and AccumulatedWattHours using Delta (seconds) between events, and adds the Rate and Amount.
  The Hourly report shows the EventGroups (Events with On and Off removed) as rows and total WattHours associated with the event in the hours column.
  The Plot report is a graphic representation over the selected period of the TotalWatts.
  The Realtime report displays the events as they are recorded (within the length of the individual binary files). This is the best report to watch when renaming an event because you can cycle an event (for example, turn a lamp on and then off) see what the name of the event is that cycles and then rename it to something meaningful.
  

• Freeform Query - for analysis of the tables and data.
  This allows you to analyze or modify the data. (Use MySQL valid queries.)
  
• Tables - Underlying Tables Supporting the BBMonitor Database.
  

Notes:

• See Energy Profile Exchange to View, Upload and Download Energy Load Profiles.
• Double Click on date fields to bring up a calendar.

© Copyright 2011, 2013 by MODEL Software - All rights reserved.	You may send us an email: