Hi,
Im not sure if im correct in having the CallTable within the slowsequence 1sec scan, while there is a 250ms sensor in the data table.
Or is it neccesary to call the table in the 250ms main scan?
As a test i made the Rain_mm=0.01 to see if it is missing data.
The test show a total in the datatable of 0.60mm so it looks like it is working ok.
See example:
Public Rain_mm
Public AirTC
DataTable(Table1,True,-1)
DataInterval(0,1,Min,10)
Totalize(1,Rain_mm,FP2,False)
Maximum(1,AirTC,FP2,False,False)
EndTable
BeginProg
Scan(250,mSec,0,0)
Pulsecount(Rain_mm,1,1,2,0,0.1,0)
NextScan
SlowSequence
Scan (1,Sec,0,0)
VoltDiff(AirTC,1,mV2500,3,True,0,_60Hz,0.05,-65)
Calltable Table1
NextScan
EndProg
Hi,
the slowscan has a lower priority than the main table, so it may happen that it is not executed.
In practice it is performed in the time remaining between the executions of the main one
Each time this happens, a counter of status errors is incremented.
Smile
Makada, with the CallTable in the Slowsequence, this is only called every 1s. So, it adds to the total whatever value is in "Rain_mm" every 1s.
In the main scan the PulseCount sets the value in the "Rain_mm" to be the number of tips from the bucket raingauge. As this is normaly either zero or 0.1 every 250ms, you could miss tips as it is not totalised every 250ms. Ie. at 0.25s, the value in rain_mm is 0.1, but at 0.5s, there is no new tip, so the rain_mm is zero. It would be better to put the CallTable in the main scan then it will include every tip from the raingauge.
Of course, at that rate it would difficult for a raingauge to fill up and tip more than once in a 1s period, but the principle remains.
The fact that your average calculation will include 4 of the same values to calculate AirTC the average gives the same result.
Thanks alot smile and nsw, that makes sense.
I realy like to have all data in one table, but thats not going to work.
With kind regards.