Search found 6 matches

by G0KAD
20 Mar 2023, 19:29
Forum: Error reports
Topic: QRZ.com Problem
Replies: 8
Views: 1439

QRZ.com Problem

Hi, Just updated to v2.27.1.0. Spotted that some other were having a problem with QRZ.com so thought I'd check. External data lookup is working well but the auto-upload of QSO isn't working. Using QSL Manager I selected the necessary QSO and tried uploading them. QSLcom Capture.jpg All but one uploa...
by G0KAD
04 Apr 2022, 18:18
Forum: Error reports
Topic: Solar Information at upper RHS of main window
Replies: 2
Views: 998

Re: Solar Information at upper RHS of main window

I love that we have this problem :)
by G0KAD
04 Apr 2022, 18:09
Forum: Feature suggestions
Topic: Cluster Filter by Date
Replies: 1
Views: 770

Cluster Filter by Date

Hi all, I wonder if others would find it useful to have the cluster filtered by data? For example, when chasing DXCC for the year i.e. marathon chasing. JTAlert has a great way of highlighting new DXCC for the year on any band or all bands. Having something similar for SSB and CW in Log4OM Cluster w...
by G0KAD
18 May 2020, 08:38
Forum: User support
Topic: MSK144 Edit QSO Problem
Replies: 2
Views: 1599

Re: MSK144 Edit QSO Problem

Thanks, that fixed the problem. 73 until the next time :D
by G0KAD
14 May 2020, 17:41
Forum: User support
Topic: MSK144 Edit QSO Problem
Replies: 2
Views: 1599

MSK144 Edit QSO Problem

Hi,

A small issue in v2.5.0. When editing a logged QSO which has been correctly auto-logged from MSHV the RST (sent and received) are changed from the actual report which is normally in the range of 0 to +22 to a CW report e.g. 599. This doesn't appear to be edittable.

Regards
Mike
G0KAD
by G0KAD
02 Feb 2020, 13:31
Forum: User support
Topic: Voice Keyer PTT
Replies: 4
Views: 2806

Voice Keyer PTT

I'm using a K3 with Log4OM V2. I've recorded a Voice Keyer message as per the LOG4OMNG manual. Using the CTRL F1 on the PC keyboard sends the message perfectly including activating the K3 PTT. The levels are fine and the AUDIO box appears on the status bar of Log4OM as expected. After the message ha...