Date   

Re: Zulu time, GMT & UTC

Paula K7PAX #1739
 

Good to know about Iceland time. That could be very useful!

Paula K7PAX

On Dec 10, 2020, at 10:50 AM, Josef 'Jeff' Sipek <jeffpc@josefsipek.net> wrote:

On Thu, Dec 10, 2020 at 18:07:46 +0000, Jerry N9AVY wrote:
This may clear up some confusion about time ...
Jerry n9avy

"Zulu" time, more commonly know as "GMT" ( Greenwich Mean Time )
is time at the Zero Meridian. ... Due to various scientific reasons and
increased accuracy in measuring the earth's rotation, a new timescale,
called Universal Time Coordinated or Coordinated Universal Time (UTC), has
been adopted and replaced the term GMT.
This is true. Additionally, using "GMT" can get *really* confusing, and
that's why I avoid it.

There is a subtle difference between the three quantities.

During the winter, UTC = GMT = "time in the UK" (well, +-1 second).

During the summer, things get more complicated. While UTC just continues on
without interruption, the "time in the UK" is BST (British Summer Time)
which equals UTC+1 hour. GMT is the confusing one. Some say that it is
equal to UTC, some say that it is equal to "time in the UK". (Obviously, it
cannot be both.)

It's very annoying to deal with, and that's why I strongly suggest everyone
avoids saying "GMT" - especially during the summer.

In short:

* if you mean "zulu" time, write "UTC"
* if you mean "time in the UK", just write it out. (E.g., "let's meet at
noon London-time" or if it is clear from the context: "noon local time")

Tip for scheduling cross-timezone meetings:

Make sure you agree on both the time and the timezone. Then, enter the
event into your calendar as that - even if it isn't your timezone. Any
calendaring program worth using will correctly deal with changes to DST. If
you try to be clever, you might end up showing up at the wrong time.

For example, say I living in Massachusetts want to schedule a QSO with
someone in Frankfurt, Germany. If we agree to 12:30 local time in
Frankfurt, I'll enter it into my calendar just like that: 12:30 in
Frankfurt. Then, it doesn't matter if it is DST here, summer time in EU, or
the weird in-between few weeks where the US is on DST but EU is still on
winter time.

If I try to be clever, and instead of 12:30 in Frankfurt I put 06:30 in
Massachusetts it may work most of the time (namely when US and EU are both
using winter/summer time). But during the spring and fall, when the local
time difference between MA and Germany is only 5 hours, I'll have to be on
the radio at 07:30. Had I entered it as 12:30 Frankfurt, the calendar would
have automatically figured it out. But if I enter it as 06:30 MA, the
calendar doesn't know it should adjust it by an hour.

Oh, and if you want to schedule something for a UTC time and your calendar
doesn't let you enter "zulu" time, pick Iceland as the timezone location.
Iceland uses UTC year-round as their local time.

Huh... this turned out longer than I anticipated. Anyway, calendaring is
hard, timezones are hard, and it is a minor miracle civilization hasn't
collapsed because of the two :)

Jeff.






Re: Zulu time, GMT & UTC

Josef 'Jeff' Sipek
 

On Thu, Dec 10, 2020 at 13:58:41 -0500, Josef 'Jeff' Sipek wrote:
On Thu, Dec 10, 2020 at 18:38:28 +0000, Jerry N9AVY wrote:
...
Once you know your time zone is it get easier.  For example:  CST is
GMT/UTC plus 5 hours and CDST is plus 6 hours.  Simple, yes ?
Assuming CST is Central Standard Time, I have two things to point out:

(1)

CST is UTC *minus* 6 hours
CDT is UTC *minus* 5 hours

(2) The official abbreviations for the timezones in the lower 48 states are:
EST/CST/MST/PST (winter/non-DST) and EDT/CDT/MDT/PDT (winter/DST)
Err, copy & paste error - that should read:

(2) The official abbreviations for the timezones in the lower 48 states are:
EST/CST/MST/PST (winter/non-DST) and EDT/CDT/MDT/PDT (summer/DST)


Sorry,

Jeff.



Jeff.


Jerry  n9avy
On Thursday, December 10, 2020, 12:31:23 PM CST, Rick - N7WE <n7we1980@gmail.com> wrote:

I find the attached chart helpful.
--
Rick - N7WE
070 - #1602










Re: Zulu time, GMT & UTC

Josef 'Jeff' Sipek
 

