next »

- Can the new Phase 2 P25 systems be added to the RR trunk import warning about non-scannable systems? Here are 2 examples;
 
http://www.radioreference.com/apps/db/?sid=6341
 
http://www.radioreference.com/apps/db/?sid=6524
 
 
- Can the warning be modified slightly to mention that these system types cannot be trunktracked but can be monitored conventionally? These would be LTR Multinet, LTR Passport and MPT-1327 and examples follow
 
http://www.radioreference.com/apps/db/?sid=987
(LTR Multinet)
 
http://www.radioreference.com/apps/db/?sid=7019
(LTR Passport)
 
http://www.radioreference.com/apps/db/?sid=4393
(MPT-1327)

It's probably too difficult to reroute these system types from importing to a trunked form, but how about modifying the target form so that folks that do import these types end up with a conventional, rather than a trunked system?

Thanks and have a nice Xmas if I don't hear from you before then...Mike

Thanks for letting me know about the issue with the P25 P2 systems - I'll make the update so a warning pops up.

But  I cannot make FS manhandle an untrackable trunked system into a conventional one. I just think it would be a mess to do it that way. They get their warning that the scanner isn't compatible with these systems, and what the user does afterwards is his business. If they want to scan those systems conventionally I think it is more something that advanced users could do. I don't think its really FS's job to cater to those type of edge scenarios.

OK I thought it might be too difficult to do, but hey it was worth a try

Can you at least modify that warning message about those 3 system types not being scannable? It's not correct - LTR MultiNet, Passport and MPT-1327 can't be trunktracked, but can be scanned conventionally.  The others (i.e. Open Sky, NXDN) can't even be scanned because they use a protocol that isn't supported.

Thanks...Mike

I'll look into rewording that warning.