Re: [Elecraft] K3/0 mini remoting problem
Great!Happy to hear it was such an easy fix! 73 de Jim - KE8G Sent from my iPad > On Oct 3, 2014, at 11:25 PM, "bwru...@gmail.com" wrote: > > Wow! Just unplugged and replugged all the RS232 lines, and it works! > > Thanks for the help--- I am very pleased with the result. > > 73 de Brian W3BW > > > > Brian F. Wruble, C.F.A. > From my iPad > > >> On Oct 3, 2014, at 10:43 PM, KE8G wrote: >> >> Hi Brian, >> Try removing the cable from the K3 RS232 and make sure no dust is there. >> >> I had a very similar problem and it turned out to be a little dust! >> >> 73 de Jim - KE8G >> >> Sent from my iPad >> >>> On Oct 3, 2014, at 10:00 PM, "bwru...@gmail.com" wrote: >>> >>> Hi guys: >>> >>> Last year, I had wonderful success controlling my "big station" (K3, >>> KPA500,KAT500) on Maryland's Eastern Shore from our winter home in Key >>> West. When I took the setup down last May, I carefully documented every >>> step required to set things back up. >>> >>> Well, I have just gone through that process, and I can't get it to work --- >>> at least not from within my own LAN and from another home LAN using a >>> downstream router. >>> >>> I can turn on the K3 from the K3/0 mini, and I can hear the audio from the >>> K3 but I cannot control the K3. Also, the freq. readout on the mini does >>> not correspond to the K3 and does not change with movement of the mini vfo >>> dial. The mini cannot turn off the K3. The mini also comes up with "TERM" >>> showing, which I don't remember from the last time I did this. (I can clear >>> that by holding down the "CONFIG" button for 3 seconds.). >>> >>> I am pretty sure this has to do with the configuration of the control end >>> RemoteRig. I have had problems in the past getting things to work from >>> within my own home --- whether same LAN or a downstream LAN. Problem is, I >>> don't want to get to Key West and discover it doesn't work. >>> >>> Can anyone suggest things for me to try? >>> >>> Tnx. 73, >>> >>> Brian W3BW >>> >>> >>> >>> Brian F. Wruble, C.F.A. >>> From my iPad >>> >>> __ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:Elecraft@mailman.qth.net >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to k...@cox.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/0 mini remoting problem
Wow! Just unplugged and replugged all the RS232 lines, and it works! Thanks for the help--- I am very pleased with the result. 73 de Brian W3BW Brian F. Wruble, C.F.A. >From my iPad > On Oct 3, 2014, at 10:43 PM, KE8G wrote: > > Hi Brian, > Try removing the cable from the K3 RS232 and make sure no dust is there. > > I had a very similar problem and it turned out to be a little dust! > > 73 de Jim - KE8G > > Sent from my iPad > >> On Oct 3, 2014, at 10:00 PM, "bwru...@gmail.com" wrote: >> >> Hi guys: >> >> Last year, I had wonderful success controlling my "big station" (K3, >> KPA500,KAT500) on Maryland's Eastern Shore from our winter home in Key West. >> When I took the setup down last May, I carefully documented every step >> required to set things back up. >> >> Well, I have just gone through that process, and I can't get it to work --- >> at least not from within my own LAN and from another home LAN using a >> downstream router. >> >> I can turn on the K3 from the K3/0 mini, and I can hear the audio from the >> K3 but I cannot control the K3. Also, the freq. readout on the mini does not >> correspond to the K3 and does not change with movement of the mini vfo dial. >> The mini cannot turn off the K3. The mini also comes up with "TERM" >> showing, which I don't remember from the last time I did this. (I can clear >> that by holding down the "CONFIG" button for 3 seconds.). >> >> I am pretty sure this has to do with the configuration of the control end >> RemoteRig. I have had problems in the past getting things to work from >> within my own home --- whether same LAN or a downstream LAN. Problem is, I >> don't want to get to Key West and discover it doesn't work. >> >> Can anyone suggest things for me to try? >> >> Tnx. 73, >> >> Brian W3BW >> >> >> >> Brian F. Wruble, C.F.A. >> From my iPad >> >> __ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:Elecraft@mailman.qth.net >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to k...@cox.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] K3/0 mini remoting problem
Hi guys: Last year, I had wonderful success controlling my "big station" (K3, KPA500,KAT500) on Maryland's Eastern Shore from our winter home in Key West. When I took the setup down last May, I carefully documented every step required to set things back up. Well, I have just gone through that process, and I can't get it to work --- at least not from within my own LAN and from another home LAN using a downstream router. I can turn on the K3 from the K3/0 mini, and I can hear the audio from the K3 but I cannot control the K3. Also, the freq. readout on the mini does not correspond to the K3 and does not change with movement of the mini vfo dial. The mini cannot turn off the K3. The mini also comes up with "TERM" showing, which I don't remember from the last time I did this. (I can clear that by holding down the "CONFIG" button for 3 seconds.). I am pretty sure this has to do with the configuration of the control end RemoteRig. I have had problems in the past getting things to work from within my own home --- whether same LAN or a downstream LAN. Problem is, I don't want to get to Key West and discover it doesn't work. Can anyone suggest things for me to try? Tnx. 73, Brian W3BW Brian F. Wruble, C.F.A. >From my iPad __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] FS: New K2 top with speaker
I somehow ended up with an as new K2 top cover with the speaker mounted in it, the tape has never been taken off the back holes, only the headphone jack has been installed. There are no marks or scratches on it. I'll sell it for $25 including priority mail shipping. PayPal or Postal Money order. I have a couple pictures if anyone is interested. Thanks Tim NZ8J __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] [K3] Using NaP3 in AFSK A mode
Interesting. I was beginning to think something like that, but I had to data to support that. I was running V4 for a while, but I had trouble with it playing nice with some other stuff I run. So, I dumped it and went back to V3.1. This configuration appears to be quite stable and plays nice with the rest of my software. I do us CW Skimmer vice datatext. I find the demod in Skimmer works a bit better than the demod on the KX3 and I found the display of calls over signals both neat and overwhelming on my monitor. So I guess I'll stay with what is working here; I guess it's a matter now of it it isn't broke, don't fix it. 73, Barry K3NDM On 10/3/2014 3:26 PM, Richard Ferch wrote: K3NDM wrote: You're right. I didn't understand what you were trying to do. I would never have seen what you are referring to as I wouldn't operate as you describe; it never occurred to me to do so. And, I use NaP3 V3.1 which may also have some subtle differences. If I get some time, I'll need to play and see what I can discover, but I'll need to do a little station reconfiguration first. I would like to know more. I believe the problem only exists in v4; as far as I know v3 is OK in this respect. 73, Rich VE3KI __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to k3...@comcast.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] Looking for LP-Pan(2) for K3
Perhaps someone upgraded to the P3 and would like to sell their LP-Pan? Looking for LP-Pan(2) preferably with a USB "sound card" interface for my new-to-me K3/10. -- http://www.qrz.com/db/k7on __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] Using K3 (or KX3) Macros for custom SPLIT functions
Yup, I well remember the day when Wayne announced the macro facility - and a very fine day that was! From that day, I have used a personalized SPLIT macro that sets the K3 up just right from a single button-press, and avoids all risk of appearing on the wrong frequency or seeing that SPLIT N/A message [1]. The problem is that a Smart Split (or Safe Split) macro is not assignable to the SPLIT button itself - instead, the SPLIT button become something to *avoid*. If there was an option to assign a special user-defined macro to the SPLIT button (using one of the many available examples) then the K3's SPLIT control would instantly become "best in its class". Moving on to Wayne's question about any missing points in his original example, the main point is that when the KRX3 is installed, "A>B, A>B" will also change many other parameters in the sub-rx. That may not be what every user needs. For example, the main RX (VFO A) generally needs to be optimized to listen for a weak DXpedition station, while the sub-rx is tuning a pileup of very strong signals using VFOB. There are a number of workarounds for that, but those macros will obviously be more complex than Wayne's original "day 1" example. [1] If anyone doesn't understand the urge to make the K3 do things quickly, automatically and with minimum risk... I am a DXer, a contester and one of those "race tuners" who spend a lot of time optimizing the performance and efficiency of our stations. We do this so that on "race days" - in contest or DX pileups - we won't have to waste any time or attention on unnecessary complications like pressing 6 different buttons in the correct sequence. Why? Because on "race days" there are far more important things to do. 73 from Ian GM3SEK >-Original Message- >From: Wayne Burdick [mailto:n...@elecraft.com] >Sent: 03 October 2014 17:49 >To: Joe Subich, W4TV >Cc: Ian White >Subject: Re: Using K3 (or KX3) Macros for custom SPLIT functions > >A>B twice sets mode B equal to mode A, so what am I missing? > >On Oct 3, 2014, at 9:43 AM, "Joe Subich, W4TV" wrote: > >> >> That doesn't address the issue of resetting the VFO B mode when >> pressing split (or when an external program commands split) if the >> modes are different e.g., SSB vs. DATA or CW vs. DATA or the VFOs >> are on different bands (VFO IND = YES). >> >> 73, >> >> ... Joe, W4TV >> >> >> On 2014-10-03 11:04 AM, Wayne Burdick wrote: >>> For those who may have missed this when I first described it-- >>> >>> * * * >>> >>> In a recent discussion about SPLIT, many proposals were made (too >>> many :) Others argued for no change. >>> >>> With this in mind, we've created a new "switch macro" feature. It >>> allows you to create your own variation on SPLIT -- or any other radio >>> function -- and execute it with a single switch press. In effect, >>> you'll be creating your own custom firmware for the K3 that automates >>> control sequences you use most. >>> >>> Example #1 (SPLIT+2): >>> >>>A>B >>>A>B >>>SPLIT >>>VFO B up 2 >>>RIT and XIT off >>> >>> Example #2 (WEAKSIG): >>> >>>Sub ON >>>Diversity mode >>>main/sub preamps on >>>200-Hz bandwidth >>>center passband >>> >>> Many other combinations are possible, limited only by the K3's remote- >>> control command set and the macro length limit (presently 56 bytes). >>> You'll be able to set VFO frequencies or RIT/XIT offsets, adjust gain >>> or filter controls, and virtually "tap" or "hold" nearly any control >>> on the radio. >>> >>> First, you enter a sequence of K3 control commands into one or more >>> macros using K3 Utility, which can store them in the K3's EEPROM. >>> Next, you assign the macros to any of the K3's 10 programmable >>> function switches (PF1, PF2, M1-M4 tap, or M1-M4 hold) using the new >>> MACRO menu entry. >>> >>> After that, activating the switch will perform the desired functions, >>> and the name of the macro will flash on VFO B as a reminder (e.g., >>> "SPLIT+2"). >>> >>> * * * >>> >>> Many K3 (and KX3) owners are using such macros to obtain exactly the >splits that they prefer. >>> >>> 73, >>> Wayne >>> N6KR >>> >>> >>> >>> __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] [K3] Using NaP3 in AFSK A mode
K3NDM wrote: You're right. I didn't understand what you were trying to do. I would never have seen what you are referring to as I wouldn't operate as you describe; it never occurred to me to do so. And, I use NaP3 V3.1 which may also have some subtle differences. If I get some time, I'll need to play and see what I can discover, but I'll need to do a little station reconfiguration first. I would like to know more. I believe the problem only exists in v4; as far as I know v3 is OK in this respect. 73, Rich VE3KI __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] modifying an aux cable for remote kpa operation
I am getting ready to set up my K3 & KPA for remote operation and will have to modify the KPA to K3 AUX cable for remote power on/off. How have others added the wire at pin 11 at the K3 to pin 8 at the KPA? Have you torn apart a standard VGA cable and changed the connections, or just made up a new custom cable? Howard AE3T __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] [K3] Using NaP3 in AFSK A mode
Rich, You're right. I didn't understand what you were trying to do. I would never have seen what you are referring to as I wouldn't operate as you describe; it never occurred to me to do so. And, I use NaP3 V3.1 which may also have some subtle differences. If I get some time, I'll need to play and see what I can discover, but I'll need to do a little station reconfiguration first. I would like to know more. 73, Barry K3NDM On 10/3/2014 2:23 PM, Richard Ferch wrote: K3NDM wrote: I guess I don't understand. That's right, you don't. RTTY in AFSK A is a different animal from PSK31 in DATA A. In AFSK A, the K3's dial displays the actual Mark frequency of the RTTY signal, not the BFO or suppressed carrier frequency as in DATA A. The expectation when clicking on a signal peak in the panadapter waterfall is exactly the same in AFSK A as in CW or FSK D; you would expect the rig to tune directly to the chosen frequency so that you can hear the signal at your chosen audio tone (set by the K3's PITCH setting). The mitigating factor for me personally is that I never click in the panadapter window in RTTY. I do all my tuning either with the radio's tuning knob or from the keyboard. My mouse stays in my receive text window - I left click to copy a call sign or exchange, and right-click to send the next message or log the contact. Since I installed NaP3 v4 I have never once clicked in the NaP3 window to tune in an RTTY signal, so I had never seen the problem Pete has reported. Once I tried it to see, the problem was immediately evident, but given the way I operate (which I believe is not unusual for RTTY), this bug in NaP3 does not affect me. 73, Rich VE3KI __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to k3...@comcast.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] [K3] Using NaP3 in AFSK A mode
K3NDM wrote: I guess I don't understand. That's right, you don't. RTTY in AFSK A is a different animal from PSK31 in DATA A. In AFSK A, the K3's dial displays the actual Mark frequency of the RTTY signal, not the BFO or suppressed carrier frequency as in DATA A. The expectation when clicking on a signal peak in the panadapter waterfall is exactly the same in AFSK A as in CW or FSK D; you would expect the rig to tune directly to the chosen frequency so that you can hear the signal at your chosen audio tone (set by the K3's PITCH setting). The mitigating factor for me personally is that I never click in the panadapter window in RTTY. I do all my tuning either with the radio's tuning knob or from the keyboard. My mouse stays in my receive text window - I left click to copy a call sign or exchange, and right-click to send the next message or log the contact. Since I installed NaP3 v4 I have never once clicked in the NaP3 window to tune in an RTTY signal, so I had never seen the problem Pete has reported. Once I tried it to see, the problem was immediately evident, but given the way I operate (which I believe is not unusual for RTTY), this bug in NaP3 does not affect me. 73, Rich VE3KI __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K144XV
Harlan, I was waiting to see if anyone from Elecraft would respond before replying. I use a different transverter for 2m but the situation is the same using the K3. RF output appears to drop quickly above 30-MHz when in the transverter mode though receive seems functional to 32-MHz enabling receiving the entire 4-MHz 2meter band. At 146.52 (K3=30.52 MHz) my 50w 2m transverter will only output 8w because drive drops to minimum. This is too low for me to operate in the FM repeater sub-band of 2m as all but one repeater are > 65 miles from me. Typically takes 25w to have a full-quieted signal thru these repeaters. From what I understood in communication with Elecraft this is a hardware limitation with no fix. That is the bad news. The good news is the KX3 suffers no power drop off over the whole 2meter band with the new 2M module. 3w drives my "little" RFS 2-23 amp to 30w which is adequate for my FM needs. If I need more power the 30w drives my RFC 2-317 to 150w, and if that is not enough 55w out of the RFC 2-317 will drive my 8877 to 1400w. Of course I do not use the 8877 with repeaters else they "melt down" :-) I usually run my K3 with the 8877 via the 50w transverter for ms/eme. 73, Ed - KL7UW --- Subject: [Elecraft] K144XV Message-ID: Content-Type: text/plain; charset=utf-8 Finally got around to installing this in my K3. There seems to be a large difference in output power vs input power when transitioning across the 146.000 threshold. ? Below 146, 0.5mW drive gives 6 out. Above 146 it only gives 2 out. And swr does not change. Ideas? Harlan NC3C 73, Ed - KL7UW http://www.kl7uw.com "Kits made by KL7UW" Dubus Mag business: dubus...@gmail.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] PX3 & Pigknob
Hi Nick, I am trying that now and it looks like the KX3 is not giving the PX3 the new frequency information. I'll pass this on to Wayne. Thanks for finding it! Kind regards, Paul -- View this message in context: http://elecraft.365791.n2.nabble.com/PX3-Pigknob-tp7593570p7593588.html Sent from the Elecraft mailing list archive at Nabble.com. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] PX3 & Pigknob
Hi Sid, Thank you for confirming that it works. I think the second part is a question for the Elecraft folks. Elecraft, If the KX3 is manipulated with the UP/DN commands via the serial port, is that reflected to the PX3 in the same way that a VFO knob turn on the KX3 does? 73, Nick N3WG On Fri, Oct 3, 2014 at 8:13 AM, Sid Leben wrote: > Hi Nick, > Tnx for quick reply. Yes, when connect the Pigknob to the PX3 Acc1PC port, > the knob works on the KX3 BFO, but the PX3 does not follow the knob > rotation. The kx3 BFO changes, but the px3 does not. > In this configuration, just the kx3 moves px3. > Sid > > Sent from my iPhone > > On Oct 2, 2014, at 8:35 PM, Nick Garner wrote: > > Hi Sid, > You can daisy chain them, similar to the KXPA100. Connect the knob to the > PX3 ACC1 PC port. Then the PX3 ACC1 XCVR port to the KX3 ACC1 port. > > 73, > Nick > N3WG > On Oct 2, 2014 6:09 PM, "Sid Leben" wrote: > >> Just finished the PX3 (kit) and it works like a charm. Now comes the >> question. >> I had a Pigknob attached to the “Acc 1” port. Now the Acc1 port is >> connected between the KX3 & PX3. >> >> Can I “Y” the connection into the PX3, (From KX3 & Pigknob), or some >> other way. If I had to chose, of course it’s the PX3 that wins… >> Sid >> KC2EE >> __ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:Elecraft@mailman.qth.net >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to nwgar...@gmail.com >> > __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] Using K3 (or KX3) Macros for custom SPLIT functions
That doesn't address the issue of resetting the VFO B mode when pressing split (or when an external program commands split) if the modes are different e.g., SSB vs. DATA or CW vs. DATA or the VFOs are on different bands (VFO IND = YES). 73, ... Joe, W4TV On 2014-10-03 11:04 AM, Wayne Burdick wrote: For those who may have missed this when I first described it-- * * * In a recent discussion about SPLIT, many proposals were made (too many :) Others argued for no change. With this in mind, we've created a new "switch macro" feature. It allows you to create your own variation on SPLIT -- or any other radio function -- and execute it with a single switch press. In effect, you'll be creating your own custom firmware for the K3 that automates control sequences you use most. Example #1 (SPLIT+2): A>B A>B SPLIT VFO B up 2 RIT and XIT off Example #2 (WEAKSIG): Sub ON Diversity mode main/sub preamps on 200-Hz bandwidth center passband Many other combinations are possible, limited only by the K3's remote- control command set and the macro length limit (presently 56 bytes). You'll be able to set VFO frequencies or RIT/XIT offsets, adjust gain or filter controls, and virtually "tap" or "hold" nearly any control on the radio. First, you enter a sequence of K3 control commands into one or more macros using K3 Utility, which can store them in the K3's EEPROM. Next, you assign the macros to any of the K3's 10 programmable function switches (PF1, PF2, M1-M4 tap, or M1-M4 hold) using the new MACRO menu entry. After that, activating the switch will perform the desired functions, and the name of the macro will flash on VFO B as a reminder (e.g., "SPLIT+2"). * * * Many K3 (and KX3) owners are using such macros to obtain exactly the splits that they prefer. 73, Wayne N6KR __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] [K3] Using NaP3 in AFSK A mode
Pete, I guess I don't understand. I use NaP3 and PSK31 without a problem. I may not understand how you are configured. I use either DM780 or FLDIGI and spot my signals on that and click in that window for a signal. I do not use NaP3 or the KX3 for demodulation or decoding of any of my digital signals. I think most of us are doing this. I, therefore, do not have a problem. Another issue I sense in this thread is possibly going to cause some real problems. The tuning issue is not simple. The offsets will be different for differing digital signals. One signal may want a 1200 Hz offset while another may want 1800 Hz, etc. A single Data A offset wouldn't work; it would need to b signal specific. I don't consider this a bug in either NaP3 or the KX3. It's just the nature of the various signals we play with. Here is a site the shows a configuration that will work: https://sdrzone.com/index.php?option=com_content&view=article&id=92:kx3-sdr-review&catid=20:mosaics&Itemid=572 73, Barry K3NDM On 10/3/2014 8:49 AM, Pete Smith N4ZR wrote: I just confirmed that offsets in the latest NaP3 setup menu have no effect when in AFSK A. As someone reported, either here or elsewhere, this is apparently a bug in NaP3, and since NaP3 is no longer supported I'll have to find another solution. Too bad - it was *so* close to perfect. 73, Pete N4ZR Check out the Reverse Beacon Network at http://reversebeacon.net, blog at reversebeacon.blogspot.com. For spots, please go to your favorite ARC V6 or VE7CC DX cluster node. On 10/2/2014 2:58 PM, Pete Smith N4ZR wrote: I would like to be able to use my K3 with NaP3 through an LP-PAN, but when I click on a signal, instead of going where clicked it sends the VFO to a frequency approximately 2 KHz lower. I presume it may be going to the suppressed carrier frequency instead of the Mark frequency. Both NaP3 and the K3 are in AFSK A mode. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to k3...@comcast.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] Using K3 (or KX3) Macros for custom SPLIT functions
If you use DXLab's Commander radio control module, you can create user-defined controls that don't have the length limitation of the K3. However, the program already has the capability to do splits of plus or minus 1, 2, 5, or 10 kHz with a mouse click. http://www.dxlabsuite.com/ and click on the Xcvr_Control tab. 73, Jim N7US -Original Message- For those who may have missed this when I first described it-- * * * In a recent discussion about SPLIT, many proposals were made (too many :) Others argued for no change. With this in mind, we've created a new "switch macro" feature. It allows you to create your own variation on SPLIT -- or any other radio function -- and execute it with a single switch press. In effect, you'll be creating your own custom firmware for the K3 that automates control sequences you use most. Example #1 (SPLIT+2): A>B A>B SPLIT VFO B up 2 RIT and XIT off Example #2 (WEAKSIG): Sub ON Diversity mode main/sub preamps on 200-Hz bandwidth center passband Many other combinations are possible, limited only by the K3's remote- control command set and the macro length limit (presently 56 bytes). You'll be able to set VFO frequencies or RIT/XIT offsets, adjust gain or filter controls, and virtually "tap" or "hold" nearly any control on the radio. First, you enter a sequence of K3 control commands into one or more macros using K3 Utility, which can store them in the K3's EEPROM. Next, you assign the macros to any of the K3's 10 programmable function switches (PF1, PF2, M1-M4 tap, or M1-M4 hold) using the new MACRO menu entry. After that, activating the switch will perform the desired functions, and the name of the macro will flash on VFO B as a reminder (e.g., "SPLIT+2"). * * * Many K3 (and KX3) owners are using such macros to obtain exactly the splits that they prefer. 73, Wayne N6KR __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] PX3 Text Decode is ready for testing
If you have a PX3 and KX3 and would like to try the PX3's new text display feature, please email me directly. Here's how it works: - The PX3's LABEL switch (hold of MENU) now has three settings: Normal (no labels or text), FN labels, or text decode. - When text decode is selected, two lines of scrolling text can be shown at the bottom of the screen. Text decode must be turned on at the KX3 and properly adjusted (applies to CW, FSK-D, PSK-D modes). - Decoded text is displayed in white. When you transmit, via either the KX3's stored message memories or a keyer paddle, your transmitted text is displayed in green. Total number of characters per line is either 42 (large font) or 65 (small font). We plan to add a USB keyboard interface later this year. Wayne N6KR __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] Need volunteers to try an even better version of KAT500 firmware (rev. 1.63) -- more accurate initial tunes
This is definitely high on my list, Bob. Thanks-- Wayne N6KR On Oct 3, 2014, at 8:30 AM, Bob wrote: > Hello, > > It's been a while since we've seen firmware updates for the K line -- is > there any chance that the RIT bug described below will be fixed this year? > > Thanks, > > Bob NW8L > > On Thu, 27 Feb 2014, Bob wrote: > >> Date: Thu, 27 Feb 2014 07:02:55 + (UTC) >> From: Bob >> To: Wayne Burdick >> Cc: Elecraft Reflector , >>"elecraft...@yahoogroups.com" >> Subject: Re: [Elecraft] Need volunteers to try an even better version of >>KAT500 firmware (rev. 1.63) -- more accurate initial tunes >> >> I updated to KAT500 1.63 and latest KPA500 and K3 firmware. I like the way >> the KAT500 follows the VFO on the K3 but I noticed something odd when the >> VFO is set near a boundary between two KAT500 stored band slice memories. >> >> When RIT is enabled, the KAT500 follows the frequency set by the RIT offset. >> That is, I hear the relays click after crossing the memory boundary using >> RIT and stopping on a new listening frequency. If I press CLR to reset the >> RIT offset, the relays click again as the KAT500 follows >> the VFO back to the original frequency and recalls the settings for that >> band slice. >> >> However, When XIT is enabled, the KAT500 does not follow the frequency set >> by the XIT offset. That is, I hear no relay clicking after crossing the >> boundary using XIT and stopping on a new transmit frequency in the adjacent >> band slice, for which different settings are normally recalled. >> >> Shouldn't it be the other way around, to optimize the match for the >> transmitter, not the receiver? >> >> It's late, maybe I'm missing something. >> >> Bob NW8L >> >> >> On Tue, 25 Feb 2014, Wayne Burdick wrote: >> >>> Date: Tue, 25 Feb 2014 09:31:16 -0800 >>> From: Wayne Burdick >>> To: Elecraft Reflector , >>>"elecraft...@yahoogroups.com" >>> Subject: [Elecraft] Need volunteers to try an even better version of KAT500 >>>firmware (rev. 1.63) -- more accurate initial tunes >>> Hi all, >>> We just posted a new beta-test release of KAT500 firmware (rev 1.63) that >>> does a better job on initial tunes than the previous release (1.58). We'd >>> really like to get this firmware into production quickly, but to do that >>> we'll need some testing help. >>> If you can spare a few minutes, please do the following: >>> 1) Save your current configuration so that you can return to it if >>> necessary >>> 2) Install KAT500 rev. 1.63 (follow instructions for beta releases) >>> 3) Erase memories on at least one band where the tuner has to work to find >>> solutions (that?s 160 through 40 meters for most of us) >>> 4) Do some full-search tunes. >>> The KAT500 should find very good tuning solutions (within its specified >>> impedance-matching limits, of course). Please send me your results. >>> Thanks-- >>> Wayne >>> N6KR >>> __ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:Elecraft@mailman.qth.net >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >> >> n...@sdf.org >> SDF Public Access UNIX System - http://sdf.org >> > > n...@sdf.org > SDF Public Access UNIX System - http://sdf.org __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] Need volunteers to try an even better version of KAT500 firmware (rev. 1.63) -- more accurate initial tunes
Hello, It's been a while since we've seen firmware updates for the K line -- is there any chance that the RIT bug described below will be fixed this year? Thanks, Bob NW8L On Thu, 27 Feb 2014, Bob wrote: Date: Thu, 27 Feb 2014 07:02:55 + (UTC) From: Bob To: Wayne Burdick Cc: Elecraft Reflector , "elecraft...@yahoogroups.com" Subject: Re: [Elecraft] Need volunteers to try an even better version of KAT500 firmware (rev. 1.63) -- more accurate initial tunes I updated to KAT500 1.63 and latest KPA500 and K3 firmware. I like the way the KAT500 follows the VFO on the K3 but I noticed something odd when the VFO is set near a boundary between two KAT500 stored band slice memories. When RIT is enabled, the KAT500 follows the frequency set by the RIT offset. That is, I hear the relays click after crossing the memory boundary using RIT and stopping on a new listening frequency. If I press CLR to reset the RIT offset, the relays click again as the KAT500 follows the VFO back to the original frequency and recalls the settings for that band slice. However, When XIT is enabled, the KAT500 does not follow the frequency set by the XIT offset. That is, I hear no relay clicking after crossing the boundary using XIT and stopping on a new transmit frequency in the adjacent band slice, for which different settings are normally recalled. Shouldn't it be the other way around, to optimize the match for the transmitter, not the receiver? It's late, maybe I'm missing something. Bob NW8L On Tue, 25 Feb 2014, Wayne Burdick wrote: Date: Tue, 25 Feb 2014 09:31:16 -0800 From: Wayne Burdick To: Elecraft Reflector , "elecraft...@yahoogroups.com" Subject: [Elecraft] Need volunteers to try an even better version of KAT500 firmware (rev. 1.63) -- more accurate initial tunes Hi all, We just posted a new beta-test release of KAT500 firmware (rev 1.63) that does a better job on initial tunes than the previous release (1.58). We'd really like to get this firmware into production quickly, but to do that we'll need some testing help. If you can spare a few minutes, please do the following: 1) Save your current configuration so that you can return to it if necessary 2) Install KAT500 rev. 1.63 (follow instructions for beta releases) 3) Erase memories on at least one band where the tuner has to work to find solutions (that?s 160 through 40 meters for most of us) 4) Do some full-search tunes. The KAT500 should find very good tuning solutions (within its specified impedance-matching limits, of course). Please send me your results. Thanks-- Wayne N6KR __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html n...@sdf.org SDF Public Access UNIX System - http://sdf.org n...@sdf.org SDF Public Access UNIX System - http://sdf.org __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] Using K3 (or KX3) Macros for custom SPLIT functions
For those who may have missed this when I first described it-- * * * In a recent discussion about SPLIT, many proposals were made (too many :) Others argued for no change. With this in mind, we've created a new "switch macro" feature. It allows you to create your own variation on SPLIT -- or any other radio function -- and execute it with a single switch press. In effect, you'll be creating your own custom firmware for the K3 that automates control sequences you use most. Example #1 (SPLIT+2): A>B A>B SPLIT VFO B up 2 RIT and XIT off Example #2 (WEAKSIG): Sub ON Diversity mode main/sub preamps on 200-Hz bandwidth center passband Many other combinations are possible, limited only by the K3's remote- control command set and the macro length limit (presently 56 bytes). You'll be able to set VFO frequencies or RIT/XIT offsets, adjust gain or filter controls, and virtually "tap" or "hold" nearly any control on the radio. First, you enter a sequence of K3 control commands into one or more macros using K3 Utility, which can store them in the K3's EEPROM. Next, you assign the macros to any of the K3's 10 programmable function switches (PF1, PF2, M1-M4 tap, or M1-M4 hold) using the new MACRO menu entry. After that, activating the switch will perform the desired functions, and the name of the macro will flash on VFO B as a reminder (e.g., "SPLIT+2"). * * * Many K3 (and KX3) owners are using such macros to obtain exactly the splits that they prefer. 73, Wayne N6KR __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] CR/LF, SP, or something better for RTTY
After the discussion here and on the RTTY reflector I checked with AA5AU and W0YK (aka P49X) as they are the go to guys for anything related to rtty contesting. Here's what they said: AA5AU CR/LF before and space after W0YK CR/LF before and space after (there are some building block macros that don't have the leading CR/LF as they need to seemlessly stack) VE3NEA, who is the author of RTTYSKimmer came up with another possibility with a dynamic way of freezing the data input window based on the mouse movement. He has a demo of this approach as well as its source code. This program simulates an RTTY client program that prints received characters and allows you to click on the words in the scrolling window. To see this in action, please download the freezer demo from (http://www.dxatlas.com/private/freezer.zip) extract Freezer.exe from the zip file, and play with it. While it doesn't have real callsigns you can quickly get the sense of how it operates. If this gets picked up by the various contest logging programs, it is maybe a way to make the discussion of cr/lf moot. Mark n2qt __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] [K3] Using NaP3 in AFSK A mode
I just confirmed that offsets in the latest NaP3 setup menu have no effect when in AFSK A. As someone reported, either here or elsewhere, this is apparently a bug in NaP3, and since NaP3 is no longer supported I'll have to find another solution. Too bad - it was *so* close to perfect. 73, Pete N4ZR Check out the Reverse Beacon Network at http://reversebeacon.net, blog at reversebeacon.blogspot.com. For spots, please go to your favorite ARC V6 or VE7CC DX cluster node. On 10/2/2014 2:58 PM, Pete Smith N4ZR wrote: I would like to be able to use my K3 with NaP3 through an LP-PAN, but when I click on a signal, instead of going where clicked it sends the VFO to a frequency approximately 2 KHz lower. I presume it may be going to the suppressed carrier frequency instead of the Mark frequency. Both NaP3 and the K3 are in AFSK A mode. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] Split N/A
Other transceiver manufacturers recognise the need for better protection against that hugely embarrassing mistake, which is why Smart Split has become an industry standard. With one notable exception. If you are going to do a "Smart Split" it needs *its own control.* I *DO NOT* want the Split button to change the frequency of VFO B. That can cause big issues when toggling in and out of split. Frankly, it is up to the operator to make sure where he transmits. There is altogether too much nanny mentality - it's time *PEOPLE* take personal responsibility for their actions rather than expect some one or some thing to fix their mistakes. 73, ... Joe, W4TV On 2014-10-03 4:11 AM, Ian White wrote: The reason for programming a default "smart split" is to move the TX VFO *away* from the frequency of the DX station. "How far to move?" is a secondary issue. No single value of frequency offset can be optimum for all modes, but anything is better than leaving it at zero! As a frequent user of Split for CW and RTTY, but only very rarely on SSB, I have found +3kHz a very acceptable compromise. Obviously it isn't perfect; but remember it is only a starting-point for tuning the pileup, so the exact value isn't hugely important. The main point is: the default Split offset should *never, never* be zero... and that is exactly where the K3 gets it wrong. When the user double-presses A>B to escape from the "SPLIT N/A" situation, it brings both VFOs onto the same frequency - leaving the user only one step away from accidentally calling on top of the DX station. Other transceiver manufacturers recognise the need for better protection against that hugely embarrassing mistake, which is why Smart Split has become an industry standard. With one notable exception. 73 from Ian GM3SEK -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Joe Subich, W4TV Sent: 02 October 2014 17:48 To: elecraft@mailman.qth.net Subject: Re: [Elecraft] Split N/A And I do not have any issue with the K3 not going split with RTTY on one freq and CW/SSB on the other. You have to admit operating RTTY and SSB/CW split is not exactly a common mode. However, it would be appropriate when initiating SPLIT from the A->B button that VFO B mode be forced to that of VFO A if VFO A is digital and the frequency of VFO B be forced to that of VFO A if VFO B is on a different band rather than SPLIT N/A. Unlike Ian, I would not want the VFO B *frequency* changed (e.g., Quick Split) as long as it was on the current band since I'm just as likely to have set it manually even if I have not set the mode and the "Smart Split" splits will invariably be different mode to mode (up 1 in CW, UP 2 in RTTY, UP 5 in SSB, etc.) and band to band. 73, ... Joe, W4TV On 2014-10-02 11:13 AM, Dick wrote: Frank, Like yourself, I do quite a bit of DX RTTY operation using split, and to tell you the truth, I just tried what you are talking about, and you are right! To me honest with you, I hadn't noticed it before because I have a nasty habit of "double pushing" the SPLIT button before holding it to engage split. This relative simple operation of double pushing the SPLIT button transfers everything from A to B; then pushing the SPLIT button works just fine. Am curious what "a whole lot of button pushing" means to you? Personally, I don't consider double pushing the same button I use to go split once, before holding the same button to be "extremely annoying". And I do not have any issue with the K3 not going split with RTTY on one freq and CW/SSB on the other. You have to admit operating RTTY and SSB/CW split is not exactly a common mode. SSB and CW split (though not common) does occur. In any case, I hope you do not "dump" your K3 because you find a double push, and then a "hold" to be that much of an annoyance. Dick, K8ZTT -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Frank Westphal Sent: Thursday, October 02, 2014 12:03 AM To: Elecraft@mailman.qth.net Subject: [Elecraft] Split N/A Every time I change modes from CW to RTTY or RTTY to CW I get the Split N/A error message. I do not get this message when changing modes from CW to SSB or SSB to CW. Since I am primarily a DXer who works split having to change from split operation before mode change and then change back to split operation requires a whole lot of button pushing. This is extremely annoying almost to he point of considering selling the K3. Elecraft told me this was for my own protection. I don't need a company to tell me this is for my own protection and not willing to make a product easy to operate. I hope someone out there is radio land has a firmware fix for this annoying issue. Otherwise I have enjoyed operating the K3 for the last year. Thanks in advance. Frank K6FW -Original Message- From: Elecraft [mailto:elecraft-boun...@mailm
Re: [Elecraft] Split N/A
Im not sure I would like this at all. sometimes I think that fool-proofing a rig is the wrong way to go as it take the ownership away from the operator to pay attention to what they are doing and panders to the shall I say the bad drivers. if I am working split I make it habbit to set offset where I make the most mistakes is when I set the offset and forget to enable split. or worse make the contact move on to a station working simplex and forget that I am in split. and its really not that embarrassing and most figure it out in a call or so. those that don't aren't paying enough attention. In most cases when someone makes this error its often the Up cops that are worse QRM than the original offender. Thats when I get frustrated. If this must be done however make the offset mode specific it automatically 1khz in cw and 3 in ssb. but I dont see a great need. David Moes President: Peterborough Amateur Radio Club. dm...@nexicom.net VE3DVY, VE3SD On 10/3/2014 05:24, Ken Chandler wrote: I'll agree with that Ian, set it a 3KHz, then let the user define his own split offset once split is activated. Ken.. G0ORH Sent from my iPad On 3 Oct 2014, at 09:11, Ian White wrote: The reason for programming a default "smart split" is to move the TX VFO *away* from the frequency of the DX station. "How far to move?" is a secondary issue. No single value of frequency offset can be optimum for all modes, but anything is better than leaving it at zero! As a frequent user of Split for CW and RTTY, but only very rarely on SSB, I have found +3kHz a very acceptable compromise. Obviously it isn't perfect; but remember it is only a starting-point for tuning the pileup, so the exact value isn't hugely important. The main point is: the default Split offset should *never, never* be zero... and that is exactly where the K3 gets it wrong. When the user double-presses A>B to escape from the "SPLIT N/A" situation, it brings both VFOs onto the same frequency - leaving the user only one step away from accidentally calling on top of the DX station. Other transceiver manufacturers recognise the need for better protection against that hugely embarrassing mistake, which is why Smart Split has become an industry standard. With one notable exception. 73 from Ian GM3SEK -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Joe Subich, W4TV Sent: 02 October 2014 17:48 To: elecraft@mailman.qth.net Subject: Re: [Elecraft] Split N/A And I do not have any issue with the K3 not going split with RTTY on one freq and CW/SSB on the other. You have to admit operating RTTY and SSB/CW split is not exactly a common mode. However, it would be appropriate when initiating SPLIT from the A->B button that VFO B mode be forced to that of VFO A if VFO A is digital and the frequency of VFO B be forced to that of VFO A if VFO B is on a different band rather than SPLIT N/A. Unlike Ian, I would not want the VFO B *frequency* changed (e.g., Quick Split) as long as it was on the current band since I'm just as likely to have set it manually even if I have not set the mode and the "Smart Split" splits will invariably be different mode to mode (up 1 in CW, UP 2 in RTTY, UP 5 in SSB, etc.) and band to band. 73, ... Joe, W4TV On 2014-10-02 11:13 AM, Dick wrote: Frank, Like yourself, I do quite a bit of DX RTTY operation using split, and to tell you the truth, I just tried what you are talking about, and you are right! To me honest with you, I hadn't noticed it before because I have a nasty habit of "double pushing" the SPLIT button before holding it to engage split. This relative simple operation of double pushing the SPLIT button transfers everything from A to B; then pushing the SPLIT button works just fine. Am curious what "a whole lot of button pushing" means to you? Personally, I don't consider double pushing the same button I use to go split once, before holding the same button to be "extremely annoying". And I do not have any issue with the K3 not going split with RTTY on one freq and CW/SSB on the other. You have to admit operating RTTY and SSB/CW split is not exactly a common mode. SSB and CW split (though not common) does occur. In any case, I hope you do not "dump" your K3 because you find a double push, and then a "hold" to be that much of an annoyance. Dick, K8ZTT -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Frank Westphal Sent: Thursday, October 02, 2014 12:03 AM To: Elecraft@mailman.qth.net Subject: [Elecraft] Split N/A Every time I change modes from CW to RTTY or RTTY to CW I get the Split N/A error message. I do not get this message when changing modes from CW to SSB or SSB to CW. Since I am primarily a DXer who works split having to change from split operation before mode change and then change back to split operation requires a whole lot of button pushing.
Re: [Elecraft] Split N/A
Pushing the button twice is so stressful??!! ...FYI there is a PSK application that will wait expectantly for some one to call you, answer the call automatically, and transfer the message you had for the calling station. I do not believe it completes the log entry however. :-)) Jim, W4ATK 61 years of amateur radio and still having fun! __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] Split N/A
I'll agree with that Ian, set it a 3KHz, then let the user define his own split offset once split is activated. Ken.. G0ORH Sent from my iPad > On 3 Oct 2014, at 09:11, Ian White wrote: > > The reason for programming a default "smart split" is to move the TX VFO > *away* from the frequency of the DX station. "How far to move?" is a > secondary issue. > > No single value of frequency offset can be optimum for all modes, but > anything is better than leaving it at zero! As a frequent user of Split > for CW and RTTY, but only very rarely on SSB, I have found +3kHz a very > acceptable compromise. Obviously it isn't perfect; but remember it is > only a starting-point for tuning the pileup, so the exact value isn't > hugely important. > > The main point is: the default Split offset should *never, never* be > zero... and that is exactly where the K3 gets it wrong. When the user > double-presses A>B to escape from the "SPLIT N/A" situation, it brings > both VFOs onto the same frequency - leaving the user only one step away > from accidentally calling on top of the DX station. > > Other transceiver manufacturers recognise the need for better protection > against that hugely embarrassing mistake, which is why Smart Split has > become an industry standard. With one notable exception. > > > 73 from Ian GM3SEK > > >> -Original Message- >> From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of > Joe >> Subich, W4TV >> Sent: 02 October 2014 17:48 >> To: elecraft@mailman.qth.net >> Subject: Re: [Elecraft] Split N/A >> >> >>> And I do not have any issue with the K3 not going split with RTTY on >>> one freq and CW/SSB on the other. You have to admit operating RTTY >>> and SSB/CW split is not exactly a common mode. >> >> However, it would be appropriate when initiating SPLIT from the A->B >> button that VFO B mode be forced to that of VFO A if VFO A is digital >> and the frequency of VFO B be forced to that of VFO A if VFO B is on >> a different band rather than SPLIT N/A. >> >> Unlike Ian, I would not want the VFO B *frequency* changed (e.g., Quick >> Split) as long as it was on the current band since I'm just as likely >> to have set it manually even if I have not set the mode and the "Smart >> Split" splits will invariably be different mode to mode (up 1 in CW, >> UP 2 in RTTY, UP 5 in SSB, etc.) and band to band. >> >> 73, >> >> ... Joe, W4TV >> >> >>> On 2014-10-02 11:13 AM, Dick wrote: >>> Frank, >>> >>> Like yourself, I do quite a bit of DX RTTY operation using split, and > to >>> tell you the truth, I just tried what you are talking about, and you > are >>> right! To me honest with you, I hadn't noticed it before because I > have a >>> nasty habit of "double pushing" the SPLIT button before holding it to >> engage >>> split. This relative simple operation of double pushing the SPLIT > button >>> transfers everything from A to B; then pushing the SPLIT button works > just >>> fine. >>> >>> Am curious what "a whole lot of button pushing" means to you? >> Personally, >>> I don't consider double pushing the same button I use to go split > once, >>> before holding the same button to be "extremely annoying". And I do > not >>> have any issue with the K3 not going split with RTTY on one freq and >> CW/SSB >>> on the other. You have to admit operating RTTY and SSB/CW split is > not >>> exactly a common mode. SSB and CW split (though not common) does >> occur. >>> >>> In any case, I hope you do not "dump" your K3 because you find a > double >>> push, and then a "hold" to be that much of an annoyance. >>> >>> Dick, K8ZTT >>> >>> -Original Message- >>> From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of >> Frank >>> Westphal >>> Sent: Thursday, October 02, 2014 12:03 AM >>> To: Elecraft@mailman.qth.net >>> Subject: [Elecraft] Split N/A >>> >>> Every time I change modes from CW to RTTY or RTTY to CW I get the > Split >> N/A >>> error message. I do not get this message when changing modes from >>> CW to SSB or SSB to CW. Since I am primarily a DXer who works split >>> having to change from split operation before mode change and then >> change >>> back to split operation requires a whole lot of button pushing. This > is >>> extremely annoying almost to he point of considering selling the K3. >>> Elecraft told me this was for my own protection. I don't need a > company >> to >>> tell me this is for my own protection and not willing to make a > product >> easy >>> to operate. I hope someone out there is radio land has a firmware > fix for >>> this annoying issue. Otherwise I have enjoyed operating the K3 for > the >> last >>> year. >>> >>> Thanks in advance. >>> >>> Frank >>> K6FW >>> >>> -Original Message- >>> From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of >> Frank >>> Westphal >>> Sent: Thursday, October 02, 2014 12:03 AM >>> To: Elecraft@mailman.qth.net >>> Subject: [Elecraft] Split N/A >>> >>> Every
Re: [Elecraft] Split N/A
The reason for programming a default "smart split" is to move the TX VFO *away* from the frequency of the DX station. "How far to move?" is a secondary issue. No single value of frequency offset can be optimum for all modes, but anything is better than leaving it at zero! As a frequent user of Split for CW and RTTY, but only very rarely on SSB, I have found +3kHz a very acceptable compromise. Obviously it isn't perfect; but remember it is only a starting-point for tuning the pileup, so the exact value isn't hugely important. The main point is: the default Split offset should *never, never* be zero... and that is exactly where the K3 gets it wrong. When the user double-presses A>B to escape from the "SPLIT N/A" situation, it brings both VFOs onto the same frequency - leaving the user only one step away from accidentally calling on top of the DX station. Other transceiver manufacturers recognise the need for better protection against that hugely embarrassing mistake, which is why Smart Split has become an industry standard. With one notable exception. 73 from Ian GM3SEK >-Original Message- >From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Joe >Subich, W4TV >Sent: 02 October 2014 17:48 >To: elecraft@mailman.qth.net >Subject: Re: [Elecraft] Split N/A > > >> And I do not have any issue with the K3 not going split with RTTY on >> one freq and CW/SSB on the other. You have to admit operating RTTY >> and SSB/CW split is not exactly a common mode. > >However, it would be appropriate when initiating SPLIT from the A->B >button that VFO B mode be forced to that of VFO A if VFO A is digital >and the frequency of VFO B be forced to that of VFO A if VFO B is on >a different band rather than SPLIT N/A. > >Unlike Ian, I would not want the VFO B *frequency* changed (e.g., Quick >Split) as long as it was on the current band since I'm just as likely >to have set it manually even if I have not set the mode and the "Smart >Split" splits will invariably be different mode to mode (up 1 in CW, >UP 2 in RTTY, UP 5 in SSB, etc.) and band to band. > >73, > >... Joe, W4TV > > >On 2014-10-02 11:13 AM, Dick wrote: >> Frank, >> >> Like yourself, I do quite a bit of DX RTTY operation using split, and to >> tell you the truth, I just tried what you are talking about, and you are >> right! To me honest with you, I hadn't noticed it before because I have a >> nasty habit of "double pushing" the SPLIT button before holding it to >engage >> split. This relative simple operation of double pushing the SPLIT button >> transfers everything from A to B; then pushing the SPLIT button works just >> fine. >> >> Am curious what "a whole lot of button pushing" means to you? >Personally, >> I don't consider double pushing the same button I use to go split once, >> before holding the same button to be "extremely annoying". And I do not >> have any issue with the K3 not going split with RTTY on one freq and >CW/SSB >> on the other. You have to admit operating RTTY and SSB/CW split is not >> exactly a common mode. SSB and CW split (though not common) does >occur. >> >> In any case, I hope you do not "dump" your K3 because you find a double >> push, and then a "hold" to be that much of an annoyance. >> >> Dick, K8ZTT >> >> -Original Message- >> From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of >Frank >> Westphal >> Sent: Thursday, October 02, 2014 12:03 AM >> To: Elecraft@mailman.qth.net >> Subject: [Elecraft] Split N/A >> >> Every time I change modes from CW to RTTY or RTTY to CW I get the Split >N/A >> error message. I do not get this message when changing modes from >> CW to SSB or SSB to CW. Since I am primarily a DXer who works split >> having to change from split operation before mode change and then >change >> back to split operation requires a whole lot of button pushing. This is >> extremely annoying almost to he point of considering selling the K3. >> Elecraft told me this was for my own protection. I don't need a company >to >> tell me this is for my own protection and not willing to make a product >easy >> to operate. I hope someone out there is radio land has a firmware fix for >> this annoying issue. Otherwise I have enjoyed operating the K3 for the >last >> year. >> >> Thanks in advance. >> >> Frank >> K6FW >> >> -Original Message- >> From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of >Frank >> Westphal >> Sent: Thursday, October 02, 2014 12:03 AM >> To: Elecraft@mailman.qth.net >> Subject: [Elecraft] Split N/A >> >> Every time I change modes from CW to RTTY or RTTY to CW I get the Split >N/A >> error message. I do not get this message when changing modes from >> CW to SSB or SSB to CW. Since I am primarily a DXer who works split >> having to change from split operation before mode change and then >change >> back to split operation requires a whole lot of button pushing. This is >> extremely annoying almost to he point of consi
