LINUX LOG Time Series

All MOBY's functions and scheduling of data acquisition by MOS are controlled by the MLML Instrument Controller located in the upper instrument bay. The controller logs all daily functions in a number of different ASCII LOg files. There are currently 8 different log files: *_shutdown.log, *_sendmsg.log, *_batt_maint.log, *_session_master.log, *_run_mos.log, *_upload_data.log, *_upload_homeetc.log, and *_set_date.log. The data I thought might be useful are plotted below. These parameters include temperature and humidity of the controller housing, battery status and voltages, flags and other events.

Updated: 19-Oct-2017 12:56:35 - Date of last log file downloaded: 02-Aug-2017 04:08:10 - filename: 20170802_040810_upload_homeetc_NEW.log


Reading for the last day of the run_mos and batt_maint log files: 02-Aug-2017 04:07:20 to 01-Aug-2017 04:09:29 (1 day). Zero values removed from the battery voltages, Art says it will read "0 volts if a measurement is attempted while the battery is being used for something else"
Measurment Mean Min Max %std comment
U0C0, main battery voltage: 13.1815 12.4 13.9 2.97
U0C7, falcon power supply bus: 11.994 11.96 12.06 0.13
L0C12, lower battery 1 voltage: 13.092 13.05 13.35 0.70
L0C13, lower battery 2 voltage: 13.0622 12.85 13.46 1.66
L0C14, lower battery 3 voltage: 13.069 12.9 13.31 0.88
L0C15, lower battery 4 voltage: 13.036 12.97 13.08 0.32
U0C1, heatsink temperature: 25.0362 25.01 25.06 0.06
U0C2, case air temperature: 25.0162 25 25.03 0.03
U0C3, case humidity: 51.3241 48.23 53.7 3.20
U0C4, +5APwr: 5.0532 5.02 5.07 0.15
step time server -1.1744 -1.1744 -1.1744 -0.00

The last 10 batteries charged and the number of hours of daylight the charging occured in
Local Start Time Local Stop Time Battery Total Charging
time (hours)
Daylight Charging
time (hours)
sum of cos(zen)
31-Jul-2017 1:16:11 PM 31-Jul-2017 1:52:11 PM Lower 3 0.60001 0.60001 2.9133
31-Jul-2017 2:51:13 PM 31-Jul-2017 5:07:08 PM Lower 3 2.2655 2.2655 6.6058
31-Jul-2017 5:13:31 PM 31-Jul-2017 6:07:14 PM Lower 1 0.89555 0.89555 1.3431
31-Jul-2017 6:11:00 PM 01-Aug-2017 7:09:16 AM Upper 12.9714 1.9956 0.87456
01-Aug-2017 7:10:51 AM 01-Aug-2017 8:09:15 AM Upper 0.97334 0.97334 1.3283
01-Aug-2017 8:10:53 AM 01-Aug-2017 10:45:09 AM Lower 2 2.5714 2.5714 7.6937
01-Aug-2017 11:44:12 AM 01-Aug-2017 12:16:07 PM Lower 2 0.53195 0.53195 2.9594
01-Aug-2017 1:16:19 PM 01-Aug-2017 1:52:11 PM Lower 2 0.59778 0.59778 2.912
01-Aug-2017 2:51:42 PM 01-Aug-2017 5:11:21 PM Upper 2.3275 2.3275 6.5824
01-Aug-2017 5:12:56 PM 01-Aug-2017 6:07:19 PM Lower 2 0.90666 0.90666 1.3461

Summary graph: Shows when all the logs files where created


Figure 1

COLLATED FROM A NUMBER OF LOG FILES



A compliation of the batt_maint (BML) and run_mos (RML) logs for the U0C0, main battery voltage and U0C7, falcon power supply bus. The below graph is every reading from all the BML and RML files. The Main battery voltages are plotted for when charge is being provided by the solar panels (Cup) and when charge is being sent to the lower bank (Cdwn).

Figure 2

A compliation of the batt_maint (BML) and run_mos (RML) logs for the L0C12-LOC15, lower battery voltage 1 through 4. The below graph is every reading from all the BML and RML files. The lower battery voltages are all, always taken with no load and no charge being directed to them. So the charge was switched to 0 first, before the voltage measurement was taken.

