Date   
Re: Problem

Bob
 

Two things - First point, the option to set WSJT/JTDX on-top must be configured. On the UDP BandMap Click START (or STOP). Click SETUP SHORTCUTS. At the bottom of the SETUP START MENUS check START WSJT/JTDX ON-TOP option. Click the APPLY button. If this option is checked, then starting WSJT/JTDX from Logger32 will send the command to WSJT/JTDX to be on-top. Second point, when Logger32 starts WSJT/JTDX (you will notice after four/five seconds that The caption of WSJT/JTDX changes to be WSJT/JTDX & LOGGER32. If/when you see this, you know Logger has successfully started WSJT/JTDX and is able to send commands to the main Window. First it sends a command to change the caption. Second it sends a command to disable the X (top right corner button), and third it sends a command to place the WSJT/JTDX window on-top. If WSJT/JTDX does as it is told, yay! If it doesn't, so sad. SeventyThree(s).

On October 12, 2019 at 1:15 PM Dave Colliau <n8dc-8@...> wrote:


My friend is running win7 and he says even with the box checked for wsjt-x and jtdx to run on top wsjt-x keeps hiding if he clicks somewhere else in Logger 32.
I have win10 and its fine here ?
Any ideas.
Dave N8DC


Problem

Dave Colliau
 

My friend is running win7 and he says even with the box checked for wsjt-x and jtdx to run on top wsjt-x keeps hiding if he clicks somewhere else in Logger 32.
I have win10 and its fine here ?
Any ideas.
Dave N8DC

Re: Error Message

Colin
 

OK, problem solved, I think.

The offset frequency of 21141.72 was appearing in the logbook page but the band wasn't appearing.   Changing the entry in the Band/Modes table from 21140 -21140 to 21140 - 21142 seems to have solved it.

Thanks for pointing me in the right direction BoB.

73

Colin, G3PSM


On Sat, 12 Oct 2019 at 14:48, Bob <k4cy@...> wrote:

... the error message text should be:

I am about to reset the complex keys in the database and have temporarily lost track of data for your QSO with callsign on band mode 


I see no band in your report. So, Logger32 didn't see 15M in the modified record and decided not to change the QSO as requested. SeventyThree(s).

On October 12, 2019 at 9:20 AM Colin <colin.g3psm@...> wrote:


Hi all,

I have suddenly started getting the following error message, strangely
enough when I started using FT4 on 21140 kHz.   That might be
coincidence though -

"It's my fault, I'm getting old and forgetful

I am about to reset the complex keys in the database and have
temporarily lost track of data for your QSO with (whatever callsign) on FT4.

dbBusy flag is set to false

I have not modified your logbook.   Please try this again."

Thoughts please?

73

Colin, G3PSM



Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#77803): https://groups.io/g/hamlogger/message/77803
Mute This Topic: https://groups.io/mt/34510691/849411
Group Owner: hamlogger+owner@groups.io
Unsubscribe: https://groups.io/g/hamlogger/leave/defanged [k4cy@...]

Re: Error Message

Bob
 

... the error message text should be:

I am about to reset the complex keys in the database and have temporarily lost track of data for your QSO with callsign on band mode 


I see no band in your report. So, Logger32 didn't see 15M in the modified record and decided not to change the QSO as requested. SeventyThree(s).

On October 12, 2019 at 9:20 AM Colin <colin.g3psm@...> wrote:


Hi all,

I have suddenly started getting the following error message, strangely
enough when I started using FT4 on 21140 kHz.   That might be
coincidence though -

"It's my fault, I'm getting old and forgetful

I am about to reset the complex keys in the database and have
temporarily lost track of data for your QSO with (whatever callsign) on FT4.

dbBusy flag is set to false

I have not modified your logbook.   Please try this again."

Thoughts please?

73

Colin, G3PSM



Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#77803): https://groups.io/g/hamlogger/message/77803
Mute This Topic: https://groups.io/mt/34510691/849411
Group Owner: hamlogger+owner@groups.io
Unsubscribe: https://groups.io/g/hamlogger/leave/defanged [k4cy@...]

Re: Error Message

Bob
 

... what were you attempting to do when the error occurred? It looks like you were attempting to modify a previously entered QSO in the Logbook. Before actually making the change, Logger32 checked that there was a callsign, a band, and a mode in the new record it was going to overwrite the existing. One of those three fields was missing. It's probably not a good idea to change the QSO with one of those three missing. Did you try again, and what happened? SeventyThree(s).

On October 12, 2019 at 9:20 AM Colin <colin.g3psm@...> wrote:


Hi all,

I have suddenly started getting the following error message, strangely
enough when I started using FT4 on 21140 kHz.   That might be
coincidence though -

"It's my fault, I'm getting old and forgetful

I am about to reset the complex keys in the database and have
temporarily lost track of data for your QSO with (whatever callsign) on FT4.

dbBusy flag is set to false

I have not modified your logbook.   Please try this again."

Thoughts please?

73

Colin, G3PSM




Error Message

Colin
 

Hi all,

I have suddenly started getting the following error message, strangely enough when I started using FT4 on 21140 kHz.   That might be coincidence though -

"It's my fault, I'm getting old and forgetful

I am about to reset the complex keys in the database and have temporarily lost track of data for your QSO with (whatever callsign) on FT4.

dbBusy flag is set to false

I have not modified your logbook.   Please try this again."

Thoughts please?

73

Colin, G3PSM

Re: UDP Bandmap Highlight Worked Before

Bob
 

Is there any way to highlight a station worked before in the UDP bandmap other than the "X" that appears next to the call sign?


Yes, click the option SHOW/BLOCK CALLSIGNS WORKED BEFORE. Then check the option BLOCK SELECTED CALLSIGNS QSOD B4. With this combination you only see stations not worked B4. SeventyThree(s).

On October 11, 2019 at 4:57 PM Gary Hinson <Gary@...> wrote:

The bold X works fine for me, Art, coupled with the multicolour highlighting of ‘new ones’ (new DXCCs or grid on this band, new this mode, new this year, ATNOs …), bold text for stations that have been CQing, and the green blobs for LoTW users (or rather, in my case, FOC members).

 

A quick glance down the column tells me that, so far this year, I’ve already worked just 4 of the 20+ stations on 20m FT8 right now …

 

 

… while the absence of coloured highlighting tells me there are no new DXCCs or FOC members to work at the moment, unfortunately.

 

If you are hinting at maybe using coloured highlighting or text to indicate ‘worked before’, that would need fit in with the ‘new DXCC’ indications, which are already quite complex.  Bob has given us loads of useful info already: for me, as a keen DXer, it’s one of the best features of Logger32 to be able to see juicy morsels of DX hiding among the krill.   Or not.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Art - VE3UTT / W1AJT
Sent: 12 October 2019 01:12
To: hamlogger@groups.io
Subject: [hamlogger] UDP Bandmap Highlight Worked Before

 

Hello,
Is there any way to highlight a station worked before in the UDP bandmap other than the "X" that appears next to the call sign?  For FT modes it would enable quicker identification of stations worked before.  I know the grids can be highlighted for various characteristics and that works well.

Thanks & 73,
Art - W1AJT / VE3UTT

 



 


 

Re: UDP Bandmap Highlight Worked Before

Gary Hinson
 

The bold X works fine for me, Art, coupled with the multicolour highlighting of ‘new ones’ (new DXCCs or grid on this band, new this mode, new this year, ATNOs …), bold text for stations that have been CQing, and the green blobs for LoTW users (or rather, in my case, FOC members).

 

A quick glance down the column tells me that, so far this year, I’ve already worked just 4 of the 20+ stations on 20m FT8 right now …

 

 

… while the absence of coloured highlighting tells me there are no new DXCCs or FOC members to work at the moment, unfortunately.

 

If you are hinting at maybe using coloured highlighting or text to indicate ‘worked before’, that would need fit in with the ‘new DXCC’ indications, which are already quite complex.  Bob has given us loads of useful info already: for me, as a keen DXer, it’s one of the best features of Logger32 to be able to see juicy morsels of DX hiding among the krill.   Or not.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Art - VE3UTT / W1AJT
Sent: 12 October 2019 01:12
To: hamlogger@groups.io
Subject: [hamlogger] UDP Bandmap Highlight Worked Before

 

Hello,
Is there any way to highlight a station worked before in the UDP bandmap other than the "X" that appears next to the call sign?  For FT modes it would enable quicker identification of stations worked before.  I know the grids can be highlighted for various characteristics and that works well.

Thanks & 73,
Art - W1AJT / VE3UTT

UDP Bandmap Highlight Worked Before

Art - VE3UTT / W1AJT
 

Hello,
Is there any way to highlight a station worked before in the UDP bandmap other than the "X" that appears next to the call sign?  For FT modes it would enable quicker identification of stations worked before.  I know the grids can be highlighted for various characteristics and that works well.

Thanks & 73,
Art - W1AJT / VE3UTT

Re: Time sync error

Bob
 

Jim, I connect to ROLEX.USG.EDU. To simulate your report, I changed the address to ROLEX.USG.EDUXX. Now, I see this error




It would appear that your Chernobyl like Error 5 is not caused by simple failure to connect, but by receipt of unexpected data (which I have never seen from USG.EDU). Shooting in the dark, I have added additional error checking to the SNTP code. SeventyThree(s).

On October 10, 2019 at 6:08 AM Jim Altman <jaltman636@...> wrote:

Lately, if you have the ‘set time on udp bandmap open’ ticked, if it fails to get the time, it generates a runtime error 5 and the program crashes.

 

73

 

 

Jim Altman

jaltman636@...

 


 


 

logger problem corrected

larry fields
 

Wish to thank N2AMG for his work last night and help in correcting my logging program. I been trying to correct some problems and kept getting multi boxes of Password/Name not correct. When I attempted to use XML the password was in CAPS vice the other HTTP was not. As a result was where the boxes were coming up.

After 1 1/2 hours we came to the conclusion that the 2 passwords were the problem and once changed it came up each time.

since then I have managed to add 2000 Grids and eliminate other problems.

N2AMG Thanks for the help on this and I am back to normal(or semi normal) 

Time sync error

Jim Altman
 

Lately, if you have the ‘set time on udp bandmap open’ ticked, if it fails to get the time, it generates a runtime error 5 and the program crashes.

 

73

 

 

Jim Altman

jaltman636@...

 

Re: Double in the log...

Bob
 

Steph, if it works, enjoy. SeventyThree(s).

On October 9, 2019 at 3:02 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi Bob,

 

I can not contradict you, technically, but I am pragmatic and what I have described, in my case at least works perfectly.

 

The double entries have been deleted (+5000 entries).

 

But mebbe there is a confusion…

 

In my .ADI file, some fields <RST_RCVD:3>, was missing.

 

The “empty” fields was in the Previous Logbook page.

 

When I GREP only the <RST_RCVD:3> from my “original” Logbook.ADI file, then exported into a Logbook-corrected.ADI, then created a new Logbook, then import the Logbook-corrected.ADI file, the double entries in the Previous.

 

I don’t know if I am clear?

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 9 octobre 2019 18:50
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

If you add <RST_RCVD:3> to the QSO record, the RST_RCVD will be the next three characters after <RST_RCVD:3> For example, it the QSO record is <RST_RCVD:3> CALL:5>F5NZY .... then RCD_RCVD is read as " CA". SeventyThree(s).

On October 9, 2019 at 12:41 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Bob,

 

It Is corresponding to the received RST.

 

When I had double entries in my logbook, the value was empty.

 

Since the description of what I did, have no more such double entries.

 

It is not correct?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 9 octobre 2019 17:16
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, are you sure? Look in your logbook and see what is in the RST_RCVD field. SeventyThree(s).

On October 9, 2019 at 8:48 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Never Say Die!

 

I found how to proceed to remove my double entries in my LogBook and to get back with a clean one.

 

I studied my .ADI file and noticed, that for the wrong entries, the field <RST_RCVD:3> was missing.

 

So, easy to solve it!

 

I use Cygwin, a Linux Emulator on Windows 10, (https://cygwin.com/).

 

The way to proceed is as follow:

 

  • Export your full LogBook in .ADI file
  • With Cygwin, type the commands: cat your_file.ADI | grep "<RST_RCVD:3>" >your_file-corrected.ADI
  • Create a new LogBook
  • Import your new LogBook-corrected.ADI file
  • I rebuilt the database

 

I lost more than 5,000 entries in my LogBook, but now, it is Clean!

 

😉

 

Hope it helps!

 

73 de Steph, F5NZY

 

PS: Of course, you can do the same thing with a text editor, like notepad, but I prefer Cygwin.

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph Collas via Groups.Io
Envoyé : jeudi 12 septembre 2019 14:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Hi Bob,

 

I understand.

 

I will remberber the lesson for the next time…

 

😊

 

Tks for your support, as usual…

 

Merci.

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 14:19
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, that is the correct way to synchronize with LoTW. I think that you have made a mistake once, and imported the file and not synchronized it. 73.

On September 12, 2019 at 8:14 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi Bob,

 

OK, but how I can solve it?

 

If I delete manually the entries, how could I sync my entries from eqsl or lotw?

 

Actually, what I do is:

 

  1. I download report from lotw, for exemple (lotwreport.adi)
  2. I syncrhronize lotw from an ADIF file.

 

Am I right?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 13:35
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, Looking at the ADIF data you sent, looked at 'duplicate' QSOs like this:

 

Line 30139:
<BAND:3>80M
<CALL:5>G3NCN
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<FREQ:8>3.500000
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<QSL_RCVD:1>Y
<QSLRDATE:8>20141007
<QSO_DATE:8:D>20091209
<TIME_ON:6>173900
<RST_RCVD:3>599
<RST_SENT:3>599
<TIME_OFF:6>173900
<TX_PWR:3>100
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15066
<COUNTRY:7>England
<EOR>

Line 30141:
<BAND:3>80M
<CALL:5>G3NCN
<COMMENT:19>ts590, 100w, windom
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<APP_LOGGER32_QSL:1>Y
<QSL_SENT:1>Y
<QSO_DATE:8:D>20091209
<TIME_ON:6>174300
<QTH:5>Berks
<RST_SENT:3>599
<TEN_TEN:4>1996
<TIME_OFF:6>174300
<eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15067
<COUNTRY:7>England
<EOR>

 

Two QSOs with G3NCN four minutes apart. You will notice that the two ADIF records are quite different ... One has a comment field describing the station, on has a QTH, one has a QSLRDATE, one has a TEN_TEN number, one has a FREQ, etc. Looks to me like you taken an LoTW or eQSL sync file and imported it to Logger32 ... So, one of the QSOs has data from your QSO with G3NCN, the other QSO has data from G3NCNs QSO with you.

 

Not Kosher, Halal, or Haram. SeventyThree(s).

 

On September 12, 2019 at 6:59 AM Bob <k4cy@...> wrote:

Steph, LoTW sync and eQSL sync does not write QSOs to the logbook . If it finds a QSO that is not in the logbook that ADIF record is put in the BAD.ADI files and a QSO is not added to your logbook. If you have duplicate QSOs in the logbook they come from somewhere else. What have you done? Please send me a small piece of your ADIF file that shows these duplicate QSOs.  There is no way in Logger32 to remove duplicate QSOs automatically (because there should be none :). SeventyThree(s).

On September 11, 2019 at 3:20 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Since I sync my log with lotw, eqsl and clublog, I have double in my log.

 

I can delete them, one by one, but is it a possibility to delete all the double entries, by the soft ?

 

73 de Steph, F5NZY


 


 


 


 

 

 


 


 

 

 


 


 

 

 


 


 

 



 


 

Re: Double in the log...

Paul Evans W4/VP9KF
 

You are correct. I don't think Bob knows about *NIX command line commands.......................

Re: Double in the log...

Steph Collas <f5nzy@...>
 

Hi Bob,

 

I can not contradict you, technically, but I am pragmatic and what I have described, in my case at least works perfectly.

 

The double entries have been deleted (+5000 entries).

 

But mebbe there is a confusion…

 

In my .ADI file, some fields <RST_RCVD:3>, was missing.

 

The “empty” fields was in the Previous Logbook page.

 

When I GREP only the <RST_RCVD:3> from my “original” Logbook.ADI file, then exported into a Logbook-corrected.ADI, then created a new Logbook, then import the Logbook-corrected.ADI file, the double entries in the Previous.

 

I don’t know if I am clear?

 

73 de Steph, F5NZY

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 9 octobre 2019 18:50
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

If you add <RST_RCVD:3> to the QSO record, the RST_RCVD will be the next three characters after <RST_RCVD:3> For example, it the QSO record is <RST_RCVD:3> CALL:5>F5NZY .... then RCD_RCVD is read as " CA". SeventyThree(s).

On October 9, 2019 at 12:41 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Bob,

 

It Is corresponding to the received RST.

 

When I had double entries in my logbook, the value was empty.

 

Since the description of what I did, have no more such double entries.

 

It is not correct?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 9 octobre 2019 17:16
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, are you sure? Look in your logbook and see what is in the RST_RCVD field. SeventyThree(s).

On October 9, 2019 at 8:48 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Never Say Die!

 

I found how to proceed to remove my double entries in my LogBook and to get back with a clean one.

 

I studied my .ADI file and noticed, that for the wrong entries, the field <RST_RCVD:3> was missing.

 

So, easy to solve it!

 

I use Cygwin, a Linux Emulator on Windows 10, (https://cygwin.com/).

 

The way to proceed is as follow:

 

  • Export your full LogBook in .ADI file
  • With Cygwin, type the commands: cat your_file.ADI | grep "<RST_RCVD:3>" >your_file-corrected.ADI
  • Create a new LogBook
  • Import your new LogBook-corrected.ADI file
  • I rebuilt the database

 

I lost more than 5,000 entries in my LogBook, but now, it is Clean!

 

😉

 

Hope it helps!

 

73 de Steph, F5NZY

 

PS: Of course, you can do the same thing with a text editor, like notepad, but I prefer Cygwin.

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph Collas via Groups.Io
Envoyé : jeudi 12 septembre 2019 14:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Hi Bob,

 

I understand.

 

I will remberber the lesson for the next time…

 

😊

 

Tks for your support, as usual…

 

Merci.

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 14:19
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, that is the correct way to synchronize with LoTW. I think that you have made a mistake once, and imported the file and not synchronized it. 73.

On September 12, 2019 at 8:14 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi Bob,

 

OK, but how I can solve it?

 

If I delete manually the entries, how could I sync my entries from eqsl or lotw?

 

Actually, what I do is:

 

  1. I download report from lotw, for exemple (lotwreport.adi)
  2. I syncrhronize lotw from an ADIF file.

 

Am I right?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 13:35
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, Looking at the ADIF data you sent, looked at 'duplicate' QSOs like this:

 

Line 30139:
<BAND:3>80M
<CALL:5>G3NCN
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<FREQ:8>3.500000
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<QSL_RCVD:1>Y
<QSLRDATE:8>20141007
<QSO_DATE:8:D>20091209
<TIME_ON:6>173900
<RST_RCVD:3>599
<RST_SENT:3>599
<TIME_OFF:6>173900
<TX_PWR:3>100
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15066
<COUNTRY:7>England
<EOR>

Line 30141:
<BAND:3>80M
<CALL:5>G3NCN
<COMMENT:19>ts590, 100w, windom
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<APP_LOGGER32_QSL:1>Y
<QSL_SENT:1>Y
<QSO_DATE:8:D>20091209
<TIME_ON:6>174300
<QTH:5>Berks
<RST_SENT:3>599
<TEN_TEN:4>1996
<TIME_OFF:6>174300
<eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15067
<COUNTRY:7>England
<EOR>

 

Two QSOs with G3NCN four minutes apart. You will notice that the two ADIF records are quite different ... One has a comment field describing the station, on has a QTH, one has a QSLRDATE, one has a TEN_TEN number, one has a FREQ, etc. Looks to me like you taken an LoTW or eQSL sync file and imported it to Logger32 ... So, one of the QSOs has data from your QSO with G3NCN, the other QSO has data from G3NCNs QSO with you.

 

Not Kosher, Halal, or Haram. SeventyThree(s).

 

On September 12, 2019 at 6:59 AM Bob <k4cy@...> wrote:

Steph, LoTW sync and eQSL sync does not write QSOs to the logbook . If it finds a QSO that is not in the logbook that ADIF record is put in the BAD.ADI files and a QSO is not added to your logbook. If you have duplicate QSOs in the logbook they come from somewhere else. What have you done? Please send me a small piece of your ADIF file that shows these duplicate QSOs.  There is no way in Logger32 to remove duplicate QSOs automatically (because there should be none :). SeventyThree(s).

On September 11, 2019 at 3:20 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Since I sync my log with lotw, eqsl and clublog, I have double in my log.

 

I can delete them, one by one, but is it a possibility to delete all the double entries, by the soft ?

 

73 de Steph, F5NZY


 


 


 


 

 

 


 


 

 

 


 


 

 

 


 


 

Re: Double in the log...

Bob
 

If you add <RST_RCVD:3> to the QSO record, the RST_RCVD will be the next three characters after <RST_RCVD:3> For example, it the QSO record is <RST_RCVD:3> CALL:5>F5NZY .... then RCD_RCVD is read as " CA". SeventyThree(s).

On October 9, 2019 at 12:41 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Bob,

 

It Is corresponding to the received RST.

 

When I had double entries in my logbook, the value was empty.

 

Since the description of what I did, have no more such double entries.

 

It is not correct?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 9 octobre 2019 17:16
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, are you sure? Look in your logbook and see what is in the RST_RCVD field. SeventyThree(s).

On October 9, 2019 at 8:48 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Never Say Die!

 

I found how to proceed to remove my double entries in my LogBook and to get back with a clean one.

 

I studied my .ADI file and noticed, that for the wrong entries, the field <RST_RCVD:3> was missing.

 

So, easy to solve it!

 

I use Cygwin, a Linux Emulator on Windows 10, (https://cygwin.com/).

 

The way to proceed is as follow:

 

  • Export your full LogBook in .ADI file
  • With Cygwin, type the commands: cat your_file.ADI | grep "<RST_RCVD:3>" >your_file-corrected.ADI
  • Create a new LogBook
  • Import your new LogBook-corrected.ADI file
  • I rebuilt the database

 

I lost more than 5,000 entries in my LogBook, but now, it is Clean!

 

😉

 

Hope it helps!

 

73 de Steph, F5NZY

 

PS: Of course, you can do the same thing with a text editor, like notepad, but I prefer Cygwin.

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph Collas via Groups.Io
Envoyé : jeudi 12 septembre 2019 14:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Hi Bob,

 

I understand.

 

I will remberber the lesson for the next time…

 

😊

 

Tks for your support, as usual…

 

Merci.

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 14:19
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, that is the correct way to synchronize with LoTW. I think that you have made a mistake once, and imported the file and not synchronized it. 73.

On September 12, 2019 at 8:14 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi Bob,

 

OK, but how I can solve it?

 

If I delete manually the entries, how could I sync my entries from eqsl or lotw?

 

Actually, what I do is:

 

  1. I download report from lotw, for exemple (lotwreport.adi)
  2. I syncrhronize lotw from an ADIF file.

 

Am I right?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 13:35
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, Looking at the ADIF data you sent, looked at 'duplicate' QSOs like this:

 

Line 30139:
<BAND:3>80M
<CALL:5>G3NCN
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<FREQ:8>3.500000
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<QSL_RCVD:1>Y
<QSLRDATE:8>20141007
<QSO_DATE:8:D>20091209
<TIME_ON:6>173900
<RST_RCVD:3>599
<RST_SENT:3>599
<TIME_OFF:6>173900
<TX_PWR:3>100
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15066
<COUNTRY:7>England
<EOR>

Line 30141:
<BAND:3>80M
<CALL:5>G3NCN
<COMMENT:19>ts590, 100w, windom
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<APP_LOGGER32_QSL:1>Y
<QSL_SENT:1>Y
<QSO_DATE:8:D>20091209
<TIME_ON:6>174300
<QTH:5>Berks
<RST_SENT:3>599
<TEN_TEN:4>1996
<TIME_OFF:6>174300
<eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15067
<COUNTRY:7>England
<EOR>

 

Two QSOs with G3NCN four minutes apart. You will notice that the two ADIF records are quite different ... One has a comment field describing the station, on has a QTH, one has a QSLRDATE, one has a TEN_TEN number, one has a FREQ, etc. Looks to me like you taken an LoTW or eQSL sync file and imported it to Logger32 ... So, one of the QSOs has data from your QSO with G3NCN, the other QSO has data from G3NCNs QSO with you.

 

Not Kosher, Halal, or Haram. SeventyThree(s).

 

On September 12, 2019 at 6:59 AM Bob <k4cy@...> wrote:

Steph, LoTW sync and eQSL sync does not write QSOs to the logbook . If it finds a QSO that is not in the logbook that ADIF record is put in the BAD.ADI files and a QSO is not added to your logbook. If you have duplicate QSOs in the logbook they come from somewhere else. What have you done? Please send me a small piece of your ADIF file that shows these duplicate QSOs.  There is no way in Logger32 to remove duplicate QSOs automatically (because there should be none :). SeventyThree(s).

On September 11, 2019 at 3:20 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Since I sync my log with lotw, eqsl and clublog, I have double in my log.

 

I can delete them, one by one, but is it a possibility to delete all the double entries, by the soft ?

 

73 de Steph, F5NZY


 


 


 


 

 

 


 


 

 

 


 


 

 



 


 

Re: Double in the log...

Steph Collas <f5nzy@...>
 

Bob,

 

It Is corresponding to the received RST.

 

When I had double entries in my logbook, the value was empty.

 

Since the description of what I did, have no more such double entries.

 

It is not correct?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : mercredi 9 octobre 2019 17:16
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, are you sure? Look in your logbook and see what is in the RST_RCVD field. SeventyThree(s).

On October 9, 2019 at 8:48 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Never Say Die!

 

I found how to proceed to remove my double entries in my LogBook and to get back with a clean one.

 

I studied my .ADI file and noticed, that for the wrong entries, the field <RST_RCVD:3> was missing.

 

So, easy to solve it!

 

I use Cygwin, a Linux Emulator on Windows 10, (https://cygwin.com/).

 

The way to proceed is as follow:

 

  • Export your full LogBook in .ADI file
  • With Cygwin, type the commands: cat your_file.ADI | grep "<RST_RCVD:3>" >your_file-corrected.ADI
  • Create a new LogBook
  • Import your new LogBook-corrected.ADI file
  • I rebuilt the database

 

I lost more than 5,000 entries in my LogBook, but now, it is Clean!

 

😉

 

Hope it helps!

 

73 de Steph, F5NZY

 

PS: Of course, you can do the same thing with a text editor, like notepad, but I prefer Cygwin.

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph Collas via Groups.Io
Envoyé : jeudi 12 septembre 2019 14:54
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Hi Bob,

 

I understand.

 

I will remberber the lesson for the next time…

 

😊

 

Tks for your support, as usual…

 

Merci.

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 14:19
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, that is the correct way to synchronize with LoTW. I think that you have made a mistake once, and imported the file and not synchronized it. 73.

On September 12, 2019 at 8:14 AM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi Bob,

 

OK, but how I can solve it?

 

If I delete manually the entries, how could I sync my entries from eqsl or lotw?

 

Actually, what I do is:

 

  1. I download report from lotw, for exemple (lotwreport.adi)
  2. I syncrhronize lotw from an ADIF file.

 

Am I right?

 

73

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de Bob
Envoyé : jeudi 12 septembre 2019 13:35
À : hamlogger@groups.io
Objet : Re: [hamlogger] Double in the log...

 

Steph, Looking at the ADIF data you sent, looked at 'duplicate' QSOs like this:

 

Line 30139:
<BAND:3>80M
<CALL:5>G3NCN
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<FREQ:8>3.500000
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<QSL_RCVD:1>Y
<QSLRDATE:8>20141007
<QSO_DATE:8:D>20091209
<TIME_ON:6>173900
<RST_RCVD:3>599
<RST_SENT:3>599
<TIME_OFF:6>173900
<TX_PWR:3>100
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15066
<COUNTRY:7>England
<EOR>

Line 30141:
<BAND:3>80M
<CALL:5>G3NCN
<COMMENT:19>ts590, 100w, windom
<CONT:2>EU
<CQZ:2>14
<DXCC:3>223
<GRIDSQUARE:6>IO91ok
<ITUZ:2>27
<MODE:2>CW
<NAME:4>John
<OPERATOR:5>F5NZY
<PFX:2>G3
<APP_LOGGER32_QSL:1>Y
<QSL_SENT:1>Y
<QSO_DATE:8:D>20091209
<TIME_ON:6>174300
<QTH:5>Berks
<RST_SENT:3>599
<TEN_TEN:4>1996
<TIME_OFF:6>174300
<eQSL_QSL_SENT:1>Y
<eQSL_QSL_RCVD:1>Y
<LOTW_QSL_SENT:1>Y
<LOTW_QSL_RCVD:1>Y
<APP_LOGGER32_QSO_NUMBER:5>15067
<COUNTRY:7>England
<EOR>

 

Two QSOs with G3NCN four minutes apart. You will notice that the two ADIF records are quite different ... One has a comment field describing the station, on has a QTH, one has a QSLRDATE, one has a TEN_TEN number, one has a FREQ, etc. Looks to me like you taken an LoTW or eQSL sync file and imported it to Logger32 ... So, one of the QSOs has data from your QSO with G3NCN, the other QSO has data from G3NCNs QSO with you.

 

Not Kosher, Halal, or Haram. SeventyThree(s).

 

On September 12, 2019 at 6:59 AM Bob <k4cy@...> wrote:

Steph, LoTW sync and eQSL sync does not write QSOs to the logbook . If it finds a QSO that is not in the logbook that ADIF record is put in the BAD.ADI files and a QSO is not added to your logbook. If you have duplicate QSOs in the logbook they come from somewhere else. What have you done? Please send me a small piece of your ADIF file that shows these duplicate QSOs.  There is no way in Logger32 to remove duplicate QSOs automatically (because there should be none :). SeventyThree(s).

On September 11, 2019 at 3:20 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Hi all,

 

Since I sync my log with lotw, eqsl and clublog, I have double in my log.

 

I can delete them, one by one, but is it a possibility to delete all the double entries, by the soft ?

 

73 de Steph, F5NZY


 


 


 


 

 

 


 


 

 

 


 


 

Re: ClubLog problem...

Steph Collas <f5nzy@...>
 

Everything works fine, now!

73

-----Message d'origine-----
De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph Collas
via Groups.Io
Envoyé : mercredi 9 octobre 2019 18:07
À : hamlogger@groups.io
Objet : [hamlogger] ClubLog problem...

Hello all,

I wrote to Bob because I had an Error#5, when I entered, then removed a
contact (it was for a demo).

The problem is not coming from Logger32, but from Clublog.

It will be certainly fixed befefore long.

In the meantime I advise you to Uncheck Auto Update QSO, for ClubLog, in the
L32Sync.

Tks Bob.

73 de Steph, F5NZY

ClubLog problem...

Steph Collas <f5nzy@...>
 

Hello all,

I wrote to Bob because I had an Error#5, when I entered, then removed a
contact (it was for a demo).

The problem is not coming from Logger32, but from Clublog.

It will be certainly fixed befefore long.

In the meantime I advise you to Uncheck Auto Update QSO, for ClubLog, in the
L32Sync.

Tks Bob.

73 de Steph, F5NZY

Re: Edit Errors

HI3B Radhames
 

Hi Edwin....Thanks for your suggestion.
I just to write your email address.
73.
Radhames 


From: hamlogger@groups.io <hamlogger@groups.io> on behalf of YV5EN - Edwin via Groups.Io <yv5en@...>
Sent: Wednesday, October 9, 2019 10:10 AM
To: hamlogger@groups.io <hamlogger@groups.io>
Subject: Re: [hamlogger] Edit Errors
 
Hi Rada.
Please be sure you have checked the hh:mm:ss format.
To do so, please do the following steps:
Go to "Ajustes"
Then, go to "Formato de hora"
Then check the bottom option: 23:59:59

Now you have to check if you have hh:mm:ss duplicated

Cheers

--
HI3B