Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Hamlogger
- Messages
Search
Re: QSL Utility
Rick the reason I said it didn't upload is because one, I received an error message telling me to check the error log which I cannot find, two, normally after it says successful I see the QSO's in the lower right corner being processed which I didn't this time, and third I have been unable to reach LOTW on my network for the past two days and am trying to troubleshoot that. The last time something like this happened I exported a partial log and manually signed it with TQSL then uploaded it and it didn't report any duplicate QSO's that I can recall so that tells me they were never uploaded, unless as you stated it might take a day or two for the original upload to appear.
?
Jim K2QB |
Re: QSL Utility
¿ªÔÆÌåÓý
Dear all ... the uploaded file if it is uploaded on LoTW will no longer be on your computer you just have to give the time for the server to manage and at the same time there is actually the crossing of data that's all ... if you have any doubts just manually
flag any suspicious qsos when at the next sending these will be added again if missing otherwise if they are already present you will be notified by the system.
73's Steve
Da: [email protected] <[email protected]> per conto di Rick Ellison via groups.io <rellison@...>
Inviato: marted¨¬ 4 marzo 2025 02:41 A: [email protected] <[email protected]> Oggetto: Re: [hamlogger] QSL Utility ?
"The utility removes all the Flag to Upload to LOTW before it actually uploads the file. "
This is not the case. This question is being asked by Logger32 and has not passed any Data off to the utility at this point.
"Today I attempted to upload almost 800 QSO'S to LOTW and the utility indicated the ADIF file was signed and uploaded and asked if I wanted to remove the QSL upload flag to which I said yes. When I attempted to download from LOTW I was told there was an
error and to try again later. Well, the server was not available so now I have almost 800 QSO's that should still be flagged as Send LOTW QSL."
How do you know your qso's are not uploaded to LOTW? If you received a return from TQSL that says the upload was complete. 9 out of 10 times your qso's are located on LOTW and you just need to wait for them to show up. Over the past week I have been checking
LOTW a couple times a day for a qso to show up for another project I am working on and after 2 days it finally showed up for the other station I worked but I have yet seen no confirmation from the other station yet to show in my qso's.
"Isn't there a way that the Send LOTW QSL flag wouldn't get removed until there is an actual confirmation of a successful upload, not just the signing of the ADIF file by TQSL?"
On the utility on the LOTW tab there is a checkbox that tells the utility to update the qso flags in Logger32 as each qso is uploaded. This takes QUITE a bit of time (With 800 qso's I estimate about 20 minutes.) and a lot of people do not want to wait
that long. So the checkbox was put in place.
73 Rick N2AMG
On 3/3/2025 1:24 PM, Jim K2QB via groups.io wrote:
|
Re: QSL Utility
¿ªÔÆÌåÓý"The utility removes all the Flag to Upload to LOTW before it
actually uploads the file. "
This is not the case. This question is being asked by Logger32
and has not passed any Data off to the utility at this point.
"Today I attempted to upload almost 800 QSO'S to LOTW and the
utility indicated the ADIF file was signed and uploaded and asked
if I wanted to remove the QSL upload flag to which I said yes.
When I attempted to download from LOTW I was told there was an
error and to try again later. Well, the server was not available
so now I have almost 800 QSO's that should still be flagged as
Send LOTW QSL."
How do you know your qso's are not uploaded to LOTW? If you
received a return from TQSL that says the upload was complete. 9
out of 10 times your qso's are located on LOTW and you just need
to wait for them to show up. Over the past week I have been
checking LOTW a couple times a day for a qso to show up for
another project I am working on and after 2 days it finally showed
up for the other station I worked but I have yet seen no
confirmation from the other station yet to show in my qso's.
"Isn't there a way that the Send LOTW QSL flag wouldn't get
removed until there is an actual confirmation of a successful
upload, not just the signing of the ADIF file by TQSL?"
On the utility on the LOTW tab there is a checkbox that tells
the utility to update the qso flags in Logger32 as each qso is
uploaded. This takes QUITE a bit of time (With 800 qso's I
estimate about 20 minutes.) and a lot of people do not want to
wait that long. So the checkbox was put in place.
73 Rick N2AMG
On 3/3/2025 1:24 PM, Jim K2QB via
groups.io wrote:
|
QSL Utility
First thanks to Rick for the QSL utility and his other add-ins that work great. One issue with the QSL utility that I wish could be addressed is the following. The utility removes all the Flag to Upload to LOTW before it actually uploads the file. Today I attempted to upload almost 800 QSO'S to LOTW and the utility indicated the ADIF file was signed and uploaded and asked if I wanted to remove the QSL upload flag to which I said yes. When I attempted to download from LOTW I was told there was an error and to try again later. Well, the server was not available so now I have almost 800 QSO's that should still be flagged as Send LOTW QSL.
Isn't there a way that the Send LOTW QSL flag wouldn't get removed until there is an actual confirmation of a successful upload, not just the signing of the ADIF file by TQSL?
?
Thanks...K2QB |
Re: font
I have no idea what a AGHIv?font is, but if it works for you on the Logbook Entry Window, use it. SeventyThree(s).
|
Re: font
In your example, Logger32 uses the ADIF fields NAME and QTH, not NAME_INTL and QTH_INTL
?
The ADIF fields NAME and QTH use ASCII characters 32 to 126. The NAME_INTL and QTH_INTL use UTF-8 encoded Unicode.
?
Logger32 does not support import/export of ASX files, only ADIF files. Unicode fields (like NAME_INTL and QTH_INTL) are not allowed in ADIF files, only ADX files.
?
The short answer to your question is no, the Logbook Entry Window entry fields support ASCCI characters 32 to 126 only. This is by design.
?
Or something like that. SeventyThree(s).
|
Re: Strange
#ft8
If, as you say, there are no decoded callsigns appearing the UDP BandMap, then it is possible/probable that Logger32 and JTDX (or whatever) are not talking to each other by UDP messages. One of the numerous messages is the all important 'Log this contact' message.
?
You should probably check that the UDP port in JTDX (or whatever) and Logger32 are both open, and they are both using?the same port #. You could also look at the UDP port debug window to see in JTDX (or whatever) is talking to Logger32.
?
SeventyThree(s).
|
Re: Strange
#ft8
¿ªÔÆÌåÓýSorry about ?little information , the call signs don¡¯t show up in the band map panel and I also checked the tcp/adif is and it was unchecked Bob, ?every thing working on the 26th of Feb and nothing was installed on or after shutdown my evening time, using windows 10 pro and to be honest I¡¯ve had this as the only issue in a hell of a while Ron G6GA On 27 Feb 2025, at 7:49?pm, Bob via groups.io <k4cy@...> wrote:
|
Re: Strange
#ft8
Precious little information ....I'll assume you're using UDP logging. I'll further assume the Logger32 UDP BandMap is alive as well, and showing decoded stations callsigns.
?
If my assumptions are correct, then on the UDP BandMap click CONFIG. Click LOGGING OPTIONS. Make sure the TCP/ADIF LOGGING option is UNchecked. If it is checked, it turns UDP logging off.
?
SeventyThree(s).
|
Strange
#ft8
Anyone had any problems today as regard to logging FT8 and FT4 qso¡¯s direct into to logger32
none of qso¡¯s were logged into my logbook using?
JTDX WSJTX luck has if the went info there respective logbooks. Everything worked as normal yesterday nothing added today or removed?
73 Ron G6GA |
Re: GO-to-previous_Freq
AHHH!? So you are the ONE !!!!??? 73 de Larry K8YYY On Wed, Feb 26, 2025 at 1:48?PM Bob via <k4cy=[email protected]> wrote:
|
Re: GO-to-previous_Freq
If I needed to do that, I would use macros I already have ...
?
a)? Split up 5
b)??Tune
c)? Split off.
?
SeventyThree(s).
?
PS. I always tune on the TX frequency. It gives the other station warning to turn down his RF gain before I call ...
|
Re: GO-to-previous_Freq
HI Gary, John et All.
Thank you for the advices, after 20 et more years of L32 use I have learned more options I never used HI.
Both options the Scratchpad and the DX-Spot_History relate to the SPOTs list,?
but these are not my almost 20Y_newby needs...
Let me be more specific: I am on QRG_A have to check the PA_tuning and dont want to TX on A_QRG
so I move to QRG_B anywhere up\down the band or just move from A to B or even C,D,E qrgs
(the ColibriNano SDR and his big brothers) have a memorized list of more that 10 positions)
and I want go back without being?related to any SPOT.
For the QRG BtoA move N1MM has F8 hotkey, only one position but it suffice in many occasions.
Bet you to recall the previous QRG....
Or take pen&paper to write on HI.
As I have written in my previous post the modern FLEXRADIO8k6 has not such feature...
but this is another story
73
Phil ex IC8POF-now IU0EBV
? |
Re: oqrs direct requests
There is no column for OQRS on the Logger32 Logbook Page or Previous QSOs? windows. SeventyThree(s).
|
Re: L32LogSynch question
¿ªÔÆÌåÓýOn Logsync you will need to use the dropdown on the LOTW tab and
select the call you want to upload under. That dropdown is filled
by reading the station_data file that is created by Tqsl. If you
don't have a station_date file created then open Tqsl and it is
located on the top menu. 73 Rick N2AMG On 2/26/2025 3:04 AM, IK6CGO via
groups.io wrote:
|
to navigate to use esc to dismiss