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.
I’m ready on 6cm with the same dish I’m using on 3cm.
Despite the strong local 5 GHz WiFi noise, had a nice 579/569 first QSO with this setup today with HB9Q, thank you Dan !
Setup is a 3.7m dish and 60W at CP feeder.
I can be QRV on 6cm or 3cm most of the days, skeds and tests are very welcome, as usual.
qrv 70cm, 33cm, 23cm, 13cm, 9cm, 6cm and 3cm.
Murphy paid a visit at last moonrise, in form of wind, clouds andfinaly a
I could not see any traces on the waterfall, but at first I blamed the
windy conditions that made tracking difficult, the dish was very shaky, and
I coudn't see the moon, so no aiming reference at all. After the moon came
out of the clouds I could finally verify the pointing, and it was fairly
good, so I started to look at the rest. Found the LNA not working properly,
but replace it in the dark with wind gusts peaking at 30+ knots was quite
After the change everything was back to normal and I've completed several
The first stage of the LNA is indeed dead. No clues about the cause since
everything is well sequenced. Maybe static charge by the wind?
I will be back with JT65 at moonrise but give some time to CW requests too.
Let's hope that Mr. Murphy stays clear, no more spare LNAs.
Best 73. Giulio
Anyone on the list have a Lunar Link LA-12 or Henry 3002-220 (220 MHz amps)
that they are not using that they might be interested in selling. I will
consider Lunar kits (early stuff) or units with problems as well. Please
drop me an email direct to iam4thapack (at) gmail (dot) com if you have
something I might be interested in.
Well I believe I have solved my network problem.
I use the IQ+ driving the Delta44 sound card on an XP computer.
For some time now I have used Map65 v2.7 on the XP and it has worked well.
Map65 v3.0 does not support Windows XP so I must use Linrad on the XP
and send timf2 networking to the new Ryzen5 Windows 10 PC with Map65 v3.0
on it. This initially seemed to work using a wireless network connection.
The XP has
a USB wireless wifi on it. Pings are usually about 5ms but can be as much
as 35ms. At times,
perhaps when others are streaming videos I would see dashed lines on the
Overall I had inconsistent results. Sometimes it was as sensitive as my
Yaesu feeding WSJTx
and other times not. This prompted me to try a wired network. I used a
direct connection but
did not multicast from Linrad. This sometimes worked well, but not very
often. The pings were
1ms all the time and there was no other traffic on the network. I consulted
with a CCIE as well
as SM5BSZ. I first cleared up an IRQ conflict but I don't know if that
helped or not. It can be seen on the task manager. I reasoned that if the
wireless USB network worked better than the wired network that perhaps a
USB wired network adapter might be better. I started watching a strong
carrier being sent into the IQ+ on 144.130 Mhz. I was able to spot trouble
using Linrad on the XP computer but only when sending to the wired network.
The trouble showed up as
a wide signal that looked like noise perhaps overmodulated so it was about
10Khz wide. It looked clean when I stopped sending to the network from
Linrad. This condition also caused poor performance on the Map65 v2.7 on
the XP. I switched over to the USB network adapter and cleaned up much of
the problem. It was only intermittent then perhaps every 30 seconds. I had
discovered that I was not using quite the right Delta44 driver. I'm using
the 1057 version
which is just a bit newer than the recommended 1047 version. I found
someone that had the 1047 driver and installed it. This cleaned up the
signal completely. I then tried returning to the built-in wired network
adapter and the problem was again very bad so I went back to the USB
network adapter. I did not try reintroducing the IRQ conflict. By the way,
the task manager never did report an IRQ conflict but when I looked down
the list of IRQ they were clear. Each PCI slot
has an IRQ that it assigns to the Delta44. Each of these IRQ's is shared
with something else.
One slot shared IRQ's with the fire wire which I knew I was not using so I
disabled it clearing up
the shared IRQ. I would recommend that if you are using a network for RX
data that you observe a strong clean signal and make sure it is received as
a strong pure carrier by the Map65 waterfall. This is a potential reason
for some of the reported poor results with Map65. So how does it work? I
operated this morning on both JT65b and Q65-60a and found that generally
sensitivity was within a db of each other when comparing Map65 to WSJTx.
There are still a few quirks. Map65 v3.0 rc5 nearly always reports
shorthand db numbers on JT65b that are 3 db higher on Map65 vs WSJTx. This
does NOT translate to greater sensitivity. I would like this fixed as it
tends to introduce signal reporting errors. When I was calling CQ
on JT65b there were two times that a caller came in only on WSJTx (at
-27db) but not on Map65. Both were set up the same. I need more time with
this to tell if this is a real issue or not but it is suspect. The network
problem was a difficult one. I hope my experience here helps someone else.
Perhaps you have a network problem and don't realize it. At least for now,
there is value in running WSJTx in addition to MAP65. I wish WSJTx could
select the right and left channel of the sound card independently. What I
might do then is to use two radios and feed horizontal polarization to one
instance of WSJTx and vertical polarization to another instance of WSJTx.
This would of course NOT replace Map65 but only supplement it.
Earl Shaffer, WB9UWA
My EME array photos
Detailed array photos
Plisch TV-linear-Amp ULE 1021A 470MHz-860MHZ minor modifications for
for 24/7 on 432 MHz can be liquid or air cooled liquid cooling-
The unit: PA+PS+cooling-aggregat and/or heat sink for air cooling €
For PICK-UP ONLY at my qth in JO30KI.
73 Gerd, DJ5BV