Date   
Re: trapped error 1002

Bob <k4cy@...>
 

... Jim, and all this time I thought you were a lawyer. Turns out your a closet techie¬†ūüėĄ

On September 19, 2019 at 5:54 PM Jim Altman <jaltman636@...> wrote:

Or, if you want to be really fancy you could import the adif into excel use an excel formula to multiply all the bad frequencies by 1000.  If freq <1 then freq=freq*1000

 

 

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Thursday, September 19, 2019 4:10 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] trapped error 1002

 

Andrew, shouting didn't work? Ask the XYL to try ... that's the ultimate deterrent around here. First, glad you have identified the two QSOs with no callsign ... Just ignore them, they were not imported, to the object of the exercise was achieved.

 

To fix the problem with the incorrect frequency. there are several highly recommends ADIF editors you might try (recommended by others, I've never used/needed one). Maybe one allows you to fix the FREQ field easily. Or you could import the QSOs with no frequency (but this may come back to bite you later). To do that, you edit the .ADI file with notepad (or similar). and make a global change of <FREQ: to <XFREQ:  That way, when you import the file, FREQ will be ignored (because it doesn't exist). SeventyThree(s).

 

 

On September 19, 2019 at 3:45 PM Andrew Mulholland <andrew@...> wrote:

Thanks for the reply Bob

 

When I try to import the log I get errors:

 

Error : Frequency does not appear to be in the 40M Band:  <BAND:3>40M <CALL:6>GI0DVU <CONT:2>EU <CQZ:2>14 <DXCC:3>265 <FREQ:7>.007070 <GRIDSQUARE:6>IO64xm <IOTA:6>EU-115 <ITUZ:2>27 <MODE:3>SSB <NAME:2>N. <OPERATOR:6>MI0BPB <PFX:3>GI0 <QSO_DATE:8:D>19980317 <TIME_ON:6>211600 <QTH:7>IRELAND <RST_RCVD:2>59 <RST_SENT:2>59 <TIME_OFF:6>211600 <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:1>2  <EOR>

 


These errors are generated from logs brought over from hyperlog years ago, obviously I can edit them (around 700) but just checking that is the simplest way?

 

The below are the errors I have the feeling may be causing the problem:

 

 

Error in the CALL field:  <QSO_DATE:8:D>20140322 <TIME_ON:6>084554 <APP_LOGGER32_QSO_NUMBER:5>26878  <EOR>

 

Error in the CALL field:  <QSO_DATE:8:D>20140330 <TIME_ON:6>101244 <APP_LOGGER32_QSO_NUMBER:5>26982  <EOR>

 


When I look up the QSO number in Logger and click on them the program jumps the the end of the Log. Is there any way to edit the log outside Logger so I can delete these two entries? See if that sorts the problem?

I tried shouting at the computer but that proved unsuccessful.

 

thanks Andrew

 

 


 


 

 



 


 

Re: trapped error 1002

Jim Altman
 

Or, if you want to be really fancy you could import the adif into excel use an excel formula to multiply all the bad frequencies by 1000.  If freq <1 then freq=freq*1000

 

 

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: Thursday, September 19, 2019 4:10 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] trapped error 1002

 

Andrew, shouting didn't work? Ask the XYL to try ... that's the ultimate deterrent around here. First, glad you have identified the two QSOs with no callsign ... Just ignore them, they were not imported, to the object of the exercise was achieved.

 

To fix the problem with the incorrect frequency. there are several highly recommends ADIF editors you might try (recommended by others, I've never used/needed one). Maybe one allows you to fix the FREQ field easily. Or you could import the QSOs with no frequency (but this may come back to bite you later). To do that, you edit the .ADI file with notepad (or similar). and make a global change of <FREQ: to <XFREQ:  That way, when you import the file, FREQ will be ignored (because it doesn't exist). SeventyThree(s).

 

 

On September 19, 2019 at 3:45 PM Andrew Mulholland <andrew@...> wrote:

