[Hamlib-developer] DCS, TONE, CTCSS, 1750; Who knows what else...

[Dale E. E. <de...@w-...>]

Robert,

On the U.S.A. version of the TS-2000 the 1750 Hz tone to
open the repeater is an option you may enable using the
menu.  Here in the Washington State I don't know of any
repeater that uses it.  Likewise, I don't know of any repeater
that uses DCS, or CTCSS.  All the repeaters I've accessed
use only "Tone" and fail to work if you use CTCSS or DCS.

To my limited knowledge, CTCSS is a Motorola proprietary
format for tone encoding.  (Don't quote me.)  As far as the
+/-600kHz offset for TX/RX when accessing the repeater
that I believe is identical in all systems.  The exact shift used
may vary somewhat but otherwise is the same.

When I select tone the ts2k displays 'T'.  When I select
CTCSS the rig displays "CT", and for DCS it displays
"DCS".  Only one may active at a time but always have
a value if read.

Thanks for your info on the 1750Hz.  I think I under-
stand now.  (Not really, but hopefully enough to kill
this issue.)

As far as the 1750Hz initiation/activation pulse I'm
beginning to suspect that it is an issue that is transparent to
the operator of any rig.  The only time it will  be an issue
if the rig is transported to another country.  Since this is
a menu item, let's make it go away by leaving it to the
menu unless somebody knows a reason to do otherwise.

The ts2k does "lock" a memory.  But when it is locked it
only "skips" it on scans but it can be deleted (as I found
out).

My reasoning for Hamlib performing the lock is that a
particular application may not understand or care about
my desire to have certain memories untouched.  Just like
the Linux kernel enforcing read-only file protection, I
feel Hamlib should perform more than just reading the
rig.  I don't want to take this too far, but I think we should
make provisions for it.  Also, it is not something that I am
expecting to be functional real soon.  Too much other
stuff going on...

73's

Dale