Figure 3

This graph shows which battery is being charged, when MOBY is not acquiring data. The math is done by count the number of times battery x is the last one in a batt_maint.log file. According to Art an even better metric is to look at the last battery selected before shutdown and then the first one its on at boot (should be the same) and compute the time between them. I have check how many times there would be a difference and it is very small. So I am going to leave the math as it is.

When MOBY is acquiring data the battery selected is suppose to also be charged. This in theory should be included in this graph, even thought the battery is also being dischrged at the same time. But we think that the log files may be wrong and that during acquisition the upper battery is being charged. Which is another reason to not include those numbers here.

Figure 4

Same data as the above graph just shown in time series form.

Figure 5

This shows which battery is selcted to be used by MOBY during a file acquisition. In the run_mos log there is a line "writing binary data to:" which tells which MO3 file is being created. I then search for the first "Battery in use by MOS:x1 Charge:x2 BS:x3 RS:x4" line before the "writing binary data to:" and pull the x1 battery number from the line and plot it verses the hour and date of the MOBY file.

Figure 6

Same data as the above graph just shown in bar graph form.

Figure 7

Using the run_mos and batt_maint logs I find the last "Battery in use by MOS:x1 Charge:x2 BS:x3 RS:x4" in each batt_maint logs. I then look for the next run_mos or batt_maint logs "Battery in use by MOS:x1 Charge:x2 BS:x3 RS:x4" and if the x2 number has changed then I calculate the time difference. I should mention this does not include any battery charging happening when MOBY is taking data. I should also mention this includes all log data that is on the ftp site, even test data from the tent. So if one battery is charged for days the scale data can go way off the chart so the max is caped a 50.

Figure 8

Ken wanted to see how much of the charging of the solar panels (especially the 12 hours of charging) was happening in the daylight verses night time. So I created this graph. The dot-dash-dot show the start and stop time for each battery which is being charged. The y-axes is still number of hours charged. The cos of the zenith angle is in black. The yellow and gray patches are day (zenith < 90 deg) and night (zenith > 90 deg). We can see most of the 12 hours of charging is happening over night. This potentially has the same scale problem as the previous graph.

Figure 9

This is my next attempt to figure out the battery charging relationship to the sun. I when through each charging start and stop time and removed any time in which the sun was below the horizon. So you will see that most of the time over 10 hours are gone because most of them where charging overnight. I then calculated a solar zenith angle every 15 minutes for the day light hours and calculated a mean zenith angle. I changed the symbol based on which zenith angle group the charging data set fell in. Of course the longer the charging time the greater the variablity in the sun angle. This potentially has the same scale problem as the previous graph.

Figure 10

So for the previous graph I had calculated the zenith angle every 15 minutes for all the daylight hours. Ken said to take all the 15 minute daylight solar zenith angles and sum the cos of the zenith angle. This should give a good idea of how much sun light is getting onto the solar panels during charging.

Figure 11

So for this graph I summed all the charging being done in one day. This eliminates the scale problem because if one battery is charges for many day the sum is spread out over each day.

Figure 12

This is a plot of the 4 lower batteries. The small dots are the measurments from the run_mos and batt_maint logs and the largers symbols are from the TT7 main volts saved in the MOBY file auxilliary data. The black lines are the min and max of the voltages in the files.

Figure 13

VAUX TT7 BATTERY INFO These graphs are created from the TT7 main voltage data collected after each lite/dark scan in the MOBY files.



For each MOBY file I found the mean of all the TT7 main voltage meansurements, I then looked through the run_mos log data to find the battery selected for that MO3 file. These data are plotted with the means as the colored dots. And the min and max in the file as the black line. Colors are which battery and shapes tell which MOBY hour file.

Figure 14

Mark wanted a dv/dt calculated to check the health of the batteries. So this graph shows the change in charge over the time it took to acquire the MO3 file. This graph the dv was calculated from subtracting the first voltage in the file from the last. If the dv/dt is positive it means the battery lost charge. If the dv/dt is negative it means it gained charge. The only caveat with this meansurement is that the scan-by-scan measurements can have spikes (you can see the scan-by-scan measurements in the plots for each MOBY file) so depending on if you thing the spikes matter or not this dv/dt may not be showing you what you want.

Figure 15

