Showing posts with label Equipment. Show all posts
Showing posts with label Equipment. Show all posts

Thursday, February 18, 2021

More on the Yaesu FTDX10

 


I’ve used the FTDX10 daily for just over a month now. There is much to love about this little rig.

It took a bit of head-scratching before I eventually got the single-cable control and audio I/O working. There are USB drivers and CODECs on the Yaesu web site that need to be installed. At first, there was no love from the 10; I could not get Ham Radio Deluxe to recognize the Yaesu no matter what settings I tried.  Eventually I gave up on the USB cable and tried RS232C. That didn’t work either. Finally, after much resetting and disconnecting and reconnecting cables and restarting and cursing, I was first able to get audio through the USB port and into GarageBand. A few more tweaks and the rig control started working. I’m still not sure what I did, but it was clearly an issue of getting the right devices assigned to the right virtual COM ports in Parallels. Now I have the audio CODEC feeding the Mac natively, and rig control operating via HRD running in Windows inside a Parallels virtual machine. 


An unexpected surprise: after years of searching for good external stereo speakers, I’ve finally found them—and I didn’t have to look very far: my iMac. The audio coming out of my iMac’s built-in speakers is full, undistorted, RFI-free (as far as I’ve found to date), and beautifully tailored in GarageBand. I’m starting to capture audio snippets again just like I did back when I was a kid with my brother’s Akai 1/4-in. reel-to-reel recorder hooked up to my DX-160! (Where are those tapes today?!?!?)



With all that accomplished, my next trick will be to get the K3’s audio into the Mac. This is where I will undoubtedly regret not upgrading to the KIO3B board to deliver digital audio straight from the radio. It might also be a good excuse to buy a used K3S. 

Or another FTDX10...


Saturday, January 9, 2021

FTDX10

 So, I did a thing...


First, keep in mind my K3 is #216, it hasn’t had any of the hardware revisions done to the original model, much less the K3S synth upgrade. But it’s still the best receiver I’ve ever used under tough conditions, so much so that I’ve spent most of the last 13 years completely free of rig envy. I did not and still do not need a better radio and am not looking for one; I just wanted a new second 100w rig, and I bought it fully aware of all the important (to me) K3 features the 10 is missing. 


I knew it would be a solid performer from reading some of Rob Sherwood’s comments, but I am stunned. I’ve been playing with this thing in the NAQP CW contest, purposely looking for weak signals next to strong ones to test against the K3, and I cannot find any case in which the K3 could hear better than the FTDX10. Mostly the same, but occasionally a few where the 10 really outdid the 3. 


North American QSO Party in full swing.

Best example: Both radios set as close to identical as possible: bandwidth 300 Hz, APF on, 6dB ATT, preamps off. Weak signal on frequency x, strong signal on x+100Hz. The strong signal was still clearly audible inside the passband of the K3, while there was barely a trace of it on the 10–maybe some light key clicks on signal peaks, but no cw at all, Even when using the 500Hz roofing filter instead of the 300Hz.. No matter what amount of tweaking I did to the K3, I could not remove it from the passband (short of using a notch filter). I think the difference can be attributed to its APF—the 10’s APF is adjustable with three settings (NARR, MED, WIDE; mine is set to NARR), while the K3’s APF only has one which appears to be not quite as sharp as the 10’s. The K3 did not, however, exhibit any noticeable AGC pumping or other degradation to signal quality. This was an extreme case that I deliberately went looking for. Most of the time I couldn’t tell much difference between the two receivers. Bear in mind that I’m just using an end-fed wire, my “real” antenna has been down since my last move in 2016. So there’s not a lot of microvolts present at the antenna connector.


On transmit, T/R relays clickety-clicking isn’t too bad. If I were to use it in a contest, though, I’d probably turn off the full break-in and go semi-. The fan comes on during RX and isn’t exactly whisper quiet. I’m pretty tolerant, I’ve got all sorts of ambient noise in my shack that’s worse, so it’s just another hum.


Noise reduction works nicely on CW. On phone, I typically run the DNR lightly on the K3; on the FTDX10 it introduces a reverb to the signal that I don’t like, but that is pretty much default settings. I haven’t tweaked any of the settings yet. And there are a LOT of settings to set! ðŸ˜³ I’ve only got a few hours seat time with this thing and have barely cracked the manual. 


The panadapter works. First thing I did was turn off the 3D waterfall. I’ll let the fanboys argue about whether the 7300 or 10 has the better fishfinder; to me it’s like Ford and Chevy guys arguing about who has the better radiator. It works as well as or better than my Flex 1500, and that works well enough for me. All but three analog controls are crammed to the right of the screen. There are a lot of them (24) and some of the buttons are in a tight place between protruding knobs. Familiarity will come over time—I spend a lot of time with my finger ready to press or turn something, but not sure where to poke it. Lol! I’m happy to say that they’ve at least got the right analog controls. Nothing that important hidden deep in menus, I don’t think. And the menus are a whole lot easier to navigate through than the K3 by a long shot. 


