Log4OM

Hallo. Strange thing. After starting Log4OM, downloading data from QRZ.com works. I put a sign and after a while there is everything. After a few minutes of program work, downloading data stops working. After entering the character, nothing happens. Maybe it's a relationship with JTAlert. The callsign from JTAlert is downloaded and appears in the CALLSIGN field but the data from QRZ.com is not downloaded.
Robert SP8SN

I'm having the same issue after upgrading to 2.3. 2.2. was working fine.
I got it to work entering one call... then it just stops pulling any data from QRZ to populate the qso main screen.
thanks,
Will

remote control is not working from jtalert after upgrade to 2.3
did some more testing.
if I start log4om 2.3. I can enter call signs many times and it looks up external data and displays.

as soon as I click on a call sign now in JTalert it populates the call sign... this error shows up in the log4om2 log below... then no more call signs will look up external data..

02:37:43.706 Info: [#=zjsHcIffwc7hV9JTtLtnJHtc=] : ##### REMOTE CONTROL UDP MESSAGE RECEIVED ##### :<CALLSIGN>VE1CNS on UDP port 2241 from 127.0.0.1:56889#####
02:37:43.729 Debug: [#=zjsHcIffwc7hV9JTtLtnJHtc=][MoveNext] : Remote control callsign lookup: VE1CNS
02:37:43.754 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call VE1CNS on date 2/12/2020 2:37:43 AM
02:37:43.782 Debug: [Countries][SearchCallsign] : Country internal analisys for VE1CNS(VE1CNS - ) returned: FullCallsign: Not found Prefix: Not found Callsign: Canada
02:37:44.037 Debug: * [#=z3AMERkGaC3KlBwXW6Q==][MoveNext][10270 ms] : Loading Awards items from database for multiple award codes
02:37:44.06 Debug: [#=zjsHcIffwc7hV9JTtLtnJHtc=][MoveNext] : Error ConnectionReset An existing connection was forcibly closed by the remote host on UDP port 2241

all I did was upgrade from 2.2 to 2.3. appears something is breaking when a call sign is sent from jtalert. then all external data pull stops.

thanks,
Will

Changing subject... this is not really a pulling qrz data issue as far as I can tell.
something is not working with remote control.

The main UI stops pulling data after the first JTalert call sign I click on. The UI works until I do that.
errors below..
--------
remote control is not working from jtalert after upgrade to 2.3
did some more testing.
if I start log4om 2.3. I can enter call signs many times and it looks up external data and displays.

as soon as I click on a call sign now in JTalert it populates the call sign... this error shows up in the log4om2 log below... then no more call signs will look up external data..

02:37:43.706 Info: [#=zjsHcIffwc7hV9JTtLtnJHtc=] : ##### REMOTE CONTROL UDP MESSAGE RECEIVED ##### :<CALLSIGN>VE1CNS on UDP port 2241 from 127.0.0.1:56889#####
02:37:43.729 Debug: [#=zjsHcIffwc7hV9JTtLtnJHtc=][MoveNext] : Remote control callsign lookup: VE1CNS
02:37:43.754 Debug: [Countries][SearchCallsign] : Performing Search Callsign on call VE1CNS on date 2/12/2020 2:37:43 AM
02:37:43.782 Debug: [Countries][SearchCallsign] : Country internal analisys for VE1CNS(VE1CNS - ) returned: FullCallsign: Not found Prefix: Not found Callsign: Canada
02:37:44.037 Debug: * [#=z3AMERkGaC3KlBwXW6Q==][MoveNext][10270 ms] : Loading Awards items from database for multiple award codes
02:37:44.06 Debug: [#=zjsHcIffwc7hV9JTtLtnJHtc=][MoveNext] : Error ConnectionReset An existing connection was forcibly closed by the remote host on UDP port 2241

all I did was upgrade from 2.2 to 2.3. appears something is breaking when a call sign is sent from jtalert. then all external data pull stops.

thanks,
Will

K5YE wrote: ↑12 Feb 2020, 15:55 The main UI stops pulling data after the first JTalert call sign I click on. The UI works until I do that.

exactly

Welcome

This issue has already been reported but no response. Version 2.2 works without a problem, and in 2.3 every now and then a problem.

This is a very annoying problem , like the Pse QSL problem when printing, also Omnirig is not working with my IC-7300 + IC-9700 (switching to RTTY when operating in FT8), logging from JTDX + JTAlert > Log4OM2 (v.2.3.0.0) works O.K.
I just returned to using v.2.2.0.0 at least QRZ lookup works again...
Awaiting v.2.4.0.0. ...

73 de Frank PH2M

ph2m wrote: ↑24 Feb 2020, 13:16 This is a very annoying problem , like the Pse QSL problem when printing, also Omnirig is not working with my IC-7300 + IC-9700 (switching to RTTY when operating in FT8), logging from JTDX + JTAlert > Log4OM2 (v.2.3.0.0) works O.K.
I just returned to using v.2.2.0.0 at least QRZ lookup works again...
Awaiting v.2.4.0.0. ...

73 de Frank PH2M

Switching to RTTY is because you have your IC7300 and Omnirig configured incorrectly, my 7300 switches to USB-D when I use any JT program with Log4OM and Omnirig

Use the IC7300 DATA Omnirig rig ini and set up accordingly

Hello Terry, trying Omnirig with IC-7300-Data + IC-9700-Data now, on both frequency is not correct, being on 5357 (60M-FT8 jumps to 5357,055 ), also op 144.174 the frequency jumps to 144.174,055 so still figuring out whats the best setup (I must not be the only user, using JTDX + JTAlert + Log4OM2 + IC-7300 + IC-9700 I think

73 de Frank PH2M

Good morning Frank,

looks like a JTDX problem. Having the same here and the + 55HZ diference only switching
whwn Log4OM with CAT is running and JTDX will be started. For now go to the band list
in JTDX and switch it again to the band you are working in and frequency steps back to
the correct one.