Date   

Re: QRP Still happens!

RANDY RUEMLER Member 2706
 

Good Job Steve.  The 817 is a great radio and is a lot of fun foe CW and PSK31.  Enjoy!  

Randy Ruemler

KK4OVW 

On Wednesday, February 19, 2020, 9:07 PM, Steve R via Groups.Io <oldjavadrinker@...> wrote:

I obtained an FT817ND from an estate sale a couple of months back. I have been slowly putting this thing together for digital ops. Had to order CAT cable, Signal link etc....

Tonight all the bugs are worked out, DM780 interfaced, and worked my first PSK contact into MO on the rig with 5 watts and 40M dipole about 15 feet up. Thanks KD0UN for the contact.

Steve
2301
VA3FLF


QRP Still happens!

Steve VA3FLF/KM4FLF
 

I obtained an FT817ND from an estate sale a couple of months back. I have been slowly putting this thing together for digital ops. Had to order CAT cable, Signal link etc....

Tonight all the bugs are worked out, DM780 interfaced, and worked my first PSK contact into MO on the rig with 5 watts and 40M dipole about 15 feet up. Thanks KD0UN for the contact.

Steve
2301
VA3FLF


Re: Bogus Eqsls ???

Rick - N7WE
 

I sometimes get new eQSL notices with the "Reject" or "Create" options prominently displayed.  Since I tend to be compulsive about uploading ALL my Qs to eQSL, it is surprising to get an unconfirmed. So I always look back in my log to check them out.  Often I find that the date, time, band info on the new one matches a log entry but the call doesn't match.  That leads me to dig deeper, and while some of them are just plain "not in my log," in others it is a case of the sender changing to a new call sign.  In that case, it too gets the "not in my log."  Don't know why anyone would 'update' their eQSLs changing their old call sign to the new one instead of just merging accounts, but some do!  Oh well, looking back through my log is always fun.
--
Rick - N7WE
070 - #1602


Re: Bogus Eqsls ???

Richard Rohrer
 

Hi Steve,

No I don't think anyone is doing it intentionally, I just find it interesting to get duplicate eqsls with some slightly different information.  The logging program I use, codes each entry when uploaded, so if I want to upload again I have to go in and delete the code.  Just kind of a thought on Jerry's comment.  I do get some that I can't find in my log and when I look back through the text files I either don't find them at all or the qso was never completed, as they faded out before signal exchange was completed.  Just my thoughts. 

73
Dick - KC3EF


Re: NA QSOP RTTY on 29 Feb

Rick - N7WE
 

Thanks for the heads up Mike!  Get on early and get it done is really good advice!
--
Rick - N7WE
070 - #1602


NA QSOP RTTY on 29 Feb

Mike W4BZM
 

if you’re planning on logging that PSK-31 contact on 29 Feb for the 366 day award, you might want to get on the air early to do so.  The North American QSO Party for RTTY kicks off at 1800 UTC on 29 Feb, and history tells us we will have RTTY transmissions scattered throughout the 070 to 074 bands.  Not grumbling — they are legal there, and most are not aware of the significance of Leap Day for PODXS awards.   Just suggesting early ops for PSK-31.

Mike W4BZM


Endorsement checker problems

Jerry N9AVY
 

Hi Everyone !

Looks like I can no longer approve endorsements for the past 2 weeks. Not sure what exactly happened here, but I keep getting "Software Error" every time I try to access the endorsements for approval. There's a bunch in the queue that I'm unable to process.

Have checked everything that I could and can find no reasons for the problem. At some point in last couple weeks something happened either on my computer or on the site. So , here I sit dead in the water, not knowing what else to do.

Until further notice no endorsements can be processed by yours truly.

Sorry for bad news....


Jerry n9avy


Re: Bogus Eqsls ???

Jerry N9AVY
 

Eqsl at one time claimed that "bogus QSOs" were done intentionally and that is why they requested everyone check Eqsls against their logs. It's sad that there a few individuals who feel the need to "cheat", but it happens. Many years ago I knew an SWL who was caught cheating red-handed and the results weren't nice.

Jerry

On Tuesday, February 18, 2020, 06:58:28 PM CST, Stephen Melachrinos via Groups.Io <melachri@...> wrote:


> A lot of times I find that they are and have already been verified, but the other operator must have re-sent them with some thing changed, like time or something.  Don't know why they do this.

Dick -

My guess is that's an artifact of their logging program. They may have it set to "upload automatically all new QSOs." They might then update the QSO if they either find a spelling error ("Rick" instead of "Dick", or in the QTH, or something), and then the logger views this as a new QSO.

I doubt if the operator is doing it intentionally.

Steve
W3HF

-


Re: Bogus Eqsls ???

Stephen Melachrinos
 

> A lot of times I find that they are and have already been verified, but the other operator must have re-sent them with some thing changed, like time or something.  Don't know why they do this.

Dick -

My guess is that's an artifact of their logging program. They may have it set to "upload automatically all new QSOs." They might then update the QSO if they either find a spelling error ("Rick" instead of "Dick", or in the QTH, or something), and then the logger views this as a new QSO.

I doubt if the operator is doing it intentionally.

Steve
W3HF

-


Re: Bogus Eqsls ???

Richard Rohrer
 

Hi Jerry,

