Re: tlf and the nano editor

[Joop Stakenborg]

Forgot to edit tlf.1.in. Sorry!


> Op 22 nov. 2019, om 16:10 heeft Joop Stakenborg  
> het volgende geschreven:
> 
> Ah well... might as well add it right away, seems to work okay here. Diff 
> attached!
> 
> 
> 
> Joop
> 
> Op 22-11-19 om 15:35 schreef joop.stakenb...@xs4all.nl 
> :
>> Thanks Nate! Looks really simple... Will try it out next week.
>> 
>> Joop
>> 
>> Op 22 nov. 2019 15:13 schreef Nate Bargmann  
>> :
>> * On 2019 22 Nov 08:07 -0600, 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. 
>> 
>> It should be fairly simple as I added mcedit to the list of available 
>> editors.  A quick 'git grep mcedit' shows where mcedit was added: 
>> 
>> $ git grep mcedit 
>> ChangeLog:1117:  * share/logcfg.dat, src/editlog.c, src/parse_logcfg.c: 
>> Prefer 'mcedit' for 
>> ChangeLog:1119:  Enable 'mcedit' as a log file editor. 
>> share/logcfg.dat:33:#EDITOR=mcedit 
>> src/changepars.c:359:   strcpy(cmdstring, "mcedit "); 
>> src/editlog.c:63:   strcat(comstr, "mcedit  "); 
>> src/parse_logcfg.c:904: if ((strncmp(buff, "mcedit", 6) == 0) 
>> tlf.1.in:282:Edit the log with your favourite editor (the editor 
>> (vi[m]|joe|e3|mcedit) 
>> tlf.1.in:975:You can set your favourite editor (joe | vi[m] | e3 | mcedit) 
>> in the 
>> tlf.1.in:1047:\fBEDITOR\fR=\fIjoe\fR | \fIvi\fR[\fIm\fR] | \fIe3\fR | 
>> \fImcedit\fR 
>> 
>> This should help you get started, Joop. 
>> 
>> 73, Nate 
>> 
>> -- 
>> 
>> "The optimist proclaims that we live in the best of all 
>> possible worlds.  The pessimist fears this is true." 
>> 
>> Web: https://www.n0nb.us  
>> Projects: https://github.com/N0NB  
>> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 
>> 
>> 
>> 
> 

Re: TLF-1.4.0 release

[Nate Bargmann]

* On 2019 22 Nov 00:56 -0600, Thomas Beierlein wrote:

On a side note, something happened with your GPG signature as it
appeared to be in "classic PGP" format to Mutt.  I did the Esc-P to
verify the signature and the message text disappears and all I see is
the good signature.  Scratches head...

I red your reply in the archive and now that you mention it, I do seem
to recall some discussion about vertical resize.  I'll check it out!

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: tlf and the nano editor

[Nate Bargmann]

* On 2019 22 Nov 08:07 -0600, 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.

It should be fairly simple as I added mcedit to the list of available
editors.  A quick 'git grep mcedit' shows where mcedit was added:

$ git grep mcedit
ChangeLog:1117:  * share/logcfg.dat, src/editlog.c, src/parse_logcfg.c: Prefer 
'mcedit' for
ChangeLog:1119:  Enable 'mcedit' as a log file editor.
share/logcfg.dat:33:#EDITOR=mcedit
src/changepars.c:359:   strcpy(cmdstring, "mcedit ");
src/editlog.c:63:   strcat(comstr, "mcedit  ");
src/parse_logcfg.c:904: if ((strncmp(buff, "mcedit", 6) == 0)
tlf.1.in:282:Edit the log with your favourite editor (the editor 
(vi[m]|joe|e3|mcedit)
tlf.1.in:975:You can set your favourite editor (joe | vi[m] | e3 | mcedit) in 
the
tlf.1.in:1047:\fBEDITOR\fR=\fIjoe\fR | \fIvi\fR[\fIm\fR] | \fIe3\fR | 
\fImcedit\fR

This should help you get started, Joop.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: tlf and the nano editor

[joop . stakenborg]

Thanks Nate! Looks really simple... Will try it out next week.JoopOp 22 nov. 2019 15:13 schreef Nate Bargmann :* On 2019 22 Nov 08:07 -0600, 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.

It should be fairly simple as I added mcedit to the list of available
editors.  A quick 'git grep mcedit' shows where mcedit was added:

$ git grep mcedit
ChangeLog:1117:  * share/logcfg.dat, src/editlog.c, src/parse_logcfg.c: Prefer 'mcedit' for
ChangeLog:1119:  Enable 'mcedit' as a log file editor.
share/logcfg.dat:33:#EDITOR=mcedit
src/changepars.c:359:   strcpy(cmdstring, "mcedit ");
src/editlog.c:63:   strcat(comstr, "mcedit  ");
src/parse_logcfg.c:904: if ((strncmp(buff, "mcedit", 6) == 0)
tlf.1.in:282:Edit the log with your favourite editor (the editor (vi[m]|joe|e3|mcedit)
tlf.1.in:975:You can set your favourite editor (joe | vi[m] | e3 | mcedit) in the
tlf.1.in:1047:\fBEDITOR\fR=\fIjoe\fR | \fIvi\fR[\fIm\fR] | \fIe3\fR | \fImcedit\fR

This should help you get started, Joop.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: tlf and the nano editor

[jim smith]

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.

tlf and the nano editor

[Joop Stakenborg]

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

Re: tlf and the nano editor

[Joop Stakenborg]

Ah well... might as well add it right away, seems to work okay here. 
Diff attached!



Joop

Op 22-11-19 om 15:35 schreef joop.stakenb...@xs4all.nl:

Thanks Nate! Looks really simple... Will try it out next week.

Joop

Op 22 nov. 2019 15:13 schreef Nate Bargmann :

* On 2019 22 Nov 08:07 -0600, 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.

It should be fairly simple as I added mcedit to the list of available
editors.  A quick 'git grep mcedit' shows where mcedit was added:

$ git grep mcedit
ChangeLog:1117:  * share/logcfg.dat, src/editlog.c,
src/parse_logcfg.c: Prefer 'mcedit' for
ChangeLog:1119:  Enable 'mcedit' as a log file editor.
share/logcfg.dat:33:#EDITOR=mcedit
src/changepars.c:359:   strcpy(cmdstring, "mcedit ");
src/editlog.c:63:   strcat(comstr, "mcedit  ");
src/parse_logcfg.c:904: if ((strncmp(buff, "mcedit", 6) == 0)
tlf.1.in:282:Edit the log with your favourite editor (the editor
(vi[m]|joe|e3|mcedit)
tlf.1.in:975:You can set your favourite editor (joe | vi[m] | e3 |
mcedit) in the
tlf.1.in:1047:\fBEDITOR\fR=\fIjoe\fR | \fIvi\fR[\fIm\fR] |
\fIe3\fR | \fImcedit\fR

This should help you get started, Joop.

73, Nate

-- 


"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819


diff --git a/src/changepars.c b/src/changepars.c
index 02970c1..2d5bbb1 100644
--- a/src/changepars.c
+++ b/src/changepars.c
@@ -358,6 +358,8 @@ int changepars(void) {
 		strcpy(cmdstring, "vi ");
 	} else if (editor == EDITOR_MC) {
 		strcpy(cmdstring, "mcedit ");
+	} else if (editor == EDITOR_NANO) {
+		strcpy(cmdstring, "nano ");
 	} else {
 		strcpy(cmdstring, "e3 ");
 	}
diff --git a/src/editlog.c b/src/editlog.c
index e11c140..bf82bdb 100644
--- a/src/editlog.c
+++ b/src/editlog.c
@@ -53,6 +53,8 @@ int logedit(void) {
 	strcat(comstr, "vi  ");
 else if (editor == EDITOR_MC)
 	strcat(comstr, "mcedit  ");
+else if (editor == EDITOR_NANO)
+	strcat(comstr, "nano  ");
 else
 	strcat(comstr, "e3  ");
 
diff --git a/src/parse_logcfg.c b/src/parse_logcfg.c
index 43b53a4..0de1085 100644
--- a/src/parse_logcfg.c
+++ b/src/parse_logcfg.c
@@ -934,6 +934,11 @@ int parse_logcfg(char *inputbuffer) {
 	if (j != NULL) {
 		editor = EDITOR_VI;
 		break;
+	}
+	j = strstr(fields[1], "nano");
+	if (j != NULL) {
+		editor = EDITOR_NANO;
+		break;
 	} else {
 		editor = EDITOR_E3;
 		break;
diff --git a/src/tlf.h b/src/tlf.h
index ae11b76..61b5a61 100644
--- a/src/tlf.h
+++ b/src/tlf.h
@@ -119,6 +119,7 @@ enum {
 #define EDITOR_VI 1
 #define EDITOR_E3 2
 #define EDITOR_MC 3
+#define EDITOR_NANO 4
 
 #define UNIQUECALL_ALL  1
 #define UNIQUECALL_BAND 2

Re: tlf and the nano editor

[Nate Bargmann]

* On 2019 22 Nov 15:17 -0600, Thomas Beierlein wrote:
> Hi Joop,
 
> In the case that someone forgot to specify the EDITOR= command I will
> fall back to the editor specified in the environment.

Very sensible, Tom.

It would be interesting if someone's favorite editor could not accept a
filename on the command line.  Also, I may have to see if a GUI editor
will work.  Heck, even Emacs might work! ;-)

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: Using hamlib for CW keying

[Csahok Zoltan]

Hi Christian,

Yes, keying does work with the script. But as far I can see
there are two issues with hamlib keying:

- in-band speed changes are not supported. one can't send "+++TEST---"

- sending a large message could block rig interface until it gets queued.

Given the rig protocol (KY command) and the way hamlib supports it
I see no option to circumvent these.

WinKeyer on the other hand offers in-band speed change and winkeyerdaemon
provides the buffering for a cwdaemon compatible UDP interface.

Correct me if I'm wrong here.


73,
Zoli


On Fri, Nov 22, 2019 at 12:18:18AM +0100, Christian Treldal wrote:
> 
> I tested today $echo "+\send_morse'test'" | nc -w 1 localhost 4532 to a
> IC-7610 and it cw happily
> 

Re: tlf and the nano editor

[Nate Bargmann]

* On 2019 22 Nov 09:19 -0600, Joop Stakenborg wrote:
> Forgot to edit tlf.1.in. Sorry!

Just pass along your diff for it, Joop.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: tlf and the nano editor

[Thomas Beierlein]

Hi all,

as the fixed choice of editors is quite a nuisance I prepared a
changed version for tests. Please find it at
https://github.com/dl1jbe/tlf/tree/new_editor

Download the code and build TLF as told in the INSTALL file. Do not
forget the 'autoreconf -i' step.

The new version accepts any string as editor command and will just call
that program with the logfile name as parameter.

That means

EDITOR=my-shiny-editor

in logcfg.dat will call

'my-shiny-editor '

So a simple EDITOR=nano should do afterwards.

Please test and give feedback. 

73, de Tom DL1JBE

Am Fri, 22 Nov 2019 11:08:52 -0600
schrieb jim smith :

> 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.



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: tlf and the nano editor

[Thomas Beierlein]

Hi Joop,

thanks for the test. It was just a quick shot for a test. I will look
into it tomorrow evening. 

In the case that someone forgot to specify the EDITOR= command I will
fall back to the editor specified in the environment.

73, de Tom

Am Fri, 22 Nov 2019 20:57:59 +0100 schrieb Joop Stakenborg
:

> Hi Tom,
> 
> 
> it works okay for the :edit command, but you need to change the code
> for both the :set and :cfg commands (which allows editing of
> logcfg.dat), they both start the joe editor, even though I have
> EDITOR=nano in logcfg.dat.
> 
> The code is in changepars.c
> 
> Thanks,
> 
> Joop
> 
> Op 22-11-19 om 20:19 schreef Thomas Beierlein:
> > Hi all,
> >
> > as the fixed choice of editors is quite a nuisance I prepared a
> > changed version for tests. Please find it at
> > https://github.com/dl1jbe/tlf/tree/new_editor
> >
> > Download the code and build TLF as told in the INSTALL file. Do not
> > forget the 'autoreconf -i' step.
> >
> > The new version accepts any string as editor command and will just
> > call that program with the logfile name as parameter.
> >
> > That means
> >
> > EDITOR=my-shiny-editor
> >
> > in logcfg.dat will call
> >
> > 'my-shiny-editor '
> >
> > So a simple EDITOR=nano should do afterwards.
> >
> > Please test and give feedback.
> >
> > 73, de Tom DL1JBE
> >
> > Am Fri, 22 Nov 2019 11:08:52 -0600
> > schrieb jim smith :
> >  
> >> 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.  
> >
> >  



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

Re: Using hamlib for CW keying

[Nate Bargmann]

* On 2019 22 Nov 14:31 -0600, Csahok Zoltan wrote:
> Hi Christian,
> 
> Yes, keying does work with the script. But as far I can see
> there are two issues with hamlib keying:
> 
> - in-band speed changes are not supported. one can't send "+++TEST---"
> 
> - sending a large message could block rig interface until it gets queued.
> 
> Given the rig protocol (KY command) and the way hamlib supports it
> I see no option to circumvent these.
> 
> WinKeyer on the other hand offers in-band speed change and winkeyerdaemon
> provides the buffering for a cwdaemon compatible UDP interface.
> 
> Correct me if I'm wrong here.

You may well be correct, Zoli.  As I recall, a speed change would
require sending the proper CAT command each time the change is made.
It's possible this could be done in a manner that doesn't mess up the
timing of the sent Morse, I think it would likely be very rig specific.

One thing the K3 and the later models can do is be keyed via the RTS/DTR
line and N1MM+ takes full advantage of that, speed changes and all.
Problem is whether more rigs support that and whether Hamlib supports
it.  Even though I've been a part of the Hamlib project for quite some
time, I'm not sure!  There may be some provision but probably needs some
debugging.  Again, this is a feature that is rig specific.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: tlf and the nano editor

[Joop Stakenborg]

Hi Tom,


it works okay for the :edit command, but you need to change the code for 
both the :set and :cfg commands (which allows editing of logcfg.dat), 
they both start the joe editor, even though I have EDITOR=nano in 
logcfg.dat.


The code is in changepars.c

Thanks,

Joop

Op 22-11-19 om 20:19 schreef Thomas Beierlein:

Hi all,

as the fixed choice of editors is quite a nuisance I prepared a
changed version for tests. Please find it at
https://github.com/dl1jbe/tlf/tree/new_editor

Download the code and build TLF as told in the INSTALL file. Do not
forget the 'autoreconf -i' step.

The new version accepts any string as editor command and will just call
that program with the logfile name as parameter.

That means

EDITOR=my-shiny-editor

in logcfg.dat will call

'my-shiny-editor '

So a simple EDITOR=nano should do afterwards.

Please test and give feedback.

73, de Tom DL1JBE

Am Fri, 22 Nov 2019 11:08:52 -0600
schrieb jim smith :


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: tlf and the nano editor

[Nate Bargmann]

My first test with EDITOR=gedit resulted in nothing happening.  I ran
gedit from another terminal and it opened fine.  Then I tried emacs
from the terminal and it opened fine in the GUI.  I then tested both
emacs and gedit as Tlf editors and they worked fine.  I'm not sure what
was going on so it might be useful for others to test GUI editors as
well.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: tlf and the nano editor

[Csahok Zoltan]

My 2c: try with "export EDITOR=..."

73,
Zoli

On Fri, Nov 22, 2019 at 07:18:35PM -0600, Nate Bargmann wrote:
> My first test with EDITOR=gedit resulted in nothing happening.  I ran
> gedit from another terminal and it opened fine.  Then I tried emacs

Re: Using hamlib for CW keying

[Christian Treldal]

Hi Ervin

Den 22.11.2019 kl. 09.49 skrev Ervin Hegedüs:





ohh... :)

I found it in my Dropbox :P

A memoryleak;-)
  

I've been trying to convert it to Py3 , no capitals in socketserver and
remove .decode("utf8") and is seems to run; but it don't send anything to
the radio.

hmm, sounds interesting.

Anyway, I modified the code, it's avaliable here:

https://www.dropbox.com/s/4jiqdsesomcccio/rigkeyer.py

(the old link redirects to the rigkeyer2.py)

Note, that I've tested now with both Python version (2 and 3). My
TRX doesn't support the CW keying via Hamlib (TS850 still), but I
could test it with the DUMMY RIG. Now it works as well, there
were an another necessary modification in line 25 (in old code).



I just made a quick test with my KX3 and we are back in business


you mean aboue like K3? Once I started to review how does it
works, but IMHO it's too difficult. We discussed about this topic with
Zoli HA5CQZ, but now I don't remember the results.

I've been using it with my KX3 and no problems. In the beginning there was a
buffer overflow in hamlib; but it seems to be ok now

sure, then I assume you successfully installed the Hamlib Pythons
module for Python 3.
  

I tested today $echo "+\send_morse'test'" | nc -w 1 localhost 4532 to a
IC-7610 and it cw happily

please check it again with this new version above!

Anybody can use it with this way:

python2 rigkeyer.py

or

python3 rigkeyer.py


HTH,



73, Ervin
HA2OS
  


Again thanks a lot Ervin, see you in the test

73, Chris

--
Med venlig hilsen


Christian Treldal
"Remember Darwin; building a better mousetrap merely results in smarter mice."

Re: Using hamlib for CW keying

[Ervin Hegedüs]

Hi Christian,

On Fri, Nov 22, 2019 at 12:18:18AM +0100, Christian Treldal wrote:
> 
> Den 21.11.2019 kl. 14.58 skrev Ervin Hegedüs:
> >Hi Christian,
> >
> >On Thu, Nov 21, 2019 at 12:29:38PM +0100, Christian Treldal wrote:
> >>A year or something ago Ervin wrote a quick Python2 script for keying via
> >>hamlib. It has n
> >I MADE A PYTHON SCRIPT? :D
> >
> >Could share with me/us? :)
> >
> Yes Ervin  AND THE EVIDENCE!!!
> 
> https://www.dropbox.com/s/ofn5p482dsf49tv/rigkeyer.py

ohh... :)

I found it in my Dropbox :P
 
> I've been trying to convert it to Py3 , no capitals in socketserver and
> remove .decode("utf8") and is seems to run; but it don't send anything to
> the radio.

hmm, sounds interesting. 

Anyway, I modified the code, it's avaliable here:

https://www.dropbox.com/s/4jiqdsesomcccio/rigkeyer.py

(the old link redirects to the rigkeyer2.py)

Note, that I've tested now with both Python version (2 and 3). My
TRX doesn't support the CW keying via Hamlib (TS850 still), but I
could test it with the DUMMY RIG. Now it works as well, there
were an another necessary modification in line 25 (in old code).

> >you mean aboue like K3? Once I started to review how does it
> >works, but IMHO it's too difficult. We discussed about this topic with
> >Zoli HA5CQZ, but now I don't remember the results.
> 
> I've been using it with my KX3 and no problems. In the beginning there was a
> buffer overflow in hamlib; but it seems to be ok now

sure, then I assume you successfully installed the Hamlib Pythons
module for Python 3.
 
> I tested today $echo "+\send_morse'test'" | nc -w 1 localhost 4532 to a
> IC-7610 and it cw happily

please check it again with this new version above!

Anybody can use it with this way:

python2 rigkeyer.py

or

python3 rigkeyer.py


HTH,



73, Ervin
HA2OS
 

Re: Don't forget Winkeydaemon!

[SP3RXO]

BTW there is other solution which working great with TLF.  Winkeyer USB
UDP server by OK2CQR (CQRLOG developer).
UDP server allows operation of the Winkey USB by K1EL with any Linux
program with UDP keyer capability. It works in the same way as the
popular cwdaemon. With Winkeyer USB server expands the useability of
this excellent product to all Linux program with UDP keyer capability.

Download from https://www.cqrlog.com/?q=node/149 or get source code from
https://github.com/ok2cqr/winkeyer_server

73!
Slav, SP3RXO & EI2IDB
FISTS #19019
SOC #1251
SP CW Club #UNKNOWN

W dniu 22.11.2019 o 08:42, Koos van den Hout PE4KH pisze:
> Quoting Nate Bargmann who wrote on Thu 2019-11-21 at 19:31:
> 
>> I gathered together the various pieces and put them into Git and have
>> hosted the code at GitHub for some time:
>> https://github.com/N0NB/winkeydaemon
>>
>> Wilbert has added more contributions over the years, as have Zoltan
>> All that said, if anyone has one of the Winkeyer USB models, I'd
>> appreciate some testing.  A friend has been having trouble getting his
>> to work with winkeydaemon and we've not gotten together to try
>> troubleshooting it.
> 
> I can at least share that I use that winkeydaemon with a nanokeyer and it
> works fine as described in https://idefix.net/~koos/newsitem.cgi/1567804130
> 
> I haven't gotten around to testing it with TLF, maybe there is some QRS CW
> activity that I can participate in (also good to keep practising morse).
> 
> Koos PE4KH
> 


0xD1A3320970F8F900.asc
Description: application/pgp-keys

Re: Don't forget Winkeydaemon!

[Koos van den Hout PE4KH]

Quoting Nate Bargmann who wrote on Thu 2019-11-21 at 19:31:

> I gathered together the various pieces and put them into Git and have
> hosted the code at GitHub for some time:
> https://github.com/N0NB/winkeydaemon
> 
> Wilbert has added more contributions over the years, as have Zoltan
> All that said, if anyone has one of the Winkeyer USB models, I'd
> appreciate some testing.  A friend has been having trouble getting his
> to work with winkeydaemon and we've not gotten together to try
> troubleshooting it.

I can at least share that I use that winkeydaemon with a nanokeyer and it
works fine as described in https://idefix.net/~koos/newsitem.cgi/1567804130

I haven't gotten around to testing it with TLF, maybe there is some QRS CW
activity that I can participate in (also good to keep practising morse).

Koos PE4KH

-- 

Re: Using hamlib for CW keying

[Ervin Hegedüs]

hi Christian,

On Fri, Nov 22, 2019 at 12:19:29PM +0100, Christian Treldal wrote:
> Hi Ervin
> 
> Den 22.11.2019 kl. 09.49 skrev Ervin Hegedüs:
> >
> 
> >ohh... :)
> >
> >I found it in my Dropbox :P
> A memoryleak;-)

perfect description :)

> >Note, that I've tested now with both Python version (2 and 3). My
> >TRX doesn't support the CW keying via Hamlib (TS850 still), but I
> >could test it with the DUMMY RIG. Now it works as well, there
> >were an another necessary modification in line 25 (in old code).
> 
> 
> I just made a quick test with my KX3 and we are back in business

good to read :)
 
> Again thanks a lot Ervin, see you in the test

you're welcome,

I'll participate from our club station with call HG5C - see you
there! :)


73, Ervin