Date   

Re: VUCC award is empty now

José L. Peña EA4AFP
 

Thanks Bob for the exe file !

It works, but the VUCC award reports 2 figures for worked/confirmed. The right one are 586/541.
I exported VUCC stats as ".csv" file and then import to openoffice calc, then I have checked that the csv file has the right information.

imagen.png
73 jose  EA4AFP



El lun., 25 may. 2020 a las 16:25, José L. Peña EA4AFP via groups.io (<ea4afp=gmail.com@groups.io>) escribió:
Bob,

I have a spare PC running also L32. Before a contest I synchronize both of them, so in case of a failure I can switch easily and continue operating seamless. This is what I have done in the spare PC:
  1. - copy all the files zipped at "logger32backup" and "logbookbackup_full05" of the standard PC to L32 directory at the spare PC.
  2. - full05 has been chosen because it is dated yesterday. "Numbers" above 5 have been generated today during tests.
  3. - spare PC:
    • start L32 and update to v416
    • recalculate statistics
    • awards, DXCC: everything seems to be OK.
    • awards, VUCC: statistics does not match with the amount of grids worked and confirmed on 6 meters. Even for 2018 there is a mismatch between figures reported.
    • imagen.png

imagen.png

  • rolled back spare PC to v415 and statistics for VUCC and DXCC are OK
imagen.png


standard PC:
  • rolled back to v415 in the standard PC and statistics are fine for VUCC and DXCC.
Do not know what it is broken, but it is related only to VUCC award. DXCC is always reporting fine. Even, as explained before, the 6 meters UDP bandmap is aware of the grids worked and confirmed. It does not highlight already confirmed grids/entities on 6.

Hope this explains the issue.

73  jose  EA4AFP





El lun., 25 may. 2020 a las 14:26, Bob (<k4cy@...>) escribió:
Jose, calling me 'silly' is very polite, most users use four letter Anglo Saxon explicatives.

You tried to recover version 416 zip files and failed? What were you trying to do, and why? What failed, what error did you get? SeventyThree(s).
On May 25, 2020 at 7:55 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Bob, those understanding Spanish...

fat fingers and an extra "o" was added to Bob's name, changing it to a Spanish word meaning "silly".

Sorry Bob !!!

Rolled back to v415 and everything is Ok. Generated a complete ADIF file (just in case). Updated to v416 an again failed. I zip "user files" and "database and logbook" every time I log off, so tried to recover v416 with files zipped yesterday. Still failing.

Any clue?

73 jose   EA4AFP

El lun., 25 may. 2020 a las 13:24, José L. Peña EA4AFP via groups.io (<ea4afp= gmail.com@groups.io>) escribió:

Thanks Bobo,
yes, added a new QSO with myself, and now I can see strange results, the "complete logbook" has less grids worked than "2019".

73  jose  EA4AFP

imagen.png
imagen.png


El lun., 25 may. 2020 a las 13:10, Bob (< k4cy@...>) escribió:
Looks like it is broken. SeventyThree(s).
On May 25, 2020 at 6:47 AM "José L. Peña EA4AFP" < ea4afp@...> wrote:

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


 

 

 

 

 


 


Re: Error in the STATE field

IZ5ILJ Lenio
 

Ciao Bob tnx so much, is solved also this problem,

73's, Lenio - IZ5ILJ - #69.