I posted a video of my first 5 or so minutes using the FTDX10 for the first time fresh out of the box...before I even read The Book of Words!: 



More to come as I dig into this rig.

Sunday, December 9, 2018

#shackcleaningsunday


Against all expectations, I actually did find a floor beneath all the wires and dust bunnies.

Sunday, November 18, 2018

Back again.

I've been tuning around since Wednesday with the little rig (at 5 watts) and a short wire (poorly matched) at the ass end of the sunspot cycle. Could it get any worse? 🤔

Making a few contacts, added a couple of new ones for the QRP DXCC chase (8P9 and VP2V) bringing me up to 60 worked. But damn, it's hard to make Qs! So much easier with the KPA500...

The KX2 is an amazing radio. I'm making this my main rig until I accomplish two goals: get the Tarheel and ground radials installed, and work QRP DXCC. I don't think I'm going to get 40 new ones by the end of the year, but maybe by February and the Orlando fest. The Tarheel screwdriver, though... that would definitely help with the DXCC goal.

I've been working in WordPress for a couple of clients and loving it, so this blog may be undergoing a major redesign soon.

The Jackonaut has called dibs on my office/shack, so he's the Second Op now, relieving the Tiny Brown Kitten of those duties.


Sunday, May 22, 2016

Elecraft KX2


Announced (or at least leaked to the public) just before its grand debut at Dayton last week. I held out for four (4) days before blowing the rent money.


Brother K2JK asked me, "Why do you need a KX2?" As if that's a relevant question...

Saturday, February 28, 2015

West Mountain Radio TARGETuner

West Mountain Radio TARGETuner and RigRunner 4004U
Took my first visit to the Orlando HamCation on Saturday 14-Feb and got to check out a few things on my wish list. I also scratched a couple of things off the list: a memory controller for the Tarheel screwdriver, and a PowerPole distribution box for better management of my DC power cabling.

I'd been considering the MFJ controllers ever since I bought the Tarheel. Never pulled the trigger on one, though; my track record with MFJ products has been disappointing and another dice roll wasn't going to happen. The Tarheel's standard rocker switch and the MFJ SWR analyzer (one of their products that actually works well for me) was sufficient despite being a pain to switch from the K3 to the analyzer every time I wanted to QSY to a new band. So I dealt with it for the past six years, but I kept thinking I needed a little more automation in the process of changing bands.

I first heard about the West Mountain Radio TARGETuner a few months ago and it looked like a possibility, so it was one of the first things I sought out at Orlando. After seeing it demonstrated and having my questions asked, I bought one through one of WMR's dealers at the show, Ham World, for $235 -- a fair bit more than a comparable MFJ-1927 controller. The TARGETuner is a two-box deal: a compact controller box and a remote SWR sensor that samples the RF. The two units connect together via Cat 5 ethernet cable. The controller also includes a USB port for connecting to a radio's serial port to read frequency data directly and tune the antenna without transmitting.

Four methods of tuning the antenna are available:
  • Auto SWR Tuning -- Samples transmitted RF and adjusts the antenna for lowest SWR match.
  • Auto Memory -- Samples RF and tunes the antenna to the nearest frequency stored in memory.
  • Manual Memory -- Manually recall and pick a frequency in memory and the antenna is tuned to that frequency.
  • Manual Control -- Up and Down buttons raise or lower the antenna, just like in the old rocker switch days.
Hooking everything up is a fairly simple process. The initial settings require the fully extended and fully collapsed positions to be memorized to establish the range of the antenna. I then used the MFJ-259 SWR analyzer to tune the Tarheel on every band from 12m down to 80m, storing the settings into memories.

Setup complete, I began testing. The initial results were mixed. Returning to a stored memory setting would yield wildly different SWR measurements. It seems as though it loses its count, so I reduced both Auto and User Motor Speed settings to Medium-Slow; Motor Ramping was left on. It seemed to work better for a while but would eventually lose the turn count, requiring me to manually tune the antenna after every QSY.

The tuning weirdness continued for about a week as I recalibrated and tried different settings... and suddenly it just started working with all the motor speed settings to Slowest, and the Motor Ramping turned off; I also have the low and high frequency limits set to just below the 40m band rather and just above 15m. I figured the antenna is pretty much a dummy load on 80m, and when I want to work 12m (or 10m with the amp off and ATU on) I just bring the antenna down to Pos:0101 (as low a turn count as I can get) and get a good SWR match. I suspect the really long coil travel between 12m and 80m might be one of the things messing up the turn count. With the 40m-15m configuration it behaved admirably throughout the ARRL International DX CW contest weekend as I bounced around between bands, and a week later and it's still going strong, it is still accurate when returning to stored memory positions.

