Yeah and will probably stay that way until the 700MHz sites are built out.
- Joined
- May 19, 2017
- Messages
- 609
PennDOT was doing radio checks early this morning around Pittsburgh before heading out, and someone was yelling and dropped an F-Bomb. Do they not realize that people listen to them, and that some people record transmissions from their scanners?
PennDOT's radio etiquette is awful. I hear that often.
Has there been any consideration to changing the format of the RR name format?
The current format makes using the Detailed Trunk Display mode on the SDS100 and I guess the SDS200 sort of useless. The most critical part of the Dept name is off the screen.
Dept of Conservation and Natural Resources - District 19 Talkgroups
If the naming convention was changed to my example below then life would be good.
District 19 Talkgroups Dept of Conservation and Natural Resources -
I could obviously do my own editing in Sentinel, but that defeats the Sentinel append feature which is nice to use as the system grows.
Also would it be possible to have the Tunnel TGs moved to their own Dept. Monitoring the Tunnels 24/7 provides quite a bit of interesting traffic. Having to monitor all of D11 to get the Tunnels is not as attractive.
Just thought I would throw it out their to see if others agree.
As I said I understand I can do these edits myself, but then append does not work properly when you start changing Dept name. Boy would it be nice if the Sites could also be appended.
The current format makes using the Detailed Trunk Display mode on the SDS100 and I guess the SDS200 sort of useless. The most critical part of the Dept name is off the screen.
Dept of Conservation and Natural Resources - District 19 Talkgroups
If the naming convention was changed to my example below then life would be good.
District 19 Talkgroups Dept of Conservation and Natural Resources -
I could obviously do my own editing in Sentinel, but that defeats the Sentinel append feature which is nice to use as the system grows.
Also would it be possible to have the Tunnel TGs moved to their own Dept. Monitoring the Tunnels 24/7 provides quite a bit of interesting traffic. Having to monitor all of D11 to get the Tunnels is not as attractive.
Just thought I would throw it out their to see if others agree.
As I said I understand I can do these edits myself, but then append does not work properly when you start changing Dept name. Boy would it be nice if the Sites could also be appended.
ka3aaa
Member
I edit almost everything to suite my preference which is what works for me because you can't please everyone all the time.
We have rules we are supposed to follow regarding naming. If anything, I would suggest just abbreviating to "DCNR District 19". However, the admin rulebook requires spelling out agency names. I personally find that problematic and shorten it all in my own scanners.
As far as the PennDOT Pittsburgh tunnels go, they are part of District 11. As has been suggested by others, customization is your friend. IF we move those, then it'll be "I only want to hear Somerset County PennDOT", "I only want to hear Chester County PennDOT". The district level splits provide a logical geographical division point.
And, yes, there are some abbreviations in use already (i.e. PEMA, PennDOT). Looking at similar state systems around the country, there seems to be a mix of long names and abbreviations...this is probably a topic that ought to be revisited behind the scenes. I'm just not sure I feel like taking up that banner since I can customize it to my liking in my own scanners. If subscribers want to lobby for it, have at it. I wouldn't do that in a state forum, though. The broader topic can be brought up in some of the site administration forums.
Rules are Rules. No problem. The topic requires no further discussion. Sort of makes the append function in Sentinel useless. The perfect solution would be if Sentinel matched TG#s instead of Dept Names during append.
RE: Site 1-038 INDI07 (Rossiter PA - Indiana Co)
Database shows:
The actual license shows :
151.235
151.4675 (recently changed from 151.34)
151.475
159.3225
Just wondering if 159.33 in the DB should actually be 159.3225. This was probably brought up before and probably already verified to be 159.33. But I'm just throwing it out there since they just updated a freq on the license and still show the 159 freq to be 159.3225. If somebody can monitor INDI07 and gather the latest freqs in use and compare to DB / submit changes if necessary, that'd be great.
Thanks
Mike
Database shows:
| 1 (1) | 038 (26) | Rossiter (INDI07) | Indiana | 151.235 | 151.475a | 159.330c |
The actual license shows :
151.235
151.4675 (recently changed from 151.34)
151.475
159.3225
Just wondering if 159.33 in the DB should actually be 159.3225. This was probably brought up before and probably already verified to be 159.33. But I'm just throwing it out there since they just updated a freq on the license and still show the 159 freq to be 159.3225. If somebody can monitor INDI07 and gather the latest freqs in use and compare to DB / submit changes if necessary, that'd be great.
Thanks
Mike
A closer look and this is WASH49 not INDI07. Looks like another trip is in store
Thanks Dan. I still appreciate you checking things out.
No problem. The database has the control channel for INDI07 as 159.3300 which appears to be in error. I reprogrammed to 159.3225 and went hill topping locally with no joy. Looks like a roadtrip is in my future plans, unless someone else can come up with the correct info in the meantime.
We can probably verify just by seeing what some peer of INDI07 says the CC is for INDI07. At any rate, I don't think it's extremely important -- not enough for a road tri. After all, anybody having 159.33 programmed in probably picks it up anyway. But I'd really like to know if it is supposed to be 159.3225 or 159.3325 or 159.33 for INDI07. So either somebody copying INDI07 directly and fetching all the control channel information would do, or somebody fetching the peer list (and CC) from a peer of INDI07 would do.
Thanks
Mike
To add to the confusion (mystery) here is a screen shot of CAMB02 showing INDI07 with a completely different control channel 151.4675
That actually solves the mystery, it doesn't add to the confusion. As @mtindor pointed out in his first post, 151.340 was recently changed out for 151.4675 at Site 38 (INDI07). The peer list for CAMB02 shows that the new frequency is in use as the active control channel.
Now that we have the correct control channel for INDI07. I made the adjustment here at the house and I am pleasantly surprised to find I have a solid signal for this site.
Thanks man. DB has been updated with regard to freqs and peers for 1-038.
It wouldn't surprise me that INDI07 would be wrong too, the same dyslexic that programmed WASH49 may well have mistyped 3225 as 3325 at both sites. Someone should watch the traffic channels at INDI07 and see.
I have been running Pro96Com on INDI07 for over 24 hours now and everything that is posted is correct. PennDot and PGC have been heavy users in this time frame.