Date   

Re: LONP Approved List - Update

 

Don't think for a minute that we don't appreciate what you all do.  I can only imagine how tedious and time consuming manually approving the endorsements can be.

Thank you very much
John
KC3FL


Re: LONP Approved List - Update

Jerry N9AVY
 

P.S. David,Jim, Stan , myself and others have been working our butts off keeping up with endorsements. Keep those endorsements coming !!!

Jerry

On Monday, December 14, 2020, 11:49:54 AM CST, stan W9SMR <robinstan@...> wrote:


Few understand the chaos that has ensued due to the malfunctioning endorsement checker. In spite of those issues, our Executive Director, Jim, K5SP has worked his way through mess and approved a new round of LONP 100 recipients.

 

Many thanks to N9AVY for all the extra effort it is taking to manually track and verify your endorsements. This has required manual intervention of your submissions and maintaining a separate spreadsheet to ensure each member receives their appropriate sticker.  Bravo Zulu to Jerry.

Here are the newly approved members of the LONP 100:

LONP#           070#     CALL            QSO’S
434                 2618     KD6TR        180
435                 2722     N3XL           130
436                 2727     K4VBM        128
437                 2380     N4KP           122
438                 985       WB4JJJ       114
439                 577       K6WRJ        118
440                 2017     W7RTL        112
441                 2692     YV4YY         100
442                 2741     WA4RXK     100

And Congrats also to OK1WCF, #556 who achieved the LONP Honor Roll with 500 QSOs. He is the 58th member to join the illustrious 500 level Honor Roll.

Congrats to all!

73,

Stan

W9SMR - 070  #1611

PODXS 070 - PR Director


LONP Approved List - Update

stan W9SMR
 

Few understand the chaos that has ensued due to the malfunctioning endorsement checker. In spite of those issues, our Executive Director, Jim, K5SP has worked his way through mess and approved a new round of LONP 100 recipients.

 

Many thanks to N9AVY for all the extra effort it is taking to manually track and verify your endorsements. This has required manual intervention of your submissions and maintaining a separate spreadsheet to ensure each member receives their appropriate sticker.  Bravo Zulu to Jerry.

Here are the newly approved members of the LONP 100:

LONP#           070#     CALL            QSO’S
434                 2618     KD6TR        180
435                 2722     N3XL           130
436                 2727     K4VBM        128
437                 2380     N4KP           122
438                 985       WB4JJJ       114
439                 577       K6WRJ        118
440                 2017     W7RTL        112
441                 2692     YV4YY         100
442                 2741     WA4RXK     100

And Congrats also to OK1WCF, #556 who achieved the LONP Honor Roll with 500 QSOs. He is the 58th member to join the illustrious 500 level Honor Roll.

Congrats to all!

73,

Stan

W9SMR - 070  #1611

PODXS 070 - PR Director


Re: Welcome 2811

Jim K5SP
 

John

