Date   

Re: Version 4.0

Bob
 

No need to hold your breath John. Ver 4.0 is being released in the same order as the COVID vaccinations are ... First the Royalty, then the Aristocracy, then the elected officials, then all the 'my poop doesn't smell' elected (and non elected) hangers on. Finally, to those who really need it ...
 
Bottom line John, the recent releases of Logger32 have been (IMHO) remarkably stable (for a 20 year old program - written in a language that hasn't been supported for countless years - that was never intended get this big). Ver 4.0 is nothing special, it looks like, and feels like, what you're using now. As best as I can describe it, it's like the Leaning Tower of Pisa, we've rebuilt the foundation so that it is vertical ...
 
And, I ask the ver 4.0 Beta testers to add to this thread with their observations/comments of how they view ver 4.0 ... SeventyThree(s).
 
 

On 01/04/2021 7:04 AM John Pink via groups.io <john_pink@...> wrote:
 
 

It’s a little bit like waiting for Covid vaccination – I am still waiting for the call

 

HNY john G8MM


Re: Auto Fill possible ?

Karl Beckman
 

I think I understand your request, but do have a few questions:
USA vanity callsigns change, some hams move to new QTHs but keep their old calls, ARRL changes Ontario VE3 section bouindaries, etc.
Do you have sources for all the missing details that are accurate as of the date of each legacy QSO?  If there i cosnflicting information, how will you decide which data source is correct? 
--
Karl  WA8NVW  OH
in hamlogger@groups.io


Version 4.0

John Pink
 

It’s a little bit like waiting for Covid vaccination – I am still waiting for the call

 

HNY john G8MM


Re: Auto Fill possible ?

Mike
 


Auto Fill possible ?

mike
 

Hello Logger32 friends,

  Long time user and member here, little ask.
I am approching 27,000 entries in logbook for Logger32.
Is there some service or something that I can do to auto fill states, IOTAs, name, etc in the missing sections of my logbook?
I signed up for QRZ XML and that is just current one plus later will figure out why not 100% working but wondering on my prior question on auto fill logbook.
Thank you, hope to QSO contact with some of you on the bands,
Mike
n0 odk 73


Re: Beam Headings Question for Large Countries

Greg - WC0M
 

You answered my question. No further explanation is necessary.

I raised the question because L32 was not doing what you describe for a couple of days during which I did not connect to a spots cluster or use the DX Spots window. I made several FT8 contacts with JTDX over UDP during the same timeframe. When I made a contact with anyone in Canada, no matter if they were in BC or NS or anywhere inbetween, L32 ALWAYS  resolved a beam heading to Toronto.
This behavior continued until by chance I decided to connect to a cluster and tried clicking on a spot for VE7KAJ located in BC. After that 1 single click on the DX Spots window, L32 resolved the beam headings correctly thereafter.

Anyway, it appears I am the only one who encountered this problem so there is no point to continue this thread or give it any credence. I'm writing it off as an anomaly that so far I have not been able to reproduce.

Sorry for taking up the bandwidth. Forget about it!

73.


Re: Beam Headings Question for Large Countries

Bob
 

First off, forget about QRZ (or any other lookup) and forget about Club Log exception updates.
 
When you start to enter a Canadian call in the Logbook Entry Window when you've typed VE, Logger32 knows it is Canada and calculates the beam heading from where you are to where Logger32 thinks Canada is. So, where is Canada? For my setup, Canada is at 44N/79W (somewhere around Toronto? Why not Saskatchewan? Because of the ham population density, but you can make it anything you like. It's your database, not mine.) For me, that's a beam heading of 22 degrees.
 
I type a 1 (I now have VE1). Notice that the Country name has changed from Canada to Canada - Nova Scotia. Where is Nova scotia? 44.5N/63.5W. The beam heading has now changed to 51 degrees.
 
And so we continue with VE2, VE3, etc. If Latitude/Longitude leave you cold, after typing in VEwhatever, type Ctrl_V this will show you where VEwhatever is.
 
What else can I tell you. 73.
 
 
 

On 01/02/2021 5:19 PM Greg - WC0M <wc0m.hamradio@...> wrote:
 
 
My home settings are correct for my QTH, thanks Jim.

I have an xml subscription to QRZ.com with the same coordinates for my station.

I am using ClubLog to update the exceptions list.

I've read the sections in the Help file titled: User Editable Databases, Database Maintenance, Setup Antenna Rotor, and Setup Bands and Modes.

Bob, I'm just not sure I understand how the software works at this point. I know it doesn't matter whether I'm in MN or GA or Egypt. The problem example here is just most prominent because I'm so close to the Canadian border.