On Thu, Dec 10, 2020 at 18:38:28 +0000, Jerry N9AVY wrote:
...
Once you know your time zone is it get easier.  For example:  CST is
GMT/UTC plus 5 hours and CDST is plus 6 hours.  Simple, yes ?
Assuming CST is Central Standard Time, I have two things to point out:

(1)

CST is UTC *minus* 6 hours
CDT is UTC *minus* 5 hours

(2) The official abbreviations for the timezones in the lower 48 states are:
EST/CST/MST/PST (winter/non-DST) and EDT/CDT/MDT/PDT (winter/DST)

Jeff.


Jerry  n9avy
On Thursday, December 10, 2020, 12:31:23 PM CST, Rick - N7WE <n7we1980@gmail.com> wrote:

I find the attached chart helpful.
--
Rick - N7WE
070 - #1602





Re: Zulu time, GMT & UTC

Josef 'Jeff' Sipek
 

On Thu, Dec 10, 2020 at 18:07:46 +0000, Jerry N9AVY wrote:
This may clear up some confusion about time ...
Jerry  n9avy

"Zulu" time, more commonly know as "GMT" ( Greenwich Mean Time )
is time at the Zero Meridian. ... Due to various scientific reasons and
increased accuracy in measuring the earth's rotation, a new timescale,
called Universal Time Coordinated or Coordinated Universal Time (UTC), has
been adopted and replaced the term GMT.
This is true. Additionally, using "GMT" can get *really* confusing, and
that's why I avoid it.

There is a subtle difference between the three quantities.

During the winter, UTC = GMT = "time in the UK" (well, +-1 second).

During the summer, things get more complicated. While UTC just continues on
without interruption, the "time in the UK" is BST (British Summer Time)
which equals UTC+1 hour. GMT is the confusing one. Some say that it is
equal to UTC, some say that it is equal to "time in the UK". (Obviously, it
cannot be both.)

It's very annoying to deal with, and that's why I strongly suggest everyone
avoids saying "GMT" - especially during the summer.

In short:

* if you mean "zulu" time, write "UTC"
* if you mean "time in the UK", just write it out. (E.g., "let's meet at
noon London-time" or if it is clear from the context: "noon local time")

Tip for scheduling cross-timezone meetings:

Make sure you agree on both the time and the timezone. Then, enter the
event into your calendar as that - even if it isn't your timezone. Any
calendaring program worth using will correctly deal with changes to DST. If
you try to be clever, you might end up showing up at the wrong time.

For example, say I living in Massachusetts want to schedule a QSO with
someone in Frankfurt, Germany. If we agree to 12:30 local time in
Frankfurt, I'll enter it into my calendar just like that: 12:30 in
Frankfurt. Then, it doesn't matter if it is DST here, summer time in EU, or
the weird in-between few weeks where the US is on DST but EU is still on
winter time.

If I try to be clever, and instead of 12:30 in Frankfurt I put 06:30 in
Massachusetts it may work most of the time (namely when US and EU are both
using winter/summer time). But during the spring and fall, when the local
time difference between MA and Germany is only 5 hours, I'll have to be on
the radio at 07:30. Had I entered it as 12:30 Frankfurt, the calendar would
have automatically figured it out. But if I enter it as 06:30 MA, the
calendar doesn't know it should adjust it by an hour.

Oh, and if you want to schedule something for a UTC time and your calendar
doesn't let you enter "zulu" time, pick Iceland as the timezone location.
Iceland uses UTC year-round as their local time.

Huh... this turned out longer than I anticipated. Anyway, calendaring is
hard, timezones are hard, and it is a minor miracle civilization hasn't
collapsed because of the two :)

Jeff.


Re: Zulu time, GMT & UTC

Jerry N9AVY
 

It's a helpful chart, but it's easier to hand the GMT/UTC/Zulu time at 0000 hours in one's mind and start from there rather than having to refer to a chart.  Am sure chart will be helpful to many, but I wouldn't rely on it too heavily.

Once you know your time zone is it get easier.  For example:  CST is GMT/UTC plus 5 hours and CDST is plus 6 hours.  Simple, yes ?

Jerry  n9avy

On Thursday, December 10, 2020, 12:31:23 PM CST, Rick - N7WE <n7we1980@...> wrote:


I find the attached chart helpful.
--
Rick - N7WE
070 - #1602


Re: Zulu time, GMT & UTC

Rick - N7WE
 

