Date   

Re: error message

Bob
 

Larry, you are more, much more, than temporarily stuck. You are up shit creek, and I'm sad to have to be the one to break it to you, but you don't have a paddle. Your logbook file on disk is not just corrupted, it is broken and a 4Kb piece of the data in the middle of the file is missing (that is what the error message 2005 and 1002 was saying). Other than that, it's a wonderful day in the neighborhood (who said that Mr. Rogers?). Bottom line Larry, if you don't have another backup, or any other ADIF files, that you haven't mentioned, you have 5200 QSOs, and the rest have just been deep sixed. 73.

On October 24, 2019 at 6:19 PM larry fields <n6hpx1@...> wrote:

some are paper logs but not sure how you mean I broke it..I tried to transfer the adif to a separate file and it only shows 5200 in the transfer..the problem when as mentioned before it had duplicates of callsigns, and those calls were of stations like 3 in a row or 6 in a row. I deleted those contacts. Clublog even mentioned it that I had too many duplicates. So I am temporary stuck on this..

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 Thu, Oct 24, 2019 at 11:18 AM Bob < k4cy@...> wrote:

Larry, you have broken your logbook. This time badly. Do you have backup copies of your logbook of ADIF files you can use to recover? 73.

On October 24, 2019 at 5:12 AM larry fields < n6hpx1@...> wrote:

been working on correcting problems on the log, Some duplicates as mentioned before I never made. But when I try to do the update of the log it comes up with a error message.

Message on the error is db Error:vis_other_message(2005)

source module:do update complex keys
logger32 errornum:1002

when I do the recalculation it stops at 16% (says completed) doesn't see my added 2019 contacts
what can I do to correct it.

I am nervous of deleting it as the log has 10,462 in it.

 

 


Re: error message

Bob
 

Larry, one question at a time ... Do you have a backup of your logbook or an ADIF backup? 73.

On October 24, 2019 at 6:51 PM larry fields <n6hpx1@...> wrote:

when I try to delete to reboot the program the computer doesn't even show it even exists and yet it loads up, this is getting crazy as I was trying to clean up the log so I can use it. As mentioned before the log showed me making 6m contacts to Sri Lanka that didn't even happen, and other contacts where I mad qso's of the same callsigns 3 to 6 in a row and never even made that contact that many times. 

I am still checking this out but not sure how you mean I broke the log.

One project I been doing was adding the grid squares and countries and after that I tried to do the update in the log and thats when this problem came up.
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 Thu, Oct 24, 2019 at 10:19 PM larry fields via Groups.Io <n6hpx1= gmail.com@groups.io> wrote:
some are paper logs but not sure how you mean I broke it..I tried to transfer the adif to a separate file and it only shows 5200 in the transfer..the problem when as mentioned before it had duplicates of callsigns, and those calls were of stations like 3 in a row or 6 in a row. I deleted those contacts. Clublog even mentioned it that I had too many duplicates. So I am temporary stuck on this..

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 Thu, Oct 24, 2019 at 11:18 AM Bob < k4cy@...> wrote:

Larry, you have broken your logbook. This time badly. Do you have backup copies of your logbook of ADIF files you can use to recover? 73.

On October 24, 2019 at 5:12 AM larry fields < n6hpx1@...> wrote:

been working on correcting problems on the log, Some duplicates as mentioned before I never made. But when I try to do the update of the log it comes up with a error message.

Message on the error is db Error:vis_other_message(2005)

source module:do update complex keys
logger32 errornum:1002

when I do the recalculation it stops at 16% (says completed) doesn't see my added 2019 contacts
what can I do to correct it.

I am nervous of deleting it as the log has 10,462 in it.

 

 

 

 


Re: error message

larry fields
 

when I try to delete to reboot the program the computer doesn't even show it even exists and yet it loads up, this is getting crazy as I was trying to clean up the log so I can use it. As mentioned before the log showed me making 6m contacts to Sri Lanka that didn't even happen, and other contacts where I mad qso's of the same callsigns 3 to 6 in a row and never even made that contact that many times. 

I am still checking this out but not sure how you mean I broke the log.

One project I been doing was adding the grid squares and countries and after that I tried to do the update in the log and thats when this problem came up.
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 Thu, Oct 24, 2019 at 10:19 PM larry fields via Groups.Io <n6hpx1=gmail.com@groups.io> wrote:
some are paper logs but not sure how you mean I broke it..I tried to transfer the adif to a separate file and it only shows 5200 in the transfer..the problem when as mentioned before it had duplicates of callsigns, and those calls were of stations like 3 in a row or 6 in a row. I deleted those contacts. Clublog even mentioned it that I had too many duplicates. So I am temporary stuck on this..

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 Thu, Oct 24, 2019 at 11:18 AM Bob <k4cy@...> wrote:

