Nice try Jim but Germany is way off the indicated heading from here – much the same as France up around 320 degrees short path, 140 degrees long path – definitely not about 70 degrees. It’s

Errr, not quite Gerald. France would be a completely different heading from here (roughly 340 degrees short path). Using old calls and exceptions confuses matters. TX5T is a current DXpedition

Gary I can confirm what you are seeing.I'll explain: Callsign lookup shows TX5T has a Germany address. There is an exception for Austral Isl. When the spot is received, it will show the proper

Gary, I tried your test using TX5C and TX5Z which are stations I have worked in the past. The log window shows them as follows: TX5C FO/C Clipperton 246 degrees TX5Z FO/A Austral 251 degrees The

Hi Aki. All the spots I have checked so far have been fine: the only ‘problem’ one is TX5T … which is what made me wonder about the way the program handles ambiguous prefixes. It would

Gary I can confirm what you are seeing.I'll explain: Callsign lookup shows TX5T has a Germany address. There is an exception for Austral Isl. When the spot is received, it will show the proper

sorry...I should say TX5T (not TX5C) 73 de aki ja1nlx ---In hamlogger@..., <ayoshida@...> wrote : Gary I do not see this while clicking some spots on DX spot window or BandMap. I always see same

Gary I do not see this while clicking some spots on DX spot window or BandMap. I always see same headings. Do you see this only when clicking TX5C ? or do you always see when clicking any DX spot

Friends, I’ve just ‘discovered’ that we can optionally display headings on spots on the band maps – handy for the bands on which we have beams. In the course of idly playing with the

Updating firmware did the trick logger 32 is now happy to talk to the 7700. Yhanks for all the help . 73 's Ron

Hello All, Please i need help, i try to auto-upload a QSO to Logger32 by a digitalmode program, all seems to be logged correctly except ADIF field that remain empty !!! Please if any possible

In Feb 2016 (yes last year) in msg number 68856 I asked for set up help on getting the CW machine to work post v3.50.0. I have been chasing this for the last year and have not made any progress.

Larry, You need to setup Logger32 to Automatically flag Imported QSOs for LOTW file export. See the setup process outlined in the Help file: “Tips, Tricks and Troubleshooting” Par

Aki, I did that a few times during the re-configuring without a fix. I walked away from the rig (shut everything down) for about 6 hours, fired it all up this morning and now is working normally

I am running logger version 3.50.309 on a Win 10 64 bit machine. Ijust finished the 160 meter phone contest and imported 495 Q’s as an .adi filefrom my Win-Test contest program. They all came into

When all else fails…re-boot. 73, Jim – w5ifp@... Sent: Sunday, February 26, 2017 4:12 AM To: hamlogger@... Subject: RE: [hamlogger] Preset RST Sent and Received not

Ken Try this for TEST. 1) Rename Logger32.ini to Logger32.old 2) Run Logger32 Yes Logger32 run with default settings. How you see RST fields now ? Is it normal or not ? 73 de aki ja1nlx ---In

Hmmm... Something fishy here. For some reason, earlier this week when I clicked in the bandmap (as I usually do) the callsign transferred to the Entry Window and the radio changed to the stn freq but

Jim, That's the problem. The default RST Sent and Received boxes are NOT being populated by the data in the band plan. Worked OK during the CW Worldwide contest last weekend and I've made no changes

Hi Guys It is magic. The QSL export is working again. I do not know what fixed it. Probably exiting and loading the program fixed it. Sorry Andy