99.9% of the users of the RR dB are not programming radios onto trunking systems using NAS.
the RR dB will always - and forever - be oriented towards scanner types - not RPM/CPS, et al.
Brevard County P25 (00A.92077)
- Thread starter batdude
- Start date
99.9% of the users of the RR dB are not programming radios onto trunking systems using NAS.
the RR dB will always - and forever - be oriented towards scanner types - not RPM/CPS, et al.
as of this morning, I am no longer hearing Brevard SO South EDACS TG 01-013 on the EDACS trunk. it is only on the P25 system (TG 139)
also, if no one has noticed, the P25 talkgroups seem to follow the DECIMAL EDACS TG IDs -
for example, BCSO South is 01-013 (aka DECIMAL 139) on EDACS. it is also TG139 on the P25 system......
also, if no one has noticed, the P25 talkgroups seem to follow the DECIMAL EDACS TG IDs -
for example, BCSO South is 01-013 (aka DECIMAL 139) on EDACS. it is also TG139 on the P25 system......
I am still hearing south (139) on the EDACS. What tower are you listening to?
all three sites in ID search .....
Weird. My SDS200 hears it fine and unitrunker has calls from all night without any gaps
I'm going to dump the programming and re-load (SDS200 as well....)
was a favorites list problem.... BCSO is still on EDACS....
TG numbers are decimal in Harris systems, always. Some system data is hexadecimal format, but the Harris software only uses decimal TG numbers.
It's very rational that the TG numbers stay the same as service transitions from the EDACS to the P25 system. Translations always get messed up, it's so much easier to keep things the same.
I'm hearing a lot of ear splitting screeches on the P25 system. Audio quality is...highly variable. Not sure how much of that can be tuned to be better, and how much is a matter of retraining users to speak clearly into the microphone with a normal voice.
It's very rational that the TG numbers stay the same as service transitions from the EDACS to the P25 system. Translations always get messed up, it's so much easier to keep things the same.
I'm hearing a lot of ear splitting screeches on the P25 system. Audio quality is...highly variable. Not sure how much of that can be tuned to be better, and how much is a matter of retraining users to speak clearly into the microphone with a normal voice.
- Joined
- Sep 17, 2009
- Messages
- 176
They have Melbourne PD Primary on P25 now as well.
system continues to evolve with more and more agencies coming across the P25 simultaneously with the EDACS system.
sporadic AES-256 encryption has been noted on nearly every talkgroup on the P25 system --- enjoy while you can.
TDMA is in use on the P25 system, and the audio quality is from 'poor' to 'understandable'.
sporadic AES-256 encryption has been noted on nearly every talkgroup on the P25 system --- enjoy while you can.
TDMA is in use on the P25 system, and the audio quality is from 'poor' to 'understandable'.
I've observed patched talkgroups between the two systems where the P25 system is heard first, the EDACS system heard later, and I've heard other transmissions where the EDACS system was heard first, and the P25 system was heard after a short delay.
I've heard both sides of a conversation on an EDACS talkgroup, but listening to the P25 system, the radio showed encryption in use and only the dispatcher audio was heard, so they're decrypting before patching from P25 to EDACS.
It appears that smaller departments are transitioning first, which is logical. Smaller test cases, fewer radios to reprogram if there's a problem.
Work the bugs out with the smaller users before committing to the big effort of migrating the biggest users with thousands of radios.
The P25 audio is likely to generate a ton of complaints. Coming from a well tuned and maintained analog system with good coverage, there's no real comparison in which the P25 audio will be considered better except for very rare fringe of coverage cases.
I've heard both sides of a conversation on an EDACS talkgroup, but listening to the P25 system, the radio showed encryption in use and only the dispatcher audio was heard, so they're decrypting before patching from P25 to EDACS.
It appears that smaller departments are transitioning first, which is logical. Smaller test cases, fewer radios to reprogram if there's a problem.
Work the bugs out with the smaller users before committing to the big effort of migrating the biggest users with thousands of radios.
The P25 audio is likely to generate a ton of complaints. Coming from a well tuned and maintained analog system with good coverage, there's no real comparison in which the P25 audio will be considered better except for very rare fringe of coverage cases.
Sounds like they are using the EDACS migration gateway then
There is no question, when listening side-by-side, to the EDACS analog transmissions, that P25 has a very noticable loss of intelligibility by direct comparison.These DVSI vocoder codecs remove (for efficency) many of the needed audio cues that the ear-brain requires for high speech intelligibility.
L3H radios also tend to have an even more robotic tonality in comparison to their other competitors.They also tend to have a less refined audio chain. Especially, the speaker driver(s) used in many of their radios.
And yet, Harris made something of a big deal about the XL radios (at least the 185 and 200) having a separate woofer in the back for better audio quality. Listening in analog mode, those radios do have good audio quality, but honestly it's not better than an old school analog Saber. But what is? I still think the Saber was the best sounding radio, receiver-wise, of any portable radio yet made.
For the GE-Harris side, their best speaker audio quality was the M-PD.
For the GE-Harris side, their best speaker audio quality was the M-PD.
They also brought in, which is now SAMSUNG owned, HARMAN Audio Group for the audio design. M/A-Com did a similiar thing with the P7200. They had a former BOSE engineer tweak the audio. The later run of P7200's sounded mrginally better than the P7100. However, P25 still had a more robotic and tinnier sound quality. The XL series is going to be the best audio quality radio L3H currently produces. And just as asidenote, P25 sounds even worse on their military tactical handheld radios in comparison to the public safety radios.
Anyway back on topic with Brevard County.
I'm just going on the assumption that the group numbers for the EDACS system are going to be preserved as policy for the P25 system, and program accordingly. So far I've got no evidence to think otherwise.
I really need to take some time to learn how to use my SDR dongles and software. I have it, just haven't bothered to play with it.
I'm lazy these days, I want the Windows installer to do it all for me.
I really need to take some time to learn how to use my SDR dongles and software. I have it, just haven't bothered to play with it.
I'm lazy these days, I want the Windows installer to do it all for me.
That was already established a few posts back, I believe. One quick look at the Database confirms that as well. Example: Melbourne PD Primary EDACS TG is 08-012; in DEC it is 1034. On the P25 System, the TG For Melbourne PD Primary is 1034. Ive seen this happening with the Volusia P25 system, typical use of the EDACS migration gateway.
believe it or not, i was running UT last night on the EDACS system. I think they are just deleting the channel from the EDACS lineup and LCNs are staying the same - otherwise I think they would have to re-program a few thousand EDACS radios.
they have had an "OOPS" - in the last day or so
852.8125 was left active on both the Brevard EDCAS side and the P25 side. This does not work out well. At all.
second - 851.400 is getting walked on - BAD - by Sumter County this morning due to the band opening. This is causing some problems with the Brevard P25 system ---- FWIW - DSD+ is seeing cross affiliations (did not think that was possible) between both the Brevard and Sumter P25 systems - e.g, Brevard TGs are showing up on the Sumter control channel.... most odd. Again, this is just DSD+ data.....
third, 853.375 from the OC Northwest site is completely clobbering EDACS this morning. This channel is getting hung up with P25 CC data from that site.
Someone really needs to take a look at coordination between OC and Brevard.... 853.375 isn't the only issue.
Last edited:
That explains what I've been hearing then.
Similar threads
