Bonjour AKI,
je viens de faire exactement ce que vous m'avez indiqué ... cela fonction bien ...
on ""SEND LOTW QSL""???the check mark is well removed? and on """LOTW QSL SENT ""?The check mark is present?
thank you AKI for your help
F5JVP Didier
------ Message d'origine ------
Date 01/11/2024 10:04:08
Objet Re: [hamlogger] Hawaii
Didier
I think you are using LogSync utility to upload to LoTW. If so, stop LogSync utility temporally. In Logger32 main menu, Click File/Export files/Export LoTW file. When you have this window, click Yes.
Do you see LoTW QSL Send is unchecked and LoTW QSL Sent is checked ?
On 2024-11-01 金曜日 17:45:59, DIDIER DIENNE via groups.io <f5jvp@...> wrote: Hello
Maybe I can give you more explanation, to understand where the problem is....
See below for an example.
I use LOTW with LOGGER32.
F5JVP Didier DIENNE wINDOW 11 Version 23H2 Tqsl Verstion V2.3.1 PC I7-11700 32GO 64Bits
In the logger32 settings, I indicated that I wanted to? ? ? - automatic? download (this works normally) and that? ? ? -I wanted the flags after loading (? it doesn't work )
Sample:
my QSO? in Logger32
configurtion de Logger32: auto Upload and flag Logger32 after Upload
in fact we can see
The "  " sign placed in front of the 6th? should be removed and The "  " sign should be placed in front of the 9th line?
exactly like the information from E-QSL
si l'on regarde LOTW
we can see that LOTW did record the QSO but did not give the order to modify the?  ?in logger32
With thanks F5JVP Didier
------ Message d'origine ------
Date 01/11/2024 05:58:46
Objet Re: [hamlogger] Hawaii
I have not figured that one out yet. Need more time to try and
see whats going on..
73 Rick N2AMG
On 10/31/2024 5:36 PM, DIDIER DIENNE
wrote:
why are my QSOs not flagged on?''''confirmation
envoyée avec Lotw''''
MERCI
------ Message d'origine ------
Date 31/10/2024 22:30:49
Objet Re: [hamlogger] Hawaii
Understood. There is
abundant evidence that the station is/was in Hawaii - CQ
Zone, Continent, and Prefix. I'm still narrowing down the
possibilities as to why Logger32 rejected HI as the STATE
for a station in Hawaii. What Country it was logged as is
one of them. SeventyThree(s).
?
?
When N1MM exports qso's the DXCC field is never
included.? N1MM figures where ever it is imported to will
figure it out..
73 Rick n2AMG
On 10/31/2024 5:17 PM, Bob via
groups.io wrote:
I notice there is
no DXCC field in the ADIF record. Is the QSO logged
with the DXCC of 291 or 110? SeventyThree(s).
?
?
Bob, good
evening...
I am very sorry, was my mistake about deleting
BAD.adi file.
Of course I could show you, really, I have no
problems with?
public logs (I
am finally doing LoTW today, for the first time
).
I am trying to
recover from?"deleted files".
?
Logger32 (Version
4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif
corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW
<QSO_DATE:8>20231210 <TIME_ON:6>233226
<TIME_OFF:6>233226 <STATE:2>HI
<BAND:3>10M <STATION_CALLSIGN:5>PY2NY
<FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10
<FREQ_RX:8>28.40730 <MODE:3>SSB
<RST_RCVD:2>59 <RST_SENT:2>59
<TX_PWR:3>100 <OPERATOR:5>PY2NY
<CQZ:2>31 <STX:4>1276
<APP_N1MM_POINTS:1>0
<APP_N1MM_RADIO_NR:1>1
<APP_N1MM_CONTINENT:2>OC
<APP_N1MM_RUN1RUN2:1>1
<APP_N1MM_RADIOINTERFACED:1>1
<APP_N1MM_ISORIGINAL:4>True
<APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF
<APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6
<APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0
<APP_N1MM_MULT3:1>0
<APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2
<APP_N1MM_CLAIMEDQSO:1>1
<APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis
Aidar dos Santos
?
If you
won't show me the ADIF record for the KH6KW
contact, will you at least tell me what the
DXCC field was? SeventyThree(s).
?
?
Thanks
Bob
I got BAD file,
made STATE blank for HI?(KH6KW) from the
file, and changed XE2X
TAM province to
TMS. That was enough to import those missed
3 QSOs into my
Logger32.
Now, I am just
preparing another message about "EDIT"
function.
Thanks a thousand
times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? -
Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly,
the ADIF record will be in the BAD.ADI
file. Please copy/past the record here.
SeventyThree(s).
?
?
Good
morning
I did my research
in the logger32 archive and even the
1000 pages
manual. Can't
import STATE [HI] from ADIF
generated by N1MM.
I solved?problem
with NF changing to NL. But what to
do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY /
V26NY? - Vitor Luis
Aidar dos Santos
?
?
?
?
?
?
|
Didier
I think you are using LogSync utility to upload to LoTW. If so, stop LogSync utility temporally. In Logger32 main menu, Click File/Export files/Export LoTW file. When you have this window, click Yes.
Do you see LoTW QSL Send is unchecked and LoTW QSL Sent is checked ?
On 2024-11-01 金曜日 17:45:59, DIDIER DIENNE via groups.io <f5jvp@...> wrote: Hello
Maybe I can give you more explanation, to understand where the problem is....
See below for an example.
I use LOTW with LOGGER32.
F5JVP Didier DIENNE wINDOW 11 Version 23H2 Tqsl Verstion V2.3.1 PC I7-11700 32GO 64Bits
In the logger32 settings, I indicated that I wanted to? ? ? - automatic? download (this works normally) and that? ? ? -I wanted the flags after loading (? it doesn't work )
Sample:
my QSO? in Logger32
configurtion de Logger32: auto Upload and flag Logger32 after Upload
in fact we can see
The "  " sign placed in front of the 6th? should be removed and The "  " sign should be placed in front of the 9th line?
exactly like the information from E-QSL
si l'on regarde LOTW
we can see that LOTW did record the QSO but did not give the order to modify the?  ?in logger32
With thanks F5JVP Didier
------ Message d'origine ------
Date 01/11/2024 05:58:46
Objet Re: [hamlogger] Hawaii
I have not figured that one out yet. Need more time to try and
see whats going on..
73 Rick N2AMG
On 10/31/2024 5:36 PM, DIDIER DIENNE
wrote:
why are my QSOs not flagged on?''''confirmation
envoyée avec Lotw''''
MERCI
------ Message d'origine ------
Date 31/10/2024 22:30:49
Objet Re: [hamlogger] Hawaii
Understood. There is
abundant evidence that the station is/was in Hawaii - CQ
Zone, Continent, and Prefix. I'm still narrowing down the
possibilities as to why Logger32 rejected HI as the STATE
for a station in Hawaii. What Country it was logged as is
one of them. SeventyThree(s).
?
?
When N1MM exports qso's the DXCC field is never
included.? N1MM figures where ever it is imported to will
figure it out..
73 Rick n2AMG
On 10/31/2024 5:17 PM, Bob via
groups.io wrote:
I notice there is
no DXCC field in the ADIF record. Is the QSO logged
with the DXCC of 291 or 110? SeventyThree(s).
?
?
Bob, good
evening...
I am very sorry, was my mistake about deleting
BAD.adi file.
Of course I could show you, really, I have no
problems with?
public logs (I
am finally doing LoTW today, for the first time
).
I am trying to
recover from?"deleted files".
?
Logger32 (Version
4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif
corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW
<QSO_DATE:8>20231210 <TIME_ON:6>233226
<TIME_OFF:6>233226 <STATE:2>HI
<BAND:3>10M <STATION_CALLSIGN:5>PY2NY
<FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10
<FREQ_RX:8>28.40730 <MODE:3>SSB
<RST_RCVD:2>59 <RST_SENT:2>59
<TX_PWR:3>100 <OPERATOR:5>PY2NY
<CQZ:2>31 <STX:4>1276
<APP_N1MM_POINTS:1>0
<APP_N1MM_RADIO_NR:1>1
<APP_N1MM_CONTINENT:2>OC
<APP_N1MM_RUN1RUN2:1>1
<APP_N1MM_RADIOINTERFACED:1>1
<APP_N1MM_ISORIGINAL:4>True
<APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF
<APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6
<APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0
<APP_N1MM_MULT3:1>0
<APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2
<APP_N1MM_CLAIMEDQSO:1>1
<APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis
Aidar dos Santos
?
If you
won't show me the ADIF record for the KH6KW
contact, will you at least tell me what the
DXCC field was? SeventyThree(s).
?
?
Thanks
Bob
I got BAD file,
made STATE blank for HI?(KH6KW) from the
file, and changed XE2X
TAM province to
TMS. That was enough to import those missed
3 QSOs into my
Logger32.
Now, I am just
preparing another message about "EDIT"
function.
Thanks a thousand
times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? -
Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly,
the ADIF record will be in the BAD.ADI
file. Please copy/past the record here.
SeventyThree(s).
?
?
Good
morning
I did my research
in the logger32 archive and even the
1000 pages
manual. Can't
import STATE [HI] from ADIF
generated by N1MM.
I solved?problem
with NF changing to NL. But what to
do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY /
V26NY? - Vitor Luis
Aidar dos Santos
?
?
?
?
?
?
|
Hello
Maybe I can give you more explanation, to understand where the problem is....
See below for an example.
I use LOTW with LOGGER32.
F5JVP Didier DIENNE wINDOW 11 Version 23H2 Tqsl Verstion V2.3.1 PC I7-11700 32GO 64Bits
In the logger32 settings, I indicated that I wanted to? ? ? - automatic? download (this works normally) and that? ? ? -I wanted the flags after loading (? it doesn't work )
Sample:
my QSO? in Logger32
configurtion de Logger32: auto Upload and flag Logger32 after Upload
in fact we can see
The "  " sign placed in front of the 6th? should be removed and The "  " sign should be placed in front of the 9th line?
exactly like the information from E-QSL
si l'on regarde LOTW
we can see that LOTW did record the QSO but did not give the order to modify the?  ?in logger32
With thanks F5JVP Didier
------ Message d'origine ------
Date 01/11/2024 05:58:46
Objet Re: [hamlogger] Hawaii
I have not figured that one out yet. Need more time to try and
see whats going on..
73 Rick N2AMG
On 10/31/2024 5:36 PM, DIDIER DIENNE
wrote:
why are my QSOs not flagged on?''''confirmation
envoyée avec Lotw''''
MERCI
------ Message d'origine ------
Date 31/10/2024 22:30:49
Objet Re: [hamlogger] Hawaii
Understood. There is
abundant evidence that the station is/was in Hawaii - CQ
Zone, Continent, and Prefix. I'm still narrowing down the
possibilities as to why Logger32 rejected HI as the STATE
for a station in Hawaii. What Country it was logged as is
one of them. SeventyThree(s).
?
?
When N1MM exports qso's the DXCC field is never
included.? N1MM figures where ever it is imported to will
figure it out..
73 Rick n2AMG
On 10/31/2024 5:17 PM, Bob via
groups.io wrote:
I notice there is
no DXCC field in the ADIF record. Is the QSO logged
with the DXCC of 291 or 110? SeventyThree(s).
?
?
Bob, good
evening...
I am very sorry, was my mistake about deleting
BAD.adi file.
Of course I could show you, really, I have no
problems with?
public logs (I
am finally doing LoTW today, for the first time
).
I am trying to
recover from?"deleted files".
?
Logger32 (Version
4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif
corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW
<QSO_DATE:8>20231210 <TIME_ON:6>233226
<TIME_OFF:6>233226 <STATE:2>HI
<BAND:3>10M <STATION_CALLSIGN:5>PY2NY
<FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10
<FREQ_RX:8>28.40730 <MODE:3>SSB
<RST_RCVD:2>59 <RST_SENT:2>59
<TX_PWR:3>100 <OPERATOR:5>PY2NY
<CQZ:2>31 <STX:4>1276
<APP_N1MM_POINTS:1>0
<APP_N1MM_RADIO_NR:1>1
<APP_N1MM_CONTINENT:2>OC
<APP_N1MM_RUN1RUN2:1>1
<APP_N1MM_RADIOINTERFACED:1>1
<APP_N1MM_ISORIGINAL:4>True
<APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF
<APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6
<APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0
<APP_N1MM_MULT3:1>0
<APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2
<APP_N1MM_CLAIMEDQSO:1>1
<APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis
Aidar dos Santos
?
If you
won't show me the ADIF record for the KH6KW
contact, will you at least tell me what the
DXCC field was? SeventyThree(s).
?
?
Thanks
Bob
I got BAD file,
made STATE blank for HI?(KH6KW) from the
file, and changed XE2X
TAM province to
TMS. That was enough to import those missed
3 QSOs into my
Logger32.
Now, I am just
preparing another message about "EDIT"
function.
Thanks a thousand
times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? -
Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly,
the ADIF record will be in the BAD.ADI
file. Please copy/past the record here.
SeventyThree(s).
?
?
Good
morning
I did my research
in the logger32 archive and even the
1000 pages
manual. Can't
import STATE [HI] from ADIF
generated by N1MM.
I solved?problem
with NF changing to NL. But what to
do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY /
V26NY? - Vitor Luis
Aidar dos Santos
?
?
?
?
?
?
|
I have not figured that one out yet. Need more time to try and
see whats going on..
73 Rick N2AMG
On 10/31/2024 5:36 PM, DIDIER DIENNE
wrote:
why are my QSOs not flagged on?''''confirmation
envoyée avec Lotw''''
MERCI
------ Message d'origine ------
Date 31/10/2024 22:30:49
Objet Re: [hamlogger] Hawaii
Understood. There is
abundant evidence that the station is/was in Hawaii - CQ
Zone, Continent, and Prefix. I'm still narrowing down the
possibilities as to why Logger32 rejected HI as the STATE
for a station in Hawaii. What Country it was logged as is
one of them. SeventyThree(s).
?
?
When N1MM exports qso's the DXCC field is never
included.? N1MM figures where ever it is imported to will
figure it out..
73 Rick n2AMG
On 10/31/2024 5:17 PM, Bob via
groups.io wrote:
I notice there is
no DXCC field in the ADIF record. Is the QSO logged
with the DXCC of 291 or 110? SeventyThree(s).
?
?
Bob, good
evening...
I am very sorry, was my mistake about deleting
BAD.adi file.
Of course I could show you, really, I have no
problems with?
public logs (I
am finally doing LoTW today, for the first time).
I am trying to
recover from?"deleted files".
?
Logger32 (Version
4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif
corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW
<QSO_DATE:8>20231210 <TIME_ON:6>233226
<TIME_OFF:6>233226 <STATE:2>HI
<BAND:3>10M <STATION_CALLSIGN:5>PY2NY
<FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10
<FREQ_RX:8>28.40730 <MODE:3>SSB
<RST_RCVD:2>59 <RST_SENT:2>59
<TX_PWR:3>100 <OPERATOR:5>PY2NY
<CQZ:2>31 <STX:4>1276
<APP_N1MM_POINTS:1>0
<APP_N1MM_RADIO_NR:1>1
<APP_N1MM_CONTINENT:2>OC
<APP_N1MM_RUN1RUN2:1>1
<APP_N1MM_RADIOINTERFACED:1>1
<APP_N1MM_ISORIGINAL:4>True
<APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF
<APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6
<APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0
<APP_N1MM_MULT3:1>0
<APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2
<APP_N1MM_CLAIMEDQSO:1>1
<APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis
Aidar dos Santos
?
If you
won't show me the ADIF record for the KH6KW
contact, will you at least tell me what the
DXCC field was? SeventyThree(s).
?
?
Thanks
Bob
I got BAD file,
made STATE blank for HI?(KH6KW) from the
file, and changed XE2X
TAM province to
TMS. That was enough to import those missed
3 QSOs into my
Logger32.
Now, I am just
preparing another message about "EDIT"
function.
Thanks a thousand
times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? -
Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly,
the ADIF record will be in the BAD.ADI
file. Please copy/past the record here.
SeventyThree(s).
?
?
Good
morning
I did my research
in the logger32 archive and even the
1000 pages
manual. Can't
import STATE [HI] from ADIF
generated by N1MM.
I solved?problem
with NF changing to NL. But what to
do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY /
V26NY? - Vitor Luis
Aidar dos Santos
?
?
?
?
?
?
|
Re: Logger32 v4.0.329 is on-line
... and remember to download for up-to-date info on the current version.?
73 Gary? ?beater/tester &?
Honor Roll &? checker
The maintenance release includes the following:
?
Fixed a bug showing the callsign 3D22 in the floating callsign window.
Fixed a bug where macros $radiocontrolpanelmacro37$ to $radiocontrolpanelmacro48$ did not work.
Fixed a bug where on PCs configured for Japanese, the DX Cluster command SH/DX xxx generated errors.
Changes made to the cherry-picker to detect stations running multiple streams, and to not abort contacts with these stations if they call someone else in the middle of your contact. The number at the bottom right of the cherry-picker event viewer now shows total number of decodes / number of new decodes / number of decodes?using more than one stream.
Change made for OTRSP users so that when Logger32 starts OTRSP commands are sent so select to Logger32 primary radio.
Changes made to the Logbook Page Window scrolling. After selecting a callsign by clicking on the PreviousQSO window the Logbook Page Window should scroll up/down to the previous/next QSO.
?
Remember to backup, backup, then backup again,
Enjoy.
?
|
------ Message d'origine ------
Date 31/10/2024 21:07:39
Objet Re: [hamlogger] Edit OPERATOR
I am not wondering that you do not believe me. I did not believe my eyes when I saw the stuff as well.
Attached there is the original file which was imported in the first step. I tried to attache the full adif logbook, but it is too big, myaybe the link would help. Well, I plan a short SOTA activation on two meters FM
tomorrow afternoon, typically yielding only a handful of QSOs.
Let me wait and see how it goes. 73, Ruda, OK2QA
... of course when you edited the operator <OPERATOR:5>OK2QA to be OK2QA/P you did change the 5 to 7. Oh well, SeventyThree(s)AndBackToGardening.
On 10/31/2024 2:02 PM EDT Bob < k4cy@...> wrote:
?
?
I don't believe you. If you successfully?imported an ADIF file with the OPERATOR as OK2QA/P. Those QSOs will be logged with OPERATOR as OK2QA/P. QSOs with no OPERATOR field will have been logged with OPERATOR as whoever has the logbook open. Maybe you have more luck in the garden? SeventyThree(s).
?
?
Hi,
I have similar problem.
After activating portable outdoors I always export the log from notebook with operator OK2QA/P and import it into the home PC. This is the way I used hundred times already and it always worked fine. But yesterday the affix /P was lost during the import. Manual correction one by one line was not feasible for the portable log of about 100 QSOs while correcting one record took approximately 60 seconds.
Okay. I duly made a backup, exported the whole log of 200 000 QSOs, deleted the relevant portion with missing /P and imported the clean rest into a new log. It takes time so that I can do some gardening in between. Finally I imported the relevant protion again, taking special care (checking that the OPERATOR was OK2QA/P indeed). The result was as wrong as before, /P missing.
Next step: Exported the complete log again, changed the OPERATOR from OK2QA to OK2QA/P in adif using Notepad (luckilly this can be done as bulk operation). Then I imported the corrected adif in a new logbook (more gardening) being sure it must go well this time. It went wrong again.
I am at the end of my wisdom. What irritates me most is that I used the procedure of translating my portable operation logs into the main log many times for many years without any problem until now.
Help?
73, Ruda, OK2QA
?
Tried similar way as Bob suggests proceeding as follows:
Here we go again ...
?
1) Backup your logbook
2) Look at the QSO number of the first QSO you imported with the wrong OPERATOR field.. For this example we will say it 123456
3) Export a partial logbook of QSO number 1 to QSO number 123455
4) Create a new/empty logbook
5) Import the file you made in step 3
6) Make a new backup
7) Promise yourself to ALWAYS make backups before importing files.
?
SeventyThree(s).
?
?
?
Good morning
?
I forgot to change OPERATOR before importing to Logger32.
Now, I would like to edit OPERATOR from PY5WRTC to PY2NY
but seems to me that the only way is one by one...
Is there a way to change all?PY5WRTC to PY2NY at same time?
Thanks again
?
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
|
why are my QSOs not flagged on?''''confirmation envoyée avec Lotw''''
MERCI
------ Message d'origine ------
Date 31/10/2024 22:30:49
Objet Re: [hamlogger] Hawaii
Understood. There is abundant evidence that the station is/was in Hawaii - CQ Zone, Continent, and Prefix. I'm still narrowing down the possibilities as to why Logger32 rejected HI as the STATE for a station in Hawaii. What Country it was logged as is one of them. SeventyThree(s).
On 10/31/2024 5:21 PM EDT Rick Ellison <rellison@...> wrote:
?
?
When N1MM exports qso's the DXCC field is never included.? N1MM figures where ever it is imported to will figure it out..
73 Rick n2AMG
On 10/31/2024 5:17 PM, Bob via groups.io wrote:
I notice there is no DXCC field in the ADIF record. Is the QSO logged with the DXCC of 291 or 110? SeventyThree(s).
?
?
Bob, good evening...
I am very sorry, was my mistake about deleting BAD.adi file.
Of course I could show you, really, I have no problems with?
public logs (I am finally doing LoTW today, for the first time).
I am trying to recover from?"deleted files".
?
Logger32 (Version 4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW <QSO_DATE:8>20231210 <TIME_ON:6>233226 <TIME_OFF:6>233226 <STATE:2>HI <BAND:3>10M <STATION_CALLSIGN:5>PY2NY <FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10 <FREQ_RX:8>28.40730 <MODE:3>SSB <RST_RCVD:2>59 <RST_SENT:2>59 <TX_PWR:3>100 <OPERATOR:5>PY2NY <CQZ:2>31 <STX:4>1276 <APP_N1MM_POINTS:1>0 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF <APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6 <APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0 <APP_N1MM_MULT3:1>0 <APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2 <APP_N1MM_CLAIMEDQSO:1>1 <APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
If you won't show me the ADIF record for the KH6KW contact, will you at least tell me what the DXCC field was? SeventyThree(s).
?
?
Thanks Bob
I got BAD file, made STATE blank for HI?(KH6KW) from the file, and changed XE2X
TAM province to TMS. That was enough to import those missed 3 QSOs into my
Logger32.
Now, I am just preparing another message about "EDIT" function.
Thanks a thousand times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly, the ADIF record will be in the BAD.ADI file. Please copy/past the record here. SeventyThree(s).
?
?
Good morning
I did my research in the logger32 archive and even the 1000 pages
manual. Can't import STATE [HI] from ADIF generated by N1MM.
I solved?problem with NF changing to NL. But what to do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
?
?
|
Understood. There is abundant evidence that the station is/was in Hawaii - CQ Zone, Continent, and Prefix. I'm still narrowing down the possibilities as to why Logger32 rejected HI as the STATE for a station in Hawaii. What Country it was logged as is one of them. SeventyThree(s).
On 10/31/2024 5:21 PM EDT Rick Ellison <rellison@...> wrote:
?
?
When N1MM exports qso's the DXCC field is never included.? N1MM figures where ever it is imported to will figure it out..
73 Rick n2AMG
On 10/31/2024 5:17 PM, Bob via groups.io wrote:
I notice there is no DXCC field in the ADIF record. Is the QSO logged with the DXCC of 291 or 110? SeventyThree(s).
?
?
Bob, good evening...
I am very sorry, was my mistake about deleting BAD.adi file.
Of course I could show you, really, I have no problems with?
public logs (I am finally doing LoTW today, for the first time).
I am trying to recover from?"deleted files".
?
Logger32 (Version 4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW <QSO_DATE:8>20231210 <TIME_ON:6>233226 <TIME_OFF:6>233226 <STATE:2>HI <BAND:3>10M <STATION_CALLSIGN:5>PY2NY <FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10 <FREQ_RX:8>28.40730 <MODE:3>SSB <RST_RCVD:2>59 <RST_SENT:2>59 <TX_PWR:3>100 <OPERATOR:5>PY2NY <CQZ:2>31 <STX:4>1276 <APP_N1MM_POINTS:1>0 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF <APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6 <APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0 <APP_N1MM_MULT3:1>0 <APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2 <APP_N1MM_CLAIMEDQSO:1>1 <APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
If you won't show me the ADIF record for the KH6KW contact, will you at least tell me what the DXCC field was? SeventyThree(s).
?
?
Thanks Bob
I got BAD file, made STATE blank for HI?(KH6KW) from the file, and changed XE2X
TAM province to TMS. That was enough to import those missed 3 QSOs into my
Logger32.
Now, I am just preparing another message about "EDIT" function.
Thanks a thousand times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly, the ADIF record will be in the BAD.ADI file. Please copy/past the record here. SeventyThree(s).
?
?
Good morning
I did my research in the logger32 archive and even the 1000 pages
manual. Can't import STATE [HI] from ADIF generated by N1MM.
I solved?problem with NF changing to NL. But what to do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
?
?
|
Re: QSO by bands in the Previous QSOs window
Hello Panos are you sure?
?
When I right click on Band in Previous QSO Window I get :- The Previous QSO Setup Dialogue!!
?
73
?
Ian G4GIR
?
PS It would be nice? to sort that window by Band.
?
toggle quoted message
Show quoted text
----- Original Message -----
Sent: 31/10/2024 20:10:37
Subject: Re: [hamlogger] QSO by bands in the Previous QSOs window
Hi, right click on BAND for sorting 73
|
When N1MM exports qso's the DXCC field is never included.? N1MM
figures where ever it is imported to will figure it out..
73 Rick n2AMG
On 10/31/2024 5:17 PM, Bob via
groups.io wrote:
toggle quoted message
Show quoted text
I notice
there is no DXCC field in the ADIF record. Is the QSO logged
with the DXCC of 291 or 110? SeventyThree(s).
?
?
Bob,
good evening...
I am very sorry, was my mistake about deleting BAD.adi file.
Of course I could show you, really, I have no problems with?
public logs (I am finally doing LoTW today, for the
first time).
I am
trying to recover from?"deleted files".
?
Logger32 (Version 4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif
corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW
<QSO_DATE:8>20231210 <TIME_ON:6>233226
<TIME_OFF:6>233226 <STATE:2>HI <BAND:3>10M
<STATION_CALLSIGN:5>PY2NY <FREQ:7>28.4073
<CONTEST_ID:7>ARRL-10 <FREQ_RX:8>28.40730
<MODE:3>SSB <RST_RCVD:2>59 <RST_SENT:2>59
<TX_PWR:3>100 <OPERATOR:5>PY2NY <CQZ:2>31
<STX:4>1276 <APP_N1MM_POINTS:1>0
<APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC
<APP_N1MM_RUN1RUN2:1>1
<APP_N1MM_RADIOINTERFACED:1>1
<APP_N1MM_ISORIGINAL:4>True
<APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF
<APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6
<APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0
<APP_N1MM_MULT3:1>0
<APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2
<APP_N1MM_CLAIMEDQSO:1>1
<APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar
dos Santos
?
If
you won't show me the ADIF record for the KH6KW
contact, will you at least tell me what the DXCC field
was? SeventyThree(s).
?
?
Thanks
Bob
I got BAD file,
made STATE blank for HI?(KH6KW) from the file, and
changed XE2X
TAM province to
TMS. That was enough to import those missed 3 QSOs
into my
Logger32.
Now, I am just
preparing another message about "EDIT" function.
Thanks a thousand
times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis
Aidar dos Santos
?
If the QSO was not imported correctly, the ADIF
record will be in the BAD.ADI file. Please
copy/past the record here. SeventyThree(s).
?
?
Good
morning
I did my research
in the logger32 archive and even the 1000
pages
manual. Can't
import STATE [HI] from ADIF generated by
N1MM.
I solved?problem
with NF changing to NL. But what to do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? -
Vitor Luis Aidar dos Santos
?
?
?
?
?
?
|
I notice there is no DXCC field in the ADIF record. Is the QSO logged with the DXCC of 291 or 110? SeventyThree(s).
On 10/31/2024 5:04 PM EDT PY2NY <py2ny.vitor@...> wrote:
?
?
Bob, good evening...
I am very sorry, was my mistake about deleting BAD.adi file.
Of course I could show you, really, I have no problems with?
public logs (I am finally doing LoTW today, for the first time).
I am trying to recover from?"deleted files".
?
Logger32 (Version 4.0) ADIF file import exception(s).
Source file - c:\users\py2ny - vitor\documents\adif corrigido.adi
Created 31 out 24, 11:20:16
Operator - PY2NY
<EOH>
Error in the STATE field: ?<CALL:5>KH6KW <QSO_DATE:8>20231210 <TIME_ON:6>233226 <TIME_OFF:6>233226 <STATE:2>HI <BAND:3>10M <STATION_CALLSIGN:5>PY2NY <FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10 <FREQ_RX:8>28.40730 <MODE:3>SSB <RST_RCVD:2>59 <RST_SENT:2>59 <TX_PWR:3>100 <OPERATOR:5>PY2NY <CQZ:2>31 <STX:4>1276 <APP_N1MM_POINTS:1>0 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF <APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6 <APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0 <APP_N1MM_MULT3:1>0 <APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2 <APP_N1MM_CLAIMEDQSO:1>1 <APP_N1MM_CONTACTTYPE:1>D <EOR>
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
If you won't show me the ADIF record for the KH6KW contact, will you at least tell me what the DXCC field was? SeventyThree(s).
?
?
Thanks Bob
I got BAD file, made STATE blank for HI?(KH6KW) from the file, and changed XE2X
TAM province to TMS. That was enough to import those missed 3 QSOs into my
Logger32.
Now, I am just preparing another message about "EDIT" function.
Thanks a thousand times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly, the ADIF record will be in the BAD.ADI file. Please copy/past the record here. SeventyThree(s).
?
?
Good morning
I did my research in the logger32 archive and even the 1000 pages
manual. Can't import STATE [HI] from ADIF generated by N1MM.
I solved?problem with NF changing to NL. But what to do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
?
?
|
I have connected to the AE5E DX Cluster for 36 hours with no errors.. SeventyThree(s).
On 10/30/2024 12:16 PM EDT Bob <k4cy@...> wrote:
?
?
To answer my question, you are connected to AE5E DX Cluster. I will connect to it and see if I can duplicate your problem. SeventyThree(s).
On 10/30/2024 11:58 AM EDT Bob via groups.io <k4cy@...> wrote:
?
?
What DX Cluster are you connected to? SeventyThree(s).
On 10/30/2024 11:27 AM EDT Jean-Claude ROUGE via groups.io <j-cl.rouge@...> wrote:
?
?
Hi,
Please in the attached file what I get o?àn my screen before Logger32 stops.
If I click OK, Logger shuts down and I have to restart it.
DEP is on Windows 10, Logger32 version 4.0.328.
Any idea ?
Tks for help and answer.
73's.
Jean-Claude? F6HDH
|
Bob, good evening...
I am very sorry, was my mistake about deleting BAD.adi file.
Of course I could show you, really, I have no problems with? public logs (I am finally doing LoTW today, for the first time). I am trying to recover from?"deleted files".
Logger32 (Version 4.0) ADIF file import exception(s). Source file - c:\users\py2ny - vitor\documents\adif corrigido.adi Created 31 out 24, 11:20:16 Operator - PY2NY <EOH> Error in the STATE field: ?<CALL:5>KH6KW <QSO_DATE:8>20231210 <TIME_ON:6>233226 <TIME_OFF:6>233226 <STATE:2>HI <BAND:3>10M <STATION_CALLSIGN:5>PY2NY <FREQ:7>28.4073 <CONTEST_ID:7>ARRL-10 <FREQ_RX:8>28.40730 <MODE:3>SSB <RST_RCVD:2>59 <RST_SENT:2>59 <TX_PWR:3>100 <OPERATOR:5>PY2NY <CQZ:2>31 <STX:4>1276 <APP_N1MM_POINTS:1>0 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>DESKTOP-EJIUMTF <APP_N1MM_ISRUNQSO:1>1 <PFX:3>KH6 <APP_N1MM_MULT1:1>0 <APP_N1MM_MULT2:1>0 <APP_N1MM_MULT3:1>0 <APP_N1MM_ID:32>d4a8bdafe4ad4040996209df04571af2 <APP_N1MM_CLAIMEDQSO:1>1 <APP_N1MM_CONTACTTYPE:1>D <EOR> . .. ... --------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
If you won't show me the ADIF record for the KH6KW contact, will you at least tell me what the DXCC field was? SeventyThree(s).
?
?
Thanks Bob
I got BAD file, made STATE blank for HI?(KH6KW) from the file, and changed XE2X
TAM province to TMS. That was enough to import those missed 3 QSOs into my
Logger32.
Now, I am just preparing another message about "EDIT" function.
Thanks a thousand times. [ Vitor ]
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
If the QSO was not imported correctly, the ADIF record will be in the BAD.ADI file. Please copy/past the record here. SeventyThree(s).
?
?
Good morning
I did my research in the logger32 archive and even the 1000 pages
manual. Can't import STATE [HI] from ADIF generated by N1MM.
I solved?problem with NF changing to NL. But what to do with
Hawaii?
Thanks...
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
|
Just send me the modified ADIF file that you changed the OPERATOR to be /P
SeventyThree(s).
On 10/31/2024 4:07 PM EDT Rudolf Klvana <rud.klvana@...> wrote:
?
?
I am not wondering that you do not believe me. I did not believe my eyes when I saw the stuff as well.
Attached there is the original file which was imported in the first step.
I tried to attache the full adif logbook, but it is too big, myaybe the link would help.
Well, I plan a short SOTA activation on two meters FM tomorrow afternoon, typically yielding only a handful of QSOs.
Let me wait and see how it goes.
73, Ruda, OK2QA
... of course when you edited the operator <OPERATOR:5>OK2QA to be OK2QA/P you did change the 5 to 7. Oh well, SeventyThree(s)AndBackToGardening.
On 10/31/2024 2:02 PM EDT Bob < k4cy@...> wrote:
?
?
I don't believe you. If you successfully?imported an ADIF file with the OPERATOR as OK2QA/P. Those QSOs will be logged with OPERATOR as OK2QA/P. QSOs with no OPERATOR field will have been logged with OPERATOR as whoever has the logbook open. Maybe you have more luck in the garden? SeventyThree(s).
?
?
Hi,
I have similar problem.
After activating portable outdoors I always export the log from notebook with operator OK2QA/P and import it into the home PC. This is the way I used hundred times already and it always worked fine. But yesterday the affix /P was lost during the import. Manual correction one by one line was not feasible for the portable log of about 100 QSOs while correcting one record took approximately 60 seconds.
Okay. I duly made a backup, exported the whole log of 200 000 QSOs, deleted the relevant portion with missing /P and imported the clean rest into a new log. It takes time so that I can do some gardening in between. Finally I imported the relevant protion again, taking special care (checking that the OPERATOR was OK2QA/P indeed). The result was as wrong as before, /P missing.
Next step: Exported the complete log again, changed the OPERATOR from OK2QA to OK2QA/P in adif using Notepad (luckilly this can be done as bulk operation). Then I imported the corrected adif in a new logbook (more gardening) being sure it must go well this time. It went wrong again.
I am at the end of my wisdom. What irritates me most is that I used the procedure of translating my portable operation logs into the main log many times for many years without any problem until now.
Help?
73, Ruda, OK2QA
?
Tried similar way as Bob suggests proceeding as follows:
Here we go again ...
?
1) Backup your logbook
2) Look at the QSO number of the first QSO you imported with the wrong OPERATOR field.. For this example we will say it 123456
3) Export a partial logbook of QSO number 1 to QSO number 123455
4) Create a new/empty logbook
5) Import the file you made in step 3
6) Make a new backup
7) Promise yourself to ALWAYS make backups before importing files.
?
SeventyThree(s).
?
?
?
Good morning
?
I forgot to change OPERATOR before importing to Logger32.
Now, I would like to edit OPERATOR from PY5WRTC to PY2NY
but seems to me that the only way is one by one...
Is there a way to change all?PY5WRTC to PY2NY at same time?
Thanks again
?
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
?
?
|
Re: QSO by bands in the Previous QSOs window
Hi, right click on BAND for sorting 73
|
I am not wondering that you do not believe me. I did not believe my eyes when I saw the stuff as well.
Attached there is the original file which was imported in the first step. I tried to attache the full adif logbook, but it is too big, myaybe the link would help. Well, I plan a short SOTA activation on two meters FM
tomorrow afternoon, typically yielding only a handful of QSOs.
Let me wait and see how it goes. 73, Ruda, OK2QA
... of course when you edited the operator <OPERATOR:5>OK2QA to be OK2QA/P you did change the 5 to 7. Oh well, SeventyThree(s)AndBackToGardening.
On 10/31/2024 2:02 PM EDT Bob < k4cy@...> wrote:
?
?
I don't believe you. If you successfully?imported an ADIF file with the OPERATOR as OK2QA/P. Those QSOs will be logged with OPERATOR as OK2QA/P. QSOs with no OPERATOR field will have been logged with OPERATOR as whoever has the logbook open. Maybe you have more luck in the garden? SeventyThree(s).
?
?
Hi,
I have similar problem.
After activating portable outdoors I always export the log from notebook with operator OK2QA/P and import it into the home PC. This is the way I used hundred times already and it always worked fine. But yesterday the affix /P was lost during the import. Manual correction one by one line was not feasible for the portable log of about 100 QSOs while correcting one record took approximately 60 seconds.
Okay. I duly made a backup, exported the whole log of 200 000 QSOs, deleted the relevant portion with missing /P and imported the clean rest into a new log. It takes time so that I can do some gardening in between. Finally I imported the relevant protion again, taking special care (checking that the OPERATOR was OK2QA/P indeed). The result was as wrong as before, /P missing.
Next step: Exported the complete log again, changed the OPERATOR from OK2QA to OK2QA/P in adif using Notepad (luckilly this can be done as bulk operation). Then I imported the corrected adif in a new logbook (more gardening) being sure it must go well this time. It went wrong again.
I am at the end of my wisdom. What irritates me most is that I used the procedure of translating my portable operation logs into the main log many times for many years without any problem until now.
Help?
73, Ruda, OK2QA
?
Tried similar way as Bob suggests proceeding as follows:
Here we go again ...
?
1) Backup your logbook
2) Look at the QSO number of the first QSO you imported with the wrong OPERATOR field.. For this example we will say it 123456
3) Export a partial logbook of QSO number 1 to QSO number 123455
4) Create a new/empty logbook
5) Import the file you made in step 3
6) Make a new backup
7) Promise yourself to ALWAYS make backups before importing files.
?
SeventyThree(s).
?
?
?
Good morning
?
I forgot to change OPERATOR before importing to Logger32.
Now, I would like to edit OPERATOR from PY5WRTC to PY2NY
but seems to me that the only way is one by one...
Is there a way to change all?PY5WRTC to PY2NY at same time?
Thanks again
?
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
|
... of course when you edited the operator <OPERATOR:5>OK2QA to be OK2QA/P you did change the 5 to 7. Oh well, SeventyThree(s)AndBackToGardening.
On 10/31/2024 2:02 PM EDT Bob <k4cy@...> wrote:
?
?
I don't believe you. If you successfully?imported an ADIF file with the OPERATOR as OK2QA/P. Those QSOs will be logged with OPERATOR as OK2QA/P. QSOs with no OPERATOR field will have been logged with OPERATOR as whoever has the logbook open. Maybe you have more luck in the garden? SeventyThree(s).
On 10/31/2024 1:28 PM EDT Rudolf Klvana <rud.klvana@...> wrote:
?
?
Hi,
I have similar problem.
After activating portable outdoors I always export the log from notebook with operator OK2QA/P and import it into the home PC. This is the way I used hundred times already and it always worked fine. But yesterday the affix /P was lost during the import. Manual correction one by one line was not feasible for the portable log of about 100 QSOs while correcting one record took approximately 60 seconds.
Okay. I duly made a backup, exported the whole log of 200 000 QSOs, deleted the relevant portion with missing /P and imported the clean rest into a new log. It takes time so that I can do some gardening in between. Finally I imported the relevant protion again, taking special care (checking that the OPERATOR was OK2QA/P indeed). The result was as wrong as before, /P missing.
Next step: Exported the complete log again, changed the OPERATOR from OK2QA to OK2QA/P in adif using Notepad (luckilly this can be done as bulk operation). Then I imported the corrected adif in a new logbook (more gardening) being sure it must go well this time. It went wrong again.
I am at the end of my wisdom. What irritates me most is that I used the procedure of translating my portable operation logs into the main log many times for many years without any problem until now.
Help?
73, Ruda, OK2QA
?
Tried similar way as Bob suggests proceeding as follows:
Here we go again ...
?
1) Backup your logbook
2) Look at the QSO number of the first QSO you imported with the wrong OPERATOR field.. For this example we will say it 123456
3) Export a partial logbook of QSO number 1 to QSO number 123455
4) Create a new/empty logbook
5) Import the file you made in step 3
6) Make a new backup
7) Promise yourself to ALWAYS make backups before importing files.
?
SeventyThree(s).
?
?
?
Good morning
?
I forgot to change OPERATOR before importing to Logger32.
Now, I would like to edit OPERATOR from PY5WRTC to PY2NY
but seems to me that the only way is one by one...
Is there a way to change all?PY5WRTC to PY2NY at same time?
Thanks again
?
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
|
QSO by bands in the Previous QSOs window
Hi, it would be helpful to enable sorting QSOs by bands in the Previous QSOs window. Useful when there are many QSOs with a station.
Sorting by date and by time does the same thing.
Thanks!
73?? Vytas?? LZ2VQ
|
I don't believe you. If you successfully?imported an ADIF file with the OPERATOR as OK2QA/P. Those QSOs will be logged with OPERATOR as OK2QA/P. QSOs with no OPERATOR field will have been logged with OPERATOR as whoever has the logbook open. Maybe you have more luck in the garden? SeventyThree(s).
On 10/31/2024 1:28 PM EDT Rudolf Klvana <rud.klvana@...> wrote:
?
?
Hi,
I have similar problem.
After activating portable outdoors I always export the log from notebook with operator OK2QA/P and import it into the home PC. This is the way I used hundred times already and it always worked fine. But yesterday the affix /P was lost during the import. Manual correction one by one line was not feasible for the portable log of about 100 QSOs while correcting one record took approximately 60 seconds.
Okay. I duly made a backup, exported the whole log of 200 000 QSOs, deleted the relevant portion with missing /P and imported the clean rest into a new log. It takes time so that I can do some gardening in between. Finally I imported the relevant protion again, taking special care (checking that the OPERATOR was OK2QA/P indeed). The result was as wrong as before, /P missing.
Next step: Exported the complete log again, changed the OPERATOR from OK2QA to OK2QA/P in adif using Notepad (luckilly this can be done as bulk operation). Then I imported the corrected adif in a new logbook (more gardening) being sure it must go well this time. It went wrong again.
I am at the end of my wisdom. What irritates me most is that I used the procedure of translating my portable operation logs into the main log many times for many years without any problem until now.
Help?
73, Ruda, OK2QA
?
Tried similar way as Bob suggests proceeding as follows:
Here we go again ...
?
1) Backup your logbook
2) Look at the QSO number of the first QSO you imported with the wrong OPERATOR field.. For this example we will say it 123456
3) Export a partial logbook of QSO number 1 to QSO number 123455
4) Create a new/empty logbook
5) Import the file you made in step 3
6) Make a new backup
7) Promise yourself to ALWAYS make backups before importing files.
?
SeventyThree(s).
?
?
?
Good morning
?
I forgot to change OPERATOR before importing to Logger32.
Now, I would like to edit OPERATOR from PY5WRTC to PY2NY
but seems to me that the only way is one by one...
Is there a way to change all?PY5WRTC to PY2NY at same time?
Thanks again
?
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
?
?
|
Hi, I have similar problem.
After activating portable outdoors I always export the log from notebook with operator OK2QA/P and import it into the home PC. This is the way I used hundred times already and it always worked fine. But yesterday the affix /P was lost during the import. Manual correction one by one line was not feasible for the portable log of about 100 QSOs while correcting one record took approximately 60 seconds. Okay. I duly made a backup, exported the whole log of 200 000 QSOs, deleted the relevant portion with missing /P and imported the clean rest into a new log. It takes time so that I can do some gardening in between. Finally I imported the relevant protion again, taking special care (checking that the OPERATOR was OK2QA/P indeed). The result was as wrong as before, /P missing. Next step: Exported the complete log again, changed the OPERATOR from OK2QA to OK2QA/P in adif using Notepad (luckilly this can be done as bulk operation). Then I imported the corrected adif in a new logbook (more gardening) being sure it must go well this time. It went wrong again. I am at the end of my wisdom. What irritates me most is that I used the procedure of translating my portable operation logs into the main log many times for many years without any problem until now.
Help? 73, Ruda, OK2QA
Tried similar way as Bob suggests proceeding as follows:
Here we go again ...
?
1) Backup your logbook
2) Look at the QSO number of the first QSO you imported with the wrong OPERATOR field.. For this example we will say it 123456
3) Export a partial logbook of QSO number 1 to QSO number 123455
4) Create a new/empty logbook
5) Import the file you made in step 3
6) Make a new backup
7) Promise yourself to ALWAYS make backups before importing files.
?
SeventyThree(s).
?
?
?
Good morning
?
I forgot to change OPERATOR before importing to Logger32.
Now, I would like to edit OPERATOR from PY5WRTC to PY2NY
but seems to me that the only way is one by one...
Is there a way to change all?PY5WRTC to PY2NY at same time?
Thanks again
?
.
..
...
--------------------------------
PY2NY / SP9NY / V26NY? - Vitor Luis Aidar dos Santos
?
?
|
ZL2iFB
Panos