Thanks for the reply Bob

 

When I try to import the log I get errors:

 

Error : Frequency does not appear to be in the 40M Band:  <BAND:3>40M <CALL:6>GI0DVU <CONT:2>EU <CQZ:2>14 <DXCC:3>265 <FREQ:7>.007070 <GRIDSQUARE:6>IO64xm <IOTA:6>EU-115 <ITUZ:2>27 <MODE:3>SSB <NAME:2>N. <OPERATOR:6>MI0BPB <PFX:3>GI0 <QSO_DATE:8:D>19980317 <TIME_ON:6>211600 <QTH:7>IRELAND <RST_RCVD:2>59 <RST_SENT:2>59 <TIME_OFF:6>211600 <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:1>2  <EOR>

 


These errors are generated from logs brought over from hyperlog years ago, obviously I can edit them (around 700) but just checking that is the simplest way?

 

The below are the errors I have the feeling may be causing the problem:

 

 

Error in the CALL field:  <QSO_DATE:8:D>20140322 <TIME_ON:6>084554 <APP_LOGGER32_QSO_NUMBER:5>26878  <EOR>

 

Error in the CALL field:  <QSO_DATE:8:D>20140330 <TIME_ON:6>101244 <APP_LOGGER32_QSO_NUMBER:5>26982  <EOR>

 


When I look up the QSO number in Logger and click on them the program jumps the the end of the Log. Is there any way to edit the log outside Logger so I can delete these two entries? See if that sorts the problem?

I tried shouting at the computer but that proved unsuccessful.

 

thanks Andrew

 

 


 


 

Re: trapped error 1002

Bob <k4cy@...>
 

Andrew, shouting didn't work? Ask the XYL to try ... that's the ultimate deterrent around here. First, glad you have identified the two QSOs with no callsign ... Just ignore them, they were not imported, to the object of the exercise was achieved.


To fix the problem with the incorrect frequency. there are several highly recommends ADIF editors you might try (recommended by others, I've never used/needed one). Maybe one allows you to fix the FREQ field easily. Or you could import the QSOs with no frequency (but this may come back to bite you later). To do that, you edit the .ADI file with notepad (or similar). and make a global change of <FREQ: to <XFREQ:  That way, when you import the file, FREQ will be ignored (because it doesn't exist). SeventyThree(s).



On September 19, 2019 at 3:45 PM Andrew Mulholland <andrew@...> wrote:

Thanks for the reply Bob


When I try to import the log I get errors:

 

Error : Frequency does not appear to be in the 40M Band:  <BAND:3>40M <CALL:6>GI0DVU <CONT:2>EU <CQZ:2>14 <DXCC:3>265 <FREQ:7>.007070 <GRIDSQUARE:6>IO64xm <IOTA:6>EU-115 <ITUZ:2>27 <MODE:3>SSB <NAME:2>N. <OPERATOR:6>MI0BPB <PFX:3>GI0 <QSO_DATE:8:D>19980317 <TIME_ON:6>211600 <QTH:7>IRELAND <RST_RCVD:2>59 <RST_SENT:2>59 <TIME_OFF:6>211600 <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:1>2  <EOR>



These errors are generated from logs brought over from hyperlog years ago, obviously I can edit them (around 700) but just checking that is the simplest way?


The below are the errors I have the feeling may be causing the problem:

 

 

Error in the CALL field:  <QSO_DATE:8:D>20140322 <TIME_ON:6>084554 <APP_LOGGER32_QSO_NUMBER:5>26878  <EOR>

 

Error in the CALL field:  <QSO_DATE:8:D>20140330 <TIME_ON:6>101244 <APP_LOGGER32_QSO_NUMBER:5>26982  <EOR>



When I look up the QSO number in Logger and click on them the program jumps the the end of the Log. Is there any way to edit the log outside Logger so I can delete these two entries? See if that sorts the problem?

I tried shouting at the computer but that proved unsuccessful.


thanks Andrew

 



 


 

