QRZ.COM
Please login help/register callsign: password: secure login
Database News Forums Swapmeet Resources Contact
 13:26:20 UTC 30 Oct 2014 
Advanced Search Current Hot Callsigns XML Logbook Data QSL ListMaker Database Downloads DX Spotting Network Ham Club Database QSL Corner Top Web Contacts Expired Callsigns QRZ's 1993 FCC Database Daily Update Reports Just Added Callsigns Database Help Forum
Amateur Radio News General Announcements Special Events, Contests, etc. Hamfests and Conventions Silent Keys Headlines
Forums Home Discussions, Editorials, Talk Technical Forums Logging and Contesting RV and Mobile Help Forums
Ham Radio Gear for Sale Ham Made Gear General Merchandise Swapmeet Hot List Ham to Ham References Stolen Radios, Scams and Rip-offs
Site Menu... Practice Amateur Radio Exams Amateur Radio Study Guides Online License Renewals License Wall Certificates Commercial Ham Radio Links DX Country Atlas Grid Mapper Ham Radio Trivia Quiz Life Member Honor Roll
Help Desk, for accounts, lost passwords, etc. Add your callsign to QRZ Subscription Services Users Help Forum Frequently Asked Questions - FAQ QRZ en Espanol Privacy Statement Advertise with QRZ List of Current Advertisers About QRZ Donate to QRZ Contact us
ad: L-HROutlet
ad: l-assoc
ad: l-Waters
ad: l-tentec
ad: l-gcopper
ad: l-innov
ad: l-WarrenG
ad: l-rl
N9MXI USA flag USA

Login is required for additional detail.

QSL: BEING NEW TO HF, I MUCH PREFER A PHYSICAL QSL CARD (DIRECT.

Email: Login required to view

XML Subscriber Lookups: 1955

IMPORTANT NOTE:  As of 23-June-2014, due to a bug introduced into HRD Logbook v6.2 (previous versions are okay) that causes the wrong time to be logged if entering local time, around 70 of my log entries were incorrect.  I believe I've gotten them all corrected, but if you don't see a match for a QSO you made with me between 2-June-2014 and 23-June-2014, let me know.  If you want to know more details about the bug, scroll to the bottom of this page.

QSLs: Being relatively new to HF, I prefer a physical card in the mail (direct). If you send one,I will send one in return.
I appreciate, but do not require SAE and/or postage.
  • Outside the U.S.
  • One green stamp or a U.S. postal "global forever" stampwould be appreciated, but not required.
  • If you don't want my reply sent as a postcard, a SAE would be great.
  • Within the U.S.
  • If you don't send postage or SASE, I will send my reply as a postcard
  • If you send post-card postage ($0.34 stamp), I'll send my reply as a postcard and will appreciate your stamp.
  • If yousend letter postage (domestic "forever" stamp), and/or a SAE, I'll enclose my reply in an envelope.
  • If you send me a winning Power Ball lottery ticket, I'll hand deliver my QSL card. ;-)

I log all of my QSOs to HRDLog.net, ClubLog.org, QRZ.com, eQSL.cc and LOTW.
(I upload them at least once every month, usually more often, butdon't expect them to be there immediately,
except for HRDLog.net, which is automatically updated each timeI create a log entry)

You can view pictures of the QSL card's I've received and more at:
http://www.facebook.com/N9MXIsHamRadioPage.

(Note: I'm not sure how often HRD updates their web site, and once it has, the QSO log and mapbelow won't update unless you refresh your browser.)

My QTH is Atlanta, GA, but I got my call sign when I was living in IL, where I'm originally from, and thus the "9". Maybe someday (after I get my Extra-class license) I'll get a new, vanity call and stop confusing everyone with the 9 in 4-land.

My station is proof that you don't need anything fancy to get started on HF. The map below shows where I've worked from my home in Atlanta since I first got on HF on 1/24/2011, and all I have is 100 W (Kenwood TS-590s) and a G5RV* inverted-vee with the apex at only about 32'. In just 1 day shy of 10 weeks since I first got on HF, I hadworked 76 countries on 6 continents, and all 50 states. (I sure wish people were good about responding to QSL cards though, because I'm still missing many.)

*As of 16-Oct-2011 I've added a 10m dipole that I built. As 10m opened up more, I realized how bad the G5RV is at 10m. The dipole is hung about 10' lower than the G5RV, but it is an average of three S-units better (TX and RX). The G5RV works great at 80, 40 and 20m, but terrible at 10m...yet even so I was making some good contacts, including Japan, with it. Some day I hope to add a Hexbeam.

*Update as of 24-Oct-2012: Well, I finally put up a tower and HF beam -- specifically a 40' Universal Towers aluminum, free-standing tower with a Mosley TA-63-N (6-band, 3 active elements per band) on top of the tower, with a V/U vertical above that. It's still too new to comment too much on the beam, but it definitely make huge difference on the bands that I was relying on the tuner for w/ the G5RV. Still, I was pretty impressed with how well the G5RV served me....for thousands less $$$.

