Hi folks, i just updated to version 4 and everything seems to working smoothly. I am a logger32 user for over 16 years and I am impressed by all the hard work that the logger32-team is putting into

Hi Bob These tests and checks have got me liking JTDX! Extra L32 features over WSJT-X, I could be a late adopter… Opened the manual calling event viewer and when I click a callsign in the

Chris, if I understand you correctly, when you look at the Cluster/Localhost window there are many spots. But only 25% of those appear to be making it to the DX Spot window. If I am

You need to set the DX Spot Blocking/Pass Filters to determine which spots migrate to you DX SPOTS Window. The filters will determine a lot of things about which spots you want to come to the DX

Ok, I have something similar bob but I thought on the enhancement for those who don't spend time trying to know how to confirm a qso, there are a lot of hams don't doing that...... Bit anyway thanks a

I am using the latest version of VE7CC and Logger32 v4.0.235. The issue I have is that only a percentage of the spots are feeding into Logger 32 when I compare the Logger 32 cluster window to the

John, you said: I have to start L32, then check "allow WSJT-X to.....", then start WSJT-X, use it for a while, then stop WSJT-X, then uncheck "allow WSJT-X to.....". I don't think

Ignore previous message. I have it fingered out now. I have to start L32, then check "allow WSJT-X to.....", then start WSJT-X, use it for a while, then stop WSJT-X, then uncheck "allow WSJT-X

Thanks Fonsi. 73.

The following files have been uploaded to the Files area of the hamlogger@groups.io group. /Secondary Admin data files/DVGE.csv By: ec7akv@... Description: Secondary Admin

Rick, you are correct satellite QSOs and the requirements for electronic confirmation are a pain in the ass. I understand you request (no problems with your English). It is not

Hello I know that satellites world is a little complicated for adif and specially Lotw. I have noticed that some users do not fill correclty the fields necesary to confirm a qso via Lotw or Eqsl ,

Just post your ideas here (everyone else does). SeventyThree(s).

Hello All I don't know if it is the right way to ask for an improvement or enhancement. Do I post here or is there any oter way ??? Thnaks in adv. 73 de Rick EA4M Libre de virus.

Bob Thank you for implementing that small enhancement for me it will save a lot of coping and pasting. 73 Malcolm GU0UVH

... I still can't find any problem. When you click on a callsign in the UDP BandMap, you see a box appear around the cell you clicked on. Do you see text appear in the Manual calling event viewer like

Further to my last msg Bob, if I click on a callsign - as I said the locator goes into the log entry box and the mouse clcik moves the cursor into the Call box in the log entry window and lights it up

Hi Bob I was meaning the UDP Band Map WSJT-X window. It looks like only me and one other guy has the problem – only the locator (if there is one sent) transfers to the log entry window but not

In the Logsync setup there is a place for Loger32’s path. Have you updated that path to point to the new version of Logger32? At the top of Logsync does the caption show {L32}?? If not Logsync

... and if you have Logger32 running and it is connected to your radio on comm 16. What happens if you close the radio port and re-open it? 73.