I've not tried the serial connection to the K3 yet but it is one of the supported transceivers. The instructions are not clear but it seems that the TARGETuner requires a connection to the serial port,. The shack PC is connected already to the K3's RS-232 port, so this is not an option. A support person I spoke with at WMR didn't think it could read band data from the ACC port. No big deal, selecting a memory manually is easy, and the Auto Memory tuning mode works well enough if I really need hands-off band switching -- just tap the key and wait until the controller signals the all clear. Ideally the controller would be able to connect to a second serial port on the PC and read the frequency from Ham Radio Deluxe, N1MM, or whatever logging program is controlling the rig. Maybe a firmware upgrade will address this. Meanwhile, it's working as advertised and making my life a little bit easier when chasing DX all over creation.

Monday, January 19, 2015

Ground-Mounting the Tarheel Screwdriver



I have finally dispatched the tripod! The Tarheel is now mounted at ground level on a 10 ft. galvanized pipe driven about 8 feet into the ground (thankfully the ground is sand...). So now the radials extend horizontally rather than drooping down 3 or 4 feet like before. My SWR on 80m and 10m is still way out of whack -- the antenna will not tune under 1.5:1 below 5 MHz or above 26 MHz or so -- but 40m up to 12m I can tune it to 1.2:1 or better.

There was some very bad RFI on 17m the other day, getting into the upstairs stereo so loud that I could here it downstairs in the shack. This has been greatly improved, and I'm still operating without any sort of RF ground system and only 8 radials @ 9 ft. each. The next items on my To Do list are to increase the number of radials, hopefully longer than 9 ft., and to install some ground rods at each end of the coax to ground the antenna and all the equipment inside.

Sunday, January 11, 2015

Shakedown

Everything works, for the most part. I've pretty much concluded that the high SWR on 40m and lower is simply an installation anomaly. While it tuned 40m just fine in Texas, it never could tune above 15m. Now 40m is an issue, but I can get it as low as 1.5:1 on 12m, thus allowing me to turn on the heater if needed.

The plan of attack is:

  1. Get the antenna off that stupid tripod! A more permanent ground-mounted installation and more/better/longer radials should help.
  2. Move it away from the vehicles. Currently it is sitting a few feet from the Faraway Inn E150 cargo van, which is a lot of metal. Not helping, I wouldn't think.
  3. Replace the coax -- this run of RG8X is pushing 15 years, and has been outside the whole time.  When I order supplies for the low-band dipole I will add however much more I need for a good run to the Tarheel. Probably going to go with LM400.
  4. Ground the hell out of everything -- radios, antennas, and anything in between. The RFI into the stereos is a problem, I'm sure the neighbors are scratching their heads.

Until I get my SWR issue resolved, I'll be spending a lot more time lurking on 12m and 10m (the latter requiring barefoot power and the K3's ATU), slowly chipping away at whatever I come across. Which is a lot, since damn near everything is needed on those bands; I'm currently sitting at 8 DXCC confirmed on 12m, 42 on 10m, so there's lots of catching up to do.



In other news...

Kitten discovers the one warm spot in the shack -- my PS-430 12v supply.


Sunday, July 6, 2014

DXCC #199: 4J0SFR Azerbaijan

"Safari" DX-activators club station 4J0SFR heard on 15m CW late this afternoon very weak. I had to use almost all of the K3's magic bag of tricks to pull this one out of the static: bandwidth dialed down to 200 Hz, DSP Noise Reduction on the 1-3 setting, RF Gain throttled back, phones clamped to my head in binaural mode... all this made a very difficult to copy signal pretty darn readable. Got him after a few calls, sent my call a couple-three times to make sure he got it and once I heard it repeated back to me correctly I gave my "TU 599 dit dit" and hit the log submit button. #199 worked is in the bag. US QSL manager, no mention of LOTW on his QRZ page.

Of Triple Play and Antenna Maintenance

About time! I worked 13 Colonies special event station K2C in Rhode Island on phone and their QRZ page promises QSL via LOTW! That will be the last one for the phone portion of Triple Play. Now I just need West Virginia on CW. It kills me, I have QSOs in the log for both RI on phone and WV on CW (even have a card for RI), but the Triple Play award requires LOTW verification. Rules are rules. Unfortunately, West Virginia's second ARRL Centennial operating slot isn't until October 22, so to get this done soon I need to find another CW op in WV that uses LOTW. It could happen, I guess...

And another "about time!" -- almost a year after Tarheel sent me a replacement mounting bracket, I finally got around to swapping it out. The new mount fits perfectly. Now I can send the defective mount back and clear my conscious, as I promised to return it to them 11 months ago.

While I had the antenna broken down I did the recommended maintenance -- removed the plexiglass cover, clean the coil with alcohol and a ScotchBrite pad -- and took to the tripod's mast with some sandpaper to remove the black powder coat that I neglected to fully remove when I first set up the antenna in 2009. Now I know there is a good electrical connection between the mounting bracket and the ground radial plate.

I'm still missing a few radials, lost to the lawnmower no doubt, but I seem to be hearing a little better than I have been of late. Maybe it's just coincidental and the bands have simply improved the day I did antenna maintenance. It could happen, I guess...

