NJDTechnologies

Radio: it's not just a hobby, it's a way of life

Current Operating Frequency and Mode

OFF AIR but will be QRV on CW somewhere between 472.5 kHz and 475 kHz after dark

SCHEDULED ACTIVITY: CQ 474.5 kHz CW by 1030z through sunrise most days, WX permitting

How was the band last night? Depends on who you ask; ZR6AIC listening from South Africa; WSPRnet down again for the entire session (Its back up as I compile this report)

– Posted in: 630 Meter Daily Reports, 630 Meters

Very quiet geomagnetic conditions, a North-pointing Bz and solar wind velocities near 300 km/s suggest that the band should have been pretty good if enough spark existed for openings to develop.  That’s been a problem on 630-meters in the past – quiet conditions that didn’t produce.  Roger, VK4YB, reported that his 630-meter noise floor was a very quiet -82 dBm but there was no trace of WH2XCR in KH6 as of 1200z.  On 160-meters this morning, propagation to and from Australia and the Pacific was very good.  Clearly as much as these bands seem similar, they are very different.

planetary-k-index 081616

 

Kyoto DST 081616

 

Australia 081616

 

The fly in the ointment for this session is that WSPRnet was inoperative again so band performance has largely been based on individual operator reports.  While we have HamWSPR at our disposal I have been hesitant to mention it as an alternative because a number of stations became “stuck” in the IP redirect last time we had a WSPRnet outage.  It’s otherwise a good alternative as long as you understand how to redirect your machine and restore it later.  Check the ON4KST chat/logger for details on modifying the HOST file and the redirect IP address if you would like to port your data through this alternate system.

NA 081616

HAMWSPR rendering of partial North American 24-hour activity

 

My perception was that the band was pretty good overnight.  I know I decoded WD2XSH/15 very early, in addition to WH2XGP and WH2XZO.  I was certain that I also decoded WG2XXM but I did not write him down on my list and Ken is only 200 miles away so it would be a problem if I did not decode him.  Decoded stations were all at JT9 levels and WD2XSH/15 also achieved CW levels.

It was my intention to wake up and operate JT9 for a bit at 0600z but I set the alarm for the wrong time and woke up an hour late.  Neil was decoding my WSPR signal as he waited for me to operate JT9 so it was plausible that we would have made it.  I worked KH6AT on 160-CW before heading back to bed.  At 1000z I returned to 630-meters and called CQ on JT9 hoping to catch WI2XFI but approaching rain meant increasing noise level and I suspect he had local storms to contend with.  At 1030z, I called CQ on 474.5 kHz CW but no QSO’s occurred.  QRN was really much higher by the time that I stopped calling CQ.

Larry, W7IUV / WH2XGP, reports that he “heard 5 last night, XCR, XJQ, XSV, 26XSH, and XIQ. Didn’t seem like good condx at all.”

Eden, ZF1EJ, reports that he decoded me overnight.

Neil, W0YSE/7 / WG2XSV, reports “…here is what I gleaned from HamWspr this morning… I heard XJQ, XGP, XCR, AND XIQ.  but I do not know who might have heard me.”

Rick, W7RNB / WI2XJQ, provided the following statistics from his station:

“Heard by —
2016-08-16 13:56  WI2XJQ  0.475745  -3  4  CN87ts  5  VE7CNF  CN89ng  171  348
2016-08-16 07:20  WI2XJQ  0.475754  -27  3  CN87ts  5  WE2XPQ  BP51ip  2287  322
2016-08-16 06:46  WI2XJQ  0.475753  -23  3  CN87ts  5  KL7L  BP51ip  2287  322
2016-08-15 15:12  WH2XGP  0.475688  -6  0  DN07dg  5  WI2XJQ  CN87ts  208  286
2016-08-15 15:06  WI2XJQ  0.475739  +10  0  CN87ts  5  VE7BDQ  CN89la  147  341
2016-08-15 15:06  WI2XJQ  0.475742  -21  1  CN87ts  5  WG2XSV  CN85rq  232  183

2016-08-15 15:06  WI2XJQ  0.475743  -12  0  CN87ts  5  WH2XGP  DN07dg  208  105

Heard — WG2XSV, WH2XGP, WH2XCR”

Ken, SWL-EN61, from Indiana provided these details:

“Well, the “weather guessers” got it wrong again last night. No T-Storms as predicted, but as you know, you ALWAYS have to err on the side of caution and take the outside antenna connections apart. You won’t sleep well knowing things are connected with lightning around.

