A Few Contacts, but …

I did a bit of FT8 yesterday evening. I managed one contact on 80M and three on 15M. The other bands were sounding good, but I just couldn’t seem to connect. Not a real dense map either … nothing showing anywhere except North America, and one reception report in Venezuela.

I did have an equipment problem surface, though. My USB hub kept dropping out or resetting. Wiggling the USB-A connector at the laptop duplicated the problem. Over time, with connecting and disconnecting, the plug has gotten worn and is loose. At least, I hope it’s the plug and not the laptop socket that’s worn. I looked for a replacement cord, but the hub end is a USB-B connector … like you find on most printers … sort of a square plug, rather than a rectangular one. Ah well, Amazon Basics … should be here Friday. Love Amazon Prime! The old one is still usable … I just have to make sure I don’t wiggle the cord, though.

I’m looking forward to the loooong Thanksgiving holiday. Hopefully, conditions will improve a bit. I’ve been reading a bit about Olivia and want to give that a try. Maybe I’ll also have a chance to do some antenna experimenting, too. We’ll see.

Right now, I need to find a plumber. The kitchen sink decided to plug up on Thanksgiving eve, when the kitchen is a beehive of activity. Figures …

Have a great holiday if you’re celebrating it!

73 de Dick N4BC
November Four Big Cheese

 

There it is again …

I had that problem pop up again where my output power in WSJT-X dropped to 5 watts and I couldn’t increase it. I fiddled and fiddled with settings and turned knobs and fiddled some more to no avail. Still good power out with FLDIGI and on CW, etc. So, that seemed to be a good time to have dinner. I returned from dinner and lo and behold, everything was back to normal. Windows 10 had just finished its big Fall update earlier in the day, so maybe that had something to do with it? Still an unknown …

I made a few FT-8 contacts on 80 meters, and a few more on 40 and 30, but 20, which is usually pretty good, just wasn’t cooperating with me last night. I tried calling CQ on JT-9 on several bands without any luck. Although I like the speed of FT-8, I like the sensitivity of JT-9 better. It can really pull the signals out of the mud.

Saturday I’m going to the QCWA Chapter 119 luncheon. Twice a year, it’s on my side of Hampton Roads (Newport News vs Virginia Beach). It’s the only time I get to see some of these guys. I’m not sure what the program is about, but it’s usually pretty interesting.

There’s a real chill in the air, now. Fall is officially and truly here. The past couple of mornings, it’s been in the 40’s when I leave for work at 5:30 AM. Used the heat in the house for the first time this season just the other night. Yep … Winter is coming!

73 de Dick N4BC

WSJT-X 1.8.0 rc2

The latest release┬ácandidate of the WSJT-X software incorporating FT-8 mode has been released (rc2), and it seems to have cured my power output problem. I worked several stations on 20, 17, and 15 meters this afternoon and everything looks ok — JT65, JT9, and FT8 all worked great.

The bands seem OK today … much better than the recent past. Hopefully I’ll be able to get on later this evening to see who’s about. It’s a dreary day outside with thunderstorms in the forecast so that might put a damper on later operations but hey … that’s ham radio, isn’t it?

73 de Dick N4BC

Issues with WSJT-X 1.8.0 rc1

Well, everything was going along well … no problems … just great! When I booted up the computer the next day, max power out had decreased from 20 watts to 5 watts. Can’t get it above that. I didn’t change anything, and I can’t find anything in the computer that’s changed … audio levels the same, right source for the audio … everything the same. No changes to the Signalink USB or the radio settings. Just can’t figure it out. All the computer settings are the same for PSK-31 with FLDigi and power out there is the same as it always has been.

Well, I have enough to keep me busy with other modes, so I’ll just wait until the final version is released and see if it gets fixed. Just odd that it did that all of a sudden.

73 de Dick N4BC