Either way, I was able to add a few needed countries to my 17m count -- Romania, Belarus, Samoa, Philippines, Greenland -- as well as a few more of the 13 Colonies stations.

Thursday, April 10, 2014

KX1 Returns!


Just when I thought The Walking Dead Season 4 has ended, my KX1 has risen from the grave and walks among us once again. A few months ago when my latest bout of QRP mania struck I dug it out of a box where it had been packed since our last move. Upon opening it up I found that the AA batteries that I'd forgotten to remove had leaked and pretty much ruined one of the battery holders. No other damage was apparent, no corrosion on the circuit board or any components, but when I hooked it up to my 12 volt power supply it refused to play -- nothing on the display, no signals received, no output on key-down... just some hiss when the AF Gain was turned all the way up, and the little lamp on the side still lit up.

I put it aside for a few weeks until I had time to dig into it. When I finally found some time I began poking around inside, hitting any solder joints with the iron that looked suspect, checking voltages per the construction manual. I emailed Don W3FPR for some advice, he confirmed my voltage measurements and gave me a few things to try but no luck. Finally hitting the limits of both my tool and skill sets he suggested I send the KX1 to him so he can look at it with some real test equipment. So off it went.

Upon arrival at Don's place, he plugged it in... and it worked. Perhaps the US Postal Service fixed it en route. I dunno. Whatever made it happen, the thing suddenly sprang to life, and I'll take it. Don did a quick once-over and did a calibration while he had it, changed out the damaged battery holder, and shipped it back to me.

First night back, I fired it up at the desk with the 12 volt supply just to be sure, and sure enough it worked. Took a little while to reacquaint myself with all of the menu settings. It wasn't transmitting at first, until I figured out that the ATU setting was wrong. A few attempts to make some contacts were in vain, but it appears to be working fine.

The KXPD1 paddle is kind of flaky, or maybe its just me. Either way, I'm making more mistakes than I do with the Bencher BY1. Fact is I'm just plain better with a straight key than I ever was with paddles. I'm looking into a mini key for this KX1 and someone suggested the Palm Radio PPK; I also found the KK1 by American Morse Equipment. Both look like they'd work.

Palm Radio PPK
American Morse Equipment KK1
Meanwhile I keep working with the KXPD1. It's not horrible, mind you. The lack of mechanical paddle movement just reminds me of that old Heathkit μMatic keyer I built years ago that used capacitive touch paddles. Just plain weird. I spent about an hour calling W1AW/4 (unsuccessfully) on 40m tonight, sending cleaner as I started getting more used to the KXPD1.

Wednesday, March 26, 2014

Redefining The Radio (or, Nine Months With The Flex 1500)

Cooler than penguin poop.
I've not written much about the Flex 1500 since I brought it home about nine months ago, just a few mentions here and there. It doesn't get nearly as much use as my K3 but I reckon I've had enough cockpit time to become familiar with all the controls and tweak the software that an update might be in order.

Why the Flex 1500?
I first became interested in the 1500 shortly after it was announced by Flex Radio Systems. I was QRT at that time but I still kept my ear to the ground with respect to new equipment, especially QRP rigs, and this one really grabbed my attention. Around the same time Elecraft announced their KX3. I'm encouraged to see these two companies catering to the "little pistol" QRP op even as they shake up the "big gun" high-end/high-performance transceiver market with their K3 and Flex 5000/6500/6700 models. Especially fascinating is the different approach each of them take with respect to SDR design: the Flex 1500 is a black box device that sites between a antenna and a PC; the KX3 is a self-contained SDR radio that can be used independent of a computer (or an AC outlet, for that matter). Two completely different design philosophies.

Of course I wanted both radios; fiscal restraints, however, forced me to choose one or the other. I opted for the Flex partly because I really wanted to explore their universe a little bit after years of being fully in the Elecraft camp, and partly because of price -- the 1500 costs $699, the KX3 starts at $899, and the extra few hundred bucks really wasn't in my budget at the time. So the 1500 it was.

I envisioned this radio fitting into my current station primarily as a low-power digital-mode radio, and also as a second receiver. Now that I've become more interested in getting involved in QRP activities I can see it getting more use as a CW rig as soon as I work out a way of switching my key and paddles easily between the Flex and the K3.

First Light
My first impressions were mixed -- the initial PowerSDR setup was fairly straightforward but I had some issues getting it configured with the Virtual Audio Cable (VAC) and Virtual Serial Port (VSP) software and was finding some latency issues in CW mode  -- a very short but noticeable delay between key-down and hearing the sidetone that really is disconcerting while trying to send code at anything above Novice speed. It took some experimenting with the audio and DSP buffer settings before everything worked, if not perfectly then well enough. Nothing especially problematic, just a case of needing time to get acquainted with the intricacies of the different applications needed to get the rig working in a usable fashion.  

