cpetraglia
Member
I have monitored with Pro96Com for the past 3 hours. 200-300 hits and no encryption. This here in N.VA.
BCD436HP and VSP
- Thread starter fredva
- Start date
- Status
Well, I set the P25 Threshold level on the two STARS sites to Manual 7 yesterday and Manual 6 today. It seems like that helped a little. I get traffic from the Thornburg tower up to a certain distance away from it. However, I get very little, if anything from the Edgehill tower even when I'm in close proximity to it. My settings for both towers are identical. I can't really explain it, unless there is something wrong with the tower itself. Next week, I will see what my PRO-18 does. It's always received both towers fairly well in the past.
Try making a favorites list with all sites set to avoid other than a specific site you want to monitor. See if that helps. I have specific sites for driving to work in a favorites list and a separate favorites list for driving throughout VA.
Sent from my SM-G930V using Tapatalk
Sent from my SM-G930V using Tapatalk
Mike, if I understand you correctly, that's basically what I've been doing. I have all the sites in a Favorites List, but I've had all of them avoided except for the two sites in the vicinity of my home and workplace. I have other systems in that Favorites List, and I receive them pretty well.
I've taken my PRO-18 on my commute the last couple of days, and it has received the two STARS sites as it normally does. I've tweaked the thresholds on my 436hp again, and I plan to take it with me sometime soon and see how it does. It seems to receive the nearest site fairly well now at the house. It's the second site closer to my work that it has struggled the most with.
Thanks for the suggestion.
BushDoctor
Member
[Be sure hogback site is programed into ur scanner
QUOTE=fredva;2559452]For the last couple of days, I've been trying to monitor VSP on STARS in my area with my 436hp. However, after around four hours of listening, I've only caught a VDOT unit on I-66. I appear to be getting a good signal from the local towers, but I'm not catching the talkgroups. I started out with just two VSP dispatch talkgroups and two towers. When I didn't receive anything, I programmed in all the talkgroups on the system, with those same two towers. That's when I received a VDOT unit briefly, but nothing else.
I've also tried using the zip code scanning for a little while, but still didn't get anything from STARS.
I have no trouble getting STARS on my PRO-18.
I receive local trunking systems just fine. Any ideas on what I might be doing wrong with STARS? It's a multi-site system, which might make a difference.[/QUOTE]
QUOTE=fredva;2559452]For the last couple of days, I've been trying to monitor VSP on STARS in my area with my 436hp. However, after around four hours of listening, I've only caught a VDOT unit on I-66. I appear to be getting a good signal from the local towers, but I'm not catching the talkgroups. I started out with just two VSP dispatch talkgroups and two towers. When I didn't receive anything, I programmed in all the talkgroups on the system, with those same two towers. That's when I received a VDOT unit briefly, but nothing else.
I've also tried using the zip code scanning for a little while, but still didn't get anything from STARS.
I have no trouble getting STARS on my PRO-18.
I receive local trunking systems just fine. Any ideas on what I might be doing wrong with STARS? It's a multi-site system, which might make a difference.[/QUOTE]
An update: I programmed in the voice frequencies for the two STARS towers as conventional P25 and I'm hearing a lot more traffic now. So I assume the scanner is struggling to decode the control channel when it is trying to monitor STARS as a trunked system. I've tried various P25 threshold settings working down from 8 to 3, but that didn't help. Perhaps there are other settings that might make a difference. I need to do some more reading on the various options. I knew attentuation is one I haven't tried yet, but might.
prthorsenjr
Member
I've always wondered why I can hear Fairfax, Richmond, Salem, Appomattox, Culpeper, etc., but never hear anything at all from Norfolk, Hampton, Newport News or Virginia Beach?
Pete
Pete
I seriously doubt it is having trouble decoding the control channel as that is the one commonality among these P25 systems, it is the voice channels that can throw a curveball at the scanner. It is highly likely that you have simply told the scanner not to hear the desired transmissions due to the apparently complex user interface of the thing. (And here Uniden is selling this is an easier alternative I thought.)
The fact that you can hear the voice channels fine when programmed in as conventional frequencies tells me that you don't need the attenuator, you just need to tell the scanner that you really, really want to hear those talkgroups when the system grants them to a user.
I think for your tests you should just open it up wide to hear as much as possible to discover what it CAN hear, then pare it down to what you want to hear once you have proven that it can receive it OK. Clear all the avoids/lockouts, open up every last talkgroup, quick key, everything, and then monitor in those trouble spots to note any changes.
I stick with the old skool design in the 996XT and 996P2 to minimize complexity, so I can't advise how to do that on the HP series of scanners; it seems they have so many, many ways to lock out traffic that you can easily paint yourself into a corner and not hear anything.
Maybe another pass through the manual or that guy's Easy Guide site to discover some feature that you've previously overlooked might help?
Bote, thanks for the input. I tried the attentuation and all that gave me was complete silence from both of the local towers.
I've also tried an id search, which is basically opening up all the talkgroups, and I didn't receive any more transmissions than I had been.
I'm a little short on time right now, but with the programming I have done, I can receive STARS in trunked mode in certain locations but not in others where I would expect to hear it.
I've also tried an id search, which is basically opening up all the talkgroups, and I didn't receive any more transmissions than I had been.
I'm a little short on time right now, but with the programming I have done, I can receive STARS in trunked mode in certain locations but not in others where I would expect to hear it.
W4UVV
Member
A few comments which may or may not be of interest
---------------
I have the 536 and just returned from a trip this past week to near Charlotte, NC then Bristol, VA and back home to Prince George Co, VA. A few comments are offered which may or may not help your situation.
First all FYI STARS mobiles operating only in Division 4 near the KY and WVA state lines are limited to 50 watts max ERP. This is because "legacy" licensees in these two states are afforded FCC protection to possible interference and the WVA "quiet zone". I think you are located in the eastern part of the state and interested in STARS Division 2 monitoring. I suspect Div 2 STARS sites located close to the state line have had their antenna arrays phased to minimize signal strengths to the northern direction.
I have Uniden 996XTs and my 536 programed for the entire state of VA. I used Butel ARC XT PRO to program the 996XTs easily with no problems. As for the 536, it seems Uniden does not adhere to consistently between the two models. The 996XT uses System Quick Keys but the 536 requires "Favorite Lists....basically the same thing. It uses "avoid" instead of "temporary/permanent lockout", etc....ridiculous.
I use Butel ARC536PRO to program my 536 which works great. It also supports the 436. It requires only one FL to bypass the Sentinel Software mess with limited user editing functions (It reminds me of the MS DOS days).
I used GPS controlled scanning on my recent trip. The 996XT GPS gives visual and audio alerts when locking out and unlocking a pre-defined radio system and offers virtual control displays. The 536 does not. The 996XT supports PRO96COM. The 436/536 does not.
I had excellent reception within my mobile range on all STARS repeaters in Div 3, 4, 5 and 6 with both scanners receiving the same detected signal almost simultaneously. Some mountaintop repeaters located in Divs 4 and 6 were additionally affiliated with both VSP divisions.
This may be a stupid question but have you ensured "Location Control" has been deselected?
FYI here is how I programed STARS Division 2 in my 536:
1. I created a Favorites List(FL) (System Level) for STARS Division 2.
2. I created a Department level (Site level) for each Division 2 site and entered all of the voice repeater frequencies including, of course, the primary and alternate ccs. This is a personal preference of mine and requires only the ccs hoping the techs don't change the primary cc.
3. For the Channel Level I created only one which included all, yest all, talkgroups appropriate to that division plus other selected talkgroups from adjacent divisions which typically are affiliated with STARS Division 2.
I frequently sight checked my 536 entries to confirm that the correct FL number matches the FL number I assigned and each FL contains only one STARS division. I programed all 7 VSP divisions the same way with each STARS division having its' appropriate frequencies and talkgroups.
I also entered GPS information using the "circle" option giving latitude/longitude and the radius distance I wanted to monitor a specific department within appropriate division FL.
With all the potential file conflicts which are possible in file content/naming issues which might occur in the 536, I decided very early not to attempt manually to program the scanner.
Maybe there is some different free software you can try to help resolve your issues. It sounds like something still is not correct obviously but whatever is enough to cause you a lot of frustration.
John
W4UVV
---------------
I have the 536 and just returned from a trip this past week to near Charlotte, NC then Bristol, VA and back home to Prince George Co, VA. A few comments are offered which may or may not help your situation.
First all FYI STARS mobiles operating only in Division 4 near the KY and WVA state lines are limited to 50 watts max ERP. This is because "legacy" licensees in these two states are afforded FCC protection to possible interference and the WVA "quiet zone". I think you are located in the eastern part of the state and interested in STARS Division 2 monitoring. I suspect Div 2 STARS sites located close to the state line have had their antenna arrays phased to minimize signal strengths to the northern direction.
I have Uniden 996XTs and my 536 programed for the entire state of VA. I used Butel ARC XT PRO to program the 996XTs easily with no problems. As for the 536, it seems Uniden does not adhere to consistently between the two models. The 996XT uses System Quick Keys but the 536 requires "Favorite Lists....basically the same thing. It uses "avoid" instead of "temporary/permanent lockout", etc....ridiculous.
I use Butel ARC536PRO to program my 536 which works great. It also supports the 436. It requires only one FL to bypass the Sentinel Software mess with limited user editing functions (It reminds me of the MS DOS days).
I used GPS controlled scanning on my recent trip. The 996XT GPS gives visual and audio alerts when locking out and unlocking a pre-defined radio system and offers virtual control displays. The 536 does not. The 996XT supports PRO96COM. The 436/536 does not.
I had excellent reception within my mobile range on all STARS repeaters in Div 3, 4, 5 and 6 with both scanners receiving the same detected signal almost simultaneously. Some mountaintop repeaters located in Divs 4 and 6 were additionally affiliated with both VSP divisions.
This may be a stupid question but have you ensured "Location Control" has been deselected?
FYI here is how I programed STARS Division 2 in my 536:
1. I created a Favorites List(FL) (System Level) for STARS Division 2.
2. I created a Department level (Site level) for each Division 2 site and entered all of the voice repeater frequencies including, of course, the primary and alternate ccs. This is a personal preference of mine and requires only the ccs hoping the techs don't change the primary cc.
3. For the Channel Level I created only one which included all, yest all, talkgroups appropriate to that division plus other selected talkgroups from adjacent divisions which typically are affiliated with STARS Division 2.
I frequently sight checked my 536 entries to confirm that the correct FL number matches the FL number I assigned and each FL contains only one STARS division. I programed all 7 VSP divisions the same way with each STARS division having its' appropriate frequencies and talkgroups.
I also entered GPS information using the "circle" option giving latitude/longitude and the radius distance I wanted to monitor a specific department within appropriate division FL.
With all the potential file conflicts which are possible in file content/naming issues which might occur in the 536, I decided very early not to attempt manually to program the scanner.
Maybe there is some different free software you can try to help resolve your issues. It sounds like something still is not correct obviously but whatever is enough to cause you a lot of frustration.
John
W4UVV
I started out with Location control turned off, turned it on, and then turned it back off. The results were the same.
Originally, I loaded a Favorites List with STARS data from the database. When I wasn't hearing much on my commute, I programmed the two local sites manually in a different Favorites List, in case there was something corrupted about the database download. No difference.
John, I suspect one difference between the experience you had driving through the state and me is that you are most likely using an external antenna on your vehicle. I am not. For some time, I've been taking my PRO-18, usually with a telescoping antenna on the scanner, in whichever vehicle I am driving. And except for a local LSM simulcast system, it has received reasonably well. Whether not having an antenna mounted to the outside of the vehicle is relevant to the problem with the 436, I don't know.
Originally, I loaded a Favorites List with STARS data from the database. When I wasn't hearing much on my commute, I programmed the two local sites manually in a different Favorites List, in case there was something corrupted about the database download. No difference.
John, I suspect one difference between the experience you had driving through the state and me is that you are most likely using an external antenna on your vehicle. I am not. For some time, I've been taking my PRO-18, usually with a telescoping antenna on the scanner, in whichever vehicle I am driving. And except for a local LSM simulcast system, it has received reasonably well. Whether not having an antenna mounted to the outside of the vehicle is relevant to the problem with the 436, I don't know.
W4UVV
Member
For what it's worth....
Mike,
Don't give up yet. If you are getting 4 or 5 signal strength bars on the target site's primary control channel, to me that indicates a programing issue or incorrect setting which will come as no surprise. I can relate to your frustration. In the past years I have had my scanner frustrations even with the 536. While attempting initially to program my 536 to specifically id the active FL STARS division site at the moment specifically mated to the active talkgroup, I used a scheme which required the FL to exceed 1MB. It was inefficient programing but it worked. This FL file size limitation was not documented in the user manual and resulted with me having to reprogram using a less desirable scheme. Subsequently, I discovered somebody at Uniden decided to put a maximum file size of 1MB on a FL. Why? Because nobody in the world would ever need more than 1MB FL size. That's nobody except me. I got the usual grief from the "experts" which I ignored. In my opinion, if the scanner is advertised as a DMA scanner as long as the total memory capacity for FL related files creations are not exceeded, then the scanner is not a true DMA scanner. So, don't feel alone with unexpected frustrations.
You basically are correct regarding my mobile antenna setup for monitoring. I use separate vhf and uhf approximately 5/8 wavelengths mag mount antennas roof mounted. Each antenna's output separately is inputted to a Blonder-Tongue(BT) vhf and uhf BT cable tv amplifier respectively and DC powered from the BT 115VAC power supply. I use a 300 watt 12VDC to 115AC inverter dedicated to the configuration.
You probably already "have been down this road" a number of times but for what its' worth:
Following are my entries for STARS Div 2 in my 536 which work.
"Set Scan Selection" "Manage Quick Key Status" "Favorite Quick Key" FL-2 STARS DIV 2-CULPEPER " = "On".
"Set Scan Selection" "Select Lists to Monitor" "Select Lists to Monitor" "FL-2 STARS DIV 2-CULPEPER" = "On".
"Manage Favorites" "Select Favorites" = "FL-2 STARS DIV 2-CULPEPER"
For my ARC536PRO programed settings:
Favorite List Level:
"FL-2 STARS DIV-2 CULPEPER"
"System Type" = "P25 Standard"
"ID Search" = "On"
"P25 NAC" "Search"
(All other fields at the FL level are left blank)
Department Level: (Hogback Mtn.....1 of 7 STARS sites listed)
"DL-2 SITE 108-HOGBACK MTN."
Trunked Frequencies:
Mhz.
0151.3625
0151.3925
0152.2175
0159.0075
0159.1275
0159.2325
0159.3825
0161.8500
0161.8875
0161.9000
Talkgroups:
(Only 100 of 434 talkgroups for Div 2 only listed)
20 CUL VSP DIV 2 TAC 2
21 CUL VSP DIV 2 UNKNOWN USE
22 CUL VSP DIV 2 BLUE 2
23 CUL DIV 2 ANNOUNCEMENT 2
24 CUL VSP DIV 2 UNKNOWN USE
25 CUL VSP DIV 2 GIS 2
26 CUL VSP DIV 2 UNKNOWN USE
27 CUL DIV 2 DRUG ENFORCE SECTION 2
28 CUL VSP DIV 2 CCI SURVEILLANCE 2E
29 CUL VSP DIV 2 CCI SURVEILLANCE 2A
30 CUL VSP DIV 2 CCI SURVEILLANCE 2B
31 CUL VSP DIV 2 CCI SURVEILLANCE 2C
32 CULPEPER VSP DIV 2 TAC TEAM 2
33 APMTX DIV 3 CHANNEL 1 DISPATCH
34 APPOMATTOX VSP DIV 3 TAC 1
35 APMTX DIV 3 CHANNEL 2 DISPATCH
36 APPOMATTOX VSP DIV 3 TAC 2
38 APPOMATTOX VSP DIV 3 BLUE 3
44 APMX VSP DIV 3 CCI SURVEILLANCE 3E
45 APMX VSP DIV 3 CCI SURVEILLANCE 3A
46 APMX VSP DIV 3 CCI SURVEILLANCE 3B
47 APMX VSP DIV 3 CCI SURVEILLANCE 3C
48 APMX VSP DIV 3 TAC TEAM 3
65 FFX VSP DIV 7 CHANNEL 1 DISPATCH
66 FAIRFAX VSP DIV 7 TAC 1
67 FFX VSP DIV 7 CHANNEL 2 DISPATCH
68 FAIRFAX VSP DIV 7 TAC 2
69 FAIRFAX VSP DIV 7 UNKNOWN USE
70 FAIRFAX VSP DIV 7 BLUE 7
71 FAIRFAX VSP DIV 7 ANNOUNCEMENT 7
72 FAIRFAX VSP DIV 7 UNKNOWN USE
73 FAIRFXX VSP DIV 7 GIS 7
74 FAIRFAX VSP DIV 7 UNKNOWN USE
75 FFX DIV 7 DRUG ENFORCE. SECTION 7
76 FAIRFAX DIV 7 CCI SURVEILLANCE 7E
77 FAIRFAX DIV 7 CCI SURVEILLANCE 7A
78 FAIRFAX DIV 7 CCI SURVEILLANCE 7B
79 FAIRFAX DIV 7 CCI SURVEILLANCE 7C
80 FAIRFAX VSP DIV 7 TAC TEAM 7
81 FAIRFAX VSP DIV 7 CCI SURVEILLANCE
82 STARS ALL
83 ALL DIV AVIATION
84 VSP EPU 1 (ALL DIV)
85 VSP GOVERNOR'S PROTECTION
86 VSP MANAGEMENT 1
96 RIC VSP DIV 1 STATE FAIR
98 CUL VSP DIV 2 TAC
101 UNKNOWN USE
107 RM CH. H/11/AGEE
110 VSP/EPU VEST
729 UNKNOWN USE
750 UNKNOWN USE
1153 UNKNOWN USE
1507 STAUNTON ABC REGION 3 OPERATIONS
1508 STAUNTON ABC REGION 3 TAC
1512 ALEXANDRIA ABC REGION 4 OPS..
1513 ALEXANDRIA ABC REGION 4 TAC
1515 ALEXANDRIA ABC REGION 4 SURVEIL.
1517 FREDERICKSBURG ABC REGION 5 OPS.
1518 FREDERICKSBURG ABC REGION 5 TAC
1522 RICHMOND ABC REGION 6 OPS.
1523 RICHMOND ABC REGION 6 TAC
1524 RICHMOND ABC REGION 6 SURVEIL.
1525 RICHMOND ABC REGION 6 SURVEIL.
1804 CAPITOL POLICE OPERATIONS 1
1805 CAPITOL POLICE TAC 1
1806 CAPITOL POLICE FOX 1
1807 CAPITOL POLICE RED 1
2004 DCR DISTRICT 5 LE-5
2005 DCR DISTRICT 5 LE-5A
2006 DCR DISTRICT 5 LE-5B
2009 DCR DISTRICT 5 RED 5
2013 DCR DISTRICT 1 LE-1
2014 DCR DISTRICT 1 TAC
2016 DCR DISTRICT 1 LE-1A
2017 DCR DISTRICT 1 LE-1B
2018 DCR DISTRICT 1 RED 1
2024 DCR DISTRICT 1 UNKNOWN USE
2026 DCR DISTRICT 1 UNKNOWN USE
2027 DCR DISTRICT 1 UNKNOWN USE
2030 DCR DISTRICT 1 UNKNOWN USE
2038 DCR DISTRICT 3 LE-3
"Modulation" = "NFM"
"MoT Bandplan" = "Standard"
"P25 Waiting" = 400
"P25 Threshold Mode" = "Auto"
"P25 Threshold Level " = "8"
"Site Location"
"Location Type" "Circle"
"Latitude" = "38.924956"
"Longitude" = "-78.184411
"Range" = "125" (Miles)
------------------
John
W4UVV
Mike,
Don't give up yet. If you are getting 4 or 5 signal strength bars on the target site's primary control channel, to me that indicates a programing issue or incorrect setting which will come as no surprise. I can relate to your frustration. In the past years I have had my scanner frustrations even with the 536. While attempting initially to program my 536 to specifically id the active FL STARS division site at the moment specifically mated to the active talkgroup, I used a scheme which required the FL to exceed 1MB. It was inefficient programing but it worked. This FL file size limitation was not documented in the user manual and resulted with me having to reprogram using a less desirable scheme. Subsequently, I discovered somebody at Uniden decided to put a maximum file size of 1MB on a FL. Why? Because nobody in the world would ever need more than 1MB FL size. That's nobody except me. I got the usual grief from the "experts" which I ignored. In my opinion, if the scanner is advertised as a DMA scanner as long as the total memory capacity for FL related files creations are not exceeded, then the scanner is not a true DMA scanner. So, don't feel alone with unexpected frustrations.
You basically are correct regarding my mobile antenna setup for monitoring. I use separate vhf and uhf approximately 5/8 wavelengths mag mount antennas roof mounted. Each antenna's output separately is inputted to a Blonder-Tongue(BT) vhf and uhf BT cable tv amplifier respectively and DC powered from the BT 115VAC power supply. I use a 300 watt 12VDC to 115AC inverter dedicated to the configuration.
You probably already "have been down this road" a number of times but for what its' worth:
Following are my entries for STARS Div 2 in my 536 which work.
"Set Scan Selection" "Manage Quick Key Status" "Favorite Quick Key" FL-2 STARS DIV 2-CULPEPER " = "On".
"Set Scan Selection" "Select Lists to Monitor" "Select Lists to Monitor" "FL-2 STARS DIV 2-CULPEPER" = "On".
"Manage Favorites" "Select Favorites" = "FL-2 STARS DIV 2-CULPEPER"
For my ARC536PRO programed settings:
Favorite List Level:
"FL-2 STARS DIV-2 CULPEPER"
"System Type" = "P25 Standard"
"ID Search" = "On"
"P25 NAC" "Search"
(All other fields at the FL level are left blank)
Department Level: (Hogback Mtn.....1 of 7 STARS sites listed)
"DL-2 SITE 108-HOGBACK MTN."
Trunked Frequencies:
Mhz.
0151.3625
0151.3925
0152.2175
0159.0075
0159.1275
0159.2325
0159.3825
0161.8500
0161.8875
0161.9000
Talkgroups:
(Only 100 of 434 talkgroups for Div 2 only listed)
20 CUL VSP DIV 2 TAC 2
21 CUL VSP DIV 2 UNKNOWN USE
22 CUL VSP DIV 2 BLUE 2
23 CUL DIV 2 ANNOUNCEMENT 2
24 CUL VSP DIV 2 UNKNOWN USE
25 CUL VSP DIV 2 GIS 2
26 CUL VSP DIV 2 UNKNOWN USE
27 CUL DIV 2 DRUG ENFORCE SECTION 2
28 CUL VSP DIV 2 CCI SURVEILLANCE 2E
29 CUL VSP DIV 2 CCI SURVEILLANCE 2A
30 CUL VSP DIV 2 CCI SURVEILLANCE 2B
31 CUL VSP DIV 2 CCI SURVEILLANCE 2C
32 CULPEPER VSP DIV 2 TAC TEAM 2
33 APMTX DIV 3 CHANNEL 1 DISPATCH
34 APPOMATTOX VSP DIV 3 TAC 1
35 APMTX DIV 3 CHANNEL 2 DISPATCH
36 APPOMATTOX VSP DIV 3 TAC 2
38 APPOMATTOX VSP DIV 3 BLUE 3
44 APMX VSP DIV 3 CCI SURVEILLANCE 3E
45 APMX VSP DIV 3 CCI SURVEILLANCE 3A
46 APMX VSP DIV 3 CCI SURVEILLANCE 3B
47 APMX VSP DIV 3 CCI SURVEILLANCE 3C
48 APMX VSP DIV 3 TAC TEAM 3
65 FFX VSP DIV 7 CHANNEL 1 DISPATCH
66 FAIRFAX VSP DIV 7 TAC 1
67 FFX VSP DIV 7 CHANNEL 2 DISPATCH
68 FAIRFAX VSP DIV 7 TAC 2
69 FAIRFAX VSP DIV 7 UNKNOWN USE
70 FAIRFAX VSP DIV 7 BLUE 7
71 FAIRFAX VSP DIV 7 ANNOUNCEMENT 7
72 FAIRFAX VSP DIV 7 UNKNOWN USE
73 FAIRFXX VSP DIV 7 GIS 7
74 FAIRFAX VSP DIV 7 UNKNOWN USE
75 FFX DIV 7 DRUG ENFORCE. SECTION 7
76 FAIRFAX DIV 7 CCI SURVEILLANCE 7E
77 FAIRFAX DIV 7 CCI SURVEILLANCE 7A
78 FAIRFAX DIV 7 CCI SURVEILLANCE 7B
79 FAIRFAX DIV 7 CCI SURVEILLANCE 7C
80 FAIRFAX VSP DIV 7 TAC TEAM 7
81 FAIRFAX VSP DIV 7 CCI SURVEILLANCE
82 STARS ALL
83 ALL DIV AVIATION
84 VSP EPU 1 (ALL DIV)
85 VSP GOVERNOR'S PROTECTION
86 VSP MANAGEMENT 1
96 RIC VSP DIV 1 STATE FAIR
98 CUL VSP DIV 2 TAC
101 UNKNOWN USE
107 RM CH. H/11/AGEE
110 VSP/EPU VEST
729 UNKNOWN USE
750 UNKNOWN USE
1153 UNKNOWN USE
1507 STAUNTON ABC REGION 3 OPERATIONS
1508 STAUNTON ABC REGION 3 TAC
1512 ALEXANDRIA ABC REGION 4 OPS..
1513 ALEXANDRIA ABC REGION 4 TAC
1515 ALEXANDRIA ABC REGION 4 SURVEIL.
1517 FREDERICKSBURG ABC REGION 5 OPS.
1518 FREDERICKSBURG ABC REGION 5 TAC
1522 RICHMOND ABC REGION 6 OPS.
1523 RICHMOND ABC REGION 6 TAC
1524 RICHMOND ABC REGION 6 SURVEIL.
1525 RICHMOND ABC REGION 6 SURVEIL.
1804 CAPITOL POLICE OPERATIONS 1
1805 CAPITOL POLICE TAC 1
1806 CAPITOL POLICE FOX 1
1807 CAPITOL POLICE RED 1
2004 DCR DISTRICT 5 LE-5
2005 DCR DISTRICT 5 LE-5A
2006 DCR DISTRICT 5 LE-5B
2009 DCR DISTRICT 5 RED 5
2013 DCR DISTRICT 1 LE-1
2014 DCR DISTRICT 1 TAC
2016 DCR DISTRICT 1 LE-1A
2017 DCR DISTRICT 1 LE-1B
2018 DCR DISTRICT 1 RED 1
2024 DCR DISTRICT 1 UNKNOWN USE
2026 DCR DISTRICT 1 UNKNOWN USE
2027 DCR DISTRICT 1 UNKNOWN USE
2030 DCR DISTRICT 1 UNKNOWN USE
2038 DCR DISTRICT 3 LE-3
"Modulation" = "NFM"
"MoT Bandplan" = "Standard"
"P25 Waiting" = 400
"P25 Threshold Mode" = "Auto"
"P25 Threshold Level " = "8"
"Site Location"
"Location Type" "Circle"
"Latitude" = "38.924956"
"Longitude" = "-78.184411
"Range" = "125" (Miles)
------------------
John
W4UVV
John,
What is the effect of having your ID Search set to On but having a list of programmed talkgroups? Would the ID Search setting ignore your TG list and pick up anything coming across your sites?
What is the effect of having your ID Search set to On but having a list of programmed talkgroups? Would the ID Search setting ignore your TG list and pick up anything coming across your sites?
W4UVV
Member
Using ID Search and its' benefits
Fred,
If it were a perfect world and I had a 100% completely identified talkgroups list of all STARS users automatically updated on a frequent basis to include type of comm, detailed locations, etc. I wouldn't need it. But reality is over the past 10+ years it has been a continual quest for identifying and documenting STARS talkgroups users as the system and users evolved. Some talkgroups have disappeared due to reorganizations i.e., DGIF, DOF and DJJ, cutbacks, etc. For me, the search still continues.
Although I have over 400 talkgroups average per STARS division sites, which include those directly applicable to the division user and some are recurring "crossover" affiliations. Using ID search has resulted in a significant number of new talkgroup discoveries I have made over the past years.
With ID Search ON:
1. A new STARS talkgroup number quickly can be ided as such and subsequently actions can be taken attempting to document who, where, type of talkgroup, i.e., ops, tac, etc.
2. An existing talkgroup user, which has a recurring affiliation with the STARS site currently being monitored, can be added as a "regular" to that site. For example, talkgroups "5080" and "5280" are the I81 only Safety Patrol (Motorist Assistance). TG 5280 is controlled by a VDOT contractor in Salem and services from MP 1 in Bristol, VA to approximately MP 175 in Rockbridge Co. From Rockbridge Co. to the state line control is via the Staunton VDOT contractor. For whatever reason the STARS techs affiliated "5280" with the Division 1 Midlothian and other sites for maybe 3-4 years. The closest I am to I81 is about 125 miles. I'm sure the multiple STARS sites affiliations were sourced with the purpose of having seamless STARS comms with the Safety Patrol (M.A.)base/mobile Safety Patrol.
Until I added it to my appropriate talkgroups lists for the divisions STARS sites I frequently monitored "5280" would display every time "5280" and his control had a comm. I added that talkgroup with the appropriate identification because that text display is more meaningful to me than just a talkgroup number.. Then about a year ago the "5280" affiliation was unaffiliated and I began hearing "5080" which was the Staunton VDOT I81 Safety Patrol M.A. Now I also hear "5080" via a few Division 5 sites.
ID search is a great way to initially id new STARS talkgroup user. For example, one of the latest is the DOH STARS users because only the talkgroup numbers at first displayed and caught my attention. Then I had to use whatever resources and knowledge to id who it is and the type of talkgroup. It can be quite time consuming.
ID Search has been a good scanning selection for me. Otherwise, I never would have monitored the Buchanan Co. and Grundy PD on STARS Division 1 and in time documented the situation to my satisfaction.
But if you don't like possibly previously undocumented talkgroup numbers displaying for the site(s) you monitor select "ID Scan". Then you will never know they are there.
John
W4UVV
--------
Fred,
If it were a perfect world and I had a 100% completely identified talkgroups list of all STARS users automatically updated on a frequent basis to include type of comm, detailed locations, etc. I wouldn't need it. But reality is over the past 10+ years it has been a continual quest for identifying and documenting STARS talkgroups users as the system and users evolved. Some talkgroups have disappeared due to reorganizations i.e., DGIF, DOF and DJJ, cutbacks, etc. For me, the search still continues.
Although I have over 400 talkgroups average per STARS division sites, which include those directly applicable to the division user and some are recurring "crossover" affiliations. Using ID search has resulted in a significant number of new talkgroup discoveries I have made over the past years.
With ID Search ON:
1. A new STARS talkgroup number quickly can be ided as such and subsequently actions can be taken attempting to document who, where, type of talkgroup, i.e., ops, tac, etc.
2. An existing talkgroup user, which has a recurring affiliation with the STARS site currently being monitored, can be added as a "regular" to that site. For example, talkgroups "5080" and "5280" are the I81 only Safety Patrol (Motorist Assistance). TG 5280 is controlled by a VDOT contractor in Salem and services from MP 1 in Bristol, VA to approximately MP 175 in Rockbridge Co. From Rockbridge Co. to the state line control is via the Staunton VDOT contractor. For whatever reason the STARS techs affiliated "5280" with the Division 1 Midlothian and other sites for maybe 3-4 years. The closest I am to I81 is about 125 miles. I'm sure the multiple STARS sites affiliations were sourced with the purpose of having seamless STARS comms with the Safety Patrol (M.A.)base/mobile Safety Patrol.
Until I added it to my appropriate talkgroups lists for the divisions STARS sites I frequently monitored "5280" would display every time "5280" and his control had a comm. I added that talkgroup with the appropriate identification because that text display is more meaningful to me than just a talkgroup number.. Then about a year ago the "5280" affiliation was unaffiliated and I began hearing "5080" which was the Staunton VDOT I81 Safety Patrol M.A. Now I also hear "5080" via a few Division 5 sites.
ID search is a great way to initially id new STARS talkgroup user. For example, one of the latest is the DOH STARS users because only the talkgroup numbers at first displayed and caught my attention. Then I had to use whatever resources and knowledge to id who it is and the type of talkgroup. It can be quite time consuming.
ID Search has been a good scanning selection for me. Otherwise, I never would have monitored the Buchanan Co. and Grundy PD on STARS Division 1 and in time documented the situation to my satisfaction.
But if you don't like possibly previously undocumented talkgroup numbers displaying for the site(s) you monitor select "ID Scan". Then you will never know they are there.
John
W4UVV
Curious about TG 110, VSP EPU/ VEST, can you elaborate on that?
W4UVV
Member
TG110
TG 110 Executive Protection Unit (Governor's Security) coordination with appropriate VSP division(s) statewide.(Encrypted).
John
W4UVV
TG 110 Executive Protection Unit (Governor's Security) coordination with appropriate VSP division(s) statewide.(Encrypted).
John
W4UVV
Last edited:
- Status
Similar threads
BCD436HP/BCD536HP:
bcd436hp assistance