Worked All States

Incidentally, no, I didn't make my own G5RV. I have W8AMZ's version, from eBay, which is constructed far, far better than anything I could have done myself. Fantastic construction. I wanted something that would last a long time. The 10m dipole I made is constructed similarly (though maybe not as tough), but built into it (around the 4" PVC I used for the center insulator) is an RF choke made from about 19' of Belden 9907 I had laying around.

Whahoo! As of 1-Dec-2012, I received my DXCC award. Though I've had well over 100 DXCC entities confirmed with QSL cards for a while, I finally hit the 100 mark on LOTW, so I took the easy / electronic route and applied for the DXCC certificate through LOTW.

ABOUT THE MAP BELOW: MOST, but NOT ALL points on the map below are accurate -- only as accurate as their info on QRZ.com (where HRD pulls the info from) -- but they should be very close.

Note that "Other bands" is 60m, and it apparently shows 12m &17m as just "WARC" (it doesn't separate them). The legend also doesn't match for mode. Most are voice (square), but I don't use CW, so those circles are SSTV and/or PSK31, which are supposed to be triangles per the legend.

Yes, that yellow dot at the bottom-center isSouth Pole Station.
I have worked all 7 continents, 230 "countries" (DXCC entities) - that's 228 + Alaska & Hawaii - as of 21-June-2014 (Note: "countries" includes various islands.) View the QSK cards I've received and more at www.facebook.com/N9MXIsHamRadioPage


Click here to view on Google Maps and from there, there is a link to view on Google Earth
IMPORTANT NOTE: The above Google Maps linkrequires you to have an account on hrdlog.net and be logged into it within this browser session...but it will be completely up-to-date.

If you don't have an hrdlog.net account, here is a manually updated (and thus maybe up to a month out of date) set of contacts:
- Click here to view in Google Maps
- Click here to view in Google Earth(requires that you have Google Earth installed)


Here's the "new" (24-Oct-2012) antennas & tower:

 

PLEASE FOLLOW THE

CLUB MEMBERSHIPS:


About that HRD 6.2 Logbook Bug I mentioned above...

The bug in HRD Logbook happens only in v6.2 and only when you have it configured to accept local time.  (If you have it configured to be entered as UTC, it's fine.)  If you have it configured to enter local time, it messes up the conversion to UTC before saving it to the database as follows.  Lines crossed out have been verified by myself as fixed in the August 10, 2014 (v6.2.7.285) release, while non-crossed-out lines remain an issue until a future update, and blue lines are a new behavior as of v6.2.7.285 (as a result of fixing the issues in the crossed-out lines).

  • If the COMPUTER's current date/time is NOT during Daylight Savings Time:
    • If the log date/time being entered as local time is not during Daylight Savings time, it logs correctly.
    • If the log date/time being entered as local time is during Daylight Savings time, it logs it as one hour into the future (fails to account for DST when converting to UTC).
  • If the COMPUTER's current date/time IS during Daylight Savings Time:​
    • If the actual UTC of the log date/time being entered as local time should be anything other than the 00 hour UTC, it logs it as one hour behind. (It subtracts one hour from UTC from what it should be).
    • If the actual UTC of the log date/time being entered as local time should be during the 00 hour UTC, it logs it as 23 hours into the future. (It subtracts one hour, making it 23:xx, but doesn't decrement the day when it went back across the date boundary, thus it gets logged as 23 hours into the future from what it should be.)
    • If the log date/time being entered as local time is during Daylight Savings time, it logs correctly.
    • If the log date/time being entered as local time is not during Daylight Savings time, it logs it as one hour into the past (account for DST when converting to UTC when it shouldn't have.)

​Additionally, any time you go back in and edit anything in a record -- again, only when you have HRD Logbook UI to enter local time -- it (re)applies the same bad algorithm, subtracting yet another hour (or adding 23), and I know I've edited W1AW/# QSOs because now and then I've saved them with the default (wrong) CT state, and I edit them to correct the state.  Others I've remembered to edit the state before initially saving.  Therefore, I really don't know which once are off by -1 hour vs. off by -2 hours (or potentially +22 hours).  Ugh.

Yeah, pretty aggrivating to say the least, especially since long-time working functionality broke.  Thankfully, HRD support said they already have fix, and it will be in their next update release.

1194130 Last modified: 2014-08-17 18:51:11, 21788 bytes

Login Required

Login is required for additional detail.


Apply for a new Vanity callsign...

You must be logged in to file a report on this page

Please login now...

Currently updating logbook display.
ad: giga-db
Copyright © 2014 by QRZ.COM
Thu Oct 30 13:26:20 2014 UTC
CPU: 0.085 sec 57374 bytes mp