I eventually got everything working perfectly with both VAC and VSP. This allows a single USB cable between the 1500 and the Dell laptop to be used for the PowerSDR software (which is, for the most part, all of the radio after the RF stage), Ham Radio Deluxe (for additional rig control and logging), and DM780 or JT65-HF (for digital modes). No audio cables required!

The buffer and latency settings took a bit more work. Flex's Knowledge Center and the Flex-Radio email reflector are both great sources of information for dealing with these issues and any others. In particular, I found this post by VE3WMB to be especially helpful as a starting point for getting the 1500 dialed in. I also got some key advice on VAC setup from the Flex Radio SDR community on Google+. While there is still some latency when operating CW, it is useable in that mode, although I am limited to slower sending speeds than I'm comfortable with. The only way I can get around it is to reduce the CW buffer, which in turn limits the minimum bandwidth settings. Since others have reported success in eliminating this CW latency I'm still hoping to find the magic settings someday. 

Operating the Flex 1500
I noted above that the 1500 was purchased mainly for digital modes, and it's worked out extremely well for that purpose. I've been able to dabble with JT65 for the first time and have made some DX contacts running 1.5 watts. PSK operation is quite good, too. Channeling the audio I/O as data via USB seems to deliver a cleaner signal to and from DM780 than I'm getting from the desktop PC/soundcard setup I use with the K3. This is just the impression I get, I have not done any tests to support this hunch. At the very least, the possibility of RFI getting in through audio cables should be a non-issue now.

First, the positive:
  • The cornerstone feature of this rig is it's spectrum display. It makes it easy to spot weak signals that are barely audible -- the kind you would tune right past if you were turning a VFO dial on a conventional rig. See a line on the waterfall, click on it and you're tuned! More on this below.
     
  • I expected a great receiver from the reviews and receiver tests I'd read before purchasing it but it still took me by surprise. On CW the 1500 is simply amazing. The bandwidth filtering and it's ability to dig out weak signals is a match for the K3 in all but the most extreme cases, at least to my ears. It sounds great on SSB, too, though I haven't done much listening in that mode.
     
  • MultiRX is super-useful in a pileup situation, when I want to listen to my RX frequency (the DX station) in my left ear and monitor my TX frequency (the pileup) in my right. Unfortunately it's not possible to use different bandwidth settings for each channel. 
On the downside:
  • I find the Noise Blanker (NB) to be a bit disappointing. Perhaps I've been spoiled by the K3's NB, by far the best I've ever experienced. If it's just a simple matter of not having the the parameters set correctly, then I'd say that's one of the problems -- it shouldn't take that much tweaking and effort to work properly. I've spent a lot of time adjusting the 1500's NB settings and I'm unable to find the sweet spot where the background electrical noise that often plagues my QTH is eliminated without causing distortion to the desired signal. No such issues with the K3, where I can just increase the NB level until it distorts, then back it up a little.
     
  • The DSP Noise Reduction (NR) is OK, but again not nearly as effective or easily adjustable as the K3's NR. I rarely use it.
     
  • Portability is another issue. "QRP" is often synonymous with "portability," and this rig simply ain't. If field operation is high on your priority list, either look elsewhere or prepare to lug around a bunch of batteries to power both the 1500 and a laptop.

User Interface
Despite it's (relatively few) shortcomings, I love the Flex 1500. Still, the K3 is my go-to rig and the Flex has been getting only occasional use. Why? It's not merely because of the additional output power of the K3 -- that may be part of it, but I'm fairly certain I'd do the same if the Flex were a 100W rig driving an amp. And not because of any performance issue, either -- as I noted above, the Flex is pretty much equal to the K3, and possibly better in terms of audio quality (my K3 is one of the early ones and has none of the revisions that address some audio distortion issues).

More than anything, it's just that I still prefer a conventional button-and-knob rig to a point-and-click rig. When I want to turn the volume down, it's unintuitive for me to fumble with the mouse and drag a slider on a computer monitor. When I want to change bands, it seems so much more natural to push a physical button than click on a virtual one. Is this just a generational thing? Would a younger user, someone who has been exposed to computers from the cradle, be more comfortable with PowerSDR and find a conventional radio to be a quaint relic of the past? I don't know.

Whether I'm "old school" or just stubborn, the K3 suits my operating style. This often includes tuning slowly across the band listening for weak signals with my eyes closed, something that is not easily done with PowerSDR. I ride the RF Gain control, too, and again find it cumbersome to work a slider control with the mouse to do that. I suppose the awkwardness of PowerSDR can be lessened with time as I use it more, but I don't think the point-and-click interface will ever match the tactile feedback I get from an honest-to-God front panel. 

But then there's the panafall display! That is what for me sets this radio apart from anything I've ever experienced before. PSK users know all about waterfall displays which show signals in the audio passband; panadapter spectrum displays have been a mainstay on rigs from Icom since the IC-780 and R-9000 in the 1990s and now feature prominently on rigs from nearly every manufacturer. The panafall display is a combination of the two, showing real-time band activity in both the frequency/amplitude and frequency/time domains.
PowerSDR's Panafall Display
A CW or digital signal too weak to really stand out on the panadapter display will often still leave a faint line on the waterfall. These are the signals that one risks tuning past on a conventional rig. But on the Flex... see a line, point and click, bang. It almost feels like cheating.