So I did another dv/dt calculation but this time I used the min and max voltage. This takes into account the spikes but not really the change over time since the min and max could be from any place in the file.

Figure 16

SHUTDOWN LOG INFO



This plot shows the result each time the shutdown script has run. If it runs and finds a "lock" file (basically an indication that something else is still running) it cancels the shutdown. If it runs and "no lock files found" then it shuts down. My best guess at keywords in the file (all of which have a GMT time at the start of the line)

Figure 17

SHUTDOWN LOG INFO



This plot shows the result each time the shutdown script has run. If it runs and finds a "lock" file (basically an indication that something else is still running) it cancels the shutdown. If it runs and "no lock files found" then it shuts down. My best guess at keywords in the file (all of which have a GMT time at the start of the line)

Figure 18

SESSION_MASTER LOG INFO The session_master log is the big picture, of turning on MOBY, taking data and turning MOBY off



My best guess at keywords in the file (all of which have a GMT time at the start of the line)

Figure 19

Shows the start and stop times of the session master file for the last 3 days.

Figure 20

RUN_MOS LOG INFO The run_mos is the log sheet that tells about collecting a MO3 file.



My best guess at keywords in the file (all of which have a GMT time at the start of the line)

Figure 21

The run_mos logs for the U0C0, main battery voltage and U0C7, falcon power supply bus.

Figure 22

The run_mos logs for the U0C1, heatsink temperature and U0C2, case air temperature.

Figure 23

The run_mos logs for the U0C3, case humidity.

Figure 24

The run_mos logs for the U0C4, +5APwr.

Figure 25

The run_mos logs for the U0C9-12, solar panel current 1-4.

Figure 26

The run_mos logs for the U0C13, lower bat charge current, U0C14, upper bat charge current, and U0C15, controller current.

Figure 27

The run_mos logs for the L0C0, regulated voltage and L0C1, unregulated voltage.

Figure 28

The run_mos logs for the L0C7, case air temperature.

Figure 29

The run_mos logs for the L0C8, case humidity.

Figure 30

The run_mos logs for the L0C12-LOC15, lower battery voltage 1 through 4.

Figure 31

So looking at the section of run_mos that acquired the MOBY data. I pulled out some keywords and then have plotted them below to show how long it is taking to acquire a MO3 file. I am not totally sure these are the keywords needed but they do tell a story. The cooler turn on for 15 minutes. Then the acquisition starts. The Closely packed symbols are the Es data before and after the more spaced out x symbols for the Lu data collection. The bigger group of symbols at the end of the file are the Es followed by the reference lamps. Or in the case of the newer faster files the bigger group at the end included the Ed data as well. The black dot at the end is the total time to collect the file. I have also added plotting a magenta triangle with a line for any file that shows data collection started in the log file ("Checking the scan definitions" line) but did not end with "Shutting down MOS", in the legend the string is "No EOF".

Figure 32

BATT_MAINT LOG INFO



My best guess at keywords in the file (all of which have a GMT time at the start of the line)

Figure 33

The batt_maint logs for the U0C0, main battery voltage and U0C7, falcon power supply bus.

Figure 34

The batt_maint logs for the U0C1, heatsink temperature and U0C2, case air temperature.

Figure 35

The batt_maint logs for the U0C3, case humidity.

Figure 36

The batt_maint logs for the U0C4, +5APwr.

Figure 37

The batt_maint logs for the U0C9-12, solar panel current 1-4.

Figure 38

The batt_maint logs for the U0C13, lower bat charge current, U0C14, upper bat charge current, and U0C15, controller current.

Figure 39

The batt_maint logs for the L0C0, regulated voltage and L0C1, unregulated voltage.

Figure 40

The batt_maint logs for the L0C7, case air temperature.

Figure 41

The batt_maint logs for the L0C8, case humidity.

Figure 42

The batt_maint logs for the L0C12-LOC15, lower battery voltage 1 through 4.

Figure 43

UPLOAD_HOMEETC LOG INFO



My best guess at keywords in the file (all of which have a GMT time at the start of the line)

Figure 44

SET_DATA LOG INFO



Looking for set_data messages

Figure 45

THe time adjustments made to the MOBY computer time

Figure 46
Figure 47

Stephanie Flora - Moss Landing Marine Laboratories