Sunday, November 12, 2017

Can You Spell - PILEUP? And, on EME no less!!!

Well, it sure is nice to have an Elevation Rotor that is not frozen.  I left the heat tape running all night and had not one single issue with the Elevation Rotor.  On November 12, 2017, the outside temperature was 38°F at 8 a.m. so probably not a really good test since it did not get below freezing but I'm happy it worked.

I got on the moon about 2 a.m. local time and did not see a lot of activity.  I saw UA4LCF calling CQ and I answered him.  We had an easy QSO.  Then, I3MEK on the Chat Page asked to run with me.  After I worked him, IK7EZN called and it soon became a "love fest" on my frequency!  I soon found out that many, many stations could hear me off the moon.  I received the following on the chat page from S52LM:

12Nov 10:23 W8TN Clark, you have now 8 callers ====== {S52LM/4X28XP/KW Milos xx JN65tx}

WHOOO, HOOOOO!  An actual bonafide pileup!  On the left is my log of the TWENTY-FOUR (24) stations I  worked today!!!

Check out the 0900 hour - NINE QSO's in one hour!  Now THAT is some serious RATE on EME!

When I started this project I figured that I would be able to make an "occasional" QSO off the moon with my little 2-antenna setup but NEVER - NEVER - NEVER did I think it would be like this!

And, today, I set a new record for completing a QSO with a VERY weak station.


I decoded Calls + OOO from K1DG at -31 dB -
   Nov. 10, 2017, DGR=0.8 dB - 135100  0  -31  2.2 -285  3 #      W8TN K1DG FN43      OOO   0  10

This system truly is out-performing what I had expected it would do!

New DXCC Countries worked today are:

Republic of South Africa
Balearic Islands
Finland
Hungary



My STANDINGS on EME over the last 12 days are:

72 QSO’s
68 Initials
62 Grid's
25 DXCC’s


You know in the movie "Jaws" where Roy Scheider, who played Brody in the movie, says, "You're gonna need a bigger boat!" ??  Well, it seems that now applies to me in that "I'm gonna need MORE EME QSL's!"  22 of those 72 QSO's have already been confirmed on LoTW giving me 12 countries confirmed on 2-M already!

The EME Antennas Can Really HEAR!

Steve, G4TRA, emailed me on November 9, 2017, and asked to run a schedule with me on EME the next morning.  He runs a single 11-element Tonna antenna plus 400-watts.  I felt that was WAY too small a station for me to be able to work but agreed to run with him.  Amazingly, during one of his Ground Gain lobes, I did indeed copy him when his elevation was just under 11°:

120200  2  -26  2.5 -310  3 *      CQ G4TRA IO81             0 9

He was able to copy me on 10 different sequences (I run twice his power and more than twice his antenna.)  However, we were never able to complete the QSO.  We agreed to try again the next day.

Before my schedule with G4TRA, I made a nice QSO with GM6JNJ in Scotland (by answering his CQ) for a New Country and later I made QSO's with the following:

K2ZJ    New York
K1DG    Maine
W5ADD   Louisiana


All those were New States for me.  So, all in all, a very productive morning.  Maybe the second biggest surprise (after copying the single antenna station) was that I copied full calls and "OOO" report from K1DG at a signal level of -31 dB.  That is a record for me on weakest signal copied.  I have copied calls or CQ's at -29 dB before but this is my lowest.  Of course, "Shorthand" reports of RO, RRR and 73 have been copied several times at -31 dB but never full calls plus report.

135100  0  -31  2.2 -285  3 #      W8TN K1DG FN43      OOO   0 10

At 10:30 a.m. local time there were several JA stations on the moon but I could not copy any of them.  They did not seem to be copied by many other U.S. stations either so there must have been some one-way propagation at that time.

The next morning I had plans to run again with G4TRA about 7:50 a.m.  Plus, I received an email from SuperStation I2FAK who wants to run with me also.  But, back to the "Good News, Bad News" mantra!  I got up at 1:30 a.m. and when I turned on everything, I found the elevation rotor would not turn!  BUMMER!  It was 25°F (-4°C) outside and I guess the rotor just did not have enough torque to break itself free.  Maybe the grease on the gears had gotten stiff.  So, I had to cancel both schedules.  Eventually when the outside temperature reached 41°F (+5°C) the rotor worked just fine.

I picked up a 6-foot water pipe heat tape at Home Depot to wrap around the Elevation Rotor to try and keep it warm enough to rotate.  Back at the house I managed to fight through all my boo-boos:

Climbed the tower and dropped the AC Extension Cord
Dropped one glove
  (Evelyn came out and taped them to a cable for me to pull up.)
Dropped the electrical tape
  (I had to climb down and retrieve it.)
Came down the tower again but forgot to tape the extension cord where it goes around the azimuth rotor.
  (I had to make one more trip up the tower.)
Dropped my water bottle - TWICE!

FINALLY, I now have a 6-foot heat tape wrapped around the elevation rotor.  You can see a photo of the Elevation Rotor wrapped with the Heat Tape on the right.  Click on that photo to see a larger image.  Of course, there will not be a night where the temperature falls lower than 33° for at least the next 8 days.  I will have to wait awhile to see if this works.

UPDATE:  The rotor worked just fine that night!


ARRL EME Contest Results

BOY, OH, BOY - This EME Contest was a LOT of FUNNNNNN!

I was not trying for a score in the contest, I just wanted to work folks off the moon and this contest is a good time to do that.  Over the first two nights that I was operational on the moon, I made a total of 10 QSO's which I felt was pretty neat.  Well, in the ARRL EME Contest, I bettered that number by a good bit.  I made a total of 16 QSO's the first night!  And, EIGHTEEN the second! WHEEEEEE!

Several times I heard Roger, KD8BZY, who is quite close to me, working stations with his single 12-element yagi and I know he worked some that I didn't and I might have worked some that he didn't.  I'll bet if we pooled our individual QSO's we'd really have a list.

For the most part, everything worked as it should.  I found an issue or two that I'll need to look at but overall, things just purred along like a well-oiled machine. 

By 7:20 a.m. I only had 8° of moon left and not much that I coule hear to work so I decided to hit the sack for some Z-Z-Z-Z-Z's.  It is interesting to note that some of the stations I heard in the first weekend of the ARRL EME Context last month when I could only receive,  I was not able to copy them this night when I knew they were on the moon.  This EME stuff is not as easy as you might think [grin].

Anyway, on the left is a log of the completed QSO's I made last night.  The K9MRI station I had worked previously but all the others are New Ones.  Click on the image to get a larger view.

You know, I can't come up with a big enough adjective to describe my elation at being back on-the-moon.  In some respects it is just MIND-BLOWING!

I worked SEVEN stations via EME my first night on the moon.  THREE more the second night.  SIXTEEN the third night and EIGHTEEN on the third night!  I've only  been on-the-moon for 4 nights and I have made 44 EME QSO'sI never thought I could do this well.

Of those 44 QSO's, 42 were what is called "Initials."  The first time a contact is made with a new station, this is known as an "Initial" on EME. Sometimes stations change callsigns or move.  If a station moves his location into another grid or square then they can be counted as separate "Initials."  However if a station changes his callsign (for instance G6ZTU became GØRUZ), this does not count as a new initial.

The second night was again - "Good News" and "Bad News."  Early in the evening I tried calling CQ (for 1 hour and 10 minutes) with my antennas headed directly into the trees behind the house.  I was answered and made a QSO with YL2GD, RK3FG, and RX1AS.  This is HUGE to know that I can beam east and make QSO's off the moon!  In fact, my first QSO was made with the moon at an elevation of only 4.7° (although the station I worked, HB9Q, was a Super Station running a 45' dish antenna!