Here's an example of a station (HC5AI) I found while doing some A/B tests between the 1500 and the K3. It was so weak that it didn't register at all on the panadapter display (top) but was clearly visible on the waterfall (bottom):


Odds are that I wouldn't have found this signal if I were just tuning the band on my K3 or if I were using just the panadapter display on the 1500. (This was one of those extreme cases in which the K3 beat the 1500 in terms of copying a signal so far down in the background noise that it was barely audible. Not a huge difference in readability, but noticeable.)

So why not use just the waterfall? Why have a panadapter display at all? Maybe the panadapter is just gravy, but I find it to be very useful when there are a lot of signals on the band, especially during a contest or while hunting DX. Observing a pileup of big signals spread out over a 2-3 kHz range just disappear when a weaker signal starts transmitting on a lower frequency -- the telltale sign of a DX operation -- is something that just doesn't come across as well on the waterfall. On the other hand, the waterfall is my tool of choice when monitoring a quiet band, especially the higher bands which open and close intermittently at night. That's when I will just leave the waterfall on and wait for the broken lines to appear.

This panafall method of finding and tuning weak signals is a paradigm shift for me, another one of those things that I could never have imagined when I was a kid listening to hams on a DX-160 receiver with a simple bandspread dial. Back then, a simple digital frequency readout seemed miraculous to me! I'm happy to say it's not unique to Flex radios these days, either. The Elecraft P3 panadapter option for the K3 includes this feature; NaP3, an SDR software program based on the open-source PowerSDR code, brings many of PowerSDR's user interface to the KX3 and, with devices like the LP-Pan, other rigs with suitable IF outputs; most if not all other SDR radios support software with similar functionality; the Kenwood TS-990S has it on its built-in display, and I expect Yaesu and Icom will follow soon enough. Maybe someday a panafall display will be as ubiquitous as digital readouts and computer interfaces are on radios today.
Elecraft P3
NaP3
Kenwood TS-990S
Just for the hell of it I recently hooked the K3's IF output up to the Flex 1500 and tuned the 1500 to the K3's IF 8 MHz frequency. The results were not great -- the signal level of the IF signal was pretty low so only the strongest signals on the band were showing up in the PowerSDR panafall; tuning the K3 up in frequency moved the waterfall in the opposite direction (i.e., higher frequencies are to the left of the center marker, lower to the right), something that makes perfect sense if you think about it but still less than intuitive when operating; and of course the point-and-click facility was missing. In all, and interesting exercise but a rather useless way to add a spectrum display to the K3.

My Wish List
Two things would make me even happier than I already am with this radio: A Macintosh version of PowerSDR, and an internal ATU option.

The $900 Question
Anyway, these are my random thoughts about the Flex 1500. If I had to do it all over again, would I have gone for the KX3 instead of the Flex 1500? I've been asking myself that question a lot lately and the answer is a definite and resounding "maybe." The appeal of having a stand-alone, fully functional QRP rig that I can use outside the shack wasn't a huge factor for me last June. Today I really wish I had one. I have no complaints with the Flex when it's used as I originally intended -- as a digital-mode rig -- and actually use it more than the K3 these days for PSK. At the same time I wish I had a KX3-type rig that I could use both in the field and in the living room.

That said, I have no regrets. I chose the 1500 knowing what it was and how it worked, and it honestly has met all my expectations. So I don't know if I'd go the other way and get the KX3 instead of the 1500. Hopefully I will own both someday because they each fulfill a particular need for me.



Resources and Links
Monitoring Times review by NT0Z - Part 1 and Part 2 (PDF format)
DL4YHF's Overview of Spectrum Displays
W9XC: Flex 1500 CW Latency Issues

Wednesday, February 26, 2014

Telegraph Apparatus

Only $15.95 for a Vibroplex Bug? I'll take two!

From the 1945 Radio Shack catalog.

Monday, December 16, 2013

2013 ARRL 10M Contest

My first all-CW effort in a contest that was mixed mode. Also the first test in which I used N1MM Logger to generate the CW. This worked swimmingly. No more pushing buttons on the K3 to send my call and exchange from CW memories!

Bad noise the whole weekend -- not just the usual electrical noise (though that was bad enough) but the neighbor's dog would not shut up. And the train... folks, never buy a house across the street from the railroad tracks. Union Pacific is at the top of my shit list this weekend.

QRV a bit under 12 hours total operating time with lots of short breaks. Since the Tarheel only tunes up to 21 MHz, I had to keep the amp off and use the K3's ATU to match the antenna. Consequently, I could only hear and work the loudest signals on the band.

