NJDTechnologies

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

Current Operating Frequency and Mode

OFF AIR; Storms expected overnight into Saturday morning. Planned start time for WG2XIQ in Field Day demo is 1800z on 474.5 kHz CW, WX permitting

Session seemed down as geomagnetic field calmed below storm levels

– Posted in: 630 Meter Daily Reports, 630 Meters

Don’t get me wrong – it was NOT a poor night in my honest opinion, although it probably should have and could have been a lot worse given the recent G2 and G3 storms we have experienced.  Many comfortable CW-level reports were observed and there were several trans-Pacific reports but as Roger, VK4YB, characterized it, the band was much more subdued than what we have seen recently.  I suspect this is the result of increased absorption.  All of the bands seem to be experiencing it in one capacity or another.   630-meters was quiet for much of the night but  elevated noise levels were observed as sunrise approached likely due to lightning rich storms in the Midwest, Pacific coast and Caribbean.  Being the optimist when it comes to this radio stuff, I guess I will take it.  What choice do I have anyway?

lightning-101616

North American overnight lightning summary

 

Geomagnetic conditions are “odd” as the Kp is elevated but generally quiet, the Bz is pointing to the North and solar wind velocities are high, averaging 650 km/s at the moment.  DST values are better than they were but continue to suggest periods of disturbed conditions:

planetary-k-index-101616

 

kyoto-dst-101616

 

australia-101616

 

Doug, K4LY / WH2XZO, called this one, “Fairly noisy and disturbed conditions last night with just 3 decodes by WH2XCR and one by VE7SL.. Just 7 heard by and 29 who heard XZO.”

Ken, K5DNL / WG2XXM, reports that he was decoded by 49 unique stations in 12-hours including VK4YB,VK2XGJ and WH2XCR.  He also reported 92 decodes from VE4XC, best at +3 dB S/N.

wg2xxm-vk2xgj-101616

WG2XXM, as reported by VK2XGJ

 

wg2xxm-vk4yb-101616

WG2XXM, as reported by VK4YB

 

Roger, VK4YB, issued a “code-4 ” this morning and reported that while storms in New South Wales were not impacting his hearing during this session, he expected  band conditions to deteriorate in the next session.  Roger’s statistics and details follow:

“Rx 16*wg2xxm (-19) 34*wh2xxp (-13) 2*ve7bdq (-26) 37*wh2xcr (-14)

Tx 4*ve7bdq (-27) 5*ve7sl (-25) 2*kl7l (-29) 2*we2xpq (-28) 32*wh2xcr (-5) 22*jh1imn (-20) 3*jn1mso (-27) 1*jh3xcu (-26) 9*ja3tvf (-22)”

ve7bdq-vk4yb-101616

VE7BDQ, as reported by VK4YB

 

vk4yb-ve7bdq-101616

VK4YB, as reported by VE7BDQ

 

vk4yb-jn1mso-101616

VK4YB, as reported by JN1MSO

 

vk4yb-jh3xcu-101616

VK4YB, as reported by JH3XCU

 

vk4yb-jh1inm-101616

VK4YB, as reported by JH1INM

 

vk4yb-ja3tvf-101616

VK4YB, as reported by JH3TVF

 

Steve, VE7SL, suspected that it was noisy in British Columbia this morning but did provide Roger five WSPR decode this morning:

vk4yb-ve7sl-101616

VK4YB, as reported by VE7SL

 

Ward, WH2XXP, received reports from 51 unique stations, including four VK’s and one JA:

wh2xxp-101616

WH2XXP session WSPR activity (courtesy NI7J)

 

wh2xxp-vk5abn-101616

WH2XXP, as reported by VK5ABN

 

wh2xxp-vk4yb-101616

WH2XXP, as reported by VK4YB

 

wh2xxp-vk2xgj-101616

WH2XXP, as reported by VK2XGJ

 

wh2xxp-vk2ddi-101616

WH2XXP, as reported by VK2DDI

 

wh2xxp-jn1mso-101616

WH2XXP, as reported by JN1MSO

 

Phil, VK3ELV, received multiple reports from JA stations late in the previous session:

vk3elv-7l1rll4-101616

VK3ELV, as reported by 7L1RLL4

 

vk3elv-jh1inm-101616

VK3ELV, as reported by JH1INM

 

vk3elv-jh3xcu-101616

VK3ELV, as reported by JH3XCU

 

vk3elv-jn1mso-101616

VK3ELV, as reported by JN1MSO

 

Rick, W7RNB / WI2XJQ, reports that they made it through the night of wind and rain, with gusts up to 60 mph.  Rick has the loop “lowered” but still managed a number of reports during the session:

wi2xjq-101616

 

