Date   

Re: Explain Something for Me

Jerry N9AVY
 

Joe:
 
 
 
Is there any difference between QRP  in caps  and lowest case ????   Do the caps QRP mean the station is running more power ?   


Jerry  N9AVY


From: "'ljl2002@...' joe_molon@... [070]" <070@...>
To: "070@..." <070@...>
Sent: Monday, July 17, 2017 11:17 AM
Subject: Re: [070] Explain Something for Me

 
This is the reason that I never sign as /QRP because I heard that it screws up some logging programs.  Besides the other Ham is usually surprised to see the power levels when they get the card..
I found it a good practice to watch what I am sending out to catch anything that may not be right so that I can correct it on the next. (I'm not the greatest typist on the planet.)
Should have taken typing in HS when I had the chance.  The teacher was great and the class was all  girls.  What an idiot!

Joe
KA1PPV  #1482



On Monday, July 17, 2017 11:30 AM, "mwbesemer@... [070]" <070@...> wrote:


 
Just my humble opinion, but I find that it makes it HARDER to distinguish the call when it's bracketed like that.

No telling what it does for guys using screen readers.

Mike
WM4B


On Mon, Jul 17, 2017 at 11:22 AM, 'K9HW' k9hw@... [070] wrote:

  
Most do it I think to make their callsign stand out from the other text.  That's why I do it anyway, but I do leave a space between the brackets and the callsign.  All of the software have tried will then recognize that.  HRD doesn't have a problem parsing non-alphabetic or numeric characters, so I don't have a problem with those who don't leave spaces.  Possibly theirs can parse it as well and it hasn't occurred to them that some out there cannot.
 
Harry, K9HW – #1959
 
From: 070@... [mailto:070@...]
Sent: Monday, July 17, 2017 9:12 AM
To: 070@...
Subject: [070] Explain Something for Me
 
[Harry] <<< DELETED >>> 
 
Then there are others who send their call as in brackets.  My software does not recognize that as a call sign so I have to cut and paste it or type it in to make a QSO with that station.  Why do some stations send their call in brackets?
 
Happy Radio!  73,
 
Bill #1688






Re: OO Report

Fr Richard R
 

BZ Jerry


Fr Richard




On Monday, July 17, 2017, 2:12:58 PM EDT, Jerry n9avy@... [070] <070@...> wrote:


 


Wow !   Today I received an OO  Good Operator Report in mail from an OO in CA.
 
Blocked out his signature/call on purpose.  As an OO  , I find this really an honor; especially since some 2-lander was complaining about my signal last week !
 
 
Jerry  N9AVY  #454


OO Report

Jerry N9AVY
 


Wow !   Today I received an OO  Good Operator Report in mail from an OO in CA.
 
Blocked out his signature/call on purpose.  As an OO  , I find this really an honor; especially since some 2-lander was complaining about my signal last week !
 
 
Jerry  N9AVY  #454


Re: Utah Grid Needs

Rick - N7WE
 

Bryon -
Just added DM59 to my list.  But I didn't know what to put for a city.  It looks to be as close to nowhere as you can get in eastern Utah!  Hi hi.

Rick - N7WE
070 - #1602


Re: Explain Something for Me

Mike Flowers
 

I can certainly understand the frustrations when weird text from broken or incomplete macros gets sent, and when the other OM’s callsign is embedded in brackets, dashes or weird ASCII special characters.  We have this sophisticated software on our end – doesn’t the other guy?

 

When operating PSK31, I try (but don’t always succeed) to keep these points in mind:

 

  1. Unless you are in QSO with a PropNet robot, the other op is a human being, and like all of us, prone making to errors.
  2. The digimodes are likely new to many of the ops on the air, so you don’t know where the other op is on their learning curve with the technology.
  3. Like, Joe, I am still the operator of my station, and I am in control and not the software.  If the software is having problems with the data received, then I’ll ‘operate’ the software and capture the callsign, etc., and other data that my logger needs.
  4. Beyond the public service aspects of Amateur Radio, it’s intended to be a hobby and to be fun.  I find that focusing on what the other op is doing ‘wrong’ lessens the fun for me.

 

I was fortunate enough at age 13 to be put through two touch-typing courses at the Columbia Business College.   My mother saw it as inexpensive day-care.  All the other students were young ladies about 18 – 22 years old.   I often had difficulties paying attention to the lessons.  ;>)  The keyboard skills learned there helped me immensely through my IT career.

 

