Hello all,
Zilinas (LY2SS) helped to catch a bug with new Tlf version, which
Thomas released at last week. The bug affects some RIGs, which
doean't support the rig_get_vfo() CAT function. This occures in
new version, because we modified the Tlf to handle the RIG VFO's
correctly.
Now the WARC supp
On 02/03/14 11:11, Ervin Hegedüs wrote:
hope we can fix that correctly, 73, Ervin HA2OS
nope
make uninstall - uninstalled old version
Got source from https://github.com/airween/tlf/archive/warc.zip
Extracted. Then:
autoreconf --install
configure --enable-hamlib
make
make install
The sam
Hello,
On Sun, Mar 02, 2014 at 09:49:13AM +0100, Ervin Hegedüs wrote:
>
> Now I fixed this problem, so if in case of any RIG, if that
> doesn't support the rig_get_vfo(), and hamlib gives not RIG_OK,
> but RIG_ENIMPL ("function not implemented, but will be") or
> RIG_ENAVAIL ("function not availa
Hello Zilvinas,
On Sun, Mar 02, 2014 at 10:30:56AM +0200, Zilvinas, AUGMA wrote:
>
> Good morning Ervin,
>
> I use latest stable hamlib 12.15.3 from sf
I think you doesn't - but it doesn't matter. In my version
(hamlib 3.0) is same the code...
> My rig capability dump:
> rigctl -m 122 -u | gre
Good morning Ervin,
I use latest stable hamlib 12.15.3 from sf
My rig capability dump:
rigctl -m 122 -u | grep VFO (I wonder what the result of this command
would show the version you use)
Has targetable VFO: N
VFO list: VFOA VFOB
VFO Ops: TOGGLE
Can set VFO:N
Can get VFO:N
Can set S
Hello Zilvinas,
On Sat, Mar 01, 2014 at 11:41:16PM +0200, Zilvinas, AUGMA wrote:
> And yes - rigctld and m=2 isn' related
>
> rigctl -r /dev/ttyUSB0 -m 122 -s 9600 -v
>
> ft857:ft857_open called
> Opened rig model 122, 'FT-857'
> Backend version: 0.4, Status: Beta
>
> Rig command: v
> get_v
Hello Zilvinas,
On Sat, Mar 01, 2014 at 11:38:52PM +0200, Zilvinas, AUGMA wrote:
> 1.2.0
>
> Here's rigctld -v after running tlf -v -d (otherwise I can't
> force tlf to use hamlib)
> After setting 140 (tlf diagnostic?)
yes, now I just checked the code, and if you start Tlf with "-d",
t
Ed,
On your request
rigctl -r /dev/ttyUSB0 -m 122 -s 9600 -v
First time
Rig command: f
ft857: cache invalid
write_block(): TX 5 bytes
00 00 00 00 03 .
read_block(): RX 5 bytes
00 70 16 24 82 .p.$.
write_block(): TX 5 bytes
00 78 00 00 bb .x...
read_block(): RX 2
And yes - rigctld and m=2 isn' related
rigctl -r /dev/ttyUSB0 -m 122 -s 9600 -v
ft857:ft857_open called
Opened rig model 122, 'FT-857'
Backend version: 0.4, Status: Beta
Rig command: v
get_vfo: error = Feature not available
___
Tlf-devel maili
1.2.0
Here's rigctld -v after running tlf -v -d (otherwise I can't force
tlf to use hamlib)
After setting 140 (tlf diagnostic?) tlf tries to get currVFO ?
Connection opened from 127.0.0.1:46843
rigctl(d): 'currVFO' '' '' ''
rigctl(d): v 'currVFO' '' '' ''
rigctl(d): v 'currVFO' ''
On 03/01/2014 03:06 PM, Ervin Hegedüs wrote:
Hello,
On Sat, Mar 01, 2014 at 08:44:05PM +0100, Ervin Hegedüs wrote:
So, based on this I think that's rigctld problem. I'll see that
soon.
sorry - the problem would be on hamlib's side too. May be the
RIGMODEL 2 can't handle correctly the rig_get
Ervin,
As I said - the same problem if I connect to rig directly from tlf via
USB port, omitting rigctld (hence RIGMODEL=2 isn't the reason)
This might be some hamlib and/or tlf condition.
When I run rigctl -v I see some disturbing warnings with every 'f'
request regarding 'invalid cach
On 03/01/2014 03:06 PM, Ervin Hegedüs wrote:
Hello,
On Sat, Mar 01, 2014 at 08:44:05PM +0100, Ervin Hegedüs wrote:
So, based on this I think that's rigctld problem. I'll see that
soon.
sorry - the problem would be on hamlib's side too. May be the
RIGMODEL 2 can't handle correctly the rig_get
Hello,
On Sat, Mar 01, 2014 at 08:44:05PM +0100, Ervin Hegedüs wrote:
>
> So, based on this I think that's rigctld problem. I'll see that
> soon.
sorry - the problem would be on hamlib's side too. May be the
RIGMODEL 2 can't handle correctly the rig_get_vfo() - but may be
the problem is in the r
hi,
thanks for the report,
On Sat, Mar 01, 2014 at 08:36:07PM +0200, Zilvinas, AUGMA wrote:
>
> o.k. here's the results with another cable (YASEU CAT cable clone
> bought from ebay. I can use only USB cables for my netbook)
>
> lsusb
> 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
>
>
Hello Zilvinas,
On Sat, Mar 01, 2014 at 07:29:44PM +0200, Zilvinas, AUGMA wrote:
>
> On 01/03/14 11:23, Hegedüs Ervin wrote:
> > What's the second question?
>
> Oh... Sorry. My questions where what's wrong with my tlf-rigctld
> link and maybe this is somehow related with compile warnings I
> att
o.k. here's the results with another cable (YASEU CAT cable clone bought
from ebay. I can use only USB cables for my netbook)
lsusb
067b:2303 Prolific Technology, Inc. PL2303 Serial Port
All the same behaviour - I can switch bands, change frequency but no
frequency displayed.
tlf -v -d
On 01/03/14 11:23, Hegedüs Ervin wrote:
> What's the second question?
Oh... Sorry. My questions where what's wrong with my tlf-rigctld link
and maybe this is somehow related with compile warnings I attached
earlier (but now I am not sure).
So here's some research.
Until now I was using:
V
Hello Zilvinas,
On Sat, Mar 01, 2014 at 09:22:57AM +0200, Zilvinas, AUGMA wrote:
>
> Good morning All,
>
> Oops.. Ervin, I only this morning noticed your work announcement on
> the list...
> Quickly compiled and it works as promised! I quickly grepped log
> with earlier QSOs (so far 445 lines) a
Good morning All,
Oops.. Ervin, I only this morning noticed your work announcement on the
list...
Quickly compiled and it works as promised! I quickly grepped log with
earlier QSOs (so far 445 lines) and tlf correctly
shows all the warc qso's made earlier, including coloring to purple
color e
On 02/28/2014 07:35 PM, Ed wrote:
Get this error on ./configure --enable-hamlib
Can't exec "aclocal": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 326.
I did run::
autoreconf --install
Ed W3NR
Answer my own post. Left out 1 library on a new system.
Ed W3NR
On 02/28/2014 04:37 PM, Ervin Hegedüs wrote:
Dear Tlf users,
I fixed the "Worked window" disfunction in Tlf, you can download
here:
Get this error on ./configure --enable-hamlib
Can't exec "aclocal": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 326.
I did run
Dear Tlf users,
I fixed the "Worked window" disfunction in Tlf, you can download
here:
git: https://github.com/airween/tlf/tree/warc
zip: https://github.com/airween/tlf/archive/warc.zip
That's based on Thomas's last release, plus as Zilvinas
described, now you can use the worked window as you ac
Zilvinas, you dont have to. Just try :trx to switch rig control off.
Then you operate fldigi in parallel.
(also I must exit tlf because it interferes with fldigi while
operating digimodes)
73 Fred
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
ht
On 02/26/2014 11:25 AM, Ed wrote:
Bandmap does not work in digi mode.
Ed W3NR
Nor grabbing a spot from the cluster window
Ed W3NR
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel
Bandmap does not work in digi mode.
Ed W3NR
___
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel
On 02/26/2014 09:14 AM, Zilvinas, AUGMA wrote:
In rig I use (857) I must select DIG mode. I don't know if hamlib is
capable to transfer this MODE type to tlf I'll check.
I use fldigi for everyday psk operation but I did not yet find the way
how to thether/operate fldigi psk modes with tlf.
(
On 2014.02.26 15:14, Ervin Hegedüs wrote:
1. Nothing new - I would like to rise the Tom's question for one key
mode switching - I miss it - that typing semicolons and 2/3 letters
in qso mode is annoying (mix category in contests apply too)
good idea - I miss it too.
I would go further: it would
Hello,
On Wed, Feb 26, 2014 at 02:05:56PM +0200, Zilvinas, AUGMA wrote:
>
> On 2014.02.26 10:37, Ervin Hegedüs wrote:
> >... if anybody has any more idea, please shere with us.
>
> 1. Nothing new - I would like to rise the Tom's question for one key
> mode switching - I miss it - that typing sem
On 2014.02.26 10:37, Ervin Hegedüs wrote:
... if anybody has any more idea, please shere with us.
1. Nothing new - I would like to rise the Tom's question for one key
mode switching - I miss it - that typing semicolons and 2/3 letters in
qso mode is annoying (mix category in contests apply t
Hello all,
On Wed, Feb 26, 2014 at 09:49:08AM +0200, Zilvinas, AUGMA wrote:
>
> On 2014.02.25 22:43, Ervin Hegedüs wrote:
> >do you mean all non-WARC bands keeps this positions, and in QSO
> >mode there would be 3 new line: 12, 17 and 30 meters? Or in
> >reverse order (30, 17, 12)? That's no prob
On 2014.02.25 22:43, Ervin Hegedüs wrote:
do you mean all non-WARC bands keeps this positions, and in QSO mode
there would be 3 new line: 12, 17 and 30 meters? Or in reverse order
(30, 17, 12)? That's no problem, even that's easier.
Yes, exactly.
Maybe it would look nicer if all the bands wer
On 02/25/2014 02:57 PM, Ervin Hegedüs wrote:
Hello all,
On Mon, Jan 20, 2014 at 06:36:11PM +0200, Zilvinas, AUGMA wrote:
Greetings all,
I run tlf in qso mode also for everyday logging. I see the software
doesn't show WARC bands in "Worked" window.
so, that's true, everyone can reproduce,
T
Hello Zilvis,
On Tue, Feb 25, 2014 at 10:09:36PM +0200, Zilvinas, AUGMA wrote:
> Greetings Ervin!
>
> I am sending my current qso mode screenshot.
thanks,
> As far as I see there are exact three free lines between current QSO
> line and window frame.
yes, exactly,
> If I am not mistaking the
I just noticed that I almost repeated what you said in your letter, Ervin.
But IMHO window height shouldn't be a problem.
Just IMHO.
Sorry for the "noise"
On 25/02/14 22:09, Zilvinas, AUGMA wrote:
Greetings Ervin!
I am sending my current qso mode screenshot.
As far as I see there are exact
Hello all,
On Mon, Jan 20, 2014 at 06:36:11PM +0200, Zilvinas, AUGMA wrote:
> Greetings all,
>
> I run tlf in qso mode also for everyday logging. I see the software
> doesn't show WARC bands in "Worked" window.
so, that's true, everyone can reproduce,
> The bandmap is also affected - I just mad
Hello all,
On Wed, Jan 22, 2014 at 08:35:32AM +0100, Ervin Hegedüs - HA2OS wrote:
>
> but something is wrong in my config - when I works in QSO mode
> (CONTEST=qso, no CONTEST_MODE, SCOREWINDOW is set), I don't have
> score window... I'll review again when I'll close to my RIG.
this kept bugging
This is exactly what I was trying to tell and Ervin managed to replicate it.
I find this way of things in qso mode quite comfortable because this way
I can see some part of earlier QSOs report field and see what is
operator's name and QTH at least...
(I know these days 'modern' logs use qrz.co
Hello Thomas,
On Wed, Jan 22, 2014 at 07:18:01AM +0100, Thomas Beierlein wrote:
> Am Tue, 21 Jan 2014 23:08:30 +0100
> schrieb Ervin Hegedüs - HA2OS :
> > - start Tlf, switched to a WARC band (17m)
> > - start make a QSO (simulate), the "Worked" window opens up, but there
> > isn't any WARC band
Hi Ervin,
Am Tue, 21 Jan 2014 23:08:30 +0100
schrieb Ervin Hegedüs - HA2OS :
> On Tue, Jan 21, 2014 at 06:25:24AM +0100, Thomas Beierlein wrote:
> > Better use 'CONTEST=qso' and do NOT use 'CONTEST_MODE'. If you would
> > like to see your qso numbers on the different bands add
> > 'SCORINGWINDOW'
Hello Thomas,
On Tue, Jan 21, 2014 at 06:25:24AM +0100, Thomas Beierlein wrote:
> > LOGFILE=qso.log
> > CABRILLO=UNIVERSAL
> > CONTEST_MODE
> >
> Better use 'CONTEST=qso' and do NOT use 'CONTEST_MODE'. If you would
> like to see your qso numbers on the different bands add 'SCORINGWINDOW'
> to th
On 01/21/2014 01:42 PM, Thomas Beierlein wrote:
I still think it would be best left as is and work on refining the
rest of tlf.
Yes, that what I would also propose. At the moment we have still
a lot to fix for tlf's internal working as a contest logging program.
If some minor fixes on the way
Am Tue, 21 Jan 2014 11:45:00 -0500
schrieb Ed :
> On 01/21/2014 10:45 AM, Thomas Beierlein wrote:
>
> >> My bandmap shows the station just worked with an asterik before the
> >> call ( * ) and is colored for new and in uppercase.
> >>
> > The asterisk says the spot comes from yourself (any logged
On 01/21/2014 10:45 AM, Thomas Beierlein wrote:
My bandmap shows the station just worked with an asterik before the
call ( * ) and is colored for new and in uppercase.
The asterisk says the spot comes from yourself (any logged station will
get spooted in the internal network). If it is a dupe
Am Tue, 21 Jan 2014 08:46:39 -0500
schrieb Ed :
> On 01/21/2014 12:25 AM, Thomas Beierlein wrote:
> > Hi,
> >
> > here are my 2 ct's.
> >
> > Am Mon, 20 Jan 2014 13:26:11 -0500
> > schrieb Ed :
> >
> >> On 01/20/2014 11:36 AM, Zilvinas, AUGMA wrote:
> >>> Greetings all,
> >>>
> >>> I run tlf in qs
On 01/21/2014 12:25 AM, Thomas Beierlein wrote:
Hi,
here are my 2 ct's.
Am Mon, 20 Jan 2014 13:26:11 -0500
schrieb Ed :
On 01/20/2014 11:36 AM, Zilvinas, AUGMA wrote:
Greetings all,
I run tlf in qso mode also for everyday logging. I see the software
doesn't show WARC bands in "Worked" windo
On 2014.01.21 07:25, Thomas Beierlein wrote:
Because the limited place for the scoring window you will always see
only some of the bands. If you are on a non WARC band tlf will show the
contest bands only, as soon as you switch to a warc band you will see
the warc bands.
1. I was doing qso on
Hi,
here are my 2 ct's.
Am Mon, 20 Jan 2014 13:26:11 -0500
schrieb Ed :
> On 01/20/2014 11:36 AM, Zilvinas, AUGMA wrote:
> > Greetings all,
> >
> > I run tlf in qso mode also for everyday logging. I see the software
> > doesn't show WARC bands in "Worked" window.
Please see below.
> > The band
On 01/20/2014 03:12 PM, Ervin Hegedüs - HA2OS wrote:
Hello,
The big question is what would we like to work? I mean, the WARC
bands aren't used (never?) on any contest. So, it possible
they would be used only in QSO mode (there isn't CONTEST_MODE
option in rule file/logcfg.dat), but what's the
Ervin and all,
I really would like help to test it on ft857/hamlib/linux on your request.
Alias I can't code. Just can grab the code from git/www, compile and
test it. (but I can understand the logic behind the code).
I use tlf for everyday qso use and recently started some contesting too.
73
Hello,
On Mon, Jan 20, 2014 at 06:36:11PM +0200, Zilvinas, AUGMA wrote:
> Greetings all,
welcome on the list :)
> I run tlf in qso mode also for everyday logging. I see the software
> doesn't show WARC bands in "Worked" window.
> The bandmap is also affected - I just made a qso with station and
Thanks Ed,
The last one was missing (CONTEST_MODE) - when added it I get only
skipping WARC bands via band switching...
So this one seems needed for contests only...
73 Zilvis LY2SS
On 20/01/14 20:26, Ed wrote:
This is in my qso mode rules file
CONTEST=contest
LOGFILE=qso.log
CABRILLO=UNI
On 01/20/2014 11:36 AM, Zilvinas, AUGMA wrote:
Greetings all,
I run tlf in qso mode also for everyday logging. I see the software
doesn't show WARC bands in "Worked" window.
The bandmap is also affected - I just made a qso with station and it
does note become "lower case".
I do understand that
Greetings all,
I run tlf in qso mode also for everyday logging. I see the software
doesn't show WARC bands in "Worked" window.
The bandmap is also affected - I just made a qso with station and it
does note become "lower case".
I do understand that the all the focus and efforts are concentrate
54 matches
Mail list logo
