Dear,
I set all program as such as a Log4OM manual page 177 but whenl i put in log on WSJT-X a QSO, JTAlert make a Logging Alert Error, but on Log4OM QSO logged without problem? where is my mistake?
JTALERT Logging Warning
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: JTALERT Logging Warning
Your mistake is in JTalert settings. Give JTalert more time before it sends a warning like this.
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: JTALERT Logging Warning
Thanks for your suggestion I tried to increase the value up to 20s but nothing to do my computer is of the latest generation an eleventh generation i7 I can not imagine that it is slow enough to create this problem, one thing is sure that I notice that the QSO is recorded on Log4OM with a certain delay compared to before I would not like it to depend on this new version 2.26.0.0
Re: JTALERT Logging Warning
I checked, when I confirm the logging on wsjtx in my log4om log it is recorded more than 22 seconds later, so jtalert, even set to 20 seconds, returns the error screen. how is this exaggerated delay in log4om logging possible?
Re: JTALERT Logging Warning
Apenas Marque a conexão UDP ! O Erro parou !!
- Attachments
-
- Erro_JTAlert.jpg (168.15 KiB) Viewed 2808 times
Re: JTALERT Logging Warning
Those of you with issues need to download the current version of Log4OM and go into your settings for incoming connections and DELETE them and re-add the connections using the preset options at the bottom. This is all new. I would note your existing port to your 3rd part application before deleting the old connection. When you add the new connection, make sure the port agrees.
The new version work much better with FT8 programs.
The new version work much better with FT8 programs.
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: JTALERT Logging Warning
I'm setting up my connections between WSJT-X, JTAlert and Log4OM again after getting a new computer. Things have chantged as noted above, but after reading the JT Programs integration section I'm a bit overwhelmed with the options. What seems to be the most preferred way to set up communications? I'm trying to have a direct connection between WSJT-X and Log4OM while turning the UDP transmissions off in JTAlert but I'm not sure if that is the best practices way.
Also, is there any way to test a log from WSJT-X before going "live"?
73, Brian WB8AM
EDIT: Found the answer I'm looking for here https://forum.log4om.com/viewtopic.php?p=44553#p44553
Also, is there any way to test a log from WSJT-X before going "live"?
73, Brian WB8AM
EDIT: Found the answer I'm looking for here https://forum.log4om.com/viewtopic.php?p=44553#p44553