(2024-12-29, 23:52)dupreezd Wrote: [ -> ]Yes, this is strange. GPS seems to functioning just right.
I have those ADC alignment errors as well.
Sorry, for now I am also out of ideas as well, lets wait for input from others.
I see a couple of possibilities.... signal quality.
First, controller: to SEND series, the trigger (threshold) in
triggering channel must be at least
TWICE the noise level in that channel. That is, the
ADC trigger MUST be at least twice as high as the noise level .e.g. 100mv threshold against 55 mv noise level won't trigger a send. THEN IF the 'ignore signals below' percentage is too high, say 90%, controller should ignore any signal <90mv, even if ADC has triggered on another channel.
THEN:
Once received at computing server, IF a channel's
'signal' amplitude peak is NOT
at least 3 times the SERVER computed noise level average over first 250ms of that channel's window, the server will NOT compute the channel.
[
attachment=4912]
You have a LOT of noise, both low frequency (Power mains??)
and other faster signals. I believe they're likely culprits killing your signal recognition. I watched a few minutes, didn't observe any obvious 'sferics', just noise, so your stats look about right for what I saw... .
I think the above image indicates the controller fired on 'red' channel, sent all, then 'server' actually wanted the 'green' channel, but 'green' failed test 2, (250ms noise/amplitude at trigger time of 'red') so 'validated' 'red' channel, but couldn't associated data with any strokes. So "Signals =1" "Valid"=1 "Involved"=0 "Used"=0 for this signal.
ALSO note your sieve timing adjustment excellent for Red and Green channels... that's the "DNA" for the last 1000 signals, which indicates most of your sieve memory matches this noise signal pretty well, indicating it's holding a LOT of noise signals, so will take a bunch more strokes to overcome that junk 'bias' in your station's genetic picture! Especially since it REALLY had to 'retime' the 'yellow' channel data!
Good Luck!
Mike