K3 option request
Locked
12
12
 
|
I think it might be useful at times if the frequency of VFO B could be
displayed as an offset from VFO A (optionally of course). For example, if VFO A is set to 10.113.28 and VFO B is set to 10.114.34, then, if that option were turned on, instead of displaying VFO B's frequency as 10.114.34, it would display as +1.06. This could be useful in SPLIT operation. No big deal, just a thought. 73, Ted, W2ZK ______________________________________________________________ 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 |
|
|
Great suggestion Ted,
It would be a very helpful addition to split operation and add to the Elecraft K3 operating elegance. Frank - W6NEK ----- Original Message ----- From: "Ted Roycraft" <[hidden email]> To: "'Elecraft_List'" <[hidden email]> Sent: Saturday, April 10, 2010 8:19 PM Subject: [Elecraft] K3 option request >I think it might be useful at times if the frequency of VFO B could be > displayed as an offset from VFO A (optionally of course). For example, > if VFO A is set to 10.113.28 and VFO B is set to 10.114.34, then, if > that option were turned on, instead of displaying VFO B's frequency as > 10.114.34, it would display as +1.06. This could be useful in SPLIT > operation. No big deal, just a thought. > > 73, Ted, W2ZK ______________________________________________________________ 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 |
|
|
I think that seems like a good idea too.
Be interesting to see what the "collective" thinking says. Gary VK4FD On Sun, Apr 11, 2010 at 3:25 PM, W6NEK <[hidden email]> wrote: > Great suggestion Ted, > It would be a very helpful addition to split operation and add to the > Elecraft K3 operating elegance. > > Frank - W6NEK > > ----- Original Message ----- > From: "Ted Roycraft" <[hidden email]> > To: "'Elecraft_List'" <[hidden email]> > Sent: Saturday, April 10, 2010 8:19 PM > Subject: [Elecraft] K3 option request > > > >I think it might be useful at times if the frequency of VFO B could be > > displayed as an offset from VFO A (optionally of course). For example, > > if VFO A is set to 10.113.28 and VFO B is set to 10.114.34, then, if > > that option were turned on, instead of displaying VFO B's frequency as > > 10.114.34, it would display as +1.06. This could be useful in SPLIT > > operation. No big deal, just a thought. > > > > 73, Ted, W2ZK > > ______________________________________________________________ > 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 > -- Gary VK4FD - Motorhome Mobile K3 #679 For everything else there's Mastercard!!! ______________________________________________________________ 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 Ted Roycraft
*Display the Shift*:
---I rather like that idea. I've never managed to inteligently use the split yet. And as for tx "2 up" while retaining my rx freq - well I get totally confused. By the time I've done it I missed the boat. But Plus 2 or Minus 2 on the dial would be a KISS method I would cope with! 73 David On Sun, Apr 11, 2010 at 3:19 AM, Ted Roycraft <[hidden email]> wrote: > I think it might be useful at times if the frequency of VFO B could be > displayed as an offset from VFO A (optionally of course). For example, > if VFO A is set to 10.113.28 and VFO B is set to 10.114.34, then, if > that option were turned on, instead of displaying VFO B's frequency as > 10.114.34, it would display as +1.06. This could be useful in SPLIT > operation. No big deal, just a thought. > > 73, Ted, W2ZK > > ______________________________________________________________ > 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 |
|
|
> But Plus 2 or Minus 2 on the dial would be a KISS method I > would cope with! That's what RIT and/or XIT give you. You can enable display of the offset full time by tapping "display" and selecting the offset with the VFO B knob. However, since one is not likely to use RIT/XIT when split it would be handy to have an option that automatically displayed the offset when RIT/XIT are on. 73, ... Joe, W4TV > -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf Of David Dunn > Sent: Sunday, April 11, 2010 5:56 AM > To: Ted Roycraft > Cc: Elecraft_List > Subject: Re: [Elecraft] K3 option request > > > *Display the Shift*: > ---I rather like that idea. I've never managed to > inteligently use the > split yet. And as for tx "2 up" while retaining my rx freq > - well I get > totally confused. By the time I've done it I missed the boat. > > But Plus 2 or Minus 2 on the dial would be a KISS method I > would cope with! > > 73 David > > On Sun, Apr 11, 2010 at 3:19 AM, Ted Roycraft > <[hidden email]> wrote: > > > I think it might be useful at times if the frequency of VFO > B could be > > displayed as an offset from VFO A (optionally of course). For > > example, if VFO A is set to 10.113.28 and VFO B is set to > 10.114.34, > > then, if that option were turned on, instead of displaying VFO B's > > frequency as 10.114.34, it would display as +1.06. This could be > > useful in SPLIT operation. No big deal, just a thought. > > > > 73, Ted, W2ZK > > > > ______________________________________________________________ > > 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 |
|
|
I think the split "option" is a good idea also. People "go split" in
different ways. If the split is close I almost always use the XIT. I have a friend who always uses VFO B because he likes to see the frequency for VFO B. Some logging programs record the split frequency when split using both VFO's but not when using XIT. Some people like to incorporate the split frequency into their log so even though an option would be to show the "delta", the output for logging purposes might remain "frequency". Then if a cluster spot is made after logging a QSO, the "split" will go into the cluster spot...which may be useful for those who "click" to QSY the radio to the cluster spot. Just some thoughts. 73 de Greg-N4CC ______________________________________________________________ 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 Ted Roycraft
I agree that would be a nice feature (and an optional one), but only if I could see the split for a few seconds after the "Split" function is engaged to allow me to easily set VFO B. For example, Icom's menu system on the IC-7800 displays a number (+ or -) when you press and hold split; you dial in the split you want, press split again, and VFO B is set to that frequency.
When I go into split initially, I pay attention to the + or - VFO B transmit frequency. After that, I pay attention to the actual frequency I'm transmitting on. I follow the receiving frequency in the pileup by listening to who is working the DX station, or by seeing the spots on the cluster and moving VFO B to the frequency area where the DX station is working. Having VFO B display only a + or - offset all the time would make it harder to find a good transmit frequency in the pile. Perhaps that "on-the-fly" options could easily be toggled into one display mode or another through panel switch depression (vs a menu driven setting). Lou, W0FK
St. Louis, MO
"The difference between stupidity and genius is that genius has its limits." Albert Einstein |
|
|
In reply to this post by Ted Roycraft
JMO, but, er.... can't we just use math? I.e. subtract or add what's in the VFO B buffer to A? Seems to me this would create more clutter in the options and add little of value that we can't just do in our heads to begin with.
The only use I could see for this is if you just want to blindly add/subtract some offset to whatever is in VFO A. In a split situation I don't see how that'll increase your chances of making the contact and in fact will likely just create more QRM. You have to listen for where the station is listening anyway before you pull the trigger and by that time you've got VFO B set where it needs to be. My personal vote is no as I don't see the value... 73 LS W5QD |
|
|
In reply to this post by GREG WILSON
>Some people like to incorporate the split
frequency into their log so even though an option would be to show the "delta", the output for logging purposes might remain "frequency"< This would be my other quarrel with this. you'd need to retrofit something like this to the option, which is likely already available for free as-is. Remember: just because the DX says (s)he's listening "up 2", doesn't necessarily mean they're actually listening up exactly 2 at the time. IMO, the K3 is already ideally setup the way you want it for working split (as is the K2 even). What I do is: - find the DX (i.e. listen for ubiquitous "up lid", "?" etc. if the station isn't transmitting at the time) - hit A > B - hold Rev and start tuning up the band - release/press Rev as needed to catch the actual QSO between the DX and the other station. Presto, you're ready to go. You don't even need to look at the freq on VFO B except for spot-checking to see what freq. you're on. If you really want to make the contact you have to do this anyway. Just blindly going up by some offset and firing away is terrible practice to begin with that does little but create QRM so I don't see the value of a feature that'll only encourage that hi hi. Just my other .02, 73, LS W5QD |
|
|
Like several others have commented, I see the option
as confusing and unwarranted. Working "split" is -so- very easy, and is the way I -always- use my K3 ... or any other radio. This way the transmitter "stays put" while I "tweak" the receiver tuning. I -never- use the RIT or XIT functions, either. That's a sure way to get "lost" while constantly having to juggle the +/- numbers in one's mind. Which just illustrates that each of us have different ideas about how to accomplish a task. (:-)) Rose and I expect to see some of you at Visalia. Stop at her booth and say "Hello". 73! Ken Kopp - K0PP [hidden email] ______________________________________________________________ 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 lstavenhagen
You're making too big a thing about this. It doesn't have to change the
way you operate. It doesn't suddenly make you pounce "up 1" without listening. It just gives you a different perspective of the environment around the DX's frequency. It doesn't have to change the way logging programs work either. I would suggest that the only effect of this option would be in displaying the frequency offset on the K3's display and not affect frequency queries made by logging programs. Also, not everyone does things the way you do. I have the SUB rx and I don't follow your script for operating. I also have a panadaptor which changes the way I do things. The point is that everyone has their own style and this option would just support that. All I'm suggesting is that this be an option. No one would force you to use it. It's ridiculous to say that this would create QRM. We definitely want to keep those pileups pristine and without QRM and I would never suggest anything that would do that! 73, Ted, W2ZK On 4/11/2010 11:14 AM, lstavenhagen wrote: > >> Some people like to incorporate the split >> > frequency into their log so even though an option would be to show the > "delta", the output for logging purposes might remain "frequency"< > > This would be my other quarrel with this. you'd need to retrofit something > like this to the option, which is likely already available for free as-is. > > Remember: just because the DX says (s)he's listening "up 2", doesn't > necessarily mean they're actually listening up exactly 2 at the time. > > IMO, the K3 is already ideally setup the way you want it for working split > (as is the K2 even). What I do is: > - find the DX (i.e. listen for ubiquitous "up lid", "?" etc. if the station > isn't transmitting at the time) > - hit A> B > - hold Rev and start tuning up the band > - release/press Rev as needed to catch the actual QSO between the DX and the > other station. > > Presto, you're ready to go. You don't even need to look at the freq on VFO B > except for spot-checking to see what freq. you're on. > > If you really want to make the contact you have to do this anyway. Just > blindly going up by some offset and firing away is terrible practice to > begin with that does little but create QRM so I don't see the value of a > feature that'll only encourage that hi hi. > > Just my other .02, > > 73, > LS > W5QD > > ______________________________________________________________ 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 Ted Roycraft
Hi Ted:
I personally like your idea and I would benefit from it. I realize that it would be something you could turn on or off via the CONFIG or MENU or DISPLAY buttons. I also realize that RIT/XIT give you this feature but if you have the SUB RX installed it's more likely that you will want to use VFO B. I don't get all of the negative comments. How does having an available option negatively affect anybody. For example, I have not found AFX to be useful but I see no reason to complain about its existence. It's just a tool in the arsenal that I might find beneficial one day. Now if you really want to see some fireworks, suggest an APF (audio peak filter) for CW. 73, Mike K2MK > > > Ted Roycraft > Sat, 10 Apr 2010 20:19:44 -0700 > > I think it might be useful at times if the frequency of VFO B could be > displayed as an offset from VFO A (optionally of course). For example, > if VFO A is set to 10.113.28 and VFO B is set to 10.114.34, then, if > that option were turned on, instead of displaying VFO B's frequency as > 10.114.34, it would display as +1.06. This could be useful in SPLIT > operation. No big deal, just a thought. > > 73, Ted, W2ZK ______________________________________________________________ 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 Ted Roycraft
>everyone has their own
style and this option would just support that. All I'm suggesting is that this be an option. No one would force you to use it.< But there's a cost - additional complexity to the K3 feature set. I submit that you'd only want to do this if there's a compelling reason to do so. Simply adding a feature with little or no demonstrable use is not something I'd personally want to pester elecraft to do. Again, the K3 is already setup _ideally_ for working split (and I assume also with the sub RX installed) so I just don't see what value this adds (relative to the cost). >It's ridiculous to say that this would create QRM. We definitely want to keep those pileups pristine and without QRM and I would never suggest anything that would do that!< Well lemme put it another way - If you're in that much of a hurry to hit the key that you're unable or unwilling to do simple math on the buffer contents, you probably havn't done the necessary footwork of listening to start with. Instead, you're probably more likely to simply be adding QRM than you are to actually make the QSO. These folks are easy to pick out in the pile; they're 20 over 9 at least and endlessly call and call. Note that the DX takes a while to get back to them if they answer them at all. The chances are good the DX is using a K3 and, since the KW's are off his RX freq. he can't hear them anyway hi hi. 73, LS W5QD |
|
In reply to this post by Ken Kopp-3
On Sun, 11 Apr 2010 15:28:29 -0000, "Ken Kopp" <[hidden email]>
wrote: I agree. Like Ken I have never used RIT/XIT on any rig I've ever owned and I really do like having command of the RX frequency dial (Oops! make that display) to be mine and not a feature. Let's get back to using our heads and not depend on a computer to do it all for us. >Like several others have commented, I see the option >as confusing and unwarranted. Working "split" is -so- >very easy, and is the way I -always- use my K3 ... or any >other radio. This way the transmitter "stays put" while >I "tweak" the receiver tuning. > >I -never- use the RIT or XIT functions, either. That's a >sure way to get "lost" while constantly having to juggle >the +/- numbers in one's mind. > TOM, N5GE BT 73 ES GUD LUK AR DE N5GE SK http://www.n5ge.com ______________________________________________________________ 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
Amateur Radio Operator N5GE
|
|
|
In reply to this post by lstavenhagen
Well LS, if "the K3 is already setup _ideally_ for working split", as
you say, then case closed. Forget I said anything. By the way, I'm not in a hurry to hit the key. I can also do arithmetic in my head. As I said, it gives you a different perspective on the environment around the DX. If your argument is that this option is useless don't use it but let's listen to user comments. So far, there have been more positive ones than negative ones and most of the negative ones have been from the same person. Remember, it would be OPTIONAL. As for Elecraft resources, I would rather hear from the Elecraft people on that rather than from you. You might be right but only Elecraft can say whether this option would cost more development time and resources than other implemented options of equal or lesser value. I personally don't use VFO B very much except for working split and I would find this option useful - not essential but useful. I proposed this option to start a discussion. Please don't shoot it down just because you wouldn't use it. There have been many many options proposed for the K3 that I wouldn't find useful but others would and I haven't weighed in to try and shoot them down just because I wouldn't use them. We get it - you won't use it. It's a danger to world peace. Thanks. 73, Ted, W2ZK On 4/11/2010 12:02 PM, lstavenhagen wrote: > >> everyone has their own >> > style and this option would just support that. All I'm suggesting is > that this be an option. No one would force you to use it.< > > But there's a cost - additional complexity to the K3 feature set. I submit > that you'd only want to do this if there's a compelling reason to do so. > Simply adding a feature with little or no demonstrable use is not something > I'd personally want to pester elecraft to do. > Again, the K3 is already setup _ideally_ for working split (and I assume > also with the sub RX installed) so I just don't see what value this adds > (relative to the cost). > > >> It's ridiculous to say that this would create QRM. We definitely want to >> > keep those pileups pristine and without QRM and I would never suggest > anything that would do that!< > > Well lemme put it another way - If you're in that much of a hurry to hit the > key that you're unable or unwilling to do simple math on the buffer > contents, you probably havn't done the necessary footwork of listening to > start with. Instead, you're probably more likely to simply be adding QRM > than you are to actually make the QSO. These folks are easy to pick out in > the pile; they're 20 over 9 at least and endlessly call and call. Note that > the DX takes a while to get back to them if they answer them at all. The > chances are good the DX is using a K3 and, since the KW's are off his RX > freq. he can't hear them anyway hi hi. > > 73, > LS > W5QD > ______________________________________________________________ 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 |
|
|
Hmm,
Anybody try these things out first? Double tap A>B. Hold <SPLIT>. Tap XIT. Current XIT setting displays briefly. Change XIT to split offset desired. While turning R/XIT knob the offset (e.g. +2.00) displays. When the knob ceases turning, the VFO B reverts to the transmitting frequency (RX+offset) and VFO A shows the receiving frequency. If you have the subRX and have <SUB> on you can listen to both RX and TX frequency. Use that when what you have is the offset from the spot. If you have the actual frequency specified on the spot, turn off XIT and tune VFO B to the specified frequency. What am I missing? 73, Guy. On Sun, Apr 11, 2010 at 12:29 PM, Ted Roycraft <[hidden email]> wrote: > Well LS, if "the K3 is already setup _ideally_ for working split", as > you say, then case closed. Forget I said anything. > > By the way, I'm not in a hurry to hit the key. I can also do arithmetic > in my head. As I said, it gives you a different perspective on the > environment around the DX. If your argument is that this option is > useless don't use it but let's listen to user comments. So far, there > have been more positive ones than negative ones and most of the negative > ones have been from the same person. Remember, it would be OPTIONAL. As > for Elecraft resources, I would rather hear from the Elecraft people on > that rather than from you. You might be right but only Elecraft can say > whether this option would cost more development time and resources than > other implemented options of equal or lesser value. > > I personally don't use VFO B very much except for working split and I > would find this option useful - not essential but useful. I proposed > this option to start a discussion. Please don't shoot it down just > because you wouldn't use it. There have been many many options proposed > for the K3 that I wouldn't find useful but others would and I haven't > weighed in to try and shoot them down just because I wouldn't use them. > We get it - you won't use it. It's a danger to world peace. Thanks. > > 73, Ted, W2ZK > > On 4/11/2010 12:02 PM, lstavenhagen wrote: >> >>> everyone has their own >>> >> style and this option would just support that. All I'm suggesting is >> that this be an option. No one would force you to use it.< >> >> But there's a cost - additional complexity to the K3 feature set. I submit >> that you'd only want to do this if there's a compelling reason to do so. >> Simply adding a feature with little or no demonstrable use is not something >> I'd personally want to pester elecraft to do. >> Again, the K3 is already setup _ideally_ for working split (and I assume >> also with the sub RX installed) so I just don't see what value this adds >> (relative to the cost). >> >> >>> It's ridiculous to say that this would create QRM. We definitely want to >>> >> keep those pileups pristine and without QRM and I would never suggest >> anything that would do that!< >> >> Well lemme put it another way - If you're in that much of a hurry to hit the >> key that you're unable or unwilling to do simple math on the buffer >> contents, you probably havn't done the necessary footwork of listening to >> start with. Instead, you're probably more likely to simply be adding QRM >> than you are to actually make the QSO. These folks are easy to pick out in >> the pile; they're 20 over 9 at least and endlessly call and call. Note that >> the DX takes a while to get back to them if they answer them at all. The >> chances are good the DX is using a K3 and, since the KW's are off his RX >> freq. he can't hear them anyway hi hi. >> >> 73, >> LS >> W5QD >> > > ______________________________________________________________ > 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 lstavenhagen
I don't have enough time in to be a slave to tradition....<grin>. I'm
still learning my K3. What I do is: - find the DX - hit A > B - tune up the band using the VFO B - hold "Split" - send my call, and so on - adjust the VFO B frequency as needed. What I'd like is: - find the DX ( I enjoy finding DX without the cluster, but do use cluster for dxpeditions). - hold "Split" - Tap a button, and then hit "2" or "5" or some other number to quickly set the split frequency - send my call, and so on, - adjust the VFO B frequency as needed. Rich NU6T lstavenhagen wrote: >> Some people like to incorporate the split >> > frequency into their log so even though an option would be to show the > "delta", the output for logging purposes might remain "frequency"< > > This would be my other quarrel with this. you'd need to retrofit something > like this to the option, which is likely already available for free as-is. > > Remember: just because the DX says (s)he's listening "up 2", doesn't > necessarily mean they're actually listening up exactly 2 at the time. > > IMO, the K3 is already ideally setup the way you want it for working split > (as is the K2 even). What I do is: > - find the DX (i.e. listen for ubiquitous "up lid", "?" etc. if the station > isn't transmitting at the time) > - hit A > B > - hold Rev and start tuning up the band > - release/press Rev as needed to catch the actual QSO between the DX and the > other station. > > Presto, you're ready to go. You don't even need to look at the freq on VFO B > except for spot-checking to see what freq. you're on. > > If you really want to make the contact you have to do this anyway. Just > blindly going up by some offset and firing away is terrible practice to > begin with that does little but create QRM so I don't see the value of a > feature that'll only encourage that hi hi. > > Just my other .02, > > 73, > LS > W5QD > > ______________________________________________________________ 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 Guy, K2AV
That might do it Guy. Let me road test it in a pile up if conditions
ever improve. Thanks, Ted, W2ZK On 4/11/2010 12:47 PM, Guy Olinger K2AV wrote: > Hmm, > > Anybody try these things out first? > > Double tap A>B. Hold<SPLIT>. Tap XIT. Current XIT setting > displays briefly. Change XIT to split offset desired. While turning > R/XIT knob the offset (e.g. +2.00) displays. When the knob ceases > turning, the VFO B reverts to the transmitting frequency (RX+offset) > and VFO A shows the receiving frequency. If you have the subRX and > have<SUB> on you can listen to both RX and TX frequency. > > Use that when what you have is the offset from the spot. > > If you have the actual frequency specified on the spot, turn off XIT > and tune VFO B to the specified frequency. > > What am I missing? > > 73, Guy. > > On Sun, Apr 11, 2010 at 12:29 PM, Ted Roycraft<[hidden email]> wrote: > >> Well LS, if "the K3 is already setup _ideally_ for working split", as >> you say, then case closed. Forget I said anything. >> >> By the way, I'm not in a hurry to hit the key. I can also do arithmetic >> in my head. As I said, it gives you a different perspective on the >> environment around the DX. If your argument is that this option is >> useless don't use it but let's listen to user comments. So far, there >> have been more positive ones than negative ones and most of the negative >> ones have been from the same person. Remember, it would be OPTIONAL. As >> for Elecraft resources, I would rather hear from the Elecraft people on >> that rather than from you. You might be right but only Elecraft can say >> whether this option would cost more development time and resources than >> other implemented options of equal or lesser value. >> >> I personally don't use VFO B very much except for working split and I >> would find this option useful - not essential but useful. I proposed >> this option to start a discussion. Please don't shoot it down just >> because you wouldn't use it. There have been many many options proposed >> for the K3 that I wouldn't find useful but others would and I haven't >> weighed in to try and shoot them down just because I wouldn't use them. >> We get it - you won't use it. It's a danger to world peace. Thanks. >> >> 73, Ted, W2ZK >> >> On 4/11/2010 12:02 PM, lstavenhagen wrote: >> >>> >>>> everyone has their own >>>> >>>> >>> style and this option would just support that. All I'm suggesting is >>> that this be an option. No one would force you to use it.< >>> >>> But there's a cost - additional complexity to the K3 feature set. I submit >>> that you'd only want to do this if there's a compelling reason to do so. >>> Simply adding a feature with little or no demonstrable use is not something >>> I'd personally want to pester elecraft to do. >>> Again, the K3 is already setup _ideally_ for working split (and I assume >>> also with the sub RX installed) so I just don't see what value this adds >>> (relative to the cost). >>> >>> >>> >>>> It's ridiculous to say that this would create QRM. We definitely want to >>>> >>>> >>> keep those pileups pristine and without QRM and I would never suggest >>> anything that would do that!< >>> >>> Well lemme put it another way - If you're in that much of a hurry to hit the >>> key that you're unable or unwilling to do simple math on the buffer >>> contents, you probably havn't done the necessary footwork of listening to >>> start with. Instead, you're probably more likely to simply be adding QRM >>> than you are to actually make the QSO. These folks are easy to pick out in >>> the pile; they're 20 over 9 at least and endlessly call and call. Note that >>> the DX takes a while to get back to them if they answer them at all. The >>> chances are good the DX is using a K3 and, since the KW's are off his RX >>> freq. he can't hear them anyway hi hi. >>> >>> 73, >>> LS >>> W5QD >>> >>> >> ______________________________________________________________ >> 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 Guy, K2AV
Now you have two knobs to bump that can change your TX freq. The advantage IMHO to using just XIT is that it allows one to listen on his TX freq by just tapping RIT. (Assumes no 2nd RX---my situation)
If both knob B and the offset knob change the TX freq, neither RIT nor REV let you hear your TX freq. Lots of room for error simply to have the display show the TX freq. Who cares anyway? If it doesn't go into my log, I don't, and the next guy can find the DX listen freq on his own, just like I did. If it's really important to you to see the offset, punch DISP and dial it in. --- On Sun, 4/11/10, Guy Olinger K2AV <[hidden email]> wrote: > From: Guy Olinger K2AV <[hidden email]> > Subject: Re: [Elecraft] K3 option request > To: "Ted Roycraft" <[hidden email]> > Cc: [hidden email] > Date: Sunday, April 11, 2010, 10:47 AM > Hmm, > > Anybody try these things out first? > > Double tap A>B. Hold <SPLIT>. > Tap XIT. Current XIT setting > displays briefly. Change XIT to split offset > desired. While turning > R/XIT knob the offset (e.g. +2.00) displays. When the > knob ceases > turning, the VFO B reverts to the transmitting frequency > (RX+offset) > and VFO A shows the receiving frequency. If you have > the subRX and > have <SUB> on you can listen to both RX and TX > frequency. > > Use that when what you have is the offset from the spot. > > If you have the actual frequency specified on the spot, > turn off XIT > and tune VFO B to the specified frequency. > > What am I missing? > > 73, Guy. > > ______________________________________________________________ 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 Richard-3
Richard Hill wrote:
> What I do is: > - find the DX That's the switch I want on my K3: "Find DX." Tap or Hold, I don't care. 73, Fred K6DGW - Northern California Contest Club - CU in the 2010 Cal QSO Party 2-3 Oct 2010 - www.cqp.org ______________________________________________________________ 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 |
«
Return to [K3]
|
1 view|%1 views
| Free forum by Nabble | Edit this page |