Re: trapped error 1002

Andrew Mulholland
 

Thanks for the reply Bob


When I try to import the log I get errors:

Error : Frequency does not appear to be in the 40M Band:  <BAND:3>40M <CALL:6>GI0DVU <CONT:2>EU <CQZ:2>14 <DXCC:3>265 <FREQ:7>.007070 <GRIDSQUARE:6>IO64xm <IOTA:6>EU-115 <ITUZ:2>27 <MODE:3>SSB <NAME:2>N. <OPERATOR:6>MI0BPB <PFX:3>GI0 <QSO_DATE:8:D>19980317 <TIME_ON:6>211600 <QTH:7>IRELAND <RST_RCVD:2>59 <RST_SENT:2>59 <TIME_OFF:6>211600 <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:1>2  <EOR>



These errors are generated from logs brought over from hyperlog years ago, obviously I can edit them (around 700) but just checking that is the simplest way?


The below are the errors I have the feeling may be causing the problem:

Error in the CALL field:  <QSO_DATE:8:D>20140322 <TIME_ON:6>084554 <APP_LOGGER32_QSO_NUMBER:5>26878  <EOR>

 

Error in the CALL field:  <QSO_DATE:8:D>20140330 <TIME_ON:6>101244 <APP_LOGGER32_QSO_NUMBER:5>26982  <EOR>



When I look up the QSO number in Logger and click on them the program jumps the the end of the Log. Is there any way to edit the log outside Logger so I can delete these two entries? See if that sorts the problem?

I tried shouting at the computer but that proved unsuccessful.


thanks Andrew


Re: QSLs SCAN (Suggestions wanted)

Tom Wylie
 

Try Nigel G3TXF


Tom

On Wed, 18 Sep 2019, 19:42 HI3B Radhames, <hi3b@...> wrote:
Hi all: 
I intend to scan thousands of QSL cards.
Obviously I don't just need only a fast scanner, the most important thing should be a  software that automatically extracts data from the cards, to make easier a quick search of a specific QSL in the future. 
Most software brings document samples with fields like invoice number, amount, and soon.
 Who has experience with this? 
What could be my best two options in hardware and software?. 
Most software does not help my purposes.
We accept all the suggestions.
It looks difficult for my project.
Thanks in advance to all.
Radhames (Rada), HI3B 

--
HI3B

QSLs SCAN (Suggestions wanted)

HI3B Radhames
 

Hi all: 
I intend to scan thousands of QSL cards.
Obviously I don't just need only a fast scanner, the most important thing should be a  software that automatically extracts data from the cards, to make easier a quick search of a specific QSL in the future. 
Most software brings document samples with fields like invoice number, amount, and soon.
 Who has experience with this? 
What could be my best two options in hardware and software?. 
Most software does not help my purposes.
We accept all the suggestions.
It looks difficult for my project.
Thanks in advance to all.
Radhames (Rada), HI3B 

--
HI3B

Re: Frequency Display in Logger 32

YV5EN - Edwin
 

Hi Radhames,
Aki is Ok in QRZ.dom.  Please check  https://www.qrz.com/db/JA1NLX

Best 73,
Edwin YV5EN

Re: QUESTION: FIELD 6 AND FIELD 7

larry fields
 

i REMEMBER THE OTHERS AS WELL AS I ENDED UP PUTTING AUSSIES AND JAPAN MANY TIMES..

WAS ALWAYS CURIOUS AS I NEVER TOUCHED THE BOX BUT AS THEY SAY IF THERE IS A WAY THERE IS A REASON

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz
DX1PAR HF NET  7095.00 khz & 7165.0 khz
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08) HT Satellite (-02)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY













On Wed, Sep 18, 2019 at 2:32 AM Bob <k4cy@...> wrote:

