Log4OM

Not that would be listening to UDP ports,

WSJT-X 2.1.2 wont work when its open on its own with Log4om, I'm only opening the 2nd program to test them side by side,

EI2GLB wrote: 17 Jan 2020, 15:46 I have it set that way Terry

WSJT-X is on port 2334
Bot is on port 2333

Log4OM is set to listen to both,

I'm trying to find error's in the log file but it's not making any sense to me

That’s the same way I’m doing it.

There is an INBOUND service named MESSAGE_LISTENER.

This type of service is only used to track and write incoming messages into application log.
First of all, check if something is arriving on that port to Log4OM by setting this service running on the listening UDP port and check program log.
If you don't see anything, nothing is arriving to Log4OM.
If you see something we can start thinking about

I have testing qso logging with multi-slices where log4om is on a different PC and found it work ok with wsjtx & mshv previously not supported on V1.

Note I've tested the logging QSO the area I may use in the future.

On Mshv only use the message_ADif option (middle tick) & wsjtx only use the second UDP setup, set ip port to say Slice A 2301 Slice B 2302 etc

On log4om v2 setup a In-Bound ADIF_message service for each port 2301, 2302, etc.

I tried local and remote and was able to log QSO on all slices, note there is a delay until it hits the log, but for logging it is no problem.

I'm only testing at moment, but may switch over to log4om when the qsl card is functional.

If I can help in any way, please email I can send screen dumps.

[email protected] Neil

"When QSL card is functional!"

Please explain

I can find no reference to MESSAGE_LISTENER in my complete log file and that includes the port that works,

here is a section of the file that references a station I am calling but his call does not enter the callsign box in Log4om

17:49:39.252 Debug: [#=z3kID5hlOqeRk$dRRNo3sYrI=][MoveNext] : ##### UDP MESSAGE RECEIVED ##### ??? WSJT-X - Slice / FT8 DL5JM -2 FT8 ? ? EI2GLB IO63MD JO31 ???? ???????? Default on UDP port 2334 (TEST/JT_MESSAGE) from 127.0.0.1:63104#####
17:49:39.582 Debug: [#=zfRyP11wsrr3YnUM09HZJMYLQIw59Q8vheQ==][MoveNext] : INCOMING MESSAGE FROM SERVICE: TEST: ???? WSJT-X - Slice / FT8 DL5JM -19 FT8 ? ? EI2GLB IO63MD JO31 ???? ???????? Default

Message listner is a udp inbound service in the conndctions menu, set one up to listen to the port causing the issue and watch the realtime log window in the help menu

Hi Terry,

Off subject Documentation Tab is only a place holder, although the eqsl cards existing downloaded from eqsl.
Structure and cards look good, viewing is not possible yet.

Any back on subject Gridtracker passes QSO through to Log4om V2 ok, therefore it can be fed from WSJTx, JTDX or MSHV, a workaround for JTDX (gridtracker is heavy on resources though most people jtalert will be better when a release is available)

Sorry I did intend to go off subject, the connectivity looks really magic... thanks to all the team

Here is what I could interpret from Log file (sorry but I honestly get lost in the file):

241 DEBUG: [#=zfRyP11wsrr3YnUM09HZJMYLQIw59Q8vheQ==][MoveNext] : INCOMING MESSAGE FROM SERVICE: DX CALL: ???? WSJT-X 2.1.2 0068f9
2020-01-17 18:10:14.3974 DEBUG: [#=z3kID5hlOqeRk$dRRNo3sYrI=][MoveNext] : ##### UDP MESSAGE RECEIVED ##### :
???? WSJT-X - Slice ??? FT8 N3MK -15 FT8
n ? HI8SMX FK58AK FM27 ???? ???????? Default
on UDP port 2338 (DX/JT_MESSAGE) from 127.0.0.1:53548
#####
2020-01-17 18:10:14.3984 ERROR: [#=zfRyP11wsrr3YnUM09HZJMYLQIw59Q8vheQ==][MoveNext] : [EXCEPTION] Length cannot be less than zero.
Parameter name: length System.ArgumentOutOfRangeException: Length cannot be less than zero.
Parameter name: length
at System.String.Substring(Int32 startIndex, Int32 length)
at L4ONG.BL.StaticFunctions.#=zfRyP11wsrr3YnUM09HZJMYLQIw59Q8vheQ==.MoveNext()

This was the message I got when I worked N3MK a few minutes ago.

Could you guys interpret something out of this?

Thanks

I saved the log file from that window and did a search and no sign of MESSAGE_LISTENER in it??

G4POP wrote: 17 Jan 2020, 18:05 Message listner is a udp inbound service in the conndctions menu, set one up to listen to the port causing the issue and watch the realtime log window in the help menu