On 12/31/2013 04:18 AM, Ervin Hegedüs - HA2OS wrote:
Ed,
could you try this with your rig?
* remove/uncomment the SHOW_FREQUENCY option in logcfg.dat, if
exists
* set up your rig model
* start TLF
* then Tlf show the frequency of your RIG at middle-right side,
eg: TRX: 14004.5
* switch
Hello Thomas,
On Tue, Dec 31, 2013 at 12:53:17PM +0100, Thomas Beierlein wrote:
Hi Ervin,
let us keep the scoring aside for a minute and look for the rig problem
first
ok, no problem,
Therefore I asked you (Tlf users), please check this on other
rigs. May be it's a hamlib bug, but
Hi Ed,
On Tue, Dec 31, 2013 at 07:24:29AM -0500, Ed wrote:
On 12/31/2013 04:18 AM, Ervin Hegedüs - HA2OS wrote:
Does Tlf follow it? Does it show the new frequency with another
VFO, than was active when Tlf had started?
Tlf does not see or follow VFO B, only A. It sees and follows B if I
Hi Ed,
Am Mon, 30 Dec 2013 17:07:14 -0500
schrieb Ed au...@comcast.net:
There are too many LF's on TX. Send the macro, 4 LF's before the next
macro. You will scroll off most RTTY screens. fldigi sends 1 before
and 1 after, by default and is perfect.
did you use the old tlf-1.1.x version?
* On 2013 31 Dec 06:07 -0600, Thomas Beierlein wrote:
The single rig backends are normally implemented by different OMs. So
we have a situation where different rigs show different behaviour quite
often.
One of the things I would like to see addressed in Hamlib is this
difference between