Larry, User fields 6 & 7 are not STATE and CNTY by default. It is just a convenient place to put them side by side ... You have to manually configure them ... A word about ADIF nomenclature. Back in the early days of ADIF, the USA was the center of the Universe, so the fields were named STATE and CNTY ... Later other Countries wanted to share their various awards for their equivalents of the US STATE/CNTY ... So, while the ADIF names STATE & CNTY are still used, their meaning has change ... STATE is used for the Primary Administrative Subdivision and CNTY is used for the Secondary Administrative Subdivision ... That is why, if you look at my picture, the USER FIELDS 6 & 7 are labeled PRI  and SEC ... We go to great lengths to confuse the user (it makes us feel important/superior :)  73.

On September 17, 2019 at 10:12 PM larry fields <n6hpx1@...> wrote:

MUCH THANKS FOR THE INFO i NEVER USED THE BOX AS WASN'T SURE WHAT THE PURPOSE WAS.  NOW I KNOW.

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz
DX1PAR HF NET  7095.00 khz & 7165.0 khz
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08) HT Satellite (-02)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY













On Tue, Sep 17, 2019 at 11:15 PM Bob < k4cy@...> wrote:

Larry, they are user defined fields. In my case, I use them to input the ADIF defined STATE/CNTY fields. For me, it looks like this




For those who have no interest, user fields 6 and 7 can be hidden. Right click on any USER FIELD, move the mouse to SETUP and check the option ALLOW AUTOMATIC HEIGHT ADJUSTMENT. If USER FIELD 6 and 7 are not assigned to any ADIF field, the height of the Logbook Entry Window is automagically adjusted to hide the unused fields. SeventyThree(s).

On September 17, 2019 at 6:59 PM larry fields < n6hpx1@...> wrote:

Question on what are these 2 boxes for? you have it in the spot where you add the info. Its right below QTH in the box.

 

 

Re: QUESTION: FIELD 6 AND FIELD 7

Larry Fravel
 

And sometimes you succeed  beyond your wildest expectations! :-D  This what makes logger32 such an excellent program.  The user configurations are many and very useful.

Larry K8YYY

Re: QUESTION: FIELD 6 AND FIELD 7

Bob <k4cy@...>
 

Larry, User fields 6 & 7 are not STATE and CNTY by default. It is just a convenient place to put them side by side ... You have to manually configure them ... A word about ADIF nomenclature. Back in the early days of ADIF, the USA was the center of the Universe, so the fields were named STATE and CNTY ... Later other Countries wanted to share their various awards for their equivalents of the US STATE/CNTY ... So, while the ADIF names STATE & CNTY are still used, their meaning has change ... STATE is used for the Primary Administrative Subdivision and CNTY is used for the Secondary Administrative Subdivision ... That is why, if you look at my picture, the USER FIELDS 6 & 7 are labeled PRI  and SEC ... We go to great lengths to confuse the user (it makes us feel important/superior :)  73.

On September 17, 2019 at 10:12 PM larry fields <n6hpx1@...> wrote:

MUCH THANKS FOR THE INFO i NEVER USED THE BOX AS WASN'T SURE WHAT THE PURPOSE WAS.  NOW I KNOW.

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz
DX1PAR HF NET  7095.00 khz & 7165.0 khz
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08) HT Satellite (-02)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY













On Tue, Sep 17, 2019 at 11:15 PM Bob < k4cy@...> wrote:

Larry, they are user defined fields. In my case, I use them to input the ADIF defined STATE/CNTY fields. For me, it looks like this




For those who have no interest, user fields 6 and 7 can be hidden. Right click on any USER FIELD, move the mouse to SETUP and check the option ALLOW AUTOMATIC HEIGHT ADJUSTMENT. If USER FIELD 6 and 7 are not assigned to any ADIF field, the height of the Logbook Entry Window is automagically adjusted to hide the unused fields. SeventyThree(s).

On September 17, 2019 at 6:59 PM larry fields < n6hpx1@...> wrote:

Question on what are these 2 boxes for? you have it in the spot where you add the info. Its right below QTH in the box.

 

 

Re: QUESTION: FIELD 6 AND FIELD 7

