--------------8D88731858B9FD2322E9868A
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
John:
Thanks---but I guess that, as carefully as I tried to word my question, I was
not clear enough. I am indeed using "Rig on COMM1"---were I not, I would be in
full manual mode. Although the rig and WriteLog are talking to each other, the
communication seems incomplete and far from each seamlessly tracking the other.
That is, WriteLog ignores the radio until a frequency has been selected in that
frequency selection window and sent to the radio. Then, it does not appear to
allow the listed frequency selections to be permanently modified (e.g. to 14040
instead of 14000), requiring instead that the desired QSY frequency be typed in
each time. Once the QSY is accomplished, WL polls and tracks the A VFO
frequency.
I asked:
* Is it possible to control the default frequencies in the frequency select
window?
* Is it possible to set the radio to a new band from its memories, and have
Writelog immediately track it?
This brings up a corollary question:
* Can WriteLog respond to either MP VFO? I observe only a response to the A
VFO, even if the B VFO is selected for transmitting. (My guess is that this is
allowable in the MP hardware, but is a shortcoming in Yaesu's CAT interface.)
This is a rational question, because it would be useful to use both VFO's on
the same band as a "poor man's" SO2R. If WL won't follow the B VFO, and a QSO
is made with the B VFO, the logged frequency associated with the QSO will be
wrong, and it will appear in the log as a QSY violation (not moving the
required 1 or 5 kHz). This in turn necessitates an extra motion to swap VFO's,
to complete the QSO on the A VFO. More work for Mother.
Garry
WA9ALS - John wrote:
> > I am not observing fully bidirectional frequency control, as I
> > understand it to be.
> >
> > I have an FT1000MP controlled through COM1. According to the quote
> > above, the frequency displayed in the QSO window should be slaved to the
> > MP's VFO---presumably including immediately after a band change. At the
> > moment, it is slaved and updates with each poll....but only if and after
> > I follow the following procedure:
>
> Click on the button to the left of the ENTRY window - the one that displays
> the frequency and mode. The at the bottom of the window that opens, you'll
> see "Logf the frequency of QSOs, and it will probably say "Manual Entry" in
> the window. However, if you have your rig setup in Setup|Ports earlier,
> that window will be a drop down box with at least one other choice besides
> "manual entry" - There should be a choice like "Rig on COMM1". You choose
> that, and from then on your freq/band/mode should display on the button and
> get logged correctly. And update with each poll. 73
--
160 meters-not a band but an obsession
--------------8D88731858B9FD2322E9868A
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
John:
<p>Thanks---but I guess that, as carefully as I tried to word my question,
I was not clear enough. <i>I am indeed using "Rig on COMM1"---were I not,
I would be in full manual mode</i>. Although the rig and WriteLog <i>are</i>
talking to each other, the communication seems incomplete and far from
each seamlessly tracking the other. That is, WriteLog ignores the radio
until a frequency has been selected in that frequency selection window
and sent to the radio. Then, it does not appear to allow the listed frequency
selections to be permanently modified (e.g. to 14040 instead of 14000),
requiring instead that the desired QSY frequency be typed in each time.
Once the QSY is accomplished, WL polls and tracks the A VFO frequency.
<p>I asked:
<p><i>* Is it possible to control the default frequencies in the frequency
select window?</i><i></i>
<p><i>* Is it possible to set the radio to a new band from its memories,
and have Writelog immediately track it?</i>
<p>This brings up a corollary question:
<p>* Can WriteLog respond to <i>either</i> MP VFO? I observe only a response
to the A VFO, even if the B VFO is selected for transmitting. (My guess
is that this is allowable in the MP hardware, but is a shortcoming in Yaesu's
CAT interface.) This is a rational question, because it would be useful
to use both VFO's on the same band as a "poor man's" SO2R. If WL won't
follow the B VFO, and a QSO is made with the B VFO, the logged frequency
associated with the QSO will be wrong, and it will appear in the log as
a QSY violation (not moving the required 1 or 5 kHz). This in turn necessitates
an extra motion to swap VFO's, to complete the QSO on the A VFO. More work
for Mother.
<p>Garry
<p>WA9ALS - John wrote:
<blockquote TYPE=CITE>> I am not observing fully bidirectional frequency
control, as I
<br>> understand it to be.
<br>>
<br>> I have an FT1000MP controlled through COM1. According to the quote
<br>> above, the frequency displayed in the QSO window should be slaved
to the
<br>> MP's VFO---presumably including immediately after a band change.
At the
<br>> moment, it is slaved and updates with each poll....but only if and
after
<br>> I follow the following procedure:
<p>Click on the button to the left of the ENTRY window - the one that displays
<br>the frequency and mode. The at the bottom of the window that
opens, you'll
<br>see "Logf the frequency of QSOs, and it will probably say "Manual Entry"
in
<br>the window. However, if you have your rig setup in Setup|Ports
earlier,
<br>that window will be a drop down box with at least one other choice
besides
<br>"manual entry" - There should be a choice like "Rig on COMM1".
You choose
<br>that, and from then on your freq/band/mode should display on the button
and
<br>get logged correctly. And update with each poll. 73</blockquote>
<p>--
<br>160 meters-not a band but an obsession
<br> </html>
--------------8D88731858B9FD2322E9868A--
|