In CR1000 OS 15, the following fix was made:
"Fix WindVector using aliases."
In CR1000 OS 19, the following fix was made:
"Fixed WindVector so that the default units of "Deg" is inserted correctly."
In CR1000 OS 21, the following fix was made:
"Fixed default units for WindVector."
What specifically (details and examples please) was done in each of the above OS fixes?
Thank you.
I can't confirm until I update the OS on my loggers but it may be related to this feature/bug (a program chunk followed by a bit from a data file):
From the program:
Units WindSpeed()=meters / second
Units Wind_Direction = Degrees
' ...
WindVector (1,WindSpeed(1),Wind_Direction,FP2,False,0,0,0)
From the .dat retrieved by LoggerNet:
"TOA5","SS_Met","CR1000","30801","CR1000.Std.20","CPU:ss_met_2010-10-14.CR1","63078","Wind"
"TIMESTAMP","RECORD","WindSpeed_WVc(1)","WindSpeed_WVc(2)","WindSpeed_WVc(3)"
"TS","RN","meters / second","meters / second","meters / second"
"","","WVc","WVc","WVc"
I have not confirmed these assumptions, but ---
"Fix WindVector using aliases."
To me, this would mean that the WindVector instruction was not properly referencing memory locations that had been Aliased. For example, if you were using array and repetitions for reading two wind sensors, you might also alias those measurements to give them descriptive names:
--
Public WS(2)
Public WD(2)
Dim I
Alias WS(1) = WindSpd_3m
Alias WS(2) = WindSpd_10m
Alias WD(1) = WindDir_3m
Alias WD(2) = WindDir_10m
DataTable(Table1,True,-1)
DataInterval(0,60,Min,10)
WindVector (1,WindSpd_3m,WindDir_3m,FP2,False,0,0,0)
WindVector (1,WindSpd_10m,WindDir_10m,FP2,False,0,0,0)
EndTable
BeginProg
Scan(5,Sec,1,0)
PulseCount(WS(),2,1,1,1,0.75,0.2)
For I = 1 To 2
If WS(I)<0.21 Then WS(I)=0
Next I
BrHalf(WD(),2,mV2500,1,1,1,2500,True,0,_60Hz,352,0)
For I = 1 To 2
If WD(I)>=360 OR WD(I)<0 Then WD(I)=0
Next I
CallTable(Table1)
NextScan
EndProg
--
"Fixed WindVector so that the default units of "Deg" is inserted correctly."
and
"Fixed default units for WindVector."
Would be similar bugs found related to the Bobfbks' comment that the table headers were not properly populated with the correct units. This would not have affected your measurements, just the meta data / table headers.