kcvanover
Member
Any of you Daviess county guys interested in starting a scanning club?
KSP Discussion Thread
- Thread starter N4DXX
- Start date
-
- Tags
- bcd325p2 proscan 14.3 sticky
I have
P25 signals are data signals.
This last statement is the smoking gun. I probably mis-diagnosed the situation by assuming an internal scanner bug. Electro Magnetic Interference (from other scanners, wifi, computers, passing vehicles, florescent lights, you name it) is a more than likely culprit.
This seems unnecessary for KSP communications purposes. Scanners might be employed for other reasons, or they may be seen as a distraction to the critical mission of the KSP. For officer safety I assume that direct two way communication is preferred.
But, I have been wrong a couple of times before before.
We both could be wrong or right. It's just how I hear it. When we listen to a simplex frequency on our radio system from a Pro-197 you don't hear that slight tone at the end, but when we listen to the repeater frequency, you'll hear it for about a second at the end. I dunno, I may be confused as to what I'm saying. I'm in Ohio for school right now, but I'm going back to Boyd this weekend, so I'll leave a recorder on my headphone output & record what I'm talking about & see if it's the same thing as he's hearing on KSP...
@ sound_efex, in reference to your PM, I know.
It's cool. If I'm wrong, I'm wrong.
ak4fn
Member
We both could be wrong or right. It's just how I hear it. When we listen to a simplex frequency on our radio system from a Pro-197 you don't hear that slight tone at the end, but when we listen to the repeater frequency, you'll hear it for about a second at the end. I dunno, I may be confused as to what I'm saying. I'm in Ohio for school right now, but I'm going back to Boyd this weekend, so I'll leave a recorder on my headphone output & record what I'm talking about & see if it's the same thing as he's hearing on KSP...
@ sound_efex, in reference to your PM, I know.
They have now stopped, It quit doing it about a week ago (at least post 2 has), life is good!
Is anyone having problems hearing Post 5 - Campbellsburg, Post 4 - E-town and Post 12 - Frankfort.
It's been several days since I've heard anything from either Post. Living in Louisville I've had no problems before hearing either of the Posts. I've re-entered all the frequencies using Win500 but nothing. I'm using a Pro106.
Has something changed?
Thanks,
Paul
It's been several days since I've heard anything from either Post. Living in Louisville I've had no problems before hearing either of the Posts. I've re-entered all the frequencies using Win500 but nothing. I'm using a Pro106.
Has something changed?
Thanks,
Paul
DARRELL34
Member
Iam having no problem hering post 12 but i live here p25
PSR800 - Monitoring P25 Conventional Talkgroups On KSP
Notes from a trip to the Owensboro area this AM:
For KSP Post 2, monitored several transmissions off the Sacramento tower.
For KSP Post 16, monitored several transmissions off Reed, Cloverport, Whitesville, & Henderson towers.
It appears talkgroup ID (TGID) = 1 is the P25 conventional talkgroup for dispatch for both KSP Post 2 & 16.
Radio ID's for the dispatch consoles:
200001 Console 1 for Post 2
200002 Console 2 for Post 2
200003 Console 3 for Post 2
likewise,
1600001 Console 1 for Post 16
1600002 Console 2 for Post 16
1600003 Console 3 for Post 16
Individual trooper radio ID's are random in nature and have no observable correlation to unit numbers.
Notes from a trip to the Owensboro area this AM:
For KSP Post 2, monitored several transmissions off the Sacramento tower.
For KSP Post 16, monitored several transmissions off Reed, Cloverport, Whitesville, & Henderson towers.
It appears talkgroup ID (TGID) = 1 is the P25 conventional talkgroup for dispatch for both KSP Post 2 & 16.
Radio ID's for the dispatch consoles:
200001 Console 1 for Post 2
200002 Console 2 for Post 2
200003 Console 3 for Post 2
likewise,
1600001 Console 1 for Post 16
1600002 Console 2 for Post 16
1600003 Console 3 for Post 16
Individual trooper radio ID's are random in nature and have no observable correlation to unit numbers.
RonnieUSA
Member
What are You using to see this, I tried pressing func + tune, and all I get is the nac.
RonnieUSA
Member
You are correct.
Same for 4,7,11,12, and 15
When programmed correctly. The radio will show a unit # instead of the "random radio I'd"
Same for 4,7,11,12, and 15
When programmed correctly. The radio will show a unit # instead of the "random radio I'd"
RonnieUSA
Member
Been noticing lots of Mods to KSP License this month, anyone know whats up with all of this.
Here is a link for yesterdays list.
Application Search - Search Results
Here is a link for yesterdays list.
Application Search - Search Results
Confuzzled
Member
- Joined
- Aug 16, 2008
- Messages
- 704
Let me clarify the statement...
the individual trooper RID's show no discernible pattern in relationship to unit numbers/badge numbers...
I have no idea what you're looking at, but wouldn't the radio ID be more like a serial number or property tag number that would stay with the radio no matter who it was assigned to?
RonnieUSA
Member
460.300000, P25, 286
Been hearing this loud, and clear this morning.
It's not listed in the data base that I could find.
The last unit I heard Her talking to was, Frankfort to 694, was giving license plate info.
Been hearing this loud, and clear this morning.
It's not listed in the data base that I could find.
The last unit I heard Her talking to was, Frankfort to 694, was giving license plate info.
How are you programming post 4? I just added the frequencies p25 and they work.... how are you making them into a talk group. What would i enter? Thanks
RonnieUSA
Member
Yes I'm using DSD on my 15X, and it is showing the Console ID's as:
800001 Post 8
800002 Post 8
800003 Post 8
1400001 Post 14
1400002 Post 14
Have not seen a 3rd one yet.
None of the Trooper are matching what is show as the ID in DSD, just the Console ID's.
This only works on the 396XT, BC996XT, Home Patrol, and GRE80 - or using a tapped scanner running DSD.
Which scanner are you utilizing???
Last edited:
Ronnie - you are correct.
The console IDs line up similar in Post 1, 2, and 16.
The portable/mobiles have no pattern or match to the Trooper's radio call/unit number.
Similar threads
BCD325P2/BCD996P2:
Easy Fix For BC_VUP3 Firmware Updater Locking Up After Selecting A COM Port
