Changed a battery at DF logger. Replaced a new power line and battery in the 104 logger

reconnected the rain-gauge on BCSE 102 logger.

After swapping multiplexer, there was no improvement in G1. Check again.

Changed a multiplexer in G1 plot after it showed all channels of multiplexer reading the same depth.

Changed a multiplexer in GT plot of 104 logger. GT is working normal after this. Reconnected G1 plot to the 102 logger. G1 is working normal after this. All tdr\’s are working normal as of today.

Replaced battery in 104 logger and DF logger. After the battery replacement, DF logger was backed up, but 104 and 105 loggers still have communicating issue. Plugged the entry hole of DF logger with steel wool to prevent mice invasion. Fixed the crimp of battery in CF logger.

Sanitized the CF logger box after clearing left our debris and mice materials. Changed the drier packs, sealed all entry into logger. CF is working normal. Changed tdr100 in Ft (aka 105) hoping to make this box back again. At end of the day after this change, no help. There is no FT data appearing in the data table. Battery looks good. There is some communication issue not with tdr100.

Changed battery in BT and CF plots. After replacing the batteries, both plots are backed up. But FT site is not backed up. FT box receive power from 104 BT box. Need to check FT again. CF box is invaded by several mice. Box is cleaned with alcohol after replacing the battery.

Changed a battery in the logger box 104 that connecting FT and BT plots. These plots were down after battery was completely drained. Desiccants also changed.

All tdr\’s (CF, DF, BT, FT and G6) have been re-checked a week after changing multiplexers (changed on 21 Aug 2020). It seems, changing multiplexer in these tdr plots did not resolve the problem (probes reading same depths). Thus, tdr depths whatever they reads must be real, and do not reflect any non-functionality of one or more multiplexer channels.

Multiplexer changed in following tdr plots because one or more depths are reading the same value (see below) G6 tdr plot at BCSE: bottom four depths seems have closer values, so multiplexer replaced; BT tdr plot at forest transition: 90 cm, 125 cm depths have closer values; FT tdr plot at forest transition: 10 and 20 cm depths looks similar; CF tdr plot at LTER: 20, 35 cm depths looks similar values; DF tdr plot at LTER: 20, 35 and 50 cm depths had similar values.

rebooted logger 101 (G2, 4,7 and 9). Switched the power source from 12v to SW in all BCSE loggers, this also includes profiler CS650\’s in 102 logger.

Rebooted logger102 at BCSE after it reporting no data, even no \’Nan\’.

Changing multiplexers on 2nd July 2020 in G6 and G10 did not resulted in any desirable change. These depths behaved in a same way as before the swapping of multiplexers. Either the probes are not functioning normally or the data is just real as it could be.

Changed multiplexers in G6 and G10 after some depths are reading the same value. In G6, 50 and 65 cm while 35 cm and 65 cm in G10 are reading like a same depth. I used multiplexers that were came back from inspection and repair from Campbell Scientific.

I swapped multiplexer in the following plots 1. BT plot: 65-cm and 95-cm depths seems reading the same value during the period of rainfall but look different druing the period of fewer rainfall (e.g., after 238 DOY). Thus, I changed a multiplexer to take care of this problem 2. G10 plot: 35-cm depth doesn\’t look right in 2019, and even this trend is continuing in 2020. I changed a multiplexer to take care of this problem. 10-cm probe started to fail from May 2020. After the logger 102 started to work from 24th April, 10-cm probe was also working but only for few days, then it failed. In my next visit, I should check this probe and investigate its problem, although there was no physical damage to surface probe. 3. G8 plot: some depths like 50-cm and 65-cm depths behaved differently, and also 35-cm and 50-cm depths reading the same value., so i changed a multiplexer. 10-cm probe was not working, it seems not sending data from 5th June 2020 (155 DOy). I checked this probe. This probe was uninstalled by someone and away from the plot. I put back the probe into the soil. Hope, this will send data again. A day later multiplexer swapping, I re-checked the data of BT, G10 and G8. There is no change in data due to swapping of multiplexer. So, unsure what caused those changes in their depths (see above). But surface depth of G8 is working.

101 and 102 loggers are working normal. I checked 104 and 105 loggers at forested site. Solar panel was OK, battery and controller also OK. Radio in 104 was flashing and logger had power. There was no power in 105 logger, so radio was not flashing. Sven says, he can connect 104 logger through 105 logger only if 105 is powered. I changed the power cable between 104 and 105 loggers, then 105 was powered, and radio was flashing. Sven was able to connect 105 logger and also 104 logger, and confirmed the values are reading OK. So success.

