It was really terrific to snag you on JT6M meteor scatter (1572 miles) this morning, and I'm especially pleased to see a resurgence in interest in JT6M on the Ping Jockey page today and tonight. The European MS ops make greater use of JT6M than we do here in North America....perhaps we could be making more DX QSOs by following their example.
Thanks Joe for making such a fantastic program available to the ham community. Long live JT6M.
-------------- Original message --------------
> Today I worked AJ6T using JT6M. Walt started calling CQ at 14:48 my
> direction. We let Walt know we were listening but really didn't expect to
> hear a thing. At 15:27 I copied and decoded Walts CQ!
> I stared calling Walt at 15:27 and we finally completed at 17:31 UTC. We ate
> dinner, visited with company and washed dishes among other things during the
> contact. Patience & long runs can pay off. Connie wrote on PJ this morning
> it is hard to find stations willing to run the time required for long
> distances. I have always thought for those long distace contacts a minimun
> of 1 hour is required to make a decision and if you have one ping the
> contact is probably possible but could take an additional hour or more. So
> after the first hour, you need to be prepared to run longer.
> I finally have worked California on six meters via meteors. On my end all
> but the RRR ping were strong enough for FSK441 but Walt says only JT6M would
> have worked on his end.
> I am wondering if in NA if we have been overlooking JT6M in preference of
> FSK441 contacts. We have all heard pings too short for JT6M but the issue is
> reopened for me, especially long distance attempts.
> I used Version 5.8.3 and no files were saved when I clicked on "Save
> Current" button in JT6M mode. Anyone else had this problems with the "save
> current" function during JT6M contacts?