Distance


Rob
 

Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Bob
 

On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.

On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Rob
 

Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob


On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Giuseppe Giunta
 

Ciao Guys,
I am equally interested in a retrospective calculation of the Km, of my + 118k Qso. Thank you, Giu IT9VDQ
(one of IB9T)


Il giorno mar 9 feb 2021 alle ore 08:57 Rob <rob.harrison@...> ha scritto:
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Bob
 

Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).

On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Rob
 
Edited

opps that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob


On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:
<!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).
On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Bob
 

Rob, if importing an ADIF file does not automagically populate DISTANCE, then I guess you're out of luck. 73.

On 02/09/2021 6:44 AM Rob <rob.harrison@...> wrote:
 
 
poppas that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob

On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:
<!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).
On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Rob
 

guess so then...cheers Rob


On Tue, Feb 9, 2021 at 11:57 AM, Bob wrote:
<!doctype html>
Rob, if importing an ADIF file does not automagically populate DISTANCE, then I guess you're out of luck. 73.
On 02/09/2021 6:44 AM Rob <rob.harrison@...> wrote:
 
 
poppas that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob

On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:
<!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).
On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Gianfranco
 

This topic was mentioned a few days ago but as far as I'm concerned it is still an outstanding issue.
In fact, it is not possible in any way to enter the distance for QSOs already in the log unless the
"locator" is deleted and rewritten again.
With version 3.50 it was still possible to enter the "distance":

        If you have QSOs in the logbook with a GRIDSQUARE and no DISTANCE, left click on
        the DISTANCE CELL and select the <INSERT> key. Calculated distance is populated
        in the DISTANCE CELL.

Now in version 4.0.242 it seems that this is no longer possible (or at least it doesn't work for me)
 and there is no indication in the help on how this can be done... possibly.
The questions at the end are:
- is it still possible to somehow enter the distance (without having to rewrite the gridsquare) or not?
- if not, can the method be reverted as in version 3.50?
Thanks.

ik3ogn GFranco

Il 09/02/2021 12:44, Rob ha scritto:

[Edited Message Follows]

opps that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob

On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:
<!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).
On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Bob
 

Try Alt+D. SeventyThree(s).

On 02/13/2021 3:29 AM Gianfranco via groups.io <tog-franco@...> wrote:
 
 
This topic was mentioned a few days ago but as far as I'm concerned it is still an outstanding issue.
In fact, it is not possible in any way to enter the distance for QSOs already in the log unless the
"locator" is deleted and rewritten again.
With version 3.50 it was still possible to enter the "distance":

        If you have QSOs in the logbook with a GRIDSQUARE and no DISTANCE, left click on
        the DISTANCE CELL and select the <INSERT> key. Calculated distance is populated
        in the DISTANCE CELL.

Now in version 4.0.242 it seems that this is no longer possible (or at least it doesn't work for me)
 and there is no indication in the help on how this can be done... possibly.
The questions at the end are:
- is it still possible to somehow enter the distance (without having to rewrite the gridsquare) or not?
- if not, can the method be reverted as in version 3.50?
Thanks.

ik3ogn GFranco

Il 09/02/2021 12:44, Rob ha scritto:

[Edited Message Follows]

opps that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob

On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:
<!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).
On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS


Michael Harris
 

This is interesting. I don't bother with distance but enabled distance in the logbook and fancy that a load if distances showed, but not all QSOs despite there being a grid locator. Alt D fixed that.

I have one or two ideas about how this works in my log. This I will have to test on some FT8 where it is likely to log QSOs with or without grid and then see what happens after a LoTW confirmation where grid might be applied from the LoTW report.

One thing I have noticed is that distance is (in my log) is always short path. I work a lot of long path JA!

Regards,

Mike VP8NO

On 13/02/2021 06:01, Bob wrote:
Try Alt+D. SeventyThree(s).

On 02/13/2021 3:29 AM Gianfranco via groups.io <tog-franco=libero.it@groups.io> wrote:
This topic was mentioned a few days ago but as far as I'm concerned it is still an outstanding issue.
In fact, it is not possible in any way to enter the distance for QSOs already in the log unless the
"locator" is deleted and rewritten again.
With version 3.50 it was still possible to enter the "distance":

If you have QSOs in the logbook with a GRIDSQUARE and no DISTANCE, left click on
the DISTANCE CELL and select the <INSERT> key. Calculated distance is populated
in the DISTANCE CELL.

