Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: Re: 137.1 kc at df2py

To: [email protected]
Subject: Re: LF: Re: 137.1 kc at df2py
From: Gerhard Hickl <[email protected]>
Date: Fri, 02 Jul 2010 23:07:27 +0200
In-reply-to: <003301cb1a00$e034a5e0$0301a8c0@your91hoehfy9g>
References: <668C63FD05804C3CA542F9CF65AA4F96@df2py> <003301cb1a00$e034a5e0$0301a8c0@your91hoehfy9g>
Reply-to: [email protected]
Sender: [email protected]
ge Mal!

I agree, activity on 137 is poor in the moment and even someone is
active, it is in a "automated"-mode.

This might have to do partially with the poor conditions. But on the
other hand it has to do with the season in general. Summertime is always
busy for someone who owns a house and a garden as it is in my case.

I bought a 18m fibre-pole in Friedrichshafen last weekend which is
supposed to replace the 12m pole I'm using now. I wonder if I would be
able to do the swap until fall....

I'm looking forward to winter and a possible (plain and simple) CW-QSO
with you. I'm sure, activity in general will increase!

73 es gl

OE3GHB
Gerhard






Am Freitag, den 02.07.2010, 17:08 +0100 schrieb mal hamilton:
>  
> what has gone wrong on 137 kcs. Now the best anyone can do is radiate
> a Carrier, appliance mode like Ros etc.
> Not long ago there was over 30 countries active on normal CW with BIG
> signals. This is going backwards,  certainly not progressive signal
> technology as some would make you believe.
> Beacons, Carriers, Appliance modes, QSL via EMAIL.   WHAT NEXT even
> CB ers are doing better at communication.
>  g3kev
>         ----- Original Message ----- 
>         From: Wolf Ostwald 
>         To: [email protected] 
>         Sent: Friday, July 02, 2010 1:12 PM
>         Subject: LF: 137.1 kc at df2py
>         
>         
>         Hi amigos J
>         
>         I am transmitting a carrier on 137.1  from 1200z on.
>         
>         I hope it can be detected in a few places.
>         
>         73 de wolf
>         
>         




<Prev in Thread] Current Thread [Next in Thread>