KPA-1500, too?
Locked
 
|
Perhaps KV5J can come up with an amplifier monitor for the KPA-1500, too? Hope so!
K4TM Sent from Clovelly Cottage II, home of amateur radio station K4TM and the most creative Sue Cary, in the foothills of the beautiful Blue Ridge mountains of Virginia. > On Jul 14, 2020, at 2:29 PM, [hidden email] wrote: > > Send Elecraft mailing list submissions to > [hidden email] > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qth.net/mailman/listinfo/elecraft > or, via email, send a message with subject or body 'help' to > [hidden email] > > You can reach the person managing the list at > [hidden email] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Elecraft digest..." > > > Today's Topics: > > 1. Very pleased with KV5J Digital Display Unit for the Elecraft > KPA500 (Macy monkeys) > 2. Fwd: Re[2]: K2 7747 VCO alignment problem (Keith Hamilton) > 3. Re: FT8 - was "On Second Thought, I'll Take The Stairs" > (Robert Hand) > 4. Re: Fwd: Re[2]: K2 7747 VCO alignment problem (Dave Van Wallaghen) > 5. Re: "On second thought, I'll take the stairs." (Kurt Pawlikowski) > 6. Re: Fwd: Re[2]: K2 7747 VCO alignment problem (Keith Hamilton) > 7. K3 very slow to reach dialed rf output (John) > 8. Re: "On Second Thought, I'll Take The Stairs (Doug Turnbull) > 9. Elecraft K2 CW key shaping (dl2ki) > 10. Re: Elecraft K2 CW key shaping (Victor Rosenthal 4X6GP) > 11. Re: Elecraft K2 CW key shaping (Matt Maguire) > 12. Re: Elecraft K2 CW key shaping #chirp #click (Rich NE1EE) > 13. Re: K3 very slow to reach dialed rf output (David Herring) > 14. Re: [K3] Sub receiver intermittant failures (w4sc) > 15. Re: K3 very slow to reach dialed rf output (John) > 16. Replace backup battery CR2032 in a K3 (Steef PA2A) > 17. Re: Replace backup battery CR2032 in a K3 (Grant Youngman) > 18. Re: "On Second Thought, I'll Take The Stairs (Jim Brown) > 19. Re: "On Second Thought, I'll Take The Stairs (Tony Estep) > 20. Re: Replace backup battery CR2032 in a K3 (Nr4c) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 13 Jul 2020 17:05:31 -0700 > From: Macy monkeys <[hidden email]> > To: [hidden email] > Subject: [Elecraft] Very pleased with KV5J Digital Display Unit for > the Elecraft KPA500 > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=us-ascii > > > I just finished hooking up the remote KV5J DDU for my KPA500. It arrived today via USPS extremely well packed. Hook up was a snap. The unit does exactly what Keith says it does. And it looks terrific! The display is not too bright, not too dim. Perfect! It is very professional looking in a stout metal housing. Keith was quick to answer my emails. > > Very pleased! I have no connection to Keith or his products other than being a satisfied customer. > > John K7FD > > >> On Jul 13, 2020, at 3:04 PM, Macy monkeys <[hidden email]> wrote: >> >> I purchased it exactly for those reasons; my KPA500 is on a shelf under my operating desk. The DDU will enable me to see what I can't easily see now. Perfect solution. >> >> And yes, my DDU arrived today and I will soon give it a shakedown cruise... >> >> John K7FD >> >>>> On Jul 13, 2020, at 12:58 PM, Keith Ennis via Elecraft <[hidden email]> wrote: >>> >>> Andy, >>> >>> It's design was not to replace the KPA500 utility if that is what you want >>> to use. It was designed to show the 5 most often used readings from the >>> front panel that can only be seen one at a time. >>> >>> Plus it does not use any PC resources. Monitor space is limited to most >>> operators. Same with com ports. >>> >>> Place the KPA500 wherever you want and place the DDU next to your radio. >>> Saves on heat, noise and desktop space. >>> >>> Thanks for your input.73 >>> >>> Keith,KV5J >>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > > > ------------------------------ > > Message: 2 > Date: Mon, 13 Jul 2020 21:34:03 -0400 > From: Keith Hamilton <[hidden email]> > To: [hidden email] > Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem > Message-ID: > <[hidden email]> > Content-Type: text/plain; charset="UTF-8" > > ---------- Forwarded message --------- > From: Keith Hamilton <[hidden email]> > Date: Mon, Jul 13, 2020 at 9:19 PM > Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem > To: Dave Van Wallaghen <[hidden email]> > > > Dave > > Yes the frequency changes when turning the VFO knob when measuring with CAL > FCTR on TP1. > > I have checked the markings on C71, C72, C73, and C74 (C75 is not installed > yet). They are > all correct and I resoldered them to be sure. > > I am beginning to think I might have a bad relay K13, K14 or K15. My good > bands are 80,40 and > 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the relay > table in appendix B > I am not sure which relay could be bad. How can I test them? Should I try > to replace them? > 73, > Keith N8CEP > > >> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> wrote: >> >> Ok Keith, just to make sure things are where we want on the bands that >> seem to work, does the frequency change when turning the VFO knob when >> measuring with CAL FCTR on TP1? If they do, then things are working ok. >> >> For the bands that are locked at 8.28v, that is the max output from the >> integrator circuit (U6B). This means that there is no lock between the PLL >> Oscillator and the VCO circuit and the PLL chip (U4) is trying to drive the >> varactors to provide more capacitance to the VCO circuit. The most likely >> cause will be a misplaced capacitor in the VCO range selector (C71 - C75) >> or a problem in the VCO circuit itself. But because this may be band >> dependent, I would look first in that range selection circuit. Verify that >> those caps are the proper values. They are easily misread and will cause >> the type of thing you are seeing. >> >> Also verify those varactor diodes are the proper type and in the right >> places. Soldering issues are typically the leading cause of problems, so >> check that also. If all looks right to you, you may want to signal trace >> through that selection circuit to verify the proper relays and active for >> the bands not working. There is a relay table in Appendix B that shows you >> which relays are active for each band. >> >> This is a brand new build, correct? >> >> 73, >> Dave, W8FGU >> >> >> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> wrote: >> >> Thanks for your help Dave! >> >> Yes. I was able to get 6 volts on R30 by turning L30. At first the voltage >> was too high >> so I adjusted the turns on T5 by spreading the red windings further apart. >> Then I >> was able to get to 6 volts. >> >> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >> The reading is 8912.22 >> >> 73 Keith N8CEP >> >> >>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> wrote: >>> >>> Hi Keith, >>> >>> Were you able to get 6v on R30 by tuning L30? Did you have to bring the >>> voltage down or up by moving the windings on T5? >>> >>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>> know what the reading is. I'm just looking for a couple of clues before >>> we proceed. >>> >>> 73, >>> Dave, W8FGU >>> >>> >>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> wrote: >>> >>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>> windings >>>> and obtained 6 volts at the left end of R30. I then went on to the chart >>>> (table 6-1) to measure the voltages at the listed frequencies. My >>> readings >>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on 30,20,17 >>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>> >>>> I have checked the solder connections of T5 and the value of C72 (271). >>> The >>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also went >>>> over the solder connections of K13, K14 and K15. >>>> >>>> Now I'm stuck. Any help will be appreciated. >>>> >>>> Keioth Hamilton N8CEP >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >>> >>> > > > ------------------------------ > > Message: 3 > Date: Tue, 14 Jul 2020 01:48:37 +0000 > From: Robert Hand <[hidden email]> > To: Victor Rosenthal 4X6GP <[hidden email]> > Cc: "[hidden email]" <[hidden email]>, > "[hidden email]" <[hidden email]> > Subject: Re: [Elecraft] FT8 - was "On Second Thought, I'll Take The > Stairs" > Message-ID: > <[hidden email]> > > Content-Type: text/plain; charset="utf-8" > > I still say, ?appliance operator ? > > Sent from my iPhone > >> On Jul 13, 2020, at 3:36 PM, Victor Rosenthal 4X6GP <[hidden email]> wrote: >> >> ?I didn't notice myself "denigrating" anything or "talking down" to anyone. I explained why I like CW, even though other modes have their own advantages. >> >> Regarding "increasing knowledge" and "innovating," I suspect that 90% of the guys pointing and clicking their way to DXCC with K1JT's code couldn't explain how it works. >> >> 73, >> Victor, 4X6GP >> Rehovot, Israel >> Formerly K2VCO >> CWops no. 5 >> http://www.qsl.net/k2vco/ >> . >>>> On 13/07/2020 23:11, Jim Rhodes wrote: >>> Connecting to history and making history are not the same thing. Doing things the same way they were done a hundred years ago may make a "connection" for you. But hams are supposed to innovate, invent and increase the knowledge. So you buy or build equipment with way more ability than to send simple CW, so you can do simple CW? Yes, CW is great stuff, but it sure isn't innovative, nor does in increase the knowledge of communication. As a group we should encourage others to explore new communications systems, not denigrate them as "not REAL HAM RADIO". Some of you people should be ashamed of yourselves for your attitudes. We do not want Amateur Radio to die with our generation, so we should encourage new folks to do new things, not talk down to them because they don't choose to spend 99% of their operating time pounding brass. They don't give you static about taking up bandwidth with your ancient operating mode, why hassle them because they can make Qs below the noise leve > l. Oh yes, my DXCC certificate says "Mixed" on it. I quit counting when I got that. >>>> On Mon, Jul 13, 2020, 03:25 Victor Rosenthal 4X6GP <[hidden email] <mailto:[hidden email]>> wrote: >>> Actually, I'm building a regenerative receiver now. I have to use JFETs >>> because I got rid of all my tube stuff due to lack of room. But of >>> course I will continue to benefit from the DSP in my K3, and its keyer >>> (although I have a bug that I use once in a while). >>> But those things don't take away the connection to history, they >>> make it >>> better. The point for me isn't to use the same gear as they did in >>> 1912, >>> but to enter the Morse space as they did. If I can do it with equipment >>> that is more stable and effective, so much the better. >>> After all, a modern sailboat is very much more sophisticated than an >>> old >>> one, but sailing is still sailing. >>> 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:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > ------------------------------ > > Message: 4 > Date: Tue, 14 Jul 2020 02:35:36 +0000 > From: "Dave Van Wallaghen" <[hidden email]> > To: "Keith Hamilton" <[hidden email]>, [hidden email] > Subject: Re: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem > Message-ID: <em385dd5fe-747a-45c7-91aa-6be7eb9502cb@desktop-lqvflms> > Content-Type: text/plain; format=flowed; charset=utf-8 > > Keith, > > I saw Don respond to this and he is right that K15 would be the common > denominator if not for 15m. You can check to see if the coils are intact > if you measure the resistance between pins 1 and 10 for each. It should > be around 230 ohms or so. If you find one open or well away from that > resistance, then it would indicate a bad coil on that relay. > > You can also measure the intended path through the relays for each band > and make sure there are no unintended paths. If you can read the > schematic, it shows the path with each relay in it's reset state. You > would need to consult the table in Appendix B to see which relay(s) are > active for a respective band and you can then measure the continuity of > the intended path. You should also check any unintended paths which > could indicate a problem. > > As Don stated, this is not a fun problem to find and will take some good > debugging skills. So far, everything you've indicated seems to suggest > the PLL oscillator and VCO circuits are working properly, but the range > selection area is not producing the proper capacitance to allow the VCO > to produce the proper frequency on those bands you indicated. > > If reading the schematic is a problem, let us know and I am sure between > Don and myself, we can give you some step by step instructions for > tracing through this problem. > > 73, > Dave W8FGU > > ------ Original Message ------ > From: "Keith Hamilton" <[hidden email]> > To: [hidden email] > Sent: 7/13/2020 9:34:03 PM > Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem > >> ---------- Forwarded message --------- >> From: Keith Hamilton <[hidden email]> >> Date: Mon, Jul 13, 2020 at 9:19 PM >> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >> To: Dave Van Wallaghen <[hidden email]> >> >> >> Dave >> >> Yes the frequency changes when turning the VFO knob when measuring with CAL >> FCTR on TP1. >> >> I have checked the markings on C71, C72, C73, and C74 (C75 is not installed >> yet). They are >> all correct and I resoldered them to be sure. >> >> I am beginning to think I might have a bad relay K13, K14 or K15. My good >> bands are 80,40 and >> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the relay >> table in appendix B >> I am not sure which relay could be bad. How can I test them? Should I try >> to replace them? >> 73, >> Keith N8CEP >> >> >>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> wrote: >>> >>> Ok Keith, just to make sure things are where we want on the bands that >>> seem to work, does the frequency change when turning the VFO knob when >>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>> >>> For the bands that are locked at 8.28v, that is the max output from the >>> integrator circuit (U6B). This means that there is no lock between the PLL >>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to drive the >>> varactors to provide more capacitance to the VCO circuit. The most likely >>> cause will be a misplaced capacitor in the VCO range selector (C71 - C75) >>> or a problem in the VCO circuit itself. But because this may be band >>> dependent, I would look first in that range selection circuit. Verify that >>> those caps are the proper values. They are easily misread and will cause >>> the type of thing you are seeing. >>> >>> Also verify those varactor diodes are the proper type and in the right >>> places. Soldering issues are typically the leading cause of problems, so >>> check that also. If all looks right to you, you may want to signal trace >>> through that selection circuit to verify the proper relays and active for >>> the bands not working. There is a relay table in Appendix B that shows you >>> which relays are active for each band. >>> >>> This is a brand new build, correct? >>> >>> 73, >>> Dave, W8FGU >>> >>> >>>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> wrote: >>> >>> Thanks for your help Dave! >>> >>> Yes. I was able to get 6 volts on R30 by turning L30. At first the voltage >>> was too high >>> so I adjusted the turns on T5 by spreading the red windings further apart. >>> Then I >>> was able to get to 6 volts. >>> >>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>> The reading is 8912.22 >>> >>> 73 Keith N8CEP >>> >>> >>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> wrote: >>> >>>> Hi Keith, >>>> >>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring the >>>> voltage down or up by moving the windings on T5? >>>> >>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>> know what the reading is. I'm just looking for a couple of clues before >>>> we proceed. >>>> >>>> 73, >>>> Dave, W8FGU >>>> >>>> >>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> wrote: >>>> >>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>> windings >>>>> and obtained 6 volts at the left end of R30. I then went on to the chart >>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>> readings >>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on 30,20,17 >>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>> >>>>> I have checked the solder connections of T5 and the value of C72 (271). >>>> The >>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also went >>>>> over the solder connections of K13, K14 and K15. >>>>> >>>>> Now I'm stuck. Any help will be appreciated. >>>>> >>>>> Keioth Hamilton N8CEP >>>>> ______________________________________________________________ >>>>> Elecraft mailing list >>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>> Post: mailto:[hidden email] >>>>> >>>>> This list hosted by: http://www.qsl.net >>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>> Message delivered to [hidden email] >>>> >>>> >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > > > ------------------------------ > > Message: 5 > Date: Mon, 13 Jul 2020 21:47:01 -0500 > From: Kurt Pawlikowski <[hidden email]> > To: Wayne Burdick <[hidden email]>, Elecraft Reflector > <[hidden email]> > Subject: Re: [Elecraft] "On second thought, I'll take the stairs." > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Wayne: Would you mind if I forwarded this to our ham newsletter editor > for reprint? Thanks! k WB9FMC > >> On 7/12/2020 10:07 AM, Wayne Burdick wrote: >> I have a friend about my age who got into amateur radio only a few years ago. Like many of us, he was enthusiastic about the technology. Intrigued with DX. >> >> I showed him my station; we talked endlessly about gear. Later, I helped him put up a simple wire antenna. >> >> Then, when his license arrived, he dove straight into FT8 and didn't look back. Within days, he'd worked all states, then DXCC. He'd bag a few rare ones over a light lunch, then pat his laptop on the back and congratulate his software app for its near-mythical ability to extract weak signals out of noise. >> >> Within weeks, he'd mastered everything there was to know about this glorious new hobby. >> >> Point. Click. >> >> In this new world order, those of us who took the longer, slower path to ionospheric enlightenment -- and who still occasionally enjoy making waves by hand -- often fail to explain why. >> >> I had failed to explain it to my friend. Even as hints of his boredom crept in, creating an opening, the best argument I'd made for trying CW was that he could do it without a computer. Coming in a weak second was the notion that CW was the original digital mode. For obvious reasons, I didn't bother with the classic argument about CW's signal-to-noise advantage over SSB. >> >> I had all but given up. >> >> Then, in a moment of delayed clarity, I decided on a different approach. I invited him to a weekday brunch. A bit of an escape. He willingly took the bait. >> >> On the appointed day, arriving at his workplace, I bypassed the lobby's glistening elevators and climbed the four flights of stairs to his office. I insisted we take the stairs down, too. >> >> "Why?" he asked. "And how'd you get up here so fast?" >> >> I pointed out that I always chose stairs, when possible. That's why I wasn't out of breath. We hustled down, jockeying for position, and emerged on the ground floor invigorated by the effort. >> >> "So, where are we going?" he asked. We'd been to every overrated twenty-dollar burger venue at least twice. >> >> I replied that we'd be going someplace we'd never tried. My kitchen. >> >> When we arrived, I put him to work chopping onions and broccoli and squeezing oranges while I whipped eggs into a froth and grated Swiss cheese. We ate our omelettes outside, in full sun and a cool breeze. >> >> "What's for desert?" he asked. "Isn't there a frozen yogurt place a two-minute drive from here?" >> >> I had something else in mind. Back in the kitchen, I handed him a water bottle, then strapped on a small pack I'd prepared earlier. >> >> We walked a mile or so through my neighborhood, admiring the houses' varied architecture, ending up (as planned) at a local park festooned with blackberry bushes. The most accessible branches had been picked clean, but with teamwork and persistence we were able to gather several large handfuls of fat, ripe berries, which we devoured on the spot. >> >> We'd been poked and scratched but didn't care. >> >> "Doesn't brunch usually end with champagne?" he wondered aloud, admiring his wounds. >> >> Not this time. I pulled out two bottles of craft beer that I'd obtained from a neighbor in trade for repairing his ancient home stereo. Carlos had spent years crafting an American pilsner to die for, sweating every detail, including iconic, hand-painted labels. >> >> My friend accepted the bottle, then tried in vain to remove the cap. Not a twist-off. >> >> "Opener?" he said. >> >> I handed him a small pocket knife, an antique without specialty blades. He soon discovered it could not be used to remove the cap directly. He looked at me with a bemused expression, no doubt wondering what I had up my sleeve this time. >> >> I pointed out that we were surrounded by white oaks, a species known for its hard wood. He got the message, smiled, and began hunting. Within seconds he'd collected a small fallen branch. I watched as he used the knife to fashion a few inches of it into a passable bottle opener. We popped the caps, toasted his new-found skill, and traded stories of our misspent youths. >> >> "Oh, one more thing," I said. >> >> I pulled a KX2 out of my pack, along with two lengths of wire. Of course he knew everything there was to know about Elecraft, and me, so he wasn't surprised when I also pulled out the rig's attachable keyer paddle. We threw one wire in the closest tree and laid the other on the ground. >> >> He didn't have to ask whether I'd brought a laptop. >> >> We listened to CW signals up and down 20 meters, which was open to Europe at the time. As he tuned in each station, I copied for him using pencil and paper. He'd learned Morse code, but only at very slow speeds. >> >> After making a contact, I set the internal keyer speed to 10 words per minute and dialed power output to zero, for practice purposes, then showed him how to use the paddle. He smiled as he got the hang of it. Sending the full alphabet was a challenge, but he got there. The KX2 decoded and displayed his keying, providing confirmation. >> >> We'd blown through his allotted lunch break by a factor of three, so it was time to go. We coiled up the antenna wires, packed up, and walked back. As I drove him back to his employer, we made plans to get together again for a weekend hike. >> >> I could have just dropped him off, but we went back into the lobby together. Out of habit, he stopped in front of the elevator. Then he looked up. >> >> "OK," he said. "I get it. This CW thing. It's slow, it's hard to do well, and it takes years of practice." >> >> "Like hunting for your own food, or carving your own tools," I added. >> >> "Or cooking from scratch. Or brewing your own beer. Building your own radio. And you use more of your senses. Not just your eyes, but your ears. Your sense of touch." >> >> I nodded. Listening. Feeling. That was the radio I'd grown up with. >> >> "Of course it's harder to work DX with CW than with FT8," I reminded him, playing devil's advocate. >> >> "Is that what matters, though?" he asked. >> >> A longer discussion for another day. >> >> "Your call," I said. >> >> He gripped my shoulder and smiled, then reached toward the elevator's glowing, ivory colored button, framed by polished brass. >> >> The path most taken. >> >> Point. Click. >> >> "On second thought," he said, "I'll take the stairs." >> >> * * * >> >> Wayne, >> N6KR >> >> >> >> >> >> >> >> >> >> >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > > ------------------------------ > > Message: 6 > Date: Mon, 13 Jul 2020 23:00:59 -0400 > From: Keith Hamilton <[hidden email]> > To: Dave Van Wallaghen <[hidden email]> > Cc: [hidden email] > Subject: Re: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem > Message-ID: > <CAJkuCUZmuY7Ys=ypJjjEK0wt7o5ocWzVCZQL=SZkPC7E=[hidden email]> > Content-Type: text/plain; charset="UTF-8" > > OK Dave - > > I will check the relays as you suggest. In troubleshooting capacitors I > messed up > C74. I pulled it off the board and sent a request to Elecraft for a > replacement. > That may solve the problem. In the meantime I will check the coils on the > K13 to K15 > relays and let you know what I find. > > I did not see Don's post. I will check it out. So I will be waiting a bit > to fix this problem, > > 73 and thanks! > Keith N8CEP > >> On Mon, Jul 13, 2020 at 10:36 PM Dave Van Wallaghen <[hidden email]> wrote: >> >> Keith, >> >> I saw Don respond to this and he is right that K15 would be the common >> denominator if not for 15m. You can check to see if the coils are intact >> if you measure the resistance between pins 1 and 10 for each. It should >> be around 230 ohms or so. If you find one open or well away from that >> resistance, then it would indicate a bad coil on that relay. >> >> You can also measure the intended path through the relays for each band >> and make sure there are no unintended paths. If you can read the >> schematic, it shows the path with each relay in it's reset state. You >> would need to consult the table in Appendix B to see which relay(s) are >> active for a respective band and you can then measure the continuity of >> the intended path. You should also check any unintended paths which >> could indicate a problem. >> >> As Don stated, this is not a fun problem to find and will take some good >> debugging skills. So far, everything you've indicated seems to suggest >> the PLL oscillator and VCO circuits are working properly, but the range >> selection area is not producing the proper capacitance to allow the VCO >> to produce the proper frequency on those bands you indicated. >> >> If reading the schematic is a problem, let us know and I am sure between >> Don and myself, we can give you some step by step instructions for >> tracing through this problem. >> >> 73, >> Dave W8FGU >> >> ------ Original Message ------ >> From: "Keith Hamilton" <[hidden email]> >> To: [hidden email] >> Sent: 7/13/2020 9:34:03 PM >> Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> >>> ---------- Forwarded message --------- >>> From: Keith Hamilton <[hidden email]> >>> Date: Mon, Jul 13, 2020 at 9:19 PM >>> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >>> To: Dave Van Wallaghen <[hidden email]> >>> >>> >>> Dave >>> >>> Yes the frequency changes when turning the VFO knob when measuring with >> CAL >>> FCTR on TP1. >>> >>> I have checked the markings on C71, C72, C73, and C74 (C75 is not >> installed >>> yet). They are >>> all correct and I resoldered them to be sure. >>> >>> I am beginning to think I might have a bad relay K13, K14 or K15. My good >>> bands are 80,40 and >>> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the >> relay >>> table in appendix B >>> I am not sure which relay could be bad. How can I test them? Should I try >>> to replace them? >>> 73, >>> Keith N8CEP >>> >>> >>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> >> wrote: >>> >>>> Ok Keith, just to make sure things are where we want on the bands that >>>> seem to work, does the frequency change when turning the VFO knob when >>>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>>> >>>> For the bands that are locked at 8.28v, that is the max output from the >>>> integrator circuit (U6B). This means that there is no lock between the >> PLL >>>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to >> drive the >>>> varactors to provide more capacitance to the VCO circuit. The most >> likely >>>> cause will be a misplaced capacitor in the VCO range selector (C71 - >> C75) >>>> or a problem in the VCO circuit itself. But because this may be band >>>> dependent, I would look first in that range selection circuit. Verify >> that >>>> those caps are the proper values. They are easily misread and will >> cause >>>> the type of thing you are seeing. >>>> >>>> Also verify those varactor diodes are the proper type and in the right >>>> places. Soldering issues are typically the leading cause of problems, >> so >>>> check that also. If all looks right to you, you may want to signal >> trace >>>> through that selection circuit to verify the proper relays and active >> for >>>> the bands not working. There is a relay table in Appendix B that shows >> you >>>> which relays are active for each band. >>>> >>>> This is a brand new build, correct? >>>> >>>> 73, >>>> Dave, W8FGU >>>> >>>> >>>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> >> wrote: >>>> >>>> Thanks for your help Dave! >>>> >>>> Yes. I was able to get 6 volts on R30 by turning L30. At first the >> voltage >>>> was too high >>>> so I adjusted the turns on T5 by spreading the red windings further >> apart. >>>> Then I >>>> was able to get to 6 volts. >>>> >>>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>>> The reading is 8912.22 >>>> >>>> 73 Keith N8CEP >>>> >>>> >>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> >> wrote: >>>> >>>>> Hi Keith, >>>>> >>>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring >> the >>>>> voltage down or up by moving the windings on T5? >>>>> >>>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>>> know what the reading is. I'm just looking for a couple of clues >> before >>>>> we proceed. >>>>> >>>>> 73, >>>>> Dave, W8FGU >>>>> >>>>> >>>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> >> wrote: >>>>> >>>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>>> windings >>>>>> and obtained 6 volts at the left end of R30. I then went on to the >> chart >>>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>>> readings >>>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on >> 30,20,17 >>>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>>> >>>>>> I have checked the solder connections of T5 and the value of C72 >> (271). >>>>> The >>>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also >> went >>>>>> over the solder connections of K13, K14 and K15. >>>>>> >>>>>> Now I'm stuck. Any help will be appreciated. >>>>>> >>>>>> Keioth Hamilton N8CEP >>>>>> ______________________________________________________________ >>>>>> Elecraft mailing list >>>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>>> Post: mailto:[hidden email] >>>>>> >>>>>> This list hosted by: http://www.qsl.net >>>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>>> Message delivered to [hidden email] >>>>> >>>>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> > > > ------------------------------ > > Message: 7 > Date: Mon, 13 Jul 2020 22:52:20 -0700 > From: John <[hidden email]> > To: [hidden email] > Subject: [Elecraft] K3 very slow to reach dialed rf output > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8; format=flowed > > > When I dial up, or down rf output, it takes in excess of 30 seconds > > to reach the output level, which is much lower than requested. > > 3 "bars" on the rf meter.? That looks to be 20 to 25 watts. > > If I readjust the level, up or down, it takes another 30+ > > seconds and it will not go over 3 "bars". > > Anyone offer any suggestions? > > Thanks. > > 73. > > John. > > ve7day. > > > > > > ------------------------------ > > Message: 8 > Date: Tue, 14 Jul 2020 06:26:00 -0000 > From: "Doug Turnbull" <[hidden email]> > To: "'Dauer, Edward'" <[hidden email]>, <[hidden email]>, > "'Victor Rosenthal 4X6GP'" <[hidden email]> > Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs > Message-ID: <007201d659a7$a5099f10$ef1cdd30$@net1.ie> > Content-Type: text/plain; charset="us-ascii" > > Dear Friends, > Nor are SSB, RTTY and PSK the same as CW but they all serve a purpose. > Any technology which allows one to work weaker signals with lower power is > going to make DXCC easier. Even using CW it is infinitely easier to work > DXCC on multiple bands these days than back in the fifties, well maybe I > will make an exception for the 1958 era. There are so many aids and > radios are better. This is a technological hobby and now the guy with the > apartment and balcony might actually work DXCC. Viva engineering. > 73 Doug EI2CN > > -----Original Message----- > From: [hidden email] <[hidden email]> On > Behalf Of Dauer, Edward > Sent: Monday 13 July 2020 15:39 > To: [hidden email]; Victor Rosenthal 4X6GP <[hidden email]> > Subject: [Elecraft] "On Second Thought, I'll Take The Stairs > > I agree fully with Victor; though the difference may be even simpler: > > Making a QSO using CW is a ham doing something with a radio. Making a QSO > with FT8 is a radio doing something for a ham. > > Neither is better or worse; but they are different. > > Ted, KN1CBR > > ------------------------------ > > Message: 8 > Date: Mon, 13 Jul 2020 10:41:41 +0300 > From: Victor Rosenthal 4X6GP <[hidden email]> > To: [hidden email] > Subject: Re: [Elecraft] FT8 - was "On Second Thought, I'll Take The > Stairs" > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8; format=flowed > > For me, it's simple. > > When I make a CW contact, even if its total content is "ENN TU", I am > connected to history, to Jack Phillips on the Titanic, to all of the > military traffic men and airborne radio operators of WWII, to the operators > on the merchant ships on the high seas and the Great Lakes, and to all the > hams of the past, even Mr. Marconi, the first ham. > > I like hearing the propagation change with my own ears and struggling to > capture an ESP-level call. I like the feel of the key and the sound of the > code. I like the idea that there is another person like me at the other end > with his or her hand on a key. > > I consider myself extremely lucky to have caught the bug at a young age and > developed the skill needed to make CW as transparent to me as my mother > tongue. I see how hard it is for those who begin to learn at middle age or > older. They shouldn't give up -- it's worth it. > > 73, > Victor, 4X6GP > Rehovot, Israel > Formerly K2VCO > CWops no. 5 > https://urldefense.com/v3/__http://www.qsl.net/k2vco/__;!!NCZxaNi9jForCP_SxB > KJCA!F4lkQrp7vnWsJyPT-T7iUPs1Sk1a79YI92FbY7WOC4FPuQvWxE1lsChUamJuUgiP$ > . > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html Message > delivered to [hidden email] > > > > ------------------------------ > > Message: 9 > Date: Mon, 13 Jul 2020 23:29:41 -0700 (MST) > From: dl2ki <[hidden email]> > To: [hidden email] > Subject: [Elecraft] Elecraft K2 CW key shaping > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=us-ascii > > Hi, > > since someone told me that there is a small "chirp" in my K2-CW signal, I > would like to check the signal visually. > > How can I display the CW Key envelope as shown in the document "Elecraft K2 > Keying Modification Instructions", page 1. > > An oscilloscope "Tektronix 2465A" is at my disposal, but I have little > experience with measuring instruments, since I only use them occasionally. > > Thank you and 73 > Wolfgang > DL2KI > > > > > -- > Sent from: http://elecraft.365791.n2.nabble.com/ > > > ------------------------------ > > Message: 10 > Date: Tue, 14 Jul 2020 11:00:04 +0300 > From: Victor Rosenthal 4X6GP <[hidden email]> > To: [hidden email] > Subject: Re: [Elecraft] Elecraft K2 CW key shaping > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8; format=flowed > > A chirp can't be seen visually on an oscilloscope (well, maybe on a > panadpter or spectrum analyzer if it is a very big one). > > A chirp is a change in frequency of the transmitted signal. It is not > the same as a click, which is a wide signal caused by too-short rise and > fall times of the keyed envelope, or a badly shaped envelope. You can > see the envelope shape on an oscilloscope. But the change in frequency > caused by a chirp is very small in comparison with the frequency of the > signal. > > The way to detect a chirp is to listen to the transmitted signal on a > second receiver. Your ear is very sensitive to changes in pitch. > > 73, > Victor, 4X6GP > Rehovot, Israel > Formerly K2VCO > CWops no. 5 > http://www.qsl.net/k2vco/ > . >> On 14/07/2020 9:29, dl2ki wrote: >> Hi, >> >> since someone told me that there is a small "chirp" in my K2-CW signal, I >> would like to check the signal visually. >> >> How can I display the CW Key envelope as shown in the document "Elecraft K2 >> Keying Modification Instructions", page 1. >> >> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >> experience with measuring instruments, since I only use them occasionally. >> >> Thank you and 73 >> Wolfgang >> DL2KI >> >> >> >> >> -- >> Sent from: http://elecraft.365791.n2.nabble.com/ >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] >> > > > ------------------------------ > > Message: 11 > Date: Tue, 14 Jul 2020 18:15:22 +1000 > From: Matt Maguire <[hidden email]> > To: Victor Rosenthal 4X6GP <[hidden email]> > Cc: [hidden email] > Subject: Re: [Elecraft] Elecraft K2 CW key shaping > Message-ID: > <[hidden email]> > Content-Type: text/plain; charset="UTF-8" > > Generally a chirp would be due to an unstable power supply, resistance in > the fuse holder, etc.. It can also be cause by poor decoupling/loading of > the oscillator circuit, but in the case of a well-designed circuit like the > K2, this would normally only arise with misplaced components or poor > connections. > > On Tue, 14 Jul 2020 at 18:01, Victor Rosenthal 4X6GP <[hidden email]> > wrote: > >> A chirp can't be seen visually on an oscilloscope (well, maybe on a >> panadpter or spectrum analyzer if it is a very big one). >> >> A chirp is a change in frequency of the transmitted signal. It is not >> the same as a click, which is a wide signal caused by too-short rise and >> fall times of the keyed envelope, or a badly shaped envelope. You can >> see the envelope shape on an oscilloscope. But the change in frequency >> caused by a chirp is very small in comparison with the frequency of the >> signal. >> >> The way to detect a chirp is to listen to the transmitted signal on a >> second receiver. Your ear is very sensitive to changes in pitch. >> >> 73, >> Victor, 4X6GP >> Rehovot, Israel >> Formerly K2VCO >> CWops no. 5 >> http://www.qsl.net/k2vco/ >> . >>> On 14/07/2020 9:29, dl2ki wrote: >>> Hi, >>> >>> since someone told me that there is a small "chirp" in my K2-CW signal, I >>> would like to check the signal visually. >>> >>> How can I display the CW Key envelope as shown in the document "Elecraft >> K2 >>> Keying Modification Instructions", page 1. >>> >>> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >>> experience with measuring instruments, since I only use them >> occasionally. >>> >>> Thank you and 73 >>> Wolfgang >>> DL2KI >>> >>> >>> >>> >>> -- >>> Sent from: http://elecraft.365791.n2.nabble.com/ >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >>> >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] >> > > > ------------------------------ > > Message: 12 > Date: Tue, 14 Jul 2020 08:45:02 -0400 > From: Rich NE1EE <[hidden email]> > To: [hidden email] > Subject: Re: [Elecraft] Elecraft K2 CW key shaping #chirp #click > Message-ID: <[hidden email]> > Content-Type: text/plain; charset="UTF-8" > > I don't have any experience with chirps, but I can add this bit. > > If you can hear the change, then the change can be seen on an FFT. At least that would give a sense of whether the shift is up or down, if it is difficult to tell by listening. An FFT could also be applied to the RF, but, as Victor mentioned, the shift is small wrt the TX freq. It is NOT small wrt the decoded audio, however, which is why it was reported. So an FFT may well find it. There are different ways to get that analysis, and might not be worth the effort. One method would be to use a modern scope with FFT; another, a software scope such as the Zeitnitz scope; another might be fldigi. In the last two cases, you'd have to pipe the audio...that is the RX decoded audio...into the audio line in on a computer. > > But you still have to find out why...so maybe this FFT business isn't worth the effort...because you still then have to find the /cause/, even though you now have a pretty good idea where to look. > >> On 2020-07-14 18:15:+1000, you wrote: >> Generally a chirp would be due to an unstable power supply, resistance in >> the fuse holder, etc.. It can also be cause by poor decoupling/loading of >> the oscillator circuit, but in the case of a well-designed circuit like the >> K2, this would normally only arise with misplaced components or poor >> connections. >> >> On Tue, 14 Jul 2020 at 18:01, Victor Rosenthal 4X6GP <[hidden email]> >> wrote: >> >>> A chirp can't be seen visually on an oscilloscope (well, maybe on a > panadpter or spectrum analyzer if it is a very big one). >>> >>> A chirp is a change in frequency of the transmitted signal. It is not > the same as a click, which is a wide signal caused by too-short rise and > fall times of the keyed envelope, or a badly shaped envelope. You can > see the envelope shape on an oscilloscope. But the change in frequency > caused by a chirp is very small in comparison with the frequency of the > signal. >>> >>> The way to detect a chirp is to listen to the transmitted signal on a > second receiver. Your ear is very sensitive to changes in pitch. >>> >>> 73, >>> Victor, 4X6GP >>> Rehovot, Israel > > > ~R~ > 72/73 de Rich NE1EE > On the banks of the Piscataqua > > > > ------------------------------ > > Message: 13 > Date: Tue, 14 Jul 2020 07:18:48 -0600 > From: David Herring <[hidden email]> > To: John <[hidden email]> > Cc: [hidden email] > Subject: Re: [Elecraft] K3 very slow to reach dialed rf output > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8 > > Sounds like your audio level it set too low. > Try adjusting that up. Don?t quote me, but if memory serves that has to be 4 bars with the 5th flickering. > A search through the archives will find that addressed many times. > Audio too low makes the K3 ?power hunt? which is what it sounds like yours is doing. > > 73, > David - N5DCH > > > >> On Jul 13, 2020, at 11:52 PM, John <[hidden email]> wrote: >> >> >> When I dial up, or down rf output, it takes in excess of 30 seconds >> >> to reach the output level, which is much lower than requested. >> >> 3 "bars" on the rf meter. That looks to be 20 to 25 watts. >> >> If I readjust the level, up or down, it takes another 30+ >> >> seconds and it will not go over 3 "bars". >> >> Anyone offer any suggestions? >> >> Thanks. >> >> 73. >> >> John. >> >> ve7day. >> >> >> >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > > > ------------------------------ > > Message: 14 > Date: Tue, 14 Jul 2020 10:14:18 -0400 > From: w4sc <[hidden email]> > To: "[hidden email]" <[hidden email]>, > "[hidden email]" <[hidden email]> > Subject: Re: [Elecraft] [K3] Sub receiver intermittant failures > Message-ID: <[hidden email]> > Content-Type: text/plain; charset="utf-8" > > Ray > > If you have KSYN3A synthesizers installed, check for the following mod. > > Ref: KSYN3A Synthesized Installation Instructions pp 5 > > https://ftp.elecraft.com/K3S/Manuals%20Downloads/E740257%20KSYN3A%20Installation%20Rev%20A6.pdf > > KREF3 Output Level Modification > https://ftp.elecraft.com/K3/Mod%20Notes%20Alerts/E740278%20KREF3%20Output%20Level%20Modification.pdf > > Ben W4SC > > Sent from Mail for Windows 10 > > > > ------------------------------ > > Message: 15 > Date: Tue, 14 Jul 2020 07:55:42 -0700 > From: John <[hidden email]> > To: David Herring <[hidden email]> > Cc: [hidden email] > Subject: Re: [Elecraft] K3 very slow to reach dialed rf output > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Thanks to all who had suggestions. > > Windows had made an update and changed audio settings. > > Problem solved. > > 73. > > John. > > ve7day. > > >> On 14/07/2020 6:18 a.m., David Herring wrote: >> Sounds like your audio level it set too low. >> Try adjusting that up. Don?t quote me, but if memory serves that has to be 4 bars with the 5th flickering. >> A search through the archives will find that addressed many times. >> Audio too low makes the K3 ?power hunt? which is what it sounds like yours is doing. >> >> 73, >> David - N5DCH >> >> >> >>>> On Jul 13, 2020, at 11:52 PM, John <[hidden email]> wrote: >>> >>> >>> When I dial up, or down rf output, it takes in excess of 30 seconds >>> >>> to reach the output level, which is much lower than requested. >>> >>> 3 "bars" on the rf meter. That looks to be 20 to 25 watts. >>> >>> If I readjust the level, up or down, it takes another 30+ >>> >>> seconds and it will not go over 3 "bars". >>> >>> Anyone offer any suggestions? >>> >>> Thanks. >>> >>> 73. >>> >>> John. >>> >>> ve7day. >>> >>> >>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] > > > ------------------------------ > > Message: 16 > Date: Tue, 14 Jul 2020 17:23:44 +0200 > From: Steef PA2A <[hidden email]> > To: [hidden email] > Subject: [Elecraft] Replace backup battery CR2032 in a K3 > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi, > > has anyone already changed the CR2032 backup battery in a K3? Under the > carton cover the battery has started to oxydize but the Voltage is still > 3.06 Volts after twelve years. I guess an external 3 Volts source should > be applied to save all settings during the replacement. > > 73s Steef PA2A, K3 #1184 > > > ------------------------------ > > Message: 17 > Date: Tue, 14 Jul 2020 11:39:39 -0400 > From: Grant Youngman <[hidden email]> > To: [hidden email] > Cc: Elecraft Refl <[hidden email]> > Subject: Re: [Elecraft] Replace backup battery CR2032 in a K3 > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8 > > The battery supports the real time clock only. You won?t lose any other settings if you replace it. > > Grant NQ5T > >> On Jul 14, 2020, at 11:23 AM, Steef PA2A <[hidden email]> wrote: >> >> Hi, >> >> has anyone already changed the CR2032 backup battery in a K3? Under the carton cover the battery has started to oxydize but the Voltage is still 3.06 Volts after twelve years. I guess an external 3 Volts source should be applied to save all settings during the replacement. >> >> 73s Steef PA2A, K3 #1184 >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > > > ------------------------------ > > Message: 18 > Date: Tue, 14 Jul 2020 09:27:06 -0700 > From: Jim Brown <[hidden email]> > To: [hidden email] > Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs > Message-ID: > <[hidden email]> > Content-Type: text/plain; charset=utf-8; format=flowed > >> On 7/13/2020 11:26 PM, Doug Turnbull wrote: >> Even using CW it is infinitely easier to work >> DXCC on multiple bands these days than back in the fifties, well maybe I >> will make an exception for the 1958 era. > > Except that noise levels have escalated by 20 dB since that era. > > 73, Jim K9YC > > > ------------------------------ > > Message: 19 > Date: Tue, 14 Jul 2020 11:53:08 -0500 > From: Tony Estep <[hidden email]> > To: Elecraft <[hidden email]> > Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs > Message-ID: > <CACHwrmM3o3dCL=[hidden email]> > Content-Type: text/plain; charset="UTF-8" > >> >> >> ...Even using CW it is infinitely easier to work >> DXCC on multiple bands these days than back in the fifties, well maybe I >> will make an exception for the 1958 era.... >> > ================= > Ha ha, yep. I worked DXCC as a Novice in 1957-58, all on 15 CW. It's true > that signals were popping in from all over the world at the time. But the > level and type of activity were completely different, of course. I worked > many countries still deemed to be rare via QSOs with local hams (e.g. > Johnston Island) or visiting scientists (e.g. Amsterdam Island), but only a > couple via DXpeditions (e.g. Navassa). Often you'd have an exchange of name > and qth, even with rare DX when others were waiting. You found DX by tuning > and listening, and most QSLing was via direct mail. A different world. > Now with clusters and micro-QSOs (5nn tu) you can knock off DXCC within 24 > hours during a contest. Which is more fun? I dunno. Either way, hearing > your call come back from the other edge of the world can give a little jolt > of adrenaline, no matter how many times you've done it. I don't get any > jolt seeing my call on the FT8 scroll. > > 73, > Tony KT0NY > > > ------------------------------ > > Message: 20 > Date: Tue, 14 Jul 2020 14:26:36 -0400 > From: Nr4c <[hidden email]> > To: [hidden email] > Cc: [hidden email] > Subject: Re: [Elecraft] Replace backup battery CR2032 in a K3 > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8 > > Don?t get too excited. I?m told it only keeps the clock running. All settings are in non-volatile memory. > > Sent from my iPhone > ...nr4c. bill > > >> On Jul 14, 2020, at 11:25 AM, Steef PA2A <[hidden email]> wrote: >> >> ?Hi, >> >> has anyone already changed the CR2032 backup battery in a K3? Under the carton cover the battery has started to oxydize but the Voltage is still 3.06 Volts after twelve years. I guess an external 3 Volts source should be applied to save all settings during the replacement. >> >> 73s Steef PA2A, K3 #1184 >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > > > ------------------------------ > > _______________________________________________ > Elecraft mailing list > Post to: [hidden email] > http://mailman.qth.net/mailman/listinfo/elecraft > You must be a subscriber to post. > Elecraft web page: http://www.elecraft.com > > End of Elecraft Digest, Vol 195, Issue 17 > ***************************************** Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
I am usingga Raspberry Pi on my network to monitor and control the KPA1500 remotely. It also allows rotor control and AC power control turn turn various equipment on & off. This is accessible from any web browser, local or remote including smartphones. Definitely helps running remote.
In the shack I run it on my iPad. A picture of the dashboard can be seen at the link below. It runs on a gui program,ing software on th e Pi called Node Red. We nave a groups.io group https://groups.io/g/nodered-hamradio It is open to all hams and we have flows supporting various ancillary ham equipment. I am currently writing a flow for the W2 wattmeter. Dave wo2x Sent from my iPad > On Jul 14, 2020, at 6:20 PM, Hunsdon Cary III <[hidden email]> wrote: > > Perhaps KV5J can come up with an amplifier monitor for the KPA-1500, too? Hope so! > K4TM > > Sent from Clovelly Cottage II, home of amateur radio station K4TM and the most creative Sue Cary, in the foothills of the beautiful Blue Ridge mountains of Virginia. > >> On Jul 14, 2020, at 2:29 PM, [hidden email] wrote: >> >> Send Elecraft mailing list submissions to >> [hidden email] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://mailman.qth.net/mailman/listinfo/elecraft >> or, via email, send a message with subject or body 'help' to >> [hidden email] >> >> You can reach the person managing the list at >> [hidden email] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Elecraft digest..." >> >> >> Today's Topics: >> >> 1. Very pleased with KV5J Digital Display Unit for the Elecraft >> KPA500 (Macy monkeys) >> 2. Fwd: Re[2]: K2 7747 VCO alignment problem (Keith Hamilton) >> 3. Re: FT8 - was "On Second Thought, I'll Take The Stairs" >> (Robert Hand) >> 4. Re: Fwd: Re[2]: K2 7747 VCO alignment problem (Dave Van Wallaghen) >> 5. Re: "On second thought, I'll take the stairs." (Kurt Pawlikowski) >> 6. Re: Fwd: Re[2]: K2 7747 VCO alignment problem (Keith Hamilton) >> 7. K3 very slow to reach dialed rf output (John) >> 8. Re: "On Second Thought, I'll Take The Stairs (Doug Turnbull) >> 9. Elecraft K2 CW key shaping (dl2ki) >> 10. Re: Elecraft K2 CW key shaping (Victor Rosenthal 4X6GP) >> 11. Re: Elecraft K2 CW key shaping (Matt Maguire) >> 12. Re: Elecraft K2 CW key shaping #chirp #click (Rich NE1EE) >> 13. Re: K3 very slow to reach dialed rf output (David Herring) >> 14. Re: [K3] Sub receiver intermittant failures (w4sc) >> 15. Re: K3 very slow to reach dialed rf output (John) >> 16. Replace backup battery CR2032 in a K3 (Steef PA2A) >> 17. Re: Replace backup battery CR2032 in a K3 (Grant Youngman) >> 18. Re: "On Second Thought, I'll Take The Stairs (Jim Brown) >> 19. Re: "On Second Thought, I'll Take The Stairs (Tony Estep) >> 20. Re: Replace backup battery CR2032 in a K3 (Nr4c) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 13 Jul 2020 17:05:31 -0700 >> From: Macy monkeys <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Very pleased with KV5J Digital Display Unit for >> the Elecraft KPA500 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=us-ascii >> >> >> I just finished hooking up the remote KV5J DDU for my KPA500. It arrived today via USPS extremely well packed. Hook up was a snap. The unit does exactly what Keith says it does. And it looks terrific! The display is not too bright, not too dim. Perfect! It is very professional looking in a stout metal housing. Keith was quick to answer my emails. >> >> Very pleased! I have no connection to Keith or his products other than being a satisfied customer. >> >> John K7FD >> >> >>>> On Jul 13, 2020, at 3:04 PM, Macy monkeys <[hidden email]> wrote: >>> >>> I purchased it exactly for those reasons; my KPA500 is on a shelf under my operating desk. The DDU will enable me to see what I can't easily see now. Perfect solution. >>> >>> And yes, my DDU arrived today and I will soon give it a shakedown cruise... >>> >>> John K7FD >>> >>>>> On Jul 13, 2020, at 12:58 PM, Keith Ennis via Elecraft <[hidden email]> wrote: >>>> >>>> Andy, >>>> >>>> It's design was not to replace the KPA500 utility if that is what you want >>>> to use. It was designed to show the 5 most often used readings from the >>>> front panel that can only be seen one at a time. >>>> >>>> Plus it does not use any PC resources. Monitor space is limited to most >>>> operators. Same with com ports. >>>> >>>> Place the KPA500 wherever you want and place the DDU next to your radio. >>>> Saves on heat, noise and desktop space. >>>> >>>> Thanks for your input.73 >>>> >>>> Keith,KV5J >>>> >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Mon, 13 Jul 2020 21:34:03 -0400 >> From: Keith Hamilton <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> Message-ID: >> <[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> ---------- Forwarded message --------- >> From: Keith Hamilton <[hidden email]> >> Date: Mon, Jul 13, 2020 at 9:19 PM >> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >> To: Dave Van Wallaghen <[hidden email]> >> >> >> Dave >> >> Yes the frequency changes when turning the VFO knob when measuring with CAL >> FCTR on TP1. >> >> I have checked the markings on C71, C72, C73, and C74 (C75 is not installed >> yet). They are >> all correct and I resoldered them to be sure. >> >> I am beginning to think I might have a bad relay K13, K14 or K15. My good >> bands are 80,40 and >> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the relay >> table in appendix B >> I am not sure which relay could be bad. How can I test them? Should I try >> to replace them? >> 73, >> Keith N8CEP >> >> >>>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> wrote: >>> >>> Ok Keith, just to make sure things are where we want on the bands that >>> seem to work, does the frequency change when turning the VFO knob when >>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>> >>> For the bands that are locked at 8.28v, that is the max output from the >>> integrator circuit (U6B). This means that there is no lock between the PLL >>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to drive the >>> varactors to provide more capacitance to the VCO circuit. The most likely >>> cause will be a misplaced capacitor in the VCO range selector (C71 - C75) >>> or a problem in the VCO circuit itself. But because this may be band >>> dependent, I would look first in that range selection circuit. Verify that >>> those caps are the proper values. They are easily misread and will cause >>> the type of thing you are seeing. >>> >>> Also verify those varactor diodes are the proper type and in the right >>> places. Soldering issues are typically the leading cause of problems, so >>> check that also. If all looks right to you, you may want to signal trace >>> through that selection circuit to verify the proper relays and active for >>> the bands not working. There is a relay table in Appendix B that shows you >>> which relays are active for each band. >>> >>> This is a brand new build, correct? >>> >>> 73, >>> Dave, W8FGU >>> >>> >>>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> wrote: >>> >>> Thanks for your help Dave! >>> >>> Yes. I was able to get 6 volts on R30 by turning L30. At first the voltage >>> was too high >>> so I adjusted the turns on T5 by spreading the red windings further apart. >>> Then I >>> was able to get to 6 volts. >>> >>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>> The reading is 8912.22 >>> >>> 73 Keith N8CEP >>> >>> >>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> wrote: >>>> >>>> Hi Keith, >>>> >>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring the >>>> voltage down or up by moving the windings on T5? >>>> >>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>> know what the reading is. I'm just looking for a couple of clues before >>>> we proceed. >>>> >>>> 73, >>>> Dave, W8FGU >>>> >>>> >>>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> wrote: >>>> >>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>> windings >>>>> and obtained 6 volts at the left end of R30. I then went on to the chart >>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>> readings >>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on 30,20,17 >>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>> >>>>> I have checked the solder connections of T5 and the value of C72 (271). >>>> The >>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also went >>>>> over the solder connections of K13, K14 and K15. >>>>> >>>>> Now I'm stuck. Any help will be appreciated. >>>>> >>>>> Keioth Hamilton N8CEP >>>>> ______________________________________________________________ >>>>> Elecraft mailing list >>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>> Post: mailto:[hidden email] >>>>> >>>>> This list hosted by: http://www.qsl.net >>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>> Message delivered to [hidden email] >>>> >>>> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Tue, 14 Jul 2020 01:48:37 +0000 >> From: Robert Hand <[hidden email]> >> To: Victor Rosenthal 4X6GP <[hidden email]> >> Cc: "[hidden email]" <[hidden email]>, >> "[hidden email]" <[hidden email]> >> Subject: Re: [Elecraft] FT8 - was "On Second Thought, I'll Take The >> Stairs" >> Message-ID: >> <[hidden email]> >> >> Content-Type: text/plain; charset="utf-8" >> >> I still say, ?appliance operator ? >> >> Sent from my iPhone >> >>>> On Jul 13, 2020, at 3:36 PM, Victor Rosenthal 4X6GP <[hidden email]> wrote: >>> >>> ?I didn't notice myself "denigrating" anything or "talking down" to anyone. I explained why I like CW, even though other modes have their own advantages. >>> >>> Regarding "increasing knowledge" and "innovating," I suspect that 90% of the guys pointing and clicking their way to DXCC with K1JT's code couldn't explain how it works. >>> >>> 73, >>> Victor, 4X6GP >>> Rehovot, Israel >>> Formerly K2VCO >>> CWops no. 5 >>> http://www.qsl.net/k2vco/ >>> . >>>>> On 13/07/2020 23:11, Jim Rhodes wrote: >>>> Connecting to history and making history are not the same thing. Doing things the same way they were done a hundred years ago may make a "connection" for you. But hams are supposed to innovate, invent and increase the knowledge. So you buy or build equipment with way more ability than to send simple CW, so you can do simple CW? Yes, CW is great stuff, but it sure isn't innovative, nor does in increase the knowledge of communication. As a group we should encourage others to explore new communications systems, not denigrate them as "not REAL HAM RADIO". Some of you people should be ashamed of yourselves for your attitudes. We do not want Amateur Radio to die with our generation, so we should encourage new folks to do new things, not talk down to them because they don't choose to spend 99% of their operating time pounding brass. They don't give you static about taking up bandwidth with your ancient operating mode, why hassle them because they can make Qs below the noise leve >> l. Oh yes, my DXCC certificate says "Mixed" on it. I quit counting when I got that. >>>>> On Mon, Jul 13, 2020, 03:25 Victor Rosenthal 4X6GP <[hidden email] <mailto:[hidden email]>> wrote: >>>> Actually, I'm building a regenerative receiver now. I have to use JFETs >>>> because I got rid of all my tube stuff due to lack of room. But of >>>> course I will continue to benefit from the DSP in my K3, and its keyer >>>> (although I have a bug that I use once in a while). >>>> But those things don't take away the connection to history, they >>>> make it >>>> better. The point for me isn't to use the same gear as they did in >>>> 1912, >>>> but to enter the Morse space as they did. If I can do it with equipment >>>> that is more stable and effective, so much the better. >>>> After all, a modern sailboat is very much more sophisticated than an >>>> old >>>> one, but sailing is still sailing. >>>> 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:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> ------------------------------ >> >> Message: 4 >> Date: Tue, 14 Jul 2020 02:35:36 +0000 >> From: "Dave Van Wallaghen" <[hidden email]> >> To: "Keith Hamilton" <[hidden email]>, [hidden email] >> Subject: Re: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> Message-ID: <em385dd5fe-747a-45c7-91aa-6be7eb9502cb@desktop-lqvflms> >> Content-Type: text/plain; format=flowed; charset=utf-8 >> >> Keith, >> >> I saw Don respond to this and he is right that K15 would be the common >> denominator if not for 15m. You can check to see if the coils are intact >> if you measure the resistance between pins 1 and 10 for each. It should >> be around 230 ohms or so. If you find one open or well away from that >> resistance, then it would indicate a bad coil on that relay. >> >> You can also measure the intended path through the relays for each band >> and make sure there are no unintended paths. If you can read the >> schematic, it shows the path with each relay in it's reset state. You >> would need to consult the table in Appendix B to see which relay(s) are >> active for a respective band and you can then measure the continuity of >> the intended path. You should also check any unintended paths which >> could indicate a problem. >> >> As Don stated, this is not a fun problem to find and will take some good >> debugging skills. So far, everything you've indicated seems to suggest >> the PLL oscillator and VCO circuits are working properly, but the range >> selection area is not producing the proper capacitance to allow the VCO >> to produce the proper frequency on those bands you indicated. >> >> If reading the schematic is a problem, let us know and I am sure between >> Don and myself, we can give you some step by step instructions for >> tracing through this problem. >> >> 73, >> Dave W8FGU >> >> ------ Original Message ------ >> From: "Keith Hamilton" <[hidden email]> >> To: [hidden email] >> Sent: 7/13/2020 9:34:03 PM >> Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> >>> ---------- Forwarded message --------- >>> From: Keith Hamilton <[hidden email]> >>> Date: Mon, Jul 13, 2020 at 9:19 PM >>> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >>> To: Dave Van Wallaghen <[hidden email]> >>> >>> >>> Dave >>> >>> Yes the frequency changes when turning the VFO knob when measuring with CAL >>> FCTR on TP1. >>> >>> I have checked the markings on C71, C72, C73, and C74 (C75 is not installed >>> yet). They are >>> all correct and I resoldered them to be sure. >>> >>> I am beginning to think I might have a bad relay K13, K14 or K15. My good >>> bands are 80,40 and >>> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the relay >>> table in appendix B >>> I am not sure which relay could be bad. How can I test them? Should I try >>> to replace them? >>> 73, >>> Keith N8CEP >>> >>> >>>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> wrote: >>>> >>>> Ok Keith, just to make sure things are where we want on the bands that >>>> seem to work, does the frequency change when turning the VFO knob when >>>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>>> >>>> For the bands that are locked at 8.28v, that is the max output from the >>>> integrator circuit (U6B). This means that there is no lock between the PLL >>>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to drive the >>>> varactors to provide more capacitance to the VCO circuit. The most likely >>>> cause will be a misplaced capacitor in the VCO range selector (C71 - C75) >>>> or a problem in the VCO circuit itself. But because this may be band >>>> dependent, I would look first in that range selection circuit. Verify that >>>> those caps are the proper values. They are easily misread and will cause >>>> the type of thing you are seeing. >>>> >>>> Also verify those varactor diodes are the proper type and in the right >>>> places. Soldering issues are typically the leading cause of problems, so >>>> check that also. If all looks right to you, you may want to signal trace >>>> through that selection circuit to verify the proper relays and active for >>>> the bands not working. There is a relay table in Appendix B that shows you >>>> which relays are active for each band. >>>> >>>> This is a brand new build, correct? >>>> >>>> 73, >>>> Dave, W8FGU >>>> >>>> >>>>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> wrote: >>>> >>>> Thanks for your help Dave! >>>> >>>> Yes. I was able to get 6 volts on R30 by turning L30. At first the voltage >>>> was too high >>>> so I adjusted the turns on T5 by spreading the red windings further apart. >>>> Then I >>>> was able to get to 6 volts. >>>> >>>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>>> The reading is 8912.22 >>>> >>>> 73 Keith N8CEP >>>> >>>> >>>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> wrote: >>>> >>>>> Hi Keith, >>>>> >>>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring the >>>>> voltage down or up by moving the windings on T5? >>>>> >>>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>>> know what the reading is. I'm just looking for a couple of clues before >>>>> we proceed. >>>>> >>>>> 73, >>>>> Dave, W8FGU >>>>> >>>>> >>>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> wrote: >>>>> >>>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>>> windings >>>>>> and obtained 6 volts at the left end of R30. I then went on to the chart >>>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>>> readings >>>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on 30,20,17 >>>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>>> >>>>>> I have checked the solder connections of T5 and the value of C72 (271). >>>>> The >>>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also went >>>>>> over the solder connections of K13, K14 and K15. >>>>>> >>>>>> Now I'm stuck. Any help will be appreciated. >>>>>> >>>>>> Keioth Hamilton N8CEP >>>>>> ______________________________________________________________ >>>>>> Elecraft mailing list >>>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>>> Post: mailto:[hidden email] >>>>>> >>>>>> This list hosted by: http://www.qsl.net >>>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>>> Message delivered to [hidden email] >>>>> >>>>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> >> ------------------------------ >> >> Message: 5 >> Date: Mon, 13 Jul 2020 21:47:01 -0500 >> From: Kurt Pawlikowski <[hidden email]> >> To: Wayne Burdick <[hidden email]>, Elecraft Reflector >> <[hidden email]> >> Subject: Re: [Elecraft] "On second thought, I'll take the stairs." >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> Wayne: Would you mind if I forwarded this to our ham newsletter editor >> for reprint? Thanks! k WB9FMC >> >>>> On 7/12/2020 10:07 AM, Wayne Burdick wrote: >>> I have a friend about my age who got into amateur radio only a few years ago. Like many of us, he was enthusiastic about the technology. Intrigued with DX. >>> >>> I showed him my station; we talked endlessly about gear. Later, I helped him put up a simple wire antenna. >>> >>> Then, when his license arrived, he dove straight into FT8 and didn't look back. Within days, he'd worked all states, then DXCC. He'd bag a few rare ones over a light lunch, then pat his laptop on the back and congratulate his software app for its near-mythical ability to extract weak signals out of noise. >>> >>> Within weeks, he'd mastered everything there was to know about this glorious new hobby. >>> >>> Point. Click. >>> >>> In this new world order, those of us who took the longer, slower path to ionospheric enlightenment -- and who still occasionally enjoy making waves by hand -- often fail to explain why. >>> >>> I had failed to explain it to my friend. Even as hints of his boredom crept in, creating an opening, the best argument I'd made for trying CW was that he could do it without a computer. Coming in a weak second was the notion that CW was the original digital mode. For obvious reasons, I didn't bother with the classic argument about CW's signal-to-noise advantage over SSB. >>> >>> I had all but given up. >>> >>> Then, in a moment of delayed clarity, I decided on a different approach. I invited him to a weekday brunch. A bit of an escape. He willingly took the bait. >>> >>> On the appointed day, arriving at his workplace, I bypassed the lobby's glistening elevators and climbed the four flights of stairs to his office. I insisted we take the stairs down, too. >>> >>> "Why?" he asked. "And how'd you get up here so fast?" >>> >>> I pointed out that I always chose stairs, when possible. That's why I wasn't out of breath. We hustled down, jockeying for position, and emerged on the ground floor invigorated by the effort. >>> >>> "So, where are we going?" he asked. We'd been to every overrated twenty-dollar burger venue at least twice. >>> >>> I replied that we'd be going someplace we'd never tried. My kitchen. >>> >>> When we arrived, I put him to work chopping onions and broccoli and squeezing oranges while I whipped eggs into a froth and grated Swiss cheese. We ate our omelettes outside, in full sun and a cool breeze. >>> >>> "What's for desert?" he asked. "Isn't there a frozen yogurt place a two-minute drive from here?" >>> >>> I had something else in mind. Back in the kitchen, I handed him a water bottle, then strapped on a small pack I'd prepared earlier. >>> >>> We walked a mile or so through my neighborhood, admiring the houses' varied architecture, ending up (as planned) at a local park festooned with blackberry bushes. The most accessible branches had been picked clean, but with teamwork and persistence we were able to gather several large handfuls of fat, ripe berries, which we devoured on the spot. >>> >>> We'd been poked and scratched but didn't care. >>> >>> "Doesn't brunch usually end with champagne?" he wondered aloud, admiring his wounds. >>> >>> Not this time. I pulled out two bottles of craft beer that I'd obtained from a neighbor in trade for repairing his ancient home stereo. Carlos had spent years crafting an American pilsner to die for, sweating every detail, including iconic, hand-painted labels. >>> >>> My friend accepted the bottle, then tried in vain to remove the cap. Not a twist-off. >>> >>> "Opener?" he said. >>> >>> I handed him a small pocket knife, an antique without specialty blades. He soon discovered it could not be used to remove the cap directly. He looked at me with a bemused expression, no doubt wondering what I had up my sleeve this time. >>> >>> I pointed out that we were surrounded by white oaks, a species known for its hard wood. He got the message, smiled, and began hunting. Within seconds he'd collected a small fallen branch. I watched as he used the knife to fashion a few inches of it into a passable bottle opener. We popped the caps, toasted his new-found skill, and traded stories of our misspent youths. >>> >>> "Oh, one more thing," I said. >>> >>> I pulled a KX2 out of my pack, along with two lengths of wire. Of course he knew everything there was to know about Elecraft, and me, so he wasn't surprised when I also pulled out the rig's attachable keyer paddle. We threw one wire in the closest tree and laid the other on the ground. >>> >>> He didn't have to ask whether I'd brought a laptop. >>> >>> We listened to CW signals up and down 20 meters, which was open to Europe at the time. As he tuned in each station, I copied for him using pencil and paper. He'd learned Morse code, but only at very slow speeds. >>> >>> After making a contact, I set the internal keyer speed to 10 words per minute and dialed power output to zero, for practice purposes, then showed him how to use the paddle. He smiled as he got the hang of it. Sending the full alphabet was a challenge, but he got there. The KX2 decoded and displayed his keying, providing confirmation. >>> >>> We'd blown through his allotted lunch break by a factor of three, so it was time to go. We coiled up the antenna wires, packed up, and walked back. As I drove him back to his employer, we made plans to get together again for a weekend hike. >>> >>> I could have just dropped him off, but we went back into the lobby together. Out of habit, he stopped in front of the elevator. Then he looked up. >>> >>> "OK," he said. "I get it. This CW thing. It's slow, it's hard to do well, and it takes years of practice." >>> >>> "Like hunting for your own food, or carving your own tools," I added. >>> >>> "Or cooking from scratch. Or brewing your own beer. Building your own radio. And you use more of your senses. Not just your eyes, but your ears. Your sense of touch." >>> >>> I nodded. Listening. Feeling. That was the radio I'd grown up with. >>> >>> "Of course it's harder to work DX with CW than with FT8," I reminded him, playing devil's advocate. >>> >>> "Is that what matters, though?" he asked. >>> >>> A longer discussion for another day. >>> >>> "Your call," I said. >>> >>> He gripped my shoulder and smiled, then reached toward the elevator's glowing, ivory colored button, framed by polished brass. >>> >>> The path most taken. >>> >>> Point. Click. >>> >>> "On second thought," he said, "I'll take the stairs." >>> >>> * * * >>> >>> Wayne, >>> N6KR >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> ------------------------------ >> >> Message: 6 >> Date: Mon, 13 Jul 2020 23:00:59 -0400 >> From: Keith Hamilton <[hidden email]> >> To: Dave Van Wallaghen <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> Message-ID: >> <CAJkuCUZmuY7Ys=ypJjjEK0wt7o5ocWzVCZQL=SZkPC7E=[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> OK Dave - >> >> I will check the relays as you suggest. In troubleshooting capacitors I >> messed up >> C74. I pulled it off the board and sent a request to Elecraft for a >> replacement. >> That may solve the problem. In the meantime I will check the coils on the >> K13 to K15 >> relays and let you know what I find. >> >> I did not see Don's post. I will check it out. So I will be waiting a bit >> to fix this problem, >> >> 73 and thanks! >> Keith N8CEP >> >>>> On Mon, Jul 13, 2020 at 10:36 PM Dave Van Wallaghen <[hidden email]> wrote: >>> >>> Keith, >>> >>> I saw Don respond to this and he is right that K15 would be the common >>> denominator if not for 15m. You can check to see if the coils are intact >>> if you measure the resistance between pins 1 and 10 for each. It should >>> be around 230 ohms or so. If you find one open or well away from that >>> resistance, then it would indicate a bad coil on that relay. >>> >>> You can also measure the intended path through the relays for each band >>> and make sure there are no unintended paths. If you can read the >>> schematic, it shows the path with each relay in it's reset state. You >>> would need to consult the table in Appendix B to see which relay(s) are >>> active for a respective band and you can then measure the continuity of >>> the intended path. You should also check any unintended paths which >>> could indicate a problem. >>> >>> As Don stated, this is not a fun problem to find and will take some good >>> debugging skills. So far, everything you've indicated seems to suggest >>> the PLL oscillator and VCO circuits are working properly, but the range >>> selection area is not producing the proper capacitance to allow the VCO >>> to produce the proper frequency on those bands you indicated. >>> >>> If reading the schematic is a problem, let us know and I am sure between >>> Don and myself, we can give you some step by step instructions for >>> tracing through this problem. >>> >>> 73, >>> Dave W8FGU >>> >>> ------ Original Message ------ >>> From: "Keith Hamilton" <[hidden email]> >>> To: [hidden email] >>> Sent: 7/13/2020 9:34:03 PM >>> Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >>> >>>> ---------- Forwarded message --------- >>>> From: Keith Hamilton <[hidden email]> >>>> Date: Mon, Jul 13, 2020 at 9:19 PM >>>> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >>>> To: Dave Van Wallaghen <[hidden email]> >>>> >>>> >>>> Dave >>>> >>>> Yes the frequency changes when turning the VFO knob when measuring with >>> CAL >>>> FCTR on TP1. >>>> >>>> I have checked the markings on C71, C72, C73, and C74 (C75 is not >>> installed >>>> yet). They are >>>> all correct and I resoldered them to be sure. >>>> >>>> I am beginning to think I might have a bad relay K13, K14 or K15. My good >>>> bands are 80,40 and >>>> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the >>> relay >>>> table in appendix B >>>> I am not sure which relay could be bad. How can I test them? Should I try >>>> to replace them? >>>> 73, >>>> Keith N8CEP >>>> >>>> >>>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> >>> wrote: >>>> >>>>> Ok Keith, just to make sure things are where we want on the bands that >>>>> seem to work, does the frequency change when turning the VFO knob when >>>>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>>>> >>>>> For the bands that are locked at 8.28v, that is the max output from the >>>>> integrator circuit (U6B). This means that there is no lock between the >>> PLL >>>>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to >>> drive the >>>>> varactors to provide more capacitance to the VCO circuit. The most >>> likely >>>>> cause will be a misplaced capacitor in the VCO range selector (C71 - >>> C75) >>>>> or a problem in the VCO circuit itself. But because this may be band >>>>> dependent, I would look first in that range selection circuit. Verify >>> that >>>>> those caps are the proper values. They are easily misread and will >>> cause >>>>> the type of thing you are seeing. >>>>> >>>>> Also verify those varactor diodes are the proper type and in the right >>>>> places. Soldering issues are typically the leading cause of problems, >>> so >>>>> check that also. If all looks right to you, you may want to signal >>> trace >>>>> through that selection circuit to verify the proper relays and active >>> for >>>>> the bands not working. There is a relay table in Appendix B that shows >>> you >>>>> which relays are active for each band. >>>>> >>>>> This is a brand new build, correct? >>>>> >>>>> 73, >>>>> Dave, W8FGU >>>>> >>>>> >>>>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> >>> wrote: >>>>> >>>>> Thanks for your help Dave! >>>>> >>>>> Yes. I was able to get 6 volts on R30 by turning L30. At first the >>> voltage >>>>> was too high >>>>> so I adjusted the turns on T5 by spreading the red windings further >>> apart. >>>>> Then I >>>>> was able to get to 6 volts. >>>>> >>>>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>>>> The reading is 8912.22 >>>>> >>>>> 73 Keith N8CEP >>>>> >>>>> >>>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> >>> wrote: >>>>> >>>>>> Hi Keith, >>>>>> >>>>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring >>> the >>>>>> voltage down or up by moving the windings on T5? >>>>>> >>>>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>>>> know what the reading is. I'm just looking for a couple of clues >>> before >>>>>> we proceed. >>>>>> >>>>>> 73, >>>>>> Dave, W8FGU >>>>>> >>>>>> >>>>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> >>> wrote: >>>>>> >>>>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>>>> windings >>>>>>> and obtained 6 volts at the left end of R30. I then went on to the >>> chart >>>>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>>>> readings >>>>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on >>> 30,20,17 >>>>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>>>> >>>>>>> I have checked the solder connections of T5 and the value of C72 >>> (271). >>>>>> The >>>>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also >>> went >>>>>>> over the solder connections of K13, K14 and K15. >>>>>>> >>>>>>> Now I'm stuck. Any help will be appreciated. >>>>>>> >>>>>>> Keioth Hamilton N8CEP >>>>>>> ______________________________________________________________ >>>>>>> Elecraft mailing list >>>>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>>>> Post: mailto:[hidden email] >>>>>>> >>>>>>> This list hosted by: http://www.qsl.net >>>>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>>>> Message delivered to [hidden email] >>>>>> >>>>>> >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >>> >>> >> >> >> ------------------------------ >> >> Message: 7 >> Date: Mon, 13 Jul 2020 22:52:20 -0700 >> From: John <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] K3 very slow to reach dialed rf output >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> >> When I dial up, or down rf output, it takes in excess of 30 seconds >> >> to reach the output level, which is much lower than requested. >> >> 3 "bars" on the rf meter.? That looks to be 20 to 25 watts. >> >> If I readjust the level, up or down, it takes another 30+ >> >> seconds and it will not go over 3 "bars". >> >> Anyone offer any suggestions? >> >> Thanks. >> >> 73. >> >> John. >> >> ve7day. >> >> >> >> >> >> ------------------------------ >> >> Message: 8 >> Date: Tue, 14 Jul 2020 06:26:00 -0000 >> From: "Doug Turnbull" <[hidden email]> >> To: "'Dauer, Edward'" <[hidden email]>, <[hidden email]>, >> "'Victor Rosenthal 4X6GP'" <[hidden email]> >> Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs >> Message-ID: <007201d659a7$a5099f10$ef1cdd30$@net1.ie> >> Content-Type: text/plain; charset="us-ascii" >> >> Dear Friends, >> Nor are SSB, RTTY and PSK the same as CW but they all serve a purpose. >> Any technology which allows one to work weaker signals with lower power is >> going to make DXCC easier. Even using CW it is infinitely easier to work >> DXCC on multiple bands these days than back in the fifties, well maybe I >> will make an exception for the 1958 era. There are so many aids and >> radios are better. This is a technological hobby and now the guy with the >> apartment and balcony might actually work DXCC. Viva engineering. >> 73 Doug EI2CN >> >> -----Original Message----- >> From: [hidden email] <[hidden email]> On >> Behalf Of Dauer, Edward >> Sent: Monday 13 July 2020 15:39 >> To: [hidden email]; Victor Rosenthal 4X6GP <[hidden email]> >> Subject: [Elecraft] "On Second Thought, I'll Take The Stairs >> >> I agree fully with Victor; though the difference may be even simpler: >> >> Making a QSO using CW is a ham doing something with a radio. Making a QSO >> with FT8 is a radio doing something for a ham. >> >> Neither is better or worse; but they are different. >> >> Ted, KN1CBR >> >> ------------------------------ >> >> Message: 8 >> Date: Mon, 13 Jul 2020 10:41:41 +0300 >> From: Victor Rosenthal 4X6GP <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] FT8 - was "On Second Thought, I'll Take The >> Stairs" >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> For me, it's simple. >> >> When I make a CW contact, even if its total content is "ENN TU", I am >> connected to history, to Jack Phillips on the Titanic, to all of the >> military traffic men and airborne radio operators of WWII, to the operators >> on the merchant ships on the high seas and the Great Lakes, and to all the >> hams of the past, even Mr. Marconi, the first ham. >> >> I like hearing the propagation change with my own ears and struggling to >> capture an ESP-level call. I like the feel of the key and the sound of the >> code. I like the idea that there is another person like me at the other end >> with his or her hand on a key. >> >> I consider myself extremely lucky to have caught the bug at a young age and >> developed the skill needed to make CW as transparent to me as my mother >> tongue. I see how hard it is for those who begin to learn at middle age or >> older. They shouldn't give up -- it's worth it. >> >> 73, >> Victor, 4X6GP >> Rehovot, Israel >> Formerly K2VCO >> CWops no. 5 >> https://urldefense.com/v3/__http://www.qsl.net/k2vco/__;!!NCZxaNi9jForCP_SxB >> KJCA!F4lkQrp7vnWsJyPT-T7iUPs1Sk1a79YI92FbY7WOC4FPuQvWxE1lsChUamJuUgiP$ >> . >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html Message >> delivered to [hidden email] >> >> >> >> ------------------------------ >> >> Message: 9 >> Date: Mon, 13 Jul 2020 23:29:41 -0700 (MST) >> From: dl2ki <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Elecraft K2 CW key shaping >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=us-ascii >> >> Hi, >> >> since someone told me that there is a small "chirp" in my K2-CW signal, I >> would like to check the signal visually. >> >> How can I display the CW Key envelope as shown in the document "Elecraft K2 >> Keying Modification Instructions", page 1. >> >> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >> experience with measuring instruments, since I only use them occasionally. >> >> Thank you and 73 >> Wolfgang >> DL2KI >> >> >> >> >> -- >> Sent from: http://elecraft.365791.n2.nabble.com/ >> >> >> ------------------------------ >> >> Message: 10 >> Date: Tue, 14 Jul 2020 11:00:04 +0300 >> From: Victor Rosenthal 4X6GP <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] Elecraft K2 CW key shaping >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> A chirp can't be seen visually on an oscilloscope (well, maybe on a >> panadpter or spectrum analyzer if it is a very big one). >> >> A chirp is a change in frequency of the transmitted signal. It is not >> the same as a click, which is a wide signal caused by too-short rise and >> fall times of the keyed envelope, or a badly shaped envelope. You can >> see the envelope shape on an oscilloscope. But the change in frequency >> caused by a chirp is very small in comparison with the frequency of the >> signal. >> >> The way to detect a chirp is to listen to the transmitted signal on a >> second receiver. Your ear is very sensitive to changes in pitch. >> >> 73, >> Victor, 4X6GP >> Rehovot, Israel >> Formerly K2VCO >> CWops no. 5 >> http://www.qsl.net/k2vco/ >> . >>>> On 14/07/2020 9:29, dl2ki wrote: >>> Hi, >>> >>> since someone told me that there is a small "chirp" in my K2-CW signal, I >>> would like to check the signal visually. >>> >>> How can I display the CW Key envelope as shown in the document "Elecraft K2 >>> Keying Modification Instructions", page 1. >>> >>> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >>> experience with measuring instruments, since I only use them occasionally. >>> >>> Thank you and 73 >>> Wolfgang >>> DL2KI >>> >>> >>> >>> >>> -- >>> Sent from: http://elecraft.365791.n2.nabble.com/ >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >>> >> >> >> ------------------------------ >> >> Message: 11 >> Date: Tue, 14 Jul 2020 18:15:22 +1000 >> From: Matt Maguire <[hidden email]> >> To: Victor Rosenthal 4X6GP <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] Elecraft K2 CW key shaping >> Message-ID: >> <[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> Generally a chirp would be due to an unstable power supply, resistance in >> the fuse holder, etc.. It can also be cause by poor decoupling/loading of >> the oscillator circuit, but in the case of a well-designed circuit like the >> K2, this would normally only arise with misplaced components or poor >> connections. >> >> On Tue, 14 Jul 2020 at 18:01, Victor Rosenthal 4X6GP <[hidden email]> >> wrote: >> >>> A chirp can't be seen visually on an oscilloscope (well, maybe on a >>> panadpter or spectrum analyzer if it is a very big one). >>> >>> A chirp is a change in frequency of the transmitted signal. It is not >>> the same as a click, which is a wide signal caused by too-short rise and >>> fall times of the keyed envelope, or a badly shaped envelope. You can >>> see the envelope shape on an oscilloscope. But the change in frequency >>> caused by a chirp is very small in comparison with the frequency of the >>> signal. >>> >>> The way to detect a chirp is to listen to the transmitted signal on a >>> second receiver. Your ear is very sensitive to changes in pitch. >>> >>> 73, >>> Victor, 4X6GP >>> Rehovot, Israel >>> Formerly K2VCO >>> CWops no. 5 >>> http://www.qsl.net/k2vco/ >>> . >>>> On 14/07/2020 9:29, dl2ki wrote: >>>> Hi, >>>> >>>> since someone told me that there is a small "chirp" in my K2-CW signal, I >>>> would like to check the signal visually. >>>> >>>> How can I display the CW Key envelope as shown in the document "Elecraft >>> K2 >>>> Keying Modification Instructions", page 1. >>>> >>>> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >>>> experience with measuring instruments, since I only use them >>> occasionally. >>>> >>>> Thank you and 73 >>>> Wolfgang >>>> DL2KI >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://elecraft.365791.n2.nabble.com/ >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >>>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >>> >> >> >> ------------------------------ >> >> Message: 12 >> Date: Tue, 14 Jul 2020 08:45:02 -0400 >> From: Rich NE1EE <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] Elecraft K2 CW key shaping #chirp #click >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> I don't have any experience with chirps, but I can add this bit. >> >> If you can hear the change, then the change can be seen on an FFT. At least that would give a sense of whether the shift is up or down, if it is difficult to tell by listening. An FFT could also be applied to the RF, but, as Victor mentioned, the shift is small wrt the TX freq. It is NOT small wrt the decoded audio, however, which is why it was reported. So an FFT may well find it. There are different ways to get that analysis, and might not be worth the effort. One method would be to use a modern scope with FFT; another, a software scope such as the Zeitnitz scope; another might be fldigi. In the last two cases, you'd have to pipe the audio...that is the RX decoded audio...into the audio line in on a computer. >> >> But you still have to find out why...so maybe this FFT business isn't worth the effort...because you still then have to find the /cause/, even though you now have a pretty good idea where to look. >> >>>> On 2020-07-14 18:15:+1000, you wrote: >>> Generally a chirp would be due to an unstable power supply, resistance in >>> the fuse holder, etc.. It can also be cause by poor decoupling/loading of >>> the oscillator circuit, but in the case of a well-designed circuit like the >>> K2, this would normally only arise with misplaced components or poor >>> connections. >>> >>> On Tue, 14 Jul 2020 at 18:01, Victor Rosenthal 4X6GP <[hidden email]> >>> wrote: >>> >>>> A chirp can't be seen visually on an oscilloscope (well, maybe on a > panadpter or spectrum analyzer if it is a very big one). >>>> >>>> A chirp is a change in frequency of the transmitted signal. It is not > the same as a click, which is a wide signal caused by too-short rise and > fall times of the keyed envelope, or a badly shaped envelope. You can > see the envelope shape on an oscilloscope. But the change in frequency > caused by a chirp is very small in comparison with the frequency of the > signal. >>>> >>>> The way to detect a chirp is to listen to the transmitted signal on a > second receiver. Your ear is very sensitive to changes in pitch. >>>> >>>> 73, >>>> Victor, 4X6GP >>>> Rehovot, Israel >> >> >> ~R~ >> 72/73 de Rich NE1EE >> On the banks of the Piscataqua >> >> >> >> ------------------------------ >> >> Message: 13 >> Date: Tue, 14 Jul 2020 07:18:48 -0600 >> From: David Herring <[hidden email]> >> To: John <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] K3 very slow to reach dialed rf output >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8 >> >> Sounds like your audio level it set too low. >> Try adjusting that up. Don?t quote me, but if memory serves that has to be 4 bars with the 5th flickering. >> A search through the archives will find that addressed many times. >> Audio too low makes the K3 ?power hunt? which is what it sounds like yours is doing. >> >> 73, >> David - N5DCH >> >> >> >>>> On Jul 13, 2020, at 11:52 PM, John <[hidden email]> wrote: >>> >>> >>> When I dial up, or down rf output, it takes in excess of 30 seconds >>> >>> to reach the output level, which is much lower than requested. >>> >>> 3 "bars" on the rf meter. That looks to be 20 to 25 watts. >>> >>> If I readjust the level, up or down, it takes another 30+ >>> >>> seconds and it will not go over 3 "bars". >>> >>> Anyone offer any suggestions? >>> >>> Thanks. >>> >>> 73. >>> >>> John. >>> >>> ve7day. >>> >>> >>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> >> ------------------------------ >> >> Message: 14 >> Date: Tue, 14 Jul 2020 10:14:18 -0400 >> From: w4sc <[hidden email]> >> To: "[hidden email]" <[hidden email]>, >> "[hidden email]" <[hidden email]> >> Subject: Re: [Elecraft] [K3] Sub receiver intermittant failures >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset="utf-8" >> >> Ray >> >> If you have KSYN3A synthesizers installed, check for the following mod. >> >> Ref: KSYN3A Synthesized Installation Instructions pp 5 >> >> https://ftp.elecraft.com/K3S/Manuals%20Downloads/E740257%20KSYN3A%20Installation%20Rev%20A6.pdf >> >> KREF3 Output Level Modification >> https://ftp.elecraft.com/K3/Mod%20Notes%20Alerts/E740278%20KREF3%20Output%20Level%20Modification.pdf >> >> Ben W4SC >> >> Sent from Mail for Windows 10 >> >> >> >> ------------------------------ >> >> Message: 15 >> Date: Tue, 14 Jul 2020 07:55:42 -0700 >> From: John <[hidden email]> >> To: David Herring <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] K3 very slow to reach dialed rf output >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> Thanks to all who had suggestions. >> >> Windows had made an update and changed audio settings. >> >> Problem solved. >> >> 73. >> >> John. >> >> ve7day. >> >> >>>> On 14/07/2020 6:18 a.m., David Herring wrote: >>> Sounds like your audio level it set too low. >>> Try adjusting that up. Don?t quote me, but if memory serves that has to be 4 bars with the 5th flickering. >>> A search through the archives will find that addressed many times. >>> Audio too low makes the K3 ?power hunt? which is what it sounds like yours is doing. >>> >>> 73, >>> David - N5DCH >>> >>> >>> >>>>> On Jul 13, 2020, at 11:52 PM, John <[hidden email]> wrote: >>>> >>>> >>>> When I dial up, or down rf output, it takes in excess of 30 seconds >>>> >>>> to reach the output level, which is much lower than requested. >>>> >>>> 3 "bars" on the rf meter. That looks to be 20 to 25 watts. >>>> >>>> If I readjust the level, up or down, it takes another 30+ >>>> >>>> seconds and it will not go over 3 "bars". >>>> >>>> Anyone offer any suggestions? >>>> >>>> Thanks. >>>> >>>> 73. >>>> >>>> John. >>>> >>>> ve7day. >>>> >>>> >>>> >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >> >> >> ------------------------------ >> >> Message: 16 >> Date: Tue, 14 Jul 2020 17:23:44 +0200 >> From: Steef PA2A <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Replace backup battery CR2032 in a K3 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=US-ASCII; format=flowed >> >> Hi, >> >> has anyone already changed the CR2032 backup battery in a K3? Under the >> carton cover the battery has started to oxydize but the Voltage is still >> 3.06 Volts after twelve years. I guess an external 3 Volts source should >> be applied to save all settings during the replacement. >> >> 73s Steef PA2A, K3 #1184 >> >> >> ------------------------------ >> >> Message: 17 >> Date: Tue, 14 Jul 2020 11:39:39 -0400 >> From: Grant Youngman <[hidden email]> >> To: [hidden email] >> Cc: Elecraft Refl <[hidden email]> >> Subject: Re: [Elecraft] Replace backup battery CR2032 in a K3 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8 >> >> The battery supports the real time clock only. You won?t lose any other settings if you replace it. >> >> Grant NQ5T >> >>>> On Jul 14, 2020, at 11:23 AM, Steef PA2A <[hidden email]> wrote: >>> >>> Hi, >>> >>> has anyone already changed the CR2032 backup battery in a K3? Under the carton cover the battery has started to oxydize but the Voltage is still 3.06 Volts after twelve years. I guess an external 3 Volts source should be applied to save all settings during the replacement. >>> >>> 73s Steef PA2A, K3 #1184 >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> >> ------------------------------ >> >> Message: 18 >> Date: Tue, 14 Jul 2020 09:27:06 -0700 >> From: Jim Brown <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs >> Message-ID: >> <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >>>> On 7/13/2020 11:26 PM, Doug Turnbull wrote: >>> Even using CW it is infinitely easier to work >>> DXCC on multiple bands these days than back in the fifties, well maybe I >>> will make an exception for the 1958 era. >> >> Except that noise levels have escalated by 20 dB since that era. >> >> 73, Jim K9YC >> >> >> ------------------------------ >> >> Message: 19 >> Date: Tue, 14 Jul 2020 11:53:08 -0500 >> From: Tony Estep <[hidden email]> >> To: Elecraft <[hidden email]> >> Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs >> Message-ID: >> <CACHwrmM3o3dCL=[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >>> >>> >>> ...Even using CW it is infinitely easier to work >>> DXCC on multiple bands these days than back in the fifties, well maybe I >>> will make an exception for the 1958 era.... >>> >> ================= >> Ha ha, yep. I worked DXCC as a Novice in 1957-58, all on 15 CW. It's true >> that signals were popping in from all over the world at the time. But the >> level and type of activity were completely different, of course. I worked >> many countries still deemed to be rare via QSOs with local hams (e.g. >> Johnston Island) or visiting scientists (e.g. Amsterdam Island), but only a >> couple via DXpeditions (e.g. Navassa). Often you'd have an exchange of name >> and qth, even with rare DX when others were waiting. You found DX by tuning >> and listening, and most QSLing was via direct mail. A different world. >> Now with clusters and micro-QSOs (5nn tu) you can knock off DXCC within 24 >> hours during a contest. Which is more fun? I dunno. Either way, hearing >> your call come back from the other edge of the world can give a little jolt >> of adrenaline, no matter how many times you've done it. I don't get any >> jolt seeing my call on the FT8 scroll. >> >> 73, >> Tony KT0NY >> >> >> ------------------------------ >> >> Message: 20 >> Date: Tue, 14 Jul 2020 14:26:36 -0400 >> From: Nr4c <[hidden email]> >> To: [hidden email] >> Cc: [hidden email] >> Subject: Re: [Elecraft] Replace backup battery CR2032 in a K3 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8 >> >> Don?t get too excited. I?m told it only keeps the clock running. All settings are in non-volatile memory. >> >> Sent from my iPhone >> ...nr4c. bill >> >> >>>> On Jul 14, 2020, at 11:25 AM, Steef PA2A <[hidden email]> wrote: >>> >>> ?Hi, >>> >>> has anyone already changed the CR2032 backup battery in a K3? Under the carton cover the battery has started to oxydize but the Voltage is still 3.06 Volts after twelve years. I guess an external 3 Volts source should be applied to save all settings during the replacement. >>> >>> 73s Steef PA2A, K3 #1184 >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> ------------------------------ >> >> _______________________________________________ >> Elecraft mailing list >> Post to: [hidden email] >> http://mailman.qth.net/mailman/listinfo/elecraft >> You must be a subscriber to post. >> Elecraft web page: http://www.elecraft.com >> >> End of Elecraft Digest, Vol 195, Issue 17 >> ***************************************** > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
In reply to this post by Hunsdon Cary III
Why ? I may have missed something, but my KPA-1500 seems to display all
of the same info simultaneously. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity worldwide. For spots, please use your favorite "retail" DX cluster. On 7/14/2020 6:17 PM, Hunsdon Cary III wrote: > Perhaps KV5J can come up with an amplifier monitor for the KPA-1500, too? Hope so! > K4TM > > Sent from Clovelly Cottage II, home of amateur radio station K4TM and the most creative Sue Cary, in the foothills of the beautiful Blue Ridge mountains of Virginia. > >> On Jul 14, 2020, at 2:29 PM, [hidden email] wrote: >> >> Send Elecraft mailing list submissions to >> [hidden email] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://mailman.qth.net/mailman/listinfo/elecraft >> or, via email, send a message with subject or body 'help' to >> [hidden email] >> >> You can reach the person managing the list at >> [hidden email] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Elecraft digest..." >> >> >> Today's Topics: >> >> 1. Very pleased with KV5J Digital Display Unit for the Elecraft >> KPA500 (Macy monkeys) >> 2. Fwd: Re[2]: K2 7747 VCO alignment problem (Keith Hamilton) >> 3. Re: FT8 - was "On Second Thought, I'll Take The Stairs" >> (Robert Hand) >> 4. Re: Fwd: Re[2]: K2 7747 VCO alignment problem (Dave Van Wallaghen) >> 5. Re: "On second thought, I'll take the stairs." (Kurt Pawlikowski) >> 6. Re: Fwd: Re[2]: K2 7747 VCO alignment problem (Keith Hamilton) >> 7. K3 very slow to reach dialed rf output (John) >> 8. Re: "On Second Thought, I'll Take The Stairs (Doug Turnbull) >> 9. Elecraft K2 CW key shaping (dl2ki) >> 10. Re: Elecraft K2 CW key shaping (Victor Rosenthal 4X6GP) >> 11. Re: Elecraft K2 CW key shaping (Matt Maguire) >> 12. Re: Elecraft K2 CW key shaping #chirp #click (Rich NE1EE) >> 13. Re: K3 very slow to reach dialed rf output (David Herring) >> 14. Re: [K3] Sub receiver intermittant failures (w4sc) >> 15. Re: K3 very slow to reach dialed rf output (John) >> 16. Replace backup battery CR2032 in a K3 (Steef PA2A) >> 17. Re: Replace backup battery CR2032 in a K3 (Grant Youngman) >> 18. Re: "On Second Thought, I'll Take The Stairs (Jim Brown) >> 19. Re: "On Second Thought, I'll Take The Stairs (Tony Estep) >> 20. Re: Replace backup battery CR2032 in a K3 (Nr4c) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 13 Jul 2020 17:05:31 -0700 >> From: Macy monkeys <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Very pleased with KV5J Digital Display Unit for >> the Elecraft KPA500 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=us-ascii >> >> >> I just finished hooking up the remote KV5J DDU for my KPA500. It arrived today via USPS extremely well packed. Hook up was a snap. The unit does exactly what Keith says it does. And it looks terrific! The display is not too bright, not too dim. Perfect! It is very professional looking in a stout metal housing. Keith was quick to answer my emails. >> >> Very pleased! I have no connection to Keith or his products other than being a satisfied customer. >> >> John K7FD >> >> >>> On Jul 13, 2020, at 3:04 PM, Macy monkeys <[hidden email]> wrote: >>> >>> I purchased it exactly for those reasons; my KPA500 is on a shelf under my operating desk. The DDU will enable me to see what I can't easily see now. Perfect solution. >>> >>> And yes, my DDU arrived today and I will soon give it a shakedown cruise... >>> >>> John K7FD >>> >>>>> On Jul 13, 2020, at 12:58 PM, Keith Ennis via Elecraft <[hidden email]> wrote: >>>> Andy, >>>> >>>> It's design was not to replace the KPA500 utility if that is what you want >>>> to use. It was designed to show the 5 most often used readings from the >>>> front panel that can only be seen one at a time. >>>> >>>> Plus it does not use any PC resources. Monitor space is limited to most >>>> operators. Same with com ports. >>>> >>>> Place the KPA500 wherever you want and place the DDU next to your radio. >>>> Saves on heat, noise and desktop space. >>>> >>>> Thanks for your input.73 >>>> >>>> Keith,KV5J >>>> >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> ------------------------------ >> >> Message: 2 >> Date: Mon, 13 Jul 2020 21:34:03 -0400 >> From: Keith Hamilton <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> Message-ID: >> <[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> ---------- Forwarded message --------- >> From: Keith Hamilton <[hidden email]> >> Date: Mon, Jul 13, 2020 at 9:19 PM >> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >> To: Dave Van Wallaghen <[hidden email]> >> >> >> Dave >> >> Yes the frequency changes when turning the VFO knob when measuring with CAL >> FCTR on TP1. >> >> I have checked the markings on C71, C72, C73, and C74 (C75 is not installed >> yet). They are >> all correct and I resoldered them to be sure. >> >> I am beginning to think I might have a bad relay K13, K14 or K15. My good >> bands are 80,40 and >> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the relay >> table in appendix B >> I am not sure which relay could be bad. How can I test them? Should I try >> to replace them? >> 73, >> Keith N8CEP >> >> >>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> wrote: >>> >>> Ok Keith, just to make sure things are where we want on the bands that >>> seem to work, does the frequency change when turning the VFO knob when >>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>> >>> For the bands that are locked at 8.28v, that is the max output from the >>> integrator circuit (U6B). This means that there is no lock between the PLL >>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to drive the >>> varactors to provide more capacitance to the VCO circuit. The most likely >>> cause will be a misplaced capacitor in the VCO range selector (C71 - C75) >>> or a problem in the VCO circuit itself. But because this may be band >>> dependent, I would look first in that range selection circuit. Verify that >>> those caps are the proper values. They are easily misread and will cause >>> the type of thing you are seeing. >>> >>> Also verify those varactor diodes are the proper type and in the right >>> places. Soldering issues are typically the leading cause of problems, so >>> check that also. If all looks right to you, you may want to signal trace >>> through that selection circuit to verify the proper relays and active for >>> the bands not working. There is a relay table in Appendix B that shows you >>> which relays are active for each band. >>> >>> This is a brand new build, correct? >>> >>> 73, >>> Dave, W8FGU >>> >>> >>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> wrote: >>> >>> Thanks for your help Dave! >>> >>> Yes. I was able to get 6 volts on R30 by turning L30. At first the voltage >>> was too high >>> so I adjusted the turns on T5 by spreading the red windings further apart. >>> Then I >>> was able to get to 6 volts. >>> >>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>> The reading is 8912.22 >>> >>> 73 Keith N8CEP >>> >>> >>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> wrote: >>>> >>>> Hi Keith, >>>> >>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring the >>>> voltage down or up by moving the windings on T5? >>>> >>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>> know what the reading is. I'm just looking for a couple of clues before >>>> we proceed. >>>> >>>> 73, >>>> Dave, W8FGU >>>> >>>> >>>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> wrote: >>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>> windings >>>>> and obtained 6 volts at the left end of R30. I then went on to the chart >>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>> readings >>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on 30,20,17 >>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>> >>>>> I have checked the solder connections of T5 and the value of C72 (271). >>>> The >>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also went >>>>> over the solder connections of K13, K14 and K15. >>>>> >>>>> Now I'm stuck. Any help will be appreciated. >>>>> >>>>> Keioth Hamilton N8CEP >>>>> ______________________________________________________________ >>>>> Elecraft mailing list >>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>> Post: mailto:[hidden email] >>>>> >>>>> This list hosted by: http://www.qsl.net >>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>> Message delivered to [hidden email] >>>> >> >> ------------------------------ >> >> Message: 3 >> Date: Tue, 14 Jul 2020 01:48:37 +0000 >> From: Robert Hand <[hidden email]> >> To: Victor Rosenthal 4X6GP <[hidden email]> >> Cc: "[hidden email]" <[hidden email]>, >> "[hidden email]" <[hidden email]> >> Subject: Re: [Elecraft] FT8 - was "On Second Thought, I'll Take The >> Stairs" >> Message-ID: >> <[hidden email]> >> >> Content-Type: text/plain; charset="utf-8" >> >> I still say, ?appliance operator ? >> >> Sent from my iPhone >> >>> On Jul 13, 2020, at 3:36 PM, Victor Rosenthal 4X6GP <[hidden email]> wrote: >>> >>> ?I didn't notice myself "denigrating" anything or "talking down" to anyone. I explained why I like CW, even though other modes have their own advantages. >>> >>> Regarding "increasing knowledge" and "innovating," I suspect that 90% of the guys pointing and clicking their way to DXCC with K1JT's code couldn't explain how it works. >>> >>> 73, >>> Victor, 4X6GP >>> Rehovot, Israel >>> Formerly K2VCO >>> CWops no. 5 >>> http://www.qsl.net/k2vco/ >>> . >>>>> On 13/07/2020 23:11, Jim Rhodes wrote: >>>> Connecting to history and making history are not the same thing. Doing things the same way they were done a hundred years ago may make a "connection" for you. But hams are supposed to innovate, invent and increase the knowledge. So you buy or build equipment with way more ability than to send simple CW, so you can do simple CW? Yes, CW is great stuff, but it sure isn't innovative, nor does in increase the knowledge of communication. As a group we should encourage others to explore new communications systems, not denigrate them as "not REAL HAM RADIO". Some of you people should be ashamed of yourselves for your attitudes. We do not want Amateur Radio to die with our generation, so we should encourage new folks to do new things, not talk down to them because they don't choose to spend 99% of their operating time pounding brass. They don't give you static about taking up bandwidth with your ancient operating mode, why hassle them because they can make Qs below the noise leve >> l. Oh yes, my DXCC certificate says "Mixed" on it. I quit counting when I got that. >>>>> On Mon, Jul 13, 2020, 03:25 Victor Rosenthal 4X6GP <[hidden email] <mailto:[hidden email]>> wrote: >>>> Actually, I'm building a regenerative receiver now. I have to use JFETs >>>> because I got rid of all my tube stuff due to lack of room. But of >>>> course I will continue to benefit from the DSP in my K3, and its keyer >>>> (although I have a bug that I use once in a while). >>>> But those things don't take away the connection to history, they >>>> make it >>>> better. The point for me isn't to use the same gear as they did in >>>> 1912, >>>> but to enter the Morse space as they did. If I can do it with equipment >>>> that is more stable and effective, so much the better. >>>> After all, a modern sailboat is very much more sophisticated than an >>>> old >>>> one, but sailing is still sailing. >>>> 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:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> ------------------------------ >> >> Message: 4 >> Date: Tue, 14 Jul 2020 02:35:36 +0000 >> From: "Dave Van Wallaghen" <[hidden email]> >> To: "Keith Hamilton" <[hidden email]>, [hidden email] >> Subject: Re: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> Message-ID: <em385dd5fe-747a-45c7-91aa-6be7eb9502cb@desktop-lqvflms> >> Content-Type: text/plain; format=flowed; charset=utf-8 >> >> Keith, >> >> I saw Don respond to this and he is right that K15 would be the common >> denominator if not for 15m. You can check to see if the coils are intact >> if you measure the resistance between pins 1 and 10 for each. It should >> be around 230 ohms or so. If you find one open or well away from that >> resistance, then it would indicate a bad coil on that relay. >> >> You can also measure the intended path through the relays for each band >> and make sure there are no unintended paths. If you can read the >> schematic, it shows the path with each relay in it's reset state. You >> would need to consult the table in Appendix B to see which relay(s) are >> active for a respective band and you can then measure the continuity of >> the intended path. You should also check any unintended paths which >> could indicate a problem. >> >> As Don stated, this is not a fun problem to find and will take some good >> debugging skills. So far, everything you've indicated seems to suggest >> the PLL oscillator and VCO circuits are working properly, but the range >> selection area is not producing the proper capacitance to allow the VCO >> to produce the proper frequency on those bands you indicated. >> >> If reading the schematic is a problem, let us know and I am sure between >> Don and myself, we can give you some step by step instructions for >> tracing through this problem. >> >> 73, >> Dave W8FGU >> >> ------ Original Message ------ >> From: "Keith Hamilton" <[hidden email]> >> To: [hidden email] >> Sent: 7/13/2020 9:34:03 PM >> Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> >>> ---------- Forwarded message --------- >>> From: Keith Hamilton <[hidden email]> >>> Date: Mon, Jul 13, 2020 at 9:19 PM >>> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >>> To: Dave Van Wallaghen <[hidden email]> >>> >>> >>> Dave >>> >>> Yes the frequency changes when turning the VFO knob when measuring with CAL >>> FCTR on TP1. >>> >>> I have checked the markings on C71, C72, C73, and C74 (C75 is not installed >>> yet). They are >>> all correct and I resoldered them to be sure. >>> >>> I am beginning to think I might have a bad relay K13, K14 or K15. My good >>> bands are 80,40 and >>> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the relay >>> table in appendix B >>> I am not sure which relay could be bad. How can I test them? Should I try >>> to replace them? >>> 73, >>> Keith N8CEP >>> >>> >>>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> wrote: >>>> >>>> Ok Keith, just to make sure things are where we want on the bands that >>>> seem to work, does the frequency change when turning the VFO knob when >>>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>>> >>>> For the bands that are locked at 8.28v, that is the max output from the >>>> integrator circuit (U6B). This means that there is no lock between the PLL >>>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to drive the >>>> varactors to provide more capacitance to the VCO circuit. The most likely >>>> cause will be a misplaced capacitor in the VCO range selector (C71 - C75) >>>> or a problem in the VCO circuit itself. But because this may be band >>>> dependent, I would look first in that range selection circuit. Verify that >>>> those caps are the proper values. They are easily misread and will cause >>>> the type of thing you are seeing. >>>> >>>> Also verify those varactor diodes are the proper type and in the right >>>> places. Soldering issues are typically the leading cause of problems, so >>>> check that also. If all looks right to you, you may want to signal trace >>>> through that selection circuit to verify the proper relays and active for >>>> the bands not working. There is a relay table in Appendix B that shows you >>>> which relays are active for each band. >>>> >>>> This is a brand new build, correct? >>>> >>>> 73, >>>> Dave, W8FGU >>>> >>>> >>>>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> wrote: >>>> Thanks for your help Dave! >>>> >>>> Yes. I was able to get 6 volts on R30 by turning L30. At first the voltage >>>> was too high >>>> so I adjusted the turns on T5 by spreading the red windings further apart. >>>> Then I >>>> was able to get to 6 volts. >>>> >>>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>>> The reading is 8912.22 >>>> >>>> 73 Keith N8CEP >>>> >>>> >>>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> wrote: >>>>> Hi Keith, >>>>> >>>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring the >>>>> voltage down or up by moving the windings on T5? >>>>> >>>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>>> know what the reading is. I'm just looking for a couple of clues before >>>>> we proceed. >>>>> >>>>> 73, >>>>> Dave, W8FGU >>>>> >>>>> >>>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> wrote: >>>>> >>>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>>> windings >>>>>> and obtained 6 volts at the left end of R30. I then went on to the chart >>>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>>> readings >>>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on 30,20,17 >>>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>>> >>>>>> I have checked the solder connections of T5 and the value of C72 (271). >>>>> The >>>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also went >>>>>> over the solder connections of K13, K14 and K15. >>>>>> >>>>>> Now I'm stuck. Any help will be appreciated. >>>>>> >>>>>> Keioth Hamilton N8CEP >>>>>> ______________________________________________________________ >>>>>> Elecraft mailing list >>>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>>> Post: mailto:[hidden email] >>>>>> >>>>>> This list hosted by: http://www.qsl.net >>>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>>> Message delivered to [hidden email] >>>>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> ------------------------------ >> >> Message: 5 >> Date: Mon, 13 Jul 2020 21:47:01 -0500 >> From: Kurt Pawlikowski <[hidden email]> >> To: Wayne Burdick <[hidden email]>, Elecraft Reflector >> <[hidden email]> >> Subject: Re: [Elecraft] "On second thought, I'll take the stairs." >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> Wayne: Would you mind if I forwarded this to our ham newsletter editor >> for reprint? Thanks! k WB9FMC >> >>> On 7/12/2020 10:07 AM, Wayne Burdick wrote: >>> I have a friend about my age who got into amateur radio only a few years ago. Like many of us, he was enthusiastic about the technology. Intrigued with DX. >>> >>> I showed him my station; we talked endlessly about gear. Later, I helped him put up a simple wire antenna. >>> >>> Then, when his license arrived, he dove straight into FT8 and didn't look back. Within days, he'd worked all states, then DXCC. He'd bag a few rare ones over a light lunch, then pat his laptop on the back and congratulate his software app for its near-mythical ability to extract weak signals out of noise. >>> >>> Within weeks, he'd mastered everything there was to know about this glorious new hobby. >>> >>> Point. Click. >>> >>> In this new world order, those of us who took the longer, slower path to ionospheric enlightenment -- and who still occasionally enjoy making waves by hand -- often fail to explain why. >>> >>> I had failed to explain it to my friend. Even as hints of his boredom crept in, creating an opening, the best argument I'd made for trying CW was that he could do it without a computer. Coming in a weak second was the notion that CW was the original digital mode. For obvious reasons, I didn't bother with the classic argument about CW's signal-to-noise advantage over SSB. >>> >>> I had all but given up. >>> >>> Then, in a moment of delayed clarity, I decided on a different approach. I invited him to a weekday brunch. A bit of an escape. He willingly took the bait. >>> >>> On the appointed day, arriving at his workplace, I bypassed the lobby's glistening elevators and climbed the four flights of stairs to his office. I insisted we take the stairs down, too. >>> >>> "Why?" he asked. "And how'd you get up here so fast?" >>> >>> I pointed out that I always chose stairs, when possible. That's why I wasn't out of breath. We hustled down, jockeying for position, and emerged on the ground floor invigorated by the effort. >>> >>> "So, where are we going?" he asked. We'd been to every overrated twenty-dollar burger venue at least twice. >>> >>> I replied that we'd be going someplace we'd never tried. My kitchen. >>> >>> When we arrived, I put him to work chopping onions and broccoli and squeezing oranges while I whipped eggs into a froth and grated Swiss cheese. We ate our omelettes outside, in full sun and a cool breeze. >>> >>> "What's for desert?" he asked. "Isn't there a frozen yogurt place a two-minute drive from here?" >>> >>> I had something else in mind. Back in the kitchen, I handed him a water bottle, then strapped on a small pack I'd prepared earlier. >>> >>> We walked a mile or so through my neighborhood, admiring the houses' varied architecture, ending up (as planned) at a local park festooned with blackberry bushes. The most accessible branches had been picked clean, but with teamwork and persistence we were able to gather several large handfuls of fat, ripe berries, which we devoured on the spot. >>> >>> We'd been poked and scratched but didn't care. >>> >>> "Doesn't brunch usually end with champagne?" he wondered aloud, admiring his wounds. >>> >>> Not this time. I pulled out two bottles of craft beer that I'd obtained from a neighbor in trade for repairing his ancient home stereo. Carlos had spent years crafting an American pilsner to die for, sweating every detail, including iconic, hand-painted labels. >>> >>> My friend accepted the bottle, then tried in vain to remove the cap. Not a twist-off. >>> >>> "Opener?" he said. >>> >>> I handed him a small pocket knife, an antique without specialty blades. He soon discovered it could not be used to remove the cap directly. He looked at me with a bemused expression, no doubt wondering what I had up my sleeve this time. >>> >>> I pointed out that we were surrounded by white oaks, a species known for its hard wood. He got the message, smiled, and began hunting. Within seconds he'd collected a small fallen branch. I watched as he used the knife to fashion a few inches of it into a passable bottle opener. We popped the caps, toasted his new-found skill, and traded stories of our misspent youths. >>> >>> "Oh, one more thing," I said. >>> >>> I pulled a KX2 out of my pack, along with two lengths of wire. Of course he knew everything there was to know about Elecraft, and me, so he wasn't surprised when I also pulled out the rig's attachable keyer paddle. We threw one wire in the closest tree and laid the other on the ground. >>> >>> He didn't have to ask whether I'd brought a laptop. >>> >>> We listened to CW signals up and down 20 meters, which was open to Europe at the time. As he tuned in each station, I copied for him using pencil and paper. He'd learned Morse code, but only at very slow speeds. >>> >>> After making a contact, I set the internal keyer speed to 10 words per minute and dialed power output to zero, for practice purposes, then showed him how to use the paddle. He smiled as he got the hang of it. Sending the full alphabet was a challenge, but he got there. The KX2 decoded and displayed his keying, providing confirmation. >>> >>> We'd blown through his allotted lunch break by a factor of three, so it was time to go. We coiled up the antenna wires, packed up, and walked back. As I drove him back to his employer, we made plans to get together again for a weekend hike. >>> >>> I could have just dropped him off, but we went back into the lobby together. Out of habit, he stopped in front of the elevator. Then he looked up. >>> >>> "OK," he said. "I get it. This CW thing. It's slow, it's hard to do well, and it takes years of practice." >>> >>> "Like hunting for your own food, or carving your own tools," I added. >>> >>> "Or cooking from scratch. Or brewing your own beer. Building your own radio. And you use more of your senses. Not just your eyes, but your ears. Your sense of touch." >>> >>> I nodded. Listening. Feeling. That was the radio I'd grown up with. >>> >>> "Of course it's harder to work DX with CW than with FT8," I reminded him, playing devil's advocate. >>> >>> "Is that what matters, though?" he asked. >>> >>> A longer discussion for another day. >>> >>> "Your call," I said. >>> >>> He gripped my shoulder and smiled, then reached toward the elevator's glowing, ivory colored button, framed by polished brass. >>> >>> The path most taken. >>> >>> Point. Click. >>> >>> "On second thought," he said, "I'll take the stairs." >>> >>> * * * >>> >>> Wayne, >>> N6KR >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> ------------------------------ >> >> Message: 6 >> Date: Mon, 13 Jul 2020 23:00:59 -0400 >> From: Keith Hamilton <[hidden email]> >> To: Dave Van Wallaghen <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >> Message-ID: >> <CAJkuCUZmuY7Ys=ypJjjEK0wt7o5ocWzVCZQL=SZkPC7E=[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> OK Dave - >> >> I will check the relays as you suggest. In troubleshooting capacitors I >> messed up >> C74. I pulled it off the board and sent a request to Elecraft for a >> replacement. >> That may solve the problem. In the meantime I will check the coils on the >> K13 to K15 >> relays and let you know what I find. >> >> I did not see Don's post. I will check it out. So I will be waiting a bit >> to fix this problem, >> >> 73 and thanks! >> Keith N8CEP >> >>> On Mon, Jul 13, 2020 at 10:36 PM Dave Van Wallaghen <[hidden email]> wrote: >>> >>> Keith, >>> >>> I saw Don respond to this and he is right that K15 would be the common >>> denominator if not for 15m. You can check to see if the coils are intact >>> if you measure the resistance between pins 1 and 10 for each. It should >>> be around 230 ohms or so. If you find one open or well away from that >>> resistance, then it would indicate a bad coil on that relay. >>> >>> You can also measure the intended path through the relays for each band >>> and make sure there are no unintended paths. If you can read the >>> schematic, it shows the path with each relay in it's reset state. You >>> would need to consult the table in Appendix B to see which relay(s) are >>> active for a respective band and you can then measure the continuity of >>> the intended path. You should also check any unintended paths which >>> could indicate a problem. >>> >>> As Don stated, this is not a fun problem to find and will take some good >>> debugging skills. So far, everything you've indicated seems to suggest >>> the PLL oscillator and VCO circuits are working properly, but the range >>> selection area is not producing the proper capacitance to allow the VCO >>> to produce the proper frequency on those bands you indicated. >>> >>> If reading the schematic is a problem, let us know and I am sure between >>> Don and myself, we can give you some step by step instructions for >>> tracing through this problem. >>> >>> 73, >>> Dave W8FGU >>> >>> ------ Original Message ------ >>> From: "Keith Hamilton" <[hidden email]> >>> To: [hidden email] >>> Sent: 7/13/2020 9:34:03 PM >>> Subject: [Elecraft] Fwd: Re[2]: K2 7747 VCO alignment problem >>> >>>> ---------- Forwarded message --------- >>>> From: Keith Hamilton <[hidden email]> >>>> Date: Mon, Jul 13, 2020 at 9:19 PM >>>> Subject: Re: Re[2]: [Elecraft] K2 7747 VCO alignment problem >>>> To: Dave Van Wallaghen <[hidden email]> >>>> >>>> >>>> Dave >>>> >>>> Yes the frequency changes when turning the VFO knob when measuring with >>> CAL >>>> FCTR on TP1. >>>> >>>> I have checked the markings on C71, C72, C73, and C74 (C75 is not >>> installed >>>> yet). They are >>>> all correct and I resoldered them to be sure. >>>> >>>> I am beginning to think I might have a bad relay K13, K14 or K15. My good >>>> bands are 80,40 and >>>> 15 meters. My bad bands are 30,20,17,12 and 10 meters. Looking at the >>> relay >>>> table in appendix B >>>> I am not sure which relay could be bad. How can I test them? Should I try >>>> to replace them? >>>> 73, >>>> Keith N8CEP >>>> >>>> >>>> On Mon, Jul 13, 2020 at 4:58 PM Dave Van Wallaghen <[hidden email]> >>> wrote: >>>>> Ok Keith, just to make sure things are where we want on the bands that >>>>> seem to work, does the frequency change when turning the VFO knob when >>>>> measuring with CAL FCTR on TP1? If they do, then things are working ok. >>>>> >>>>> For the bands that are locked at 8.28v, that is the max output from the >>>>> integrator circuit (U6B). This means that there is no lock between the >>> PLL >>>>> Oscillator and the VCO circuit and the PLL chip (U4) is trying to >>> drive the >>>>> varactors to provide more capacitance to the VCO circuit. The most >>> likely >>>>> cause will be a misplaced capacitor in the VCO range selector (C71 - >>> C75) >>>>> or a problem in the VCO circuit itself. But because this may be band >>>>> dependent, I would look first in that range selection circuit. Verify >>> that >>>>> those caps are the proper values. They are easily misread and will >>> cause >>>>> the type of thing you are seeing. >>>>> >>>>> Also verify those varactor diodes are the proper type and in the right >>>>> places. Soldering issues are typically the leading cause of problems, >>> so >>>>> check that also. If all looks right to you, you may want to signal >>> trace >>>>> through that selection circuit to verify the proper relays and active >>> for >>>>> the bands not working. There is a relay table in Appendix B that shows >>> you >>>>> which relays are active for each band. >>>>> >>>>> This is a brand new build, correct? >>>>> >>>>> 73, >>>>> Dave, W8FGU >>>>> >>>>> >>>>> On 7/13/2020 4:41:07 PM, "Keith Hamilton" <[hidden email]> >>> wrote: >>>>> Thanks for your help Dave! >>>>> >>>>> Yes. I was able to get 6 volts on R30 by turning L30. At first the >>> voltage >>>>> was too high >>>>> so I adjusted the turns on T5 by spreading the red windings further >>> apart. >>>>> Then I >>>>> was able to get to 6 volts. >>>>> >>>>> I did a CAL FCTR with the probe on TP1 and the frequency set to 4000, >>>>> The reading is 8912.22 >>>>> >>>>> 73 Keith N8CEP >>>>> >>>>> >>>>> On Mon, Jul 13, 2020 at 3:59 PM Dave Van Wallaghen <[hidden email]> >>> wrote: >>>>>> Hi Keith, >>>>>> >>>>>> Were you able to get 6v on R30 by tuning L30? Did you have to bring >>> the >>>>>> voltage down or up by moving the windings on T5? >>>>>> >>>>>> If you would, set the VFO to 4 MHz and do a CAL FCTR on TP1 and let me >>>>>> know what the reading is. I'm just looking for a couple of clues >>> before >>>>>> we proceed. >>>>>> >>>>>> 73, >>>>>> Dave, W8FGU >>>>>> >>>>>> >>>>>> On 7/13/2020 2:52:11 PM, "Keith Hamilton" <[hidden email]> >>> wrote: >>>>>>> I am having trouble with the K2 VCO alignment. I have moved the T5 >>>>>> windings >>>>>>> and obtained 6 volts at the left end of R30. I then went on to the >>> chart >>>>>>> (table 6-1) to measure the voltages at the listed frequencies. My >>>>>> readings >>>>>>> are ok on 80 40 and 15 meters (between 1.5 to 7.5 volts) but on >>> 30,20,17 >>>>>>> ,12 and 10 meters the voltage is 8.29 volts and does not change. >>>>>>> >>>>>>> I have checked the solder connections of T5 and the value of C72 >>> (271). >>>>>> The >>>>>>> diodes D21,D22,D23, D24, D25 and D26 are correctly installed. I also >>> went >>>>>>> over the solder connections of K13, K14 and K15. >>>>>>> >>>>>>> Now I'm stuck. Any help will be appreciated. >>>>>>> >>>>>>> Keioth Hamilton N8CEP >>>>>>> ______________________________________________________________ >>>>>>> Elecraft mailing list >>>>>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>>>>> Help: http://mailman.qth.net/mmfaq.htm >>>>>>> Post: mailto:[hidden email] >>>>>>> >>>>>>> This list hosted by: http://www.qsl.net >>>>>>> Please help support this email list: http://www.qsl.net/donate.html >>>>>>> Message delivered to [hidden email] >>>>>> >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >>> >> >> ------------------------------ >> >> Message: 7 >> Date: Mon, 13 Jul 2020 22:52:20 -0700 >> From: John <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] K3 very slow to reach dialed rf output >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> >> When I dial up, or down rf output, it takes in excess of 30 seconds >> >> to reach the output level, which is much lower than requested. >> >> 3 "bars" on the rf meter.? That looks to be 20 to 25 watts. >> >> If I readjust the level, up or down, it takes another 30+ >> >> seconds and it will not go over 3 "bars". >> >> Anyone offer any suggestions? >> >> Thanks. >> >> 73. >> >> John. >> >> ve7day. >> >> >> >> >> >> ------------------------------ >> >> Message: 8 >> Date: Tue, 14 Jul 2020 06:26:00 -0000 >> From: "Doug Turnbull" <[hidden email]> >> To: "'Dauer, Edward'" <[hidden email]>, <[hidden email]>, >> "'Victor Rosenthal 4X6GP'" <[hidden email]> >> Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs >> Message-ID: <007201d659a7$a5099f10$ef1cdd30$@net1.ie> >> Content-Type: text/plain; charset="us-ascii" >> >> Dear Friends, >> Nor are SSB, RTTY and PSK the same as CW but they all serve a purpose. >> Any technology which allows one to work weaker signals with lower power is >> going to make DXCC easier. Even using CW it is infinitely easier to work >> DXCC on multiple bands these days than back in the fifties, well maybe I >> will make an exception for the 1958 era. There are so many aids and >> radios are better. This is a technological hobby and now the guy with the >> apartment and balcony might actually work DXCC. Viva engineering. >> 73 Doug EI2CN >> >> -----Original Message----- >> From: [hidden email] <[hidden email]> On >> Behalf Of Dauer, Edward >> Sent: Monday 13 July 2020 15:39 >> To: [hidden email]; Victor Rosenthal 4X6GP <[hidden email]> >> Subject: [Elecraft] "On Second Thought, I'll Take The Stairs >> >> I agree fully with Victor; though the difference may be even simpler: >> >> Making a QSO using CW is a ham doing something with a radio. Making a QSO >> with FT8 is a radio doing something for a ham. >> >> Neither is better or worse; but they are different. >> >> Ted, KN1CBR >> >> ------------------------------ >> >> Message: 8 >> Date: Mon, 13 Jul 2020 10:41:41 +0300 >> From: Victor Rosenthal 4X6GP <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] FT8 - was "On Second Thought, I'll Take The >> Stairs" >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> For me, it's simple. >> >> When I make a CW contact, even if its total content is "ENN TU", I am >> connected to history, to Jack Phillips on the Titanic, to all of the >> military traffic men and airborne radio operators of WWII, to the operators >> on the merchant ships on the high seas and the Great Lakes, and to all the >> hams of the past, even Mr. Marconi, the first ham. >> >> I like hearing the propagation change with my own ears and struggling to >> capture an ESP-level call. I like the feel of the key and the sound of the >> code. I like the idea that there is another person like me at the other end >> with his or her hand on a key. >> >> I consider myself extremely lucky to have caught the bug at a young age and >> developed the skill needed to make CW as transparent to me as my mother >> tongue. I see how hard it is for those who begin to learn at middle age or >> older. They shouldn't give up -- it's worth it. >> >> 73, >> Victor, 4X6GP >> Rehovot, Israel >> Formerly K2VCO >> CWops no. 5 >> https://urldefense.com/v3/__http://www.qsl.net/k2vco/__;!!NCZxaNi9jForCP_SxB >> KJCA!F4lkQrp7vnWsJyPT-T7iUPs1Sk1a79YI92FbY7WOC4FPuQvWxE1lsChUamJuUgiP$ >> . >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html Message >> delivered to [hidden email] >> >> >> >> ------------------------------ >> >> Message: 9 >> Date: Mon, 13 Jul 2020 23:29:41 -0700 (MST) >> From: dl2ki <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Elecraft K2 CW key shaping >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=us-ascii >> >> Hi, >> >> since someone told me that there is a small "chirp" in my K2-CW signal, I >> would like to check the signal visually. >> >> How can I display the CW Key envelope as shown in the document "Elecraft K2 >> Keying Modification Instructions", page 1. >> >> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >> experience with measuring instruments, since I only use them occasionally. >> >> Thank you and 73 >> Wolfgang >> DL2KI >> >> >> >> >> -- >> Sent from: http://elecraft.365791.n2.nabble.com/ >> >> >> ------------------------------ >> >> Message: 10 >> Date: Tue, 14 Jul 2020 11:00:04 +0300 >> From: Victor Rosenthal 4X6GP <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] Elecraft K2 CW key shaping >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> A chirp can't be seen visually on an oscilloscope (well, maybe on a >> panadpter or spectrum analyzer if it is a very big one). >> >> A chirp is a change in frequency of the transmitted signal. It is not >> the same as a click, which is a wide signal caused by too-short rise and >> fall times of the keyed envelope, or a badly shaped envelope. You can >> see the envelope shape on an oscilloscope. But the change in frequency >> caused by a chirp is very small in comparison with the frequency of the >> signal. >> >> The way to detect a chirp is to listen to the transmitted signal on a >> second receiver. Your ear is very sensitive to changes in pitch. >> >> 73, >> Victor, 4X6GP >> Rehovot, Israel >> Formerly K2VCO >> CWops no. 5 >> http://www.qsl.net/k2vco/ >> . >>> On 14/07/2020 9:29, dl2ki wrote: >>> Hi, >>> >>> since someone told me that there is a small "chirp" in my K2-CW signal, I >>> would like to check the signal visually. >>> >>> How can I display the CW Key envelope as shown in the document "Elecraft K2 >>> Keying Modification Instructions", page 1. >>> >>> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >>> experience with measuring instruments, since I only use them occasionally. >>> >>> Thank you and 73 >>> Wolfgang >>> DL2KI >>> >>> >>> >>> >>> -- >>> Sent from: http://elecraft.365791.n2.nabble.com/ >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >>> >> >> ------------------------------ >> >> Message: 11 >> Date: Tue, 14 Jul 2020 18:15:22 +1000 >> From: Matt Maguire <[hidden email]> >> To: Victor Rosenthal 4X6GP <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] Elecraft K2 CW key shaping >> Message-ID: >> <[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> Generally a chirp would be due to an unstable power supply, resistance in >> the fuse holder, etc.. It can also be cause by poor decoupling/loading of >> the oscillator circuit, but in the case of a well-designed circuit like the >> K2, this would normally only arise with misplaced components or poor >> connections. >> >> On Tue, 14 Jul 2020 at 18:01, Victor Rosenthal 4X6GP <[hidden email]> >> wrote: >> >>> A chirp can't be seen visually on an oscilloscope (well, maybe on a >>> panadpter or spectrum analyzer if it is a very big one). >>> >>> A chirp is a change in frequency of the transmitted signal. It is not >>> the same as a click, which is a wide signal caused by too-short rise and >>> fall times of the keyed envelope, or a badly shaped envelope. You can >>> see the envelope shape on an oscilloscope. But the change in frequency >>> caused by a chirp is very small in comparison with the frequency of the >>> signal. >>> >>> The way to detect a chirp is to listen to the transmitted signal on a >>> second receiver. Your ear is very sensitive to changes in pitch. >>> >>> 73, >>> Victor, 4X6GP >>> Rehovot, Israel >>> Formerly K2VCO >>> CWops no. 5 >>> http://www.qsl.net/k2vco/ >>> . >>>> On 14/07/2020 9:29, dl2ki wrote: >>>> Hi, >>>> >>>> since someone told me that there is a small "chirp" in my K2-CW signal, I >>>> would like to check the signal visually. >>>> >>>> How can I display the CW Key envelope as shown in the document "Elecraft >>> K2 >>>> Keying Modification Instructions", page 1. >>>> >>>> An oscilloscope "Tektronix 2465A" is at my disposal, but I have little >>>> experience with measuring instruments, since I only use them >>> occasionally. >>>> Thank you and 73 >>>> Wolfgang >>>> DL2KI >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://elecraft.365791.n2.nabble.com/ >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >>>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >>> >> >> ------------------------------ >> >> Message: 12 >> Date: Tue, 14 Jul 2020 08:45:02 -0400 >> From: Rich NE1EE <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] Elecraft K2 CW key shaping #chirp #click >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >> I don't have any experience with chirps, but I can add this bit. >> >> If you can hear the change, then the change can be seen on an FFT. At least that would give a sense of whether the shift is up or down, if it is difficult to tell by listening. An FFT could also be applied to the RF, but, as Victor mentioned, the shift is small wrt the TX freq. It is NOT small wrt the decoded audio, however, which is why it was reported. So an FFT may well find it. There are different ways to get that analysis, and might not be worth the effort. One method would be to use a modern scope with FFT; another, a software scope such as the Zeitnitz scope; another might be fldigi. In the last two cases, you'd have to pipe the audio...that is the RX decoded audio...into the audio line in on a computer. >> >> But you still have to find out why...so maybe this FFT business isn't worth the effort...because you still then have to find the /cause/, even though you now have a pretty good idea where to look. >> >>> On 2020-07-14 18:15:+1000, you wrote: >>> Generally a chirp would be due to an unstable power supply, resistance in >>> the fuse holder, etc.. It can also be cause by poor decoupling/loading of >>> the oscillator circuit, but in the case of a well-designed circuit like the >>> K2, this would normally only arise with misplaced components or poor >>> connections. >>> >>> On Tue, 14 Jul 2020 at 18:01, Victor Rosenthal 4X6GP <[hidden email]> >>> wrote: >>> >>>> A chirp can't be seen visually on an oscilloscope (well, maybe on a > panadpter or spectrum analyzer if it is a very big one). >>>> >>>> A chirp is a change in frequency of the transmitted signal. It is not > the same as a click, which is a wide signal caused by too-short rise and > fall times of the keyed envelope, or a badly shaped envelope. You can > see the envelope shape on an oscilloscope. But the change in frequency > caused by a chirp is very small in comparison with the frequency of the > signal. >>>> >>>> The way to detect a chirp is to listen to the transmitted signal on a > second receiver. Your ear is very sensitive to changes in pitch. >>>> >>>> 73, >>>> Victor, 4X6GP >>>> Rehovot, Israel >> >> ~R~ >> 72/73 de Rich NE1EE >> On the banks of the Piscataqua >> >> >> >> ------------------------------ >> >> Message: 13 >> Date: Tue, 14 Jul 2020 07:18:48 -0600 >> From: David Herring <[hidden email]> >> To: John <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] K3 very slow to reach dialed rf output >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8 >> >> Sounds like your audio level it set too low. >> Try adjusting that up. Don?t quote me, but if memory serves that has to be 4 bars with the 5th flickering. >> A search through the archives will find that addressed many times. >> Audio too low makes the K3 ?power hunt? which is what it sounds like yours is doing. >> >> 73, >> David - N5DCH >> >> >> >>> On Jul 13, 2020, at 11:52 PM, John <[hidden email]> wrote: >>> >>> >>> When I dial up, or down rf output, it takes in excess of 30 seconds >>> >>> to reach the output level, which is much lower than requested. >>> >>> 3 "bars" on the rf meter. That looks to be 20 to 25 watts. >>> >>> If I readjust the level, up or down, it takes another 30+ >>> >>> seconds and it will not go over 3 "bars". >>> >>> Anyone offer any suggestions? >>> >>> Thanks. >>> >>> 73. >>> >>> John. >>> >>> ve7day. >>> >>> >>> >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> ------------------------------ >> >> Message: 14 >> Date: Tue, 14 Jul 2020 10:14:18 -0400 >> From: w4sc <[hidden email]> >> To: "[hidden email]" <[hidden email]>, >> "[hidden email]" <[hidden email]> >> Subject: Re: [Elecraft] [K3] Sub receiver intermittant failures >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset="utf-8" >> >> Ray >> >> If you have KSYN3A synthesizers installed, check for the following mod. >> >> Ref: KSYN3A Synthesized Installation Instructions pp 5 >> >> https://ftp.elecraft.com/K3S/Manuals%20Downloads/E740257%20KSYN3A%20Installation%20Rev%20A6.pdf >> >> KREF3 Output Level Modification >> https://ftp.elecraft.com/K3/Mod%20Notes%20Alerts/E740278%20KREF3%20Output%20Level%20Modification.pdf >> >> Ben W4SC >> >> Sent from Mail for Windows 10 >> >> >> >> ------------------------------ >> >> Message: 15 >> Date: Tue, 14 Jul 2020 07:55:42 -0700 >> From: John <[hidden email]> >> To: David Herring <[hidden email]> >> Cc: [hidden email] >> Subject: Re: [Elecraft] K3 very slow to reach dialed rf output >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> Thanks to all who had suggestions. >> >> Windows had made an update and changed audio settings. >> >> Problem solved. >> >> 73. >> >> John. >> >> ve7day. >> >> >>> On 14/07/2020 6:18 a.m., David Herring wrote: >>> Sounds like your audio level it set too low. >>> Try adjusting that up. Don?t quote me, but if memory serves that has to be 4 bars with the 5th flickering. >>> A search through the archives will find that addressed many times. >>> Audio too low makes the K3 ?power hunt? which is what it sounds like yours is doing. >>> >>> 73, >>> David - N5DCH >>> >>> >>> >>>>> On Jul 13, 2020, at 11:52 PM, John <[hidden email]> wrote: >>>> >>>> When I dial up, or down rf output, it takes in excess of 30 seconds >>>> >>>> to reach the output level, which is much lower than requested. >>>> >>>> 3 "bars" on the rf meter. That looks to be 20 to 25 watts. >>>> >>>> If I readjust the level, up or down, it takes another 30+ >>>> >>>> seconds and it will not go over 3 "bars". >>>> >>>> Anyone offer any suggestions? >>>> >>>> Thanks. >>>> >>>> 73. >>>> >>>> John. >>>> >>>> ve7day. >>>> >>>> >>>> >>>> ______________________________________________________________ >>>> Elecraft mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:[hidden email] >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> Message delivered to [hidden email] >> >> ------------------------------ >> >> Message: 16 >> Date: Tue, 14 Jul 2020 17:23:44 +0200 >> From: Steef PA2A <[hidden email]> >> To: [hidden email] >> Subject: [Elecraft] Replace backup battery CR2032 in a K3 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=US-ASCII; format=flowed >> >> Hi, >> >> has anyone already changed the CR2032 backup battery in a K3? Under the >> carton cover the battery has started to oxydize but the Voltage is still >> 3.06 Volts after twelve years. I guess an external 3 Volts source should >> be applied to save all settings during the replacement. >> >> 73s Steef PA2A, K3 #1184 >> >> >> ------------------------------ >> >> Message: 17 >> Date: Tue, 14 Jul 2020 11:39:39 -0400 >> From: Grant Youngman <[hidden email]> >> To: [hidden email] >> Cc: Elecraft Refl <[hidden email]> >> Subject: Re: [Elecraft] Replace backup battery CR2032 in a K3 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8 >> >> The battery supports the real time clock only. You won?t lose any other settings if you replace it. >> >> Grant NQ5T >> >>> On Jul 14, 2020, at 11:23 AM, Steef PA2A <[hidden email]> wrote: >>> >>> Hi, >>> >>> has anyone already changed the CR2032 backup battery in a K3? Under the carton cover the battery has started to oxydize but the Voltage is still 3.06 Volts after twelve years. I guess an external 3 Volts source should be applied to save all settings during the replacement. >>> >>> 73s Steef PA2A, K3 #1184 >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> >> ------------------------------ >> >> Message: 18 >> Date: Tue, 14 Jul 2020 09:27:06 -0700 >> From: Jim Brown <[hidden email]> >> To: [hidden email] >> Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs >> Message-ID: >> <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >>> On 7/13/2020 11:26 PM, Doug Turnbull wrote: >>> Even using CW it is infinitely easier to work >>> DXCC on multiple bands these days than back in the fifties, well maybe I >>> will make an exception for the 1958 era. >> Except that noise levels have escalated by 20 dB since that era. >> >> 73, Jim K9YC >> >> >> ------------------------------ >> >> Message: 19 >> Date: Tue, 14 Jul 2020 11:53:08 -0500 >> From: Tony Estep <[hidden email]> >> To: Elecraft <[hidden email]> >> Subject: Re: [Elecraft] "On Second Thought, I'll Take The Stairs >> Message-ID: >> <CACHwrmM3o3dCL=[hidden email]> >> Content-Type: text/plain; charset="UTF-8" >> >>> >>> ...Even using CW it is infinitely easier to work >>> DXCC on multiple bands these days than back in the fifties, well maybe I >>> will make an exception for the 1958 era.... >>> >> ================= >> Ha ha, yep. I worked DXCC as a Novice in 1957-58, all on 15 CW. It's true >> that signals were popping in from all over the world at the time. But the >> level and type of activity were completely different, of course. I worked >> many countries still deemed to be rare via QSOs with local hams (e.g. >> Johnston Island) or visiting scientists (e.g. Amsterdam Island), but only a >> couple via DXpeditions (e.g. Navassa). Often you'd have an exchange of name >> and qth, even with rare DX when others were waiting. You found DX by tuning >> and listening, and most QSLing was via direct mail. A different world. >> Now with clusters and micro-QSOs (5nn tu) you can knock off DXCC within 24 >> hours during a contest. Which is more fun? I dunno. Either way, hearing >> your call come back from the other edge of the world can give a little jolt >> of adrenaline, no matter how many times you've done it. I don't get any >> jolt seeing my call on the FT8 scroll. >> >> 73, >> Tony KT0NY >> >> >> ------------------------------ >> >> Message: 20 >> Date: Tue, 14 Jul 2020 14:26:36 -0400 >> From: Nr4c <[hidden email]> >> To: [hidden email] >> Cc: [hidden email] >> Subject: Re: [Elecraft] Replace backup battery CR2032 in a K3 >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8 >> >> Don?t get too excited. I?m told it only keeps the clock running. All settings are in non-volatile memory. >> >> Sent from my iPhone >> ...nr4c. bill >> >> >>> On Jul 14, 2020, at 11:25 AM, Steef PA2A <[hidden email]> wrote: >>> >>> ?Hi, >>> >>> has anyone already changed the CR2032 backup battery in a K3? Under the carton cover the battery has started to oxydize but the Voltage is still 3.06 Volts after twelve years. I guess an external 3 Volts source should be applied to save all settings during the replacement. >>> >>> 73s Steef PA2A, K3 #1184 >>> ______________________________________________________________ >>> Elecraft mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/elecraft >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[hidden email] >>> >>> This list hosted by: http://www.qsl.net >>> Please help support this email list: http://www.qsl.net/donate.html >>> Message delivered to [hidden email] >> >> ------------------------------ >> >> _______________________________________________ >> Elecraft mailing list >> Post to: [hidden email] >> http://mailman.qth.net/mailman/listinfo/elecraft >> You must be a subscriber to post. >> Elecraft web page: http://www.elecraft.com >> >> End of Elecraft Digest, Vol 195, Issue 17 >> ***************************************** > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |