20170111 - device online for 1 min @0948 - someone on roof?

20170112 - device offline at 1524, surprised if that's power? check

20170113 - device work @ 0933 briefly - see early-wake-theory below

           early-wake-theory:

            if device goes below 11.1V while sleeping then it won't wake on

            the RTC but will wake when the solar charger sees 12V again,

            at which point it will see that it ought be asleep unti 1100

            and so it dozes until then - possibly means that we're keeping

            the kerlink up after the eurotech has gone to sleep, otherwise

            why is the voltage still dropping?

            - I modified /etc/stopproc.sh to stop pbm and call ker-off

20170124 - took that out again, added code to pbm binary

           looks like that fix didn't do it, need to test

           some more when at node Monday

20170118 - fixed kerlink not powering off - both s/w and wiring!

           we re-charged unit from mains around 1400-1430, after

           that back to solar, hopefully voltage on 19th will

           behave

20170124 - validated that ker-off does remove voltage from kerlink

           power input; found a code path in pbm that wasn't 

           calling ker-off, testing of that needs to be finished

           when device has power again. Note: left device with

           sleeping only set from 1440 to 1455 so it'll wake 

           early on 25th (not likely to get more power today

           due to sun angle)

20170125 - eek, I'd put the ker-off code in the wrong place;-)

           fixed now I think finally

20170126 - seems to have worked out - node went down @1600

           on 25th with battery @12.52V, awoke on schedule 

           @1102 on 26th with battery @12.49V and weather was

           overcast all morning (that I saw:-) on the 26th,

           node is drawing about 0.9-1.1A around 11am

           probably only safe to fully believe stats from

           here on, though some info can be gleaned from

           earlier data no doubt

20170127 - there was a wake @ 10:02 - might be ok though, node

           went into long standby at 1459 on the 26th so was

           close to out of power (11.34V)

20170128 - looks like basil was rebooted about 17 hours ago 

           (around 1800 on the 27th?) (down is also down)

           so vpn wasn't up - not sure if client will connect

           before it's next reboot, hasn't so far after 5

           mins (vpn manually restarted @ 1140) I'm guessing

           there was a power off event

20170201 - basil reboot: there was a bridge0 that was ifup'd

           and that might be interfering somehow, took that

           down, we'll see @ 1100 if that helps, if not, I'll

           wanna go check unit physically (also could be 

           SIM card crap, check that too - SIM seems ok, has

           7GB and 8 days left) 

           Turns out that the SIM was not ok - the "add on"

           thing is not being used and the balance was down

           to 0.65c or actually maybe negative. Topped the

           fecker up.

           Clock was still on jan 29 today, odd - maybe

           rtc isn't working right? also that might interact

           with vpn, not sure - actually no, it was that

           the node thought it was 1600 on the 29th so it

           went to sleep, wonder when it'd have awoken if

           Kerry hadn't hit the physical switch?

           I have the kerlink boottimes.txt that could be

           used to fix the boot times and hence battery

           log of the loradtn node if we want

20170202 - odd timing - node woke @1047 - is power still being

           consumed?

           also odd vpn pattern - new client IPs every few

           minutes, check node's syslog later

20170206 - looks nominal at the moment, nice weekend weather

           helps:-)

20170213 - VPN went down at 1427 in good bright weather with

           battery nicely high  (13.28V at 1357), GSM balance

           also fine, but maybe it's the add-on fecking thing

           I added 3GB of data (good 'till March 15) which'll

           take effect at next connect (reboot?) it didn't

           reconnect in 5 mins anyway. Or, it could just be

           a DHCP lease meets VPN issue. Check tomorrow.

20170214 - yep, yesterday's outage was gsm related - pppd saw

           a disconnection. Device stayed powered up 'till

           1600 as planned, but had no n/w. Once it powered

           up today, it was back on line. Must check that

           again on March 10th (set a reminder:-)

           Meanwhile no sun today, so node will likely go

           to sleep in an hour or so (now @12.27V and drawing

           0.9A) 

20170222 - seems like there is some browning out happening,

           today and on the 18th - might be the higher load

           means that the thresholds aren't right for this

           setup with voltage is marginal (e.g. 11.5V)

20170228 - graphs show node up yesterday but I didn't see 

           that from CLI, check it out

           also - redo scripts to add March

20170308 - we added the code for the 2nd ammeter for the 

           device under test (DUT). Noted that the voltage

           calibration may need a bit of work, but not

           enough to make a change now as that'd invalidate

           data since Jan. Worth doing more before any 

           further deployment. The new pbm code was tested

           on the bench and deployed to the rooftop node

           at 1500 today. We'll follow up with the new

           phidgets/veroboard assembly shortly (so DUT

           figures for now will be garbage) some voltages

           seen on the bench power supply and as seen by

           pbmd are:

              Bench                 pbmd

              11.6                  11.87

              11.8                  12.10

              12.8                  12.97

              13.2                  13.44

           Current measurements OTOH, seem accurate 

           enough to within 100mA or so.

20170310 - veroboard with new ammeter deployed today (so 

           some outage this morning) DUT readings showing

           about 300+/-40mA

20170317 - added a graphic showing the DUT power consumption

           vs. the overall power log

20170321 - extended sripts to cover to end-April

           also noticed that SPIKE readings are being generated

           when voltage is identical in two successive readings

           probably a pbm bug, but not a biggie

20170408 - topped up SIM card - balance was small and device

           offline on a sunny day, see if fixed with tomorrow's

           reboot

20170409 - seems like that's it, up nomimally this am, and

           past three days readings seem corrupted (no NTP to

           set date, odd that it falls back to the last "good"

           day, something to check out)

20170416 - seems like the root FS is full on DTN node, note

           sure since when, cleaning today. Also can't ping

           the kerlink, not sure if connected. Need a way 

           for unattended upgrades to not fill / based on

           adding stuff to /boot. Fixed that manually and

           did a reboot at 1500 IST... unit came back up

           fine, but still no sign of kerlink. Will have to

           go over and see Tuesday

           oops - node went offline in the middle of an

           apt get upgrade about 1530 local, not sure if 

           power (should be enough, I'd have thought) maybe

           vpn, check tomorrow

20170417 - further checking... unit came up @1100 nominal

           last time kerlink asked for dhcp was march 25

           finish update for dtn node then check dhcp is

           running (looks like it might not be)

           Ah-ha! kerlink has moved to .17 from .11 for

           some reason, and syslog I copied down yesterday

           seems odd, more when endlless update done

20170418 - nominal, still not sure what's up with syslog

           but will look tomorrow

20170516 - refreshed vodafone a/c, was offline for a week

           or two before that, back now

20170831 - device down for a couple of weeks (since TBD),

           went over, possible short on power input, rewired

           that and battery seems to be charging (at ~10.5V now)

		   will check and fix if needed

20170906 - replaced a bit more wiring, still not clearly

           charging, will check again and bring to lab

           if not