[Elecraft] K3s port isolation??
So I have a weird situation going on with my K3s. First a bit of background: I have been experiencing extreme powerline noise for years (this isn't about that), so I've been looking for ways of mitigating it on my end to at least get useful signals of some kind on 80 and 160. I have a K9AY loop RX antenna and a full-size 80m Inverted Vee at 65'. Tonight, I was switching between my Inverted Vee and the K9AY loop with an external noise-canceller (WIMO "QRM Eliminator") in line. It's somewhat effective with about a 30dB improvement on the K9AY. But then something quite unexpected happened. I wanted to see how low my noise floor was with this new device inline so I figured I'd switch to an empty antenna port (ANT-2 on the K3s). As soon as I pressed the button my noise floor dropped to from about -130 to -140 on my P3, lower than it's been in years. But I was still hearing FT8 and the signal-to-noise improved considerably. This is.surprising to say the least. How am I still able to copy weak FT8 signals (and CW) with absolutely nothing connected to the ANT-2 port? I'm talking about copying stations in A7, V3, CT3, and west-coast US, not strong locals. I don't think I've ever had lowband S/N that good before to be honest. What is the port isolation supposed to be like on the K3s and is what I'm seeing normal? Just to be clear, I disconnected my AUX antenna that I use occasionally for diversity RX, and my K9AY and it was still the same. Only my Inverted Vee was connected to the K3s. When I disconnected it everything dropped to nothing. Is what I'm seeing expected behaviour? And this leads to a big question. With ANT-2 selected for RX, (remember, there's nothing connected to the ANT-2 SO-239 on the radio) is it possible to select a different TX Antenna? I'd be pleased as punch to receive in this configuration but it's not practical to manually switch from ANT-2 on receive back to ANT-1 for transmit. Regards, Peter Dougherty, W2IRT __ 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] K3s USB audio connections no longer visible in WSJT after 22H2 Win11 update
Earlier tonight I got the big Windows 11 fall update (known as 22H2). It confirmed my worst fears in that it broke WSJT functionality, but unlike previous times, it wasn't just a matter of going in and re-selecting the appropriate sound device. With this update, in WSJT, the only sound options to choose are the default Windows system audio options (Microphone (USB Audio CODEC) and (Line IN (Realtek Audio). In the Windows Sound control panel the K3s options are there (they were renamed back to default values, but as I do every time one of these stupid updates comes through, I rename them so I know for sure which entries are which in this list), but they are *not* there in WSJT. Any ideas how to get these back? I'm the furthest thing from a Windows expert, and it seems like every new version causes more damage that average users are incapable of fixing on their own. I've got a sneaking suspicion that this is going to become a major issue for a lot of users as more people get the 22H2 update, unless it's just a simple fix. Regards, Peter Dougherty, W2IRT __ 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] COM port problems
Thanks for this. I will try to see what the COM devices are supposedly
connected to when it's in failure mode but it's all very cryptic.
I have already deleted old phantom devices during the first phase of
troubleshooting, as well as deleted all unnecessary software from the system.
The problem of *ALL* COM ports being shown as busy upon reboot persists.
- pjd
-Original Message-
From: elecraft-boun...@mailman.qth.net On
Behalf Of Dave B via Elecraft
Sent: Sunday, July 3, 2022 7:00 AM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] COM port problems
FYI...
Windows users, can use these utilities to find out what is/was connected to
their PC's by USB etc...
USBview: A Microsoft (was System Internals who MS bought) tool.
The easiest way to find it is here:- https://ftdichip.com/utilities/ "Microsoft
USBView - USB Connection Viewer"
There is a link to download a zipfile that contains it:-
https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
That contains a single stand-alone exe file that is the utility. Put it in a
folder of it's own, and create a shortcut to it for your desktop.
(Also a link to a Linux version, that does work, but needs compiling from
source, and running using sudo as it needs elevated rights to read the running
configuration files to get the information to display.)
Another similar tool is USBDview
https://www.nirsoft.net/utils/usb_devices_view.html
That shows a much more detailed list of what Windows knows about, that is, any
USB device that was ever connected since windows was initially installed,
regardless of if it was ever used!
You can also delete instances of old / defunct devices easily with this very
useful tool.
(Some AV tools say it's suspect or malicious. Use VirusTotal.com to verify if
it (or anything else) is bad, on a file by file, or webpage basis. )
Note that if for whatever reason Windows (or Linux) re-enumerates things, the
linkage between a physical device and it's COM port number can (and often
does!) change. Seemingly at the will of some minor deity somewhere... That
of course, will break any software that expects some specific device to be at a
specific COM port.
Windows has the means to "Fix" that. (Known to work up to Win10, that I have
personally tested it on.) Find those details here:-
https://sourceforge.net/p/fldigi/wiki/windows_com_howto/
I wrote much of that after hours of "fun" some years ago... As above, it
works well with Win-10.
For Linux users, look up and explore the world of "udev rules". But...
They are only really easy to setup, if a USB device has a unique "something" in
it's USB descriptor, that the OS uses to identify it. Such as a Serial Number.
FTDI devices have unique sn's, but Prolific, SiLabs and others sadly do not.
So, it gets funky if you have several of the same type of device that all "look
the same" to the OS.
(Newer genuine FTDI devices also have the ability to have that serial number
(and some other settings) re-programmed! Fakes seem to take the
reprogramming, but the new data does not "stick". Don't ask how I found that
out!)
However, you can use the "connection path" between the OS and the Device, as a
deciding factor, but then you are forced into hooking everything up "EXACTLY"
the same each time. (Hub's and all...) But it does work.
Using them, you create "symbolic links" to the actual port used, so for example
my VHF radio appears as /dev/ttyFT736 Regardless of which hole I connect it's
associated FTDI serial adapter to on the PC (or via any
hubs!) Or what /dev/ttyUSB* the OS re-assigns it to if things are
re-enumerated for whatever reason.)
For example, this is the rule for my ancient FT-736
#FT-736r
SUBSYSTEM=="tty", ATTRS{serial}=="A50285BI", SYMLINK+="ttyFT736"
Flrig and most other software both accept symlinks and work well.
(For the odd software title that insists on using the full /dev/ttyUSBx for
example, they often store their settings in a file that can often be edited
with a text editor, where you can in effect force-feed it the symlink. The
fun part is finding where that is stored!)
The exact details of how to use udev rules are way to much for this list, but
as usual, there are many websites that can furnish such info, plus some
examples. Has to be said though, different "flavors" of Linux, often store
such rules in subtly different places to others.
I have zero experience of Apple Mac's. But they use a custom version of BSD as
their OS, that is more like Unix than Linux. So it is likely some if not all
of the above could work on them too. If Apple let you dig that deep and
meddle...
Hope some of the above helps, and or gives people some ideas how to tame things.
73.
Dave G0WBX(G8KBV)
--
Created on and sent from a Unix like PC running and using free and open source
software:
__
Elecraft mailing list
Home:
Re: [Elecraft] Com Port Problems
Yes, that is likely my next step, an in-place reinstall. I do not have the time to fully reconfigure the system so I can't do a bare metal install job. It's my work computer as well as my ham computer, and work MUST take precedence on it. - pjd -Original Message- From: Lyn Norstad Sent: Saturday, July 2, 2022 3:01 PM To: 'Peter Dougherty (W2IRT)' ; 'Wilson Lamb' ; 'elecraft' Subject: RE: [Elecraft] Com Port Problems Peter - If you're sure that the problem is not what we addressed, then I suggest you reinstall Windows 11. Presumably you're using the " Pro " edition. If not, switch to that one. The latest build is # 22000.778 released on 06/23/2022 (last week). Instructions here: https://support.microsoft.com/en-us/topic/june-23-2022-kb5014668-os-build-22000-778-preview-2b5f1da6-d602-48b4-b443-96b460e3c38d 73 Lyn, W0LEN -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Peter Dougherty (W2IRT) Sent: Friday, July 01, 2022 5:22 PM To: 'Wilson Lamb'; 'elecraft' Subject: Re: [Elecraft] Com Port Problems The problem isn't the Elecraft radio, or the COM ports, it's a defect of some nature within Windows 11 that has suddenly manifested itself. I've tried all the usual troubleshooting problems and no-go, and even a Microsoft 2nd Level guy spent three hours with me on the phone and did it all again and still couldn’t' find it. Making things work "once" isnt' too difficult. Making everything work 100% reliably *repeatedly*, as it has been for years, is the problem. I really hate the fact that it took SO long for ham radio manufacturers to move away from RS-232 to pure USB, and only recently to TCP/IP, which is the correct way of doing things in my opinion. - pjd -Original Message- From: elecraft-boun...@mailman.qth.net On Behalf Of Wilson Lamb via Elecraft Sent: Friday, July 1, 2022 2:18 PM To: elecraft Subject: [Elecraft] Com Port Problems Please read my rant about Ham Qualifications and Technology. We are at the mercy of MANY programmers and "software engineers." The operating system people have no resistance to making things steadily more obscure and complicated. They don't know or care what the programmers of our many programs are doing and have little incentive to find out. The programmers typically have only a nodding acquaintance with what the Operating System really does and don't have time/ability to find out. WE are way out on a thin limb that gets more and more likely to break or sag down to the ground. All the people mentioned above are whittling away at the limb, each contributing to its weakness/impending breakage, and none have much incentive to help US. I really hope you find it and I guarantee, if you do, there will be a gotcha that someone will tell you should have seen and that will make you feel inadequate! In this area, we are all inadequate! I know this doesn't help. It's meant as sympathy. I have been building and using computers since the 50s, when I helped build one that used relays and I still have NO interest in software except to say what it should do, at which I've been pretty successful. Good luck and remember, there are knobs on the radio and they will probably work for you, since the software in the radio has likely had a few years to get sorted out and the worst bugs found. WL __ 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 li...@w2irt.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 l...@lnainc.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] Heil Pro 7 headset with KX3 - RF feedback?
I have never owned a Heil that didn't give me problems at some point in its life. It's always something. I gave up a long time ago and bought an Arlan Communications radiosport headset. It's more expensive but it's absolutely amazing. No clamping on my head, no mechanical construction problems, and dare I say it, mechanically overbuilt for severe duty. I would trust their products for communicating on a desert island or the southern ocean. It Just Works. - pjd -Original Message- From: elecraft-boun...@mailman.qth.net On Behalf Of Drew Arnett Sent: Saturday, July 2, 2022 2:08 PM To: elecraft@mailman.qth.net Subject: Re: [Elecraft] Heil Pro 7 headset with KX3 - RF feedback? Ignored this for quite a while, but came back to take a look this morning. Sharing in case it helps someone else out in the future. I think the jack on the headset itself has an intermittent and/or faulty connection. That's why trying the straight cable (which I never use) as Heil suggested didn't help me narrow it down before. (I always used the curly cable and left the straight one in the box.) Symptoms I see today: KX3 on battery. RF power level set to 0 watts (so no RF feedback of course). Mon set to 4. Gear: Pro 7 headset. Heil Y cable (for mic/foot switch) but using the little hand/button switch Heil includes, a cheap pair of Walkman style earphones, and a homebrew electret handmic (that also requires 5V bias). No difference between curly cord that I normally use and the straight cable that I never took out of the box. In all cases, I use the Y cable. Notice the combinations that work and don't work: * walkman head phones & homebrew handmic - works OK * walkman head phones & pro 7 mic - works OK * pro 7 headphones & homebrew handmic - works OK * pro 7 headphones & pro 7 mic - ***PROBLEM*** I suspect the feedback path is due to wiring fault causing the headphone audio return to share path with microphone return causing IxR coupling. (I hate the term ground loop, but there you go.) Wiggle testing. Nothing at the jack/plug interfaces on the radio (mic, headphone). Nothing on the jack/plug interfaces on the Y cable. Ah, the jack/plug on the headset definitely has some sort of mechanical intermittent at the least. And it does for both the curly cable and the straight cable. So, it's the headset and not the cable. :-( So, off to Heil for repair. (Looks like snap plastic/spudger tool work, which I'm not really interested in doing.) Or to perhaps shop for something more reliable? Best regards, Drew n7da On Sat, Jul 3, 2021 at 9:05 PM Drew Arnett wrote: > > No luck sorting this out in the field during FD, especially with a > workaround available. (Alternative mic.) I'd like to resolve it if > possible before replacing the Pro 7, the KX3, or both. :-O So, now > that I'm unpacked at home, I'll try a simple setup for debugging. > > Trouble shooting setup now: KX3 (with new, charged internal NiMH), > Pro 7 with Y cable and that little clip on PTT switch they include, 3 > FT coax to (shielded) dummy load. Electret mic element. MIC BIAS on, > CMP 0, PWR 5, 14 MHz, SSB. > > With MON 0, no RF output indicated while transmitting and speaking or > whistling for MIC GAIN 0 to 80. > > With MON 3 (a level I like for CW sidetone) and PTT on, doesn't matter > if I'm speaking/whistling or not. The RF output indicates nothing > until about MIC GAIN 70 when it abruptly comes up with a harsh sound. > Other electret microphone sounds fine at MIC GAIN 60. > > This is probably something simple. I just haven't found it, yet. > > Thanks, > > Drew > n7da > > On Thu, Jun 17, 2021 at 3:36 AM Drew Arnett wrote: > > > > Shield of mic jack goes to bare metal Elecraft thoughtfully left on > > the chassis metal. 10 nF shunt to ground. (Need to see where that > > is, but hopefully SMT and with very small loop area.) Sheet 9: > > https://ftp.elecraft.com/KX3/Manuals%20Downloads/KX3SchematicDiagram > > Dec2012.pdf > > > > Heil suggests on their tips page generous ferrite choking of all 3 > > leads of their Y adapter cable: > > https://heilhamradio.com/support/tips/ > > > > Drew > > n7da > > > > On Thu, Jun 17, 2021 at 3:23 AM Drew Arnett wrote: > > > > > > Hi, > > > > > > In the KX3 for Field Day department, we plan to use it for the > > > GOTA station for phone on HF. (Yes, will have antennas not on top > > > of each other and bandpass filters on ALL radios.) Would be great > > > to setup with a headset and foot switch. > > > > > > Last weekend, I used my KX3 barefoot on 6 and with a > > > transverters-store.com transverter (also barefoot) for 2. 6m > > > antenna was 2 elements about 15 ft above the ground and 2m antenna > > > 6 elements at 10 feet above the ground. > > > > > > I worked a couple of contacts on 2m phone with the headset. > > > Later, when I tried to use the headset for phone on 6, seemed like > > > I was having a feedback problem. Cabling was the stock cabling > > > that comes
Re: [Elecraft] Com Port Problems
The problem isn't the Elecraft radio, or the COM ports, it's a defect of some nature within Windows 11 that has suddenly manifested itself. I've tried all the usual troubleshooting problems and no-go, and even a Microsoft 2nd Level guy spent three hours with me on the phone and did it all again and still couldn’t' find it. Making things work "once" isnt' too difficult. Making everything work 100% reliably *repeatedly*, as it has been for years, is the problem. I really hate the fact that it took SO long for ham radio manufacturers to move away from RS-232 to pure USB, and only recently to TCP/IP, which is the correct way of doing things in my opinion. - pjd -Original Message- From: elecraft-boun...@mailman.qth.net On Behalf Of Wilson Lamb via Elecraft Sent: Friday, July 1, 2022 2:18 PM To: elecraft Subject: [Elecraft] Com Port Problems Please read my rant about Ham Qualifications and Technology. We are at the mercy of MANY programmers and "software engineers." The operating system people have no resistance to making things steadily more obscure and complicated. They don't know or care what the programmers of our many programs are doing and have little incentive to find out. The programmers typically have only a nodding acquaintance with what the Operating System really does and don't have time/ability to find out. WE are way out on a thin limb that gets more and more likely to break or sag down to the ground. All the people mentioned above are whittling away at the limb, each contributing to its weakness/impending breakage, and none have much incentive to help US. I really hope you find it and I guarantee, if you do, there will be a gotcha that someone will tell you should have seen and that will make you feel inadequate! In this area, we are all inadequate! I know this doesn't help. It's meant as sympathy. I have been building and using computers since the 50s, when I helped build one that used relays and I still have NO interest in software except to say what it should do, at which I've been pretty successful. Good luck and remember, there are knobs on the radio and they will probably work for you, since the software in the radio has likely had a few years to get sorted out and the worst bugs found. WL __ 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 li...@w2irt.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] COM port problems
The issue is far deeper than this. None of the COM ports work normally after starting the system. Occasionally the radio connects to the software normally, other times it doesn't. If I have it working with N1MM, close down N1MM and try to start Commander (DX Labs) it won't work initially, but if I try it 3 or 4 times in a row it will connect normally. Ditto with my two rotors. Those are the only serial ports in my system. The K3s, my 6m rotor (Rotor-EZ board in the controller box) and a Green Heron RT-20 (serial-to-USB, not pure USB like the newer RT-21). For whatever reason, there is *something* holding all the installed/configured COM ports open and unavailable. I cannot find that "something." - pjd -Original Message- From: elecraft-boun...@mailman.qth.net On Behalf Of Geoffrey Feldman Sent: Friday, July 1, 2022 1:23 PM To: elecraft@mailman.qth.net Subject: Re: [Elecraft] COM port problems These is nothing unique about the Elecraft serial cable except possibly the radio side connector. Basically it's a USB to RS232 Ground/transmit/Receive cable. Anyone who understands USB com ports can help you. They don't need to know radio. They should understand what I wrote here. For USB COM port problems (with anything, including these). Run DEVMGR (I do this by entering that in the search bar) In Devmgr "View" menu , click / check "Show Hidden Devices" Look in the list for "Ports(COM & LPT) Expand that to the sub list You will see a list of ports there in the sub list. Some are grayed out, those are not connected. Plug in your Elecraft serial cable. Is there a change? You should see a grayed out one now dark (enabled) (as COM 1 is) That is the number of the Elecraft port. OR ... a new one just appears. This sometimes happens. That is the new number of the Elecraft port. (This is a likely outcome). Make a note of anything in devmgr list, this may help Elecraft help you but I expect you will have figured it out with the above steps. If this does not work, try other USB ports on your computer with the above procedure. If this does not work, try the Elecraft cable on a friends computer (the driver for Elecraft is pretty standard you don't need the radio to check the cable). If this does not work, you need a Elecraft serial cable. You can also look in the cable and make one. There are USB to RS232 cables you can change the connector to match the cable description in the manual. Others available may have the same connector but TX and RX are reversed. Some are already the same as elecraft. W1GCF Geoff __ 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 li...@w2irt.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] COM port problems
Reassigning port numbers did not solve the problem, and I did try that as one of the first steps in troubleshooting. With one day’s work under my belt here’s where the situation lies as of tonight. 1. After a cold reboot, the first attempt to launch either CI-V Commander (DX Labs rig interface) or N1MM Logger + may or may not capture the COM5 port used for CAT control (which was briefly changed to COM8 then changed back after finding no change). 2. Launching either the old version of N1MM Rotor (v12.11) or the current .NET version, there’s about a very slim chance that it will work, but the usual result is that on attempting to start the rotor software it indicates both rotor com ports (COM1 and COM3) are already in use, and any attempt to invoke a direction command generates an error message (8018, IIRC) stating the function can only work if a port is open. 3. Using the DX Lab “DX View” software, which interfaces with the rotor control software, if I repeatedly enable/disable the rotor control tick box, it **MAY** come back, and will keep working until the program is closed. 4. If CAT control is in fact established, whether through N1MM or Commander, it will remain active until the program is closed. Once closed, either reopening it or opening the other control software will result in either program not being able to see the radio (i.e. the port remains locked out). Note than if it is Commander that is closed and N1MM does not see the radio at first, if I hit the “Reset Radio” bar in the bandmap several times it does seem to come back and start working again. 5. Every other function of the PC is working the same as it always has, and once a COM port feature is working it remains working flawlessly. 6. Troubleshooting has involved using Process Explorer to see if any devices are holding a port open when the problem is occurring, and none appear to be doing so. Phantom COM ports were removed, all USB devices were set to fix the issue of stopping the device for power saving (I hoped that one would work, but it didn’t), and all USB Serial drivers were deleted and allowed to reinstall themselves upon reboot. The results were identical. In short, it appears to me that there is SOMETHING within Windows 11 that has changed somehow, and is locking serial ports on its own, with no easy way to release them. - pjd From: Lyn Norstad Sent: Thursday, June 30, 2022 8:46 PM To: 'Julia Tuttle' Cc: 'Peter Dougherty (W2IRT)' ; 'George Thornton' ; 'Elecraft' Subject: RE: [Elecraft] COM port problems Julie – I can look for it … but I don’t believe it was in an official MSFT document. Nevertheless, it has been going on for a couple years. It seems to affect almost every ham using Win 10 sooner or later. My understanding is that one or more specific Windows 10 Pro 64 updates reassigned COM ports in order to prevent a potential hacker from accessing the system. It may have been related to the presence of specific software installed on the system. In any event, the fix I mentioned does indeed work and ends the problem. George may have other issues, since he’s already tried this 73 Lyn, W0LEN From: Julia Tuttle [mailto:ju...@juliatuttle.net] Sent: Thursday, June 30, 2022 2:47 PM To: l...@lnainc.com <mailto:l...@lnainc.com> Cc: Peter Dougherty (W2IRT); George Thornton; Elecraft Subject: Re: [Elecraft] COM port problems Lyn, Can you share your source that COM port reassignment is a deliberate security feature? I'm curious what vulnerability it's mitigating. Thanks, Julie On Thu, Jun 30, 2022 at 3:25 PM Lyn Norstad mailto:l...@lnainc.com> > wrote: Are you running Windows 10 by any chance? As a security measure, Win 10 automatic updates often reassign COM port numbers. If you know how to do it, you can rename and reassign port numbers. If you give them a number of 20 or higher, Win 10 update will leave them alone. Hint: Control Panel>Device Manager>Ports>(Elecraft connection port)>General>Advanced>COM Port Number Be sure to make the corresponding port number change in the software. 73 Lyn, W0LEN -Original Message- From: elecraft-boun...@mailman.qth.net <mailto:elecraft-boun...@mailman.qth.net> [mailto:elecraft-boun...@mailman.qth.net <mailto:elecraft-boun...@mailman.qth.net> ] On Behalf Of Peter Dougherty (W2IRT) Sent: Thursday, June 30, 2022 12:28 AM To: 'George Thornton'; Elecraft@mailman.qth.net <mailto:Elecraft@mailman.qth.net> Subject: Re: [Elecraft] COM port problems It's possible (and I'm guessing somehow likely), but darned if I know what to even look for. These are things that were set when the computer was built from scratch last year, they have worked 100% reliably over thousands of QSOs in both Commander and N1MM+ ever since, and absolutely nothing was changed in terms of configuration or even a Windows Update
Re: [Elecraft] COM port problems
It's possible (and I'm guessing somehow likely), but darned if I know what to even look for. These are things that were set when the computer was built from scratch last year, they have worked 100% reliably over thousands of QSOs in both Commander and N1MM+ ever since, and absolutely nothing was changed in terms of configuration or even a Windows Update in at least two weeks. I just needed to restart the computer after moving it from a wall outlet to a UPS, and it started going crazy from that point on. Whatever the issue is, it seems to affect ALL the COM ports in the system the same; neither Commander nor N1MM can open the radio port, or either of the two rotor ports. I did somehow manage to get Commander working (don't aske me how, it just started), but the rotors are still no-go (and not critical at the moment). - pjd From: George Thornton Sent: Wednesday, June 29, 2022 10:23 PM To: Peter Dougherty (W2IRT) ; Elecraft@mailman.qth.net Subject: RE: [Elecraft] COM port problems It is possible the parameters set in the computer after reboot don't match those set in the program. Check the port and baud settings. Generally xom port settings need to match for communication to occur. Sent from my Galaxy Original message From: "Peter Dougherty (W2IRT)" mailto:li...@w2irt.net> > Date: 6/29/22 6:59 PM (GMT-08:00) To: Elecraft@mailman.qth.net <mailto:Elecraft@mailman.qth.net> Subject: [Elecraft] COM port problems OK, got a massive problem that just cropped up this evening that is far beyond my understanding that has completely killed my ability to use my K3 with my computer. After restarting the PC, suddenly I cannot communicate with the radio using DX Lab Suite or N1MM+ on the assigned COM port. I have downloaded the K3 Utility software and it is able to connect to the radio on COM5, its usual port, and invoke macros via the Utility. So I know there's proper communication between the radio and the PC. But once I close down the K3 Utility program I get the first major problem. The radio goes into transmit for 10 seconds, releases for about 4 or 5 second, and goes back in to transmit. Only powering the radio off and back on again stops this behavior. The main issue is that no CAT control software seems to be able to connect to the radio at all. The radio is on COM5, and has been for at least the last 4 or 5 years, and until today it has just worked, even after building a new computer last November. I just rebooted today and everything went to heck. The kicker is that's it's not a K3 hardware problem, and since it works with neither N1MM nor DX Lab software any more it's apparently not those programs either, and quite frankly I just don't know where to look next. Compounding the issue, and likely related to it, the N1MM Rotor control cannot find either COM port assigned to the rotors (COM1 and COM3). I have tried removing the ports and re-adding them in Device Manager but the problem still persists. I am absolutely prepared to pay a certified systems professional to diagnose and fix this, but with ultra-specialized radio gear I doubt they'd be able to figure it out either. Any suggestions? I'm basically QRT until I can fix this. ---- Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT <http://www.facebook.com/W2IRT> __ 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 gthorn...@thorntonmostullaw.com <mailto:gthorn...@thorntonmostullaw.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
[Elecraft] COM port problems
OK, got a massive problem that just cropped up this evening that is far beyond my understanding that has completely killed my ability to use my K3 with my computer. After restarting the PC, suddenly I cannot communicate with the radio using DX Lab Suite or N1MM+ on the assigned COM port. I have downloaded the K3 Utility software and it is able to connect to the radio on COM5, its usual port, and invoke macros via the Utility. So I know there's proper communication between the radio and the PC. But once I close down the K3 Utility program I get the first major problem. The radio goes into transmit for 10 seconds, releases for about 4 or 5 second, and goes back in to transmit. Only powering the radio off and back on again stops this behavior. The main issue is that no CAT control software seems to be able to connect to the radio at all. The radio is on COM5, and has been for at least the last 4 or 5 years, and until today it has just worked, even after building a new computer last November. I just rebooted today and everything went to heck. The kicker is that's it's not a K3 hardware problem, and since it works with neither N1MM nor DX Lab software any more it's apparently not those programs either, and quite frankly I just don't know where to look next. Compounding the issue, and likely related to it, the N1MM Rotor control cannot find either COM port assigned to the rotors (COM1 and COM3). I have tried removing the ports and re-adding them in Device Manager but the problem still persists. I am absolutely prepared to pay a certified systems professional to diagnose and fix this, but with ultra-specialized radio gear I doubt they'd be able to figure it out either. Any suggestions? I'm basically QRT until I can fix this. Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT __ 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 Suddenly Putting Out Only 25 watts at 100 watts indicated
That's how I discovered it. Normally I can work anybody I hear, but at the start of WW I was working one in ten that I called in S, and after one long, difficult exchange I was told I sounded terrible. The day before I'd been working a Dxpedition on CW and FT8 and no problem, until I started calling on 15m FT8. The op was begging, I was running over 1300W, signals were strong and I couldn't make a Q for love or money with 'em. I chalked it up to one-way propagation but I suspect that was about the time the failure occurred. I was feeding the KPA-1500 with whatever power it needed to get about 1300-1400W out. Likewise, for CQWW, I was doing the same. Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT -Original Message- From: j...@kk9a.com [mailto:j...@kk9a.com] Sent: Thursday, December 13, 2018 2:04 PM To: elecraft@mailman.qth.net Cc: li...@w2irt.net Subject: re: [Elecraft] K3 Suddenly Putting Out Only 25 watts at 100 watts indicated It would be nice to know what conditions caused this FET failure. Is there an easy way to know when this failure occurs other than getting crappy audio reports? John KK9A Peter Dougherty (W2IRT) wrote: This happened to me at the start of CQWW-SSB in October. My K3s is finally enroute back home after a 6 week stay in the Elecraft Repair Department with a blown FET in the HPA, cause unknown. And I know I've been told I'm not the only one to suffer this failure, and it sounds like this is now a known issue. Does anybody have an idea as to what could be causing these FETs to fail, or steps to consider to lessen the chances of it happening? I can't speak for anybody else, but I baby the heck out of my gear and was shocked to discover it failed, when feeding directly into a KPA-1500. Regards, Peter Dougherty, W2IRT -Original Message- From: elecraft-bounces at mailman.qth.net [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Wes Stewart Sent: Wednesday, December 12, 2018 4:55 PM To: elecraft at mailman.qth.net Subject: Re: [Elecraft] K3 Suddenly Putting Out Only 25 watts at 100 watts indicated If you have another receiver, run a two-test and listen to the K3 output in a narrow BW. Ideally, the two tones will be considerably stronger than the first pair of sidebands. I suspect they won't be, you'll have a lot more than two and you have a blown FET in the HPA. Wes N7WS __ 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 Suddenly Putting Out Only 25 watts at 100 watts indicated
This happened to me at the start of CQWW-SSB in October. My K3s is finally enroute back home after a 6 week stay in the Elecraft Repair Department with a blown FET in the HPA, cause unknown. And I know I've been told I'm not the only one to suffer this failure, and it sounds like this is now a known issue. Does anybody have an idea as to what could be causing these FETs to fail, or steps to consider to lessen the chances of it happening? I can't speak for anybody else, but I baby the heck out of my gear and was shocked to discover it failed, when feeding directly into a KPA-1500. Regards, Peter Dougherty, W2IRT -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Wes Stewart Sent: Wednesday, December 12, 2018 4:55 PM To: elecraft@mailman.qth.net Subject: Re: [Elecraft] K3 Suddenly Putting Out Only 25 watts at 100 watts indicated If you have another receiver, run a two-test and listen to the K3 output in a narrow BW. Ideally, the two tones will be considerably stronger than the first pair of sidebands. I suspect they won't be, you'll have a lot more than two and you have a blown FET in the HPA. Wes N7WS On 12/12/2018 12:47 PM, N4ZR wrote: > Transmitted on my K3 for the first time since the 10-meter contest, and it is > only showing 25 watts out on the built-in meter into a dummy load. Power > output setting of the K3 is 100W, and same results seen on all bands. What > could possibly be going on here? Back to Watsonville? > > The cruel karma of it all is that *yesterday* I ordered a KPA-1500. > __ 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 li...@w2irt.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] Wish I had a KAT1500
I agree, Victor! I have a newer HF-Auto which is even more problematic than the AT-Auto. The issues for me are 40 and 80. I have a shorty forty Yagi, with about 175 kHz between the 2:1 points. Since I normally operate in the bottom end of the band (CW and occasionally FT8) I set the resonant point around 7040, which makes it usable all the way to the bottom of the phone band. But on phone, the SWR varies from 2:1 at 7128 to about 8:1 at 7300. It's equally problematic on 80 (resonant 3575, 3:1 points 3500 to 3675 to make the KPA-1500 happy). Above 40, and 160m, my antennas are resonant. I'd pay anything for an auto-tuner that can handle full power, works properly every time and uses band data, rather than RF sensing (which is how the HF-Auto works). I don't have a tower that can handle a full-size/full-bandwidth 40m Yagi as well as everything else I need up there, so I'm reliant on a tuner to make things usable. I remote in to my station once in a while, and I'm at a big disadvantage on 40 when I need to go on phone. I'm almost never on 80 phone (except for two contest weekends a year) so that's not a big problem. I can't believe that nobody in the ham community has come out with a 5kW-rated 10:1 fully automatic tuner, with everything else that's been done lately. Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Victor Rosenthal 4X6GP Sent: Tuesday, November 27, 2018 10:32 AM To: Elecraft Reflector Subject: [Elecraft] Wish I had a KAT1500 I am using an older Palstar AT-Auto automatic tuner. It has a coil and capacitor operated by stepper motors. When it works, it's fine; but it requires a lot of maintenance and fiddling. What I need is something that works as well as the KAT3 in my K3; quick, trouble-free, and good for a 10:1 SWR on HF. Oh yes, it has to handle 1.5 kW, too. If Elecraft would beef up the KAT500 to meet the above specs, I'd buy one. -- 73, Victor, 4X6GP Rehovot, Israel Formerly K2VCO CWops no. 5 http://www.qsl.net/k2vco/ __ 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 li...@w2irt.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] Possible K3s TX failure - distorted audio
Well here we are two weeks later. The radio's been sitting in the repair queue since Nov. 1st and hasn't even been looked at yet according to the phone call I just placed. Still waiting to experience that legendary Elecraft support that everybody here raves about. To have a radio that I went four years into debt to buy fail catastrophically after two years of extremely light use isn't something I signed up for. Sorry for venting, but I basically lost a chance at setting a personal best in CQWW-SSB and now CW seems out of the question too, although thankfully a loaned Flex 6500 has at least kept me on the air. Regards, Peter Dougherty, W2IRT -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Gary Smith Sent: Sunday, October 28, 2018 8:58 PM To: Elecraft@mailman.qth.net Subject: Re: [Elecraft] Possible K3s TX failure - distorted audio Peter, I had that issue with the K3s, same kind of issue. I'd sent it in maybe 3 months ago for some warranty work & work on the PA I believe it was, but hadn't used the SSB for the same reasons as you. I heard no issue in the headphones listening to Monitor but got many reports of a terrible signal. I bought a HM4 mic thinking that was the issue but the new mic did no better. I ran the backup K3 and got excellent reports with the KM4 mic so knew the issue was in the K3s. It's in California, in Queue right now. Your issue may be different. 73, Gary KA1J > Hi all. > Early into CQWW this weekend I was getting reports of extremely > distorted audio from my K3s. Being mostly a CW (and 6m FT8) operator I > wasn't sure what was going on. I figured it was RF, but it was > happening at all power levels, from QRP to 100W, and QRO with my > KPA-1500. Same (bad) audio, just stronger/weaker signals. All bands > were equally bad. > > I ended up going from the radio directly to the tower, physically > bypassing the amp and tuner, and only running low power, with the same > result. It sounded more like distorted audio than RF ingress. > > Some troubleshooting by Dave, WO2X, who is a Flex owner: He remoted in > to his Flex a few miles away and noticed my garbled signal was > absolutely dirty and wide, despite low mic gain and little or no > compression. The audio sounded clean through the monitor, so it wasn't > the audio chain. He's speculating I may have a blown FET in the PA > stage. > > We put in a Flex 6500 temporarily and it seems to be running fine. > Wondering if anybody here has had experience with this, and if so, > what are my next steps? > > Thanks in advance. > > - > 73 and Good DX > Peter, W2IRT > > K3s S/N 10023 > > > __ > 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 g...@ka1j.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 li...@w2irt.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] Accessories or upgrades to K3s?
Now that the problem with the KPA3 module on my K3s has been identified I'm sending my beloved rig off to Watsonville later today. While it's out getting re-Elecrafted, I'm wondering if there are any mods or improvements that I should be considering. I bought it assembled in 2015, ordered the first day it was offered for sale, in fact. I have matched 2.7 filters, matched 400s for Diversity RX, a 250 and 2.1 in the main RX and the 13 kHz TX filter. I don't have the DVK or TXCO (and I still don't know what I'd do with the latter). So anything else I should consider? Thanks in advance! Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT __ 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] Retiring my MK-II
-Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Gary Smith Sent: Monday, October 29, 2018 1:11 PM To: Elecraft@mailman.qth.net Subject: Re: [Elecraft] Retiring my MK-II > I know I'm going to lose two things: The Winkeyer, and true FSK RTTY. # Perhaps not, I use the marvelous Win4K3Suite which with com0com gives me com ports aplenty to use MMTTY, N1MM, WSJT-X and Logic 9 all running at the same time. [pjd] I do plan to purchase Win4K3 eventually. # I check off the Winkey box in the N1MM setup and use the USB winkey. I'm assuming you don't have the USB version. maybe there's a mod to add USB to your unit? [pjd] I don't own a stand-alone Winkeyer. I own the MicroHam Microkeyer-II, has a Winkeyer built-in, and it's that device that I want to retire. # With RTTY, I use N1MM and run the MMTTY digital window with the K3 set to AFSK A and it works beautifully. When not using RTTY I set the radio to DATA A for WSJT-X Flawless. [pjd] That's good to know. I will be using both RTTY and FT-8. For RTTY, the need is to have left audio/control for VFO-A and right for VFO-B, which is how I have it set now. Receive shouldn't change, I don't imagine, but I'm not sure how to transmit RTTY on the K3s without the Microkeyer-II. And as another posted mentioned, sequencing .WAV files in N1MM and WinWarbler is an extremely high priority. There are two issues at play for me. One is a complex hardware setup that can easily allow the ingress of RFI into the audio chain, and that makes physical reconnection of the radio a real chore after I have to take it out for whatever reason. Connections that are fragile, wires that can't be dressed correctly because of length due to the arrangement of my radio desk and so on. The other side of the equation, and I think I may be fearing this even more, is the need to replace all sorts of hardware and cables with a maze of even more impenetrable software. As anybody who knows me knows, I *detest* software solutions since it's so easy for any one app to break when Windows 10 veers off in another direction. So basically, what it boils down to is this: Can I transmit and receive CW, SSB, two-VFO RTTY, FT-8 and other digimodes, .WAV file sequencing, firmware uploads, and CAT control to/from the K3s using mostly just the single USB cable and the physical connection to my paddles? I want to implement a KISS solution **IF** it can be done. Otherwise I'll just keep the MK-II in line since it's a known-valid configuration, albeit one I don't particularly like (no offense, Joe). 73, Gary KA1J __ 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 li...@w2irt.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] Retiring my MK-II
Hi all, Now that I have my K3s out of the desk for repairs, one of the things I'd planned to do is to retire my MicroHam Microkeyer-II. Since the K3s has its own built-in sound card it connects via USB I don't see the need for the MK-II any longer, and frankly I'd like to reduce the complexity and clutter behind the radio in a very tight space. I am using both the K3s and a P3 (with TX monitor), so I'm unsure of the needed cabling. I also have a Y-box installed at the moment, for my band decoder to the antenna switch and to my KPA-1500. I set this all up in July, 2015 and quite honestly, I've forgotten all the steps I needed to get the rig working with the MK-II, so I'd appreciate any details of how to get everything working without it. I know I'm going to lose two things: The Winkeyer, and true FSK RTTY. I've operated away from home just using the K3s's internal keyer and never had a problem (I'm still a relative slowpoke, rarely over 32WPM in contests and lower other times). RTTY will be a challenge for me, though. I haven't used AFSK for 17 years so would greatly appreciate help in making that work, especially with dual VFOs. Thanks in advance! Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT K3s S/N 10023 KPA-1500 S/N 0398 __ 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] Possible K3s TX failure - distorted audio
Hi all. Early into CQWW this weekend I was getting reports of extremely distorted audio from my K3s. Being mostly a CW (and 6m FT8) operator I wasn't sure what was going on. I figured it was RF, but it was happening at all power levels, from QRP to 100W, and QRO with my KPA-1500. Same (bad) audio, just stronger/weaker signals. All bands were equally bad. I ended up going from the radio directly to the tower, physically bypassing the amp and tuner, and only running low power, with the same result. It sounded more like distorted audio than RF ingress. Some troubleshooting by Dave, WO2X, who is a Flex owner: He remoted in to his Flex a few miles away and noticed my garbled signal was absolutely dirty and wide, despite low mic gain and little or no compression. The audio sounded clean through the monitor, so it wasn't the audio chain. He's speculating I may have a blown FET in the PA stage. We put in a Flex 6500 temporarily and it seems to be running fine. Wondering if anybody here has had experience with this, and if so, what are my next steps? Thanks in advance. - 73 and Good DX Peter, W2IRT K3s S/N 10023 __ 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] K-Pod CTS to match VFO
If Elecraft chooses to make this available, **please** make it optional. I personally prefer it the way it is, but I certainly understand how others would want it to track the main VFO, and I understand their arguments as well. Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Fred Jensen Sent: Wednesday, October 3, 2018 5:29 PM To: elecraft@mailman.qth.net Subject: Re: [Elecraft] K-Pod CTS to match VFO Count me in if it's an option. 73, Fred ["Skip"] K6DGW Sparks NV DM09dn Washoe County On 10/3/2018 1:08 PM, Mike Cox wrote: > I'd use this for sure! > > Mike, AB9V > > > On 10/3/2018 12:27 PM, NW0M wrote: >> Art, >> >> I've been for this too. Wayne said a couple years back that they >> were going >> to add this to the firmware. I guess we're the only two K-Pod owners >> that >> want this. I'm not calling this a major enhancement request but it >> would be >> a nice one. >> >> 73, >> Mitch NWØM __ 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 li...@w2irt.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] Shipping high value items by UPS
I ship *everything* by the US Postal Service, and if the day ever comes that I need to send my K3s or KPA-1500 back for service you can bet it'll be using the post office, with original Elecraft shipping boxes and a premium shipping method with full insurance. I ship merchandise commercially and I've found their insurance far easier to claim on the 2 instances in 27 years that I needed to do so than the first (and only) time I ever tried to do this with UPS on a used/dead laptop. And they refused to pay. FedEx I wouldn't trust to pick up a piece of litter on the ground, let alone a $6,000 amp. Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Grant Youngman Sent: Tuesday, September 25, 2018 3:53 PM To: Elecraft Reflector Reflector Subject: Re: [Elecraft] Shipping high value items by UPS I don’t know what the other guys do. But this has apparently been a UPS policy since February for packages delivered to the Service Center. Didn’t know about it of course, and don’t think there was any kind of warning on the website. Maybe just missed the announcement. I seem to recall the last time I shipped something insured for near maximum value, that the UPS Store could take it and sign for it, but that doesn’t seem to be the case any longer. I’m not deriding UPS, just be aware if you ship an item (like a K3) with high-value insurance by UPS, and have to take it to a Service Center, expect them to ask you (you have to do yourself) to open or unpack the item so they can inspect it and make sure it isn’t ticking :-) Grant NQ5T K3 #2091 KX3 #8342 > On Sep 25, 2018, at 3:31 PM, Carl Jón Denbow wrote: > > Never had a problem like that at UPS, and I’ve shipped many high value items > with them. I did have a problem like that, but not as severe, at FedEx once. > They opened the box because I said the value was about $4000.00. They had to > insure the packing was sufficient. I’ve avoided them for high-value items > ever since. 73 de Carl > __ 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 li...@w2irt.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] KPA-1500 and Remotehams.com
Hi all, I'd like to be able to use my KPA-1500 with Remotehams, but I'm not sure how to set this up. First off, the baud rate is limited in the RCFOrb server app to 115200, and secondly, I'm guessing I have to open a port somewhere?? If the only way to do this is drop the baud rate on the KPA, what else will have to change in other software or with the K3s in order to communicate? I have the amp running on COM-14, and it is also on my LAN. Thanks in advance. Regards, Peter Dougherty, W2IRT DXCC Card Checker/CQ-WAZ Checkpoint www.facebook.com/W2IRT __ 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
