Date   

Re: Down but not out!

Ken N6PCD
 

Hi Malcolm,

Thanks for asking!
I need DE, MN, NE, and RI confirmed by LoTW.

--
All the best,
Ken N6PCD


10M open?

Chuck M
 

Giving 10M a try, 28121, at 17:33 utc.

Thanks
Chuck
KD9DVB


Re: Trying 6m PSK now

Rick - N7WE
 

Zero, Zilch, Zip, Nada, Nichts, Nulla, Niente, Nasshingu...nothing!  Sometimes the magic works, sometimes it doesn't.  I'm off to feed my face.  Thanks to all who tried, Bill, Steve, Chuck, and probably others!  Maybe later!

--
Rick - N7WE
070 - #1602


Re: Trying 6m PSK now

Steve VA3FLF/KM4FLF
 

Looks dead in the Great North for now. Keep looking... it will open up sometime soon.

Steve
VA3FLF


On May 24, 2020, at 12:00, William Wagaman <n3gty@...> wrote:



I am calling CQ on 6m now 50.290 I will also listen for a bit de Bill N3GTY

On 2020-05-24 15:46, Rick - N7WE wrote:
Looks like lots of 6m FT8 from Florida to the Pacific Northwest.  I know that just because FT-8 is open, it doesn't mean PSK, CW or SSB is.  But I'm going to get on 50.290 and CQ using PSK31 from now until about 16:15 UTC.  Hope to catch a few of you!
--
Rick - N7WE
070 - #1602


Re: Trying 6m PSK now

William Wagaman
 

Same here nothing on the waterfall but calling cq de Bill N3GTY

On 2020-05-24 16:07, Rick - N7WE wrote:

Not seeing you Bill.  I fact, I'm not seeing any signals.  I'll hang in for about another 10 minutes then break for lunch. 

Rick - N7WE
070 - #1602

On 5/24/2020 12:00, William Wagaman wrote:

I am calling CQ on 6m now 50.290 I will also listen for a bit de Bill N3GTY

On 2020-05-24 15:46, Rick - N7WE wrote:
Looks like lots of 6m FT8 from Florida to the Pacific Northwest.  I know that just because FT-8 is open, it doesn't mean PSK, CW or SSB is.  But I'm going to get on 50.290 and CQ using PSK31 from now until about 16:15 UTC.  Hope to catch a few of you!
--
Rick - N7WE
070 - #1602

--
Rick - N7WE
070 - #1602


Re: Trying 6m PSK now

Rick - N7WE
 

Not seeing you Bill.  I fact, I'm not seeing any signals.  I'll hang in for about another 10 minutes then break for lunch. 

Rick - N7WE
070 - #1602

On 5/24/2020 12:00, William Wagaman wrote:

I am calling CQ on 6m now 50.290 I will also listen for a bit de Bill N3GTY

On 2020-05-24 15:46, Rick - N7WE wrote:
Looks like lots of 6m FT8 from Florida to the Pacific Northwest.  I know that just because FT-8 is open, it doesn't mean PSK, CW or SSB is.  But I'm going to get on 50.290 and CQ using PSK31 from now until about 16:15 UTC.  Hope to catch a few of you!
--
Rick - N7WE
070 - #1602

--
Rick - N7WE
070 - #1602


Re: Trying 6m PSK now

Steve VA3FLF/KM4FLF
 

I’m headed over. We had an opening this am but seemed to moved south. I will give it a shot.

Steve 
VA3FLF


On May 24, 2020, at 11:46, Rick - N7WE <n7we1980@...> wrote:

Looks like lots of 6m FT8 from Florida to the Pacific Northwest.  I know that just because FT-8 is open, it doesn't mean PSK, CW or SSB is.  But I'm going to get on 50.290 and CQ using PSK31 from now until about 16:15 UTC.  Hope to catch a few of you!
--
Rick - N7WE
070 - #1602


Re: Trying 6m PSK now

Chuck M
 

Wish I could join you.  Only have an old 6M Maratrac FM transceiver.  Oh well.

73s
Chuck
KD9DVB


On Sunday, May 24, 2020, 12:00:13 PM EDT, William Wagaman <n3gty@...> wrote:


I am calling CQ on 6m now 50.290 I will also listen for a bit de Bill N3GTY

On 2020-05-24 15:46, Rick - N7WE wrote:
Looks like lots of 6m FT8 from Florida to the Pacific Northwest.  I know that just because FT-8 is open, it doesn't mean PSK, CW or SSB is.  But I'm going to get on 50.290 and CQ using PSK31 from now until about 16:15 UTC.  Hope to catch a few of you!
--
Rick - N7WE
070 - #1602


