Date   

This does not appear to be a LOTW.adi file

rick darwicki
 

I download the QSL report from ARRL and when I try to synchronize and get the subject message. Tried renaming it, cleaning the header etc. Is there a fix?

Thanks


Re: Eqsl synchro problem

ja1nlx
 

Do you use LogSync utility to synchronize ?

If so do you select correct downloaded file ?

73

On 2020/01/14 20:45, Panos wrote:
Hi to all. I am using the latest version but when I try to synchronize I get the "no valid adif record found" message, . The file can be opened by adifmaster. Is there a solution? 73

The file header:
ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>
--
73 de aki
JA1NLX


Re: Logger32 and IC9700

Bob
 

Google IC-9700 CAT MANUAL. I just took a peek myself. Apparently this is a VHF/UHF radio and requires 10 characters for the frequency. As I recall generic Icoms (not the 7xxx variety) use the same 10 characters for frequency, so on the surface, configuring a plain and simple Icom might just be your best bet. SeventyThree(s).

On January 14, 2020 at 2:47 PM "Neil, G3RIR via Groups.Io" <ackerley.neil@...> wrote:

good idea. I can see the debug info but I don't know what is correct. Are they documented somewhere?

 


Re: Logger32 and IC9700

Neil, G3RIR
 

good idea. I can see the debug info but I don't know what is correct. Are they documented somewhere?


Re: Logger32 and IC9700

Bob
 

Try looking at the Radio Debug Window to verify correct polling commands are being sent. 73.

On January 14, 2020 at 1:56 PM "Neil, G3RIR via Groups.Io" <ackerley.neil@...> wrote:

I am having problems connecting my IC9700 to Logger32 for CAT. The IC9700 connects to N1MM nicely. Logger32 will not connect to the IC9700.  My IC7610 connects to Logger32 and N1MM nicely.

Any clues, please.

Neil G3RIR

 


Re: Eqsl synchro problem

Bob
 

Please send the file to me as an attachment to k4cy@... 73.

On January 14, 2020 at 11:31 AM Panos <sv1grn@...> wrote:

New header:

ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>

still not working 73

 


Logger32 and IC9700

Neil, G3RIR
 

I am having problems connecting my IC9700 to Logger32 for CAT. The IC9700 connects to N1MM nicely. Logger32 will not connect to the IC9700.  My IC7610 connects to Logger32 and N1MM nicely.

Any clues, please.

Neil G3RIR


Re: Eqsl synchro problem

Bob
 

Send me the ADIF file by direct email to k4cy@... I will test it. 73.

On January 14, 2020 at 11:10 AM Panos <sv1grn@...> wrote:

Thanks I'll change the header. Ofcourse the adif isn't empty 73

 


Re: Eqsl synchro problem

Panos
 

New header:

ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>

still not working 73


Re: Eqsl synchro problem

Panos
 

Thanks I'll change the header. Ofcourse the adif isn't empty 73


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Gregg E
 

Thanks you Aki, I will try that when I have some more free time.
I am already configured for Auto Lookup.
Thanks
Gregg
W5IDX


On Tuesday, January 14, 2020, 12:16:27 AM CST, ja1nlx <ayoshida0205@...> wrote:


When you type W5IDX in Logbook entry window, do you see auto lookup window ?

and Name, State etc are populated in Logbook entry window ?

If so check "Log additional info from Logbook entry window" in Config/Logging option

in UDP BandMap. This is explained in the Logger32 Help. Look at paragraph 5.0 Menu

in the section "The UDP BandMap"

If not then setup Callsign lookup first. This is explained in the Logbook window/Callsign

lookup section in the Logger32 Help.


73

On 2020/01/14 13:04, Gregg E via Groups.Io wrote:
Bob or Anyone; how do you do this?  Is it in print somewhere?
I use the UDP setup to save the QSO into my logger file from WSJT but it only records the info from the WSJT screen. No auto Lookup.
Thanks
W5IDX