larry fields
 

MUCH THANKS FOR THE INFO i NEVER USED THE BOX AS WASN'T SURE WHAT THE PURPOSE WAS.  NOW I KNOW.

Thanks and 73
Larry Fields: du1/n6hpx
Manila PHILIPPINES

Retired looking for more work
Office:(63)46-571-5687
cell:    (63)916-756-7781
=====================================================
member:
American Radio Relay League W1AW
Philippine Amatuer Radio Association DX1PAR
Philippine Radio Pyramid Society DX1PRS 
=====================================================
owner:
=======================================================
LICENSED HAM RADIO OP:
DX1PRS GROUP 145.340 mhz
DX1PAR HF NET  7095.00 khz & 7165.0 khz
========================================================
DU1/N6HPX:QRX DX1PAR 7095
DX1PRS 7165 khz evening
DX1PRS 145.340 mhz
DX1L 431.9,
SIMPLEX 144.6, 145.600
2M 144.225 SSB ,
APRS n6hpx(-08) HT Satellite (-02)
=============================================================
SATELLITE:
APRS N6HPX-2 GATEWAY













On Tue, Sep 17, 2019 at 11:15 PM Bob <k4cy@...> wrote:

Larry, they are user defined fields. In my case, I use them to input the ADIF defined STATE/CNTY fields. For me, it looks like this




For those who have no interest, user fields 6 and 7 can be hidden. Right click on any USER FIELD, move the mouse to SETUP and check the option ALLOW AUTOMATIC HEIGHT ADJUSTMENT. If USER FIELD 6 and 7 are not assigned to any ADIF field, the height of the Logbook Entry Window is automagically adjusted to hide the unused fields. SeventyThree(s).

On September 17, 2019 at 6:59 PM larry fields <n6hpx1@...> wrote:

Question on what are these 2 boxes for? you have it in the spot where you add the info. Its right below QTH in the box.

Re: Frequency Display in Logger 32

ja1nlx
 

Fred

Good to hear that.  Enjoy !

73

On 2019/09/18 9:45, K4LQ - Fred wrote:
Thanks Aki, your recommended solution worked fine!
73/Fred K4LQ
--
73 de aki
JA1NLX

Re: Frequency Display in Logger 32

K4LQ - Fred
 

Thanks Aki, your recommended solution worked fine!
73/Fred K4LQ

Re: Frequency Display in Logger 32

HI3B Radhames
 

Hello Aki:

How I could contact you directly.
You're not at qrz.com.
Thanks,

Rada, HI3B
hi3b@...


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of ja1nlx <ayoshida0205@...>
Sent: Tuesday, September 17, 2019 7:55 PM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Frequency Display in Logger 32
 

Fred

Click Setup in main menu. Click Frequency and check "Show frequency display and log frequency"

73

On 2019/09/18 8:31, K4LQ - Fred wrote:
Recently lost the output on my remote jack on my Icom 756 Pro ll transceiver. Had it repaired.  Now i get good frequency display  on the computer from N1MM+ and WSJT but not from Logger 32.  The computer displays correct band and mode in Logger 32 but not frequency.  Settings that work correctly in  the other two logging programs are Com 7,9600, Icom, 8, 1. None, DTR high, RTS high, Polling 200, icom address 64.  Using these settings in Logger 32 does not result in a frequency displaY.  Any recommendations as to how i get my frequency display back?
73/FredK4LQ
--
73 de aki
JA1NLX

--
HI3B

Re: Frequency Display in Logger 32

ja1nlx
 

Fred

Click Setup in main menu. Click Frequency and check "Show frequency display and log frequency"

73

On 2019/09/18 8:31, K4LQ - Fred wrote:
Recently lost the output on my remote jack on my Icom 756 Pro ll transceiver. Had it repaired.  Now i get good frequency display  on the computer from N1MM+ and WSJT but not from Logger 32.  The computer displays correct band and mode in Logger 32 but not frequency.  Settings that work correctly in  the other two logging programs are Com 7,9600, Icom, 8, 1. None, DTR high, RTS high, Polling 200, icom address 64.  Using these settings in Logger 32 does not result in a frequency displaY.  Any recommendations as to how i get my frequency display back?
73/FredK4LQ
--
73 de aki
JA1NLX

