When water droplets go from being present to not being present over the probe head there is a noticeable decay in the data which causes a curve to be present when graphed and shows that there should be droplets during this time even though during test runs there shouldn't be. Below are some examples of data collected to visibly show this issue with the WCM.

• Reference: /nas/und/NorthEast/2025/Lab/CH423/GroundData/20250416_165626/PostProcessing
• Reference: /nas/und/NorthEast/2025/Lab/CH423/GroundData/20250416_165626/Camera_Data

Below is a collection of pictures with their associated graph to show what the WCM reading is compared to frames from the video showing the mist that is being sent over the probe at that given time.

The main thing to notice in the images provided above is that there is an apparent delay in when the WCM reads 'zero' to when the probe head experiences zero water content present. The zero value in this case is at around 2.2 seen on the graph and this is also another issue that is present with the WCM in which it doesn't record a zero value during the presence of no water.

The delay between when the WCM displays a 'zero' value and when the probe should be at zero is around about a five or so second delay which can be observed by the graphs. Which after applying a 66.7% data validity factor to the delayed seconds this comes out to being about a 3.34 second delay where data is being displayed that shouldn't be.

During the setup of the WCM, we were having issues with the power not being supplied to the WCM Power Box which prompted the WCM software to say that ser17 can't open.

The power connection of the leads from the WCM Power box to the D/C Power supply was not making a good connection with the prongs themselves on the D/C Power supply.

The leads coming from the WCM power box where squeezed together to help in making better contact with the prongs on the D/C Power supply.