On Sunday, January 12, 2020, 09:10:38 AM CST, Bob <k4cy@...> wrote:


I have never downloaded an LoTW file, but I thought the state and some other fields were included in the record.

As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state.

And, FWIW, I'd recommend JTDX in preference to WSJT (fewer bugs and foibles, and much better receive sensitivity). SeventyThree(s).
On January 12, 2020 at 9:48 AM Marvin Stern <marbern@...> wrote:

When downloading LOTW received QSL's, how can Logger32 print state names in the State column instead of leaving it blank.
I'm mainly interested in files received from WSJT files which only contain grids, not names.
Marv, W2AOC

 
--
73 de aki
JA1NLX


Re: Eqsl synchro problem

Bob
 

The eQSL ADIF file header must have either  <PROGRAMID:20>eQSL.cc DownloadADIF or  <PROGRAMID:21>eQSL.cc DownloadInBox as its PROGRAMID, or it is rejected by Logger32. SeventyThree(s).

On January 14, 2020 at 6:54 AM Panos <sv1grn@...> wrote:

Later, from adifmaster saved it as adi with other name, this time I get the "wrong file type this does not appear to be a eqsl.adi file"

 


Re: Eqsl synchro problem

Bob
 

Silly question, but are there any QSO records in the file? SeventyThree(s).

On January 14, 2020 at 6:45 AM Panos <sv1grn@...> wrote:

Hi to all. I am using the latest version but when I try to synchronize I get the "no valid adif record found" message, . The file can be opened by adifmaster. Is there a solution? 73

The file header:
ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>

 


Re: Eqsl synchro problem

Marc-ON7SS-OO9O
 

No problem here and running also the latest version.

73  Marc, ON7SS - OO9O

Amateur Radio Station
ON7SS - OO9O

Marc Domen

http://www.on7ss.be


DM a.i. Antwerpen - 
https://www.uba.be

UBA HF Contest Manager -  https://www.uba.be

EPC Award Manager for BEPA and NLPA awards - https://www.eupsk.com/

30MDG Award Manager for ITU Zones and Prefix Awards - http://www.30mdg.org/

 

Only a boy and his radio

 

Op 14/01/2020 om 12:45 schreef Panos:

Hi to all. I am using the latest version but when I try to synchronize I get the "no valid adif record found" message, . The file can be opened by adifmaster. Is there a solution? 73

The file header:
ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>


Re: Eqsl synchro problem

Panos
 

Later, from adifmaster saved it as adi with other name, this time I get the "wrong file type this does not appear to be a eqsl.adi file"


Eqsl synchro problem

Panos
 

Hi to all. I am using the latest version but when I try to synchronize I get the "no valid adif record found" message, . The file can be opened by adifmaster. Is there a solution? 73

The file header:
ADIF 3 Export from eQSL.cc
Received eQSLs for SV1GRN 
for QSOs between 04-May-2004 and 04-May-2024 
Generated on Tuesday, January 14, 2020 at 11:02:35 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:5>3.1.0
<EOH>


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

ja1nlx
 

When you type W5IDX in Logbook entry window, do you see auto lookup window ?

and Name, State etc are populated in Logbook entry window ?

If so check "Log additional info from Logbook entry window" in Config/Logging option

in UDP BandMap. This is explained in the Logger32 Help. Look at paragraph 5.0 Menu

in the section "The UDP BandMap"

If not then setup Callsign lookup first. This is explained in the Logbook window/Callsign

lookup section in the Logger32 Help.


73

On 2020/01/14 13:04, Gregg E via Groups.Io wrote:
Bob or Anyone; how do you do this?  Is it in print somewhere?
I use the UDP setup to save the QSO into my logger file from WSJT but it only records the info from the WSJT screen. No auto Lookup.
Thanks
W5IDX



On Sunday, January 12, 2020, 09:10:38 AM CST, Bob <k4cy@...> wrote:


I have never downloaded an LoTW file, but I thought the state and some other fields were included in the record.

