What about PSKReporter? (http://www.pskreporter.info <http://www.pskreporter.info> ) While there is not a direct interface from the PSKReporter output back into your digital comm program (that I know of), there are certainly decent interfaces in fldigi (Thank you, David and friends) and HRD (Thank you, Simon and friends) to PSKReporter. And the data is pretty fresh. With the map display, there is no mystery which bits of traffic are DX.
- Doug/KE7SEI --- In digitalradio@yahoogroups.com, "Dave AA6YQ" <aa...@...> wrote: > > >>>AA6YQ comments below > > -----Original Message----- > From: digitalradio@yahoogroups.com [mailto:digitalra...@yahoogroups.com]on > Behalf Of Andy obrien > Sent: Monday, February 22, 2010 9:56 PM > To: digitalradio@yahoogroups.com > Subject: [digitalradio] PSK SPOTS > > > > That is a good point, Alan. Now that i think about it, you would think that > after 10 years we would have come up with a point and click method. > > >>>In WinWarbler, one click in the waterfall selects a PSK signal, and one > click of the Spot button generates an outgoing spot (via SpotCollector). > > >>>Double-clicking a PSK Spot Database Entry in SpotCollector directs > WinWarbler or MultiPSK to immediately begin decoding the spotted station, > QSYing the transceiver as required to achieve the specified optimal offset. > Alternatively, one can click a plotted DX spot on DXView's World Map or > click a DX spot on Commander's bandspread to accomplish the same result. > > >>>WinWarbler's broadband decoder continuously identifies active PSK QSOs > within the receiver bandpass, listing the decoded callsigns in its "Stations > Heard" window. Optionally, these callsigns can be inserted into > SpotCollector's Spot Database, where they are color coded for "need" with > respect to the user's award objectives and award progress, dynamically > obtained from DXKeeper. Thus its straightforward to identify needed PSK DX. > > >>>These capabilities have been in broad use by DXLab users for many years. > > 73, > > Dave, AA6YQ >
