Atmos Wiki

User Tools

Site Tools

Trace: • yearly_archiving • pos • calibration_validation • documentation • notifications • home • home • home
atmos:instruments:wcm:home

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
atmos:instruments:wcm:home [2025/05/23 15:04] – external edit 127.0.0.1atmos:instruments:wcm:home [2025/06/24 15:43] (current) – rickbeil
Line 7: Line 7:
  
 ==== Cause ==== ==== Cause ====
-In the fml.300 table that is present on the m300 computer and is used by the WCM data collection software it was noticed that the code that is supposed to correct for this non zero value wasn't included in the table. There was however correction code in there but it appeared to be from the older WCM model in which it had a compensation term that would remove this non zero value and instead keep the probe at a zero value until water content is present. '+In the fml.300 table that is present on the m300 computer and is used by the WCM data collection software it was noticed that the code that is supposed to correct for this non zero value wasn't included in the table. There was however correction code in there but it appeared to be from the older WCM model in which it had a compensation term that would remove this non zero value and instead keep the probe at a zero value until water content is present. 
  
 ==== Solution ==== ==== Solution ====
-In the manual for the WCM 3000 probe there is a section in which a couple different was are discussed as to how to get the probe to go to a zero value during the non presence of water. **(These will be added here)**.+In the manual for the WCM 3000 probe there is a section in which a couple different ways are discussed as to how to get the probe to go to a zero value during the non presence of water. The way that was used in our correction of this issue was as follows; Psensedry = K1 * (Tsense - Tambient)*(Pambient * TAS)^k2. Where Psensedry is the value that is subtracted from Psensetotal which gives us Psensewet, K1 is a constant that is used which can be changed based upon testing of the probe, Tsense is the temperature of the sensor, Tambient is the ambient temperature, Pambient is the ambient pressure, TAS is the true airspeed, and K2 is another constant that can again be found by testing of the probe. This together does appear to work in the laboratory setting but still should be tested in the field as the higher airspeed values might cause the need for changing the constants K1 and K2 as needed. 
  
 ===== Problem (Spring 2025) ===== ===== Problem (Spring 2025) =====
Line 64: Line 64:
 Now that the long decay was removed from the graphs by removing the averaging function in the fml.300 table the PID controller should now have a more noticeable impact on the data collected. **Another thing to note which was found during the initial PID tuning was that the derivative term will also contribute to a decay since the derivative term is acting as a dampener to stop the probe from immediately going to zero after water content is stopped.** So now taking that into account when tuning the PID board it is known that the derivative term should be set fairly low so as to stop the probe from over dampening itself during data collection. The values that were found that allowed the probe to work fairly well are as follows; **(TWC terms Kp- 2000 Ki- 90 Kd- 20) (LWC terms Kp- 9500 Ki- 95 Kd- 20)**. These values were only tested during no airflow to try and calibrate the probe to be as stead as possible. This was done as a control just to factor out the unpredictability of the airflow that would normally be present over the probe and to make the tuning of the probe more easier.  Now that the long decay was removed from the graphs by removing the averaging function in the fml.300 table the PID controller should now have a more noticeable impact on the data collected. **Another thing to note which was found during the initial PID tuning was that the derivative term will also contribute to a decay since the derivative term is acting as a dampener to stop the probe from immediately going to zero after water content is stopped.** So now taking that into account when tuning the PID board it is known that the derivative term should be set fairly low so as to stop the probe from over dampening itself during data collection. The values that were found that allowed the probe to work fairly well are as follows; **(TWC terms Kp- 2000 Ki- 90 Kd- 20) (LWC terms Kp- 9500 Ki- 95 Kd- 20)**. These values were only tested during no airflow to try and calibrate the probe to be as stead as possible. This was done as a control just to factor out the unpredictability of the airflow that would normally be present over the probe and to make the tuning of the probe more easier. 
  
-These above PID values still need to be tested in lab to validate that they are actually good values that should be used during future field campaigns with this probe. +==== Solution Two Continued... ==== 
 +Continuing on with the second solution the PID values were now tuned with airflow present over the probe which did result in different values from the zero airflow calibration. The values that were found are as follows **(TWC terms Kp - 1500 Ki - 25 Kd - 200) (LWC terms Kp - 2000 Ki - 25 Kd - 150)**. These values overall did improve the response time in the WCM 3000 but something to still note is that these are not perfect. There is still a 1-2 second delay present in the data which seems to be just a limitation of the probe itself and not necessarily something that can be fixed. **(These values have yet to be tested on an aircraft at higher airspeeds meaning that these are still subject to change since these values were only derived at lower airspeeds, further updates may be needed to these values)**
  
 ===== Problem (Winter 2024) ===== ===== Problem (Winter 2024) =====
atmos/instruments/wcm/home.1748012691.txt.gz · Last modified: 2025/05/23 15:04 by 127.0.0.1