Il 25/05/2020 15:57, Bob ha scritto:
Maybe Logger32 does not know about a STATE of CB in Asiatic Russia. Click TOOLS | DATABASE MAINTENANCE | PRIMARY ADMINISTRATION MAINTENANCE. On the Window that opens, choose Asiatic Russia as the Country. Do you see Chelyabinskaya Oblast a CB? If not, ask a friend with Logger32 to export a CSV file of Asiatic Russia Primary Admin subdivisions for you to import (see the import/export option at the bottom right of the window.

Logger32 will not allow you to import QSOs with a STATE field that it can not verify as being valid. SeventyThree(s).


On May 25, 2020 at 9:40 AM IZ5ILJ Lenio <iz5ilj@...> wrote:


Hi Bob and guys, I've solved the problem of "Frequency does not appear
to be in the 20M Band:" but now I've one of "Error in the STATE field",
like this, and really I'vent any idea how to solve it.

Error in the STATE field:  <DISTANCE:3>0.0 <BAND:3>10M <CALL:4>RG9A
<CONT:2>AS <CONTEST_ID:17>ARI International <CQZ:2>17 <DXCC:2>15
<FREQ:9>28.509940 <GRIDSQUARE:6>MO04ew <ITUZ:2>30 <MODE:3>SSB
<OPERATOR:6>IZ5ILJ <PFX:3>RG9 <QSL_SENT:1>Y <QSLSDATE:8>20190701
<QSO_DATE:8:D>20140504 <TIME_ON:6>090200 <RST_RCVD:2>59 <RST_SENT:2>59
<SRX:4>1857 <STATE:2>CB <TIME_OFF:6>090200 <eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:4>7680 <COUNTRY:14>Asiatic Russia
<APP_LOGGER32_LAT:7>54.9375 <APP_LOGGER32_LNG:7>-60.375
<STATION_CALLSIGN:6>IZ5ILJ <EOR>

Tnx in advance, 73's, Lenio - IZ5ILJ - #69.





Re: VUCC award is empty now

José L. Peña EA4AFP
 

Bob,

I have a spare PC running also L32. Before a contest I synchronize both of them, so in case of a failure I can switch easily and continue operating seamless. This is what I have done in the spare PC:
  1. - copy all the files zipped at "logger32backup" and "logbookbackup_full05" of the standard PC to L32 directory at the spare PC.
  2. - full05 has been chosen because it is dated yesterday. "Numbers" above 5 have been generated today during tests.
  3. - spare PC:
    • start L32 and update to v416
    • recalculate statistics
    • awards, DXCC: everything seems to be OK.
    • awards, VUCC: statistics does not match with the amount of grids worked and confirmed on 6 meters. Even for 2018 there is a mismatch between figures reported.
    • imagen.png

imagen.png

  • rolled back spare PC to v415 and statistics for VUCC and DXCC are OK
imagen.png


standard PC:
  • rolled back to v415 in the standard PC and statistics are fine for VUCC and DXCC.
Do not know what it is broken, but it is related only to VUCC award. DXCC is always reporting fine. Even, as explained before, the 6 meters UDP bandmap is aware of the grids worked and confirmed. It does not highlight already confirmed grids/entities on 6.

Hope this explains the issue.

73  jose  EA4AFP





El lun., 25 may. 2020 a las 14:26, Bob (<k4cy@...>) escribió:
Jose, calling me 'silly' is very polite, most users use four letter Anglo Saxon explicatives.

You tried to recover version 416 zip files and failed? What were you trying to do, and why? What failed, what error did you get? SeventyThree(s).
On May 25, 2020 at 7:55 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Bob, those understanding Spanish...

fat fingers and an extra "o" was added to Bob's name, changing it to a Spanish word meaning "silly".

Sorry Bob !!!

Rolled back to v415 and everything is Ok. Generated a complete ADIF file (just in case). Updated to v416 an again failed. I zip "user files" and "database and logbook" every time I log off, so tried to recover v416 with files zipped yesterday. Still failing.

Any clue?

73 jose   EA4AFP

El lun., 25 may. 2020 a las 13:24, José L. Peña EA4AFP via groups.io (<ea4afp= gmail.com@groups.io>) escribió:

Thanks Bobo,
yes, added a new QSO with myself, and now I can see strange results, the "complete logbook" has less grids worked than "2019".

73  jose  EA4AFP

imagen.png
imagen.png


El lun., 25 may. 2020 a las 13:10, Bob (< k4cy@...>) escribió:
Looks like it is broken. SeventyThree(s).
On May 25, 2020 at 6:47 AM "José L. Peña EA4AFP" < ea4afp@...> wrote:

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


 

 

 

 

 


 


Re: Error in the STATE field

Bob
 

Maybe Logger32 does not know about a STATE of CB in Asiatic Russia. Click TOOLS | DATABASE MAINTENANCE | PRIMARY ADMINISTRATION MAINTENANCE. On the Window that opens, choose Asiatic Russia as the Country. Do you see Chelyabinskaya Oblast a CB? If not, ask a friend with Logger32 to export a CSV file of Asiatic Russia Primary Admin subdivisions for you to import (see the import/export option at the bottom right of the window.

Logger32 will not allow you to import QSOs with a STATE field that it can not verify as being valid. SeventyThree(s).

On May 25, 2020 at 9:40 AM IZ5ILJ Lenio <iz5ilj@...> wrote:


Hi Bob and guys, I've solved the problem of "Frequency does not appear
to be in the 20M Band:" but now I've one of "Error in the STATE field",
like this, and really I'vent any idea how to solve it.

Error in the STATE field:  <DISTANCE:3>0.0 <BAND:3>10M <CALL:4>RG9A
<CONT:2>AS <CONTEST_ID:17>ARI International <CQZ:2>17 <DXCC:2>15
<FREQ:9>28.509940 <GRIDSQUARE:6>MO04ew <ITUZ:2>30 <MODE:3>SSB
<OPERATOR:6>IZ5ILJ <PFX:3>RG9 <QSL_SENT:1>Y <QSLSDATE:8>20190701
<QSO_DATE:8:D>20140504 <TIME_ON:6>090200 <RST_RCVD:2>59 <RST_SENT:2>59
<SRX:4>1857 <STATE:2>CB <TIME_OFF:6>090200 <eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:4>7680 <COUNTRY:14>Asiatic Russia
<APP_LOGGER32_LAT:7>54.9375 <APP_LOGGER32_LNG:7>-60.375
<STATION_CALLSIGN:6>IZ5ILJ <EOR>

Tnx in advance, 73's, Lenio - IZ5ILJ - #69.





Error in the STATE field

IZ5ILJ Lenio
 

Hi Bob and guys, I've solved the problem of "Frequency does not appear to be in the 20M Band:" but now I've one of "Error in the STATE field", like this, and really I'vent any idea how to solve it.

Error in the STATE field:  <DISTANCE:3>0.0 <BAND:3>10M <CALL:4>RG9A <CONT:2>AS <CONTEST_ID:17>ARI International <CQZ:2>17 <DXCC:2>15 <FREQ:9>28.509940 <GRIDSQUARE:6>MO04ew <ITUZ:2>30 <MODE:3>SSB <OPERATOR:6>IZ5ILJ <PFX:3>RG9 <QSL_SENT:1>Y <QSLSDATE:8>20190701 <QSO_DATE:8:D>20140504 <TIME_ON:6>090200 <RST_RCVD:2>59 <RST_SENT:2>59 <SRX:4>1857 <STATE:2>CB <TIME_OFF:6>090200 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:4>7680 <COUNTRY:14>Asiatic Russia <APP_LOGGER32_LAT:7>54.9375 <APP_LOGGER32_LNG:7>-60.375 <STATION_CALLSIGN:6>IZ5ILJ <EOR>

Tnx in advance, 73's, Lenio - IZ5ILJ - #69.


Re: VUCC award is empty now

Bob
 

Jose, calling me 'silly' is very polite, most users use four letter Anglo Saxon explicatives.

You tried to recover version 416 zip files and failed? What were you trying to do, and why? What failed, what error did you get? SeventyThree(s).

On May 25, 2020 at 7:55 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Bob, those understanding Spanish...

fat fingers and an extra "o" was added to Bob's name, changing it to a Spanish word meaning "silly".

Sorry Bob !!!

Rolled back to v415 and everything is Ok. Generated a complete ADIF file (just in case). Updated to v416 an again failed. I zip "user files" and "database and logbook" every time I log off, so tried to recover v416 with files zipped yesterday. Still failing.

Any clue?

73 jose   EA4AFP

El lun., 25 may. 2020 a las 13:24, José L. Peña EA4AFP via groups.io (<ea4afp= gmail.com@groups.io>) escribió:

Thanks Bobo,
yes, added a new QSO with myself, and now I can see strange results, the "complete logbook" has less grids worked than "2019".

73  jose  EA4AFP

imagen.png
imagen.png


El lun., 25 may. 2020 a las 13:10, Bob (< k4cy@...>) escribió:
Looks like it is broken. SeventyThree(s).
On May 25, 2020 at 6:47 AM "José L. Peña EA4AFP" < ea4afp@...> wrote:

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


 

 

 

 

 


 


Re: VUCC award is empty now

Jan
 

Jose
If you send him a bottle of Famous Grouse (whiskey) he will do what ever you want and never become mad about you. :-):-D

73
Jan
PA4JJ

Op 25-5-2020 om 13:55 schreef José L. Peña EA4AFP:
Bob, those understanding Spanish...

fat fingers and an extra "o" was added to Bob's name, changing it to a Spanish word meaning "silly".

Sorry Bob !!!

Rolled back to v415 and everything is Ok. Generated a complete ADIF file (just in case). Updated to v416 an again failed. I zip "user files" and "database and logbook" every time I log off, so tried to recover v416 with files zipped yesterday. Still failing.

Any clue?

73 jose   EA4AFP

El lun., 25 may. 2020 a las 13:24, José L. Peña EA4AFP via groups.io (<ea4afp=gmail.com@groups.io>) escribió:

Thanks Bobo,
yes, added a new QSO with myself, and now I can see strange results, the "complete logbook" has less grids worked than "2019".

73  jose  EA4AFP

imagen.png
imagen.png


El lun., 25 may. 2020 a las 13:10, Bob (<k4cy@...>) escribió:
Looks like it is broken. SeventyThree(s).
On May 25, 2020 at 6:47 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


 

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: Latest Update disabled "on top" option on UDP socket window !

Damian M0BKV
 

Thanks Bob for putting the UDP Band plan always on top  option in the UDP Bandplan Configuration settings. So now you can have it on top of WSJD-x if you want


Re: VUCC award is empty now

José L. Peña EA4AFP
 

Bob, those understanding Spanish...

fat fingers and an extra "o" was added to Bob's name, changing it to a Spanish word meaning "silly".

Sorry Bob !!!

Rolled back to v415 and everything is Ok. Generated a complete ADIF file (just in case). Updated to v416 an again failed. I zip "user files" and "database and logbook" every time I log off, so tried to recover v416 with files zipped yesterday. Still failing.

Any clue?

73 jose   EA4AFP


El lun., 25 may. 2020 a las 13:24, José L. Peña EA4AFP via groups.io (<ea4afp=gmail.com@groups.io>) escribió:

Thanks Bobo,
yes, added a new QSO with myself, and now I can see strange results, the "complete logbook" has less grids worked than "2019".

73  jose  EA4AFP

imagen.png
imagen.png


El lun., 25 may. 2020 a las 13:10, Bob (<k4cy@...>) escribió:
Looks like it is broken. SeventyThree(s).
On May 25, 2020 at 6:47 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


 


Re: VUCC award is empty now

José L. Peña EA4AFP
 


Thanks Bobo,
yes, added a new QSO with myself, and now I can see strange results, the "complete logbook" has less grids worked than "2019".

73  jose  EA4AFP

imagen.png
imagen.png


El lun., 25 may. 2020 a las 13:10, Bob (<k4cy@...>) escribió:
Looks like it is broken. SeventyThree(s).
On May 25, 2020 at 6:47 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


 


Re: VUCC award is empty now

Bob
 

Looks like it is broken. SeventyThree(s).

On May 25, 2020 at 6:47 AM "José L. Peña EA4AFP" <ea4afp@...> wrote:

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


 


VUCC award is empty now

José L. Peña EA4AFP
 

Hi all,

updated to 3.50.416 this morning, then updated some QSLs received through LoTW, tried to check VUCC award status and now it is empty. Neither grids worked nor grids comfirmed, the award status does not show any info.
The funny thing is the behaviour of the UDP bandmap. It is configured to highlight new entities on 6m and non-confirmed grids on 6 and it is working. The UDP bandmap is "aware" of the grid status.
Stats have been recalculated and the program restated.
Any clue?

73 de jose  Ea4AFP

imagen.png


Re: Latest Update disabled "on top" option on UDP socket window !

Bob
 

Do you mean the UDP BandMap?  It is fixed as application on-top (it always shows on-top of the main Logger32 window (just like all the BandMaps). It has an additional option that allows the user to set is as system on-top (it shows on-top of all applications). SeventyThree(s).

On May 25, 2020 at 5:33 AM Pedro P <ct1elp@...> wrote:

Hello !

The latest update done this morning has made some change in the software that I cannot prevent the WSJT/JTDX UDP socket window to remain "on top".
Or is there a new way to change it ?
I have gone to the Start->Setup Shortcuts and disable the mark on the "on top" windows but it remains on top.
Any suggestion appreciated.
Thanks
 
73 de CT1ELP
Pedro Pedroso
----------------------------------------
http://ppedroso.planetaclix.pt
----------------------------------------

 


Re: Misalignment of alternative row color

Ken JN7FAH
 

This problem has been fixed in Ver. 3.50.416.
Thanks Bob
73 Ken JN7FAH
image.png


2020年5月21日(木) 23:16 Ken JN7FAH via groups.io <jn7fah=gmail.com@groups.io>:

I just happened to discover this misalignment on the
DXCC challenge table.

image.png
Ken JN7FAH


Re: problem to export and import adif log

IZ5ILJ Lenio
 

Hi Bob and John,

tnx so much, problem solved, I had assumed that the problem was in the band and modes but I could not understand the reason, now it is all clear,

73's, Lenio - IZ5ILJ - #69.
Il 25/05/2020 11:52, John Munton - G7SSE ha scritto:

Lenio
Check that these frequencies are within the entries you have made in your Band/Mode Table.
73
John - G7SSE

------ Original Message ------
From: "IZ5ILJ Lenio" <iz5ilj@...>
Sent: 25/05/2020 10:42:54
Subject: [hamlogger] problem to export and import adif log

Hi Bob and all, if I exported a log from Logger32 and imported the same, after clearing the log, I've many of this errors and I can't import many qsos.
 


Re: problem to export and import adif log

Bob
 

... Click on TOOLS | SETUP BANDS & MODES. Do you have 14.077 MHz somewhere in your BandPlan? SeventyThree(s).

On May 25, 2020 at 5:42 AM IZ5ILJ Lenio <iz5ilj@...> wrote:


Hi Bob and all, if I exported a log from Logger32 and imported the same,
after clearing the log, I've many of this errors and I can't import many
qsos.

This is an example:

Error : Frequency does not appear to be in the 20M Band: <DISTANCE:3>0.0
<BAND:3>20M <CALL:4>W3PT <CONT:2>NA <CQZ:1>5 <DXCC:3>291
<FREQ:9>14.077000 <GRIDSQUARE:6>FM18lv <ITUZ:1>8 <MODE:4>RTTY <NOTES:1>B
<OPERATOR:6>IZ5ILJ <PFX:2>W3 <QSL_SENT:1>Y <QSLSDATE:8>20190701
<QSO_DATE:8:D>20060902 <TIME_ON:6>185200 <RST_RCVD:2>59 <RST_SENT:2>59
<RX_PWR:3>0.0 <K_INDEX:3>0.0 <TIME_OFF:6>185200 <TX_PWR:3>0.0 <SFI:3>0.0
<A_INDEX:3>0.0 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y
<APP_LOGGER32_QSO_NUMBER:2>55 <COUNTRY:3>USA
<APP_LOGGER32_LAT:16>38.8958333333333
<APP_LOGGER32_LNG:16>77.0416666666667 <STATION_CALLSIGN:6>IZ5ILJ <EOR>

Error : Frequency does not appear to be in the 15M Band: <DISTANCE:3>0.0
<BAND:3>15M <CALL:5>TT8FC <CONT:2>AF <CQZ:2>36 <DXCC:3>410
<FREQ:9>21.180000 <GRIDSQUARE:6>JK72mc <ITUZ:2>47 <MODE:3>SSB <NOTES:1>D
<OPERATOR:6>IZ5ILJ <PFX:3>TT8 <QSL_RCVD:1>Y <QSL_SENT:1>Y
<QSL_VIA:6>EA4AHK <QSLRDATE:8>20080616 <QSLSDATE:8>20190701
<QSO_DATE:8:D>20060926 <TIME_ON:6>171700 <RST_RCVD:2>59 <RST_SENT:2>59
<RX_PWR:3>0.0 <K_INDEX:3>0.0 <TIME_OFF:6>171700 <TX_PWR:3>0.0 <SFI:3>0.0
<A_INDEX:3>0.0 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y
<APP_LOGGER32_QSO_NUMBER:2>71 <COUNTRY:4>Chad
<APP_LOGGER32_LAT:16>12.1041666666667
<APP_LOGGER32_LNG:17>-15.0416666666667 <STATION_CALLSIGN:6>IZ5ILJ <EOR>

The frequency 14.077000 not is on 20M band or 21.180000 in 15M band?

I think I have some wrong settings but I can't understand which.

Tnx in advance, 73's, Lenio - IZ5ILJ - #69.





Re: problem to export and import adif log

John Munton - G7SSE
 

Lenio

Check that these frequencies are within the entries you have made in your Band/Mode Table.

73
John - G7SSE

------ Original Message ------
From: "IZ5ILJ Lenio" <iz5ilj@...>
Sent: 25/05/2020 10:42:54
Subject: [hamlogger] problem to export and import adif log

Hi Bob and all, if I exported a log from Logger32 and imported the same, after clearing the log, I've many of this errors and I can't import many qsos.
 
This is an example:
 
Error : Frequency does not appear to be in the 20M Band: <DISTANCE:3>0.0 <BAND:3>20M <CALL:4>W3PT <CONT:2>NA <CQZ:1>5 <DXCC:3>291 <FREQ:9>14.077000 <GRIDSQUARE:6>FM18lv <ITUZ:1>8 <MODE:4>RTTY <NOTES:1>B <OPERATOR:6>IZ5ILJ <PFX:2>W3 <QSL_SENT:1>Y <QSLSDATE:8>20190701 <QSO_DATE:8:D>20060902 <TIME_ON:6>185200 <RST_RCVD:2>59 <RST_SENT:2>59 <RX_PWR:3>0.0 <K_INDEX:3>0.0 <TIME_OFF:6>185200 <TX_PWR:3>0.0 <SFI:3>0.0 <A_INDEX:3>0.0 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:2>55 <COUNTRY:3>USA <APP_LOGGER32_LAT:16>38.8958333333333 <APP_LOGGER32_LNG:16>77.0416666666667 <STATION_CALLSIGN:6>IZ5ILJ <EOR>
 
Error : Frequency does not appear to be in the 15M Band: <DISTANCE:3>0.0 <BAND:3>15M <CALL:5>TT8FC <CONT:2>AF <CQZ:2>36 <DXCC:3>410 <FREQ:9>21.180000 <GRIDSQUARE:6>JK72mc <ITUZ:2>47 <MODE:3>SSB <NOTES:1>D <OPERATOR:6>IZ5ILJ <PFX:3>TT8 <QSL_RCVD:1>Y <QSL_SENT:1>Y <QSL_VIA:6>EA4AHK <QSLRDATE:8>20080616 <QSLSDATE:8>20190701 <QSO_DATE:8:D>20060926 <TIME_ON:6>171700 <RST_RCVD:2>59 <RST_SENT:2>59 <RX_PWR:3>0.0 <K_INDEX:3>0.0 <TIME_OFF:6>171700 <TX_PWR:3>0.0 <SFI:3>0.0 <A_INDEX:3>0.0 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:2>71 <COUNTRY:4>Chad <APP_LOGGER32_LAT:16>12.1041666666667 <APP_LOGGER32_LNG:17>-15.0416666666667 <STATION_CALLSIGN:6>IZ5ILJ <EOR>
 
The frequency 14.077000 not is on 20M band or 21.180000 in 15M band?
 
I think I have some wrong settings but I can't understand which.
 
Tnx in advance, 73's, Lenio - IZ5ILJ - #69.
 
 
 
 

--
73, John - G7SSE


problem to export and import adif log

IZ5ILJ Lenio
 

Hi Bob and all, if I exported a log from Logger32 and imported the same, after clearing the log, I've many of this errors and I can't import many qsos.

This is an example:

Error : Frequency does not appear to be in the 20M Band: <DISTANCE:3>0.0 <BAND:3>20M <CALL:4>W3PT <CONT:2>NA <CQZ:1>5 <DXCC:3>291 <FREQ:9>14.077000 <GRIDSQUARE:6>FM18lv <ITUZ:1>8 <MODE:4>RTTY <NOTES:1>B <OPERATOR:6>IZ5ILJ <PFX:2>W3 <QSL_SENT:1>Y <QSLSDATE:8>20190701 <QSO_DATE:8:D>20060902 <TIME_ON:6>185200 <RST_RCVD:2>59 <RST_SENT:2>59 <RX_PWR:3>0.0 <K_INDEX:3>0.0 <TIME_OFF:6>185200 <TX_PWR:3>0.0 <SFI:3>0.0 <A_INDEX:3>0.0 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:2>55 <COUNTRY:3>USA <APP_LOGGER32_LAT:16>38.8958333333333 <APP_LOGGER32_LNG:16>77.0416666666667 <STATION_CALLSIGN:6>IZ5ILJ <EOR>

Error : Frequency does not appear to be in the 15M Band: <DISTANCE:3>0.0 <BAND:3>15M <CALL:5>TT8FC <CONT:2>AF <CQZ:2>36 <DXCC:3>410 <FREQ:9>21.180000 <GRIDSQUARE:6>JK72mc <ITUZ:2>47 <MODE:3>SSB <NOTES:1>D <OPERATOR:6>IZ5ILJ <PFX:3>TT8 <QSL_RCVD:1>Y <QSL_SENT:1>Y <QSL_VIA:6>EA4AHK <QSLRDATE:8>20080616 <QSLSDATE:8>20190701 <QSO_DATE:8:D>20060926 <TIME_ON:6>171700 <RST_RCVD:2>59 <RST_SENT:2>59 <RX_PWR:3>0.0 <K_INDEX:3>0.0 <TIME_OFF:6>171700 <TX_PWR:3>0.0 <SFI:3>0.0 <A_INDEX:3>0.0 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:2>71 <COUNTRY:4>Chad <APP_LOGGER32_LAT:16>12.1041666666667 <APP_LOGGER32_LNG:17>-15.0416666666667 <STATION_CALLSIGN:6>IZ5ILJ <EOR>

The frequency 14.077000 not is on 20M band or 21.180000 in 15M band?

I think I have some wrong settings but I can't understand which.

Tnx in advance, 73's, Lenio - IZ5ILJ - #69.


Latest Update disabled "on top" option on UDP socket window !

Pedro P
 

Hello !

The latest update done this morning has made some change in the software that I cannot prevent the WSJT/JTDX UDP socket window to remain "on top".
Or is there a new way to change it ?
I have gone to the Start->Setup Shortcuts and disable the mark on the "on top" windows but it remains on top.
Any suggestion appreciated.
Thanks
 
73 de CT1ELP
Pedro Pedroso
----------------------------------------
http://ppedroso.planetaclix.pt
----------------------------------------


Re: Uploading (partial) log to LOTW

Bob
 

Axel, the error message tells me (no need for you to understand it) that you were had imported an ADIF record and were trying to write it to your logbook. Logger32 checks the imported records very carefully to make sure they are correct. In this case, it looks like everything passed the checks, but Logger32 would still not allow you to write the record into your logbook. Something is very wrong, and it is trying to bedecke deinen arsch. So, the question is, what ADIF file/record were you trying to import, an where did it come from? Please zip it and send it to me at <k4cy@...>. SeventyThree(s).

On May 24, 2020 at 5:58 PM Axel <dl3zh@...> wrote:

Thanks Jim for your help!
I tried to follow the steps described in paragraph 1.13, but I got stuck, when I wanted to re-import the previously exported ADIF logfile.

When I finally clicked on the start button of the Import ADIF Log-Window, I received the following error message (see attachment).
I could not get rid of this error message than asking the task manager to stop the L32 app.
I have no idea what this error message means.

Tnx es 73 de Axel, DL3ZH