Hi Ervin, hi Nate,
I think you both have your points
RIG_PASSBAND_NORMAL is defined as a special coded width value. Every
rig should interpret that value as 'use the defined _normal_ bandwidth
for that mode. As it seems that there are backends which misses these
behavior I think the problem
Hello Thomas, hello Nate,
a few days ago I sent a patch to Nate (through this list) for
hamlib, to fix this bug in case of Kenwood rigs. May be he will
merge...
But I think the original problem will not solved with this,
namely I would like to keep untouched my filter state, when I
switch
Am Sun, 5 Jan 2014 14:09:21 +0100
schrieb Ervin Hegedüs - HA2OS airw...@gmail.com:
Hello Thomas, hello Nate,
a few days ago I sent a patch to Nate (through this list) for
hamlib, to fix this bug in case of Kenwood rigs. May be he will
merge...
But I think the original problem will not
Hello Thomas,
On Sun, Jan 05, 2014 at 02:21:56PM +0100, Thomas Beierlein wrote:
Am Sun, 5 Jan 2014 14:09:21 +0100
schrieb Ervin Hegedüs - HA2OS airw...@gmail.com:
Hello Thomas, hello Nate,
a few days ago I sent a patch to Nate (through this list) for
hamlib, to fix this bug in case
* On 2014 02 Jan 12:34 -0600, Hegedüs Ervin wrote:
If that function got 0 as 'width', then that set the filter the
lower value... :(
That mean the using of RIG_PASSBAND_NORMAL is not that what the
author wanted.
I don't know, what should be the solution.
At first glance, I will say the
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
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
* 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
Hi Ervin,
Am Mon, 30 Dec 2013 11:40:02 +0100
schrieb Ervin Hegedüs - HA2OS airw...@gmail.com:
Note, these are just proposals, may be these aren't bugs.
* point calculating
At last weekend I made the RAC. On RAC all VE/VA station worth
10 points, any other does 2 points. My config was:
On 12/30/2013 01:42 PM, Thomas Beierlein wrote:
Hi Ervin,
Am Mon, 30 Dec 2013 11:40:02 +0100
schrieb Ervin Hegedüs - HA2OS airw...@gmail.com:
Note, these are just proposals, may be these aren't bugs.
* point calculating
At last weekend I made the RAC. On RAC all VE/VA station worth
10
10 matches
Mail list logo
