Linux-Hams archive - June 1997: CW Ident.

CW Ident.

Alun ()
Mon, 9 Jun 1997 14:06:18 +0100

Hi all,

Recently, I discovered that my TNC, in KISS mode, doesn't do a CW beacon.
So, I hacked a little program that sent raw KISS data to the TNC, with byte
patterns that would sound like CW when transmitted. This worked OK, or so I
thought. However, it turns out that other people are seeing spurious
callsigns in their mheard lists, due to this data. I don't quite understand
how this can be, since I'm not creating a header, or calculating a checksum
on it, but anyway, it's happening.

My latest solution has been to send these byte sequences in a set of UI
frames. But of course, these are showing up in everyone's monitors, and the
frame headers are causing glitches in the sound of the CW.

I wonder, has anyone else approached this problem and come up with a
sensible solution. Alternatively, is there a TNC2 Eprom image I can get
which does CW Ident even when in KISS mode. Finally, wouldn't it be quite
nice to have an extra KISS command which would cause the TNC to send a piece
of text as CW?

All speculation, but I'm interested in hearing what people can suggest. In
particular, how come the transmitted raw KISS packets are showing up in
mheard lists?

Alun, GW1URF

6 6 scale .2 setlinewidth 1 .7 0 setrgbcolor{}forall N G G I 0 U N E E E E E
I 1 U N E E E gsave I grestore 0 U n .3 U N E E n 1 0 360 arc I showpage%auj