I have been playing with a new Triquint ULNA device (TQP3M9036). It
Shows a lot of promise. It is like a MAR or MSA device in that it is
50ohm in and out. and has a claimed NF about .4db nf ( their numbers).
I have built several pramps to test them and have gotten even better
than they claim and they cover 50-1296 with ease and NF is .4ish or
below. The S11 and S22 are both great and the OIP3 is +35db also
...very nice device. It has great promise as a good terrestrial LNA.
Preamps are foolproof to build and would cost under $50 if all the best
quality parts are used.
Just for information only ...
Pete WA2ODO
--
++++++CONFIDENTIALITY NOTICE++++++
The information in this email may be confidential and/or privileged. This email is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system.
Sri I made, at least a mistake, I send it again.
Hi all,
Very interesting answers. I come from Sats world, where the Doppler
is a serious issue and it is so quick that it is impossible to work
JT65.
I will speak thinking in one carrier. Sats need to receive in only
one fix frequency (it is an active RX with a wideband), if the Sat
receives a carrier in this frequency then it will be repeated. The
signal TX from the Sat will be in one fix frequency. So people who
work Sats must correct its TX frequency (according with actual
Doppler) to reach the sat in its fix frequency, in the same way
because of the Sats will repeat this signal in a fix frequency, people
must correct its RX frequency (according with actual Doppler).
This way of dealing with Doppler is very interesting because NOBODY
KNOWS the Doppler of the other stations and nobody needs to know it,
we only need to know our own Doppler.
If we would use this agreement to EME communications we will always
speak about the frequency we hit the Moon, in other words the
frequency which the Moon hear us and repeat our signal.
The actual EME software shows us the Doppler as the sum of the Doppler
effects to reach the Moon and to receive the bounce signal, so Moon
will receive us at ½ Doppler announced, the other ½ effect will appear
after de bounce.
I will try to set a couple of examples.
1.- We will agree to hit the Moon in 1296.070. This is the frequency I
will announce in the log. In our software the dates will be:
*Self Doppler
+3KHz
*DX Doppler
-2KHz
The sign that the software shows will aplly to RX frequency and the
opposite to the TX frequency, and always ½ magnitude on each one.
Both of us must deal with Doppler, each one must do their task to hit
the moon in the agreed frequency and to receive the bounce according
our Doppler. Then we must set on our transceivers:
*Me
TX: 1296.070 -1.5KHz = 1296.0685MHz
RX: 1296.070 +1.5KHz= 1296.0715MHz
*DX
TX: 1296.070 +1.0KHz = 1299.071MHz
RX: 1296.070 -1.0KHz= 1296.069MHz
Each station who sees the post will act only according its own
Doppler. Don´t mind where is the DX station.
2.- In this case I see a signal in my receiver in 1296.070. What
kind of pair of frequencies I must set (I know nothing about the DX
station I have still decode nothing), I only know me own Doppler, and
it is +2KHz. I must hit the moon in the same frequency that my
partner:
TX: 1296.070 -1.0KHz = 1296.069MHz
RX: 1296.070 = 1296.070MHz
WE WILL NOT NEED TO KNOW NO MORE THAN OUR DATES.
I haven´t spoken about what frequencies will be the echoes (both
echoes), to make the understanding easy.
As a drawback we should change our habits, we should always use the
RIT as follow:
TX: The frequency we choose plus the opposite sign of Doppler and ½
Doppler magnitude.
RIT: the sign of our Doppler and ½ Doppler magnitude.
Although at first glance it seems not to be interesting in 144MHz but
we will always hit the target in whatever band, even in 144MHz.
Somebody can tell that they need a computer, to do JT65 of course, if
you do CW surely have a smart phone with the proper software to know
your own Doppler or you can print it before.
If I made some mistakes let me know.
It is my 2 cents.
Juan Antonio
EA4CYQ
Its been awhile since I have been QRV with my 2m-eme station.
Four independent problems in my transmission line during the winter
kept me off the Moon and then my HVPS acted up. Well it turned out
to be a simple problem but it didn't appear that way. My 4kV dropped
to 2.8kV without a load. I envisioned all kinds of problems but in
the end it was simply a blown HV fuse. It did not blow open but
instead went to 16meg-ohm which was enough to drop the HV with very
low current being drawn by the HV panel meter.
Having no replacement fuse, I decided to remove the HB fuse holder
from the HVPS since changing the fuse required removing the 8877 deck
from the rack to gain access thru the HVPS top plate which is
directly under the amplifier. I will order some more HV fuses from
Nebraska sales ($25/ea.) and make an inline HV fuse box which will be
much quicker access to replace a fuse. Actually, I have only blown
two of these fuses in 8-years of running.
How I blew this one is that the 6-dB attenuator that I was using to
lower drive to my transverter to keep drive below 50w to the 8877
failed in short resulting in over 100w drive to the 8877. Anode
current spiked taking out the HV fuse as it is designed to
do. Probably hit over 2kW output!
A couple other improvements will make recovery from HV events
quicker: I brought the 240vac mains fuses to the front panel of the
HVPS and increased them to 20A. And I added a vernier to the 8877
drive input cap. Looks like I got a finer tune on the input as it is
taking less drive to reach 1200w.
I will be QRV Sunday from about 1400utc to 1700utc (Moonset):
144.116, 1st for CQ and on N0UK logger. Mon> I will be trying to
work 6W/PE1L in Senegal very early in my morning. We only have about
30-min common Moon on Monday but this increases on subsequent days.
73, Ed - KL7UW
http://www.kl7uw.com
"Kits made by KL7UW"
Dubus Mag business:
dubususa(a)gmail.com
If at all possible try and make an accurate measurement of sun noise during the eclipse period on what ever band you can. Ideally we are looking for the ratio between normal level (measured on the same day) and the minimum sun noise occurring at the time of maximum shadowing. You can get the timing for your exact location from this link. http://eclipse.gsfc.nasa.gov/SEgoogle/SEgoogle2001/SE2015Mar20Tgoogle.html
We believe that we can possibly accumulate some interesting measurements on a non-quiet sun which might indicate how much noise comes from the corona compared to the disc. This influences what value is used for the solar diameter when making beamwidth measurements for example.
GL 73 Peter G3LTF
As anticipated the very strong winds on both days here in S. UK, up to 88kph, meant that there was no possibility of operation except for the first hour or so of the contest, I operated until the dish hit the ground and worked, ES5PC, VE6TA,W5LUA and WA9FWD all with nice signals. I can easily get on 9cm so if anyone wants a test ( CW) let me know, the gear worked fine and I was getting nice ssb echoes.
73 Peter G3LTF
Hi,
Anyone out there using I0JXX 8 element Xpols for 2m EME?
Am seriously thinking of using them along with an HB9DRI IQ+ which I purchased secondhand recently.
They seem to be well made, have a decent feedpoint and are readily available in UK. However, I cannot find anybody who has put their experiences down on the internet. Any feedback good or bad greatly appreciated.
Thanks, Peter G4URT
g4urt(a)btinternet.com
I'm trying to 'reverse engineer' the VE1ALQ 16 bit boards. I can read the
contents of the little NV memory buttons, but I can't figure out how to
relate the contents to reality.
This is for the elevation encoder. The system stores only five bytes of
data. The first three bytes are the actual elevation. Four and five are
the calibration constant, which is always the same, once calibrated.
The encoder is a 2500ppr US Digital inclinometer. So it only travels
1/4th or 625 pulses from zero to 90 degrees. The count is 4 times 625 due
to the LS7084 Quadrature clock converter, so we are back to 2500 pulses
from 0 to 90. So the system stored C3 09 01 which somehow equates to 2500
pulses for 0-90 degrees. I cannot figure out any correlation here.
Also I downloaded data below for various positions and I see no
relationship other than the zero position.
Does anyone have a clue how this works? I can't 'break the code.'
Any help is appreciated.
Parked 0.0 degrees
----------------
Data:
<000> 00 00 C3 09 01
Parked at 0.1 degrees
---------------------
Data:
<000> 02 00 C3 09 01
Parked at 1.1 degrees
---------------------
Data:
<000> 1E 00 C3 09 01
Parked at 4.4 degrees
--------
Data:
<000> 79 00 C3 09 01
Parked at 45.5 degrees
--------
Data:
<000> F8 04 C3 09 01
Parked at 67.8 degrees
--------
Data:
<000> 5A 07 C3 09 01
73
Mike, KL6M BP51dc http://www.qsl.net/kl6m
Hi Community.
During a big gust with the storm this morning the welded joints on my
elevation rotor broke and array dropped on the roof.
Antennas, cables and elevation system heavily damaged. I don't expect to be
back soon.
It seems an always returning problem here on the coast. Have to make up my
mind. The array was new and left 6 months..
73 all. Peter PA2V
