[Lowfer] Copied on 160m 4/22/10 (With help of KU4XR)

[Trevor Smithers]

Hello Rick,
This looks like random noise that just happens to have been interpreted by WSPR as valid data. 
Switch mode power supplies or powerline noise can often cause false decodes. 

>I was monitoring 1.836.60 USB with a Yaesu 1000MP and a 160m
>Loop approximatley 35'-40' off the ground.
No problem there

>Also just noticed I had 18db
>of attentuation cut on using the 2.4k filter.
While WSPR is running in receive mode have a look at the bottom left corner of the WSPR 
screen and you will see the "RX Noise" box. This should show something around 0dB, +/- 5dB 
is ok but if you find its much higher/lower then you may have too much attenuation or need to 
adjust the soundcard input to bring it back within range.
Noise blankers can also make a mess of decoding.
Reducing your rx filter bandwidth can often improve decoding.
   
>However, after further research it appears the following from one of the
>websites: 
>S59VVH was in RE12 in Slovenia at 9114 miles. 
>670LQP was in EA92 in ??? At 8527 miles.
The S59 call looks genuine but a search of  the database doesn't show it as ever having been 
active on WSPR so its probably just coincidence... and the RE12 grid square is around ZL

WSPR User Guide here
http://physics.princeton.edu/pulsar/K1JT/WSPR_2.0_User.pdf

Would also be worth registering on the WSPRnet site, all sorts of questions/answers in the 
forum etc
http://wsprnet.org/drupal/

Hope this helps

73
Trevor  G0KTN