Today worked with 101 and 102 logger. Because of last week storm and lightening, there are serious trouble in 101 logger, 104 and 105 loggers and Lux Arbor MLE. Check marginal-land tab for more details what impact of storm and for which plot or block. 101 logger: Radio was not communicating in 101. I rebooted couple of times, Sven says, radio is communicating very slowly even after rebooting. I swapped a tdr100 in 101 logger. After tdr100, Sven is able to communicate with radio, although the rate of data flow is slow. Overall, swapping tdr100 helps and data is coming from these plots. 102 logger: It was a long struggle with this logger. Before connecting tdr100, CR1000 has power and works normal when CS650 is powered. When tdr100 connected, CR1000 loose power after few seconds. I changed the all data cables between tdr100 and CR1000, and between multiplexer and tdr100, and between primary multiplexer and G5 multiplexer. I used terminal blocks at very intersection to isolate the cables and so minimize the cable short. Even after this, still the problem persist, i.e., CR1000 loose power when tdr100 reconnected to it. Sven feels, some cable is shorting the power supply. Finally I found that piece of cable that is shorting the power supply. I rewired everything correctly, checked connectivity,put back everything in the box, connected G5 and G10 plots. Overall, this helps, data is coming from this logger from G5 and G10 plots. Forest transition sites: FT and BT sites are down. I checked, that there was no power voltage coming from Solar panel. Presumably it had some issue. Sven has changed the power supply for 104 and 105. The newer power supply is in the link https://files.slack.com/files-pri/T10025EEN-F0140QBLY21/image.png —————————- Some slack messages between me and Sven that can be a document for the future regarding the power supply in 104 and 105 Sven: you want to keep all your batteries on the battery side of the solar controller… 10:37 Ie connect the battery packs in series. Imagine the current flow in the second diagram if the battery on the solar controller is removed but the battery on the 105 logger is working… mhussai 10:44 AM So technically we don\’t need a battery for 105 if I understand. We can add 1 or 2 batteries directly to solar controller in 104 box. Since the battery is connected now to 104, I assume it charges 105 as well regardless of solar is working or not. right? 10:45 So I\’d expect the 105 is also getting powered after I connected a battery to 104. sven 10:46 AM right it does not matter where the second battery is or if we even have a second battery. 10:49 They are tied together either way. except that in the case of the second diagram you are getting much less charge to the 105 battery because it\’s off the regulated output and not the battery charge input. plus there is the failure mode i mentioned earlier. It\’s probably not too healthy for the solar controller to have current input through the output. mhussai 10:52 AM I got it now. Now the question is, a battery is connected to 104 logger. I assume, its gives power to 105. Can we connect 105 or 104? or do we need solar power to get this both going? sven 10:56 AM We can only power them together since we have only on power source —————————————- Overall, FT and BT plots are not working. They need more investigation.

Today worked with loggers 101 and 102 at BCSE 101 logger: Sven said that there is no communication with radio. There are no good data or nan\’s from this logger. I rebooted the logger and radio was flashed red and green that indicates radio is OK. At the end of day, however there is no change in the logger. 102 logger: There was no good data from G5 plot which is only connected to the logger. After Sven fasten the relay cycle, there were no relay clicks in multiplexer in G5 plot (that has older version multiplexer). I reconnected G10 and there were no relay clicks in either G5 or G10. After reconnecting G10, CR1000 lost power. Again, I tracked down to see where the problem was by disconnecting and reconnecting G5 and G10 step-wise. Cr1000 had no power. I disconnected primary multiplexer data cables (that also has tdr 100 data cables) from cr1000, then CR1000 got the power. That indicates the data cable that runs between primary multiplexer-tdr100 and cr1000 was faulty one. I replaced this data cable and tried to rewired the whole thing, but the work was hampered by rain, I closed the box immediately leaving everything as such in a loose way. Will check this tomorrow, disappointing day though…