Keep smiling and we’ll see you on the bands!!

 

- 73 and good DX de Mike, K6MKF, Past President - NCDXC

 

From: 070@... [mailto:070@...]
Sent: Monday, July 17, 2017 9:17 AM
To: 070@...
Subject: Re: [070] Explain Something for Me

 

 

This is the reason that I never sign as /QRP because I heard that it screws up some logging programs.  Besides the other Ham is usually surprised to see the power levels when they get the card..

I found it a good practice to watch what I am sending out to catch anything that may not be right so that I can correct it on the next. (I'm not the greatest typist on the planet.)

Should have taken typing in HS when I had the chance.  The teacher was great and the class was all  girls.  What an idiot!

 

Joe

KA1PPV  #1482

 

 

On Monday, July 17, 2017 11:30 AM, "mwbesemer@... [070]" <070@...> wrote:

 

 

Just my humble opinion, but I find that it makes it HARDER to distinguish the call when it's bracketed like that.

 

No telling what it does for guys using screen readers.

 

Mike

WM4B

 

On Mon, Jul 17, 2017 at 11:22 AM, 'K9HW' k9hw@... [070] wrote:

 

  

Most do it I think to make their callsign stand out from the other text.  That's why I do it anyway, but I do leave a space between the brackets and the callsign.  All of the software have tried will then recognize that.  HRD doesn't have a problem parsing non-alphabetic or numeric characters, so I don't have a problem with those who don't leave spaces.  Possibly theirs can parse it as well and it hasn't occurred to them that some out there cannot.

 

Harry, K9HW – #1959

 

From: 070@... [mailto:070@...]

Sent: Monday, July 17, 2017 9:12 AM

To: 070@...

Subject: [070] Explain Something for Me

 

[Harry] <<< DELETED >>> 

 

Then there are others who send their call as in brackets.  My software does not recognize that as a call sign so I have to cut and paste it or type it in to make a QSO with that station.  Why do some stations send their call in brackets?

 

Happy Radio!  73,

 

Bill #1688

 

 


Utah Grid Needs

W7RIV
 

I started this spreadsheet to add all of you.


Please feel free to add to it. Try not to change the layout I've started. DM39 is a pretty easy place to get to. The others are a little further out 3+ hours. Though, I'm happy to see DM58 because that is in Utah 4 Wheeling happy land!

Thanks
Bryon, W7RIV


Re: Explain Something for Me

mwbesemer@...
 


Re: Explain Something for Me

ljl2002@att.net
 

This is the reason that I never sign as /QRP because I heard that it screws up some logging programs.  Besides the other Ham is usually surprised to see the power levels when they get the card..
I found it a good practice to watch what I am sending out to catch anything that may not be right so that I can correct it on the next. (I'm not the greatest typist on the planet.)
Should have taken typing in HS when I had the chance.  The teacher was great and the class was all  girls.  What an idiot!

Joe
KA1PPV  #1482



On Monday, July 17, 2017 11:30 AM, "mwbesemer@... [070]" <070@...> wrote:


 
Just my humble opinion, but I find that it makes it HARDER to distinguish the call when it's bracketed like that.

No telling what it does for guys using screen readers.

Mike
WM4B


On Mon, Jul 17, 2017 at 11:22 AM, 'K9HW' k9hw@... [070] wrote:

  
Most do it I think to make their callsign stand out from the other text.  That's why I do it anyway, but I do leave a space between the brackets and the callsign.  All of the software have tried will then recognize that.  HRD doesn't have a problem parsing non-alphabetic or numeric characters, so I don't have a problem with those who don't leave spaces.  Possibly theirs can parse it as well and it hasn't occurred to them that some out there cannot.
 
Harry, K9HW – #1959
 
From: 070@... [mailto:070@...]
Sent: Monday, July 17, 2017 9:12 AM
To: 070@...
Subject: [070] Explain Something for Me
 
[Harry] <<< DELETED >>> 
 
Then there are others who send their call as in brackets.  My software does not recognize that as a call sign so I have to cut and paste it or type it in to make a QSO with that station.  Why do some stations send their call in brackets?
 
Happy Radio!  73,
 
Bill #1688




DXLab Suite

W7RIV
 

I'm running DX Lab Suite, I have for sometime, big learning curve, but really an awesome program when you start to understand it. I've ran into an issue recently with an error when I try to sync LotW QSLs in the DXKeeper portion. 

I have the latest TQSL installed, my username and password are correct (I tested on the LotW website), and this isn't my first time doing this. For the last couple months I've been occupied and not really working to correct it. The instruction I get from DXLabs Yahoo Group is that Windows Internet Explorer needs to be removed and reinstalled. I've done that. No change.

The error reads, "Unable to download from LotW: download failure"


Any input or experience with this issue from members here in 070?

Thanks,
Bryon, W7RIV


Re: Explain Something for Me

mwbesemer@...
 


Re: Explain Something for Me

Harry Wilkins
 

Most do it I think to make their callsign stand out from the other text.  That's why I do it anyway, but I do leave a space between the brackets and the callsign.  All of the software have tried will then recognize that.  HRD doesn't have a problem parsing non-alphabetic or numeric characters, so I don't have a problem with those who don't leave spaces.  Possibly theirs can parse it as well and it hasn't occurred to them that some out there cannot.

 

Harry, K9HW – #1959

 

From: 070@... [mailto:070@...]
Sent: Monday, July 17, 2017 9:12 AM
To: 070@...
Subject: [070] Explain Something for Me

 

[Harry] <<< DELETED >>> 

 

Then there are others who send their call as in brackets.  My software does not recognize that as a call sign so I have to cut and paste it or type it in to make a QSO with that station.  Why do some stations send their call in brackets?

 

Happy Radio!  73,

 

Bill #1688


Re: Grids

W7RIV
 

I'll look some of these up and see what I can do. I've had intentions to do this, but hasn't happened. I'm fixing my Jeep (I broke an axle 4-wheeling recently) and I'm wanting to take it out and do some mobile operations. I'm happy to create a Google sheet and get these added. Southern Utah is 100+ right now and approaching 100 in Northern Utah so it might be more like late august (maybe APE) or into September.

Anyone else needing grids in Utah let me know, and even if they are grids near the borders of Utah especially Northern Utah.

Bryon, W7RIV

On Sat, Jul 15, 2017 at 5:49 PM, w3hf@... [070] <070@...> wrote:
 

Bryon -


You asked Jerry (not me), but I'll answer too.

DM38, DM39, and DM47.

Steve
W3HF



Re: Explain Something for Me

Jerry N9AVY
 

Have seen it all since 2006...   aaaaaaaarrrrrrrrrrrgggggggggggggghhhhhhhhhhhh !



From: "Bill Garwood n4gbk@... [070]" <070@...>
To: "070@..." <070@...>
Sent: Monday, July 17, 2017 9:45 AM
Subject: [070] Explain Something for Me

 
All of the recent posts about PSK31 operators sending stuff like .  Why do they not know what they are sending out over the air?

I started years ago with PSK31 using MixW software and have stuck with it as it does the job for me.  I always see on my monitor what I am sending whether using macros or when I'm typing.

I guess other software does not have this feature by default or similar?

If I understand why it happens, I may be able to occasionally assist them with getting up to speed.  As has been mentioned, some of these folks cannot be helped as they already know it all, but most are just trying a new mode or new software.

Then there are others who send their call as in brackets.  My software does not recognize that as a call sign so I have to cut and paste it or type it in to make a QSO with that station.  Why do some stations send their call in brackets?

Happy Radio!  73,

Bill #1688



Re: Finally on

Steve W3HF
 

Joe -


Likewise. I saw your call pop us as you worked the SE station, but never saw your trace. Seems to me the band was pretty long last night, at least at that time. I had pretty good copy on stations over 1000 miles away (other than Jon WX5NCO), but not the close-in ones.


Steve

W3HF


---In 070@..., <joe_molon@...> wrote :

Steve W3HF,

I know that you were on 40m last night because I could see the hams talking to you but nada on your end from here.
That is unusual because 40m usually works well locally most of the time.
There's just no accounting for what is going on up there. I get Canadian special event stations in Ontario no problem but then see stations coming in from CA and end up working a station in the Czech Rep. with a 599. I've been on 40m more lately because 20m has been really bad here too.
Good thing I repaired the 40m radio when I did or I would be pretty high and dry here. ( That's "beached" for all you Navy guys) 

Hangin out on 40m.

Joe
KA1PPV  #1482







Re: Weird Eqsl stuff

Bill Garwood
 

Yep, same here…took me a while to mark as duplicates in eQSL.  I do not send replies to the other station, just mark them as duplicates and delete.

 

Bill  N4GBK

 

Sent from Mail for Windows 10

 

From: Jerry n9avy@... [070]
Sent: Monday, July 17, 2017 10:12 AM
To: 070 List Service 070 List Service
Subject: [070] Weird Eqsl stuff

 

 


Just had a number of contacts show up as new, but when I went to confirm them, Eqsl showed them as already confirmed.  ???

 

I never initiate Eqsls, but only confirm what is sent me.

 

Wonder if Eqsl is having problems ?  Anyone see this ?

 

Jerry  n9avy

 


Weird Eqsl stuff

Jerry N9AVY
 


Just had a number of contacts show up as new, but when I went to confirm them, Eqsl showed them as already confirmed.  ???
 
I never initiate Eqsls, but only confirm what is sent me.
 
Wonder if Eqsl is having problems ?  Anyone see this ?
 
Jerry  n9avy


Explain Something for Me

Bill Garwood
 

All of the recent posts about PSK31 operators sending stuff like and CQ CQ de .  Why do they not know what they are sending out over the air?


I started years ago with PSK31 using MixW software and have stuck with it as it does the job for me.  I always see on my monitor what I am sending whether using macros or when I'm typing.


I guess other software does not have this feature by default or similar?


If I understand why it happens, I may be able to occasionally assist them with getting up to speed.  As has been mentioned, some of these folks cannot be helped as they already know it all, but most are just trying a new mode or new software.


Then there are others who send their call as in brackets.  My software does not recognize that as a call sign so I have to cut and paste it or type it in to make a QSO with that station.  Why do some stations send their call in brackets?


Happy Radio!  73,


Bill #1688


Re: first namer

ljl2002@att.net
 

Hey Randy,
Is he the same guy that runs the station???

Joe
KA1PPV  #1482


On Sunday, July 16, 2017 11:36 PM, "Jerry n9avy@... [070]" <070@...> wrote:


 
I agree.



From: "'Justin Mattes-KC2GIK' kc2gik@... [070]" <070@...>
To: 070@...
Sent: Sunday, July 16, 2017 10:32 PM
Subject: Re: [070] first namer

 
I have been following this thread from the beginning and still have no
idea why it's cntinuing on for so long. Especially since the ham can't
read it. Maybe people should be forwarding these messages to him so he
sees the error of his ways. Seriously whenever I read about a wrong doing
over the air by a non-member on this list, I think to myself time might be
better spent dropping the offending operate a polite email explaining to
him how to become a better opeator

Justin KC2GIK

> Only 23 lookups on QRZ. Must be a new Ham.
>
>
> Randy W4RTT
>
>
> ________________________________
> From: 070@... <070@...> on behalf of randy true
> w4rttrandy@... [070] <070@...>
> Sent: Sunday, July 16, 2017 10:42 PM
> To: 070@...
> Subject: Re: [070] first namer
>
>
>
> Yeah, he's around 7.070.7
>
>
> Randy W4RTT
>
>
> ________________________________
> From: 070@... <070@...> on behalf of Jon Greene -
> wx5nco wx5nco@... [070] <070@...>
> Sent: Sunday, July 16, 2017 10:41 PM
> To: randy true w4rttrandy@... [070]
> Subject: Re: [070] first namer
>
>
>
> You mean the
>
> BTU Your Call de XX#XXX kn ??
>
> I noticed he said he is running between 20 and 100 watts????
>
> 73
> Jon Greene WX5NCO
> Tulsa, Oklahoma EM26
> 070 - 592
> 30DMC - 1233
> DMC - 741
> EPC - 5134
> 1010 - 74420
>
>
>
>
>
> On Sunday, July 16, 2017, 9:38:30 PM CDT, randy true
> w4rttrandy@... [070] <070@...> wrote:
>
>
>
>
> Uh oh, looks like the dude with the "first name" macro is back on.
>
>
> Randy W4RTT
>
>
>
>






Re: Finally on

ljl2002@att.net
 

Steve W3HF,

I know that you were on 40m last night because I could see the hams talking to you but nada on your end from here.
That is unusual because 40m usually works well locally most of the time.
There's just no accounting for what is going on up there. I get Canadian special event stations in Ontario no problem but then see stations coming in from CA and end up working a station in the Czech Rep. with a 599. I've been on 40m more lately because 20m has been really bad here too.
Good thing I repaired the 40m radio when I did or I would be pretty high and dry here. ( That's "beached" for all you Navy guys) 

Hangin out on 40m.

Joe
KA1PPV  #1482



On Sunday, July 16, 2017 10:03 PM, "Jerry n9avy@... [070]" <070@...> wrote:


 
Randy is correct ... 20m was like walking thru the desert....   lousy , lousy conditions...   signals were 599 one minute and gone the next !
 
Jerry  n9avy



From: "randy true w4rttrandy@... [070]" <070@...>
To: "070@..." <070@...>
Sent: Sunday, July 16, 2017 8:46 PM
Subject: Re: [070] Finally on

 
It's not your antenna. 20 has been up and down all day. Everything else sucked too.

Randy W4RTT



From: 070@... <070@...> on behalf of Jon Greene - wx5nco wx5nco@... [070] <070@...>
Sent: Sunday, July 16, 2017 8:37 PM
To: 070 List Service 070 List Service
Subject: [070] Finally on
 
 
I'm finally on PSK.  Been a long weekend of work, cleaning/re-arranging the shack, and playing with some JT65.  I've gone over to 20 psk, and it's been dead all day.  I'm seeing some signals on 40.  I NEEEEEEEEEEEEEEEED to get a better 40m antenna.
Where 'bouts are y'all on the bands tonight?  

73
Jon Greene WX5NCO
Tulsa, Oklahoma EM26
070 - 592
30DMC - 1233
DMC - 741
EPC - 5134
1010 - 74420

 





Re: ???

ljl2002@att.net
 

Hey Jerry,

 RTFM was exactly what we said when we were assembling nuclear  warheads in the Army  too!

Joe
KA1PPV  #1482


On Sunday, July 16, 2017 7:31 PM, "Jerry n9avy@... [070]" <070@...> wrote:


 
RTFM  -  have given that advice for last 47 years in service industry.  



From: "n7we1980@... [070]" <070@...>
To: 070@...
Sent: Sunday, July 16, 2017 6:01 PM
Subject: RE: [070] ???

 
"RT-M" assumes one can read and understand.  Not a safe assumption any more.  "Plug and Play" was an attempt to make things idiot proof.  All it did was make more idiots.  The Law of Unintended Consequences struck again!

IMHO!

Rick - N7WE
070 - #1602  




13681 - 13700 of 65339