Hi Team
This is a V1 question (V1.41.0).
It appears that Log4OM is not able to send long calls such as XXnSTAYHOME for lookup query to QRZ.com (when entering the call in the QSO details). Other lookups with shorter calls are working fine and I have a working XML subscription on QRZ.com. The calls where I have observed this problem do have records at QRZ.com.
Any thoughts?
Thansk
Tony YO3IPR
V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
Hi Tony,
same problem is in V2 but Log4OM is send what is in the callsign field. Please ask qrz.com
for that support question.
same problem is in V2 but Log4OM is send what is in the callsign field. Please ask qrz.com
for that support question.
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: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
Hi Juergen
This one works for example: ON4HEROES
Are we sure the full call is being sent? not a shortened one?
Please confirm and if so, I will open a ticket at QRZ.com
Thanks
Tony YO3IPR
This one works for example: ON4HEROES
Are we sure the full call is being sent? not a shortened one?
Please confirm and if so, I will open a ticket at QRZ.com
Thanks
Tony YO3IPR
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
Hi Tony,
i am not a Member of qrz.com anymore so i can´t check. Simply try a new upload and after that check
the Log4OM Logfile. It will show you what V1 have send to qrz.com. See the Help Menu item to open
the Logfile.
But see my screenshot of the HRDlog.net site. Log4OM transmitting the full call to each external service.
i am not a Member of qrz.com anymore so i can´t check. Simply try a new upload and after that check
the Log4OM Logfile. It will show you what V1 have send to qrz.com. See the Help Menu item to open
the Logfile.
But see my screenshot of the HRDlog.net site. Log4OM transmitting the full call to each external service.
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.
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
By the way, you have posted thi in the V2 version section of the Forum. If i, or another team member, see
your next answere we will be move it to the V1 section ....
your next answere we will be move it to the V1 section ....
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: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
Hi Juergen
The problem is with LoG4OM, see log details here:
2020-04-12 14:59:00.8862 INFO: QrzComManagement: Begin search for OR4STAYHOM
2020-04-12 14:59:01.5075 WARN: QrzComManagement: QRZ.COM Lookup error: Not found: OR4STAYHOM
2020-04-12 14:59:01.5105 INFO: Log4OMMainWindow: Updating QSO after QTH Lookup
2020-04-12 14:59:01.5125 INFO: SharedFunctionsManagement: Checking External information. Initial values: DXCC COUNTRY
2020-04-12 14:59:01.5345 INFO: SharedFunctionsManagement: Check Country got Belgium
2020-04-12 14:59:05.3169 INFO: QrzComManagement: Begin search for OR8STAYHOM
2020-04-12 14:59:05.4654 WARN: QrzComManagement: QRZ.COM Lookup error: Not found: OR8STAYHOM
2020-04-12 14:59:05.4674 INFO: Log4OMMainWindow: Updating QSO after QTH Lookup
2020-04-12 14:59:05.4704 INFO: SharedFunctionsManagement: Checking External information. Initial values: DXCC COUNTRY
2020-04-12 14:59:05.4904 INFO: SharedFunctionsManagement: Check Country got Belgium
We are not sending the last letter!
Appologies for posting in the V2 secion by mistake. I didnt look closely enough. If you want to move this query thats fine but please let me know the new URL so I can find it easily (I already have opened a ticket at QRZ.com and gave them the current link to this thread).
Thanks
Tony YO3IPR
The problem is with LoG4OM, see log details here:
2020-04-12 14:59:00.8862 INFO: QrzComManagement: Begin search for OR4STAYHOM
2020-04-12 14:59:01.5075 WARN: QrzComManagement: QRZ.COM Lookup error: Not found: OR4STAYHOM
2020-04-12 14:59:01.5105 INFO: Log4OMMainWindow: Updating QSO after QTH Lookup
2020-04-12 14:59:01.5125 INFO: SharedFunctionsManagement: Checking External information. Initial values: DXCC COUNTRY
2020-04-12 14:59:01.5345 INFO: SharedFunctionsManagement: Check Country got Belgium
2020-04-12 14:59:05.3169 INFO: QrzComManagement: Begin search for OR8STAYHOM
2020-04-12 14:59:05.4654 WARN: QrzComManagement: QRZ.COM Lookup error: Not found: OR8STAYHOM
2020-04-12 14:59:05.4674 INFO: Log4OMMainWindow: Updating QSO after QTH Lookup
2020-04-12 14:59:05.4704 INFO: SharedFunctionsManagement: Checking External information. Initial values: DXCC COUNTRY
2020-04-12 14:59:05.4904 INFO: SharedFunctionsManagement: Check Country got Belgium
We are not sending the last letter!
Appologies for posting in the V2 secion by mistake. I didnt look closely enough. If you want to move this query thats fine but please let me know the new URL so I can find it easily (I already have opened a ticket at QRZ.com and gave them the current link to this thread).
Thanks
Tony YO3IPR
Last edited by yo3ipr on 12 Apr 2020, 15:15, edited 1 time in total.
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
We have extended the acceptable number of characters for the call sign field in the next release
FYI the ARRL/LOTW have just had to do the same due to this stayathome call suffix
I wish the different legislative bodies would stick to the parameters ant not allow these weird exceptions
FYI the ARRL/LOTW have just had to do the same due to this stayathome call suffix
I wish the different legislative bodies would stick to the parameters ant not allow these weird exceptions
73 Terry G4POP
Re: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
Hi Terry
Yes, you and me both, but we all know that the various national administrative bodies either don't listen or don't adequately understand their users.
Stay well and Happy Easter.
73 Tony YO3IPR
Yes, you and me both, but we all know that the various national administrative bodies either don't listen or don't adequately understand their users.
Stay well and Happy Easter.
73 Tony YO3IPR
Re: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
And we can only imagine when someone, some group comes up with some event related to the Mary Poppins song:
Supercalifragilisticexpialidocious
I can almost see this happening in today's world.
Supercalifragilisticexpialidocious
I can almost see this happening in today's world.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: V1 not able to send long callsigns (e.g. XXnSTAYHOME) for QRZ.com lookup
Agreed Nolan. if the modern world tells us anything it's "never say never".
PY100RADIOAFICIONADOSDOBRASIL anyone?
PY100RADIOAFICIONADOSDOBRASIL anyone?