I checked your last submission and you are correct.  Your log was submitted at 12:05:29 12/13/20.  Under you In Progress column when I click on the blue 491 under HAVE, the last log entry was 20201214 @ 0301Z.  (KM4MK).  Try resubmitting your latest log and lets see if it picks it up this time.  (Not sure what time your QSo with Terry was.

Jim

On 12/13/2020 11:17 AM, John - KC3FL via groups.io wrote:

 Welcome Terry
Jim,
I had a contact with Terry last night and uploaded but he doesn't show up in my LONP list.  I have had contacts with several new members in the past few months and they don't show up either.  Looking at the Alpha list, the last entry was with #2786 on 7/8/20.  Is it possible that they have to be on the list before you can get credit for the contact and if so, how do we update it?

John
KC3FL


--
Jim,  K5SP #483
Executive Director/Member Services Director


Re: Welcome 2811

Ken N6PCD
 

Welcome to the family, Mr. Terry! 👍🏻👋🏻😁
--
All the best,
Ken N6PCD
070 #801
LONP #187


Re: Welcome 2811

Jerry N9AVY
 

Yep,  noticed that.

Jerry  n9avy

On Sunday, December 13, 2020, 11:17:26 AM CST, John - KC3FL via groups.io <kc3fl@...> wrote:


 Welcome Terry
Jim,
I had a contact with Terry last night and uploaded but he doesn't show up in my LONP list.  I have had contacts with several new members in the past few months and they don't show up either.  Looking at the Alpha list, the last entry was with #2786 on 7/8/20.  Is it possible that they have to be on the list before you can get credit for the contact and if so, how do we update it?

John
KC3FL


Re: Welcome 2811

 

Agreed!
Steve is absolutely correct.
The checker shows me with 846.
My records put me at 848. I'm aware of the 2 missing contacts and I know who they are.
It doesn't really matter until my records indicate 850. 
Then a quick eye-ball scan by management will be necessary for the 50 new earned contacts.
It's not quite time for Steve to start looking over his shoulder just yet... :-)
Milt.
N6MG
070-650
LONP #76

 


-----Original Message-----
From: Stephen Melachrinos via groups.io <melachri@...>
To: main@070Club.groups.io <main@070Club.groups.io>
Sent: Sun, Dec 13, 2020 9:36 am
Subject: Re: [070Club] Welcome 2811

John -

That's an artifact of the broken software. Something isn't getting connected between the "add the new member" logic and the "rebuild the membership list" logic. As a result, we are defaulting to more manual processes that aren't reflected in the endorsement checker.

Steve
W3HF


-----Original Message-----
From: John - KC3FL via groups.io <kc3fl@...>
To: main@070Club.groups.io
Sent: Sun, Dec 13, 2020 5:17 pm
Subject: Re: [070Club] Welcome 2811

 Welcome Terry
Jim,
I had a contact with Terry last night and uploaded but he doesn't show up in my LONP list.  I have had contacts with several new members in the past few months and they don't show up either.  Looking at the Alpha list, the last entry was with #2786 on 7/8/20.  Is it possible that they have to be on the list before you can get credit for the contact and if so, how do we update it?

John
KC3FL


Re: Welcome 2811

Stephen Melachrinos
 

John -

That's an artifact of the broken software. Something isn't getting connected between the "add the new member" logic and the "rebuild the membership list" logic. As a result, we are defaulting to more manual processes that aren't reflected in the endorsement checker.

Steve
W3HF


-----Original Message-----
From: John - KC3FL via groups.io <kc3fl@...>
To: main@070Club.groups.io
Sent: Sun, Dec 13, 2020 5:17 pm
Subject: Re: [070Club] Welcome 2811

 Welcome Terry
Jim,
I had a contact with Terry last night and uploaded but he doesn't show up in my LONP list.  I have had contacts with several new members in the past few months and they don't show up either.  Looking at the Alpha list, the last entry was with #2786 on 7/8/20.  Is it possible that they have to be on the list before you can get credit for the contact and if so, how do we update it?

John
KC3FL


Re: Welcome 2811

 

 Welcome Terry
Jim,
I had a contact with Terry last night and uploaded but he doesn't show up in my LONP list.  I have had contacts with several new members in the past few months and they don't show up either.  Looking at the Alpha list, the last entry was with #2786 on 7/8/20.  Is it possible that they have to be on the list before you can get credit for the contact and if so, how do we update it?

John
KC3FL


Welcome 2811

Jim K5SP
 

Please join me in welcoming new member:

2811 Terry KZ4KX

Terry's Membership data is 12/12/20, which means those contacts he has had since the contest started count as a member. 

Welcome to the club Terry!

Jim K5SP
Executive Director
--
Jim,  K5SP #483
Executive Director/Member Services Director


Re: RC3 Standings

Stephen Melachrinos
 

Steve -

I'm pretty sure we've identified both callsigns as belonging to you. I was really posting that about RC3, and that's an annual thing. During this year, we've had two callsign changes we know about, but I was afraid there might be more.

If you've been uploading under one callsign, then all your awards are intact. 

Thanks for checking.

73,
Steve
W3HF



-----Original Message-----
From: Steve R via groups.io <oldjavadrinker@...>
To: main@070Club.groups.io
Sent: Sun, Dec 13, 2020 2:36 am
Subject: Re: [070Club] RC3 Standings

 Steve.

Not sure how I missed this. I operated KM4FLF/VE3 from 2016 to May 2017 until I got Canada ticket. Every time I upload for awards I always just merge that old adif into the new one since it was same QTH. I found that easier than all of us tracking two calls.

Steve
VA3FLF
2301


Re: RC3 Standings

Steve VA3FLF/KM4FLF
 

 Steve.

Not sure how I missed this. I operated KM4FLF/VE3 from 2016 to May 2017 until I got Canada ticket. Every time I upload for awards I always just merge that old adif into the new one since it was same QTH. I found that easier than all of us tracking two calls.

Steve
VA3FLF
2301


Re: Doubleheader contest

Josef 'Jeff' Sipek
 

On Sat, Dec 12, 2020 at 23:28:49 +0000, Stephen Melachrinos via groups.io wrote:
John -
Exactly correct. You never really know what the other station is going to
do, and since the exchange is so quick, I just run with it. Besides, it's
the courteous approach.
I also like to throw in that it is a dup. On several occasions that has
revealed an error in logging.

Jeff.

I usually average two or three dupes on this type of contest.
SteveW3HF


-----Original Message-----
From: John - KC3FL via groups.io <kc3fl=aol.com@groups.io>
To: main@070Club.groups.io
Sent: Sat, Dec 12, 2020 11:13 pm
Subject: Re: [070Club] Doubleheader contest


So if you make a contact with a station that shows up as a dupe there is the possibility that the station decided to start a different block.  With that being the case it is easier and quicker to just go ahead and log the contact just in case they changed their block.  It would take longer trying to explain they were a dupe.

John
KC3FL






Re: Doubleheader contest

Stephen Melachrinos
 

John -

Exactly correct. You never really know what the other station is going to do, and since the exchange is so quick, I just run with it. Besides, it's the courteous approach.

I usually average two or three dupes on this type of contest.

Steve
W3HF


-----Original Message-----
From: John - KC3FL via groups.io <kc3fl@...>
To: main@070Club.groups.io
Sent: Sat, Dec 12, 2020 11:13 pm
Subject: Re: [070Club] Doubleheader contest

So if you make a contact with a station that shows up as a dupe there is the possibility that the station decided to start a different block.  With that being the case it is easier and quicker to just go ahead and log the contact just in case they changed their block.  It would take longer trying to explain they were a dupe.

John
KC3FL


Re: Doubleheader contest

 

So if you make a contact with a station that shows up as a dupe there is the possibility that the station decided to start a different block.  With that being the case it is easier and quicker to just go ahead and log the contact just in case they changed their block.  It would take longer trying to explain they were a dupe.

John
KC3FL


Re: Doubleheader contest

Randy True
 

Yeah, I'm one of the still confused. Just make it any 6 hours in a 24hr block.

Randy W4RTT


From: main@070Club.groups.io <main@070Club.groups.io> on behalf of Stephen Melachrinos via groups.io <melachri@...>
Sent: Saturday, December 12, 2020 11:31 AM
To: main@070club.groups.io <main@070club.groups.io>
Subject: [070Club] Doubleheader contest
 
I hope everyone is enjoying the contest. I've seen a lot of stations on the air, and that's great. But I've also seen some signals on the air this morning that cause me to question whether everyone understands the rules. So here are some thoughts about parts of the rules that may not be obvious.

1. This is a low-band sprint, limited to 40, 80, and 160 meter bands. So QSOs on any other bands won't count. (They may be really great rag-chews, or good DX, or even LONP points, though!)

2. The contest timing is based on UTC days, and you are allowed a single six-hour block of time on each of those days. So if you operated last night from 0000z to 0600z (as I did), which was the start of UTC 12 December, then any contacts until 0000z of 13 December would constitute a different six-hour block and you'd have to choose one or the other to count in your score. This will repeat into the 14 of December. I've made two 40m contacts this morning that won't count for me, but they will count for the "other guy" if he chooses that block.

3. That said, recognize that people will be operating at different times during the days, and it's possible that those "other guys" might be on the air again tonight, during my chosen block of time for 13 December. And I hope they'll realize that although another QSO with me will be a dupe for them, it won't be for me. So I'd appreciate that QSO for my purposes.

73,
Steve
W3HF





Doubleheader contest

Stephen Melachrinos
 

I hope everyone is enjoying the contest. I've seen a lot of stations on the air, and that's great. But I've also seen some signals on the air this morning that cause me to question whether everyone understands the rules. So here are some thoughts about parts of the rules that may not be obvious.

1. This is a low-band sprint, limited to 40, 80, and 160 meter bands. So QSOs on any other bands won't count. (They may be really great rag-chews, or good DX, or even LONP points, though!)

2. The contest timing is based on UTC days, and you are allowed a single six-hour block of time on each of those days. So if you operated last night from 0000z to 0600z (as I did), which was the start of UTC 12 December, then any contacts until 0000z of 13 December would constitute a different six-hour block and you'd have to choose one or the other to count in your score. This will repeat into the 14 of December. I've made two 40m contacts this morning that won't count for me, but they will count for the "other guy" if he chooses that block.

3. That said, recognize that people will be operating at different times during the days, and it's possible that those "other guys" might be on the air again tonight, during my chosen block of time for 13 December. And I hope they'll realize that although another QSO with me will be a dupe for them, it won't be for me. So I'd appreciate that QSO for my purposes.

73,
Steve
W3HF





Re: Zulu time, GMT & UTC

Don - KM4UDX
 

Wait, Iceland time always = UTC?
Why am I just hearing this now? 
This is great.
--
Don, km4udx, uBITX, and other obscure acronyms go here...


Re: HRD Logbook to LoTW with Other Grids

Eric KG6MZS
 

Thanks for the reply Darin.

I did that and then when I imported an ADI file it didn't take the "My Station" data from the new Location.  I think you might have to make an entree in the new Database with the "Add" button first to make sure the import takes the new Location.

Thanks again,

Eric


On 12/11/20 2:03 PM, Darin - KO4EJD wrote:
Eric,
You can go to my station and set that up.  I have 3 locations configured.
Before operating just select the one you want.

From logbook go to configure, my station and you'll see the option.

From DM780 go to program options and select calling.  This ties back to my station in logbook.

Good luck
Darin 

On Fri, Dec 11, 2020, 2:38 PM Eric KG6MZS <contact@...> wrote:
Hello All,

While restricted by the pandemic, I'm getting ready to activate other grids and I've pretty much got it all worked out except for one hitch.

I see in HRD Logbook you can define different Locations and you can create different Databases for different logs.  What I can't seem to figure out is how to assign those Locations to the different Databases.

I have set up different locations in LoTW but when I try and sign and upload the logs from HRD, LoTW tells me that the grids don't match.  LoTW thinks the logs have my home grid, not the new grid from elsewhere.

So how do I tell HRD to assign the grid from the activating location to the new database?

TIA
Eric, KG6MZS


Re: Zulu time, GMT & UTC

Jerry N9AVY
 

Yup, most software will convert local time from computer to UTC/GMT/Zulu.  If your software doesn't do that, you were ripped off !

Emoji

Jerry



On Friday, December 11, 2020, 04:35:32 PM CST, Barry VA7GEM via groups.io <boat.anchor@...> wrote:


I keep m computer on local time and my software (HRD)
on UTC. No question about what time it is.

3121 - 3140 of 67892