I was right about the Win4Icom/N1MM+/WinKeyer USB problem … it was a port conflict. I had Win4Icom and N1MM+ both pointing to the same serial port for the WinKeyer. The simplest solution was to temporarily disconnect the connection from Win4Icom to the WinKeyer, and now N1MM+ works fine. If I’m not using N1MM+, I can just toggle the port back on in Win4Icom and all is well again … easy peasy!
I rushed home from choir practice and caught the last half of the Tidewater VA DMR Net (TG31515). It was a small group tonight and Darrell, KF4HJW was doing the honors as Net Control. Don’t know where Howard was … hopefully he’ll be back next week.
I downloaded the latest version of JS8Call this evening … JS8Call v0.7.5-devel. The main update is a fix for some decode issues, and there are several other fixes as well. Jordan, KN4CRD, is really responsive to feedback and the groups.io site is a good way to provide that interaction.
73 for now de Dick N4BC
Michael has come and gone now, and it was nowhere as bad as it could have been here at my QTH in Tidewater, VA. There were tornadoes and heavy rains all around us … to the South, West, and North … but most of the really nasty stuff was to the North of us. At the house, it was mostly high winds, rain, overturned trash cans, and lots of silver maple branches in the front yard. Many people are without power, but my power never failed. I did lose internet for about a half hour. When I look at the videos of the storm hitting the Florida panhandle, it’s sobering to see what Mother Nature can dish out.
Of course, the internet dropout was in the middle of the weekly Tidewater DMR Net on TG 31515, so my hotspot became a nice paperweight with a pretty blinky red led. Before I lost my link, we had nine check-ins, and several regulars were absent, no doubt because of the storm. So, better luck next week!
After the Net went away for me, I went ahead and got the DXLab Suite working with Win4Icom. Simple, really … just set up the virtual ports to interface with DXCommander and all worked well. I’m using two monitors and if I don’t judiciously manage what applications I’ve got open, I find I’m running out of room on the monitor desktops. You have to be creative in closing or minimizing and resizing windows on the monitors to keep things from piling up on top of each other.
Today, things are getting back to normal. Michael is heading out to sea, and I’m at work, looking forward to the weekend (as I always do!). We still have generators running at our tower sites that are without power. My daughter, who is doing her practice teaching for her teaching certification/licence, has the day off, since schools are closed today (again!) due to trees down, minor flooding, and power outages.
73 de Dick N4BC
Last night was a failure for the Tidewater DMR Net. Not that it was our fault … I think I can lay this one right on the doorstep of the network. There were lots of network dropouts, weird noises, and just general failure. I never did get checked in and all of the stations I heard intermittently were having trouble communicating. This brought home … in an obvious way … that in a disaster, like a hurricane and the resulting flooding, those of us dependent on hotspots and the internet for DMR operation would literally be “up the creek without a paddle.” There’s still a real need for that good ol’ RF!
73 de Dick N4BC
Once again, we met last night for our weekly net. It was a good-sized group, and we had quite a bit of discussion on several topics. We talked about choosing a hotspot frequency … what to avoid, such as national, regional, or local active simplex frequencies, weak signal frequencies, repeater input/output frequencies, satellite uplink/downlink frequencies … and probably some I’ve forgotten. The moral of the story is “don’t use a frequency that somebody else is using.”
We also discussed setting up an groups.io discussion group to keep everybody informed about what’s going on locally. We got a bit of a history lesson on how the 31515 TG came about … who set it up, why it was set up, etc. It was suggested that some of the net members visit local clubs and explain about the weekly nets to increase participation. We already have a few new people checking in most weeks, but the more the merrier!
Finally, we had a check in from Guam! It was an active duty Navy member with ties to this area checking in from KH2-land with his handheld and hotspot. Perfect copy … what a great mode for these propagation doldrums we’re experiencing. He gave us a few details of the recent Typhoon that hit Guam.
We meet Thursday nights at 9 PM Local (Eastern) time on TG 31515. Join us!
73 de Dick N4BC
Last night, we had our monthly radio club meeting. We had a good turnout, with some old friends we hadn’t seen for a while, and some new ones. We even picked up a few new members … HOORAY!
Our Treasurer, who has held that position for over fifteen years tendered his resignation as treasurer due to health and family issues, and I was elected to take his place. I’ve really got some big shoes to fill, don’t I?
We had a good meeting, and the presentation was on mobile radio installation. Well done and very interesting. It’s my turn next month, and my tentative subject will be portable operation … Radios in the Wild.
There were ten checkins to the Tidewater 31515 DMR Net this evening. Topics of discussion were the upcoming Virginia Beach Hamfest and IDing on DMR to comply with FCC Regulations … Section 97.119, to be specific. As I’ve said before, it’s more of a casual gathering than a formal net, and it’ll be nice to put some faces to the calls at the hamfest Saturday. I noticed that a couple of new calls showed up as unknown, so I updated the user database in my MD-380. I hadn’t done that for a while.
I also went into my new DStar radio and added some local non-digital simplex channels. The programming in that radio is still a work in progress, but truthfully, with the GPS and built-in repeater database, not much pre-programming is needed for repeater use.
73 de Dick N4BC