When I download from EQSL I always seem to get a couple that are not in the log.  A lot of times I find that they are and have already been verified, but the other operator must have re-sent them with some thing changed, like time or something.  Don't know why they do this.   I think lotw matches better, but that is just my opinion.  Do you still need EL59 in LA?  Will be going thru there in April again.  

73
Dick - KC3EF


Re: Bogus Eqsls ???

 

Art,
It has done it to me several times.  Go into the Sounds and check the levels for recording, good chance the update muted the mic


Re: Bogus Eqsls ???

John Fickler
 

You might have to re-install the drivers associated with the microphone/line input.

John
W8VYM

On Tue, Feb 18, 2020 at 12:24 PM K7DWI Art <k7dwicn82@...> wrote:
When I got back on the air in Oregon this last August, I made a few FT8 QSOs to see id everything was working okay.
I am quickly learning that with a mountain to my east and northeast that it is easier to work Asian, Oceania and Australia than the Midwest U.S.
After a couple of weeks, I received 2 European SWL QSL requests on eQSL. Both requests showed who I had QSO'd with and the report I had sent.
After a few more weeks,  I have come to terms that I am not working Europe, let alone getting WAS anytime in the foreseeable future. I am only hearing California on PSK31 (but have worked Texas and Arizona).
I finally realized those 2 European QSL requests came off of one of the real time reporting sites.  Policy is no more SWL QSLs will be accepted and those QSLs were deleted. All my logging ADIF files are loaded to both eQSL and LOTW and are automatically checked off in a matching. 

Now I have a new problem. A recent Windows 10 update has killed my input device on a laptop. External microphone/line input does not function. Thank you Microsoft!!
I hope to get my tower up eventually with a new HF beam. Praying it helps or will have to go longpath or backscatter as the Sun gets active again. Also have a 800 year old mast for a 160 Meter sloper (Sequoia).

73 Art K7DWI #2518


Re: Bogus Eqsls ???

K7DWI Art
 

When I got back on the air in Oregon this last August, I made a few FT8 QSOs to see id everything was working okay.
I am quickly learning that with a mountain to my east and northeast that it is easier to work Asian, Oceania and Australia than the Midwest U.S.
After a couple of weeks, I received 2 European SWL QSL requests on eQSL. Both requests showed who I had QSO'd with and the report I had sent.
After a few more weeks,  I have come to terms that I am not working Europe, let alone getting WAS anytime in the foreseeable future. I am only hearing California on PSK31 (but have worked Texas and Arizona).
I finally realized those 2 European QSL requests came off of one of the real time reporting sites.  Policy is no more SWL QSLs will be accepted and those QSLs were deleted. All my logging ADIF files are loaded to both eQSL and LOTW and are automatically checked off in a matching. 

Now I have a new problem. A recent Windows 10 update has killed my input device on a laptop. External microphone/line input does not function. Thank you Microsoft!!
I hope to get my tower up eventually with a new HF beam. Praying it helps or will have to go longpath or backscatter as the Sun gets active again. Also have a 800 year old mast for a 160 Meter sloper (Sequoia).

73 Art K7DWI #2518


Welcome 2733

Jim K5SP
 

Please join me in welcoming our new member(s):

2733  Rob  KC4UPR

Jim K5SP
Membership Director
--
Jim,  K5SP #483
Member Services Director


Bogus Eqsls ???

Jerry N9AVY
 

This morning I received about 7 Eqsls from a YO3 station. Checked against my actual logs and found only 2 were legitimate while the rest (all from 2013) were fake. Got to be careful with Eqsl as there seem to be some who put in bogus data.

Jerry n9avy


Bogus Eqsls

Jerry N9AVY
 


Bogus Eqsls

Jerry N9AVY
 


Re: Welcome 2732

DAVE KB3RAN 1692/381
 

Welcome to the group, JJ.  Hope to see you on the air soon.  

BTW, it was an interesting sprint.  Had 3 time periods: 6 contacts, 5 contacts then 8 contacts.  Only one dup; thanks Stan.  Maybe this might be turned into a 24 hours contest???

Dave H
KB3RAN
1692/381

--
Dave H
KB3RAN
1692/381


Welcome 2732

Jim K5SP
 

Please join me in welcoming our new member(s):

2732  JJ  WR5E

Jim K5SP
Membership Director
--
Jim,  K5SP #483
Member Services Director


Re: Valentine Sprint Soapbox

Jim K5SP
 

Barry, 40 died here about 45 minutes in. Went to 80, and there were lots of members there.

Went back to 40 around 0230z, wanted to work left coast. Nothing at all, stayed there until around 0400Z, dead, so went QRT. Thought maybe left coast fell off into the ocean.

Jim K5SP 



Sent via the Samsung Galaxy S10e, an AT&T 5G Evolution capable smartphone


-------- Original message --------
From: "1470 via Groups.Io" <boat.anchor@...>
Date: 2/14/20 12:34 PM (GMT-06:00)
To: 070Club@groups.io
Subject: Re: [070Club] Valentine Sprint Soapbox

On Fri, Feb 14, 2020 at 06:10 AM, 1470 wrote:
Last night was a bust.
Still trying on 40M this morning 1400Z
Barry
4 1/2 hrs later still empty log.
Time to organize valentines for my sweetie of 42yrs.
Happy Valentine to everyone
Barry
--
Jim,  K5SP #483
Member Services Director

6021 - 6040 of 68029