Frequency Display in Logger 32

K4LQ - Fred
 

Recently lost the output on my remote jack on my Icom 756 Pro ll transceiver. Had it repaired.  Now i get good frequency display  on the computer from N1MM+ and WSJT but not from Logger 32.  The computer displays correct band and mode in Logger 32 but not frequency.  Settings that work correctly in  the other two logging programs are Com 7,9600, Icom, 8, 1. None, DTR high, RTS high, Polling 200, icom address 64.  Using these settings in Logger 32 does not result in a frequency displaY.  Any recommendations as to how i get my frequency display back?
73/FredK4LQ

Re: QUESTION: FIELD 6 AND FIELD 7

Bob <k4cy@...>
 

Larry, they are user defined fields. In my case, I use them to input the ADIF defined STATE/CNTY fields. For me, it looks like this




For those who have no interest, user fields 6 and 7 can be hidden. Right click on any USER FIELD, move the mouse to SETUP and check the option ALLOW AUTOMATIC HEIGHT ADJUSTMENT. If USER FIELD 6 and 7 are not assigned to any ADIF field, the height of the Logbook Entry Window is automagically adjusted to hide the unused fields. SeventyThree(s).

On September 17, 2019 at 6:59 PM larry fields <n6hpx1@...> wrote:

Question on what are these 2 boxes for? you have it in the spot where you add the info. Its right below QTH in the box.

QUESTION: FIELD 6 AND FIELD 7

larry fields
 

Question on what are these 2 boxes for? you have it in the spot where you add the info. Its right below QTH in the box.

Re: Changed callsign

Mihai Ioan
 

OK. Thanks Bob !!!

On Tuesday, September 17, 2019, 10:48:32 PM GMT+3, Bob <k4cy@...> wrote:


Click FILE | CHANGE CALLSIGN. Change the OPERATOR from YO7CVL to YO7CW. Click APPLY. Right click on the WORKED/CONFIRMED Window. UNcheck the option SHOW DXCC INFO FOR YO7CW (maybe it says DXCC_MIXED, or DXCC_CW). Right click on the PREVIOUS QSOs Window and UNcheck the option SJOW QSOs for YO7CW only. Now log your QSOs. 73.

On September 17, 2019 at 3:04 PM "Mihai Ioan via Groups.Io" <yo7cvl@...> wrote:

Hi,
I have change my callsign from YO7CVL in YO7CW.
I want to add QSOs made with my new callsign (YO7CW) to the old logbook (YO7CVL). I need to merge the too logbooks so that the QSOs with the new callsign are taken into consideration with the QSOs made with the old callsign
for awards.


Thanks,
Miki, YO7CW (ex YO7CVL)


 


 

Re: Changed callsign

Bob <k4cy@...>
 

Click FILE | CHANGE CALLSIGN. Change the OPERATOR from YO7CVL to YO7CW. Click APPLY. Right click on the WORKED/CONFIRMED Window. UNcheck the option SHOW DXCC INFO FOR YO7CW (maybe it says DXCC_MIXED, or DXCC_CW). Right click on the PREVIOUS QSOs Window and UNcheck the option SJOW QSOs for YO7CW only. Now log your QSOs. 73.

On September 17, 2019 at 3:04 PM "Mihai Ioan via Groups.Io" <yo7cvl@...> wrote:

Hi,
I have change my callsign from YO7CVL in YO7CW.
I want to add QSOs made with my new callsign (YO7CW) to the old logbook (YO7CVL). I need to merge the too logbooks so that the QSOs with the new callsign are taken into consideration with the QSOs made with the old callsign
for awards.


Thanks,
Miki, YO7CW (ex YO7CVL)