Larry, you have broken your logbook. This time badly. Do you have backup copies of your logbook of ADIF files you can use to recover? 73.

On October 24, 2019 at 5:12 AM larry fields <n6hpx1@...> wrote:

been working on correcting problems on the log, Some duplicates as mentioned before I never made. But when I try to do the update of the log it comes up with a error message.

Message on the error is db Error:vis_other_message(2005)

source module:do update complex keys
logger32 errornum:1002

when I do the recalculation it stops at 16% (says completed) doesn't see my added 2019 contacts
what can I do to correct it.

I am nervous of deleting it as the log has 10,462 in it.


Re: error message

larry fields
 

some are paper logs but not sure how you mean I broke it..I tried to transfer the adif to a separate file and it only shows 5200 in the transfer..the problem when as mentioned before it had duplicates of callsigns, and those calls were of stations like 3 in a row or 6 in a row. I deleted those contacts. Clublog even mentioned it that I had too many duplicates. So I am temporary stuck on this..

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 Thu, Oct 24, 2019 at 11:18 AM Bob <k4cy@...> wrote:

Larry, you have broken your logbook. This time badly. Do you have backup copies of your logbook of ADIF files you can use to recover? 73.

On October 24, 2019 at 5:12 AM larry fields <n6hpx1@...> wrote:

been working on correcting problems on the log, Some duplicates as mentioned before I never made. But when I try to do the update of the log it comes up with a error message.

Message on the error is db Error:vis_other_message(2005)

source module:do update complex keys
logger32 errornum:1002

when I do the recalculation it stops at 16% (says completed) doesn't see my added 2019 contacts
what can I do to correct it.

I am nervous of deleting it as the log has 10,462 in it.


Re: DX Filters on Comments

Gary Hinson
 

thANKs bOb

 

73

gARy  zl2Ifb

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 25 October 2019 00:12
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Gary, they are NOT case sensitive. *SOTA* and *SoTa* are the same. SeventyThree(s).

On October 24, 2019 at 1:20 AM Gary Hinson <Gary@...> wrote:

Easy peasy when you know how!

 

I’m being alerted to DXcluster spots with comments that mention SOTA using the alerting string *SOTA*

 

 

I hope I would also get alerts for Bear Island and Shetland Island spot comments (both separate entities for CQ but not for DXCC) although I wonder if the alerting strings are case-sensitive …  I haven’t checked them yet since they are both as rare as hen’s teeth and I don’t like to generate fake cluster spots.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 24 October 2019 16:05
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim, I've never tried it, but in theory, it works like this:

 

RTTY  Blocks DX Spots where the comment text is RTTY.

RTTY*  Blocks DX Spots where the comment text starts with RTTY.

*RTTY  Blocks DX Spots where the comment text ends with RTTY

*RTTY*  Blocks DX Spots where RTTY is somewhere in the comment text.

 

SeventyThree(s).

On October 23, 2019 at 9:02 PM Jim Altman <jaltman636@...> wrote:

I will try it, thanks.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Wednesday, October 23, 2019 8:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim

Try *RTTY* instead of RTTY.

73

On 2019/10/24 9:29, Jim Altman wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

 

 


 


 

 

 


 


 


Re: [ham logger] 3 transceivers

N4IS
 

Hi Neil

I am using UCXlog , it supports 5 radios. Not a rocket science to do that. I backup QSO's between Logger32 and UCXlog. Most HF with Logger32 and VHF up with UCXlog.


73's
JC
N4IS

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Neil, G3RIR
Sent: Thursday, October 24, 2019 4:00 AM
To: hamlogger@groups.io
Subject: [hamlogger] 3 transceivers

Can I have more than 2 radios set up in Logger32? I have IC7610 for HF, IC7300 for 6m and 4m and TS2000X for 144,432 and 1296. I would like to be able to switch between these in Logger32. Is it possible?
Neil G3RIR


Re: error message

Bob
 

Larry, you have broken your logbook. This time badly. Do you have backup copies of your logbook of ADIF files you can use to recover? 73.

On October 24, 2019 at 5:12 AM larry fields <n6hpx1@...> wrote:

been working on correcting problems on the log, Some duplicates as mentioned before I never made. But when I try to do the update of the log it comes up with a error message.

Message on the error is db Error:vis_other_message(2005)

source module:do update complex keys
logger32 errornum:1002

when I do the recalculation it stops at 16% (says completed) doesn't see my added 2019 contacts
what can I do to correct it.

I am nervous of deleting it as the log has 10,462 in it.


Re: DX Filters on Comments

Bob
 

Gary, they are NOT case sensitive. *SOTA* and *SoTa* are the same. SeventyThree(s).

On October 24, 2019 at 1:20 AM Gary Hinson <Gary@...> wrote:

Easy peasy when you know how!

 

I’m being alerted to DXcluster spots with comments that mention SOTA using the alerting string *SOTA*

 

 