Re: Trying 6m PSK now

William Wagaman
 

I am calling CQ on 6m now 50.290 I will also listen for a bit de Bill N3GTY

On 2020-05-24 15:46, Rick - N7WE wrote:
Looks like lots of 6m FT8 from Florida to the Pacific Northwest.  I know that just because FT-8 is open, it doesn't mean PSK, CW or SSB is.  But I'm going to get on 50.290 and CQ using PSK31 from now until about 16:15 UTC.  Hope to catch a few of you!
--
Rick - N7WE
070 - #1602


Trying 6m PSK now

Rick - N7WE
 

Looks like lots of 6m FT8 from Florida to the Pacific Northwest.  I know that just because FT-8 is open, it doesn't mean PSK, CW or SSB is.  But I'm going to get on 50.290 and CQ using PSK31 from now until about 16:15 UTC.  Hope to catch a few of you!
--
Rick - N7WE
070 - #1602


Re: Alerts?

Steve VA3TPS
 

Hi Mike ,
I have attached my watchlist which is up to date to May 20.
You  also have to go into the files section on AC Log and under watchlist check off the boxes for the type of alert you want.
Remember if you add any if has to be as follows with no spaces ...."VA3TPS","070-526"

Hope this helps you out and will be looking for you in the TDW next weekend.

73 de Steve
VA3TPS # 526


Re: Down but not out!

malcolm heard
 

What four states?

On Sat, May 23, 2020 at 10:53 AM Ken Campbell <n6pcd1@...> wrote:
Jim,
We can be kept quiet for a small fee... 🤣🤣🤣🤣
Anyway, congrats on the new rig, and hope the old one is repairable. Hope to see you during TDW.
Who knows, I might even be able to pick up the final four states I  need for WAS LoTW PSK31 endorsement!
--
All the best,
Ken N6PCD

--

Malcolm Heard, M.S.
7516 South 37th Street
Lincoln, NE 68516
heardmalcolm2017@...
402.202.3853

Leadership • Culture • Talent


Re: Down but not out!

Ken N6PCD
 

Jim,
We can be kept quiet for a small fee... 🤣🤣🤣🤣
Anyway, congrats on the new rig, and hope the old one is repairable. Hope to see you during TDW.
Who knows, I might even be able to pick up the final four states I  need for WAS LoTW PSK31 endorsement!
--
All the best,
Ken N6PCD


Re: Alerts?

Steve McEdwards
 

Hi Mike,
I use AC Log along with HRD so I can't help you with Fldigi.
But I do have my watchlist up to date and I know it has to be entered a particular way to work and mine works great for me.
I am busy getting all of my chores done for the xyl so I will be free next weekend and I will send you or if allowed can post my up to date watchlist later today or tomorrow.
Hope it helps
73 de Steve
VA3TPS #526


On Sat., 23 May 2020 at 10:36 a.m., Jim K5SP
<jinnis@...> wrote:

Jerry that does not answer the question. 

Mike wants to be able to get Alerts in his software, he is specifically looking for 070 club members to complete his LONP.  If you know of a way using his particular software, then  tell him how.

Can anyone help Mike with the combination of FlDigi and ACLog?

Jim K5SP

On 5/22/2020 8:58 PM, Jerry N9AVY wrote:
Just work everyone you hear . Non-070 members are allowed in contests now. So every contact counts !


73, Jerry n9avy
On Friday, May 22, 2020, 08:37:04 PM CDT, Mike W4BZM <behrcave@...> wrote:


(This is probably a stupid question, but I'll bet someone in the club has the answer.  I'm not proud, so...)

Question:  Is there a good way to flag 070 members during the upcoming TDW event?

I'm runing Fldigi 4.1.09 for PSK-31, coupled to N3FJP's Amateur Contact Log 6.6 for logging purposes.  Fldigi is in CAT control and communicates with ACL via TCP API.   When I double click on the station call in the Fldigi receive window, the station info from QRZ.com automatically populates the ACL windows.  ACL has a Watch List function that is supposed to provide an alert when a call on the watch list pops up; however, that doesn't seem to be functional when I have tried to test it.  

1.  Can anyone help with the seemingly non-functional ACL watch list?

2.  Assuming that #1 is resolved, is there a way to load the ACL watch list from the hamclubs.info list, other than manually typing in every PODxS member's call sign?