VE7 is just one example for a Canadian call. Any station that I manually enter into the Log Entry window, located in any province of Canada, wants to point my beam to Toronto which is obviously the main coordinates for VE in the database. Sometimes as I'm entering a call, I see the square yellow marker on the Tracking window very briefly flash at the offset coordinates in the database, but then the marker goes right back to Toronto and that is the beam heading I get.

I realize that the Offset DB helps Logger32 determine the correct time zone, but is my rotor supposed to control to the coordinates in the Offset database for a given prefix number or not? I'm thinking yes.
What is the hierarchy for determining the correct bearing? Is the station's coordinates on QRZ supposed to trump what is in the Offset database? 

Here are some additional pictures showing what is happening on my end, (attached). Logger32 points me to 93 degrees from my home QTH, but QRZ points me correctly to 291 degrees for the pictured call; VE7CMR located in BC.
My home coordinates are the same on QRZ that I have set in Logger32.

OK. I think I may have uncovered a bug? I have no idea how I started it though. I can say that most of my operating lately has been using JTDX for FT8 without connecting to the cluster.

As I have been drafting this post and working through the problem, it is now gone. Here is what I did:
This problem went away after connecting to the cluster and clicking on a spot in VE7 land. (See the picture of the spot for VE7KAJ)
Even after I disconnected from the cluster, I can now enter a call for any province in Canada, and get the correct heading! I closed Logger32 and reopened Logger32 and without connecting to the cluster, I manually enter a call and the problem is still gone. I get the correct heading.

I'm not being critical here. This software is incredibly powerful. With that kind of power is complexity that sometimes escapes me!

Thanks for the best Logging software at the best price I've ever seen.
I'm looking forward to version 4.0. If you need anyone else to run it for a while before releasing it, I'd be happy to do what I can with the short hours of operating I have available.

Thanks,
Greg - WC0M


Re: Beam Headings Question for Large Countries

Greg - WC0M
 

My home settings are correct for my QTH, thanks Jim.

I have an xml subscription to QRZ.com with the same coordinates for my station.

I am using ClubLog to update the exceptions list.

I've read the sections in the Help file titled: User Editable Databases, Database Maintenance, Setup Antenna Rotor, and Setup Bands and Modes.

Bob, I'm just not sure I understand how the software works at this point. I know it doesn't matter whether I'm in MN or GA or Egypt. The problem example here is just most prominent because I'm so close to the Canadian border.

VE7 is just one example for a Canadian call. Any station that I manually enter into the Log Entry window, located in any province of Canada, wants to point my beam to Toronto which is obviously the main coordinates for VE in the database. Sometimes as I'm entering a call, I see the square yellow marker on the Tracking window very briefly flash at the offset coordinates in the database, but then the marker goes right back to Toronto and that is the beam heading I get.

I realize that the Offset DB helps Logger32 determine the correct time zone, but is my rotor supposed to control to the coordinates in the Offset database for a given prefix number or not? I'm thinking yes.
What is the hierarchy for determining the correct bearing? Is the station's coordinates on QRZ supposed to trump what is in the Offset database? 

Here are some additional pictures showing what is happening on my end, (attached). Logger32 points me to 93 degrees from my home QTH, but QRZ points me correctly to 291 degrees for the pictured call; VE7CMR located in BC.
My home coordinates are the same on QRZ that I have set in Logger32.

OK. I think I may have uncovered a bug? I have no idea how I started it though. I can say that most of my operating lately has been using JTDX for FT8 without connecting to the cluster.

As I have been drafting this post and working through the problem, it is now gone. Here is what I did:
This problem went away after connecting to the cluster and clicking on a spot in VE7 land. (See the picture of the spot for VE7KAJ)
Even after I disconnected from the cluster, I can now enter a call for any province in Canada, and get the correct heading! I closed Logger32 and reopened Logger32 and without connecting to the cluster, I manually enter a call and the problem is still gone. I get the correct heading.

I'm not being critical here. This software is incredibly powerful. With that kind of power is complexity that sometimes escapes me!

Thanks for the best Logging software at the best price I've ever seen.
I'm looking forward to version 4.0. If you need anyone else to run it for a while before releasing it, I'd be happy to do what I can with the short hours of operating I have available.

Thanks,
Greg - WC0M


Re: L32 v4

Gary Hinson
 

Hi there Paul, HNY mate.

Yes, that link is awaiting the full release. I plan to update it to point to the actual v4 installer, once it is released.

Meanwhile, there is only a limited v4 release for beta testers and pilots.

