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.