Send DX Hints or Kinks to any of the Blog Authors shown below.

Wednesday, February 27, 2019

Have You Worked UA4WHX?

In the last few days, Vladimir Bykov, UA4WHX, has been operating from Mayotte as FH/UA4WHX.  You can see some photos from his current operation by visiting this DX-World page (https://dx-world.net/fh-ua4whx-mayotte/). FH, Mayotte, is only No. 103 on the Club Log Needed List.  However, I'm sure Vlad is filling in MANY Band/Slots for a lot of folks and even handing out the occasional ATNO!

Do you realize just how prolific this single DX'peditioner has been over the years?  He has operated from dozens and dozens of countries giving New Ones to thousands of DX'ers.  Just during the last month he has operated from the following places.  Click on the callsign to link to the DX-World page describing the operation with photos.  S70VB - Seychelles, 3B8VB - Mauritius, 3B9VB - Rodrigues Island, FR/UA4WHX - Reunion Island, and currently FH/UA4WHX - Mayotte.  Particularly note the write-up on the 3B9VB operation regarding Cyclone Gelena passing right by Rodrigues Island while Vlad was there.

He is a one-man operation running just 100-watts to wire antennas.  Check out his innovative antenna set-up on his QRZ web page.  Note that he also holds a U.S. Amateur Extra Class license - AC4LN.

Unfortunately, Vlad does NOT use LoTW so you will need to QSL him directly.  He has detailed instructions on his QRZ web page about sending for a QSL.  He does accept QSL requests via PayPal so that should speed up the process for sure.

I have scoured the Internet for an exhaustive list of calls for UA4WHX's operations but can not find such a list.  So, I used a few sources to put together the following list.  I plan to check this list against my own log to see if I have some gems just waiting for a QSL from Vlad.  You can see the actual QSL's for many of the calls below at this web site.  Also on that web site is a link to a 2009 audio interview with Vlad by OE1WHC.  You can gain some very interesting insights into Vlad himself and what it is like to operate from these DX locations by listening to this 14 minute interview.

Here is the list of callsigns which I have found were UA4WHX operations:  3B8VB  -  3B9VB  - 3D2VB  -  3DA0VB  -  4K0VB  -  4LOB  -  4O7VB  -  4S7VG  -  4W0VB  -  5H3VMB  -  5H3VNS  -  5R8VB  -  5T5TI  -  5T9VB  -  5W0VB  -  5X1VB  -  5Z4/UA4WHX  -  6W/UA4WHX/P  -  6Y5/AC4LN  -  7P8VB  -  7Q7VB  -  7V7V  -  8P9/AC4LN  -  8Q7VB  -  8R1/AC4LN  -  9A8VB  -  9H3WHX  -  9J2VB  -  9U0VB  -  9X0VB  -  9Y4/AC4LN  -  A25VB  -  A35VB  -  C50VB  -  C91VB  -  CE/UA4WHX  -  CE0/UA4WHX  -  CE0Z/UA4WHX  -  CE7/UA4WHX  -  CE8/UA4WHX  -  CE9/UA4WHX  -  CN2VB  -  CP/UA4WHX  -  CP4WHX  -  AC4LN/CT1  -  CT8/UA4WHX  -  CT9/UA4WHX  -  D20VB  -  D44TVB  -  D60VB  -  E40VB  -  E7/UA4WHX  -  EA8/UA4WHX  -  EA9/UA4WHX  -  ER0VP-UT/UA4WHX  -  ES0VB  -  EX/UA4WHX  -  EY8/UA4WHX  -  F0/AC4LN  -  FH/UA4WHX  -  FK/AC4LN  -  FR/UA4WHX  -  FW/AC4LN  -  H40VB  -  H44VV  -  H7/AC4LN  -  HB0/AC4LN  -  HB9/AC4LN  -  HC2/UA4WHX  -  HC8ART  -  HH2/AC4LN  -  HI8/AC4LN  -  HK0/UA4WHX  -  HK3/UA4WHX  -  HP1/AC4LN  -  HP8/AC4LN  -  HR1/AC4LN  -  HR2/AC4LN  -  IT9/UA4WHX  -  J20VB  -  J3/AC4LN  -  J73/AC4LN  -  J8/AC4LN  -  JT1FDC  -  JY8VB  -  KD4DZH  -  KH0/AC4LN etc.  -  KH6/AC4LN  -  LU/UA4WHX  -  UA4WHX/CX  -  LY/UA4WHX  -  O19VB  -  OA7/UA4WHX  -  OD5/UA4WHX  -  OJ0/UA4WHX  -  ON9VB  -  P29VVB  -  PY/UA4WHX  -  PY0/UA4WHX  -  PY8/UA4WHX  -  PZ5VB  -  R/AC4LN  -  R00BVB  -  R00KVB  -  R00QVB  -  R11PVB  -  RI0BV  -  RI0BV/P  -  RI0KV  -  RI0POL  -  RI0QV  -  RI0QV/P  -  RI44ANT  -  S70VB  -  ST2VB  -  SU9VB  -  T10VB  -  T20VB  -  T30VB  -  T88VV  -  TG4/AC4LN  -  TI1/AC4LN  -  UA4WHX/2  -  UK/UA4WHX  -  UN8/UA4WHX  -  V31BV  -  V51VV  -  V63MB  -  V73VV  -  VK8VB  -  YJ0VB  -  YL/UA4WHX  -  YS1/AC4LN  -  YU9VB  -  YV5/AC4LN  -  Z2/UA4WHX  -  Z38VB  -  ZA/UA4WHX  -  ZK1/AC4LN  -  ZK2VB  -  ZP9/UA4WHX

Sunday, February 3, 2019

Exporting WSJT-X logs to LOGic & other logging programs

My logging program, LOGic, has been promising for many months to add a fix that will allow WSJT-X QSOs to automatically become a part of my LOGic log.  I have been logging those QSOs on paper and then later typing them into the LOGic program.  But I finally got tired of waiting for the fix and decided to learn how to export my FT8 and other QSOs out of WSJT-X and into LOGic. 

I thought that would be simple.  I was wrong.  It took many hours for me (not the most computer literate guy in the world) to finally make these transfers work quickly and smoothly.

WVDXA President Clark Stewart W8TN suggested I put a "how-to" into writing in case others have been having similar problems with their logging programs.  I won't go through all the other methods I used, all of them taking several steps and wasting time before QSOs would finally get into my logging program's log, but here is the explanation of what I finally did.

First, in order to import into LOGic I must click on an "import" tab and then an "ADIF" dropdown tab.  That brings up a window that allows me to browse for a file's location.  I can then browse to most places; like desktop, documents, downloads, etc.  However it will not find the directory where wsjtx_log.adi is located.  Specifically it will not browse me to C:\Users\Garry\AppData\Local\WSJT-X\wsjtx_log.adi.  Even when I typed all that into Logic's window, it would not take me there.  It just kept telling me the file was not found and instructing me to check spelling and try again.  I must have done this 50 times over the past few days.

However, I finally discovered a way to get LOGic to the right location.
I remembered that LOGic's export window always opens at the last place that it found and used an export file.  I figured that LOGic's import window would do the same.  If I could only get it to the right location in the first place, it ought to automatically go there the next time.  So, I went into the WSJT-X program and put my cursor on the wsjtx_log.adi file and right clicked.  That took me to a "send to" button where a dropdown allowed me to send a shortcut to the desktop.  LOGic's import window went there without problem and did the import, and now (voila) every time I call up LOGic's import window it takes me to C:\Users\Garry\AppData\Local\WSJT-X\wsjtx_log.adi automatically.  Eureka!
Whew.  What a struggle.  Now the process is simple as long as I remember to erase the log file in WSJT-X after each export.  That way only the new contacts are added to my log each time I import in LOGic.  Otherwise the QSOs that were transferred before will be transferred again putting duplicate QSOs into my log.