Are you desperate to join the beta/pilot crew?

73
Gary ZL2iFB

-----Original Message-----
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Paul Evans W4/VP9KF
Sent: 02 January 2021 01:43
To: hamlogger@groups.io
Subject: Re: [hamlogger] L32 v4

From PDF help:

• The Logger32 version 4 upgrade zip file: download it from https://www.logger32.net/

Doesn't work. No file present. It'll be a VERY soft rollout at this rate..... please provide a link.


Re: ver 4.0

Gary Hinson
 

😊

 

At a mere 700 pages, the v4 manual is the new, cut-down, ultra-succinct, de-duped, lightweight version, Jan.

 

The original v3.5 help file which spawned it came in at a whopping 1,300 pages.  Not so much heavyweight as sumo wrestling team, with entourage.

 

The original authors, who are all (I hope) gratefully acknowledged in the ‘bits at the bottom’, wrote it piecemeal over the past decade or two.

 

At some point, I’d like to split the 4 sections into 4 PDF files … but first I need to figure out how to retain/update all the internal hyperlinked cross-references accordingly.

 

A featherweight ‘Quick Start Guide’ (aimed at non-geeks) is also a possibility, further down the line once the v4 User Manual stabilises. 

 

73 HNY

Gary  ZL2iFB

 

PS  Please don’t print out the manual.  It is designed to be browsed and searched electronically.  The hyperlinks don’t function on paper, and there is no detailed index.  Save the planet: hug a whale.

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of KX2A
Sent: 01 January 2021 16:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] ver 4.0

 

To whet your appetite, you should take a peek at the preliminary v4.0 documentation at this temporary location: https://www.g4ifb.com/Logger32_v4_User_Manual.pdf

 

Even it you don't want to participate in the soft release the 700 page document will give you an insight into the v4.0 changes. To get any real benefit from v4.0, this is a MUST READ.

I will investigate how to submit this document to the Pulitzer Prize committee.  Failing that, perhaps a note to the Guinness World Record people for the longest technical manual ever written by a volunteer(s).

Of course,  this will occupy my New Year's Eve and New Years Week completely.

Happy New Year, may it be better than 2020.

Jan, KX2A


Re: ver 4.0

Gary Hinson
 

Logging software is hardly the most photogenic subject, Mike.  Glad you like it!

 

HNY, 73 from across the ditch

Gary  ZL2iFB  (ed.)

 

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of mikewalkington
Sent: 01 January 2021 10:53
To: hamlogger@groups.io
Subject: Re: [hamlogger] ver 4.0

 

Hi Bob

I must be a bit slow. It is January 1st here. But that's hardly an excuse. I was going to ask what the significance of the front cover picture was. Then it slowly dawned on me. Very clever.

Best wishes for Songkran when you get there.

Cheers, Mike, VK1OO

PS. I will happily look for the kitchen sink in the beta.


Re: ver 4.0

John Munton - G7SSE
 

Appetite wetted Bob, as if it had been to the  Songkran festivities.

Have just upgraded (and updated) both my PC's to version 4.0.218 and joined the beta IO Group.

HNY 73(s)

John - G7SSE

------ Original Message ------
From: "Bob" <k4cy@...>
Sent: 31/12/2020 02:33:46
Subject: [hamlogger] ver 4.0

To whet your appetite, you should take a peek at the preliminary v4.0 documentation at this temporary location: https://www.g4ifb.com/Logger32_v4_User_Manual.pdf
 
Even it you don't want to participate in the soft release the 700 page document will give you an insight into the v4.0 changes. To get any real benefit from v4.0, this is a MUST READ.
 
Personally, I don't celebrate the January 1st New Year, I much prefer the Songkran festivities mid April. For those who don't know what a real party is, and will celebrate tomorrow night, I wish you Happy New Year. SeventyThree(s).


--
73, John - G7SSE


Re: Beam Headings Question for Large Countries

Arturo LU6ETB
 

It works right

In my case, when I only type VE7 I can not see the beam heading.
Is there a way to reduce the width of the window Call ?

Happy New Year & Big Thanks for all the effort you put into Logger

73 de Arturo, LU6ETB

image.png


El vie, 1 ene 2021 a las 22:37, Greg - WC0M (<wc0m.hamradio@...>) escribió:
Just wondering if I am understanding the calculated beam heading for geographically large countries correctly...

I live in Minnesota and whenever I enter any Canadian callsign into the log entry window and hit tab, my rotor always points to Toronto, Ontario. 
So if I enter a call from VE7, that points my beam about 150 degrees away from VE7 land in British Columbia.

