Print

[KD1I]

I have used VARA - licensed version - with my Flex 6500 for some time now with little problems. Works quite well. However, I just set up a station with my FT 897 and have an unusual issue. If I set the frequency via memory in the radio, the offset is correct, 1.5 KHZ. But if I click on a station - in this case AB4NX - in channel selection, the offset is one KHZ low.
Here are my conditions:   VARA HF V 4.6.9      Winlink Exp  1.7.2.0    These are the latest SW revisions of each.
AB4NX dial 3587.000   Ch center 3588.500     This is correct if I set it via radio memory.
AB4NX dial 3587.000   Ch center-3587.000    This is wrong when set by "channel select" in Winlink and, of course, it does not connect.
Any thoughts on where this error is being generated?    It is a big advantage to using channel selections in Winlink rather than manually setting in the radio.
Many Thanks, Jim     KD1I

[G4AON]

Jim, I have just checked my Winlink Express with channel selection and it shows AB4NX as CF 3588.5 and dial as 3587. My radio (Elecraft K4D) sets to 3587.

Is the program displaying the wrong channel information, or is the program setting the radio to the wrong frequency? Sounds like you may need to update your channel selection.

73 Dave

[KD1I]

Thanks for the reply, Dave.   The display is always correct.  Only the actual offset is incorrect. I do update the channel selection frequently when the message "solar flux has changed" pops up which is every day.  I have tried other gateways as well, K4FEM, for example.  It only malfunctions when Winlink channel selection sets the frequency. If the radio memory sets the frequency it works fine.     Jim

[KD1I]

I spent some quality hours working on this today but it was a learning experience so not a complete waste.
I had not configured ARDOP on the little laptop for the FT897 previously so that was the first challenge of the day but now
 that is working.
ARDOP works fine on both the Flex and the FT897... no problems with two gateways, K4FEM and AB4NX... no weird offset.
VARA works fine on the Flex when selecting a gateway from Winlink....  no weird offset either.
VARA does have an incorrect offset on the FT897 when selecting a channel from Winlink and this is true for both of the gateways I tried.
It seems the issue is unique to the combination of FT897 and VARA and selecting the gateway in Winlink.
I would have thought that offset was "hardcoded" into Winlink and not unique to the radio.  Guess it is not that simple.

In all cases, I updated the channel selections via the web just to be sure it is current information.

So far this is all on 80 Meters.   I will try 40 or other bands tonight.

[KD1I]

So I tried 40 meters and the results were the same.... wrong offset when the frequency is selected via Winlink.   Next, I tried another computer. The latest VARA and Winlink were downloaded to another small laptop and configured. It worked as before. If the frequency is set from the radio's memory, the offset is correct and communication is possible.  If set via Winlink using "channel selection" it is incorrect and naturally, there is no communication possible.   Has anyone else experienced this?   I have never observed this before.   

[WA8NVW]

If you can determine the erroneous frequency offset value, that should give you a clue where to look in the Winlink radio definition to correct the channel programming.  Some possibilities include setting AFSK mode on the rig which is always sent in LSB, having VFO A set to a different frequency than VFO B, having the audio filter response set to other than flat audio on both Xmt and Rcv, RIT or XIT engaged by default on the FT897, using some digital modes software package that assumes 1 kHz offset, etc.

[KD1I]

Thanks for the reply. The rig is set for USB or DIGU which is normal for digital modes. It is not set for AFSK.  The incorrect tones are approximately 1 KHZ lower than they should be. There is only one VFO on this FT897.
I will check again for the audio response but it does work fine if the frequency is set via radio memory rather than via Winlink. That should indicate the audio response is OK. Also, ARDOP works well under the same conditions.... no erroneous offset. Best 73, Jim