CQ-Contest
[Top] [All Lists]

Fwd: YAESU IMD

Subject: Fwd: YAESU IMD
From: KY2P@aol.com (KY2P@aol.com)
Date: Thu Oct 17 20:41:00 1996
"Buy USA" ain't what sells the rig, pardner - we sell the best
damn receiver performance in the OMNI-VI you'll ever see.

We hear 'em when you won't.

73 Scott Robbins KY2P, Ten-Tec employee and
dedicated contester.
---------------------
Forwarded message:
From:   s56a@s55tcp.ampr.org (Marijan Miletic)
Sender: owner-cq-contest@tgv.com
Reply-to:       S56A@s55tcp.ampr.org
To:     cq-contest@tgv.com

Newer rigs (TS-870, IC-775, FT-1000MP) were thoroughly tested by ARRL, RSGB
and
DARC and all data show remarkable strong signal performance of new YAESU.
 K7JA
surprised me with a fact that relays are used for input RX filter switching
so
no problem with IMD2 & IMD3 at the most sensitive spot.  I am amazed that
after
all the nice figures available, people still make subjective claims regarding
FT1000D v FT1000MP versus rest of the rigs.  At least we got rid of "Buy USA"
propaganda :-)
73 de Mario, S56A, N1YU.
P.S.  Does anybody uses superb JST-245 in contests?


>From jreid@aloha.net (Jim Reid)  Fri Oct 18 00:45:18 1996
From: jreid@aloha.net (Jim Reid) (Jim Reid)
Subject: YAESU IMD
Message-ID: <1.5.4.32.19961017234518.006757fc@aloha.net>

At 06:34 PM 10/17/96 -0400, Tyler wrote:

>Someone complained about Yaesu service!  I couldnt believe that one.  I just
>sent my MP in with several minor complaints and upgrades and they turned it 
>around in 1 week!  I even talked to the technician twice during the process.
>This 2 weeks before CQWW phone...  yeah, that's TERRIBLE service!

If I recall correctly,  that one was from a country outside the US.

>Lastly, I'd suggest to anyone that is going to post summaries please
include the
>ID's of the people responding.

I was asked by a couple not to ID them.  Also,  I have been chastised
before on this reflector for copying to the reflector mail sent only
to me.  So,  I presume that any of them who responded to me
were/are still free to copy to or expand upon their responses/remarks
to the reflector just as you CC'd to the reflector your response to
Mario.  All my responses were from regular readers and contributors
to the contest reflector.

73,  Jim,  AH6NB



>From broz@csn.net (John Brosnahan)  Fri Oct 18 01:29:12 1996
From: broz@csn.net (John Brosnahan) (John Brosnahan)
Subject: Jupiter Noise trashes 15M
Message-ID: <199610180029.AA03452@ns-1.csn.net>


>>HUBBLE FOLLOWS RAPID CHANGES IN JUPITER'S AURORA
>>
>>       Hubble Space Telescope's sharp view of the rapid, 
>>spectacular dance of luminescent gasses high in Jupiter's 
>>atmosphere -- better known as aurora -- is allowing 
>>astronomers to map Jupiter's immense magnetic field and 
>>better understand how it generates such phenomena.
>
>
>How'dja like to run DX through one a-them puppies?  Kinda puts our
>troubles in perspective, don't it?


These currents generate signals that are easily copiable on earth and
may be a minor source of qrn during contests. (Got it in.)

When IO is at a point 90 degrees or 240 (yes 240, not 270)  from
a line from earth to Jupiter the noise is easiest to copy here.  The
Jupiter -- Io connection is like a dipole and we are broadside to that
current flow (OK a dipole without a balun--hence the somewhat skewed
90/240 relationship).  Probably easiest to detect the noise on 15M
when Io is in the right position and Jupiter is near the horizon.  20M is 
usually too noisy and 10M is too high much of the time.  The noise 
sounds like the surf--waves that build up and die back down, over 
periods from a second to tens of seconds, typically.  Need
a dead band to hear it--but I have heard it on 15M when tuning for
dead band Africans in the middle of the night at K0RF's place
years ago.

No I don't have the program to calculate when Io is in the right
position--someday I'll worry about considering Jupiter noise to
whether I want to do a single 15M contest again.

73  John

John Brosnahan  W0UN
24115 WCR 40
La Salle, CO 80645

"Radio Contesting IS a Contact Sport"


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