File Attachment 1: 04aug-PBJ.jpg
File Attachment 2: 04aug-WM.jpg
WSPR
I restarted experimenting with WSPR, mainly to tinker with my new toy, a SotaBeams WSPRlite transmitter. I noticed the WSPRnet.org DATABASE tabulation for my spots, and for other participants' spots power is reported as "watts" and some call signs are listed using the once prohibited slant bar "/" symbol, e.g., W1ABC/2 or the call sign contains more than 6 alphameric characters as in WA1ABC/9.
However, on the WSPRnet.org web site power is entered and displayed in dBm, and call signs can not use the "/" symbol and more than 6 alphameric characters, ref: the bottom of this web page http://wsprnet.org/drupal/downloads
Has some thing changed and the web master not updated the support pages?
73 Frank Lotito K3DZ / WH2XHA Re: WSPR
Posted by John Davis on August 02, 2017 at 14:48:01.
In reply to WSPR posted by Frank Lotito on August 02, 2017
The only thing that appears to need revision is the sentence on the wsprnet.org/drupal/downloads page which says: "WSPR encoding of callsigns does not encode portable or other qualifying (slash) designators, so the call may not represent the true location of the transmitting station."
That one sentence is now outdated. Somewhere after 2009, the WSPR coding format was modified to accommodate "/" and longer ID strings (at the expense of having to alternate between the sending of ID and grid locator in separate transmission slots), and if you look inside any of the recent download CSV files from that page you'll see plenty of slant characters among the call signs, just as displayed in the database search page.
As for dBm versus watts, the WSPR coding and spot reporting formats have always been in decibels referenced to one milliwatt, as that allows for stating a very wide range of possible powers in just two digits, and without having to keep track of decimal points, etc. Whether you upload spots in real time or do it via bulk uploads of ALL_WSPR.TXT, it's always in dBm. The database results page merely chooses to convert and display power in watts for the reader's convenience.
But if you're using the archived data for analytical studies, you'll probably want to see power in its "native" format, dBm, for ease in comparing path performance between different stations, because the SNR is also reported in decibels.
John
Fri. Morning - WM, MTI, PBJ etc
Posted by John Davis on August 04, 2017 at 16:00:38.
Shortly after 9 AM, only NC was visible. PBJ was nice and solid at 13.557500 MHz. After that capture (attached), I tuned to the top half of the band, but only saw--and slightly heard--GNK.
Back at the watering hole, WM was also now present with good CW ID quality, and MTI began appearing visually and sometimes aurally on the top of the minute. I've attached that capture too. By then, NC was joined faintly by EH in semi-noise-mode on almost the same frequency.
John
---------------------------------------------------------------
File Attachment 1: 04aug-PBJ.jpg
File Attachment 2: 04aug-WM.jpg
Fri. Mid-day
Started getting bits of SIW WSPR just over an hour before noon, CDT.
1556 -20 -0.7 13.555404 0 K3SIW EN52 7 1612 -33 -0.9 13.555404 0 K3SIW EN52 7 1644 -30 -1.8 13.555405 0 K3SIW EN52 7 1648 -24 -1.2 13.555405 0 K3SIW EN52 7 1656 -26 -1.2 13.555405 0 K3SIW EN52 7 1700 -25 -1.0 13.555405 0 K3SIW EN52 7 1704 -31 -1.9 13.555405 0 K3SIW EN52 7 1712 -30 -1.2 13.555405 0 K3SIW EN52 7 1716 -27 -1.7 13.555405 0 K3SIW EN52 7 1736 -31 -2.0 13.555405 0 K3SIW EN52 7 1740 -25 -1.1 13.555405 0 K3SIW EN52 7 1744 -24 -1.3 13.555405 0 K3SIW EN52 7 1748 -24 -1.1 13.555407 0 K3SIW EN52 7 1752 -22 -1.1 13.555405 0 K3SIW EN52 7 1756 -28 -1.9 13.555407 0 K3SIW EN52 7 1800 -25 -1.2 13.555405 0 K3SIW EN52 7 1804 -21 -1.4 13.555406 0 K3SIW EN52 7 1808 -21 -1.2 13.555406 0 K3SIW EN52 7 1812 -22 -1.0 13.555406 0 K3SIW EN52 7 1816 -27 -1.0 13.555406 0 K3SIW EN52 7No sign of SIW slant today, though. The attachment this time shows the remainder of the watering hole denizens, including MTI and WM fading in and out over time. EH and NC are no longer in collision. The slight trace of excess RF right above EH might or might not be USC.
Kp levels have been hovering around 4 all day and are expected to crest at G1 or G2 late this afternoon. Will be hoping for interesting effects if that should occur.
---------------------------------------------------------------
File Attachment 1: 04aug-1pm.jpg
Re: Fri. Mid-day
John
After your last few captures of WM showing the frequency being a tad low, I rechecked the calibration of my receiver and found it was off also. I have been adjusting the equipment here to get it back on 300. I hope your next report shows it in the proper place.
Mike 73
Fri. Late Afternoon (PCO, GNK, more PBJ & WM)
Posted by John Davis on August 05, 2017 at 05:01:55.
In reply to Re: Fri. Mid-day posted by Mike N8OOU on August 05, 2017
Not having seen your message before returning to the field, Mike, I didn't do a really intensive calibration check on the receive frequency this evening. WM is only a few Hz closer, by my captures, but that may not mean a lot. This afternoon's calibration was within +4/-0 Hz, while this evening's (04aug-wh.jpg file attached) is closer to ±2 Hz. (The one early this morning was approximately ±1 Hz.)
By late afternoon, there had only been a few more captures of SIW WSPR, after which it never returned before I shut down at sunset:
1820 -23 -2.0 13.555405 0 K3SIW EN52 7 1832 -27 -1.1 13.555405 0 K3SIW EN52 7 1836 -24 -2.1 13.555406 0 K3SIW EN52 7 1840 -27 -1.5 13.555406 0 K3SIW EN52 7 1912 -26 -1.2 13.555406 0 K3SIW EN52 7 1924 -27 -1.5 13.555403 0 K3SIW EN52 7 1928 -28 -1.2 13.555406 0 K3SIW EN52 7 1936 -27 -1.0 13.555407 0 K3SIW EN52 7 1948 -22 -1.3 13.555407 0 K3SIW EN52 7 1952 -25 -1.1 13.555407 0 K3SIW EN52 7 1956 -27 -2.0 13.555407 0 K3SIW EN52 7By late afternoon, though, I was getting surprisingly good signals from other directions. PCO was recognizable on Argo and became audible enough at times for one or two characters, and one really good aural ID right before 6:19 PM CDT; see attached capture.
PBJ was strong again for the better part of the 7 PM hour. This evening's captures are nearly identical to the earlier ones, so I'm not posting more just yet.
GNK was remarkably strong for a time, too; even good enough for a while to get a reasonable capture on old Argo build 134's NDB mode. (It has to be really good to the ear to show up in NDB mode!) The attached GNK capture shows both the QRSS3 and NDB images.
John
---------------------------------------------------------------
File Attachment 1: 04augGNK.jpg
File Attachment 2: 04augPCO.jpg
File Attachment 3: 04aug-wh.jpg
Beacon Jam 187.015 khz and solar eclipse
Hey there fellow Lowfers. I was wondering if anyone wants Beacon Jam 187.015 khz So Cal to be on the air for this event. If any interest I can be on the air for the entire 24hrs. Midnight 8/21 to midnight 8/22. Thanks. WSPR-2 136 kHz. Aug. 6/7
KE6PCT
Posted by John Bruce McCreath on August 07, 2017 at 13:04:23.
I set up for WSPR-2 on 136 kHz. last night and here are the results:
0312 -31 -0.9 0.137528 0 WH2XND DM33 43
0316 -26 -0.8 0.137528 0 WH2XND DM33 43
0320 -28 -0.9 0.137528 0 WH2XND DM33 43
0452 -28 -0.8 0.137528 0 WH2XND DM33 43
0456 -29 -1.0 0.137528 0 WH2XND DM33 43
0512 -28 -0.8 0.137528 0 WH2XND DM33 43
0516 -28 -0.9 0.137528 0 WH2XND DM33 43
0612 -31 -1.0 0.137528 0 WH2XND DM33 43
0616 -23 -0.8 0.137528 0 WH2XND DM33 43
0620 -24 -0.8 0.137528 0 WH2XND DM33 43
0624 -22 -0.8 0.137528 0 WH2XND DM33 43
0636 -27 -0.9 0.137528 0 WH2XND DM33 43
0644 -24 -0.9 0.137528 0 WH2XND DM33 43
0648 -23 -0.8 0.137528 0 WH2XND DM33 43
0652 -23 -0.9 0.137528 0 WH2XND DM33 43
0656 -23 -0.9 0.137528 0 WH2XND DM33 43
0700 -27 -0.8 0.137528 0 WH2XND DM33 43
0724 -24 -0.9 0.137528 0 WH2XND DM33 43
0728 -22 -0.8 0.137528 0 WH2XND DM33 43
0732 -22 -0.8 0.137528 0 WH2XND DM33 43
0736 -23 -0.8 0.137528 0 WH2XND DM33 43
0740 -27 -0.9 0.137528 0 WH2XND DM33 43
0748 -25 -0.8 0.137528 0 WH2XND DM33 43
0752 -24 -0.9 0.137528 0 WH2XND DM33 43
0756 -25 -0.8 0.137528 0 WH2XND DM33 43
0800 -23 -0.8 0.137528 0 WH2XND DM33 43
0804 -27 -0.7 0.137528 0 WH2XND DM33 43
0808 -26 -0.9 0.137528 0 WH2XND DM33 43
0820 -25 -0.8 0.137528 0 WH2XND DM33 43
0824 -24 -0.8 0.137528 0 WH2XND DM33 43
0828 -26 -0.7 0.137528 0 WH2XND DM33 43
0832 -28 -0.9 0.137528 0 WH2XND DM33 43
0836 -26 -0.9 0.137528 0 WH2XND DM33 43
0840 -25 -0.8 0.137528 0 WH2XND DM33 43
0844 -25 -0.9 0.137528 0 WH2XND DM33 43
0848 -24 -0.9 0.137528 0 WH2XND DM33 43
0916 -26 -1.0 0.137528 0 WH2XND DM33 43
0920 -25 -0.9 0.137528 0 WH2XND DM33 43
0924 -26 -0.9 0.137528 0 WH2XND DM33 43
0928 -26 -0.9 0.137528 0 WH2XND DM33 43
0944 -27 -1.0 0.137528 0 WH2XND DM33 43
1000 -26 -0.9 0.137528 0 WH2XND DM33 43
1004 -25 -0.8 0.137528 0 WH2XND DM33 43
1008 -26 -0.9 0.137528 0 WH2XND DM33 43
1032 -25 -0.8 0.137528 0 WH2XND DM33 43
1036 -23 -1.0 0.137528 0 WH2XND DM33 43
1040 -23 -0.9 0.137528 0 WH2XND DM33 43
1044 -22 -0.9 0.137528 0 WH2XND DM33 43
1048 -23 -0.8 0.137528 0 WH2XND DM33 43
1052 -24 -0.8 0.137528 0 WH2XND DM33 43
1056 -22 -0.9 0.137528 0 WH2XND DM33 43
1104 -26 -0.9 0.137528 0 WH2XND DM33 43
73, J.B., VE3EAR
LowFER Beacon "EAR"
188.830 kHz. QRSS30
EN93dr
We're Back! -- For Now, Anyway
Posted by Webmaster on August 09, 2017 at 20:24:33.
Since late Monday afternoon, you've been seeing a misleading (and offensive to me, personally) message about "Account Suspended." Our hosting provider, spry.com, was unable to explain why, other than to say it was a "technical problem"--and it took very nearly 48 hours to find and fix whatever it was.
Given their track record of occasional extended outages over the past few years, I've begun setting up our site on another host, but because so much of lwca.org depends on CGI scripts to update content it's going to take a while to make sure all the scripts will work correctly on the new server. It's going to be a steep learning curve, at best, and I'm already beginning to find out that it may not work as planned.
I'll keep you posted on progress. At the very least, I hope to have lwca.net functional as a partial backup site soon.
John
Re: We're Back! -- For Now, Anyway
Posted by ed holland on August 10, 2017 at 17:46:21.
In reply to We're Back! -- For Now, Anyway posted by Webmaster on August 09, 2017
Thanks for the update John :)
NAVTEX
Posted by Frank Lotito on August 16, 2017 at 01:28:37.
ref: http://www.nws.noaa.gov/om/marine/navtex.htm
My question - What is the practical value of NAVTEX to the maritime community in this day and age? If I were a US or Canadian mariner, be it pleasure boat or commercial, and I was traversing the large inland water ways (e.g. Great Lakes) or coastal water ways, I would favor using weather and marine hazard broadcasts applicable to my immediate geographic area with high reliability, and available and up-to-date on a "24/7 basis."
What am I missing?
73 Frank Lotito K3DZ / WH2XHA
PVC back on
Posted by ed holland on August 16, 2017 at 18:19:41.
Hi Folks,
PVC suffered an un-noticed outage since the weekend after a power "dip". It was restored yesterday evening. Ident is still "PVC" at 7 sec intervals, 5 WPM.
I also cleaned up some connections in the feedline and retuned, so hopefully it is making the most of the milliwatts.
Regards,
Ed
PLM
Posted by Bill Hensel on August 16, 2017 at 20:47:20.
Copy to very slow ids at 2039 utc this is a first for me...
Where Art Thou?
Re: PLM
Posted by Bill Hensel on August 16, 2017 at 20:48:39.
In reply to PLM posted by Bill Hensel on August 16, 2017
meant to type TWO Ids
Re: PLM
Posted by John Davis on August 16, 2017 at 21:17:41.
In reply to PLM posted by Bill Hensel on August 16, 2017
Bill, you have my utmost gratitude for posting that report! Up to now, I'd been the only one hearing him (who or wherever he is), and began to doubt my sanity. Now if I'm crazy, that means there's two of us. :)
Re: PLM
Posted by Bill Hensel on August 17, 2017 at 00:58:32.
In reply to Re: PLM posted by John Davis on August 16, 2017
I'm certifiable and just listening to 22 mtr hifer band is proof.
There was some very slow fad ups and at times I thought I heard a long dash before the very very slow ID ...if the Id had been 10 wpm I bet it would have been easier to copy.
Re: NAVTEX
Posted by John Davis on August 17, 2017 at 05:49:20.
In reply to NAVTEX posted by Frank Lotito on August 16, 2017
I would favor using weather and marine hazard broadcasts applicable to my immediate geographic area with high reliability, and available and up-to-date on a "24/7 basis."
I'm sure most mariners would. However, the real question is not how such a thing would be delivered, but where it would come from in the first place.
1. Immediate geographical area. This is why NAVTEX broadcast areas are set at approximately 200 nautical miles. In the available time slot, they can presumably cover sea conditions and warnings for such an area in adequate detail.
Closer in to individual ports and harbors, the Coast Guard recommends NOAA Weather Radio for detailed local conditions and warnings that are not applicable out at sea. Maritime VHF is also useful.
And, farther than 200 nm from shore, there's really no such thing as "immediate geographical area," as we're about to see. For such large areas, forecasts are available by satellite, but those are really much more general in nature. Here's why:
2. High reliability. When you're on the high seas, you're pretty much on your own compared to anyone on land. The total number of volunteer observer ships and automated weather buoys reporting conditions on all the oceans of all the world is a little smaller than the number of comparable facilities just within the land area of the United States alone. This means the data available to forecasters is highly granular in geographical area and somewhat irregular in timing.
High seas forecasts are of necessity pretty general. Their reliability changed little between World Wars I and II, and thereafter plateaued again until the Sixties. In recent decades, satellite imagery, HF radar, and lightning detection networks have improved high seas observations significantly.
But they're still only applicable over rather broad areas...which is largely OK. There are no EF5 tornados at sea, and things like thunderstorms and fog are visible from shipboard visual or radar observation.
3. Up to date 24/7. You don't want to head into a hurricane or typhoon unawares, of course, but those don't pop up in minutes. They develop over days. Only icebergs and tsunamis are particularly timely phenomena at sea. The international ice patrol handles the former, and the AOR and POR satellites broadcast warnings of the latter on an as-needed basis. Other satellite-delivered weather can be (and often is) delivered as infrequently as four times a day, and still meets most vessels' needs because weather at sea for the most part doesn't change all that rapidly.
Along the coasts, NAVTEX delivers updates six times a day...more often than the Weather Service usually updates zonal forecasts on land, in fact. They print out automatically and thus the latest one is always available. And if you're even closer to shore where severe weather and fog can pop up more quickly, NOAA warnings on those are available real-time via Weather Radio and marine VHF.
Bottom line: practical value. Just as maritime practice calls for more than one navigation method aboard a ship, multiple sources of meteorological data have value too. Satellite and HF are available and fill the need on the open ocean. VHF is available close to shore. And MF (NAVTEX) provides excellent coverage of intermediate areas, at a much more moderate cost than satellites. A vessel engaged in coastal trade needs the latter two, while one that traverses the high seas may need all of the above.
John
Beacon "WV"
Posted by michael tyler on August 17, 2017 at 23:37:31.
I am beginning to get concerned that I have not received any reports for sometime. I checked everything twice in the last month....anybody hearing wv out there?? I can go to the airport that is about 8 air miles away and listen to it very well on the ham station there......:(
Re: Beacon "WV"
Posted by Bill Hensel on August 18, 2017 at 04:09:07.
In reply to Beacon "WV" posted by michael tyler on August 17, 2017
Does anyone listen for the hifer beacons?...I think with the solar flux so low people don't even try...but even in the low part of the cycle 13 mc does kick up a little dust now and then.
Re: Beacon "WV"
Posted by ed holland on August 18, 2017 at 15:10:31.
In reply to Re: Beacon "WV" posted by Bill Hensel on August 18, 2017
I try and listen, mostly at weekends, but it's hard to set a routine for it. It has been quiet of late. Not surprising given the season and Solar conditions.
Antenna work today
Posted by Bill Hensel on August 19, 2017 at 16:01:55.
PCO will be off the air beginning 1600 utc while I take the 3 section vertical down and inspect it as a typical fall project. Ill re-post today when PCO is back on the air.
Re: Antenna work today
Posted by Bill Hensel on August 19, 2017 at 18:06:06.
In reply to Antenna work today posted by Bill Hensel on August 19, 2017
PCO is back on the air as of 1800 utc
Net on weekend
Posted by Jerry Parker on August 20, 2017 at 02:54:53.
What time, day, frequency is the california lowfer net?
Thanks ahead of time
Sunday Hifers in ME
Posted by John, W1TAG on August 20, 2017 at 18:47:20.
Tuning around Hifer territory this afternoon for the first time in quite a while. The following were heard approximately where they should have been:
WM, MTI, NC, the SIW's, USC, PBJ and GNK. Listened for WV for quite a while, but heard/saw nothing.
Am planning to watch SIW WSPR during the eclipse period on Monday. Will also be monitoring WWVB.
John, W1TAG/1 Re: Sunday Hifers in ME
Raymond, ME
Posted by jim vm on August 21, 2017 at 00:00:07.
In reply to Sunday Hifers in ME posted by John, W1TAG on August 20, 2017
I will have hifer on this wkend and monday. ESA on 13.56593 Mhz aprox from CM99fb. NDB DXing Article
Posted by Bret Rehart on August 21, 2017 at 05:10:28.
Hello,
I see that this subject article is pulled down. When will it be available again?
Thanks.
Regards, SIW WSPR Eclipse Report
Bret
Posted by John, W1TAG on August 21, 2017 at 19:20:35.
I monitored SIW's WSPR signal on 13555.400 kHz through the eclipse period today from our Maine QTH. Garry's eclipse maximum was at 18:18 UTC, and mine was at 18:45 UTC. We are 1463 km apart. Data:
170821 1740 5 -16 -0.10 13.5554141 K3SIW EN52 7
170821 1744 4 -16 0.41 13.5554127 K3SIW EN52 7
170821 1748 5 -12 0.45 13.5554128 K3SIW EN52 7
170821 1752 4 -15 0.62 13.5554143 K3SIW EN52 7
170821 1756 4 -18 0.71 13.5554130 K3SIW EN52 7
170821 1800 4 -17 0.79 13.5554145 K3SIW EN52 7
170821 1804 4 -19 0.28 13.5554132 K3SIW EN52 7
170821 1808 3 -22 0.45 13.5554133 K3SIW EN52 7
170821 1812 2 -25 0.54 13.5554148 K3SIW EN52 7
170821 1816 2 -28 0.75 13.5554136 K3SIW EN52 7
170821 1852 4 -20 0.49 13.5554160 K3SIW EN52 7
170821 1856 5 -16 0.62 13.5554146 K3SIW EN52 7
170821 1900 5 -13 -0.32 13.5554161 K3SIW EN52 7
170821 1904 4 -16 0.37 13.5554147 K3SIW EN52 7
170821 1908 4 -17 0.32 13.5554163 K3SIW EN52 7
Note the loss of copy after 1816Z, and resumption at 1852. Given that Garry transmits a 50% duty cycle, the best I can say is that copy was lost during the time between his eclipse maximum and mine. Signal levels at 1812 and 1816Z were lower than the normal mid-teens I have been seeing in the daytime.
Interesting stuff!
John, W1TAG Re: NDB DXing Article
Posted by Webmaster on August 21, 2017 at 23:44:15.
In reply to NDB DXing Article posted by Bret Rehart on August 21, 2017
Sorry, but that series of articles is something of a sore point with us due to the magnitude of copyright infringement it suffered when first posted.
If we can find a way to make it available again yet keep it from being pirated so freely, then we will consider doing so.
John
[Revised 22Aug17]
Re: SIW WSPR Eclipse Report
Posted by John Davis on August 22, 2017 at 20:08:42.
In reply to SIW WSPR Eclipse Report posted by John, W1TAG on August 21, 2017
W1TAG wrote:
...the results on WWVB and SIW's Hifer signal were very consistent with what happens just after sunset. The Hifer thing was interesting, because I could see the other "watering hole" stations near 13555.400 on the WSPR waterfall screen. When the SIW signals fell apart, WM, NC and MTI were going strong. They got into trouble later as the "sunset" path moved along.
The HiFER signals at the watering hole were also interesting here in SE Kansas. It's good that solar flux has been in the high 80s lately, giving us more opportunity to see and hear a variety of stations on the band.
I'd hoped that the temporary twilight/sunset would open the path from Illinois, but it stayed stubbornly closed from a fairly typical early morning appearance until the usual late afternoon return. MTI, on the same side of totality as I was, seemed to remain unaffected, showing the same slow QSB cycle throughout as it did during the early morning and late evening. USC faded away before the eclipse was noticeable here and returned well after, except for 10 or 15 seconds of sudden increased strength shortly before maximum dimness.
The track of totality did pretty much as expected to the path from RY and NC to here. They faded out, in that order, just as totality was crossing the midpoint, and then returned in the same order. Shortly after, when the darkness reached Dex's QTH, there was a noticeable frequency rise on NC, presumably from the cooling caused by the eclipse.
Later in the day, well after eclipse effects were gone, I got a very good signal from PBJ on 13,557.500, plus a fairly good signal from GNK, and partial copy of FRC. During the eclipse and later I tried for PCO, but it was being stubborn again.
Just before sunset, I started seeing frequency spreading on EH, NC, and the SIW slant signal. It wasn't the obvious two or three signal multipath we've observed before, but a spreading of carrier over a 1 Hz wide swath...Mother Nature's spread spectrum. When it reached that point, SIW WSPR stopped decoding, even though it was still visible for a while longer. Found out a couple of hours later that we'd had an unexpected G2 storm. By the time it subsided, most everyone was apparently gone for the night.
John
Eclipse
Posted by ed holland on August 25, 2017 at 22:33:42.
Hi Folks,
While I failed to make any observations whatsoever using the radio, our trip to Oregon was rewarded with a terriffic view of totality. Attached is a crop from perhaps the luckiest "have a go" shot I have ever captured.
Best wishes
Ed
---------------------------------------------------------------
File Attachment 1: Diamond_Ring_Crop_2.jpg
Re: Eclipse
Superb shot, Ed! Even caught some nice prominences. Thanks for sharing.
Re: Eclipse
Posted by Bill Hensel on August 26, 2017 at 15:47:21.
In reply to Eclipse posted by ed holland on August 25, 2017
cool photo thanks, I did some LW listening for NDBs out of Wyo. nothing heard.
WV + PLM
Posted by John, W1TAG on August 27, 2017 at 18:29:48.
My Hifer checks in the last week have just turned up the regulars, as recently reported.
This afternoon (27 Aug), I tried again and was greeted with the heretofore unheard PLM on 13557.72 kHz. The signal consisted of a 5 second dash and the PLM ID in regular CW. A decent signal, here in Maine, with the expected QSB.
Also heard for the first time in a long while was WV in CW on 13555.800 kHz. That used to be a regular years ago, but recent searches have been fruitless.
Nothing else unusual heard. The regular NC and SIW signals were present, but weaker than usual.
John, W1TAG/1 Re: WV + PLM
FN43sv
Posted by John Davis on August 27, 2017 at 18:54:32.
In reply to WV + PLM posted by John, W1TAG on August 27, 2017
I tried again and was greeted with the heretofore unheard PLM on 13557.72 kHz.
Huzzah! Further proof that I wasn't hallucinating...about PLM, at least.
Glad to hear you're copying WV, too. That's a hopeful sign. I'll try to go out and listen this afternoon myself, if the lightning activity will move a little farther away than it currently is.
Re: WV + PLM
Posted by John Davis on August 28, 2017 at 00:59:02.
In reply to Re: WV + PLM posted by John Davis on August 27, 2017
To paraphrase Caesar, "I went, I saw, I heard."
Although SIW, WM, and PBJ stubbornly refused to come through at all, NC and EH were strong, USC was fair to good with fading, and MTI was frequently audible too.
With a bit of patience, I was finally able to see then hear WV by 4:17 PM CDT, after several months of absence. I had to listen for about 10 minutes to get some sense of the ID pattern this time, though, as there was QSB that recurred at the most inopportune times in almost every cycle for a while. As near as I can tell, though, it's currently five repetitions of "WV" then six dits, followed by one "WV" and five more dits.
At 4:28 PM, I tuned up to look for PLM and soon saw what appeared to be the dashes only, very faint. JA is correct that the frequency has dropped a few tens of Hz since I last copied it back in early June. After about three minutes, I started getting some good aural IDs.
Nobody was seen or heard above mid-band today, so I returned to the watering hole for about an hour to watch for signs of SIW and WM. No joy. Around 5:30 I repeated the band scan. This time, WV was still there, but PLM was only giving faint traces of the dash. There was a faint hint of FRC's carrier, but it was not audible.
With more slightly ominous clouds building, I packed up and returned to town about 6 o'clock. Not a bad day considering solar flux was only in the high 70s. No unusual space weather either, apparently.
John D Re: Net on weekend
Posted by John Davis on August 28, 2017 at 01:01:50.
In reply to Net on weekend posted by Jerry Parker on August 20, 2017
Sorry, Jerry, I've had feelers out for a week trying to find if anyone knows about the current status of the net, but so far nothing.
Re: WV + PLM
Posted by Bill Hensel on August 29, 2017 at 17:57:06.
In reply to WV + PLM posted by John, W1TAG on August 27, 2017
I confirm the long dash before the PLM ID,I failed to mention the long dash in my report but it was there.
Re: Net on weekend
Posted by Jerry Parker on August 31, 2017 at 14:32:16.
In reply to Re: Net on weekend posted by John Davis on August 28, 2017
Please join me on the LowFER Net Sunday on 3927khz
at 0800 pdt. See you there
potrzebie