Note:  I'm only five QSOs away from LONP, and during next weekend's TDW I'd like to concentrate my search on stations that are PODXS members but which I have not logged.  I can generate an Excel spreadsheet to help, but that's either a paper look-up or yet another window open on an already-crowded set of screens.

I know it's likely that only PODXS members will be calling "CQ TDW" and ACL will then flag any never-worked contact as "new", but there is always the 070 member that will just call "CQ" and I'd like to catch those, too.

Any suggestions (other than reverting to an unfamiliar program at this late date) would be appreciated.

Thanks!  
Mike W4BZM

--
Jim,  K5SP #483
Member Services Director


Re: Alerts?

Jim K5SP
 

Jerry that does not answer the question. 

Mike wants to be able to get Alerts in his software, he is specifically looking for 070 club members to complete his LONP.  If you know of a way using his particular software, then  tell him how.

Can anyone help Mike with the combination of FlDigi and ACLog?

Jim K5SP

On 5/22/2020 8:58 PM, Jerry N9AVY wrote:
Just work everyone you hear . Non-070 members are allowed in contests now. So every contact counts !


73, Jerry n9avy
On Friday, May 22, 2020, 08:37:04 PM CDT, Mike W4BZM <behrcave@...> wrote:


(This is probably a stupid question, but I'll bet someone in the club has the answer.  I'm not proud, so...)

Question:  Is there a good way to flag 070 members during the upcoming TDW event?

I'm runing Fldigi 4.1.09 for PSK-31, coupled to N3FJP's Amateur Contact Log 6.6 for logging purposes.  Fldigi is in CAT control and communicates with ACL via TCP API.   When I double click on the station call in the Fldigi receive window, the station info from QRZ.com automatically populates the ACL windows.  ACL has a Watch List function that is supposed to provide an alert when a call on the watch list pops up; however, that doesn't seem to be functional when I have tried to test it.  

1.  Can anyone help with the seemingly non-functional ACL watch list?

2.  Assuming that #1 is resolved, is there a way to load the ACL watch list from the hamclubs.info list, other than manually typing in every PODxS member's call sign?

Note:  I'm only five QSOs away from LONP, and during next weekend's TDW I'd like to concentrate my search on stations that are PODXS members but which I have not logged.  I can generate an Excel spreadsheet to help, but that's either a paper look-up or yet another window open on an already-crowded set of screens.

I know it's likely that only PODXS members will be calling "CQ TDW" and ACL will then flag any never-worked contact as "new", but there is always the 070 member that will just call "CQ" and I'd like to catch those, too.

Any suggestions (other than reverting to an unfamiliar program at this late date) would be appreciated.

Thanks!  
Mike W4BZM

--
Jim,  K5SP #483
Member Services Director


Re: Alerts?

Stephen Melachrinos
 

Jerry's right--all QSOs (not just members) count for points in the TDW. But for LONP-hunting, sometimes it's useful to have unworked members "pop out" at you on the waterfall. So I hope someone can come up with a solution for the Fldigi/N3FLP pairing you have. (I don't use either so I have no clue.)

Note that TDW scoring was changed for this year--it's a mix of last year's "non-members count" and previous years' "exchange member numbers for multipliers" rules. So any QSO (member or non-member) counts as a point, and you count the total number of members for the multiplier total. All non-members count as "member 0000" for the contest, so you even get one extra multiplier for the first non-member you work. And there are six bonus stations to hunt for, with each QSO with a bonus station earning 100 bonus points.

And for those that care about "edge cases", the member/non-member definition for TDW ONLY is a station's status as of the start of the contest. So if someone joins the club during the contest, their QSOs can count (after joining) for LONP credit, but they would still be "member 0000" for the duration of the contest. (I think we'll distribute the highest member number that will count for the contest, just at the start of the contest.)

If anyone has any questions or comments on the new TDW rules, please let me know.

Steve
W3HF


-----Original Message-----
From: Jerry N9AVY <n9avy@...>
To: main@070Club.groups.io
Sent: Fri, May 22, 2020 9:58 pm
Subject: Re: [070Club] Alerts?

Just work everyone you hear . Non-070 members are allowed in contests now. So every contact counts !


73, Jerry n9avy
On Friday, May 22, 2020, 08:37:04 PM CDT, Mike W4BZM <behrcave@...> wrote:


(This is probably a stupid question, but I'll bet someone in the club has the answer.  I'm not proud, so...)

Question:  Is there a good way to flag 070 members during the upcoming TDW event?

