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 ...
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.
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
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:
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:
TX: 1296.070 -1.5KHz = 1296.0685MHz
RX: 1296.070 +1.5KHz= 1296.0715MHz
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
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 ½
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.
As my 23cm project is underway, I no longer need the 2m EME stuff I used when I was QRV back in 2012. I don't have any plans to return to 2m EME anytime soon as I don't have the room at my house for long yagis.
With that, I have decided to sell my 2m?EME components to make some room.
Here is what I have for sale:
W6PO design 8877 2m RF deck w/8877 tube, homebrew (not by me), $1000 OBO - Pics available upon request. This works nicely, I used it in 2012 for all of my JT65 & CW EME QSO's. Rack & Power supply is NOT for sale (power supply & rack?is?not mine to sell, owner not interested in selling)
DEMI L144LNACK-2N GaAs pHEMT pre amp., 17dBG, <0.5DBNF, RX only!, $40 - I built this as a kit
YU7EF design 9 el yagis (built by me) - quantity of 4, these break down each into 3 sections, with LMR-400 phasing cables (n connectors). All are lightweight contruction. $250 OBO for all four - pickup only
M2 4 port power divider for 2m (n connectors)?- $100
I will sell the yagis and M2 4 port divider together for $300.
The yagis are the only thing I won't ship. I would prefer local pickup on the amp to ensure it's safety but I'll ship (I drove to Virginia to pick it up!)
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
"Kits made by KL7UW"
Dubus Mag business:
I can be QRV on 24 GHz the weekend of October 24/25. The weekend of October
17/18 is the annual Microwave Update conference in California.
From: Willi Bauer [mailto:firstname.lastname@example.org]
Sent: Wednesday, July 22, 2015 5:55 AM
To: 'Barry Malowanchuk'; 'Al Ward'; 'Charlie & Geraldine Kahwagi'; 'Manfred
Ploetz'; vladimir.masek(a)volny.cz; 'Paul Chominski'; 'Andre F1PYR'
Cc: 'peter blair'; 'Brian Coleman'; 'Charlie & Geraldine Kahwagi';
Hi to the 24GHz EME gang.
Please find here the collection answers for the proposed activity
weekend on 24GHz:
Barry VE4MA: . It is so humid here right now...something W5LUA has for a
so suggest something in September/ October?
I like OCT 24/25, NOV 21/22 for 24G AW.
3 days ago i had a long phone call with Johannes df1oi. He is not qrv 24GHz
this moment because hi is busy on 10ghz. (But maybe for October ?)
My 24 GHz station is rebuild and ready for contact. Only problem on my side
is bad, bad cw knowledge.
24GHz AW I propose to choose a week end without any contest activity such as
IARU VHF in September
UHF/SHF in October Marconi in November.
At ORPB society we plan to use PB8 13m dish on 24GHz probably in October.
1. and 2. WE in September I can't be QRV, but 3. WE and 4. WE in October
seems to be optimal
for the season, and I can be QRV.
For me the last 2 weeks in September, the weeks in October is also November
is possible but the WX
in November is normally not so fine.
So in conclusion we could make a choice for October. Just open the date. Any
proposal will be appreciated.
There is the proposal from Yoshiro oct.24/25, any other...that we can put a
Besides the replies here, I have also received a few direct. For the benefit of the group, I will post additional information.
First, as we know, Windows 10 won’t be officially available until next week. I am running one of the last public betas (Fast Insider builds). Based on the lack of even a Windows 8/8.1 driver from M-Audio, and the age of the card, it is unlikely to be officially supported.
I did an upgrade from Windows 7/64 bit, where it was working fine. Once I upgraded to Win 10, the Delta-44 no longer appeared as a sound card. Yet, it was detected in Device Manager (I forget exactly how it was listed, perhaps as an Unknown Device). I then ran the last software program/driver from M-Audio (version 6.0.8, 03-15-2012), and while the program seemed to install correctly, the card was still not found. That was the extent of my testing.
Today I received a reply from Udo, DK5YA and he is running Win 10 with both a Delta-44 and Delta-66 with no issues! Perhaps as others install Win 10, they will post their experiences about this, here.
73 de Sebastian, W4AS
Hi all again!...... Just as I finished sending my last email to this
group, I received an email indicating that the WIA has suggested a VK
EME segment in the 9cm band as 3398.000 to 3398.100. How does
this effect everyone?
Can your Rx' tune down 2 MHz OK?............... Please let me know
as these suggestions are "fluid" and in their infancy.
I may ask the WIA to suggest an EME or Narrow Band segment from
3398.000 - 3400.000 ???
Ø Even ISS uses 390 for APRS messaging.
It should not be doing so - certainly not when it is visible anywhere in
IARU Region 1.
If it was a Chinese system causing interference in the EME part of the band
I am sure everybody in the US would be up in arms. But I guess this is the
sort of disregard for international agreements that we often see from a few
US amateurs that seriously dents your reputation in the rest of the world.
If any amateur in IARU Region 1 (Europe/Africa) hears APRS transmissions
from ISS on 144.390Mhz please drop me an email, preferably with an AFSK
decode and I will endeavour to use international pressure to stop ALL such
Subject: Re: [Moon-Net] Rogue Satellite causing interference across
Content-Type: text/plain; charset="windows-1252"
Specifically, 390 is the standard, published APRS frequency for NA. All the
iGates, repeater, and thousands of APRS beacons are on this frequency.
What is the standard for APRS in EU? Seems many of the SOTA folks use
APRS all over the world. Just curious.
Even ISS uses 390 for APRS messaging.