[Yaesu] ft990 comm problem

Jose (Chegüi) Torres kp3g@isla.net
Thu, 24 Jan 2002 06:52:41 -0400


This is a multi-part message in MIME format.

------=_NextPart_000_02DD_01C1A4A3.B7A73E20
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sent this to the Yaesu Technical Support several time as you can see =
below but never got a reply.

So would like to share my problem in case someone has a suggestion.

73 de KP3G


----- Original Message -----=20
From: Jose (Cheg=FCi) Torres=20
To: amateurtech@vxstdusa.com=20
Sent: Wednesday, January 23, 2002 6:58 AM
Subject: Fw: ft990 comm problem


Please!!!!
Need your expert advice.

73 de KP3G

----- Original Message -----=20
From: Jose (Cheg=FCi) Torres=20
To: amateurtech@vxstdusa.com=20
Sent: Sunday, January 20, 2002 9:19 AM
Subject: Fw: ft990 comm problem


Just in case you didn't get it...

73 de KP3G

----- Original Message -----=20
From: Jose (Cheg=FCi) Torres=20
To: amateurtech@vxstdusa.com=20
Sent: Sunday, January 13, 2002 8:22 AM


Hi!

I have a FT990 that is refusing to communicate to my PC. I tried two PC, =
two logging programs that use to work, replaced cables, etc, without =
luck.

The problem began to show up slowly but now it is steady.

I have checked the sig with my Tek scope and this is what I have seen:

When an update command is sent to the radio, the CAT indicator comes on =
and there is a signal coming out on SO. Traced the sig all the way to =
the comm. port of my PC and the sig is there with the correct levels but =
nothing happens.

If I do a Set OP Freq command, the radio will respond to it without any =
problem.

I did a update command asking for 1508 bytes (U=3D0) to have time to =
sync on something. The only thing I think is kind of strange is that the =
shortest info element is less that 2.2ms which is the shortest time for =
a baud of 4800.

Ran out of bullets...

Could it be a problem with Q5004 MCU oscillator?

73 de KP3G

------=_NextPart_000_02DD_01C1A4A3.B7A73E20
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Sent this to the Yaesu Technical =
Support several=20
time as you can see below but never got a reply.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>So would like to share my problem in =
case someone=20
has a suggestion.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>73 de KP3G</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dkp3g@isla.net href=3D"mailto:kp3g@isla.net">Jose (Cheg=FCi) =
Torres</A> </DIV>
<DIV><B>To:</B> <A title=3Damateurtech@vxstdusa.com=20
href=3D"mailto:amateurtech@vxstdusa.com">amateurtech@vxstdusa.com</A> =
</DIV>
<DIV><B>Sent:</B> Wednesday, January 23, 2002 6:58 AM</DIV>
<DIV><B>Subject:</B> Fw: ft990 comm problem</DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><BR></DIV>
<DIV><FONT face=3DArial size=3D2>Please!!!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Need your expert advice.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>73 de KP3G</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dkp3g@isla.net href=3D"mailto:kp3g@isla.net">Jose (Cheg=FCi) =
Torres</A> </DIV>
<DIV><B>To:</B> <A title=3Damateurtech@vxstdusa.com=20
href=3D"mailto:amateurtech@vxstdusa.com">amateurtech@vxstdusa.com</A> =
</DIV>
<DIV><B>Sent:</B> Sunday, January 20, 2002 9:19 AM</DIV>
<DIV><B>Subject:</B> Fw: ft990 comm problem</DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><BR></DIV>
<DIV><FONT face=3DArial size=3D2>Just in case you didn't get =
it...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>73 de KP3G</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dkp3g@isla.net href=3D"mailto:kp3g@isla.net">Jose (Cheg=FCi) =
Torres</A> </DIV>
<DIV><B>To:</B> <A title=3Damateurtech@vxstdusa.com=20
href=3D"mailto:amateurtech@vxstdusa.com">amateurtech@vxstdusa.com</A> =
</DIV>
<DIV><B>Sent:</B> Sunday, January 13, 2002 8:22 AM</DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><BR></DIV>
<DIV><FONT face=3DArial size=3D2>Hi!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have a FT990 that is refusing to =
communicate to=20
my PC. I tried two PC, two logging programs that use to work, replaced =
cables,=20
etc, without luck.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The problem began to show up slowly but =
now it is=20
steady.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have checked the sig with my Tek =
scope and this=20
is what I have seen:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>When an update command is sent to the =
radio, the=20
CAT indicator comes on and there is a signal coming out on SO. Traced =
the sig=20
all the way to the comm. port of my PC and the sig is there with the =
correct=20
levels but nothing happens.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>If I do a Set OP Freq command, the =
radio will=20
respond to it without any problem.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I did a update command asking =
for&nbsp;1508 bytes=20
(U=3D0) to have time to sync on something. The only thing I think is =
kind of=20
strange is that the shortest info element is less that 2.2ms which is =
the=20
shortest time for a baud of 4800.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ran out of bullets...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Could it be a problem with Q5004 MCU=20
oscillator?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>73 de =
KP3G</FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_02DD_01C1A4A3.B7A73E20--