I hope I would also get alerts for Bear Island and Shetland Island spot comments (both separate entities for CQ but not for DXCC) although I wonder if the alerting strings are case-sensitive …  I haven’t checked them yet since they are both as rare as hen’s teeth and I don’t like to generate fake cluster spots.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 24 October 2019 16:05
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim, I've never tried it, but in theory, it works like this:

 

RTTY  Blocks DX Spots where the comment text is RTTY.

RTTY*  Blocks DX Spots where the comment text starts with RTTY.

*RTTY  Blocks DX Spots where the comment text ends with RTTY

*RTTY*  Blocks DX Spots where RTTY is somewhere in the comment text.

 

SeventyThree(s).

On October 23, 2019 at 9:02 PM Jim Altman <jaltman636@...> wrote:

I will try it, thanks.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Wednesday, October 23, 2019 8:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim

Try *RTTY* instead of RTTY.

73

On 2019/10/24 9:29, Jim Altman wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

 

 


 


 

 



 


 


Re: DX Filters on Comments

Jim Altman
 

Thanks guys!

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: Thursday, October 24, 2019 1:20 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Easy peasy when you know how!

 

I’m being alerted to DXcluster spots with comments that mention SOTA using the alerting string *SOTA*

 

 

I hope I would also get alerts for Bear Island and Shetland Island spot comments (both separate entities for CQ but not for DXCC) although I wonder if the alerting strings are case-sensitive …  I haven’t checked them yet since they are both as rare as hen’s teeth and I don’t like to generate fake cluster spots.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 24 October 2019 16:05
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim, I've never tried it, but in theory, it works like this:

 

RTTY  Blocks DX Spots where the comment text is RTTY.

RTTY*  Blocks DX Spots where the comment text starts with RTTY.

*RTTY  Blocks DX Spots where the comment text ends with RTTY

*RTTY*  Blocks DX Spots where RTTY is somewhere in the comment text.

 

SeventyThree(s).

On October 23, 2019 at 9:02 PM Jim Altman <jaltman636@...> wrote:

I will try it, thanks.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Wednesday, October 23, 2019 8:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim

Try *RTTY* instead of RTTY.

73

On 2019/10/24 9:29, Jim Altman wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

 

 


 


 


error message

larry fields
 

been working on correcting problems on the log, Some duplicates as mentioned before I never made. But when I try to do the update of the log it comes up with a error message.

Message on the error is db Error:vis_other_message(2005)

source module:do update complex keys
logger32 errornum:1002

when I do the recalculation it stops at 16% (says completed) doesn't see my added 2019 contacts
what can I do to correct it.

I am nervous of deleting it as the log has 10,462 in it.


Re: 3 transceivers

ja1nlx
 

Neil

No Logger32 does not support it.

However you can set up 2nd INI, 3rd INI etc. See section "Setting up a second Logger32 INI file"

in Logger32 Help.

I use Logger32_K3, Logger32_IC7610 and Logger32_TS480 etc.

73

On 2019/10/24 17:00, Neil, G3RIR wrote:
Can I have more than 2 radios set up in Logger32? I have IC7610 for HF, IC7300 for 6m and 4m and TS2000X for 144,432 and 1296. I would like to be able to switch between these in Logger32. Is it possible?
Neil G3RIR


--
73 de aki
JA1NLX


3 transceivers

Neil, G3RIR <neil.g3rir@...>
 

Can I have more than 2 radios set up in Logger32? I have IC7610 for HF, IC7300 for 6m and 4m and TS2000X for 144,432 and 1296. I would like to be able to switch between these in Logger32. Is it possible?
Neil G3RIR


Re: DX Filters on Comments

Gary Hinson
 

Easy peasy when you know how!

 

I’m being alerted to DXcluster spots with comments that mention SOTA using the alerting string *SOTA*

 

 

I hope I would also get alerts for Bear Island and Shetland Island spot comments (both separate entities for CQ but not for DXCC) although I wonder if the alerting strings are case-sensitive …  I haven’t checked them yet since they are both as rare as hen’s teeth and I don’t like to generate fake cluster spots.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 24 October 2019 16:05
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim, I've never tried it, but in theory, it works like this:

 

RTTY  Blocks DX Spots where the comment text is RTTY.

RTTY*  Blocks DX Spots where the comment text starts with RTTY.

*RTTY  Blocks DX Spots where the comment text ends with RTTY

*RTTY*  Blocks DX Spots where RTTY is somewhere in the comment text.

 

SeventyThree(s).

On October 23, 2019 at 9:02 PM Jim Altman <jaltman636@...> wrote:

I will try it, thanks.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Wednesday, October 23, 2019 8:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim

Try *RTTY* instead of RTTY.

73

On 2019/10/24 9:29, Jim Altman wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

 

 


 


 


Re: DX Filters on Comments