I find the attached chart helpful.
--
Rick - N7WE
070 - #1602


Re: Zulu time, GMT & UTC

Fr Richard R
 

Thank you Jerry

Fr Richard
WB8YXF




On Thursday, December 10, 2020, 1:07:54 PM EST, Jerry N9AVY <n9avy@...> wrote:


This may clear up some confusion about time ...

Jerry  n9avy


"Zulutime, more commonly know as "GMT" ( Greenwich Mean Time ) is time at the Zero Meridian. ... Due to various scientific reasons and increased accuracy in measuring the earth's rotation, a new timescale, called Universal Time Coordinated or Coordinated Universal Time (UTC), has been adopted and replaced the term GMT.


Zulu time, GMT & UTC

Jerry N9AVY
 

This may clear up some confusion about time ...

Jerry  n9avy


"Zulutime, more commonly know as "GMT" ( Greenwich Mean Time ) is time at the Zero Meridian. ... Due to various scientific reasons and increased accuracy in measuring the earth's rotation, a new timescale, called Universal Time Coordinated or Coordinated Universal Time (UTC), has been adopted and replaced the term GMT.


DOUBLEHEADER TRIPLE PLAY LOW BAND SPRINT – Tomorrow

stan W9SMR
 

The Ø7Ø Club DOUBLEHEADER TRIPLE PLAY LOW BAND SPRINT

 

Starts tomorrow evening.

 

Saturday, December 12 - 0000 UTC
to
 Monday, December 14 - 0000 UTC

 

This is a 3 day event – Friday, Saturday and Sunday evenings in US

Sprint Rules – Work a 6 hour block each UTC Date. For Scoring, your 6 hour block will start with the hour you select on the Scoring page and continue for the next 6 hours. You may have only one “Block” or “Block Portion” on a given UTC date.

 

NOTE  that any start time of 1800 or later will end at 2359 that UTC day, so those times are consolidated into a single "1800-2300" start time selection in the Contest Scorer.

 

Work each station once per band. (Same station, same band, different day is a dupe!)

 

Open to all licensed radio amateurs. Using 40M, 80M and 160M.

For Rules and detailsClick Here: Doubleheader Rules


Frequencies
: - 1.807 / 1.838 MHz (Europe). 3.580 MHz, 7.070 / 7.040 / 7.035 (Europe) MHz


4 Power Categories
:

QRP < 5 W
Low < 25 W
Medium < 50 W
High < 100 W


Exchange:
 Callsign,  RST  and  State/Province/Country (SPC)    eg: “W9SMR  599  FL”


Call: “CQ 070 Sprint”


All entry logs
 must be uploaded within 1 week after the event ends. See Uploader Link in Rules.


This event will again test your ingenuity and stealthy antenna talents. But with 3 bands to choose from, you can optimize your luck with propagation.

 

This event will also decide the ultimate 2020 winner of the annual RC3 (Rollo Cup Contest Championship). In a surprise spectacular showing in the Triple Header contest last month, John, KC3FL pulled ahead of Lee, N5SLY by a mere 5.91 points (904.39 / 898.48). Lee has been challenged to get that 160M antenna up and humming.


And it will again be worth entering, in order to grab that Top Band Endorsement Sticker with 20 QSOS on 160M. Only
44 of our 2,810 members have earned the Top Band Sticker.

 

And 160M QSOs count as 3 points each.

 

Especially for help in grabbing a few 160M QSOs, it is helpful to post your intentions to QSY on the Reflector. Also, be sure to use PSKReporter and to Spot calls seen. We need all the help we can get.

 

This is one of our most popular contests. Last year 41 logs were submitted. Top Dawg and 1st in High Power was Lee, N5SLY, with 78 QSOs and 3210 points.

 

 

Let’s see if we can beat that turnout. 




73,

Stan

W9SMR - 070  #1611

PODXS 070 - PR Director


RC3 Standings

Stephen Melachrinos
 

As the scorer of the RC3 championship, I have a request to make to a small subset of our members.

First of all, if you are unfamiliar with the Rollo Cup Contest Championship (RC3), it's the year-long challenge to determine who did "best" in the year's ten 070 club contests. Rules and standings for this year are on the web site.


If all of your contest entries used an identical callsign, you are off the hook. You don't have to read the rest of this. Feel free to scroll to the next email. But if you operated in our contests during this year and didn't use the same callsign for all contests, please read the following and determine whether my request applies to you.