Then I looked at the Country database and sure enough the Latitude and Longitude are set to Toronto. But when I look at VE7 for British Columbia in the Offset Coordinates on the lower half of the window, the correct coordinates for Vancouver, BC are there.

Shouldn't my beam point to Vancouver when I enter a VE7 callsign into the log entry window?



Any help with this is much appreciated!
Greg - WC0M


Re: Beam Headings Question for Large Countries

Jeff VE3CV
 

Are you not using the QRZ lookup utility with a paid subscription?  You have to be online for it to work otherwise you will get a generic beam heading.


Re: Beam Headings Question for Large Countries

Bob
 

... and I live in Atlanta ... I enter a call of VE3XYZ in to Logger32, it says the beam heading is 22 degrees. I enter a call of VE4XYZ and Logger32 says the beam heading is 334 degrees. I enter a call of VE5XYZ and Logger32 says the beam heading is 324 degrees. I enter a call of VE6XYZ in Logger32 and Logger32 says the beam heading is 318 degrees. I enter a call of VE7XYZ and Logger32 says the beam heading is 310 degrees.
 
You think maybe I should buy a lottery ticket? SeventyThree(s).

On 01/01/2021 8:36 PM Greg - WC0M <wc0m.hamradio@...> wrote:
 
 
Just wondering if I am understanding the calculated beam heading for geographically large countries correctly...

I live in Minnesota and whenever I enter any Canadian callsign into the log entry window and hit tab, my rotor always points to Toronto, Ontario. 
So if I enter a call from VE7, that points my beam about 150 degrees away from VE7 land in British Columbia.

Then I looked at the Country database and sure enough the Latitude and Longitude are set to Toronto. But when I look at VE7 for British Columbia in the Offset Coordinates on the lower half of the window, the correct coordinates for Vancouver, BC are there.

Shouldn't my beam point to Vancouver when I enter a VE7 callsign into the log entry window?



Any help with this is much appreciated!
Greg - WC0M


Re: Beam Headings Question for Large Countries

Jim Hargrave
 

Check your home settings.

Log Entre > Setup > My QTH

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Greg - WC0M
Sent: Friday, January 1, 2021 7:37 PM
To: hamlogger@groups.io
Subject: [hamlogger] Beam Headings Question for Large Countries

 

Just wondering if I am understanding the calculated beam heading for geographically large countries correctly...

I live in Minnesota and whenever I enter any Canadian callsign into the log entry window and hit tab, my rotor always points to Toronto, Ontario. 
So if I enter a call from VE7, that points my beam about 150 degrees away from VE7 land in British Columbia.

Then I looked at the Country database and sure enough the Latitude and Longitude are set to Toronto. But when I look at VE7 for British Columbia in the Offset Coordinates on the lower half of the window, the correct coordinates for Vancouver, BC are there.

Shouldn't my beam point to Vancouver when I enter a VE7 callsign into the log entry window?



Any help with this is much appreciated!
Greg - WC0M


Beam Headings Question for Large Countries

Greg - WC0M
 

Just wondering if I am understanding the calculated beam heading for geographically large countries correctly...

I live in Minnesota and whenever I enter any Canadian callsign into the log entry window and hit tab, my rotor always points to Toronto, Ontario. 
So if I enter a call from VE7, that points my beam about 150 degrees away from VE7 land in British Columbia.

Then I looked at the Country database and sure enough the Latitude and Longitude are set to Toronto. But when I look at VE7 for British Columbia in the Offset Coordinates on the lower half of the window, the correct coordinates for Vancouver, BC are there.

Shouldn't my beam point to Vancouver when I enter a VE7 callsign into the log entry window?



Any help with this is much appreciated!
Greg - WC0M


Thanks Bob

John Owens
 

Going on 18 years now of enjoying L32. Thanks Bob and your support group. Looking forward to 4.0. - John Owens -  N7TK


Re: L32 v4

Bob
 

The file will be there after the public release. SeventyThree(s).

On 01/01/2021 7:42 AM Paul Evans W4/VP9KF <paul@hintlink.com> wrote:


From PDF help:

• The Logger32 version 4 upgrade zip file: download it from https://www.logger32.net/

Doesn't work. No file present. It'll be a VERY soft rollout at this rate..... please provide a link.



Re: L32 v4

Prasad
 

L32Beta@groups.io | Home  

73 de Prasad VU2PTT,


On Fri, Jan 1, 2021 at 6:47 PM Paul Evans W4/VP9KF <paul@...> wrote:
Sri. Pse provide info on hw to join the beta group...... HNY, etc. It'd better be better than 2020.





2761 - 2780 of 84644