Hello and HNY to everyone.

Anyone using MSHV to log to Log4OM?

Been through most (all) UDP/TCP settings on network options - tried combination of port numbers - compared with what I have set on Log4OM.  Using the ‘Log A QSO’ button as a test I cannot get any communications - the MSHV log is populated so the logging is working.
No issues with other FT8 software not being logged.

Pointers / tips welcome.

Thanks

Tom
GM8MJV

On 2 Jan 2021, at 18:33, Michael, 5P1KZX <5p1kzx@...> wrote:

Hi Tom

Don't know if this what you are asking for:

Here I have MSHV on one computer with the Radio on 50.313. If I'm working somebody on 6m MSHV will forward the QSO when it's logged. It's done via UDP port fwd ADIF msg. The fwd port must NOT be used by anything else or it will not work.

The first picture is MSHV setting where I have chosen UDP port 2222 and the server is my PC where Log4OM is located. If MSHV are on same PC  server must be 127.0.0.1 witch "Local Host" / "Local Computer"

 The second picture show the setting in Log4OM where I have made a UDP Inbound Port for ADIF_MESSAGE called NET on port 2222. The first port with the nam MSHV_DIRECT has no Function in this Set-up. Only the one with the red lines are in use when fwd from MSHV to Log4OM.

 73 de Michael 5p1kzx

Den 02-01-2021 kl. 16:27 skrev Tom, GM8MJV:

Hello and HNY to everyone.

Anyone using MSHV to log to Log4OM?

Been through most (all) UDP/TCP settings on network options - tried combination of port numbers - compared with what I have set on Log4OM.  Using the ‘Log A QSO’ button as a test I cannot get any communications - the MSHV log is populated so the logging is working.
No issues with other FT8 software not being logged.

Pointers / tips welcome.

Thanks

Tom
GM8MJV

Thanks Michael

Thanks Michael

On 3 Jan 2021, at 02:20, Tom, GM8MJV <tom@...> wrote:

Thanks Michael

I think I have tried that setting - the only difference is I am using a multi-cast address as other apps are picking up the data GridTracker - I will knock everything back to the 127.0.0.1 address and see if it makes any difference.

Regards

Tom

GM8MJV

On 2 Jan 2021, at 18:33, Michael, 5P1KZX <5p1kzx@...> wrote:

Hi Tom

Don't know if this what you are asking for:

Here I have MSHV on one computer with the Radio on 50.313. If I'm working somebody on 6m MSHV will forward the QSO when it's logged. It's done via UDP port fwd ADIF msg. The fwd port must NOT be used by anything else or it will not work.

The first picture is MSHV setting where I have chosen UDP port 2222 and the server is my PC where Log4OM is located. If MSHV are on same PC  server must be 127.0.0.1 witch "Local Host" / "Local Computer"

<MSHV ADIF forward qso.PNG>

 The second picture show the setting in Log4OM where I have made a UDP Inbound Port for ADIF_MESSAGE called NET on port 2222. The first port with the nam MSHV_DIRECT has no Function in this Set-up. Only the one with the red lines are in use when fwd from MSHV to Log4OM.

<Adif connection NET port 2222.JPG>

 73 de Michael 5p1kzx

Den 02-01-2021 kl. 16:27 skrev Tom, GM8MJV:

Hello and HNY to everyone.

Anyone using MSHV to log to Log4OM?

Been through most (all) UDP/TCP settings on network options - tried combination of port numbers - compared with what I have set on Log4OM.  Using the ‘Log A QSO’ button as a test I cannot get any communications - the MSHV log is populated so the logging is working.
No issues with other FT8 software not being logged.

Pointers / tips welcome.

Thanks

Tom
GM8MJV

On 3 Jan 2021, at 23:43, Don, G1GEY via groups.io <g1gey@...> wrote:

Hi Tom

Do you have these set?

From the menu Options \ Log Options

x Log automatically QSO MSK ft8/4

x Log QSO start date time = end date time

x turn auto comments off

73

Don G1GEY

On 3 Jan 2021, at 02:20, Tom, GM8MJV <tom@...> wrote:

Thanks Michael

I think I have tried that setting - the only difference is I am using a multi-cast address as other apps are picking up the data GridTracker - I will knock everything back to the 127.0.0.1 address and see if it makes any difference.

Regards

Tom

GM8MJV

On 2 Jan 2021, at 18:33, Michael, 5P1KZX <5p1kzx@...> wrote:

Hi Tom

Don't know if this what you are asking for:

Here I have MSHV on one computer with the Radio on 50.313. If I'm working somebody on 6m MSHV will forward the QSO when it's logged. It's done via UDP port fwd ADIF msg. The fwd port must NOT be used       by anything else or it will not work.

The first picture is MSHV setting where I have chosen UDP port 2222 and the server is my PC where Log4OM is located. If MSHV are on same PC  server must be 127.0.0.1 witch "Local Host" / "Local Computer"

<MSHV ADIF forward qso.PNG>

 The second picture show the setting in Log4OM where I have made a UDP Inbound Port for ADIF_MESSAGE called NET on port 2222. The first port with the nam MSHV_DIRECT has no Function in this Set-up. Only the one with the red lines are in use when fwd from MSHV to Log4OM.

<Adif connection NET port 2222.JPG>

 73 de Michael 5p1kzx

Den 02-01-2021 kl. 16:27 skrev Tom, GM8MJV:

Hello and HNY to everyone.

Anyone using MSHV to log to Log4OM?

Been through most (all) UDP/TCP settings on network options - tried combination of port numbers - compared with what I have set on Log4OM.  Using the ‘Log A QSO’ button as a test I cannot get any communications - the MSHV log is populated so the logging is working.
No issues with other FT8 software not being logged.

Pointers / tips welcome.

Thanks

Tom
GM8MJV

Hi Don