So, as stated, I ran the rx station with the directional antenna generally pointed towards you and /15. That also gave VE3CIQ’s signal opportunity somewhat off the other side of the antenna pattern.
I was pleasantly surprised this morning to see that not only did CIQ do well overnight, but that I also had my first decode from VE3EFF.

I was also surprised to find that I had (any) 2 decodes from XGP, who was pretty much in the null of the antenna.

Btw, the antenna used last night was a small hula hoop on a camera tripod in the same room as the rx gear.
XIQ did well with a couple -9 db spots.

That’s it from your Indiana outpost station.  :-)”
In Australia, Edgar, EJTSWL, operating portable from NSW posted the following reports of VK4YB on the VK 600m email reflector:
0922 -9 -1.1 0.475628 0 VK4YB QG62 37 1204
0928 -9 -0.4 0.475629 -1 VK4YB QG62 37 1204
0938 -5 -0.3 0.475625 0 VK4YB QG62 37 1204
0946 -6 -0.4 0.475625 0 VK4YB QG62 37 1204

 Steph, VK5FQ, posted these reports for VK4YB:

0914 -21 0.0 0.475625 0 VK4YB QG62 37
0922 -23 0.1 0.475625 0 VK4YB QG62 37
0928 -20 0.2 0.475625 0 VK4YB QG62 37
0938 -15 0.1 0.475625 0 VK4YB QG62 37
0946 -12 0.0 0.475625 0 VK4YB QG62 37
0954 -12 0.1 0.475625 0 VK4YB QG62 37
1010 -14 0.1 0.475626 0 VK4YB QG62 37

John, VK3XGJ, was monitoring JT9 and printed VK3HP.

WSPRnet appears to be working for the moment, albeit very slowly.  What follows are the data that have been processed by 1545z.  These renderings are incomplete and we are just going to have to accept that for this session.  Whether I include line item details of decodes as I normally would for select DX paths that follow depends mostly on my ability to access the data.  If it takes 20-minutes or even 5 minutes to display a data table, I will exclude those reports from today’s summary.  I hate to lose data but this session is already compromised.

Incomplete regional and continental breakdowns follow:

NA 081616

North American 24-hour WSPR activity (Incomplete)

 

EU 081616

European 24-hour WSPR activity (Incomplete)

 

AF 081616

African 24-hour WSPR activity (Incomplete)

 

JA 081616

Japanese 24-hour WSPR activity (Incomplete)

 

VK 081616

Australian and Tasmanian 24-hour WSPR activity (Incomplete)

 

There were no known reports from the trans-Atlantic or trans-Equatorial path.  ZR1AIC was present for the first time as a WSPR receiving station on 630-meters but no known reports have been filed at this time.  I wish him lots of success in the coming season on the path to Europe.  VA3ROM/P was also present once again on a night of WSPRnet difficulties.  Its unclear at this time whether he has decoded stations since he began listening.

Laurence, KL7L / WE2XPQ, reported to the ON4KST chat / logger that “…XGP into positive integers (yay!) – XPQ high probe, KL7L will be probe on dock by lake at 5.5m”:

WE2XPQ 081616

WE2XPQ 24-hour WSPR activity

 

KL7L 081616

KL7L 24-hour WSPR activity

 

Merv, K9FD/KH6 / WH2XCR, appears to have finally made it to VK4YB in addition to VK2XGJ for this session:

WH2XCR 081616a

WH2XCR 24-hour WSPR activity (Incomplete)

 

Jim, W5EST, presents “VIEWPOINT: 630 METER TRANSMIT ANTENNA AND TOP HAT”:

“Please click on these blog links for last January’s two-part antenna article:

Part I:  http://njdtechnologies.net/gulf-storms-lead-to-a-noisy-night-in-north-america-two-trans-atlantic-stations-reported-vo1na-qrss10/

Part II: http://njdtechnologies.net/pretty-good-band-conditions-and-strong-participation-in-north-america-wh2xqc-and-wg2xpj-return-to-operation-wh2xcr-path-to-zf1ej-vk2xgj-returns-but-ja-path-disappears/

Developing experience—yours and mine—can cause us to read the same material with different “eyes.”  If you’ve already seen this blog’s two-part series from last Jan. 15-16, what do you think now? And if you weren’t reading this blog back then, welcome to the group! May you find the article interesting.  TU & GL this new 630m season!”

 

Additions, corrections, clarifications, etc? Send me a message on the Contact page or directly to KB5NJD gmail dot (com).