I'm runing Fldigi 4.1.09 for PSK-31, coupled to N3FJP's Amateur Contact Log 6.6 for logging purposes.  Fldigi is in CAT control and communicates with ACL via TCP API.   When I double click on the station call in the Fldigi receive window, the station info from QRZ.com automatically populates the ACL windows.  ACL has a Watch List function that is supposed to provide an alert when a call on the watch list pops up; however, that doesn't seem to be functional when I have tried to test it.  

1.  Can anyone help with the seemingly non-functional ACL watch list?

2.  Assuming that #1 is resolved, is there a way to load the ACL watch list from the hamclubs.info list, other than manually typing in every PODxS member's call sign?

Note:  I'm only five QSOs away from LONP, and during next weekend's TDW I'd like to concentrate my search on stations that are PODXS members but which I have not logged.  I can generate an Excel spreadsheet to help, but that's either a paper look-up or yet another window open on an already-crowded set of screens.

I know it's likely that only PODXS members will be calling "CQ TDW" and ACL will then flag any never-worked contact as "new", but there is always the 070 member that will just call "CQ" and I'd like to catch those, too.

Any suggestions (other than reverting to an unfamiliar program at this late date) would be appreciated.

Thanks!  
Mike W4BZM


Re: Alerts?

B. Smith, N3XL
 

Mike,

I probably should have mentioned that you can feed FLDigi into Log4OM. I have it set up that way along with N1MM Logger and WSJT-X feeding into Log4OM. Log4OM also feeds all of the electronic logging sites, fills in names , etc. It is nice and free – although they do accept donations like everybody these days.

 

73, Bill N3XL

 

From: main@070Club.groups.io <main@070Club.groups.io> On Behalf Of B. Smith via groups.io
Sent: Saturday, May 23, 2020 4:01 AM
To: main@070Club.groups.io
Subject: Re: [070Club] Alerts?

 

Mike,

It will be hard to verify the 070 info in particular, but if you use a logging program, Log4OM for example, many have a “Worked Before” feature, you can avoid dupes if you want to.

 

CU in the contest. I work dupes and let the chips fall where they may!

 

73, Bill N3XL

From: main@070Club.groups.io <main@070Club.groups.io> On Behalf Of Mike W4BZM
Sent: Friday, May 22, 2020 21:37 PM
To: main@070Club.groups.io
Subject: [070Club] Alerts?

 

(This is probably a stupid question, but I'll bet someone in the club has the answer  I'm not proud, so...)

Question:  Is there a good way to flag 070 members during the upcoming TDW event?

I'm runing Fldigi 41.09 for PSK-31, coupled to N3FJP's Amateur Contact Log 66 for logging purposes.  Fldigi is in CAT control and communicates with ACL via TCP API   When I double click on the station call in the Fldigi receive window, the station info from QRZ.com automatically populates the ACL windows.  ACL has a Watch List function that is supposed to provide an alert when a call on the watch list pops up; however, that doesn't seem to be functional when I have tried to test it.  

1.  Can anyone help with the seemingly non-functional ACL watch list?

2.  Assuming that #1 is resolved, is there a way to load the ACL watch list from the hamclubs.info list, other than manually typing in every PODxS member's call sign?

Note:  I'm only five QSOs away from LONP, and during next weekend's TDW I'd like to concentrate my search on stations that are PODXS members but which I have not logged.  I can generate an Excel spreadsheet to help, but that's either a paper look-up or yet another window open on an already-crowded set of screens.

I know it's likely that only PODXS members will be calling "CQ TDW" and ACL will then flag any never-worked contact as "new", but there is always the 070 member that will just call "CQ" and I'd like to catch those, too.

Any suggestions (other than reverting to an unfamiliar program at this late date) would be appreciated.

Thanks!  
Mike W4BZM


--
Bill Smith, N3XL


--
Bill Smith, N3XL


Re: Alerts?

B. Smith, N3XL
 

Mike,

It will be hard to verify the 070 info in particular, but if you use a logging program, Log4OM for example, many have a “Worked Before” feature, you can avoid dupes if you want to.

 

CU in the contest. I work dupes and let the chips fall where they may!

 

73, Bill N3XL

From: main@070Club.groups.io <main@070Club.groups.io> On Behalf Of Mike W4BZM
Sent: Friday, May 22, 2020 21:37 PM
To: main@070Club.groups.io
Subject: [070Club] Alerts?

 

(This is probably a stupid question, but I'll bet someone in the club has the answer.  I'm not proud, so...)

Question:  Is there a good way to flag 070 members during the upcoming TDW event?

