Bert wrote:
> I've yet to hear --... ...-- ... sent - hihi Don't you mean --... ...-- .----. ... ? :-) My pet peeve is use of that damned "BK". "KN" doesn't make much sense either...that's actually an open parenthesis. Both are just ham-only prosigns that would never have been heard on professional military or commercial Morse radiotelegraph circuits. What's wrong with the military standard: If a response is expected from the other station, send "K" (equivalent to phone "OVER"). If a response is not expected, send "AR" (equivalent to phone "OUT"). That's it in total! There's zero value to that repulsive "BK" that has spread like an ugly malignant Morse teratoma among many hams in the past decade or so. Mike / KK5F ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
sounds good to me...AR
On 19 July 2011 13:04, Mike Morrow <[hidden email]> wrote: > Bert wrote: > > > I've yet to hear --... ...-- ... sent - hihi > > Don't you mean --... ...-- .----. ... ? :-) > > My pet peeve is use of that damned "BK". "KN" doesn't make much sense > either...that's actually an open parenthesis. Both are just ham-only > prosigns that would never have been heard on professional military or > commercial Morse radiotelegraph circuits. > > What's wrong with the military standard: If a response is expected from > the other station, send "K" (equivalent to phone "OVER"). If a response > is not expected, send "AR" (equivalent to phone "OUT"). That's it in > total! > > There's zero value to that repulsive "BK" that has spread like an ugly > malignant Morse teratoma among many hams in the past decade or so. > > Mike / KK5F > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > -- VK4FD - Motorhome Mobile Elecraft Equipment K3 #679, KPA-500 #018 Living the dream!!! ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
When I hear something like UA9CDC de UA9AFK I always wonder if it is UA9AFK
or UA9AF K I always thought that BK is used when one wants to omit sending both call signs in the end of message. I also thought that station sending BK wants to tell me that he is using break in and therefore can be interrupted whenever is needed. 73, Igor UA9CDC ----- Original Message ----- From: "Gary Gregory" <[hidden email]> To: "Mike Morrow" <[hidden email]> Cc: <[hidden email]> Sent: Tuesday, July 19, 2011 9:25 AM Subject: Re: [Elecraft] 'Q' signal trivia > sounds good to me...AR > > On 19 July 2011 13:04, Mike Morrow <[hidden email]> wrote: > >> Bert wrote: >> >> > I've yet to hear --... ...-- ... sent - hihi >> >> Don't you mean --... ...-- .----. ... ? :-) >> >> My pet peeve is use of that damned "BK". "KN" doesn't make much sense >> either...that's actually an open parenthesis. Both are just ham-only >> prosigns that would never have been heard on professional military or >> commercial Morse radiotelegraph circuits. >> >> What's wrong with the military standard: If a response is expected from >> the other station, send "K" (equivalent to phone "OVER"). If a response >> is not expected, send "AR" (equivalent to phone "OUT"). That's it in >> total! >> >> There's zero value to that repulsive "BK" that has spread like an ugly >> malignant Morse teratoma among many hams in the past decade or so. >> >> Mike / KK5F >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> > > > > -- > > VK4FD - Motorhome Mobile > Elecraft Equipment > K3 #679, KPA-500 #018 > Living the dream!!! > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
bk doesn't bother me so much if it's sent as BK and not _BK_ (i.e. not run together). For clarity's sake, if I just end with K I leave an extra amount of space so that meaning is clear, per Igor's note below.
I don't ever use _KN_ myself anymore. Mostly because, yes, it's a parentheses, but also because all the ARRL books I ever read when I was studying back in the '80's, and these books were older than that by some amount, said that _KN_ means something like, "I only want a response from the other station, no breaking stations please", which doesn't seem terribly friendly. -- Buddy Brannan, KB5ELV - Erie, PA Phone: (814) 860-3194 or 888-75-BUDDY On Jul 19, 2011, at 8:05 AM, Igor Sokolov wrote: > When I hear something like UA9CDC de UA9AFK I always wonder if it is UA9AFK > or UA9AF K > I always thought that BK is used when one wants to omit sending both call > signs in the end of message. I also thought that station sending BK wants to > tell me that he is using break in and therefore can be interrupted whenever > is needed. > > 73, Igor UA9CDC > > ----- Original Message ----- > From: "Gary Gregory" <[hidden email]> > To: "Mike Morrow" <[hidden email]> > Cc: <[hidden email]> > Sent: Tuesday, July 19, 2011 9:25 AM > Subject: Re: [Elecraft] 'Q' signal trivia > > >> sounds good to me...AR >> >> On 19 July 2011 13:04, Mike Morrow <[hidden email]> wrote: >> >>> Bert wrote: >>> >>>> I've yet to hear --... ...-- ... sent - hihi >>> >>> Don't you mean --... ...-- .----. ... ? :-) >>> >>> My pet peeve is use of that damned "BK". "KN" doesn't make much sense >>> either...that's actually an open parenthesis. Both are just ham-only >>> prosigns that would never have been heard on professional military or >>> commercial Morse radiotelegraph circuits. >>> >>> What's wrong with the military standard: If a response is expected from >>> the other station, send "K" (equivalent to phone "OVER"). If a response >>> is not expected, send "AR" (equivalent to phone "OUT"). That's it in >>> total! >>> >>> There's zero value to that repulsive "BK" that has spread like an ugly >>> malignant Morse teratoma among many hams in the past decade or so. >>> >>> Mike / KK5F >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> >> >> >> >> -- >> >> VK4FD - Motorhome Mobile >> Elecraft Equipment >> K3 #679, KPA-500 #018 >> Living the dream!!! >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
BK sent as a procedural .... was originally brought about by the conversion of stations to automatic control of changeover from xmit to rx... with seperate rx/tx and no controling assistance, it took some time to cut the high voltage from the tx, change the antenna feed to the rx, and unmute the rx. Then when the other fellow was done, and sent his "k", the reverse had to be done... the prosign "BK" was used to let the other station know that you had fast changeover and he could start talking right away... rather than wait until he figured the changeover had been made. That one prosign speeded up converstaions a whole lot. Now.. no one needs use it.. as everyone but the brave, have xceivers that changeover very fast. Have a great day, --... ...-- Dale - WC7S in Wy ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
In reply to this post by Buddy Brannan
I normally don't respond to these threads on the Elecraft reflector because all they do is create clutter, but the over use of KN brings to mind a very funny situation I noted on 30 meters the other day. Someone (who shall remain nameless to avoid hard feelings/embarrassment on his part) was calling CQ and ending with KN.
Needless to say, I didn't bother to call him as he evidently only wanted to hear himself send and didn't really want to talk to anyone. Jim - W0EB > I don't ever use _KN_ myself anymore. > Buddy Brannan, KB5ELV - Erie, PA > Phone: (814) 860-3194 or 888-75-BUDDY ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
In reply to this post by Buddy Brannan
KN also tells a breaking station that you're in QSO. So if they creep
up on your signal during the tail end (callsign exchange), the context is clear. I've always taken KN to mean a context marking rather than some unfriendly indicator of exclusion. Haven't met any hams that are like that.... :) 73, matt W6NIA On Tue, 19 Jul 2011 08:31:18 -0400, you wrote: >bk doesn't bother me so much if it's sent as BK and not _BK_ (i.e. not run together). For clarity's sake, if I just end with K I leave an extra amount of space so that meaning is clear, per Igor's note below. > >I don't ever use _KN_ myself anymore. Mostly because, yes, it's a parentheses, but also because all the ARRL books I ever read when I was studying back in the '80's, and these books were older than that by some amount, said that _KN_ means something like, "I only want a response from the other station, no breaking stations please", which doesn't seem terribly friendly. ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
Exclusion is not always unfriendly. I have often heard net members converse
before or after a net about net matters, using KN. 73 Kate K6HTN On Tue, Jul 19, 2011 at 6:29 AM, Matt Zilmer <[hidden email]> wrote: > KN also tells a breaking station that you're in QSO. So if they creep > up on your signal during the tail end (callsign exchange), the context > is clear. I've always taken KN to mean a context marking rather than > some unfriendly indicator of exclusion. Haven't met any hams that are > like that.... :) > > 73, > matt W6NIA > > > > > On Tue, 19 Jul 2011 08:31:18 -0400, you wrote: > > >bk doesn't bother me so much if it's sent as BK and not _BK_ (i.e. not run > together). For clarity's sake, if I just end with K I leave an extra amount > of space so that meaning is clear, per Igor's note below. > > > >I don't ever use _KN_ myself anymore. Mostly because, yes, it's a > parentheses, but also because all the ARRL books I ever read when I was > studying back in the '80's, and these books were older than that by some > amount, said that _KN_ means something like, "I only want a response from > the other station, no breaking stations please", which doesn't seem terribly > friendly. > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
True. Sometimes, you would want uninterrupted exchanges, for clarity,
but also leave the net open for breaks. In practice, we break in if needed anyway. Anyone listening to a directed net really hears a KN via the Over. On Navy-Marine Corps MARS, there is no simple way to break in except for calling out Flash or Immediate traffic. Pretty common with MARS, unless the net is free. Even then, contact is between two stations in general. 73, matt W6NIA On Tue, 19 Jul 2011 06:39:54 -0700, you wrote: >Exclusion is not always unfriendly. I have often heard net members converse >before or after a net about net matters, using KN. > >73 Kate K6HTN > >On Tue, Jul 19, 2011 at 6:29 AM, Matt Zilmer <[hidden email]> wrote: > >> KN also tells a breaking station that you're in QSO. So if they creep >> up on your signal during the tail end (callsign exchange), the context >> is clear. I've always taken KN to mean a context marking rather than >> some unfriendly indicator of exclusion. Haven't met any hams that are >> like that.... :) >> >> 73, >> matt W6NIA >> >> >> >> >> On Tue, 19 Jul 2011 08:31:18 -0400, you wrote: >> >> >bk doesn't bother me so much if it's sent as BK and not _BK_ (i.e. not run >> together). For clarity's sake, if I just end with K I leave an extra amount >> of space so that meaning is clear, per Igor's note below. >> > >> >I don't ever use _KN_ myself anymore. Mostly because, yes, it's a >> parentheses, but also because all the ARRL books I ever read when I was >> studying back in the '80's, and these books were older than that by some >> amount, said that _KN_ means something like, "I only want a response from >> the other station, no breaking stations please", which doesn't seem terribly >> friendly. >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
In reply to this post by Jim Sheldon
Many late-model hams would say that "KN" means "OK now", meaning "go ahead and call/talk to me, I'm listening". (:-) 73! Ken - K0PP ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
In reply to this post by Matt Zilmer
Exactly! Which is why I continue to use KN. I only use K when calling CQ.
On Tue, 19 Jul 2011 06:29:06 -0700 Matt Zilmer <[hidden email]> wrote: > KN also tells a breaking station that you're in QSO. So if they creep > up on your signal during the tail end (callsign exchange), the context > is clear. I've always taken KN to mean a context marking rather than > some unfriendly indicator of exclusion. Haven't met any hams that are > like that.... :) > > 73, > matt W6NIA > > > > > On Tue, 19 Jul 2011 08:31:18 -0400, you wrote: > >>bk doesn't bother me so much if it's sent as BK and not _BK_ (i.e. not run >>together). For clarity's sake, if I just end with K I leave an extra amount >>of space so that meaning is clear, per Igor's note below. >> >>I don't ever use _KN_ myself anymore. Mostly because, yes, it's a >>parentheses, but also because all the ARRL books I ever read when I was >>studying back in the '80's, and these books were older than that by some >>amount, said that _KN_ means something like, "I only want a response from the >>other station, no breaking stations please", which doesn't seem terribly >>friendly. > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html |
Free forum by Nabble | Edit this page |