The shorthand notation is only supported for a received exchange. You are correct that the exchanges input by the countyline prompt is tested for valid county abbreviations and you can not use

Oh My ! This is fun and will lead to some new cutting edge stuff of course not everyone will be happy with the new ways some of us find to have fun But the expansion of our style of operating will

Steve, >apologies for me having confused the two Ah... the confusion has just begun, and you are not the only beneficiary. ;-) After posting my definition, my what-I-thought-were clear-cut

I set up for 7QP this morning, set STATION to ROVER, entered COUNTYLINE in the call sign field of the DI window, and entered the county abbreviations preceded by WY as they were invalid without the WY

Larry Thank you for setting me straight apologies for me having confused the two as they are Two different distinct Operating Categories Multi Distributed being everyone operates at their own QTH but

Yes, a couple of folks pointed that out to me via private emails. I have an inquiry in with the ARRL contest branch (so far, no response) asking specifically if rule 3.7 applies to FD, since the ARRL

I get the same message "com 4 is not functioning" but in the device manager there is nothing using com port 4...microham microkeyer2 is under serial bus or something like that

gm Gordon Thanks for that explanation. As clarification of my "remote station" description, the logging software is also local with the contest operator, but the station hardware (radio, keyer, mic,

Is your computer setup to show all file extensions, if not do so, then browse to your Users\yourusername\(My )Documents\N1MM Logger+\UserDefinedContests folder and check that .txt has not been added

Larry,     I have not used this configuration previously. I am using OpenVPN for both server and client.  The server runs on a linux system at the remote site. Each client is running the openvpn

Thanks John, You nailed the problem - both the cause and the solution. Thanks, Norm W4QN -- Norm W4QN

Thanks, Rich - it was the explicit selection that tripped me up. 73, Pete N4ZRCheck out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide.

That's what I thought Steve. Device Mangler thinks all is well. This is a new thing. I don't remote to W7RN often so it just showed up when I was getting ready for 7QP. I'm fairly

You won't like this answer, either.... It means N1MM+ got a System.IO.IOException when we asked Microsoft to open the serial port. According to the MS documentation, it occurs when the serial port

Can someone tell me what this error notice really means? COM14 is one of the 4 RRC1258 virtual ports, it is RRC COM1 and handles the CAT connection to the remote K3. The notice comes

Gordon, See my reply in this thread to KG5VK. Do I understand your architecture correctly? Had this configuration been running previously? What remote software are you using? Which VPN client? Are

Just to clarify: The new feature in N1MM+, and the Zoom teleconference this week described Distributed Multi-Op (DMO) contesting over a Virtual Private Network (VPN). In DMO each ham - in his/her own

That message is generated by the Microsoft serial port handler that N1MM+ uses. What does Device Manager think of COM14 ? 73, Steve, N2IC

Make sure you know the easy way to log the county line stations and the county line stations that send a shorthand exchange.

Rory, Are you looking at the pulldown that says: “State for Log Type QSO PARTY”? It’s there. 73, Ted W4NZ