I havent looked at your syntorxgen source code. Do you derive the hex
> values from a formula or use a lookup table? I remember some SyntorX
> codeplug layout data on a site..Xbits something? that's gone now. I
> thinks Mike B. replicated the info on his site. I think maybe the
> DPL formula was in that info? I do know the CTCSS hex values are
> derived via formula.
The basic DPL code bits are simple. But there are three additional
mystery bits in the code plug. Syntorxgen now uses a formula to
calculate the proper values for those bits. It's not clear to me what
those bits do, other than being a pita. I had originally just set those
extra bits to zeros as suggested by Paul Kasley and Mike's code plug
info, then found that there were one or two types of radios (VX-5R, and
a Pacific Research repeater controller, iirc) that Didn't Like That
<tm>. I then experimentally* built a table (it's still in the source,
but no longer used) that mostly worked, and a few other folks (e.g. Andy
Brinkley) contributed some effort to find corrections. Eventually the
formula was worked out.
Paul's site is long gone, but Mike may have a copy at onfreq, and I
fished one out of the wayback machine for my Syntor X pages.
For CTCSS, the value is basically a multiplier or divider value.
Syntorxgen will let you set non-standard tones because it just does the
math. The code plug page gives you the bit patterns for the standard
tones.
De
* Yes, this was _exactly_ as fun as it sounds. 32 modes in a code plug
will hold all 8 possible mystery bit patterns for 4 DPL codes. Burn
EEPROM. Insert into radio. Select mode 1. Try a transmission. Try a
reception. Note results. Mode 2. Lather rinse repeat. Decide which
of multiple patterns opened the squelch _fastest_. There are, what,
~104 DPL codes? :)
