notes.txt
author stephen
Mon, 13 Feb 2017 11:07:41 +0000
changeset 22 b2ba74aa0bd2
parent 18 5f5fbc348b7e
child 23 c933ade04774
permissions -rw-r--r--
feb13 up
     1 
     2 20170111 - device online for 1 min @0948 - someone on roof?
     3 20170112 - device offline at 1524, surprised if that's power? check
     4 20170113 - device work @ 0933 briefly - see early-wake-theory below
     5            early-wake-theory:
     6             if device goes below 11.1V while sleeping then it won't wake on
     7             the RTC but will wake when the solar charger sees 12V again,
     8             at which point it will see that it ought be asleep unti 1100
     9             and so it dozes until then - possibly means that we're keeping
    10             the kerlink up after the eurotech has gone to sleep, otherwise
    11             why is the voltage still dropping?
    12             - I modified /etc/stopproc.sh to stop pbm and call ker-off
    13 20170124 - took that out again, added code to pbm binary
    14            looks like that fix didn't do it, need to test
    15            some more when at node Monday
    16 20170118 - fixed kerlink not powering off - both s/w and wiring!
    17            we re-charged unit from mains around 1400-1430, after
    18            that back to solar, hopefully voltage on 19th will
    19            behave
    20 20170124 - validated that ker-off does remove voltage from kerlink
    21            power input; found a code path in pbm that wasn't 
    22            calling ker-off, testing of that needs to be finished
    23            when device has power again. Note: left device with
    24            sleeping only set from 1440 to 1455 so it'll wake 
    25            early on 25th (not likely to get more power today
    26            due to sun angle)
    27 20170125 - eek, I'd put the ker-off code in the wrong place;-)
    28            fixed now I think finally
    29 20170126 - seems to have worked out - node went down @1600
    30            on 25th with battery @12.52V, awoke on schedule 
    31            @1102 on 26th with battery @12.49V and weather was
    32            overcast all morning (that I saw:-) on the 26th,
    33            node is drawing about 0.9-1.1A around 11am
    34            probably only safe to fully believe stats from
    35            here on, though some info can be gleaned from
    36            earlier data no doubt
    37 20170127 - there was a wake @ 10:02 - might be ok though, node
    38            went into long standby at 1459 on the 26th so was
    39            close to out of power (11.34V)
    40 20170128 - looks like basil was rebooted about 17 hours ago 
    41            (around 1800 on the 27th?) (down is also down)
    42            so vpn wasn't up - not sure if client will connect
    43            before it's next reboot, hasn't so far after 5
    44            mins (vpn manually restarted @ 1140) I'm guessing
    45            there was a power off event
    46 20170201 - basil reboot: there was a bridge0 that was ifup'd
    47            and that might be interfering somehow, took that
    48            down, we'll see @ 1100 if that helps, if not, I'll
    49            wanna go check unit physically (also could be 
    50            SIM card crap, check that too - SIM seems ok, has
    51            7GB and 8 days left) 
    52            Turns out that the SIM was not ok - the "add on"
    53            thing is not being used and the balance was down
    54            to 0.65c or actually maybe negative. Topped the
    55            fecker up.
    56            Clock was still on jan 29 today, odd - maybe
    57            rtc isn't working right? also that might interact
    58            with vpn, not sure - actually no, it was that
    59            the node thought it was 1600 on the 29th so it
    60            went to sleep, wonder when it'd have awoken if
    61            Kerry hadn't hit the physical switch?
    62            I have the kerlink boottimes.txt that could be
    63            used to fix the boot times and hence battery
    64            log of the loradtn node if we want
    65 20170202 - odd timing - node woke @1047 - is power still being
    66            consumed?
    67            also odd vpn pattern - new client IPs every few
    68            minutes, check node's syslog later
    69 20170206 - looks nominal at the moment, nice weekend weather
    70            helps:-)