[Yaesu] Yaesu Service Time interval: 7wks.

[Chris Victor]

Dear Fellow Yaesu Users-

>From the FWIW arena,

I just received my FT-1000 back from Yaesu tech support, having submitted it on
March 1, 1999.
They upgraded the eprom rev. level [to work with CT contest software] and did
the PIN diode mod.
They also replaced some lithium batterys, and did a health and welfare tuneup
of the entire radio.

So for those of you who have their radio's in for repair, I guess now the wait
time is 7 weeks.

Now, I have to lift this 65lb monster back into the operating position, not a
easy task!!!

73's to all and Gud DX!

de Chris K6SUY
Work: http://www.dbc.com


Yaesu Digest wrote:

> Yaesu Digest          Friday, April 23 1999          Volume 02 : Number 070
>
> In this issue:
>
>     [Yaesu] FT990 serial interface weirdness
>
> See the end of the digest for information about yaesu-digest
>
> ----------------------------------------------------------------------
>
> Date: Fri, 23 Apr 1999 08:51:26 -0400
> From: "Brian Smithson" <brian_smithson@vds.com>
> Subject: [Yaesu] FT990 serial interface weirdness
>
> Greetings!
>
> I'm having problems with serial comms to my FT990.
>
> What I'm doing is trying to interface with my 990
> from Microsoft Access using the MSComm serial control.
> I've got it about 98% working, but one last thing is
> driving me crazy and I was wondering if anyone would
> have a minute to help me out.
>
> It has to do with reading the rig's frequency. I'm
> grabbing both VFO's and most of the time everything
> works great. There seems to be a region of frequencies
> in the 20m CW band that don't read right - when the
> radio says 14.121.00 the reading I get from the serial
> port is 13.972.52! This continues for a short range
> and then the readings are OK - 14.126.00 reads fine,
> and then 14.127.00 reads as 14.083.48.
>
> I've examined the bit streams as best I can and it looks
> like the radio is sending 158C04 hex for both 14.121.00
> and 13.972.52! I tried the same frequencies in a
> commercial logging program with rig interfacing features
> (LOGic 5 - a great program) and they displayed
> correctly. I have no way to 'sniff' the bits LOGic is
> reading to tell if they are different.
>
> At first I suspected the MSComm control itself, but
> the error is so localized - I haven't been able to
> make it happen any where else - only the low-end of
> the 20m band!
>
> Has anyone seen anything like this? Is some sort of
> correction required? Any ideas at all?
>
> Thanks so much!
>
> 73, Brian n8wrl
>
> ------------------------------
>
> End of Yaesu Digest V2 #70
> **************************
>
> --
> FAQ on WWW:               http://www.primenet.com/~ke7gh/yaesu.html
> Submissions:              yaesu@contesting.com
> Administrative requests:  yaesu-digest-REQUEST@contesting.com
> Problems:                 owner-yaesu-digest@contesting.com


--
FAQ on WWW:               http://www.qsl.net/k7on/yaesu.html
Submissions:              yaesu@contesting.com
Administrative requests:  yaesu-REQUEST@contesting.com
Problems:                 owner-yaesu@contesting.com
Search:                   http://www.contesting.com/km9p/search.htm