Some good news today after a long hours of struggle. Worked today in 102 logger. Sven changed the relay cycle to 1 min that helped in diagnosing which tdr plot is working or which is not. Until today, G1,3 and G10 were isolated from the logger, only G5 is connected. With this new relay mode, I checked for relay clicks in G5 (existing multiplexer in G5 is old fashioned that makes relay clicks). There wasn’t anything. I swapped another multiplexer (again with old fashioned one) in G5, no relay clicks. I swapped another a tdr 100 and again no relay clicks. I took this tdr 100 out and put back the old tdr 100. While changing primary multiplexer, I routed all data and power cables (from CR1000, tdr 100) through a terminal block, then to the newer primary multiplexer. I found, the data cable (green) and power (red) were shorting. I took these cables out from terminal blocks, and checked the individual cable connectivity without a terminal block, they seem ok (connectivity is good for cables without block between logger and tdr 100; tdr 100 and primary multiplexer; and primary multiplexer and G5 multiplexer). This puzzled me to understand whether problem is with data cable or with terminal block. I replaced a newer data cable that connects primary multiplexer and G5 multiplexer. All data cables (from Cr1000 and tdr

100. are connected together to primary multiplexer without a terminal block. Rewired everything, checked connectivity- all looks good. Put back everything in the logger, power connected and waited for replay clicks in G5. Yes there are relay clicks in G5, so success. My quest for a problem in G5 still remains unclear. Bottom line is - G5 working, I changed data cable between primary multiplexer and G5 multiplexer, changed multiplexer in G5 plot, changed primary multiplexer.

In the 104 logger (forest transition site), I disconnected both BT and GT tdrs from logger, and then reconnected only BT to the logger. GT is isolated. I checked at the end of day for data flow, yes, there is data flow from BT tdr, so isolating plots offered help. GT plot is suspect to have some problem which need more investigation. In the 102 logger, I disconnected all G1, G3, G5 and G10 plots from the logger, and reconnected only G5. AT the end of the day, there is no data flow from G5 plot. It just puzzled me. More investigation in the coming days.

Today, I changed a tdr100 in the logger box of 104, hoping it will GT and BT plots. Also, I reconnected G1 plot to the logger 102 box. At the end of day after these changes were made, GT and BT plots are not working yet, don\’t know why? I will isolate one by one next week. Also, reconnecting G1 to the logger 102 had caused the others G5 and G10 plots stopped. This is disappointing. In my next visit, isolate G1 again and allow G5 and G10 to work for some more weeks regardless of corn planting time set to begin.

In the 102 logger, G5 started to work after isolating with rest of tdr plots. I reconnected G10 today to the logger while leaving G1 and G3 still disconnected. I checked the data flow from G10 after it reconnected to the logger, it seems G10 sending data. Good news at the end of the day, G5 and G10 are sending data. I\’ll reconnect G1 3 days later. In the 104 logger, I replaced a primary multiplexer in the 104 box, and rewired all the data cables between multiplexer and tdr 100, also check their continuity. It seems, wiring is correct. At the end of the day, I check the data flow from 104 logger- there was no data flow from BT and GT plots even after replacing a multiplexer. Probably, tdr100 may have gone bad. I\’ll replace it on my next visit.

GT and BT plots in the logger 102 is sending only nan\’s. Don\’t know what else is missing. I may change tdr100 or primary multiplexer on Monday. Good news is that G5 plot is sending numbers. I hope to reconnect G10 on Monday to see if G5 stops or both G5 and G10 continue to work.

BT and GT plots in the logger 104 has been down for more than one week. In my last visit while fixing GT plot, I found there was a shortening of cable length (data cables) between primary multiplexer and tdr100. I tried to rewired the short cables as far as possible, but that does not helped, rather BT also failed consequently. Today, I used a terminal block to connect the corresponding data cables, assuming this will resolve the problem. I disconnected and isolated G1, G10 and G3 plots from the logger 102 while connected G5 alone to the logger. This is done to take care of the long-standing problem that occurred since fall 2019. Sven says- everything OK with address and levels id\’s in this logger. Only data cables are disconnected, not the power and camera cables.

GT plot still sending nan even after fixing data cable and replacing a multiplexer. Moreover, BT also down since I left the site.

GT plot in the forested site (logger 104) was down from some weeks. I replaced a multiplexer in GT plot, and also I found that one data cable (C1) that connects primary and GT multiplexers was cut. I fixed this one also.

Moved logger 104 tdr to switched power. Took 105 battery to be recharged

Replaced battery on logger 104. Disconnected the battery on logger 105 since it was back feeding into the solar controller. It is currently running off the battery in logger box 104. I noticed that the TDR was running on the permanent 12V output instead of the switched power. I repositioned the solar panel to point south instead of south east.

BT and GT plots of logger 104 were down again.

BT and GT plots of 104 logger was down. I replaced a tdr 100 and primary multiplexer. After replacement, BT was backed up, but not GT.

BT plot in the forest transition site was down in the last week. GT plot, another plot connected to this logger box is however working. I replaced a multiplexer in BT plot thinking that this replacement will resolve the problem. But problem still persist. I checked the connectivity of radio cable that runs between primary and BT multiplexers, found no connectivity in 2 or 3 cables (red and brown) that perhaps explained the problem. A new radio cable was replaced and rewired them. Hope, this resolve the problem. Remember to check BT tomorrow. Sven put back the radio in 102 logger at BCSE that went for a repair. After this, data started to flow from CS650 probes in G1, 5 and 10 plots. However, there was no change in their TDR\’s probes. TDR probes in these plots have trouble after fall harvest.

DF site: A battery is replaced. tdr was down in DF site due to battery. 102 logger: 102 logger was still down even after changing a tdr 100. As a next option, I changed a primary multiplexer. Also noted, the power cable (+ve) was disconnected from CR1000, this may explain why the whole logger wasn\’t working. I re-wired the whole logger, hoping to see the data flow.

G8 plot in 103 logger is reconnected. This was stopped after disconnecting the radio cable that runs between G8 and G6 for ease harvesting operation. A multiplexer is replaced in G1 after its upper depths reads the same value. 102 logger box that connects G1, 3, 5 and 10 have been down for couple of days. I suspect the problem with TDR. so TDR 100 is replaced.

A follow up from last field visit to BCSE and Forests sites where significant replacement of multiplexers was carried out due to one or more depths reading the same SWC values. DF plot: Changing a battery helps in this plot. Multiplexer that was taken from this plot was tested in my office and found nothing wrong with any channels. All channels are tested OK. SWC values in the depths of 20,35 and 50 cm might be real, cannot be related to malfunction of multiplexer channels. FT plot (105 logger): Changing a tdr100 helps. Data is back now in FT plot after tdr 100 changed. Multiplexer that was taken from this plot was tested in my office and found nothing wrong with any channels. All channels are tested OK. SWC values in the depths of 35 and 50 cm might be real, cannot be related to malfunction of multiplexer channels. BT plot: Multiplexer that was taken from this plot was tested in my office and found nothing wrong with any channels. All channels are tested OK. SWC values in the depths of 10, 20 and 35 might be real, cannot be related to malfunction of multiplexer channels. G8 plot: 10 cm depth reading now. Multiplexer that was taken from this plot was tested in my office and found nothing wrong with any channels. All channels are tested OK. SWC values in the depths of 20 and 35 might be real, cannot be related to malfunction of multiplexer channels.

FT plot (logger 103): tdr at FT site has been stopped, sending only 7999 values which is nothing but no values, problem likely due to tdr 100. So, I replaced a tdr100. tdr depths 35 and 50 cm reads the same value, thus multiplexer also replaced. BT plot (logger 104): The depths 10, 20 and 35 cms reads the same value. Multiplexer is replaced. DF plot: Battery has been draining continuously for more than a week, thus a battery is replaced. The depths 20, 35 and 50 cms reads the same value. Multiplexer is replaced. G8 plot: Surface probe, 10 cm has been outside the soil, thus not reading anything. This probe is now put back in the soil. 25 and 35 cm depths reads the same value, so multiplexer is replaced.

Replaced multiplexer in G2, G3 and G5. This is the first time since 2018, G3 is connected. Middle layers shows some noisy data, so a multiplexer is replaced.

Follow-up from multiplexer change in G6, G10, BT and GT plots. After changing multiplexer in G6 and G10 plots, there is no change in values of 20 and 35 cm depths. Although multiplexer replacement in G10 caused some spikes, but they 20 and 35 cm depths in both plots still reads the same value.I will put back multiplexer back in G10 plot. After changing primary multiplexer in 104 logger (Gt and BT plots), there is no change in 20 and 35 cm depths. However, these depths reads differently in BT plot, and slightly differently in GT plot, although multiplexer replacement do not result in any change, spreadsheet is available in file location \”continuous data monitoring\”

Surface depths (10 cm) is broken in G5, there is no 10 cm probe in G2, 10 cm probe in G9 and G10 are good but they are not reading.

In forest transition site, power line between solar and logger box 104 was laid through the conduit to protect from deer damage. The primary multiplexer in the logger 104 was replaced after 20 and 35 cm depths in both GT and BT plots reads the same value. Earlier, changing multiplexers in GT and BT plots did not remove this problem which indicates the problem could be likely with primary multiplexer, so it changed.

In BCSE, G6 plot- 20 cm and 35 cm reads the same value, so a multiplexer is replaced; G10 plot- 35 cm and 65 cm depth reads the same value, so a multiplexer is replaced.

The loggers 104 and 105 were down, not even Nan\’s. Everything looks good in 104 while inspecting the logger box. Rebooting the logger 104 helps. The logger 105 was down due to low battery, which is due to faulty power line. A newer power line between logger boxes 104 and 105 were laid, and a newer battery replaced in 105. The older power line between 104 and 105 were taken out and noticed that it went significant wear and tear that probably explain the frequent battery draining. Changing newer power line and battery helps logger 105.

CS650 probes in G1, G5 and G10 are connected to CR1000 in logger 102. But yet no script is written nor the data collection. The wiring of CS650 in logger 102 box follows the instruction given CS650 manual (p.7). The signal (green colour) of the 9 sensors are connected to one port end of the block. Jumper cable run through the other end of the block taking one single green cable from terminal block (that has 9 green colour cables) to the C5 port in CR1000. In a similar way, wiring was done for red, black, orange and clear. Orange and clear goes to ground port in the logger. Before connect to the logger, connectivity between ports (via jumper cables) were checked. After the good connectivity is established, single green cable connected to C5 port, single red connected to 12 V, single black connected to G, orange and clear connected to different G. More will follows

After G1 and G3 plots connected to logger 102, there was no good data flow from these plots. I replaced a multiplexer in G1 plot. After replacement, data is flowing good from G1. There is no good data flow from G3, probably multiplexer need to be chnaged. Since this is not a priority plot, I may replace the multiplexer at later time. CS 650 that were installed in Dec 2018 in G1, G5 and G10 were routed to logger 102 box through conduits below ground with help of Kevin. Probes were rechecked for addresses and labelled. The conduit above the ground were sealed off using Aluminum tape and steel wool. Any unnecessary cables inside the plots were taken out.

G1 and G3 tdr plots are connected to logger 102

reconnected g10 plot to the logger 102. The data cable of G10 is connected directly to G5 box, not to primary multiplexer.

G5 and G8 data were noisy in the last few days. I replaced tdr100 in both boxes. After this, data looks OK in G5, and OK in some probes in G8. TDR100 which is taken out from G5 was the one that was recently fixed by Campbell.

tdr data from G5 and G8 plots are not looking good even after changing the multiplexer.

The multiplexers that were taken from G5, logger 102 primary logger, G8 and G9 boxes are tested in the lab. The multiplexers from 102 primary logger, G5 and G8 are tested OK, and all channels in these multipliers are working well. However, the channels 5 and 6 of multiplexer from G9 are not tested OK, they are short. Thus changing multiplexer in G9 last week should help the data flow in G9.

104 logger: There is no change in data flow or data pattern between 20 and 35 cm depths in GT plot; and between 10 and 20 cm depths in BT plot even after changing their respective multiplexers. The multiplexers that I took from these plots are tested ok, all channels of these two multiplexers are working well and tested OK. Thus the issue is not likely from multiplexer or TDR 100, but may be from already buried probes.

102 logger had communication problem, no data since 8am 24 th April. I rebooted the logger.

102 logger trouble shooting by Sven, helps finally. All the probes of G5 plot are start reading differently. For now, only G5 plot is connected to the logger box. We decided to let G5 alone to work for a week.

Long standing problem in 102 logger at BCSE finally was discovered and resolved by Sven. His slack message is pasted below as an important record. \”I think the problem with 102 was that the levels on the multiplexer for 5 was wrong. In the program it was a 3rd level multiplexer but on the device it was set as 2nd level multiplexer. I\’ve moved all of the 102 multiplexers to level 2 and hooked up G10\”

Reconnected G9 in 101 and G5 (others like G1, G10 and G3 disconnected) in 102. TDR 100 and multiplexer (both were fixed by Campbell, so does not have issue) are used for 102 primary enclosure.

Replaced a multiplexer in GT plot after it shows depths 20 and 35 cms reads the same value, that means relays for these depths are not switching.

Swapped a multiplexer in BT site (104 logger) to overcome the problem where 10 and 20 cm depths reads the same value.

Replaced power line between 104 logger box and solar. A new solar panel installed at 104 site. Also newer battery replaced in 104 logger. The older solar panel need to be taken away from the site when snow melts along with the buried power cables. I was in impression, Ft site had communication and network issue, so was not sending the data. However, Sven clarified me there were no issue with communication in 105 logger, probably either tdr 100 or multiplexer might not be working. I changed a tdr 100 today along with the battery.

Installed CS650 probes in G1, g5 and G10 of 102 logger at BCSE site. In each plot, three cs 650 probes were installed at 0-30cm, 30-60 cm and 60-90 cm depths. Holes with that desired depth were made in trench (made by ditch-witch by Kevin for 16 inch depth), and probes are vertically inserted at an angle facing away from the trench. After probe installation, drenches were refilled by ditch-witch and soil around the trench were racked properly. (K2 add) TDR positions were located via GPS prior to trenching. The placement of the new CS650s was based on 2 m distance away from this profile. Probes at 0-30cm placed by Kevin in each plot, and 30-60cm in G1 and G10 placed by Kevin. Zaman placed the 60-90cm in all three plots and 30-60cm in G5. Sensors are placed perpendicular to the trench direction at a slight angle to ensure placement in fresh soil.

Replaced tdr 100 in 101 logger. 101 logger found not ok in last week. All g2, g4 and g7 sending nan values. Replaced multiplexer in G5 box of 102 logger, and G5 box or multiplexer is connected directly to tdr 100 bypassing primary multiplexer. G1, G10 and G3 are still off, not connected. The values in G1 and G10 are just artifacts.

SWC recorded at the field using old version of PCTDR to check whether the probes in G5,10 and 1 are working or not. Results are as depth G5 G10 G1 10 cm -0.042 -0.036 0.136 20 cm 0.148 -0.051 0.139 35 cm 0.149 -0.052 0.132 50 cm -0.053 -0.051 -0.052 65 cm -0.053 -0.051 -0.052 90 cm -0.052 -0.051 -0.052 125 cm 0.085 0.095 0.099

Waveforms were also generated from each probe in all plots of 102 logger except G3.

102 logger: Replaced multiplexers in G5 (SN 5238) and G10 (SN 1051) boxes and rewired them as whole. Cameras in G1 and G3 connected. 103 logger: Rebooted the logger

105 logger: Battery was suspected to be dead, but battery was good. Antenna was just red without flickering. To resolve this, I rebooted the logger box, and antenna both red and green started flickering that gives the positive outcome. 102 logger: This logger has not been good before or after I return from MLE trips. Previously this logger has been troubleshooted several times and even replaced all electronics, no results. Today, I just laid out a new data cable between G5 and G10 leaving G1 and G3 disconnected, and rewired both G5 and G10. Hoping this resolve the problem.

DF logger is backed in after some trouble shooting

FT site logger needs a battery, it seems battery is died. Lets change this one soon

Several troubles were noticed with TDR plots during my absence (2 weeks trips for MLE experiments between 2 July and 13 July). Trouble with DF, forested transition sites (104 and 105 logger) and 101 logger boxes. troubles are related to solar and battery. Df site: Battery and solar are OK. I grabbed multiplexer and TDR 100 to the lab. I tested them in the lab, and are OK, no issue, problem might related to communication. 104 and 105 sites (Forest transition sites). Battery was completely drained. Solar was shaded heavily by trees, this might be a trouble. Using some anchors, I moved the solar to a new open location and replaced the battery. Logger volt is OK, yet there is no data flow. 101 logger: Sven replaced a battery, but yet there is no data flow. 102 logger have a long standing problem.

Changing data line in 103 logger resolved the problem. Signal decay or rebooting once in every one days is resolved, no more as an issue. Logger 102 has serious problem. Changing multiplexers or TDR 100 did not resolved the problem, even changing TDR 100 from nearby plot did not helped either.

102 logger: G5 and G10 showed an unusual pattern in SWC, where in both, all depths reading the same values for over a month. To overcome this problem, I replaced multiplexers (Sn 1319 in G5, and SN 1388 in G10). Even after the replacement of multiplexers, but plots did not showed any change. I tested the multiplexers that were taken out from these plots, and found no issues with the multiplexers. Next step, is to change the primary multiplexer, and then TDR 100. 10 cm probes in CF, G2, G5 sites are failing. There was no change in G2 or G% even after I replaced with other 10 cm probe. In CF site, 10 cm was taken out from the soil presumably by animal, but reinserting it into the soil did not resulted in any change. There were no obvious damage in Coax of this 10 cm probe in CF site.

Two days ago, I suspected a problem in logger 101 where all plots stopped working. I disconnected G2 from logger while allowing G4 and G7 continue to stay on the power while G9 remained disconnected this season. It seems, G4 and G7 are sending the data, while G2 did not. Thus there is an obvious problem in G2. I replaced a multiplexer (Sn 1051) in G2 to take care of the problem.

Battery in the logger 104 changed and a new extending power cable was connected for solar panel. Solar panel is moved away from logger box to the location of older solar panels. Batteries in 104 and 105 are now charging.

104 and 105 loggers were stopped logging during week ends. Battery was almost drained, and solar was reading 18v before I connect battery or other power side. Solar reads less than 5v, when anything is connected. Most likely, issue was charger. I changed solar charger and battery in 104 box, while allowing 105 not powered. If 104 works smooth for 2 or 3 days, then I will connect 105.

On 7th May 2018, Sven updated logger programs and recomputed CF and DF data already in the database with default parameters. The purpose of doing this, to resolve the inverted trends that was apparent in 20 and 35 cm depths of DF site, and 20 cm depth of Cf site when we fitted probe calibrated parameters for these layers. After we fitted the default parameters, inverted trends is gone while the values with default parameters are more or less same as before. So we decided to fit the default parameters (from TDR 100 manual) to all probes in DF and CF sites. Default parameters are as y0=-0.053; a= 0.0292; b= -0.00055; c=

0. Fitted eqn is =((y0)+(a*lalsq)+(b*POWER(lalsq,2))+(c*POWER(lalsq,3))) After this change, all probes in DF and CF are good.

Some follow up from trouble shooting that was carried out over last couple of days… 101 logger: G4 and G7 were working until yesterday, then I reconnected G2. Today, G2 also sending data, thus G2, G4 and G7 are OK in 101 logger, mostly G9 tdr plot have issue that puts down the whole 101 logger down. G9 will be rechecked or swapped with a multiplexer next week. 102 logger: G1 and G3 were off as before. G5 was working until I reconnect G10 after swapping a multiplexer (SN 5240). After G10 reconnected, G5 also stopped, which means, G10 have some problem not related to multiplexer but something else that put the whole 102 logger down. I will disconnect G10, let G5 alone to work continuously for few more days. 103 logger: G8 was already off. G5 was replaced with new coax and data cable in order to see if problem go away. After putting new coax, G5 also stopped. Probably, I am going to put back the cable as it was before and let the G5 alone continue for some more days.

103 logger: Coax put back in G6 and reconnected. 102 logger: G10 disconnected allowing G5 to continue for some more days.

From the end of April, all TDR at BCSE site have troubles. 101 logger: There were only Nan\’s from this logger. As a trouble shooting, I isolated and disconnected G9, and G2 while G4 and G7 are connected. G7 and G4 are good, and sending the data for two days continuously that shows, G7 and G4 have no issues. Today, I connect the other plot, G2 to logger 102 and should wait for a days to see any data flow. 102 logger: Similar to 101 logger, 102 logger was sending Nan\’s only. As a trouble shooting, I isolated and disconnected G1 and G3, while G5 and G10 connected. After this, no data flow from either plots. I then disconnected G10 allowing only G5 to be connected to 102 logger. G5 sending data which shows G5 is good, and G10 is bad. I replaced multiplexer in G10 in order to resolve this problem. If G10 works along with G5, then I reconnect the other two plots, G1 and G3. 103 logger: As a trouble shooting, I isolated and disconnected G8 from 103 logger, while G6 connected, G6 sent data for two days continuously, then stopped. I am thinking now to replace the coax and data cable for G6 only. More report follows…

TDR 100 (SN 2216) is swapped in logger 102, because there were only Nan values are coming from plots G1, 3, 5 and 10. The problem started after I switched the power from SW source to 12 V in Cr1000. I found although this problem was not associated to switching the power source, as all these box were had power during this trouble. Nonetheless, I changed the tdr 100, hoping it will solve this problem. A multiplexer (sn 5247) is swapped in G2 plots, because 10 cm depth is not sending right values and also there is still identical values in the depths of 20 and 35 cm depth. The problem of identical values so far is not resolved even after changing multiplexer on three accounts.

In the logger 104, GT site showed all Nan values after I changed a TDR 100 on 04/24/2018. I am not sure, nan values in GT site was due to tdr 100 replacement or something else. Nonetheless, I put back the older tdr 100 (sn 2217) in logger 104 to make sure that I am not losing any data. Identical values in some depths of BT and GT is now resolved after tdr 100 replacement. Check these two sites and change anything what is needed.

Even after the replacement of multiplexer, there is no change in identical values in BT (between 10 and 20 cm depths) and GT (between 20 and 35 cm depths) plots. Since multiplexers already changed twice, this time I decided to replace Tdr 100, not multiplexer. A tdr100 (SN 3232) is thus changed in logger 104. Similarly, there is no change in identical values between 20 cm and 35 cm depth in G2 plot. I added a different multiplexer (SN 5241) to G2, hoping, the swapping of multiplexer will improve this trend. 10 cm depth probe in G2 and G9 are reinserted into the soil.

Replaced multiplexers in BT, GT of logger 104 and G2 sites. BT site: Replacement of multiplexer in BT site during Feb 2018 did not resulted in desired change in tdr pattern; identical values still occurring in depths 10cm and 20 cm depth, thus another multiplexer (SN 1143) is replaced today to take care of this. GT site: 20 cm and 30 cm depths showing identical values, thus a multiplexer (SN 5200) is changed today. G2 site: 20 cm and 30 cm depths showing identical values, thus a multiplexer (SN 5057) is changed today. I need to check the values of these plots in the next week or so.

Batteries changed in loggers 104 and 105 at forest transition sites

Installed a new solar panel in transition site (logger 104 and 105) to check the problem, that is occurring over the months. Problem: Batteries at 104 and 105 loggers are not charging full and they drained quickly. I checked the power cable of existing solar panel, and found this cable was damaged by deer. This might be the cause for the above problem.

Changed a solar charger (CH 150) in the logger 104 after batteries in both loggers 104 and 105 continue to drain even after their replacement.

Changed a battery in logger 105 (FT box)

Forest transition sites: 104 logger box: box cleaned, \”DESI PAK\” (desiccant packs) changed, battery is changed, solar panel was neat and clean and has good output volts- no concern with solar panel. After battery change, solar and battery reads good. BT box: \”DESI PAK\” (desiccant packs) changed. FT box (105 logger box): \”DESI PAK\” (desiccant packs) changed in both boxes, battery is changed, Multiplexer (SN 1330) changed following the same identical values in 10 and 20 cm depths (check the TDR templates of 2016 and 2017 for further comments). BCSE site: G3: A multiplexer (SN???) is changed after some issues with relays. 103 logger box: rebooted the TDR.

Some work at transition sites: Solar panel cleaned; a new battery is replaced in 104 logger box (Gt and Bt TDR); a multiplexer (SN 1388) is replaced in BT box following issues of identical data by 10 and 20 cm\’s depths (also check the comments in the template of BT_2017); also checked the battery volt of 105 logger (FT site)- seems battery at FT is OK. Remaining task at transition sites: should change a multiplexer in FT box in the future.

103 logger was rebooted after it stopped working; A multiplexer with SN 1328 is replaced today in G5 following relay issues in some layers; A multiplexer with SN 1324 is replaced today in G1 following relay issues.

A new multiplexer (SN 5244) is replaced in G10 box following the two depths (35 and 65 cm) reading the same value.

A new battery is connected to datalogger at CF site

A new data cable line was laid in the logger 103 box by Kevin and Zaman

A new power cable was laid out in TDR system at DF site

Following the problem and scattered values in 10 cm and 20 cm depths in G1, I have changed the multiplexer with SN 1330. Even after changing a newer multiplexer in G6, there have no been change in 35 cm depth. I just have to monitor this depth for some more time.

Following the problem in 35 cm depth of G6, I have changed a multiplexer with SN1325. It appears, there might be more of negative values.

Following suspicion on few layers (50, 60 and 125 cm) reading the same depth in G6, I have changed a multiplexer with SN 1388. Even after this multiplexer replacement, there is no change in the patterns of these three layers. Probably, those values reading in these depth might be good ones.

A multiplexer with SN 1328 is swapped in G6 of logger 103 after I found, that soil layers 50, 60 and 125 cm depth are suspected to read the same values. SN 1388 multiplexer has been removed.

A TDR 100 with SN 2216 have been swapped in logger 103. TDR 100 with SN 2404 taken out.

G1 and G3 are connected today to logger 102. Older data cable removed from 102 connecting g5 and g10. Newer data cable laid are connected to all boxes in 102 logger. Cameras are connected as well.

Kevin and I, added the newer data cables in 102 logger box. Older data cables were unplugged from the box and put them in the box buried in the ground. Newer data cable added through the buried conduits . Data cable in 102 logger runs first from G5 to G10, then G10 to G3, and then to G1. I also added a newer data cable between G6 and G8 to determine the cause for \”nan\’ that occurs every week.

Regarding 102 logger problem. After we moved the equipment from large tote box into the enclosure of 102, G5 and G10 and having the newer coax and data cables, the logger 102 was allowed to run for few days (G1 and G3 are not powered). Although, there was no Nan from TDR system, but the probes are not reading in G5 and G10. So we decided to use the older coax cables and revert the program back to older version. So, I plugged back the older coax to channels 2,3, 7 and 8 in the primary multiplexer. Sven updated tje 102 logger program back to older version. After this action, probes in G5, g10 are started to read, so finally success. Now we have to watch for any \”nan\” .

Multiplexer SN 1327 swapped in 103 primary enclosure

A TDR 100 with SN 2404 is swapped in logger 103 after I found logger was not sending data, only Nan. As soon as I TDR 100 changed, the logger started sending data. However, TDR 100 (SN 2216) that-off from the logger 103 had no issues while checking in the lab. Probably, the logger 103 must have stopped sending data by any other reasons, not by TDR 100.