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
I have no special contest plans other than I will be qrv in cw random calling cq on 2m-70cm-23cm. Hope gear at eme qth is ok. Emphasis will be on 144&432MHz so as to help increase cw activity on those 2 beloved bands. Pls note that I have bad qrn on 2m at moonset window even at high elevation, but will hang in there.
A tip: due to poor moon conditions and especially deep qsb minimums expected on 2m, when you hear qrz send your call a few more times for the period(s) needed, and be patient. QSO reward in this mode deserves the extra effort.
Want to wish GL to all participating stations and hope mixed and digital stations attempt to have fun in cw also. It is not about the numbers or dxcc's, it is about the moon journey...either spacecraft man guided or not, has its merits and joy.
73
Jimmy SV1BTR
2m: 16*6el xpol
70&23cm: 6.1m dishes
Anybody using a 144 mc LNA device called ALN0140WT ?
Specs look very interesting .. but are they for sale ???
73's Rick ,PA1BVM
--
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.
Hello moonbouncers,
There was very nice CW activity during ARRL contest this year (on all bands except 2m from US) and it is unfortunate I did not have a lot of free time for it.
I also “worked” JT65 logger eme (I thought: who is going to find out anyway??) and apart from constant chatter I also found JAMMING.... a lot of Jamming, even from its own creator!!?
Check a small part of it from N0UK logger:
11/19 17:04 VE3KH you being jammed by K1JT and W6YX (W7IUV Larry WA DN07dg 216.215.40.193)
11/19 17:05 Why Larry .... they on 142 also? (VE3KH Kevin ON FN03aj 24.141.203.45)
11/19 17:06 They are calling me to get a contest poitn and it ain't gonna happen!! (W7IUV Larry WA DN07dg 216.215.40.193)
11/19 17:08 Thansk Larry 73 ... Yes, I have been jumped by a quite a few stations (VE3KH Kevin ON FN03aj 24.141.203.45)
11/20 17:47 Also hr k1jt calling me -22 but not ans him (KN4SM/5WL/KW Jerry VA FM16qt 24.241.251.86)
11/20 18:02 Contest = reduced courtesy! (K5DOG/2M Stevedog NM DM52xw 65.127.140.122)
11/20 18:04 Yes, K1JT and W3SZ can hear on gold tooth. (K5DOG/2M Stevedog NM DM52xw 65.127.140.122)
One thing I wouldn’t regret missing on EME is JAMMING!!!
GL 73, Petros SV3AAF
I'm in!
Andy WA2FGK
At 10:06 AM 10/30/2013, David Kerl wrote:
>Mike,
>I am sorry to hear of your situation. You are one of the main eme
>stations for KL7. In ham spirit, in order to keep KL7 well
>represented on more than one band, via the moon, I think we should
>all kick in a small donation to the cause. Many small donations
>should make a major dent in the projects bill.
>
>What say, EME community?? Lets give Mike some help, and keep KL7 on
>the moon, on multiple bands.
>
>Mike, if you decide to rebuild, and I hope you do, please let the
>eme community know, so we can send you some "help".
>
>Dave Kerl
>N9HF
>el99jf
>_______________________________________________
>Moon-Net posting and subscription instructions are at
>http://www.nlsa.com/nets/moon-net-help.html