Bob
 

Jim, I've never tried it, but in theory, it works like this:


RTTY  Blocks DX Spots where the comment text is RTTY.

RTTY*  Blocks DX Spots where the comment text starts with RTTY.

*RTTY  Blocks DX Spots where the comment text ends with RTTY

*RTTY*  Blocks DX Spots where RTTY is somewhere in the comment text.


SeventyThree(s).

On October 23, 2019 at 9:02 PM Jim Altman <jaltman636@...> wrote:

I will try it, thanks.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Wednesday, October 23, 2019 8:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim

Try *RTTY* instead of RTTY.

73

On 2019/10/24 9:29, Jim Altman wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX

 



 


 


Re: DX Filters on Comments

Bob
 

Jim, your filter will block DX Spots where the comment field is RTTY. You probably want to block DX Spots that contain the word/text RTTY ... Try something like *RTTY* ... SeventyThree(s).

On October 23, 2019 at 8:29 PM Jim Altman <jaltman636@...> wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 


 


 


Re: DX Filters on Comments

Jim Altman
 

I will try it, thanks.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ja1nlx
Sent: Wednesday, October 23, 2019 8:33 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] DX Filters on Comments

 

Jim

Try *RTTY* instead of RTTY.

73

On 2019/10/24 9:29, Jim Altman wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX


Re: DX Filters on Comments

ja1nlx
 

Jim

Try *RTTY* instead of RTTY.

73

On 2019/10/24 9:29, Jim Altman wrote:

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX


DX Filters on Comments

Jim Altman
 

I have set a filter on dx spots to filter out spots that have RTTY in the comment field.  I still see comments that contain RTTY.  Is it case sensitive?  Can it occur anywhere in the string ?  I don’t want to filter based on the band plan, because there are non-rtty spots in the rtty portions of the band I want to see.  See picture attached.

 

73

 

Jim Altman

jaltman636@...

 


Re: FT-8 & Logger32

Paul Bigwood <paul@...>
 


JA1NLK Thanks for the Help File update.

Got the blocked access error and after unblocking still did not work, complaining that there was a mismatch with Logger32.chi. I simply renamed it Logger32_old.chi and restarted Logger32. 

Help file now works fine. Thanks

73 de Paul G3WYW


Re: Help! L32 not showing split frequencies

Bob
 

You said: Using  other logging software, I can log both the  rx and tx frequencies when I operate split


I have no idea what options other logging programs offer/provide to log split frequency, but do this: On the Radio Control Panel, right click on the header (it is at the right of the window to save precious screen space). Click the LOGGING FREQUENCY SETUP menu option. There are several options there that may suit your needs. If not, let me know exactly what you want, and I'll put it on the (very long) wish list. SeventyThree(s).

On October 22, 2019 at 5:47 PM "Bob Elek via Groups.Io" <w3hkk@...> wrote:

When I work DX split , my L32  shows  the same freq in both the  “Freq” and “Freq_Rx” columns of my log.   Among the choices  of columns there is no  Freq_Tx.”  

 

Using  other logging software, I can  log   both the  rx and tx frequencies when I operate split.

 

Whats up?

 

 

Sent from Mail for Windows 10

 

From: Ken JN7FAH
Sent: Tuesday, October 22, 2019 5:26 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Export UQF(.asc) file

 

Bob

 

ASCII file export future of L32 3.50.398 is now perfect.

Thanks

 

73

Ken JN7FAH

ex JA0RYN, JA0RYN/7, DL/JA0RYN

 

 

20191015() 9:26 Bob <k4cy@...>:

Ken, I will look at this tomorrow, but while you wait, answer me this question ... I Googled this: How many of the Japanese rugby team are actually Japanese ... Google said this: 

 

 

Do you think maybe they're trying to avoid answering the question? SeventyThree(s).

 

On October 14, 2019 at 7:37 PM Ken JN7FAH <jn7fah@...> wrote:

Bob,

 

I found bugs in [File] menu, Export Logs/Export UQF(.asc) file.

 

As shown below, when I chose this menu the box showing 

"Including this end date" isn't the present date. 

Then, I pull down date selection window as shown below, it

is apparent that, in this section, L32 refers the last two digits

of system year for DAY and system day for YEAR.

 

It is 8:00 in the local time 1 hour behind 2019-10-15 00:00 UTC. 

I think, you know why the present date of L32 is a day before UTC.

 

Next, the extension of UQF exported file is not .asc, but

it is .uqf as shown below. 

The file name should be "20191014.asc".

 

 

This function is quite useful to export QSO records of

a certain station.

If possible, let me request to add callsign or country

selection appears in Exporting ADIF(.adi) file section.  

 

73

Ken JN7FAH

ex JA0RYN, JA0RYN/7, DL/JA0RYN

 

 


 


 

7321 - 7340 of 85149