Now in version 4.0.242 it seems that this is no longer possible (or at least it doesn't work for me)
and there is no indication in the help on how this can be done... possibly.
The questions at the end are:
- is it still possible to somehow enter the distance (without having to rewrite the gridsquare) or not?
- if not, can the method be reverted as in version 3.50?
Thanks.

ik3ogn GFranco

Il 09/02/2021 12:44, Rob ha scritto:

> >
[Edited Message Follows]

opps that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob

On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:

> > > <!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).

> > > > On 02/09/2021 2:57 AM Rob <rob.harrison@mis-specialists.co.uk> mailto:rob.harrison@mis-specialists.co.uk wrote:
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:

> > > > > <!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.

> > > > > > On 02/08/2021 1:23 PM Rob <rob.harrison@mis-specialists.co.uk> mailto:rob.harrison@mis-specialists.co.uk wrote:
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS

> > > > >
> > > >
> > >
> >
>


Gianfranco
 

OK, ... Alt+D ... it works perfectly, thanks a lot.

73 de ik3ogn GFranco

Il 13/02/2021 10:01, Bob ha scritto:
Try Alt+D. SeventyThree(s).
On 02/13/2021 3:29 AM Gianfranco via groups.io <tog-franco@...> wrote:
 
 
This topic was mentioned a few days ago but as far as I'm concerned it is still an outstanding issue.
In fact, it is not possible in any way to enter the distance for QSOs already in the log unless the
"locator" is deleted and rewritten again.
With version 3.50 it was still possible to enter the "distance":

        If you have QSOs in the logbook with a GRIDSQUARE and no DISTANCE, left click on
        the DISTANCE CELL and select the <INSERT> key. Calculated distance is populated
        in the DISTANCE CELL.

Now in version 4.0.242 it seems that this is no longer possible (or at least it doesn't work for me)
 and there is no indication in the help on how this can be done... possibly.
The questions at the end are:
- is it still possible to somehow enter the distance (without having to rewrite the gridsquare) or not?
- if not, can the method be reverted as in version 3.50?
Thanks.

ik3ogn GFranco

Il 09/02/2021 12:44, Rob ha scritto:

[Edited Message Follows]

opps that was a typo on my behalf.... I just exported some QSOs with no distance calculaTED.

Opened a new logbook, imported them.......and still no distance.

Regards

Rob

On Tue, Feb 9, 2021 at 10:15 AM, Bob wrote:
<!doctype html>
Rob, you said (in your original post) that distance is calculated on log import. Does that give you any clues as to how you might go about respectively populating the distance fields? And, before you go buggering around, please make an ADIF backup and hide it under the mattress. SeventyThree(s).
On 02/09/2021 2:57 AM Rob <rob.harrison@...> wrote:
 
 
Thanks Bob, I have that ticked...is there anyway to retrospectively calculate distance when it hasn't been populated?

73

Rob

On Mon, Feb 8, 2021 at 07:12 PM, Bob wrote:
<!doctype html>
On the logbook entry window right click on any entry field. Click SETUP. Check the option to AUTOLOG DISTANCE, etc. 73.
On 02/08/2021 1:23 PM Rob <rob.harrison@...> wrote:
 
 
Is there anyway of forcing L32 to calculate the distance if it is not populated.

I notice distance is calculated on log imports and manually entered qso's

73 de Rob G4UJS



Michael Harris
 

Observations so far.

Logged a few QSOs in the RTTY contest. Some of them were with previous details which were carried forward into the Logbook Entry pane complete with Grid.

Short path, long path headings and distance are displayed in the LEP. so Logger is doing the calculation it just isn't finding its way automatically into the ADIF log field.

As advised ALT D completed the job from the logged grid. Is there any reason why this should not be automatic?

Regards,

Mike VP8NO


Bob
 

Right click on any field in the logbook entry window. Click SETUP. Is the option to AUTO LOG DISTANCE ... checked? SeventyThree(s).

On 02/13/2021 6:00 PM Michael Harris via groups.io <mike.harris=horizon.co.fk@groups.io> wrote:


Observations so far.

Logged a few QSOs in the RTTY contest. Some of them were with previous
details which were carried forward into the Logbook Entry pane complete
with Grid.

Short path, long path headings and distance are displayed in the LEP. so
Logger is doing the calculation it just isn't finding its way
automatically into the ADIF log field.

As advised ALT D completed the job from the logged grid. Is there any
reason why this should not be automatic?

Regards,

Mike VP8NO