[aprssig] Ham Radio MOBILE Traveler PL-FIND device?
John D. Hays
john at hays.org
Wed Nov 29 13:16:55 CST 2017
In practical terms the frequency only goes out 3 digits either side of the
decimal point, which doesn't account for 6.25 or 12.5 Khz channel spacing,
plus the mode and access/signaling method. Also the FFF.FFFrx could be
used as input, but with greater resolution. Frequency must be hacked for
23cm and above, and the offset definition is limited.
If frequency, mode, and signaling could be fixed then it could be possible
to maintain. However, much of the specification is coded into commercially
manufactured radios. A new beacon type could be made more flexible and take
into account all of these parameters and the type of appliance to process
it and optionally control the radio could use it, without breaking current
On Wed, Nov 29, 2017 at 10:52 AM, Tom Hayward <esarfl at gmail.com> wrote:
> On Wed, Nov 29, 2017 at 9:35 AM, John D. Hays <john at hays.org> wrote:
>> I think a much better approach would be to use an improved beacon type.
>> The message should contain:
>> LAT/LONG (Approximate or Actual)
>> Output Freq: Mhz. with a minimum scale of up to 5 digits after the
>> decimal point (e.g. 440.00625)
>> Input Freq; Mhz. with a minimum scale of up to 5 digits after the decimal
>> point (e.g. 440.00625)
>> Mode(s): FM, NFM, D-STAR, DMR, Fusion, CODEC2, etc.
>> Input signalling: CTCSS: 123.0, DCS: 44, Color: 1, ...
>> Callsign: W1AW or "W1AW C", ...
>> Comment: Other information
> It's unclear to how this differs from the current spec:
> Are you just suggesting adding identifiers for the digital modes and their
> respective access control systems to this spec?
> Tom KD7LXL
John D. Hays
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aprssig