KJ9I EME - Heard (not worked)

Dave KJ9I was trying to work DU1GM (George) and I was listening in this morning in hopes of seeing George.  I copied Dave VERY WELL several times.

JH0BBE EME - Heard (not worked)

Yuji the first single Yagi 6m EME decode that I've had.  He indicated that he was running 500w and a single 8 EL.  I run 1.5kw and and a 10EL.  Until now the smallest I've decode have been 2 antenna systems.  The moon this week has been the best I've seen.

After I found Yuji's trace and discovered he was calling I noticed there were 4 min of traces prior.  I just wasn't aware that he'd been calling until it was too late.  May have completed if I'd noticed sooner. 

Still this is very encouraging.  Moon Set is often much quieter than moon rise here.

W5ADD EME - Heard (not worked)

Parker had noise locally and didn't copy me, but had a nice signal in here via the moon.

JR6EXN EME - Heard (not worked)

I had some good echo's this morning on my moonset

Attempted to work Hide (JR6EXN) and copied him one time.

S57RR EME - Worked

Bert and I have been trying for about a year to work Earth-Moon-Earth today we finally made it.

NASA DWPR 2015-07-30 Interference @ 50 MHz

NASA Form to report reception of this sort of interference

These two video's show the NASA KSC DWPR very strong into the 50 MHz Amateur Radio Spectrum allocation.  These video's show 2.5 MHz of spectrum starting about 49.000 MHz. 

To view more like this back as far as 2011 visit this YOUTUBE Playlist

The following is what the DWPR might look like if you only have a limited spectrum display.
Note the ON/OFF nature of it.  Also the Spacing between carriers changes as the pattern changes.  Sometimes they'll be closer (more of them) sometimes less.

Click to Zoom

This Radar's location is at about EL99pp Maidenhead Grid Square.

• Work Begins to upgrade drwp @ NASA
• KSC writeup on DRWP
• Some detail about the system
• More in-depth Detail
• ITU M.2013 mentioning WPR @ 50 MHz
• 50 Mhz Doppler Radar Wind Profiler Filters

CW Skimmer > Aggregator 4.0 & 4.1 (double posts?)

UPDATE:

I found the cause of this after I posted this.  At least I'm pretty sure.

Aggregator allows you to setup a Primary Skimmer, and several "Secondary" skimmers.  I had mistakenly added the same detail for my Primary Skimmer as a "Secondary" skimmer in addition to my REAL secondary skimmer.

To the author of "Aggregator" I'd recommend checking any secondary skimmer's against what's setup in the primary and disallow the same detail to be added as a secondary and connected at the same time.

This shouldn't have taken me so long to figure out.  And certainly wastes a lot of resources.  I feel kinda stupid about it.  But anyway if anyone else runs into something like this just be sure your 'Secondary' Skimmer isn't also setup as the Primary, at the time of this writing Aggregator allows it, and WILL DOUBLE SPOT to the RBN because of it.

----------------------------------------

Black box at the top of this image below is a telnet into my CW Skimmer, the same way

"Aggregator 4.0 & 4.1" would.  This 'should be' what Aggregator reports...but instead it's sending a spot two times to the RBN.

Click on the image to see zoomed.

I can't seem to resolve why I'm getting double posts for things like this.

This results in DOUBLE posts on the RBN seen below

Another Example