There are a number of reasons why you might have operated under different callsigns, including:

1. You received a new callsign during the year, assigned to you by your licensing authority (e.g., FCC).
2. You operated one or more contests using a portable identifier, e.g. W3HF/KH2.
3. You operated one or more contests using a secondary or alternate callsign that is assigned to you personally (like my VQ9HF call), and that callsign is NOT assigned a separate 070 club number.
4. You operated from another station (like a friend's station or a club station) using that friend's or club's callsign.

If any of reasons 1 through 3 apply to you, please check the RC3 leaderboard and make sure I've consolidated your entries. I think I've consolidated entries for each of those reasons, but I might have missed you (especially for a callsign change).

If reason #4 applies, then the club's callsign policy applies, specifically Q5 and Q7. These state that you need to be the control operator of a station that is assigned to you personally for QSOs to accrue to your 070 awards.

If there's another reason that I didn't think of, tell me about it and we'll evaluate the situation.

So the request is that if you see that the leaderboard does NOT show the proper consolidation of your entries, let me know. And furthermore, if you are going to be operating in the Doubleheader this weekend under one of these cases, let me know in advance so I can make sure I score it properly from the start (instead of having to make corrections.

Thanks.

Steve
W3HF


Re: Congrats - November MONTHLY Endorsements

stan W9SMR
 

Mike,

You are so right!

Thanks for waking me up. I derived my list by opening and checking each Endorsement upload. I failed to double check the official LONP listing on you and several others.

Back in July I made the following announcement. This is the latest list of official LONP membership, also:

The list below includes those members who have been approved since January 1, 2020:
LONP  070#  CALL    QSOs
428      #2592  KG5OIB       100
429      #2707  AC8NM       100
430      #2590  KE4PWE       150
431      #2662  KI7OIY       100
432      #1227  KB9UMT       100
433      #2653  W4BZM      100
434      #2267  WJ4HCP      100

I apologize for my sloppiness.

Congrats to all for great dedication to pursue these cherished awards!!

73,
Stan
W9SMR
________________________________________
From: main@070Club.groups.io <main@070Club.groups.io> on behalf of Mike W4BZM <behrcave@...>
Sent: Sunday, December 6, 2020 10:58 AM
To: main@070club.groups.io
Subject: Re: [070Club] Congrats - November MONTHLY Endorsements

Stan, Jerry:

Thank you for all the work you do for the club on endorsements!

I’m a bit confused, though, at the recent posting which reads:


‘Here is a most recent list of those who have submitted logbooks containing 100 or more QSOs since January 1, 2020.

Note that these are not yet officially approved:


#2618            KD6TR            180
#2722             N3XL              130
#2727             K4VBM          128
#2380             N4KP              122
#2662             KI7OIY           115
#2653             W4BZM         113
#985               WB4JJJ          114
#577               K6WRJ           118
#2017             W7RTL           112
#1441             RX3VF            105
#2692             YV4YY            100
#2741             WA4RXK       100”


Yes, I submitted a logbook since Jan 1 which contains 100 or more entries, BUT, I also received notification that I was officially part of the LONP and was awarded LONP #433.  I’m on the LONP list on the web site and I received the “Official Evidence Decal” in the last mailing of stickers.  So I hope that makes me “officially approved”, and that Jerry doesn’t have to waste any time checking my log for LONP credit.

...and again, thank you both for the huge amount of effort you volunteer in support of PODXS 070.


Mike W4BZM



Re: 17 meter Sunday

Brian D. Karcher
 

John,

I am just seeing this email. I would be willing to give 17m a try if you are still up for it. I am in New Orleans, LA. Let me know and I will jump on the radio. 

73,
Brian
KG5GJT 


On Dec 6, 2020, at 12:43 PM, John Hendry KG5OIB <archer@...> wrote:

I tried for about an hour.  No signals.   Maybe next time. 

73 

John
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     de  KG5OIB

     John Hendry

     Decatur, Wise County, Texas

     LOC:  EM13eg

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Re: 17 meter Sunday

John Hendry KG5OIB
 

I tried for about an hour.  No signals.   Maybe next time. 

73 

John
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     de  KG5OIB

     John Hendry

     Decatur, Wise County, Texas

     LOC:  EM13eg

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Re: 17 meter Sunday

John Hendry KG5OIB
 

still trying.  Im at 18.098188

JH
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     de  KG5OIB

     John Hendry

     Decatur, Wise County, Texas

     LOC:  EM13eg

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Re: 17 meter Sunday

Jerry N9AVY
 

 Called  CQ a couple times on 17 around 1745UTC  - NADA!

Jerry  n9avy

On Sunday, December 6, 2020, 11:41:56 AM CST, John Hendry KG5OIB <archer@...> wrote:


Anyone want to try some 17 meters today?   18.097 should be open for a little while.  
I'm calling CQ now  17:40 UTC.

73  John
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     de  KG5OIB

     John Hendry

     Decatur, Wise County, Texas

     LOC:  EM13eg

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


17 meter Sunday

John Hendry KG5OIB
 

Anyone want to try some 17 meters today?   18.097 should be open for a little while.  
I'm calling CQ now  17:40 UTC.

73  John
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     de  KG5OIB

     John Hendry

     Decatur, Wise County, Texas

     LOC:  EM13eg

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Re: Congrats - November MONTHLY Endorsements

Mike W4BZM
 

Stan, Jerry:  

Thank you for all the work you do for the club on endorsements!

I’m a bit confused, though, at the recent posting which reads:

‘Here is a most recent list of those who have submitted logbooks containing 100 or more QSOs since January 1, 2020. 

Note that these are not yet officially approved:

#2618            KD6TR            180
#2722             N3XL              130     
#2727             K4VBM          128
#2380             N4KP              122
#2662             KI7OIY           115
#2653             W4BZM         113

#985               WB4JJJ          114     
#577               K6WRJ           118
#2017             W7RTL           112
#1441             RX3VF            105

#2692             YV4YY            100
#2741             WA4RXK       100”


Yes, I submitted a logbook since Jan 1 which contains 100 or more entries, BUT, I also received notification that I was officially part of the LONP and was awarded LONP #433.  I’m on the LONP list on the web site and I received the “Official Evidence Decal” in the last mailing of stickers.  So I hope that makes me “officially approved”, and that Jerry doesn’t have to waste any time checking my log for LONP credit.

...and again, thank you both for the huge amount of effort you volunteer in support of PODXS 070.


Mike W4BZM


Congrats - November MONTHLY Endorsements

stan W9SMR
 

As  propagation conditions improved recently, we are showing some good gains in member Endorsements. Having several contests has helped also.

LONP - To qualify for LONP, 100 QSOs with fellow members are required. As you are aware, we are struggling with issues on the Endorsement web page that limits our timely approval of Endorsements. Be sure to upload your entire log each time.

Jerry, N9AVY, has been fighting an uphill battle with our balky Endorsement Checker trying to validate and approve candidates for LONP. Here is a most recent list of those who have submitted logbooks containing 100 or more QSOs since January 1, 2020.

Note that these are not yet officially approved:

#2618            KD6TR            180
#2722             N3XL              130    
#2727             K4VBM          128
#2380             N4KP              122
#2662             KI7OIY           115
#2653             W4BZM         113

#985               WB4JJJ          114    
#577               K6WRJ           118
#2017             W7RTL           112
#1441             RX3VF            105

#2692             YV4YY            100
#2741             WA4RXK       100

We also have an excited pack of LONP Seekers in hot pursuit of this traditional first rights award. If you see them, give them a call and spot them on PSKReporter and our reflector:


#2746             KD9DVB        98
#2670             KT5WB           98
#2658             VE3RXO         95
#1797             NA8W            90
#1769             R6KEE            83

#2703             KD2QAK        74
#471               LW2EIY          61

#2691             K5RWG          60
#1341             EA3ATJ          59
#2781             WA3LXD       59
#2754             WX2DX         55

           

And in close pursuit of the next major Honor Roll level at 500 QSOs are:

#138               W7PSK           496
#2566             KC3FL             486

#1609             KC4OBB         455    
            
                                                           

And then there are the Super Achievers with more than 1,000 member QSOs:

1          #0025             W3HF             1650               Has 206 Endorsement Awards
2          #0777             NO8R             1537               Has 183 Endorsement Awards
3          #0815             K8TOM          1258               Has 133 Endorsement Awards
4          #0454             N9AVY           1017               Has 153 Endorsement Awards

24/7 - The big news in October was a unique strategy formed by Alan, KA5VZG, to enable several among us to either achieve of make great progress in the 24/7 Award. This requires making a QSO for every hour slot on every day of the week, 168 slots total. With the enthusiastic support of Bob, KK6KMU, Bob, K4VBM and several others, 4 members qualified with all 168 slots: Alan, KA5VZG, Bob, K4VBN, Don, KC4OBB and David, KR4U. Getting within easy reach were Stan, W9SMR with 166, and Bob, KK6KMU with 160 slots. Those were bleary eyed but very rewarding middle of the night hours.

WTW – Work The World - One of our toughest Endorsements. It requires 2246 specific call sign suffix letters to spell out Country names around the world:

#2241             N5SLY            2246   (Got that last letter, “i” during TDW)

#0354             W7PAQ          2213  (Needs 13 “i” and  20 “n” to complete)

Congratulations to all!

Many more Endorsements were earned, far too many to list. I apologize for any errors and if I missed your efforts. But we applaud the continuing efforts of all to reach for the sky!!  Keep up the good work!

Upcoming 070 Contest:

This is a perfect time to plan your participation in the next PODXS 070 Event, the Doubleheader Triple Play Low Band Sprint. This is another great opportunity to work toward LONP and put some 160M Q’s in the log for the Top Band 20 Endorsement.

DOUBLEHEADER – Triple Play Low Band Sprint
This is a Three Day Contest, 72 hours

Friday, Saturday and Sunday evenings in US

Second Saturday in December

Saturday, December 12 - 0000 UTC

to the Following Monday in December

Monday, December 14 - 2359 UTC

 

 See Rules at:   Doubleheader Rules

 

 

73,
Stan
W9SMR - 070  #1611
PODXS 070 - PR Director


Re: Antennas for 160m

Jerry N9AVY
 

Dick:

I find as I get older my tolerances for height decrease exponentially. Have always had a certain amount of acrophobia, but the job required access to high places and had to overcome it by just doing it, but that didn't always work. Remember a 5 story building in Chicago Z(a Gap store) which had an atrium with a smoke detector that could only be reached from a lift.  Had to rent a lift that would fit through front doors and extend up to ceiling.  Looked at it and couldn't do it; so persuaded my partner to go up.   He later got even when we both working on a scissors lift and he started rocking it while it was fully extended - I panicked !

Looking back I did a lot of dumb and wondered why I did them. Had to do it to keep job and customers, I guess. Last year my balance went to pot; so I retired.

You are very lucky you weren't hurt worse. All you had to deal with was comments from XYL.  

Climbing to 400 ft. cooling tower is something I would never do.  Your employer should have given you flight pay !  

Jerry

On Saturday, December 5, 2020, 07:14:17 PM CST, Richard Rohrer <kc3ef@...> wrote:


Hi Jerry,

Yes, I was very lucky.  Did not even have bruise on my foot.  I was expecting a visit to the ER after the xyl told me how stupid I was, hi hi. 

I never would have gone to the top of a 700 ft plus building and looked over the edge. Don't like heights.  My last employer had me go to the Ivanpah Solar Plant to test and certify the equipment we provided.  I thought no problem, its usually in the control room, but in this case it was at the 400 ft level on the boiler towers.  It looked like there was a single wide trailer placed in the tower that contained the motor controls and our instrumentation.   We could elevator up to 300ft and had to walk up the last 100 ft on a stairway that was made of diamond tread.  You could see all the way down to the ground.  Did not like that at all.  This is why I don't have anything antenna wise that I can't work on from the ground. 

Do you still need grid EL59 in LA?   We are planning a trip to TX coast next Feb so we will be going near there. 

73
Dick - KC3EF


Re: Antennas for 160m

Richard Rohrer
 

Hi Jerry,

Yes, I was very lucky.  Did not even have bruise on my foot.  I was expecting a visit to the ER after the xyl told me how stupid I was, hi hi. 

I never would have gone to the top of a 700 ft plus building and looked over the edge. Don't like heights.  My last employer had me go to the Ivanpah Solar Plant to test and certify the equipment we provided.  I thought no problem, its usually in the control room, but in this case it was at the 400 ft level on the boiler towers.  It looked like there was a single wide trailer placed in the tower that contained the motor controls and our instrumentation.   We could elevator up to 300ft and had to walk up the last 100 ft on a stairway that was made of diamond tread.  You could see all the way down to the ground.  Did not like that at all.  This is why I don't have anything antenna wise that I can't work on from the ground. 

Do you still need grid EL59 in LA?   We are planning a trip to TX coast next Feb so we will be going near there. 

73
Dick - KC3EF

2961 - 2980 of 67708