next »

Version: 2.04
Radio: BCD396T
OS: XP SP2 using Chrome

When I import a LTR Multinet system, I correctly get a warning that the system may not be scannable (actually it's scannable conventionally, it just can't be trunktracked). When the import completes, the system is set to LTR (standard) which isn't correct. Try importing Chester County Pennsylvania's trunk system.

I wonder if the logic for warning on unmonitorable/untrunkable systems could be refined to change the result of the mapping. Specifically,

- For any pre-Phase 2 system, default it to P25. That is the mode that would result if a user affiliated with the system using a normal Phase 1 P25 radio anyway. The system would revert back to TDMA once the conversation is disconnected.

- For LTR Multinet/LTR Passport and MPT-1327, default it to a conventional system.

- These are more difficult - OpenSky, NexEdge, Mototrbo, IDEN, Pro-Voice, AEGIS are all unmonitorable as they use a modulation scheme that scanners can't decode. However, there is software called DSD being worked on that can handle NexEdge, Mototrbo and ProVoice. So I wonder if importing OpenSky, AEGIS and IDEN could be blocked completely, with the others loaded conventionally?

- For systems like Ocean City Maryland which are a mix of ProVoice and Analog, might it be possible to selectively block the digital talkgroups if requested? You already have this capability in the import for Moto talkgroups - it would simply be an extension of that logic if the system voice says 'ProVoice and Analog' in the database? I'd have to look for a system that has AEGIS and analog talkgroups, but the same logic applies.

Thanks  Mike

Those are interesting ideas but users get a nice warning when they attempt to do something the scanner can't do. I know LTR standard isn't the perfect choice, but if the scanner can't scan it, it might as well be any random system type. If it's not supported by the scanner and cannot be monitored, it is also considered advanced level to try and program it, so they should be able to figure it any details by themselves. The problem with importing these as conventional systems is that people will complain about all the talk groups not being imported even though they selected them. They will also not understand why it was imported as a conventional system when it is clearly a trunk system. It will be too confusing and the right answer isn't always the right choice.

Can you give a link to the Maryland system? I will check it out.

Here you go...

http://www.radioreference.com/apps/db/?sid=2554

Go down to the Ocean City poh-leece Talkgroups, and you'll see a couple of digital tgs. Also see the Worcester County Sheriff category further down the page. There's another talkgroup there that's evidently a ProVoice user.

Here's another example

http://www.radioreference.com/apps/db/?sid=513

In the Sheriff talkgroups, 02-043 is marked as ProVoice.

As for AEGIS/Analog systems, it seems that these talkgroups are marked 'encrypted' - so setting the 'don't import encrypted talkgroups' default to ON is appropriate...

http://www.radioreference.com/apps/db/?sid=388

See talkgroups 06-141, 02-082

Thanks...Mike

Here's another unmonitorable trunk type - I don't know if it's already in the list. This one is MotoTRBO...

http://www.radioreference.com/apps/db/?sid=1792

thanks...Mike

Thanks for the examples.. I have been quite busy the past while but I do plan to take a closer look at this.