Neil, W0YSE/7 / WG2XSV, configured his station a little differently overnight.  He explains:

“GM John. I did something different this session to accommodate Steve/VE7SL. I set my dial to 473.5 kHz so that Steve might see his CW on my wsjtx screen at the +500hz mark (=474.0). I also adjusted my WSPR settings so that the wspr stations would be decoded around the +2200hz. All that worked fine and I got a ton of wspr decodes from the following: XXP, XXM, XCR, XIQ,  and BDQ. However NONE of them show up on the wsprnet data base this morning.

I also decoded your JT9 on my wsjtx screen in the 08z hour. Your “Freq” appears at 1958 & 1959 because of the 700 hz difference in our two dial frequencies.

The worst part of the storms have passed now so I will probably be back on my vertical later today and normal TX/RX operations.”

wg2xsv-101616

WG2XSV JT9 console showing my JT9 calls over night

 

Tomas, EA2BCJ, reported in the ON4KST chat/logger at 1839z that he would be operating 477 OPERA.

I woke up around 0640z because the receiver next to my bed that I use to monitor my WSPR signal while sleeping (I really do listen with one ear as I sleep – it helps to be a light sleeper) indicated that my signal was cutting out, which is a seasonal thermal problem that results in a design flaw in the Yaesu driver.  I have a number of techniques to correct the problem, not the least of which simply involves turning the rig off.  Long story short, the problem stabilized after a while without having to open up the rig and reseat jumpers.  I suspect I will have to do that once the temperature stabilizes to those typical for the Fall, however.  I stayed up for the remainder of the night, calling CQ on JT9 on a few occasions, tuning other bands at the HF position and finally beginning the morning 630-meter CW session around 1000z.  Eric, NO3M / WG2XJM, reported my signal at RST 559 about 45-minutes prior to sunrise in western Pennsylvania.  He added that he could not return my call as he has a PTT problem with his transverter that he has not repaired yet.  My WSPR transmission reports can be viewed here and my WSPR reception reports can be viewed here.  I did not remember to collect early evening data before bed time in spite of making a note, so my transmission reports prior to 0400z are missing.

wg2xiq-kh6-zf1-101616

WG2XIQ 24-hour WSPR activity

 

There was a lot of band activity once again.  At one point mid-evening in North America I observed 93 MF WSPR stations on the WSPRnet activity page.  I could not find N2BJW in my list of receive stations so he must be new to 630-meters.  Welcome aboard!

Regional and continental WSPR breakdowns follow:

na-101616

North American 24-hour WSPR activity

 

eu-101616

European 24-hour WSPR activity

 

ar-101616

Central / Asiatic Russian 24-hour WSPR activity

 

as-101616

Asian 24-hour WSPR activity

 

oc-101616

Australian and New Zealand 24-hour WSPR activity

 

There were no reports from the trans-Atlantic path.

It was pretty much standard fare for Eden, ZF1EJ, as he decoded many of us in the southern US:

zf1ej-101616

ZF1EJ 24-hour WSPR activity

 

Laurence, KL7L / WE2XPQ, reports that he was receive-only through this session as winds continue to gust at 55 mph:

we2xpq-101616

WE2XPQ 24-hour WSPR activity

 

vk4yb-we2xpq-101616

VK4YB, as reported by WE2XPQ

 

wh2xcr-we2xpq-101616a

wh2xcr-we2xpq-101616b

WH2XCR, as reported by WE2XPQ

 

kl7l-101616

KL7L 24-hour WSPR activity

 

vk4yb-kl7l-101616

VK4YB, as reported by KL7L

 

wh2xcr-kl7l-101616a

wh2xcr-kl7l-101616b

WH2XCR, as reported by KL7L

 

Merv, K9FD/KH6 / WH2XCR, continues to receive reports from Japan, Australia, Alaska and the lower mainland of North America but reports were down a bit from the previous session but still very good.  Note the large number of spots from VK4YB and VK2XGJ:

wh2xcr-101616

WH2XCR 24-hour WSPR activity

 

vk3elv-wh2xcr-101616

VK3ELV, as reported by WH2XCR

 

vk4yb-wh2xcr-101616

VK4YB, as reported by WH2XCR

 

wh2xcr-jh3xcu-101616

WH2XCR, as reported by JH3XCU

 

wh2xcr-vk2xgj-101616

WH2XCR, as reported by VK2XGJ

 

wh2xcr-vk3elv-101616

WH2XCR, as reported by VK3ELV

 

wh2xcr-vk4yb-101616

WH2XCR, as reported by VK4YB

 

wh2xcr-vk5abn-101616

WH2XCR, as reported by VK5ABN

 

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