The first "Bad News" was that for 4 hours (from 0130-0530 GMT) I could not buy a QSO!  I could see on the Chat page that Roger, KD8BZY, was making contacts during that period.  I am going to assume that Roger has his antenna vertically polarized and I was locked out of working stations because the majority of the signals were coming in on that polarization.  I called many stations but had no response.  Later in the evening I spent an hour calling WO7R in Arizona with no luck.  At one time he did come back to me but could never get my report.  He had one of the strongest signals I copied on the band but he had problems with his "horizontal" receiving and just could not work a lot of stations.  I saw Roger trying for him many times but don't think he worked him either.  I also called K6MYC with a Big-Time signal but he could not hear me.

This difference in polarization can be huge.  If your antennas are not in the same polarization as the signal coming in from the moon, you either get a very weak signal or no signal at all.  I ran with PAØJMV for awhile and he commented on the Chat page:

05Nov 04:50   W8TN/2X13H/KW Clark ur sigs -19 solid here.... ====== {PA0JMV Joop xx JO21pm 82.95.154.122}
05Nov 04:58   W8TN Clark, u have local QRM on this freq?  audio copy u ====== {PA0JMV Joop xx JO21pm 82.95.154.122}

For him to receive me at -19 dB means he has a GREAT signal from me.  For him to actually HEAR my signal in his speaker is HUGE.  But, at that time, I had zero traces from him.  Nothing, Nada, Zip, Zero, Zilch, . . . you get it - a blank screen.  I think he felt since I was a "newbie" that I had something wrong with the receive side of my system.  However, while running with him, I copied a CQ from an Argentine station and was called by (and worked) K5LA in Texas while running with PAØJMV.  Sort of like an HF pileup!

I think PAØJMV realized we had one-way propagation at that point.  However, no too much later we ran again and in short order completed the QSO. 

I called CQ again for about an hour and worked: W2DBL (the guy who just finished working 1,000 initials), ON4KHG and N1DPM.  I'm very pleased with how the CQ'ing thing was working for me.

On the right is my log from the Second Night of the EME Contest. Click on any image to see a larger view.

My first night on the moon, Paul, W2HRO said:

02Nov 04:33 Clark - you'll have 100 QSO B4 the end of the year.  Good station and ur a good OP - GL ====== {W2HRO/2X28XP/1K Paul NJ FN20ll}
Since there are only two months left in the year, I did not think Paul was going to be right on that call.  However, with 44 QSO's in my first FOUR nights, he just might be right.  And, I'll need ALL that experience to have a shot at working 3YØZ, Bouvet Island, via EME.

Then I saw one of the stations I worked on the second night of the ARRL EME Contest posted the following on the Moon-Bounce reflector:
Last night  I worked my 1000 Initial after 8 years with a modest 4x9 setup and 1KW.  I am very happy , my wife thinks I am nuts.

Thanks for all the fun.

73
W2DBL (W2LPL)
Les
WOW!  That's 1,000 DIFFERENT EME stationsSuper COOL!

Of my 44 QSO's, I now can report the following "stats":

38 Grids
15 Fields
20 DXCC entities


And, here is my list of DXCC's worked:

DXCC Countries Worked via EME

DL8II    Federal Republic of Germany
EB5EEO   Spain
EA8DBM   Canary Islands
G4CDN    England
HB9Q     Switzerland
IK4ADE   Italy
JHØBBE   Japan
K9MRI    USA
NH6Y     Hawaii
KL7UW    Alaska
LY2IJ    Lithuania
LZ1KU    Bulgaria
OK1UGA   Czech Republic
ON4KHG   Belgium
PA5Y     Netherlands
S52LM    Slovenia
SM4GGC   Sweden
UA3PTW   European Russia
UX5UL    Ukraine
YL2GD    Latvia
12 of those 44 contacts have already been confirmed via LoTW and I have picked up SIX new entities confirmed on 2-M !  WHEEE!

All in all, I'm Super pleased with how this has gone.  I know that the first 20 countries come pretty easily but, at lest it is a start and I can just build on that.  But first, I need to get back on a "Sleep at Night" schedule instead of "Stay Up All Night and Sleep in the Day."

The DX Continues to Come Via the Moon IF Everything Works Right

November 3, 2017, turned out to be another "good news - bad news" day.  The first "good news" is that I had been really worried about my ability to work to the East through the trees behind my house.  Well, at Moonrise (MR) tonight I pointed my antennas to 85° Azimuth and 0° Elevation.  When the moon was just at 86° Azimuth and 2.5° Elevation, I copied a CQ from YU7AA:

220900  0  -26  2.5  110 30 *      CQ YU7AA JN95             0  10

Boy, oh boy did this look good for being able to work stations THROUGH the trees.  I called YU7AA several times though and had no response.  But, on the Chat page, F8DGY asked if he could run with me as he was copying me.

Well, we ran for a bit with no luck.  Then another F8 station asked to run - no luck.  Then a DL - no luck.  Then my friend, N1NK from RI, and, you guessed it - no luck.  Later I ran with S56P - no luck.  I was beginning to thing that copying YU7AA was a fluke and maybe I could NOT work through the trees.

This inability to copy anyone after YU7AA went on for about 3 hours.  Finally, I when I was running with S56P (with no luck), I got a phone call from a high school friend in FL.  I stopped running with S56P and while talking to my friend, I was leaning back in my chair and I saw the elevation readout said 0° instead of 26° and the azimuth rotor was at 90° instead of about 125°.  WHAT?

It turns out that my "automatic" rotor turning software had failed. It was "thinking" that the rotors were turning but they had not moved since Moonrise.  Well, CRAP ON A CRACKER!

Once I rebooted the computer and started everything up from scratch, I found that I could not get any drive out of the K3S.  The short of that story is that during the reboot, M/S Windows graciously changed the device numbers of my USB Audio device for the K3S.  More CRAP! This time it was the M/S flavor!

Anyway, once I corrected these two bumbles, I managed an excellent QSO with LZ1KU in Bulgaria and DL8II in Germany.  WHEEE!  Back in the game!

Right after that, I saw IK4ADE was calling CQ and I copied him at -24 dB - - - - So, you can add one more New One to my score for tonight for THREE New Ones!  That makes my Digital EME QSO's now 10 in just two nights.  Would have had more if not for the bumbles!  It is simply amazing how little DX you can work if your antennas are NOT pointed at the moon!

That brings my country total up to SIX.  I can't wait to see what happens with the EME contest to see just what I can do on Digital EME.

Re: [WVDXA] WHOPPEE!!! It's STILL Alive!!

No sooner than I finished my first two EME QSO's and took a breather to let my heart rate come back into normal range, than I saw NH6Y in Hawaii calling CQ.  In short order, he was QSO No. 3 in the LOG!  You can see the screenshot of our QSO on the right.  Click on it for a larger image.

02Nov 03:36 Clark, Thanks for the qso, best was at 0327 (-26) Aloha ====== {NH6Y/4X9H/1K Tom HI BL10ts}
02Nov 03:37 033600  3  -29       211  2   73                                ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 03:37 NH6Y, Tom. THANK YOU for my 3rd ever Digital EME QSO. UR Best -21. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 03:39 That's great.  I'll send you a card. ====== {NH6Y/4X9H/1K Tom HI BL10ts}
Heck, I was all set to go lay down but who can sleep when the band is open?  One more DXCC country logged.  WHOPPEE!!

When I was working NH6Y, K8DIO running two 17-element yagis copied me at -23 dB off the moon.  I am running just two 13-element yagis so that's pretty good I think!  Small station to small station.

02Nov 03:48 2 yagi to 2 yagi   144.117  111  0 -1 -1  2.4   0  3 -23 033100  NH6Y W8TN EM98 ====== {K8DIO/2X17/K Lloyd OH EN91gh}
Next Ken, W8KEN, in Ohio wanted to run.  This made my Digital EME QSO No. 4.

