Deep search, in bozo terms. can be explained thus.. software is on, rig is on. Software is seriously hunting for signs of a JT65A signal despite weak signals, or more likely NO signals. Sofware spots a fragment of something that might eb JT65A and say "hmmm, I wonder who this might be? Software thinks a while and then says "Hmm, well I know that my set-up area has K3UK as the callsign, so I am going to guess that this fragment of a signal is someone calling K3UK". Software thinks some more and says "Hmm, maybe I'll look up the text file containing a list of callsigns and grid square and see who it might be calling K3UK".. Software then essentially takes a whild guess and then prints...
022700 0 -30 7.2 541 5 K3UK P5DX PM27 0 3 K3UK gets excited at working North Korea on 15 meters at 0227 Z with a solar flux of 68 in Spring at the bottom of an 11 year cycle and a predicted MUF of 3.6 mHz. Andy thinks that it is quite natural that P5DX would call him just to see if ANdy was in the shack. That's because Andy is a bozo... Andy K3UK On 4/19/07, cesco12342000 <[EMAIL PROTECTED]> wrote:
> How would one format an "HF call3.txt" example from file: ZS6GPM,KG33XU,,,,,,10/02 i think format is callsign,locator,,,,,,date additional entry would be: HB9TLK,JN47HJ,,,,,,3/07 Guess for HF the EME entries could be deleted to avoid false detects.
-- Andy K3UK Skype Me : callto://andyobrien73 www.obriensweb.com