In the end, 22 states (not incl. KL7 and KH6), 9 CanProvs, and 29 DXCC. No new all-time countries for me, but every one of the 29 is new on 10m, a band for which I have exactly three QSOs in the log in 26+ years. Got 8 of the 24 state I need for the CW portion of Triple Play (five already confirmed on LOTW!).

Wednesday, November 6, 2013

Saturday, August 3, 2013

K3 Receiver Sensitivity Loss With KPA500

Ever since adding the KPA500 to my station, the bands have been dead. Perfect timing as always, or so I thought at first. After a week and all propagation indices suggesting the ionosphere had not in fact packed up and left, it slowly began to dawn on me that perhaps there was something wrong in the signal chain.

I went as far as bypassing my Delta 4 antenna switch and connecting the antenna feedline directly to the amp -- a drop in signal strength being one of the signs that the gas cartridge might have gone bad --  but no change. I did not, however, bypass the amp and connect the antenna directly to the K3.

Finally, I saw a thread entitled K3 Receive Attenuation with KPA500 in Operate while perusing the Elecraft email reflector and it all clicked. Brian W3BW wrote:
I am running a newly assembled "K-Line" --- K3/100, KPA500 and KAT500.  The K3 is pretty "loaded" with KRX3, KAT3, KXV3A, etc.
I just noticed that received signals are down 4 S-units when the KPA500 is in Operate.  In Standby, signals pop right up. 
Reading past reflector emails on the topic, I found one thread that suggested this may have to do with the state of the KPA500 PTT.  I found that pulling the PTT RCA plug out ended the problem. 
This 4 S-unit drop was exactly what I was experiencing. A response from Don W3FPR confirmed it to be the PTT cable used in parallel with the KPAK3AUX control cable:
I have heard this before, and as I recall it has to do with the DB15 cable and the PTT cable when used together. 
Are you using the PTT cable in addition to the cable from the K3 ACC cable?  If so, pin 10 of the cable should not be included.  See the note on page 8 of the KAT500 manual. 
Normally you would not have to use the PTT cable with the K3.
The KPA500 manual does not mention this, at least not clearly, in the Cabling instructions:

  1. Connect your station ground to the GND thumbscrew {10}. A good station ground is important for safety and to minimize local radio frequency interference (RFI).
  2. Attach the RF INPUT {11} to the output of your driving transceiver or transmitter using a 50 ohm coaxial cable with a PL-259 male connector on the KPA500 end. The driving transmitter must supply up to 40 watts for full output from the KPA500.
  3. Attach the RF OUTPUT {1} to a suitable load with an SWR of less than 1.5:1. A dummy load is strongly recommended for initial testing.
  4. Connect the PA KEY {6} to the driving transmitter Key Output. A suitable cable is supplied with your KPA500. The transmitter must ground this circuit during transmit while sinking up to 1 mA from the PA KEY line. If the transmitter Key Output is not a contact closure or equivalent, it must be at a level between +4 and +16 VDC during receive. (Compatible with all known transmitters. No key line buffer required.)
  5. Optional: An auxiliary (AUX) connector is provided that permits more closely integrating the operation of the KPA500 with many transceivers, including the Elecraft K3. A suitable cable for use with the K3 is available from Elecraft. See AUX Connector Interface on pg 18.
  6. Optional: RS232 (PC) {9} connects the KPA500 to your personal computer with a standard 9-pin serial cable. Required for updating the KPA500 firmware.
  7. Optional: RS232 (XVCR) {8} connects the KPA500 to a Kenwood transceiver using a standard 9-pin serial cable. This connector cannot be used to update KPA500 firmware (see pg 14).
  8. Optional: ALC OUT {7} provides level information to control the driving transmitter RF level. The output is negative-going from 0 VDC to -12VDC. 
I read the above as, "You need to connect the PTT cable, and the AUX cable if you want additional control of the amp with the K3." And what receiver sensitivity might have to do with the PTT key line is beyond my understanding. But at least I had a clue.

Removing the PTT cable seems to have done the trick for me. Now both signals and background noise are back to normal levels.


Sunday, July 28, 2013

2013 RSGB IOTA Contest

I didn't really give this any serious effort, did not even get on the air until after 0200, so I'm not even going to send in a log. But it gave me a chance to give the KPA500 a good shakedown and she performed as well as I could have expected. The screwdriver antenna is still the limiting factor for me -- no amplifier is going to help me work DX that I can't hear. And it was slim pickings for a while. But when 20m opened up to the Pacific after 0330, I cracked a small pile and worked South Cook Is. (E51GC) on the first call.

In all, I only made 20 contacts (16 DXCC, 10 WAZ), picked up a new one (E51), worked Corsica (TK) and Ireland (EI) for the first time since moving to Texas, and the usual assortment of VK, ZL, KH6, and South America/Caribbean stations.

Saturday, July 27, 2013

KPA500 Passes Smoke Test


