Yaesu
[Top] [All Lists]

[Yaesu] FT990: CAT Data Structure Info

To: <yaesu@contesting.com>
Subject: [Yaesu] FT990: CAT Data Structure Info
From: wulf@ping.net.au (wulf@ping.net.au)
Date: Sun, 27 Oct 2002 15:22:25 +1030 (CST)
Mike,

thanks for the quick reply and info. I workd around this and got a little
further. 

There is yet another problem that I came across that is bugging me.
It appears that sending the M>VFO command doesn't work

e.g. 0x06 0x02 0x00 0x00 0x00

This should copy the data from channel 3 into the last used vfo. All it does
on my rig is to switch back to the last used vfo when in memory mode or
nothing when in vfo mode.

The memory operations via CAT seems to be somewhat flawed. VFO>M and
VFO/M commands don't exhibit the expected functionality.

Can someone verify this?

Many thanks in advance,

73 Berndt
VK5ABN


> 
> Berndt,
> My FT990 with v1.3 firmware returns the values you are seeing. 2.4kHz
> returrns 4, 6kHz returns a zero.
> 73, Mike NF4L
> ----- Original Message -----
> From: <wulf@ping.net.au>
> To: <yaesu@contesting.com>
> Sent: Saturday, October 26, 2002 9:04 AM
> Subject: [Yaesu] FT990: CAT Data Structure Info
> 
> 
> > G'day,
> >
> > I've a problem understanding the value that is returned in the
> > 16-byte Update Data structure when in AM mode (6khz/2.4Khz bandwidth)
> > as described in the FT990 users manual on page 42.
> >
> > The document describes the byte at offset 8 (filter) as followed:
> >
> > Filter Selection
> > Value| IF-Filter
> > ----------------
> >  0   | 2.4Khz
> >  1   | 2.0Khz
> >  2   | 500Hz
> >  3   | 250Hz
> >  4   | 6Khz (AM)     <------ ??????
> >
> > bit 7 of this byte is set for FM Packet or Reverse RTTY.
> >
> > According to the above, a value of 4 is returned whenever the transceiver
> > is in AM mode with a bandwith of 6Khz (no filter selected). The returned
> > packets that I receive back from my transceiver show the contrary. When in
> > AM mode, it returns a value of 0 for 6khz and a value of 4 for 2.4khz
> > bandwidth.
> >
> > Has anyone seen this and can confirm my observations? Is this a bug
> > in Yaesu's firmware or perhaps a misprint in the manual?
> >
> > Many thanks in advance,
> >
> > 73 Berndt,
> > VK5ABN
> >
> > _______________________________________________
> > Yaesu mailing list
> > Yaesu@contesting.com
> > http://lists.contesting.com/mailman/listinfo/yaesu
> >
> >
> 
> 
> _______________________________________________
> Yaesu mailing list
> Yaesu@contesting.com
> http://lists.contesting.com/mailman/listinfo/yaesu
> 


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