Re: Hamlib keying?

[Martin Kratoska]

Oh, it is Elecraft K4.

73 m.

Dne 29. 10. 24 v 14:31 Thomas Beierlein napsal(a):
> Hi,
>
> in meantime I had a chance to check the report. Tested it with my
> TS-590 and an IC-705.
>
> I have to confirm your observations with the TS-590. After each single
> sent bunch of characters there is an additional space inserted. That
> affects the mentioned AUTOSEND function as well as the Ctrl-K keyer
> window.
>
> Doing the same tests with the Icom rig shows no problems - it works as
> expected.
>
> Maybe you can tell us which kind of rig is in use on your side.
>
> Digging deeper It looks as the Hamlib implementation of the
> kenwood_send_morse() may be the problem. Kenwood rigs expects morse
> text as packets with fixed length of 24 characters. So the mostly
> shorter characters packets sent to the rig has to be padded by
> spaces. At the moment the padding follows the text - that seems to
> result in at least one additional space character sent. No idea what
> happens if we prepend the text with spaces.
>
> 73, de Tom DL1JBE
>
> Am Tue, 22 Oct 2024 18:28:58 +0200
> schrieb Martin Kratoska <martin@ok1rr.com>:
>
> > Yes, HAMLIB_KEYER is the solution!
> >
> > But when AUTOSEND is on, the spaces between characters with
> > HAMLIB_KEYER are incorrect (stretched, very long) from the character
> > corresponding to the AUTOSEND setting.
> >
> > Example: IK3VUT -> AUTOSEND set to start transmission at the fourth
> > character (ie after IK3V) - IK3V is sent correctly, the space between
> > V and U is already stretched (elongated), between U and T is
> > stretched even more. Is it a buffer problem?
> >
> > 73,
> > Martin, OK1RR
> >
> >
> > Dne 17. 10. 24 v 6:47 Thomas Beierlein napsal(a):
> > > Back to the original question:
> > >
> > > You can use 'HAMLIB_KEYER' instead of 'NETKEYER' in logcfg.dat.
> > >
> > > There are some limitations due to hamlibs implementation:
> > >
> > > * Not all rigs support early stop of CW messages. You will get an
> > >     information during startup if that is the case.
> > > * Changing key speed while sending is not supported. Also no
> > >     embedded '+++' or '...' to speed up and down parts of the
> > > message. But you can change the speed between messages.
> > >
> > > 73, de Tom DL1JBE
> > >
> > > Am  Wed, 16 Oct 2024 20:23:57 +0200 schrieb Martin Kratoska
> > >     <martin@ok1rr.com>:
> > >      
> > > > Hi,
> > > >
> > > > is there a possibility to use Hamlib keying?
> > > >
> > > > I have been facing problems with port numbering for a long time
> > > > both in Windows (tried 10 and 11) and in Linux (kernel:
> > > > 6.8.0-45-generic; arch: x86_64 bits: 64; compiler: gcc v: 13.2.0 ;
> > > > clocksource: hpet; tk: v: 6.2.0; vt: 1.30.0; distro: Linux Mint 22
> > > > base: Ubuntu 24.04 noble).
> > > >
> > > > COM6 suddenly becomes COM3, /dev/ttyUSB0 changes to /dev/ttyUSB1,
> > > > etc. (badly formatted in my previous posting)
> > > >
> > > > I've tried everything from upgrading drivers to different settings,
> > > > turning off power management, in Linux /udev/ rules. Nothing
> > > > helps. I replaced the whole computer, that didn't help either.
> > > >
> > > > This is not the first time this problem has happened, it always
> > > > lasted for a few weeks and then disappeared without any
> > > > intervention from me.
> > > >
> > > > Although I am a fairly experienced software engineer and computer
> > > > technician (practice since 1996 - one of the authors of CQRlog for
> > > > Linux, translator of the Kicad EDA system into Czech and a number
> > > > of smaller projects), I have not yet been able to find the cause
> > > > of this phenomenon, because of which I had to give up several
> > > > contests.
> > > >
> > > > I would be interested in your experiences.
> > > >
> > > > 73,
> > > > Martin, OK1RR
> > > >     
> > >
> > >
> > >      
> >