Search found 186 matches

by N6VH
23 Mar 2024, 19:40
Forum: Error reports
Topic: Erreurs ...
Replies: 7
Views: 319

Re: Erreurs ...

I'm using 2.32.1.0 and, using manual input, I can confirm there are many zone errors. For example, G4POP shows CQ zone 1 and ITU 2. I have "Use Clublog database" and "Use CTY database" checked.

73,
Jim N6VH
by N6VH
23 Mar 2024, 19:14
Forum: User support
Topic: POTA not storing in REF if activator in different country
Replies: 3
Views: 159

Re: POTA not storing in REF if activator in different country

Unfortunately, some stations operate in a country other than their own without using proper identification, in particular on FTxx modes. For example, if I were to operate in British Columbia, I would be required to sign N6VH/VE7. By doing so, I couldn't send my grid square in my CQ message (not real...
by N6VH
23 Mar 2024, 18:55
Forum: User support
Topic: How to prevent mode changes when changing frequency?
Replies: 3
Views: 129

Re: How to prevent mode changes when changing frequency?

I ran a test without WSJT-X running. I tested with the rig in USB and then CW. In both cases, when I got within about 500 Hz of the FT8 frequency, 24,915 in this case, Log4OM switched to FT8 mode. In Configuration/CAT Management, I do NOT have "Switch to DIGITAL mode when required" checked...
by N6VH
23 Mar 2024, 18:33
Forum: User support
Topic: Frequency not auto populating
Replies: 26
Views: 2484

Re: Frequency not auto populating

I was having the same problem, and was preparing to post about it when I saw this topic. In my case, I am using a Yaesu FTDX-101MP and the Win4Yaesu app. I had been using Omnirig 1.19, but just now installed 1.2, then restarted Log4OM 2.32.1.0. In my case the frequency is being populated as it shoul...
by N6VH
23 Mar 2024, 17:45
Forum: General discussions
Topic: ARRL is not accepting qsl cards without State printed
Replies: 2
Views: 383

Re: ARRL is not accepting qsl cards without State printed

Are you referring to the state that the recipient of your card lives in? I checked on the ARRL web page about the incoming buro, and didn't see anything about a state being required. Card for the ARRL incoming buro go to the call area of the ham's call. For example, a W6 living in Texas would get hi...
by N6VH
01 Feb 2024, 01:08
Forum: User support
Topic: POTA Data Entry On New Contact
Replies: 2
Views: 431

Re: POTA Data Entry On New Contact

As a hunter, the easy way to enter the POTA number is to put "POTA" and the park number in the comments box - POTA K-0042 - for example. It will be automatically be put into the Award Refs. section for that QSO. If you are using WSJT-X (or other similar apps) along with JTAlert for FT8/FT4...
by N6VH
23 Dec 2023, 17:55
Forum: User support
Topic: Grid locator source ?
Replies: 7
Views: 9370

Re: Grid locator source ?

I notice another issue with grids listed in the cluster. When I am spotted, my grid is spotted on the cluster as DM12, but it shows as DM05 in the cluster listing in Log4OM. Jim, This is because to avoid unnesesary load on the cluster we dont check every cluster spot with QRZ etc the spot locator i...
by N6VH
19 Dec 2023, 00:37
Forum: User support
Topic: Grid locator source ?
Replies: 7
Views: 9370

Re: Grid locator source ?

Jim, As I recall it tends to default to the approximate geographic center of the given country. Much more noticeable in large land-mass countries such as USA, Canada, Australia, etc.. I thought Lele had mostly resolved that situation, but then I don't run any FTxx modes anymore so don't have to dea...
by N6VH
11 Dec 2023, 22:16
Forum: User support
Topic: Grid locator source ?
Replies: 7
Views: 9370

Re: Grid locator source ?

If the grid isn't available from any source, Log4OM logs an arbitrary grid. I think it would be better to not log any grid (leave the field blank).

73,

Jim N6VH
by N6VH
03 Dec 2023, 15:59
Forum: General discussions
Topic: Lotw users
Replies: 3
Views: 7179

Re: Lotw users

TA4DX is in the lotw.txt file in the Log4OM configuration folder. However, that file was just updated today, at least here. It might be that your lotw.txt file hasn't been updated. Also, once it is, make sure you restart Log4OM. I hadn't done that at first, so he didn't show up as a LOTW user here, ...