02Nov 03:47 W8TN Clark, Could we try .112 ??? ====== {W8KEN/2XP22A/1K Ken OH EN91im}
02Nov 03:48 W8KEN, Ken.  RR. You go first? ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 03:57 W8KEN, Ken. Sri, I got confused in what to send as I got you on tropo at times. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 03:57 W8KEN, Ken. Finally saw the DT and knew it was EME so changed my message. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 03:58 W8KEN, Ken. You are only my 4th Digital EME QSO so I'm pretty "green." ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 03:59 W8TN Clark, Tnx Initial #114, Best -25, I had to separate your EME from Tropo also, GL,73 Ken ====== {W8KEN/2XP22A/1K Ken OH EN91im}
Whuups, then another Ohio station wanted to run and just posted on the Chat page that he was calling me.  This was the guy who already reported copying me when I worked Hawaii.   He became my Digital EME QSO No. 5.
02Nov 03:59 W8TN Clark, calling ====== {K8DIO/2X17/K Lloyd OH EN91gh}
02Nov 04:02 K8DIO, Lloyd.  Listening. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 04:12 K8DIO, Lloyd.  TNX for my No. 5 Digital EME QSO. UR Best -28. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 04:12 W8TN, tnx Clark.  Your best -24  73 and have fun. ;-) ====== {K8DIO/2X17/K Lloyd OH EN91gh}
Then, Paul, W2HRO, who I failed to complete with earlier, showed up for another go at it and he became my Digital EME QSO No. 6.
02Nov 04:23 W8TN Clark - ready for a try? ====== {W2HRO/2X28XP/1K Paul NJ FN20ll}
02Nov 04:25 W2HRO, Paul.  Sure. You call it. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 04:25 .118 - HRO - 1st ====== {W2HRO/2X28XP/1K Paul NJ FN20ll}
02Nov 04:26 W2HRO, Paul.  RR. Running. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 04:26 RRR ====== {W2HRO/2X28XP/1K Paul NJ FN20ll}
02Nov 04:31 W2HRO, Paul.  Well, now wasn't that easy?  UR Best -24.  My 6th digital EME QSO. TNX! ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 04:32 W8TN Clark - tnx fer quick qso - welcome back to EME - tnx fer initial - ur b-20 - nice sigs - 73 & GN ====== {W2HRO/2X28XP/1K Paul NJ FN20ll}
02Nov 04:33 Clark - you'll have 100 QSO B4 the end of the year.  Good station and ur a good OP - GL ====== {W2HRO/2X28XP/1K Paul NJ FN20ll}
02Nov 04:36 W2HRO, Paul. TNX for the compliment. It's been a long road to get here but this is FUN! ====== {W8TN/2X13H/KW Clark WV EM98al}

That was a nice compliment from Paul.  Cool!

It's now almost 2:20 a.m. and activity has slowed down a bit.  There are still 44 users signed into the Chat page but there have been no posts for the last 12 minutes.  So, maybe I should lay down for a couple of hours and then see if I can work someone in Asia before sunrise. 

Here is my first night's score (so far [grin]):

No. 1 - PA5Y - Netherlands - 4x8element Horizontal & Vertical
No. 2 - K9MRI - Indiana - 8x28 XP yagis
No. 3 - NH6Y - Hawaii - 4x9element Horizontal
No. 4 - W8KEN - Ohio - 2x22 XP yagis
No. 5 - K8DIO - Ohio - 2x17element
No. 6 - W2HRO - New Jersey - 2x18 XP yagis
No. 7 - W7GJ - Montana - 16x17elements

HEY, I just saw another WV station show up on the Chat Page.  Paul, WB8TFV, from Martinsburg.   I knew him years ago in Parkersburg.  He runs 2x10element H&V antennas and is trying to work NH6Y but can't seem to do it.  I'm copying NH6Y at -23 dB.  Good news.  They changed to a different frequency and made the QSO.  WB8TFV told NH6Y his best copy on the Hawaiian station was -27 dB and mine was -23 so I think my station is doing OK.  But with Paul's ability to switch polarity, he just worked NTØV in ND and I haven't heard a single peep from him all night.

I guess I didn't get my body laid down.  But, W8KEN has already uploaded our QSO to LoTW and it is confirmed.  YIPPEE!

Still, it ain't over.  The moon is down to 16-degrees and I just worked Lance, W7GJ, who was calling CQ.  This was my Digital EME QSO No. 7.
02Nov 08:16 W7GJ, Lance.  TNX for Digital EME QSO No. 7. ====== {W8TN/2X13H/KW Clark WV EM98al}
02Nov 08:17 W8TN TNX Clark - best was -14 dB hr ====== {W7GJ/16X17/1500 Lance MT DN27ub}
OK, it's 5:30 a.m. and I've still not been to bed.  Oh, well.  I've been watching everyone working DX7EME in the Phillipines but I am not able to copy them yet.  My moon is down to 3° elevation so time is running out.  I ran a schedule with ZL2MQ for about 22 minutes but no joy.  I copied him calling me one time:
071100  0  -28  2.3   30  3 #      W8TN ZL2MQ RF80     O ?   0   1
OK, that's all folks.  It's been a FUN night.   YAWN . . . . .  Wonder if I'll be able to sleep after all this excitement???

WHOPPEE!!! It's ALIVE!!

This post was for activities that took place on November 1, 2017:

A little over 7 months ago on March 22nd my Grandsons, Owen & Grant, came and dug the hole for my EME tower.  Since then there have been MANY ups and downs on the MoonBounce project.  Success has always been followed (or preceded) by failure.  Still, my motto has always been, "Never Give Up, Never Surrender."

On October 31, 2017, I successfully replaced the relay which self-destructed a couple of days before and the station was then essentially ready to go.  Today I ironed out a few bugs and felt that once the moon came up, I would be ready to give it a go.

I signed on to the WSJT EME - 1 chat page about 2120 GMT on November 1, 2017.  Without me ever sending a post, I soon saw the following appear:

01Nov 21:38 W8TN pse listen for me 144.136 first ====== {PA5Y/4X8HV Conrad xx JO21vo}
WHAAAAAT?  Well I'm guessing that Conrad, PA5Y, looked at the list of the more than 100 stations who were signed on to that page and saw my call.  Then, just out of the blue, he sent the above message.  I had not previously had any communications with him to the best of my knowledge.  But, I'm sure he saw me posting questions or comments in the last couple of weeks.  What a hoot to have someone who did not even know that I was now able to make EME QSO's ask me to listen for him.

So, I grabbed a quick dinner and saw that my computer (MAP65 program) had copied PA7Y calling CQ on 144.136 MHz so I went to that frequency and soon copied him calling CQ in the WSJT 10.0 program.  I tried to answer him but mistakenly had the software set to call CQ!  I recognized my mistake after about a minute but by then the Chat Page posted this:
01Nov 23:10 W8TN CQ is -16, please stick around really want to work you ====== {PA5Y/4X8HV Conrad xx JO21vo}
01Nov 23:21 W8TN JT65B 230900 4 -16 dB 2.5 s 162 Hz 2 W Freq 1433 Hz   CQ W8TN EM98 ====== {PA5Y/4X8ELEJXXX Conrad xx JO21vo}
It turned out that he had someone else answer his CQ and I watched him work that guy.  Then I saw:
01Nov 23:14 W8TN call you now ====== {PA5Y/4X8HV Conrad xx JO21vo}
At that point it was GAME ON!!!  The screenshot on the right was taken about an hour and a half after the QSO so only the text in the center applies to that QSO.

Here is the pertinent part of that decode:

231400  5  -22  2.5  156  3 *      W8TN PA5Y JO21            0  10
231600  9  -26       154  1   RO                                  
231800 10  -25       152  3   73        

WOWZER!  My FIRST Digital EME QSO Ever! 

