Jay, Unfortunately there's no way to make XES weak at my location...unless he turns the wick way down :~) Maybe we can try that over the weekend, John. < A chain saw would reduce my ERP, too! I will
Hartmut, XES did run in the WOLF 2.5 speed all night. I will use the 5 b/s rate tonight with 50 watts, starting around 2330 UTC. Given WOLF's error correction with copy being built up over a period o
Wolf, WOLF now optionally runs faster (at 5 or even 2.5 symbols/seconds, besides the default 10), and also faster (with 20 or 40 symbols/second). Should that first "faster" actually be "slower?" John
WD2XES will be running WOLF in the 2.5 b/s mode tonight on 137.577 kHz, starting by 0000 UTC. At 6.4 minutes per frame, you may want to drop the number of frames per session to 9 or less. Reports are
Conditions were much better last night after the departure of Thursday night's storm. The best copy was around 0100, with both Brian and Jim visible: Note that there seems to be a keying error on the
Hartmut, VE7SL was observed near that frequency last night, but was never visible here, so I can't testify about the frequency. John A. Hartmut Wolff wrote: Attached a screenshot with 2 QRSS120 dashe
Saw some activity on 136.318 that was probably Brian's. I may have caught a "C" from Laurie around 0130: That's it! The weather forecast is much better for tonight. John Andrews, W1TAG JPEG image
Steve, We were probably just far enough east of the noise to make a difference. It looks like tonight's conditions will be quite dismal here, though. John A. Hi John, Congrats to you and Jay; I watch
I had about the same results as Jay last night. The best copy of CT1DRP was just before 0000 UTC: M0BMU was identifiable by frequency, but only fragments of the callsign could be seen. Here's an "M0"
Dave, Let me correct another error from earlier today. I must have been looking at the wrong spot in the large table of Loran lines. The nearest eastern U.S. line to 136.320 is 0.28 Hz higher, which
Steve, OK - I'm confused, but that's easy as you know. Shouldn't that be 136.320 to be on the same screen as 136.318kHz,+/-? Yes, you're right of course. Dave and I aren't too handy with numbers...<g
Dave, 136.200 has a Loran line only 0.2 Hz away, but that's possible. The trouble is that we would have to run multiple screens, as it would be out of view while looking at 136.318. If you do indeed
Jim, That's good news! However, the area around 135.92 kHz has now become useless in the U.S. and Canada due to a west coast military station. We have suggested 136.318 kHz as an alternative, and CT1
Uwe, good receiving of XES. pse see attachment. Nice copy. I will add you to the QSL list. Just sent 12 cards out, and already need to do a few more. Thanks! John Andrews, W1TAG/WD2XES
Uwe, Are you sure of the frequency? I'm guessing that it's Dex, WD2XKO, who is on 137.7777 kHz. John Andrews Hi, SpecLab screen shows signs near 137,7766..kHz I cant identify: regards Uwe/dj8wx/jo43s
