Re: not1mm
On Wed, 17 May 2023 07:25:52 -0500 Mike Waters wrote: > Only Debian based distros are mentioned. I'm curious to know if this > can be installed on Manjaro (Arch based). > > 73 Mike > W0BTU In my correspondence with the developer, it had to run on Python =>3.10. My Ubuntu systems are only at 3.8, so I need to upgrade to run it (it wouldn't compile on my ubuntu systems). 73, Jim KK0U
Re: DX Cluster Setup Help
Hi Alan, Glad you got it figured out. A couple of extra things for running on Ubuntu: I like to run tlf in a big terminal, and use urxvt as a terminal for that. My startup settings for that are urxvt -fn "xft: Liberation Mono:pixelsize=16" Also, not a huge fan of the default colors, so I use these in my logcfg.dat file: TLFCOLOR1=20 # headers and footers TLFCOLOR2=60 # pop up windows TLFCOLOR3=03 # log window TLFCOLOR4=01 # markers/dupe color TLFCOLOR5=02 # input fields TLFCOLOR6=60 # window frames Good luck in the ARRL DX test, and I enjoy your work on TWiV! 73, Jim KK0U > On Thu, 17 Feb 2022 17:59:01 + > Alan Dove wrote: > > > Hey, folks: > > > > Thanks for the quick replies. While testing Ervin's solution and > > looking through my logcfg.dat before sending it as Tom requested, I > > realized I hadn't uncommented the line that just says "CLUSTER". > > Doing that and restarting Tlf seems to have fixed it - spots are > > coming in and the filter toggles work as they should. > > > > Hope to work you all sometime soon. > > > > --Alan (AB1XW) > > > > >
Re: ARRL Sweepstakes
Hi Austin, When you wrote the Cabrillo file, when it asks for "exchange", did you put "# Q 91 MO" (that was my exchange, you would put whatever yours was in there)? If you do that, it should populate the Cabrillo file correctly. 73, Jim KK0U On Thu, 12 Nov 2020 02:49:48 -0500 "Austin Seraphin, KA3TTT" via wrote: > Hello. I participated in the ARRL Sweepstakes CW contest this > weekend. I use TLF 1.4.1. I copied the configuration and rules files > into my TLF directory. I exported ADIF and Cabrillo files. When I > submitted the Cabrillo log, the ARRL log submission software gave me > an error. > > > Number of fields in each QSO line less than mininum expected(15) > > > It looks like it did not populate the "check sent" and "sec sent" > fields. I noticed that when I logged the entries, it removed the > copied call from the exchange. I suppose I already entered it once. > > >
Re: tlf comments after CQP
Hi Drew, Thanks for your input. I also had questions about how to get tlf set up for this contest. In the end, I made a multiplier file with all the counties, and added a format line to cabrillo.fmt line. It wouldn't score the mults during the contest, but wrote them correctly in the cabrillo file, which is all I was really concerned with. I love tlf, and am woking on using it for SO2R. Basically, I'll have a computer hooked up to each radio, but send the xterm of one to the other so they're both on the same monitor. 73, Jim KK0U On Sun, 4 Oct 2020 23:23:24 + Drew Arnett wrote: > Hi, > > I used TLF for the CQP (California QSO Party) yesterday from San Diego > county. (Debian stable tlf package version 1.3.2-1) > > Worked fairly well. Would be nice to have 2 entry boxes to tab > between for serial and qth (mult) instead of one, but it was workable. > > I used an initial file which held QTH (mult) as well as super partial. > The only thing that wasn't so hot was that when I'd enter the serial > (and made sure QTH sent matched the initial), sometimes it would > revert the serial to blank or to the serial it had prefilled from > earlier QSO when I used ESM to finish the Q. Not sure on the details > of how and why, yet. Haven't played with it at home after the event > to better understand. > > So, that's the feedback. > > I love TLF. Love using it from linux console. I was running QRP off > of battery all day long. I didn't want to run a laptop off the > battery as well at 40 or 80 W. That just seems like a mismatch. So, > setup a Raspberry Pi 2 B which was the lowest power consumption model > from what I could find. Used the official Pi display & case. > > Peripherals were: > Elecraft's USB serial adapter for CAT > Winkeyer USB > generic USB to PS/2 adapter with old IBM model M keyboard > NO MOUSE! :-) > > 12 to 5V was using Powerwerx USB Buddy. (I hoped it would be RFI > free.) > > On the bench, this drew 0.4 A off of a bench 13.8 V supply. Wow, nice > match with a 5 W QRP rig! > > Linux console, default font, and a cardboard box for a sunshield. > Glare wasn't bad unless my light t-shirt was lit up by the sun. (I > was trying to stay in the shade.) > > And, the model M with it's curly PS/2 cable, still is prone to RF on > 40m. I had to use a snap on ferrite choke for 40m even QRP. > > I actually prepped a folder with tlf config files and database files > and pywinkeyerdaemon ahead of time on a regular PC. Checked it out, > make a git repot, and then copied onto the Pi. Nice. > > Best regards, > > Drew > n7da >
Re: so2r
Hi Matthew, Sounds like you and I are experiemnting with the same thing. Two computers, each controlling a separate radio, and each computer running an instance of TLF. On the "main" computer, I ssh to the computer that controls the second radio, and push the tlf terminal (urxvt) to the X server on the main computer. I have two urxvt sessions side-by-side, each running separate instances of TLF on separate computers controlling separate radios. As you stated, this doesn't require any modifications to TLF. 73, Jim KK0U On Sat, 23 May 2020 19:33:00 +0100 m5evt wrote: > I am still experimenting with the options for so2r and prototyping > some ideas. However, I have had some luck with: > > - x2 instances of TLF connected on LAN; > - split screen view within a terminal, tlf instances in left/right > split view; > - shift key bind to switch between each split view terminal. > > This works with no modification needed for tlf. I think this is a nice > option for the more casual so2r operator. > > 73 Matthew M5EVT.
Re: so2r
Hi Matthew, Sounds like you and I are experiemnting with the same thing. Two computers, each controlling a separate radio, and each computer running an instance of TLF. On the "main" computer, I ssh to the computer that controls the second radio, and push the tlf terminal (urxvt) to the X server on the main computer. I have two urxvt sessions side-by-side, each running separate instances of TLF on separate computers controlling separate radios. As you stated, this doesn't require any modifications to TLF. 73, Jim KK0U On Sat, 23 May 2020 19:33:00 +0100 m5evt wrote: > I am still experimenting with the options for so2r and prototyping > some ideas. However, I have had some luck with: > > - x2 instances of TLF connected on LAN; > - split screen view within a terminal, tlf instances in left/right > split view; > - shift key bind to switch between each split view terminal. > > This works with no modification needed for tlf. I think this is a nice > option for the more casual so2r operator. > > 73 Matthew M5EVT.
Re: A unified color scheme?
All,, Perhaps I should also add that I start urxvt with the following command line command, as I like the terminal to be really big & easy to read: urxvt -fn "xft: Liberation Mono:pixelsize=22" On Sun, 24 May 2020 07:40:08 -0500 Nate Bargmann wrote: > * On 2020 24 May 05:40 -0500, Koos van den Hout PE4KH wrote: > > On 5/23/20 11:50 PM, jim smith wrote: > > > > > I don't know if this adds anything to the discussion or not, but I > > > wrangled urxvt and played with the color options in tlf until I > > > landed on a high contrast version that works for me, especially > > > when I've been up too long and my eyes are tired. > > > > > > Seems to work across a couple of different versions of linux. > > > > Could you share your TLF/urxvt settings? > > I'd like to encourage everyone with customized settings to share them > as they would make a good addition to a set of Wiki pages I am > planning. > > 73, Nate >
Re: A unified color scheme?
Hi Koos, On Sun, 24 May 2020 12:39:47 +0200 Koos van den Hout PE4KH wrote: > On 5/23/20 11:50 PM, jim smith wrote: > > > I don't know if this adds anything to the discussion or not, but I > > wrangled urxvt and played with the color options in tlf until I > > landed on a high contrast version that works for me, especially > > when I've been up too long and my eyes are tired. > > > > Seems to work across a couple of different versions of linux. > > Could you share your TLF/urxvt settings? > > Koos PE4KH > Sure, they're at the end of my logcfg.dat file: TLFCOLOR1=20 # headers and footers TLFCOLOR2=60 # pop up windows TLFCOLOR3=03 # log window TLFCOLOR4=01 # markers/dupe color TLFCOLOR5=02 # input fields TLFCOLOR6=60 # window frames -- 73, Jim KK0U
Re: A unified color scheme?
On Sat, 23 May 2020 20:52:00 -0500 Nate Bargmann wrote: > Are either of you customizing the colors through the respective > terminal settings (Konsole)/Xresources (Rxvt) or through LOGCFG.DAT? Hi Nate -- I'm doing the custom color scheme entirely throught logcfg.dat. -- 73, Jim KK0U
Re: A unified color scheme?
Hi, I don't know if this adds anything to the discussion or not, but I wrangled urxvt and played with the color options in tlf until I landed on a high contrast version that works for me, especially when I've been up too long and my eyes are tired. Seems to work across a couple of different versions of linux. On Sat, 23 May 2020 19:22:21 +0100 m5evt wrote: > Hi, > > I use a custom colour profile in konsole. I've attached a screenshot > of how I have tlf configured. With a couple of releases of tlf the > under lying code in tlf seems to have changed and my colour scheme > changes in some way. Sometimes it is hard to get back to how it was. > > If these changes make the underlying code for colours more stable and > less likely to change with each release, I think this sounds good. > > 73 Matthew M5EVT.
Re: Real RST possible?
On Tue, 28 Jan 2020 20:13:04 +0100 Thomas Beierlein wrote: > Ok, That would only extend the functionality of CHANGE_RST. If > changing only the first two numbers are enough that would be the most > easy solution. If key auto repeat does also work for PgUp/PgDn (needs > to be tested) you need not to much key presses to sweep over the > range. > > Jim, would that solve your needs? If so it can be implemented in next > weeks. I think so. And in any case, I think defer to "make it easiest for the 'Run' operator. If the S op has to make a few more keypresses to get things done, that's fine. Also, that final 9 can alwasy be 9 in RST, IMO. > > Probably the reason this hasn't been requested before is that major > > contest sponsors mostly ignore the signal report for log checking. > > And in contest we ignore the 'real' RST value from the band and stay > with 5nn to make more contacts per time. > > 73, de Tom I agree with that -- in most contests the RS(T) is a given. But for QRP and especially SOTA operations (where I would *really* like to use tlf), it would be most helpful to be able to type in the R and S of RST. Thanks to all for considering this. I used tlf in last weekend's CQ160m contest, and it never missed a beat. *I* did, but it did not. 73, Jim KK0U
Real RST possible?
First, I know there is the CHANGE_RST directive, but for QRP contests (at least in the states), many times ops send an actual RST -- 33N, 439, etc. Is there any way to incorporate this in both the received stations data (I imagine it would be in the exchange field, like a serial number) and for the sending station? It would be helpful the above mentioned QRP contests, geneal ragchews and for SOTA operations as well. Thanks! -- Jim KK0U (ex-N0OCT)
Re: tlf and the nano editor
On Fri, 22 Nov 2019 15:06:14 +0100 Joop Stakenborg wrote: > I have gotten used to the GNU nano editor, but it does not seem to > work with tlf. When I type :edit in the callsign field, tlf exits and > returns straight away without opening nano. Both joe and vi work okay > here. It is hard to debug, have to spent some time on it to see what > actually happens. Maybe use gdb with a break added. I will have a > look next week. > > > 73 de Joop PG4I > Hi Joop, I don't know if this helps any, but I don't have any problems running nano with tlf on ubuntu 18.04. I have *not* updgraded to tlf 1.4 yet (was going to do that this weekend.
Re: trouble scoring the LZ-DX contest
Thomas, Just throwing out an idea here, would it be possible to have one keyword (say CUSTOM) for the rules file, and for that particular contest the user could build their own multiplier file? Might be tedious once, but might provide an interim work-around until something more sophisticated could be implemented. -- 73, Jim N0OCT On Sun, 17 Nov 2019 18:19:14 +0100 Thomas Beierlein wrote: > Hi Joop, > > > Am Sun, 17 Nov 2019 10:30:22 +0100 > schrieb Joop Stakenborg : > > > First of all, thanks for the new release! I have started using tlf a > > few weeks ago, very happy! > > > Nice to hear. > > > > I am having trouble scoring the lz-dx contest. Points are okay, but > > multipliers not. The multiplier is either the ITU zone or the LZ > > district. So I would like to have something like ITU_&_SECTIONS, > > which would work the same as DX_&_SECTIONS. > > > Sigh, it is a trouble with those 'creative' contest designers (Rant > off). > > You are right, at the moment there is no solution for your problem. > Scoring your contest results will be correct, as it is done by the > contest organizer. But we would want at least a good guess how we are > doing. > > The keyword suggested by you (ITU_&_SECTIONS, or better > ZONE_&_SECTIONS) would work (and could be added in the next version of > TLF). > > But I fear there will be another combination of multipliers > poping up soon which we do not have in our repertoire. > So a better solution is needed - same goes for point scoring. > > I did some investigation how other contest programs solve these > problem. One of the ideas there are to classify multipliers into some > main categories: > > - Country/DXCC > - Zone CQ or ITU > - Prefix > - section or similar > > With that we could allow more to count more than one category as multi > and would need additional rules how to combine the values (add if more > than one or score only one) and how to count on different > bands (BY-BAND or ONCE). Than your ITU_&_SECTION could be something > like: > > COUNTRY_MULT = DXCC,BY_BAND > ZONE_MULT = ITU,BY_BAND ADD > > I am not sure if that would catch all or at least most of the multi > scoring problems for existing contests. > > Feedback on that is very much welcome. > > 73, de Tom DL1JBE > > > > > Here is part of my rules file, which does not work properly > > (lz_dx_mults attached): > > > > > > # > > # CONTEST PARAMETERS > > # > > # > > MULT_LIST=lz_dx_mults > > COUNTRYLIST=LZ > > SECTION_MULT > > ITUMULT > > # > > # > > # POINTS LIST > > # > > # > > COUNTRY_LIST_POINTS=10 > > MY_CONTINENT_POINTS=1 > > DX_POINTS=3 > > > > > > > > >
Re: trouble scoring the LZ-DX contest
Thomas, Just throwing out an idea here, would it be possible to have one keyword (say CUSTOM) for the rules file, and for that particular contest the user could build their own multiplier file? Might be tedious once, but might provide an interim work-around until something more sophisticated could be implemented. -- 73, Jim N0OCT On Sun, 17 Nov 2019 18:19:14 +0100 Thomas Beierlein wrote: > Hi Joop, > > > Am Sun, 17 Nov 2019 10:30:22 +0100 > schrieb Joop Stakenborg : > > > First of all, thanks for the new release! I have started using tlf a > > few weeks ago, very happy! > > > Nice to hear. > > > > I am having trouble scoring the lz-dx contest. Points are okay, but > > multipliers not. The multiplier is either the ITU zone or the LZ > > district. So I would like to have something like ITU_&_SECTIONS, > > which would work the same as DX_&_SECTIONS. > > > Sigh, it is a trouble with those 'creative' contest designers (Rant > off). > > You are right, at the moment there is no solution for your problem. > Scoring your contest results will be correct, as it is done by the > contest organizer. But we would want at least a good guess how we are > doing. > > The keyword suggested by you (ITU_&_SECTIONS, or better > ZONE_&_SECTIONS) would work (and could be added in the next version of > TLF). > > But I fear there will be another combination of multipliers > poping up soon which we do not have in our repertoire. > So a better solution is needed - same goes for point scoring. > > I did some investigation how other contest programs solve these > problem. One of the ideas there are to classify multipliers into some > main categories: > > - Country/DXCC > - Zone CQ or ITU > - Prefix > - section or similar > > With that we could allow more to count more than one category as multi > and would need additional rules how to combine the values (add if more > than one or score only one) and how to count on different > bands (BY-BAND or ONCE). Than your ITU_&_SECTION could be something > like: > > COUNTRY_MULT = DXCC,BY_BAND > ZONE_MULT = ITU,BY_BAND ADD > > I am not sure if that would catch all or at least most of the multi > scoring problems for existing contests. > > Feedback on that is very much welcome. > > 73, de Tom DL1JBE > > > > > Here is part of my rules file, which does not work properly > > (lz_dx_mults attached): > > > > > > # > > # CONTEST PARAMETERS > > # > > # > > MULT_LIST=lz_dx_mults > > COUNTRYLIST=LZ > > SECTION_MULT > > ITUMULT > > # > > # > > # POINTS LIST > > # > > # > > COUNTRY_LIST_POINTS=10 > > MY_CONTINENT_POINTS=1 > > DX_POINTS=3 > > > > > > > > >
Re: TLF-1.4.0 release
Hi, I'm a long-time lurker on this list, and a long-time user of TLF (since '04 or so) just getting back into contesting after a life detour. I think TLF is great! So in addition to SM0RUX I would like to offer many thanks to all the developers that keep this project moving forward. Completed ARRL Sweepstakes CW with it, and it worked as well as always. -- 73, Jim N0OCT On Fri, 15 Nov 2019 08:39:38 +0100 Pontus Falk wrote: > Hi, > > Den 2019-11-13 kl. 15:06, skrev Thomas Beierlein: > > > After a lot of work by all people contributing to TLF I would like > > to announce the release of the new TLF-1.4.0 version. > > > > You can find it at > > > > http://download.savannah.gnu.org/releases/tlf/tlf-1.4.0.tar.gz or > > https://github.com/Tlf/tlf/releases/download/tlf-1.4.0/tlf-1.4.0.tar.gz > Thanks a zillion to all of you involved in the development. > > I've been using tlf for a couple of years, most recently in CQ WW SSB > 2019 and I'm so happy with 1.3.0 - and I see a lot of improvements > already by just starting 1.4.0. > > Thanks again! > > 73's de SM0RUX Pontus (SM0R in contests) >
Re: [Tlf-devel] TLF goes straight to cluster?
On Sat, 17 Jan 2009 22:28:38 -0500 Ryan Ferreri r...@ryanandcorissa.com wrote: Hi there, I installed TLF 0.9.30 on Ubuntu 8.10. When I run tlf, it logs in to a DX cluster. How do I get it to go into the logging window? When it starts up it says, Use : to go to TLF ! ! but I have no idea what it's asking me to do there. Thanks! Ryan - KB8HOC Either call tlf as tlf -n or comment out all the cluster stuff in the logcfg.dat file. I use a unique logcfg.dat file for each contest. Basically, each contest has it's own directory with .dat file, rules, logs, etc. -- jim smith n0...@sbcglobal.net ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] NAQP file?
Anyone tried to write a rules file for the North American QSO Party? I think it would probably need its own separate file like arrl_ss. I've tried a couple of things, but none get the cabrillo file to print anywhere close to what it should be. If anyone has either done it, or had some suggestions, I'm all ears. ;-) Thanks. -- jim smith n0...@sbcglobal.net ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] Re: [TLF] Improvement Suggestions
I hate to stir up really old issues, but I've got some input on this: OnFri, 4 Jul 2008 08:49:31 -0700 Chris Maness wrote: 2. Separate fields specifically for populating the correct adif fields for the contests in question. For example: when it is in FD mode, the exchange 2A WWA should not just go in the comment field. 2A needs to go in the CLASS field and WWA needs to go into ARRL_SEC field. This would probably require 3 seperate entry fields (CALL, CLASS, ARRL_SEC). These fields should be re-definable -- so they could be used for other contest and other adif fields (ie grid square). This fields should be defined in the rules file for that contest. I disagree. What is the purpose of the ADIF specification? TLF was written [IMO] to conform to the Cabrillo format standard for contesting. As such, it should treat data entry for FD just like for any other contest. If you've ever used tlf for November Sweepstakes, or example, you would see the logic and the beauty of the exchange going into the comment field. For SS, the exchange is serial number, precedence, call sign, year licensed, and ARRL section. I've used a couple of logging programs [one written specifically for SS] that required you to enter the exchange in one specific order. If that's not how the op on the other end sent it, it was a small nightmare to get everything copied. In tlf, you can enter that exchange in *any* order, and the program inputs it correctly into the log, and into Cabrillo format when that file is written. SS does have its own special rules file and coding within tlf. I would suggest that [special coding of a rules file within tlf] route be taken if anyone wants to code for FD. After all, whether we like it or not, FD is a contest, and the output Cabrillo file is the deliverable produced from tlf. If you want the log formatted in another way for other purposes, I'm sure a quick processor with readily available tools can be written. Just my dwindling $0.02. -- Jim Smith n0...@sbcglobal.net ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
[Tlf-devel] If using FreeBSD and X11, run 'aterm' as your terminal.
Ever the FreeBSD advocate of the group, I would like to share something I discovered this weekend. If you're using tlf on FreeBSD, 'aterm' is your friend. I've tried running tlf on my laptop console [setting TERM as 'linux' and various other types] and it is really a mess. So, I run tlf while running X11. The standard xterm doesn't have the keyboard functionality that makes tlf useful. 'aterm' http://aterm.sourceforge.net/ gets 80-90% of the complete functionality of a standard terminal. The F1 key doesn't work [and in my window manager WindowMaker, the F11 and F12 keys are already spoken for], the alt-# keys are also controlled by my window manager, but everything else seems to work pretty well. So, if you can do without 24 different pre programmed messages [or tweak your UI so that you can] 'aterm' in X11 with FreeBSD is a winner. I'll figure out what window manager works best [i.e. doesn't map the other function keys or the alt-# keys] before two weeks. -- 73, Jim N0OCT ___ Tlf-devel mailing list Tlf-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tlf-devel