Here is the exchange on the Chat Page:
01Nov 23:20 W8TN tnx Clark excellent signals tonight, shame I have to work tomorrow :-) ====== {PA5Y/4X8HV Conrad xx JO21vo}
01Nov 23:21 W8TN JT65B 230900 4 -16 dB 2.5 s 162 Hz 2 W Freq 1433 Hz   CQ W8TN EM98 ====== {PA5Y/4X8ELEJXXX Conrad xx JO21vo}
01Nov 23:23 PA5Y, Conrad - WOOO, HOOO. My first digital EME QSO!!  THANK YOU! ====== {W8TN/2X13H/KW Clark WV EM98al}
01Nov 23:23 231400  5  -22  2.5  156  3 *      W8TN PA5Y JO21            0  10  ====== {W8TN/2X13H/KW Clark WV EM98al}
01Nov 23:23 W8TN Clark really oh thats awesome! ====== {PA5Y/4X8ELEJXXX Conrad xx JO21vo}

I took a little 3 minute 47 second video of the last part of the contact.  Even with the video displayed full-screen, it's a little hard to see the above details.  But, you can hear me make my exclamations!

https://youtu.be/D27feN_-7b4

After that QSO, I called CQ for about 12 minutes and K9MRI answered me.  We had a good QSO but I lost the screenshot of the exchange.  Still, that was my 2nd QSO.
01Nov 23:48 Clark, W8TN, great signal -15, tnx and gl on moon ====== {K9MRI Joe IN EN70iu}

Later I was told on the Chat page that W2HRO copied me:
01Nov 23:57 W8TN Clark - I see ur CQ every period ====== {W2HRO/2X28XP/1K Paul NJ FN20ll}
02Nov 00:28 0027 -21  2.4 1562 #* CQ W8TN EM98   ====== {W2HRO/2X28XP/1K Paul NJ FN20ll 173.61.117.151}
02Nov 00:32 0031 -22  2.4 1557 #* CQ W8TN EM98  ====== {W2HRO/2X28XP/1K Paul NJ FN20ll 173.61.117.151}

And, I copied him one time:
02Nov 00:36 000000  1  -28  2.6  315  3 *      W8TN W2HRO FN20           0   8  ====== {W8TN/2X13H/KW Clark WV EM98al}

But we never made a QSO.  Also, DL5OCD copied me but I never saw a thing from him.
02Nov 00:25 0023 -21  2.8 1378 #* CQ W8TN EM98 ====== {DL5OCD/10WL/400 Michael xx JO42xg}
02Nov 00:33 W8TN Clark: rrr, stable -20 to -25 on V-POL here ====== {DL5OCD/10WL/400 Michael xx JO42xg}

A little later my friend, Jim in RI asked me to call CQ.  He found me easily but his TX was not working so we did not try for a QSO.
02Nov 00:59 W8TN - 136, coming in H and -23 ====== {N1NK/2XP18/750W Jim RI FN41kn}
02Nov 01:00 W8TN - good copy here.  EME, not tropo.  my TX not operating.  dang. ====== {N1NK/2XP18/750W Jim RI FN41kn}
02Nov 01:01 W8TN - copy with both MAP and WSJT ====== {N1NK/2XP18/750W Jim RI FN41kn}

Now one of the really good things to come out of tonight's work is that ALL of the above QSO's and SWL reports of my signal came with my antennas pointing INTO the trees to the east of my house.  I was really afraid that they would cause me a ton of grief.  But, it seems that I CAN work stations in that direction!  YIPPEE!

The next couple of days are good EME conditions (the degradation was 2.3 dB this evening) and this weekend is the EME contest so I'll definitely be running up the electric bill with my solid-state kW amp.  I moved the power output up to a little over 800-watts and it seems to just purr along.  Sometimes the fan kick up to a higher speed but I see no issues at this point.  I did call CQ for over an hour so that should have caused something to fail if it was going to fail.

I wish I had a way to tell if I should give it up for tonight or stay up until MoonSet (MS) at 5:30 a.m. or if I should get up about 4 a.m. to look for Asian stations.  Decisions, decisions, decisions!!!  Whatever I decide, it will be difficult to get to sleep tonight for sure!

I think I'll leave the software running and if I get up for a bathroom visit, I may just turn on the computer monitors and see what's happening!!!

