Log4OM

pd4jo

I was chatting away on FT8 And FT4 today with Log4Om 2.28.0.0 being fed by WSJTX through GridTracker. I made several QSO's and these are normally logged immediately in Log4Om so I don't check that all the time.
But after signing off, I noticed that of all of today's QSO's (15 or so) only 1 was logged ...

DL8BDU

Hello everyone, while working in Statistics > Country Statistics, I noticed that FT4 QSLs from LotW don't result in confirmation of a country in the corresponding band. Can someone explain this to me?
73, de Klaus DL8BDU

VK7XX

... QSO's saved in Log4OM directly will be 6

Providing your using the UDP connection to WSJT in Log4OM you can edit the connection to 'Update the grid' when adding it to the logbook

thanks heaps Terry, that explains it all... yes, 99% via Digi FT8 or FT4.

cheers from way down under de John
VK7XX

va3vf

... are pirates.

Also, half of the pirate entries have no callsign. This is new to me, since they were mostly /MM before.

Lastly, they seem to be all FT4 spots.

Edit 1: I configured the cluster to "set/noft4" for now. It has reduced the number of entries, but it still happens with FT8 spots, albeit ...

2W0NED

... i work a station and manually enter into my log book on Log4OM, I see things for my callsign correctly, as :

l4om1.png

I often use WSJT-X for FT4/8, and this is where the problem lies.

QSO's that are imported have MY information incorrect, which causes a problem when uploading to LOTW.

An ...

N8XMS

With some research, I've figured it out. I needed to go into the band plan configuration files and remove the special 40-meter FT4 frequency. The mode now stays at CW for 7.047.

Paul - N8XMS

N8XMS

... But here is the strange thing... With my radio set for CW, as I tune across the lower end of 40 meters, the mode in the logging software changes to FT4 when the frequency is between 7.047 and 7.048 MHz. The radio does not change, it is still set to CW, but the mode shown in the Log4OM window, that ...

w8qh

... It shows a time (various) but does not show what it is making reference to.
In my case I have noticed this when I am using digital modes, FT8/FT4
My set up is, Windows 10 Pro, I7 Processor 16GB ram, 500 gb ssd. & WiFi 10 feet to the internet router.
Programs running
flrig to an IC-7300
UDP for ...

ve3wej

I cant get eqsl to NOT match mfsk with my mfsk(ft4) as they will allow confirms for the other qso party, but log4om rejects the match so I get nothing

Is there an override so mfsk can be matched for me. but not the other modes of mfsk. I can not get eqsl to fix this ( been trying for over 2 years

ik8ozv

Hello all,
i am looking the way how to transfer a qso made in FT8 or FT4
done with MSHV program just how it goes with WSJT-X and JTDX.
Please is it possible?
If yes where and how to set?
Thanks
Enzo

Search found 270 matches: FT4

logging stopped suddenly

no Country confirmation by FT4 LotW QSL in Statistic tool

Re: Recording of Grid Squares

Cluster tab: Pirate flag spots.

Welsh callsign change... causing a headache

Re: Unwanted operating mode change on 40 meters

Unwanted operating mode change on 40 meters

Slow Response from external source notification

confirming mfsk

MSHV Transfer QSO