Keyboard Shortcuts
Likes
Search
BITX QSO Night, Sunday, May 7, 9pm Local Time, 7.179 MHz
BITX QSO Night, Sunday, May 7, 9pm Local Time, 7.179 MHz |
I think this is a great idea, and I intend to give it a try now and then. But being a QRP activity, we might want to reach for the maximum advantage. Selecting a time near dusk in every time zone would add Greyline enhancement to the activity. My suggestion would be to try calling at local sundown, what ever the season might be. That 9 PM time will be good later this spring, but where I am located dusk is about 7:30 PM (CDT) right now. Speaking as a JT Op with WAS on several bands, when I picked up Alaska and Hawaii on 80-20m was just as the terminator crossed the stations at those locations (usually in November or December). Thats also when I got JA, VK, and ZL. |
I agree that we should try to use the best time for propagation.? However noise levels and propagation vary so much, the best strategy for QRP is always going to be jump in when conditions are good. Let's see if the QSO night becomes popular, if so, we might add local sunset to the schedule. Are the best conditions just after sunset?? From watching my WSPR beacon, I was spotted by stations to the east before dark, then later in the evening had long distance spots to the west. |
Well, I had my first "real" QSO with my bitx40 tonight. By "real" I mean that I called CQ and got a reply! Thanks to KK6QCV, Brad, who replied to my 7 watt call. The band was up and down, but we ended up having a very nice 10 minute QSO, and he reported that my bitx40 had very nice audio. Definitely worth the assembly effort and the Arduino hacking to use the rotary encoder! I was on 7.192 MHz. Carson City, NV to Riverside, CA on 7 watts. Not bad..
|
Congratulations Dave!? 73? Bill N2CQR On Thursday, May 4, 2017 12:18 AM, davetelling . <davetelling@...> wrote: Well, I had my first "real" QSO with my bitx40 tonight. By "real" I mean that I called CQ and got a reply! Thanks to KK6QCV, Brad, who replied to my 7 watt call. The band was up and down, but we ended up having a very nice 10 minute QSO, and he reported that my bitx40 had very nice audio. Definitely worth the assembly effort and the Arduino hacking to use the rotary encoder! I was on 7.192 MHz. Carson City, NV to Riverside, CA on 7 watts. Not bad..
|
The QSO parties did not overload the bands with signals this evening, so hopefully there will be no interference tomorrow night.? I was able to make a few contacts MI to MA, CT and IN.? I had to fight my way in through minor pileups to get the QSO's so I am proud of them.? I think they get extra points for QRP QSO's, so I made sure to report QRP. I put up a 270 foot delta loop on my workshop radio a few days ago, and it seems to be working. Looking forward to tomorrow's QSO night. |
I will be listening/ calling from RI. Worked west coast with excption of AZ and NV last night with the BitX40 running 7 watts with battery pwr. Have worked 16 DX countries in last week with inverted V at 50 feet. This thing is amazing. There is something that sounds like over horizon radar hr in RI from 7.185 to 7.2 MHz. Willy W1LY On Sun, May 7, 2017 at 7:44 PM, KC8WBK via Groups.Io <cruisenewsnet@...> wrote: Yes, and you may wish to try at 7pm and 8pm as well to get the neighboring time zones. |
Petry, Kevin
¿ªÔÆÌåÓýConditions not bad in Cleveland, a few contacts made in the NEQP
Kevin
This email is intended only for the use of the party to which it is addressed and may contain information that is privileged, confidential, or protected by law. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of the email or its contents is strictly prohibited. If you have received this message in error, please notify us immediately, by replying to the message and deleting it from your computer. WARNING: Internet communications are not assured to be secure or clear of inaccuracies as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this email, or any attachment, that have arisen as a result of e-mail transmission. |