HEY, DX7EME (a DX'pedition to the Phillipines) has just become operational.  I will have a window to try for them beginning at 4:00 a.m. so maybe I DO need to get up to visit the facilities [grin].

Right now I have just upped my DXCC score on 2-M to a whole TWO countries!  So, IT's ALLLL GOOOD!

Relay Replacement - Moving On

The destruction of the CX-600NL relay was a bit of a setback.  The way I had the station configured, it would not work the way I wanted it to without this relay.  Luckily, a few weeks ago while going through some of my junk box treasures, I found a Brand-New Transco relay still in the plastic.  This will work just fine - well, maybe . . . It turns out that the CX-600NL relay was a 12-volt relay and the Transco was a 28-volt relay.  Hummmm!

After thinking on several ideas that I could use to make this work, it suddenly occurred to me that the T/R relay up on the tower is a 28-volt relay and I have 28-volts available in the DEMI TR Sequencer.  All I had to do was to open the sequencer and connect a jumper from the output jack (NO1) for the T/R Relay to the unused (NO2) jack.  Simple!  Then I just had to install a 1N4003 diode across the relay coil and solder an RCA cable to the relay and run it to the NO2 jack.  DONE!  I now had a replacement for the CX-600NL.  You can see the new relay in the photo on the right.  Click on it for a larger image.

The junk box is a wonderful thing!  Never throw anything away because as soon as you do, you will find you need it.  Of course, it can be pretty difficult to find something that you "KNOW" you have but you can't remember where in the heck you put it.  Just part of gettin' older.  Hey, maybe this is part of that "Use It, or Lose It" theory on your mental ability.  Uh, Huh!

I have been really busy with this EME project and have been running behind on updating this Blog.  The relay replacement was done on October 31, 2017, but I am just now blogging about it.

Sunday, October 29, 2017

Even More "Good News - Bad News"

Well, I just couldn't let it go.  I had to see what I could do to resolve my issue tonight without waiting to call Elecraft tomorrow.  I read the manual - no help.  I searched Google and eBay for an N-Male to N-Female 3 dB, 10-watt (or more) attenuator but nothing in my price range was available except from China and that won't get here by next weekend's contest.

However, the ever-faithful Mr. Google, did give me a hint.  I found there is a menu setting in the K3S (CONFIG: XV1 PWR) which sets the maximum K3S power output for the current transverter band.  I checked that menu item and mine was set as CONFIG: XV1 PWR = L1.50 (which is the highest level) so I turned it down to the bare minimum which was L .01 and then looked at the K3S PWR control.  Instead of the previous minimum of 0.1 mW it was now 0.01 mW.  WOW, did I just find a way to lower the power even further out of the K3S?   WHUMP - Yes he did!

I turned the amp back on, set the WSJT-X software to Echo mode, and lo and behold, I no longer had 800-watts out of the amp?  At that level "0.01 mW" and with an Audio Line Input of "1" there was no measurable power out.  I played with the Line level ending up at "10" and I brought the XV1 PWR level up to 0.02 mW and got 200-watts out.  A further increase to 0.03 mW and I now had 400-watts output.  I can work with this!!!

I'm pumped now!  Bring me the moon tomorrow and I'll try echo testing for real!  WHEEE - this will make it MUCH easier for me to get some good sleep tonight instead of worrying about this problem.

But, every time I find a solution or make a step forward, Mr. Murphy pulls me back.  In disconnecting the 1/2-inch Heliax feedline connected to the CX600-NL relay from the Bird 43 wattmeter in order to connect it to the amplifier input, I must have flexed that cable a little too much and WHAM! - the NEW $112.50 CX600-NL relay self-destructed.  This would NOT have happened if that blasted RG142 cable had had the N-connectors installed properly!

 CRAP ON A CRACKER!

That happened before I was able to test my successful adjustments above and I had to rely on a double-female "N" barrel connector to replace the relay.  I "might" be able to put the N-connector back on the relay if I can find a small enough Allen wrench but at this point, I'm just happy to have the power output of the K3S low enough to work with while continuing to pursue this project.

Now I really am going to bed and try to get rid of this shoulder cramping obviously brought on by all this stress!

WHUUPS! Two Steps Forward and One Step Backward

OK, today was the day to get the amplifier running.  I finished wiring the 3 kW 48 VDC power supply and connected it to the 220 VAC in the shack and to the W6PQL amplifier.   After double and triple checking everything (and removing the PTT cable from the amp just to make sure I did not accidentally put it into transmit) I decided it was time to swallow a few times and hit the AC ON button.  The "pucker factor" was fairly high at this point [grin].

Well, for a couple of seconds nothing happened and I was sure I had made a big mistake.  Then I heard a relay click, fans started running in the 3 kW power supply and the amp displayed 52 VDC on the PA Voltage meter.  WHEW!!!  Time to remember to breathe now!

I relaxed for a bit and let the system just coast along.  The air coming out of the back of the 3 kW power supply began to warm a little so I might need to think about relocating that power supply.  The output of the air is blocked a little and if I am going to be running long schedules, I will need plenty of cooling.

The next step was to key the radio and see if the amp moved into Transmit.  I put the K3S on 2-M, DATA A mode, dialed the PWR control all the way to the left where it was reading -10.0dB (0.10 mW), and I stepped on the footswitch.  WHUUPS - BANG!!

There was a noise, some relay clicks and the amp displayed a red LED indicating "Load Fail."  I had been expecting nothing at all to happen except the sound of the Sequencer relays and the "Transmit" LED on the amp to come on.  BOY, was I surprised.

 After letting my heart return to a normal rhythm, I turned OFF the amp and began looking at the K3S.  Without the amp inline, when I step on the footswitch, the RF meter on the K3S jumps way up scale, not often but sometimes even to full scale.  That could explain the "Load Fail" indication on the amp by there being WAY too much drive power.  I had previously changed the input attenuator on the amp so that I could drive it with a maximum of 2-1/2 watts instead of 10-watts.  If the K3S put out a spike when it began transmitting, that may have driven the amp too far and the protection circuit shut it down.  I do also recall seeing the Forward and Reflected power indicators on the amp jump upscale briefly before the amp shut down.  I really had no plans to "test" that protection circuit but it's good to know that it is working perfectly ! ! !

I tried adjusting the drive on the K3S with a single tone on the input.  As I turned the PWR control, the RF meter would indicate full scale as I was turning it then, when I stopped turning it, the RF meter would stay at a specific level.  It almost acted like the PWR control was dirty.

I saw where there was some discussion about this online.  The comments seemed to indicate that it might be a Power Supply issue.  So, I checked the built-in meter of the K3S and it indicates a Supply Voltage of 13.6 VDC in Receive and 13.3 VDC in Transmit (PWR control at minimum.)  This is pretty much normal.

On a hunch, I increased the TX Delay in the K3S configuration from 8 ms to 14 ms and that seemed to stop the full-scale power readings when the footswitch was pressed.  At the same time I returned the input attenuator on the amp to the maximum amount of attenuation so that I could input more power without an issue.

I powered on the amp again, pressed the footswitch, and YAY!, it did NOT give me a fault!  Just the "Transmit" LED lit up.  I then put WSJT-X in Echo mode and set the PTT method to VOX so it would NOT key the transmitter by itself.  The program would be going into Echo mode transmit but until I pressed the Footswitch, the radio would not transmit.  This worked and I had about 800 watts out very briefly.  I let up on the footswitch and reduced the Audio Drive Line Input to the K3S from 17 to 2.  This time no power out was noted.  I brought it slowly up and at a level of 5 noticed that there was a spike in the Power output and a sound in the K3S speaker when it went into transmit. 

Except for the spike, there was 10 amps of PA Current being drawn by the amp but no power out shown when there was a tone being supplied except for an initial spike of 800-watts!  Without the tone, there was just 2 amps of PA Current which was probably just the bias level with no RF input.  This test was done with the footswitch putting the K3S into continuous transmit and the WSJT-X Echo mode supplying the tone for a cycle of 3 seconds ON and 3 seconds OFF.  The "spike" I observed here was not from the K3S going into transmit, it was from the tone being applied which caused the K3S to generate RF that then seemed to be "choked" down to the level of -10.0 dB (0.010 mW).

The next test I tried was just sending CW.  Without the amp on, the K3S still seemed to have a bit of a "spike" when just sending the letter "E" but sending my callsign, the RF meter only indicated 1 bar.  I set the keyer speed to 40 wpm, turned on the amp and sent a single "E" and the Forward Power indicated 800-watts out.  This was with the K3S PWR level at minimum.  I then sent my callsign and it continuously keyed at 800-watts out.  Bad news is that I was hearing RFI from one set of computer speakers - that will need to be taken care of.  But, the good news (what little there is) was that there was NO Reflected Power indicated.  Looks like Charlie, N8RR, and his famous SARK Analyzer helped me get the antennas tuned nicely!

My last step was to check the power output of the K3S on 2-M.  I pulled out a Bird Model 43 wattmeter and looked through my slugs to find what I had which would measure close to 2-M.  I had a 5W slug that covered 400-1000MHz which was close.  Using a Narda 40-watt termination that was good to 12.4 GHz, that 5W slug measured 2.8 watts output with the PWR control set to minimum.  With the K3S PWR control at -4.0 dB (0.43 mW) the slug was reading full-scale or 5-watts.  Next I used a 25W slug good for 50-125 MHz.  At the minimum PWR setting on the K3S this slug measured 4.5-watts and reached 8.5-watts with the PWR control at maximum of 1.8 dB (1.50 mW.)  That pretty much tells me that at the very lowest PWR out setting of the K3S, it is putting out enough power to drive the W6PQL amplifier to 800-watts output even with the attenuator connected.   Maybe I need a larger attenuator to be able to have more control of the drive level to the amplifier.

At this point, I'm out of ideas and ready to go "chill out" a bit.  Looks like I need to call Elecraft tomorrow afternoon and see what they can tell me.

Saturday, October 28, 2017

Continuing Progress on the 2-M EME Project

On Friday, with the good weather, I thought I should go ahead and fix the Inclinometer installation.  You may recall that I had to compensate in the Rotor Driver program for the Inclinometer reading being off by a negative 5°.  The problem with that was that the system would not rotate below an "indicated" 0° which occurred when the antennas were actually 5° above the horizon.  What was needed was for me to climb the tower and rotate the antennas until they were horizontal, then move the Inclinometer to where it read 0°.  With the help of my lovely wife, Evelyn, that is exactly what I did.  Once I had the Inclinometer showing 0° when the antennas were actually pointing at the horizon, I then had to re-calibrate the EA4TX ARS-USB controller so that the Inclinometer tracks correctly all the way from 0° to 90° (straight up.)  Once that was done, I rotated the antennas to 90° and went outside to check - Yep, they were pointed straight up!  YAY!

I then removed the "compensation" in the Rotor Driver program so whatever the Inclinometer said was what the program took as correct.  Over the next few hours, I let the system AutoTrack and I kept visually checking the antennas and the elevation now tracked perfectly!  I still have the 7° "compensation" factor on the Azimuth readout but that is not a problem.  Not much else got done Friday evening because that "tower climb" set my back off and it was difficult to just sit in a chair.  It's a good deal better today but still hurts.

Today I thought I would finish off some more of the little bits of the project that were still hanging.  The first thing I tackled was to wire up the CX-600NL relay that switches the Elecraft K3S between the RX (receive) line and the TX (transmit) line to the W6PQL solid-state amp.  I first soldered a 1N4003 diode across the coil of the relay.  This is done because an inductor (the relay coil) cannot change it's current instantly so the flyback diode provides a path for the current when the coil is switched off. Otherwise, a voltage spike will occur that may cause arcing on switch contacts or possibly destroy switching transistors.  I then wired a shielded cable with an RCA connector on the other end to the relay coil.  This cable will plug into the "TR" connector on the DEMI Sequencer so that 12 VDC is supplied to the CX-600NL relay for switching it as necessary from TX to RX.  Being honest with you all, the first time I soldered this cable I had too much tension on the center conductor and the heat of the soldering iron melted the center conductor right through the insulation.  That could have resulted in a short at a later time so I cut it off, removed the soldered ends and did it again being more careful this time.  But, I wasn't careful enough with my finger as I managed to lay it "briefly" on the soldering pen and got a slight burn for my lack of caution!

Not having an elegant method of mounting this relay, I just installed a screw-eye in the back of the equipment shelf and used a Ty-Rap to secure the relay to it.  Again, I was less than careful and my first placement of the Ty-Rap interfered with the relay's motion so I cut it off and picked a better location the next time.  The photo on the right should be horizontal but Blogger insists on putting it vertical.  What can you do?

Another "self-inflicted" problem occurred when sometime later I tried to turn on the Kenwood PS-430 power supply for the Elecraft K3S.  It would not come on.  I pulled it out and checked the fuse which was good.  Luckily at that point (before beginning more extensive tests) I noticed that the power cable for the PS-430 had come loose and fallen behind the operating table!  I guess I did that while messing with the installation of the CX-600NL relay above.  Oh, well.  At least that was not hard to fix.

I had used an ohmmeter to find which of the relay ports was NO (Normally Open) and which was NC (Normally Closed) and I marked them with my label maker.  Next I connected the cable that runs from the Common port of the relay to the Elecraft K3S and checked the continuity of the center pin of the BNC connector on the radio end of the cable to the center pin of the N-connector on the NC contact of the relay.  All was good.  At that point, after cycling the relay several times from the Sequencer and checking that the contacts switched correctly, I connected the cables to the NO and NC ports and mounted the relay.  Just before connecting the other ends of the cables, I ran a final continuity check and the cable that connects to the NC port on the relay (and goes to the Driver Input of the amplifier) showed it was open.  I removed the cable from the relay to the amplifier and checked the continuity of the center pins and it was good.  But, when I put the cable back on the relay and checked it again, it was open.  I disconnected the cable and in looking closely at the connectors, I noticed the center pins on both ends were recessed much further than they should have been.

I measured the tip of the center pin as being 6/64" recessed from the reference plane of the connector!  Most of the N-connectors I looked at have that tip of the pin either even with or just ever so slightly below the reference plane.  The depth of the shoulder of the pin was 18/64" (0.28125 inches) from the reference plane.  That depth should be between 0.210 to 0.230 inches.  That meant these pins were, between 0.05125 to 0.07125 inches SHORT.  In the picture above you can see that the tip of the center pin is well below the reference plane.  This meant that because the center pins were so far back in the connector, they simply were not making contact with the center pin of the female connector. 

I tried to avoid problems like this in my project by purchasing NEW cables.  This cable was purchased January 18, 2016 as an N Male to N Male Cable 36 Inch Length Using RG142 Coax for $13.50 plus $3.35 shipping.  I guess I'll try to contact the eBay seller who sold me this for either a replacement or a refund.  In the short-term, I found a 1m N-to-N piece of 1/2-inch Heliax that I can use in the meantime.

It turns out that my checking of each step of this project has turned out to be a good thing.  I don't know how long it would have taken me to track down this problem if I had not been checking everything one step at a time. 

I have nearly finished wiring the 3 kW power supply for the W6PQL amp needing only to put the 220 VAC connector on the end of the cable.  Once that is done, I can hook it up to the 220 line and see if it will produce 48 VDC.  At that point, I'm ready to slap some RF to the amp and see if I can blow something up!

On the photo at the right you can see I have run the Red and Black cables from the output pins of the power supply through a toroid to hopefully cut down on any RFI from the power supply.  The Green, White and Blue cables at the top are the 220 VAC input cables.  The Blue cable runs through a switch on the front of the amp that switches the power supply on and off and provides protection from high inrush current that is common to switching supplies.

I also labeled and connected the PTT cable from the DEMI Sequencer to the W6PQL amplifier.  That is one other part of this project that has taken a bit extra time.  I have tried to document everything I have done on this project so that if need be, I will not have to re-invent the wheel if I need to trouble-shoot any future problems.  Also, I have tried to be meticulous in labeling all cables so that if anything becomes disconnected or needs to be checked, it will be obvious where that cable goes.  Plus, if I should need to disassemble and move the station in the future, it will be a snap to put it all back together.

Thursday, October 26, 2017

Big Day on the 2-M EME Project

Wheeeeee!  Big-Time progress was made today.  I did some minor work on the antennas by covering the driven element screws with Coax-Seal, putting some Silica Gel packets in the T/R Relay - LNA box to keep down the condensation, taping some of the control lines together, and making a small re-alignment of the rearward boom.  

The next step was to see how far off my rotor indicators were from where they should be.  I had a good visual on the moon so I had Evelyn use the Rain Proof Hoist Crane Pendant to move the antennas as I stood out in the yard to visually align them with the moon.  Once we had the moon square in the sights of the antennas, I went inside and looked at where the MoonSked program said the moon really was in Azimuth and Elevation from my QTH, and compared that to what the rotors indicated on the EA4TX ARS-USB rotor controller.  I then repeated that same operation four more times over the next hour or two.  As it turned out, my Azimuth reading was consistently 7° greater than what it should be and my Elevation reading was 5° less than what it should be.  Here is what the antennas looked like when we had the pointing "nailed."  Note that in the photo below you can see the moon lined up with the left-hand antenna. (Click on any photo to see a larger image.)

Now here is where things got GOOD!  I have a "driver" program that interfaces between MoonSked and the EA4TX ARS-USB unit and in looking at it, there is a "Setup" button.  When I opened the setup screen, there were two adjustments to "compensate" the readings between the two.  I inserted a +7° in the Azimuth box and -5° in Elevation box and told the driver program to "AutoTrack" the moon.  It adjusted the rotors to exactly where they "should" be pointing and I ran out in the yard to see that BINGO! - the antennas were indeed pointed right at the Lunar Orb!  WHEEEEE!  This is HUGE for my project to have the antennas actually pointing at the moon consistently and the AutoTrack feature working to keep them pointed there regardless of whether or not I can see the moon!

After that, I began running WSJT 10.0 as well as the MAP65 program while the AutoTrack kept my antennas pointed at the moon.  After about an hour, I saw on the WSJT EME - 1 chat page that K9MRI was calling CQ on 144.149 MHz.  I put my K3S on that frequency and WHAM! - the WSJT 10.0 program copied his CQ!  At 2309 GMT I copied his first CQ and then at 2313 I copied him with the best signal strength of -18 dB:

231300  6  -18  2.9 -283  3 *      CQ K9MRI EN70             1  10

K9MRI is running 8-M2 XP28 Yagi's and 1 kW.  So, he has a pretty big signal.  However, it is interesting to note that at 2300 GMT, the Degradation is 5.8 dB so not the best of conditions.  That probably explains why I was not able to copy the two or three 2-yagi stations that K9MRI worked over the next hour or so.  Still, I'm totally PUMPED that my receive is doing as well as it is.

But, I noticed that while I could copy K9MRI just fine on WSJT 10.0, I had zero copy on MAP65.  I began looking to see what could be causing that program to not receive and realized that when I had selected the Audio Source (which was for the FUNcub Dongle Pro+ SDR Thumb Drive) I had chosen the DirectX audio stream.  There was also an MME audio stream so I selected that instead and a few minutes later, MAP65 copied K9MRI - SUCCESS!

Now as I sat at the computer, I could see both WSJT 10.0 and MAP65 copying the signals off the moon.  This is AWESOME!!!  One reason I was trying to get the MAP65 program running is that it basically works like CW Skimmer in that it listens to 60 kHz of the 2-M band all at once and copies EVERY station it hears.  It prints out the messages that those stations are sending along with the frequency they are transmitting on, the audio frequency offset and the signal strength!  Since I was only able to copy one station tonight, here on the right is the "Messages" window of MAP65 showing the signals I actually copied!

The color code gives the most recent messages in Red, older ones in Yellow and the oldest in Gray.  All I need now is to have a little better conditions so I can hear more stations to see just how valuable this MAP65 program will be to me.

I can't wait for conditions to get better.  And, I am really, really close to being able to transmit.  I have the TX feedline connected, the wiring of the amplifier power supply is nearly complete, and there is not too much I still need to do to finish off this project.  If nothing gets in my way, it should just be a few days until I can echo test.

NEWS FLASH!!!  -  As I was typing this, the screen I was typing on was covering the MAP65 screen.  I just took a look and WOW, I had copied another station off the moon:

149 -151 0 0110 2.6 -26 # CQ K5LA DM61 0 23 0

I actually copied two CQ's from K5LA and this was the strongest one.  K5LA runs four 9-element yagis and is located in El Paso, TX.

Finally, on the left is a shot of the antenna array.  You can see the feedlines from the back of each antenna connecting to the power divider, which then connects to the T/R Relay - LNA box on the rearward boom, and inside that PVC box is the T/R Relay and the LNA (preamp.)

Lots of work has gone into this setup and it's about time for it to pay off!  Right now the moon is down to under 14° Elevation so it's time to shut things down and hit the sack.  I took a look out the front door and the moon is beautifully hanging over Hurricane.  Maybe I'll keep the station listening for a little longer just in case a VK, ZL or JA shows up [grin].

P.S.  A ZL did indeed show up on the Chat page but my noise had jumped up to S-9 so there was no chance for me to copy him.   Another time - I will!

Monday, October 16, 2017

Connecting the TX Inhibit Circuit to the K3S

In order for the TX Inhibit circuit which I built into the Sequencer (See HERE) to work with the Elecraft K3S, I needed to wire a couple of connections from the Sequencer to the K3S ACC jack and change some Menu Settings on the K3S. Since I already have other accessories connected to that jack, I purchased a DB15HD "Y" cable as well as a DB-15 Male Breakout Board.  The "Y" cable was connected to the K3S ACC jack, my other accessories were connected to one branch of the "Y" and the other branch was connected to the breakout board.  You can see the breakout board in the photo below with a 2-conductor shielded cable which connects Pin 7 (TX Inhibit line) and Pin 13 (BANDØ line) to the Sequencer.

DB-15 Male Breakout Board
The K3S has several Band Outputs which will produce either a Ø or a 1 condition with Ø being when the line is pulled to ground (Ø V) and the 1 being when the line is floating at 5 V.  These Ø and 1 outputs can be used to control many things.  In order for these Band Outputs to be used to control the TX Inhibit circuit, some settings in the K3S need to be adjusted.  First,

CONFIG:KIO3B is set to TRN.  This sets the BANDØ-3 outputs to reflect the parameters of the CONFIG:XVn ADR menu entry.  There is a chart in the manual that shows which conditions will be produced by different Transverter Addresses.  I chose the TRN setting for the CONFIG:KIO3B menu item instead of HF-TRN because using the latter would give me a 1 output on various HF bands in addition to 2-M.  Using the TRN setting, I only get a 1 output on BANDØ when the K3S is tuned to the 2-M band.  That is where I need to enable the TX Inhibit line.

As I'm using the Internal 2-M Transverter in the K3S, it is delineated as Transverter 1 (TRN1) and therefore, I set CONFIG:XV1 ADR to Int. trn1.  This causes the radio to output a 1 on BANDØ when the K3S' VFO A is tuned to 2-M.  With the above settings, I will ONLY see a 1 on the BANDØ output line when the radio's A VFO is tuned to 2-M and not on any other bands.

To make sure I really understood all this, I connected the lines from the Breakout Board to the sequencer with clip leads and a volt-meter.   When I would change bands I could see the 5VDC output vary according to where the CONFIG:KIO3B menu item was set.  Watching the output on BANDØ allowed me to also test the TRN and the HF-TRN settings as well.  Once I had that figured out, I used a clip lead to put the sequencer into transmit and could see that my circuit (KL7UW's circuit) was functioning properly.

The Sequencer contains a 5 VDC power supply which I built from a circuit I found by KL7UW and that voltage is used to control the K3S' TX Inhibit line.  From the K3S manual: "Pin 7 of the ACC connector can be configured as a transmit inhibit input by setting CONFIG:TX INH to LO=Inh (or HI=Inh). Holding pin 7 low (or high) will then prevent transmit."  Putting the TX INH setting to HI = Inh will tell the K3S to NOT go into transmit if there is a 5 V signal on that line.  The KL7UW circuit connects to Pin 13 (BANDØ) to determine when the K3S is tuned to 2-M.  If that line is HI (5 V) then the circuit turns on a transistor which then pulls in a relay.  That relay connects the 5 VDC power supply I built in the Sequencer to Pin 7 (TX Inhibit) to prevent the K3S from transmitting.

To make this work, I had to set the CONFIG:TX INH menu setting in the K3S to HI = Inh so that a HI (5 VDC) voltage on Pin 7 will prevent the K3S from transmitting.  When there is a HI (5 VDC) voltage on Pin 7 of the K3S, the front panel of the K3S indicates this by flashing the TX indicator.

The whole purpose of this TX Inhibit circuit configuration is to make sure that the K3S will NOT transmit any signal until the T/R Relay has completely switched to the XMIT position.  Stage 4 of the Sequencer connects internally within the Sequencer box to the KL7UW circuit so that it shorts out the 5 VDC supply that is connected to Pin 7.  That places a LOW (0 V) on Pin 7 and the K3S can now transmit.  But this ONLY takes place after power is removed from the LNA and the CX-600NL relay, the T/R relay is de-energized to place it on the TX position, and the Amplifier PTT circuit is closed.  ONLY then can the K3S produce a signal.  This is a safety circuit to keep the system from accidentally transmitting when it shouldn't. 

One more piece of the puzzle is now complete.  I am down to needing to install one connector on the TX feedline (7/8-inch Heliax), finish the amplifier power supply, and a couple of other minor items and I'll be ready to transmit!!!

Sunday, October 8, 2017

Another Great Night of Listening to EME Signals

EME conditions on 2-M were not really optimum tonight.  The degradation was -2.6 dB which meant there was some room for improvement.  Still, it was the ARRL EME Contest weekend and I expected there would be a lot of activity, but the weather forecast called for rain and I felt that if I could not see the moon to align the antennas, it would not be worth the effort to get up in the middle of the night!

I woke up just after 0730 GMT and saw moonlight outside so I thought "Hey, I can visually aim the antennas!"  Therefore I got dressed, fired up the station, rotated the antennas to where they should be pointing at the moon, and went outside to see how far off the antennas were.  However, the clouds had rolled in and I could not see the moon!  Bummer!  So, I started listening to the moon anyway about 0750 GMT since everything was turned on and hoped I could get the antennas close.

At 0819 GMT I copied K9MRI at -24 dB (K9MRI runs EIGHT M2 XP28 yagis and a kW) calling RI1F on 144.108 MHz. 

FileID Sync dB   DT  DF   W
081900  4  -24  2.6 -253  3 *      RI1F K9MRI EN70           1   0

Then at 0824 GMT I copied KL7UW (-26 dB) running 1200-1400 watts to 4 M2 X-20 antennas calling CQ on 144.117 MHz. 

FileID Sync dB   DT  DF   W  
083800  1  -24  5.3-1025  2 *      CQ KL7UW BP40             1  10

Then I copied KG6NUB (at -24 dB) which is a contest call of the Stanford Club (W6YX/QRO/4X5WL Stanfordclub CA CM87wj) calling KL7UW:

FileID Sync dB   DT  DF   W  
083900  2  -24  2.3 -961  3 *      KL7UW KG6NUB CM87         1   0

Back on 144.108 MHz I copied:
first, VE2PN at -22 dB calling RI1F (VE2PN/2X10H/600 Marc QC FN46jw):

FileID Sync dB   DT  DF   W  
091500  3  -22  2.7  186  3 *      RI1F VE2PN FN46           1   0

and then W4RBO at -23 dB calling RI1F (W4RBO/4X12H/K John FL EL99kf):

FileID Sync dB   DT  DF   W  
091900  2  -23  1.9 -213  3 *      RI1F W4RBO EL99           1   0

Just after that I copied NH6Y at -21 dB (NH6Y/4X9/1K5 Tom HI BL10ts) on 144.117 MHz:

FileID Sync dB   DT  DF   W  
093800  3  -21  2.3   32  3 #      K2UYH NH6Y BL10     OOO   1   0

and shortly before that K2UYH (K2UYH 2 x XP28 + kW) reported on PingJockey that he was copying NH6Y at -22 dB:

FileID Sync dB   DT  DF   W  
0928 -22  2.4 1295 #* CQ NH6Y BL10  ====== {K2UYH Team NJ FN20ll)

It seemed that I had a 1 dB better copy on the Hawaii station than K2UYH did with his pair of M2 XP28 yagis.  Cool!

After that I copied WØXG at -27 dB (W0XG/4M2XP20/K Eric MN EN34gx) calling K8DIO on 144.106 MHz:

FileID Sync dB   DT  DF   W  
101200  0  -27  2.2 -511  4 *      K8DIO W0XG EN34           1   0

Later I copied WØXG even stronger at -25 dB:

FileID Sync dB   DT  DF   W  
102200  3  -25  2.5 -519  1 *      CQ W0XG EN34              0  10

I then copied N1DPM at -24 dB (N1DPM/4X9/KW Fred MA FN32qb) calling CQ on 144.124 MHz.:

FileID Sync dB   DT  DF   W  
103800  2  -24  2.9 -301  3 *      CQ N1DPM FN32             1   0

Then the JA window opened and I copied JJ3JHP at -23 dB (JJ3JHP/4X12 Hiro xx PM75xd) calling CQ on 144.129 MHz.

FileID Sync dB   DT  DF   W  
104700  4  -23  2.8  -24  1 *      CQ JJ3JHP PM75            1  10

Later I saw a report on PingJockey from N1DPM (N1DPM/4X9/KW Fred MA FN32qb) that he had copied JJ3JHP at -21 dB with his four 9-element yagis.

At 1115 GMT I again copied JJ3JHP (JJ3JHP/4X12 Hiro xx PM75xd) calling CQ at -28 dB:

FileID Sync dB   DT  DF   W  
111500  2  -28  2.9  110  3 *      CQ JJ3JHP PM75            0  10

And right after that I saw on PingJockey this report:

111500  3  -25  1.5   -8  3 *      CQ JJ3JHP PM75            1  10 ====== (AC7FL/4X12H300W Stuart AZ)
which said with his four 12-element antennas, Stuart had a 3 dB better copy of JJ3JPH at the exact same time as I did with my two 13-element yagis.  Plus, I was experiencing a light but steady rain at that time.  That tells me that my system is performing on a par with other stations and that's good news to me.

Then at 1208 GMT I copied the Stanford station, KG6NUB, (W6YX/QRO/4X5WL Stanfordclub CA CM87wj) calling JHØBBE on 144.131 MHz:

FileID Sync dB   DT  DF   W  
120800  5  -22  2.7 -210  3 *      JH0BBE KG6NUB CM87        1   0

During the night I saw a couple of false decodes like this:

FileID Sync dB   DT  DF   W  
122600  0   -6  3.4  -89  3 *      W8TN FS5UQ FK88           0  10

It is curious because the DT parameter (4th from the left) of 3.4 seconds could be an EME sigal.  But, the -6 dB signal strength is just WAY too strong. 

At 1229 GMT I knew from PingJockey that NH6Y was calling CQ on 144.117 MHz.  I got a decent trace on several periods but only printed this:

FileID Sync dB   DT  DF   W  
123200  1  -26  2.3 -170  3 *  
123400  2  -26  2.3 -172  3 * 
123600  3  -25  2.3 -172  3 * 


Finally I copied this:
FileID Sync dB   DT  DF   W  
123800  7  -22  2.3 -175  3 *      CQ NH6Y BL10              1   0

Although I had earlier copied JJ3JHP as strong as -23 dB, and he announced on PingJockey at 1244 GMT that he was calling CQ on 144.105 MHz., I was not able to see even the slightest trace over 3 periods.  It sure looks like Faraday rotation changed the game!  However, on the 4th period, I did copy the following which has a DT that agrees with my earlier copy on JJ3JHP:

FileID Sync dB   DT  DF   W
125300  0  -32  2.9 -552 41 *      

I did see on PingJockey that Art, N9BCA, worked NH6Y for his State No. 50.  Art said:
08 Oct 12:49 nh6y  THIS IS ONE OF MY HAPPIEST DAYS EVER TKS #50  73 ====== (N9BCA Art WI EN54ll)
Later I saw on the chat page that K2TW said he would call NH6Y on the next sequence on 144.117 MHz.  Shortly after that I saw TWO traces in the same period, one at -30 Hz and one at -192 Hz.  I decoded both and got this result:

FileID Sync dB   DT  DF   W  
130000  6  -27      -192  2   RRR                                 
130000  2  -30       -30  4   RO          


Followed by:
FileID Sync dB   DT  DF   W  
130200  4  -29      -192  3   73  

I wonder if there was another station that thought NH6Y was calling them too at the same time?

I then saw this on PingJockey:
08 Oct 13:02 NH6Y Tom tnx first HI, bet you hear that a lot! 73 ====== {K2TW/4XP9/KW Tom NJ FN20ll)
So it looks like I "sort of" copied K2TW - at least on his "RRR" and "73" transmissions.  I'm gonna count it!

At 1308 GMT N9LHS was going to call NH6Y on 144.117 MHz so I kept listening on that frequency.  But, I did not hear anyone.  My EL was down to 13° so I don't know if it was too low at that point.  I continued to listen to stations who announced they were calling CQ like BX4AP (BX4AP/4X9H Jesse xx PL04if) and N4HB (N4HB/4X7H/750 Henry VA FM17uu) but I was never able to copy anyone.  Maybe the moon was too low at this point for me.

My best copy of the night was NH6Y from Hawaii at -21 dB.  Tom (NH6Y) was running four 9-element yagis and 1,500 watts.  The two smallest stations I copied tonight were running less than or essentially the same as what I am running:
VE2PN - two 10-element yagis and 600-watts
K2UYH - two XP28 yagis and a kW

All in all, this turned out to be a WONDERFUL night of playing EME even though all I could do was receive.  I was able to copy 10 different stations off the moon from the USA, Alaska, Canada, Hawaii and Japan.  Now that's pretty sweet!  I also learned that I can copy stations even during a rain storm and that my received signal seems to be pretty close to what others are reporting for the same station at the same time.  I am really glad that I did not go back to bed when I saw the clouds had obscured the moon.  It really paid off for me!  And, it REALLY makes me want to get the transmit part of the station operational!