The KPA500 arrived Thursday. I started assembling it after work and got as far as sorting the parts and mounting the tilt bail and feet, power supply module, and left side panel. Finished the job on Friday night... er, Saturday morning, around 2am. Hit the sack after testing into the dummy load. Looks like full 500w takes about 35w drive from the K3 on 20m.

Wednesday, July 17, 2013

KPA500 on the way


There goes the grocery money for the next two months. But it had to be done.

Friday, July 5, 2013

June 2013 Wrap-Up

DX - I worked just 28 countries from June 12 through June 30, giving me four new DXCC (BV, DU,YB, and ZD7) and three new CQ Zones (24, 27, and 28).

So with DXCC behind me Triple Play has become my short-term goal. Digital is done, all 50 states confirmed on LOTW. Thirteen states are needed on phone, I should be able to close that column out with a few contests. CW... OK, this will require real commitment.

DXCC count as of 05-July
CW - To this end, I've been working some DX on 20m CW, which is great since "TU 5NN 5NN 73 DE WW2PT" is about the extent of my CW vocabulary at the relativistic speeds typically found at the extreme low ends of the bands. I'm getting more comfortable venturing into that territory, however. I can copy my own call at ludicrous speed, and that's pretty much all that's needed 90% of the time.

I've also been listening a lot to the QRP guys up around 14060; they usually operate inside my 15-20 wpm comfort zone. Haven't worked any of them, mind you -- I seem to get paddle shy at the prospect of having someone starting an honest to God conversation, sending me into a panic spiral once the QSO strays from the signal report exchange. It's completely psychological; if I'm not working a station, I can comfortably copy a CW QSO at this speed. Only when it's my QSO does the brain meltdown occur. This too shall pass.

Flex 1500 - Loving the new toy, for the most part. Still messing around with the settings, trying to get the noise blankers set to best handle the electrical noise ever present at my QTH. Unless I'm just not finding the optimum settings, I have to say the noise blankers are no match for those in the K3. The filtering, on the other hand, is simply amazing. Clean sounding CW right down to 25 hz. At times some distortion of signals starts to occur, gradually increasing until I have to reduce the size of the audio and DSP buffers. This makes the distortion go away, but also limits the minimum passband width, apparently. Not sure why this is happening, since CPU usage doesn't seem to be excessive (usually hums along in the 15-25% range while running PowerSDR, Ham Radio Deluxe, and Chrome). It's a clean install of Windows 8 (yeah, I know...) with a minimum of junk installed. Hasn't happened in a while, however, so maybe operator retardation is to blame.

I've been unable to install the trial version of VAC, and I've not yet wired up cabling for audio I/O, so no digital ops with the Flex as of yet. Really was hoping to run both control and audio through a single USB cable just to simplify things. But VAC simply refuses to install (I forget the error message). Compatibility issue with Windoze 8?

Also ran into latency issues with the CW keyer. Messing again with the buffers fixed the problem at the time. I've since set all buffers back to max size and there no longer seems to be any issue with sending CW. So again, maybe something I did.

So I continue to play with the Flex. Some CW contacts, but haven't been able to work anyone on phone. Patience is not one of my virtues, so if I don't get through after 5 or 6 calls, I switch over to the K3 and almost always get through at 100 watts. I remind myself that I didn't buy the Flex 1500 to work DX on phone.

Hardware - When putting the shack back together I discovered three pieces of gear were not working: the MFJ-267 wattmeter/dummy load is now just a dummy load; the meter is completely inoperative, as it the meter's light. My KX1 appears to have gone belly-up on me; just a very faint "0" on the display and no audio output at all. And my NCS-3230 Multi-RX audio console had no audio output, even though it powered up just fine and the input peak lights would flash when I turned the volume up on the radios.

Getting this last issue sorted out was No. 1 priority because the Multi-RX is a central fixture of my station -- audio from all radios go through it and feed a single set of speakers -- so having it out of action was not good. I emailed NCS to ask about possible repair suggestions and got a response from Doug, K4SWJ who told me he sold the company and the new company no longer supports the ham equipment, but he did offer some ideas about the cause. Sure enough, it was an internal fuse on the input of the audio output amp chip.

Since the chip manufacturer later determined that there is no need for the fuse, Doug advised simply soldering a jumper wire across the blown fuse. I did just that, and everything is working again. Image below shows the location of the fuse, in case anyone stumbles upon this page while Googling about their deaf Multi-RX.

The dead KX1 is more troubling, I have no test equipment anymore other than a voltmeter and honestly don't even know where to start. I suppose I'll apply power and start measuring voltages to see if I can find something obvious. If not, I guess off to Elecraft it goes. I really was hoping to finally building and adding the 80/30m board that I've been sitting on for years. Oh well.

As for the MFJ-267... I'll deal with it later. The SWR-Wattmeter never really worked that well anyway, the dummy load still works, and I have a Daiwa 410 meter that I've been using in its stead. From what I've been able to discover online, I'm not the only one who has had issues with this unit.

And that's June in a nutshell.