There’s a wider range than that available in KW software:
Fleet:
ID:
Fleetsync does have individual and group calling, which may be the “talkgroups” in SDRTrunk.
From: sdrt...@googlegroups.com <sdrt...@googlegroups.com> On Behalf Of cortland...@gmail.com
Sent: Thursday, April 24, 2025 4:21 PM
To: sdrtrunk <sdrt...@googlegroups.com>
Subject: Re: FleetSync Identifiers
It appears that the max you can go is 127 on the prefix, so trying to put in 222 it won't let you. Denny would probably have to modify it to allow that high.
On Thursday, April 24, 2025 at 7:22:19 AM UTC-4 davidtho...@gmail.com wrote:
OK, but how do I get SDRTrunk to accept the correct ID? It is forcing IDs like 222-0019 to 022-0019.
On Thursday, April 24, 2025 at 3:02:50 AM UTC-4 sdrtrunk wrote:
For Fleetsync, use the talkgroup as the radio identifier.
On Friday, April 18, 2025 at 3:53:15 AM UTC-4 davidtho...@gmail.com wrote:
The information on GitHub indicates that it is possible to add FleetSync unit identifiers. Version 0.6.1 does not appear to support this, at least not as described on GitHub. The only things that can be added are Aliases, and the only options under the FleetSync protocol menu are Talkgroup and Talkgroup Range. AFAIK, FleetSync doesn't have talkgroups.
Also, when I try to add identifiers that have been logged, SDRTrunk's editor does not permit the prefix that I am receiving. I am seeing IDs such as 222-0019, but the editor forces 022-2019.
--
You received this message because you are subscribed to the Google Groups "sdrtrunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sdrtrunk+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sdrtrunk/587366d7-4231-4d28-9398-ee7c9d396302n%40googlegroups.com.