As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state.

And, FWIW, I'd recommend JTDX in preference to WSJT (fewer bugs and foibles, and much better receive sensitivity). SeventyThree(s).
On January 12, 2020 at 9:48 AM Marvin Stern <marbern@...> wrote:

When downloading LOTW received QSL's, how can Logger32 print state names in the State column instead of leaving it blank.
I'm mainly interested in files received from WSJT files which only contain grids, not names.
Marv, W2AOC

 
--
73 de aki
JA1NLX


Re: "As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Bob
 

I have just abandoned the football (no, the round ball type) final on TV, and am on my way to bed (in disgust). The results of tonight's game not withstanding, I have two disappointments in my life that I will never overcome - First is that my third wife wasn't a nymphomaniac she promised, and second is that the hamlogger reflector proves, many times a day, that one-way-skip is real (questions are frequent, answers are rare) ... So, who want's to prove me wrong and tell everyone what/where to click the mouse? SeventyThree(s).

On January 13, 2020 at 11:04 PM "Gregg E via Groups.Io" <w5idx@...> wrote:

 
Bob or Anyone; how do you do this?  Is it in print somewhere?
I use the UDP setup to save the QSO into my logger file from WSJT but it only records the info from the WSJT screen. No auto Lookup.
Thanks
W5IDX



On Sunday, January 12, 2020, 09:10:38 AM CST, Bob <k4cy@...> wrote:


I have never downloaded an LoTW file, but I thought the state and some other fields were included in the record.

As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state.

And, FWIW, I'd recommend JTDX in preference to WSJT (fewer bugs and foibles, and much better receive sensitivity). SeventyThree(s).
On January 12, 2020 at 9:48 AM Marvin Stern <marbern@...> wrote:

When downloading LOTW received QSL's, how can Logger32 print state names in the State column instead of leaving it blank.
I'm mainly interested in files received from WSJT files which only contain grids, not names.
Marv, W2AOC

 
 

 


"As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state."

Gregg E
 

Bob or Anyone; how do you do this?  Is it in print somewhere?
I use the UDP setup to save the QSO into my logger file from WSJT but it only records the info from the WSJT screen. No auto Lookup.
Thanks
W5IDX



On Sunday, January 12, 2020, 09:10:38 AM CST, Bob <k4cy@...> wrote:


I have never downloaded an LoTW file, but I thought the state and some other fields were included in the record.

As for WSJT files, if you load the QSOs in real-time using the UDP message interface, you can auto-look up the callsign and retrieve name and state.

And, FWIW, I'd recommend JTDX in preference to WSJT (fewer bugs and foibles, and much better receive sensitivity). SeventyThree(s).
On January 12, 2020 at 9:48 AM Marvin Stern <marbern@...> wrote:

When downloading LOTW received QSL's, how can Logger32 print state names in the State column instead of leaving it blank.
I'm mainly interested in files received from WSJT files which only contain grids, not names.
Marv, W2AOC

 


Re: Radio window weirdness

Bob
 

Probably because Logger32 is not talking to the radio when your operating FT4/FT8, so it doesn't know the radio is on USB. I'll make a change so that if you have enabled WSJT/JTDX to control Logger32 frequency/mode it will force the Radio Control Panel to USB. SeventyThree(s).

On January 13, 2020 at 1:01 PM Jim Altman <jaltman636@...> wrote:

In the radio control window, where you put your radio macro buttons, I just noticed that the spectrum display, while in FT8 (either JTDX or WSJT) has the frequency markers wrong.  The carrier frequency is on the left and instead of showing the frequencies numbers ascending as you go the right, they descend from the carrier frequency.  The spectrum wave for or waterfall is correct.  A tone at 1000 Hz is the second mark to the right, as it should be, but the numbers associated with it go down (as if on LSB) instead of up.  It is correct on SSB, whether upper or lower sideband.

 

73

 

Jim Altman

jaltman636@...

 


 

4321 - 4340 of 82896