I'm runing Fldigi 4.1.09 for PSK-31, coupled to N3FJP's Amateur Contact Log 66 for logging purposes.  Fldigi is in CAT control and communicates with ACL via TCP API.   When I double click on the station call in the Fldigi receive window, the station info from QRZ.com automatically populates the ACL windows.  ACL has a Watch List function that is supposed to provide an alert when a call on the watch list pops up; however, that doesn't seem to be functional when I have tried to test it.  

1.  Can anyone help with the seemingly non-functional ACL watch list?

2.  Assuming that #1 is resolved, is there a way to load the ACL watch list from the hamclubs.info list, other than manually typing in every PODxS member's call sign?

Note:  I'm only five QSOs away from LONP, and during next weekend's TDW I'd like to concentrate my search on stations that are PODXS members but which I have not logged.  I can generate an Excel spreadsheet to help, but that's either a paper look-up or yet another window open on an already-crowded set of screens.

I know it's likely that only PODXS members will be calling "CQ TDW" and ACL will then flag any never-worked contact as "new", but there is always the 070 member that will just call "CQ" and I'd like to catch those, too.

Any suggestions (other than reverting to an unfamiliar program at this late date) would be appreciated.

Thanks!  
Mike W4BZM


--
Bill Smith, N3XL


Re: Down but not out!

Lewis Karriker (Sonny) - K4ARE - #2347
 

Jim - I have 2 of those and love them - I bought the first one new and then about a year later found this like new one for a great price.  So, now run one on SSB and the other on Digital - enjoy,

Lewis - K4ARE - 2347

On 5/22/2020 2:06 PM, Jim K5SP wrote:

Shhh! Don't tell XYL that it might be just a battery. Will check that, but just got home from Paris TX, purchased new TS590SG in a "Crazy Deal" from Main Trading Company.

Jim

On 5/22/2020 9:00 AM, Jerry N9AVY wrote:
John:

You may be correct in assessing the problem. THe TS-570 does have a battery and my best guess would be that is the problem. Several years ago I had similar problem with my TS-850SAT and it went screwy.

Replacing battery solved the problem. There a several instructions and videos on the net about replacing TS-570 battery. This may very well be a quick fix !

Jerry n9avy
On Friday, May 22, 2020, 06:14:53 AM CDT, John Kirby <n3aaz_qrp_1@...> wrote:


Jim,

Some Kenwoods  (my TS690S for example) have a mercury battery to keep memory alive. Mine is a CR2430, about the size of a US quarter, with solder tabs, located d-e--e---p  behind front panel.  Been several years since I did a lobotomy, but, full instruction on the www.


72 73 74  P^3
John 1941
N3AAZ 1957
070 1337 / LONP 0349

--
Jim,  K5SP #483
Member Services Director


Re: Alerts?

Jerry N9AVY
 

Just work everyone you hear . Non-070 members are allowed in contests now. So every contact counts !


73, Jerry n9avy

On Friday, May 22, 2020, 08:37:04 PM CDT, Mike W4BZM <behrcave@...> wrote:


(This is probably a stupid question, but I'll bet someone in the club has the answer.  I'm not proud, so...)

Question:  Is there a good way to flag 070 members during the upcoming TDW event?

I'm runing Fldigi 4.1.09 for PSK-31, coupled to N3FJP's Amateur Contact Log 6.6 for logging purposes.  Fldigi is in CAT control and communicates with ACL via TCP API.   When I double click on the station call in the Fldigi receive window, the station info from QRZ.com automatically populates the ACL windows.  ACL has a Watch List function that is supposed to provide an alert when a call on the watch list pops up; however, that doesn't seem to be functional when I have tried to test it.  

1.  Can anyone help with the seemingly non-functional ACL watch list?

2.  Assuming that #1 is resolved, is there a way to load the ACL watch list from the hamclubs.info list, other than manually typing in every PODxS member's call sign?

Note:  I'm only five QSOs away from LONP, and during next weekend's TDW I'd like to concentrate my search on stations that are PODXS members but which I have not logged.  I can generate an Excel spreadsheet to help, but that's either a paper look-up or yet another window open on an already-crowded set of screens.

I know it's likely that only PODXS members will be calling "CQ TDW" and ACL will then flag any never-worked contact as "new", but there is always the 070 member that will just call "CQ" and I'd like to catch those, too.

Any suggestions (other than reverting to an unfamiliar program at this late date) would be appreciated.

Thanks!  
Mike W4BZM

5461 - 5480 of 68328