Hi Hugh
Its a little messy , when stations use half of the system , its possible
to enter the dynamic list , by running the opera app and clicking Tx on
136 and/or 477, once in the list, random noise can trick the comparator,
to show a match, the tell tail is the time and if the station is using
a fixed frequency , the recovered frequency from the app should be the
same ..
Its possible, to be spotted by the dynamic system and never actually TX,
ie , by up loading a call , hence the system cross checks with other
users for a time match, but this is the downside of the extra 5 or 6 dB
gained by pattern matching , [136 and 477 only] , that's the same for
any correlation system
73-G
example of time stamp quality check ,
g4wgt has decode at 1929 , DL-SWL has detection, the spot times meet the
check limits = ok
19:29 477 G0NBD de DL-SWL Op8 569 mi -32 dB F:10% in 1502,2 Hz
19:29 477 G0NBD de G4WGT Op8 21 mi -9 dB F:19% in Chorley, IO83qo, 1511.2
Hz
Ik1HGI decode with DF8UO , then qty-3 dynamic spots at the same time =
ok as well
19:37 477 IK1HGI de DF1VB Op8 Deep Search -36 dB in Dortmund 1496,1 Hz
19:37 477 IK1HGI de DF1VB/1 Op8 Deep Search -34 dB in Dortmund 1496,3 Hz
19:37 477 IK1HGI de F6CNI Op8 Deep Search -35 dB in JN19QB
19:36 477 IK1HGI de DF8UO Op8 -27 dB F:14% in Karlsruhe
random noise has triggered g4wgt by vk - '??' = false g4wgt not sending
at this time
18:29 477 G4WGT de VK3XHM Op8 Deep Search ?? -37 dB in Melbourne
Australia 1503.4 Hz
'??' Not known , if the next spot from df1vb/1 shows 1510 Hz , then is
valid , if not = false
18:12 477 G0NBD de DF1VB/1 Op8 Deep Search ?? 465 mi -37 dB in Dortmund
1510,0 Hz
My local spots for df1vb = same frequency = ok
19:48 477 DF1VB Op8 Deep Search -35 dB 1496.1 Hz
18:42 477 DF1VB Op8 Deep Search -36 dB 1496.1 Hz
--------------------------------------------------
From: "LineOne" <[email protected]>
Sent: Monday, September 19, 2016 8:15 PM
To: <[email protected]>
Subject: Re: LF: A few reports Sept 18th to 19th
Hello Graham.
It was a suspect positive at 1702 but it's a bit too late to double check
the dynamic list and other receiving stations though I recall
transmissions were listed at several times in succession but differ from
my report. I suppose there are other possibilities such as his entering
the wrong frequency. Rightly or wrongly my posting was only information
for the sending stations and I naturally rejected all the other suspect
reports.
73, Hugh, M0DSZ
On 19/09/2016 16:27, Graham wrote:
Hugh
For the call to be in the dynamic list , it has to be either by the
TX station using the opera app and setting TX with 136 selected ,
the web - beacon will update the system , or QTY 2 decodes of the same
call by other stations ...
The call must of been in the list , for you to spot it .. [ dynamic
only compares the call's listed ]
If the class cannot use 136 , then its possible you have a false
positive
Where you the only station to see the call at 17-02 ? if so, then
the web linked spot would of been stamped '??'
73-G,
--------------------------------------------------
From: "LineOne" <[email protected]>
Sent: Monday, September 19, 2016 11:32 AM
To: <[email protected]>; <[email protected]>
Subject: LF: A few reports Sept 18th to 19th
A few reports overnight from Sept 18th to 19th:
WSPR15
1600 -13 0.8 0.137620 1 DK7FC JN49 30
1630 -14 0.8 0.137620 0 DK7FC JN49 30
and then consistently until:
2330 -12 0.4 0.137620 0 DK7FC JN49 30
0030 -34 0.4 0.137603 0 R7NT KN97 53
0230 -35 0.4 0.137603 0 R7NT KN97 53
2145 -9 -0.6 0.137623 0 G8HUH IO81 20
2215 -11 -0.9 0.137623 0 G8HUH IO81 20
WSPR2
0850 -32 -0.5 0.137459 0 DF1VB JO31 13 437
OPERA32
17:02 -42 1468.4 Hz DO5JWA
(deep search: appears to be correct)
Hugh, M0DSZ
|
