For long Unit IDs:
Unit ID Name 1 is the first 16 characters, Unit ID Name 2 is the second 16 characters and so on.
Okay thanks. I wasn't too sure. Its pretty long if someone puts more than 16.
- Status
Okay thanks. I wasn't too sure. Its pretty long if someone puts more than 16.
So far, there doesn't seem to be any P25 performance improvement with firmware 1.03.01 on this system:
https://www.radioreference.com/apps/db/?sid=8214
Specifically, the Ft. Lauderdale and Plantation sites. Still seems to have trouble locking onto the control channels. Talkgroups flashing quickly on and off with no audio heard. Sometimes I can get a few good decodes in a row, especially if holding on the system. If I scan this system along with other unrelated systems, it will rarely stop on Ft. Lauderdale or Plantation.
NOTE: These sites (Ft. Lauderdale, Plantation, and Coral Springs) are operated as separate systems, and are not presently linked.
https://www.radioreference.com/apps/db/?sid=8214
Specifically, the Ft. Lauderdale and Plantation sites. Still seems to have trouble locking onto the control channels. Talkgroups flashing quickly on and off with no audio heard. Sometimes I can get a few good decodes in a row, especially if holding on the system. If I scan this system along with other unrelated systems, it will rarely stop on Ft. Lauderdale or Plantation.
NOTE: These sites (Ft. Lauderdale, Plantation, and Coral Springs) are operated as separate systems, and are not presently linked.
So far things seem more stable on this revision with the Missouri MARRS system. It remains on the system during simulcast signal cancellation dips longer and decode is more consistent.
scrotumola
Member
We have a WINNER!
To date I had been really disappointed with how the SDS100 had performed with the San Antonio/Bexar County 800 mhz EDACS ProVoice system, completely missing upwards of 80% of traffic even with a -45 dbm average signal with the Radio Shack 800 antenna.
Having had the chance to put 2 SDS100s side by side with both beta open firmware options and a BUNCH of 436s, I was in the process of comparing 1.02.05a and 05b open and how the alpha open was better than b in regards to EDACS ProVoice performance.
For the record, alpha was better but still unacceptable.
Now comes SDS100 Firmware 1.03.01 and I am happy--no, ECSTATIC to report that the SDS100s are performing just as well as their 436/536 counterparts! The radio also doesn't seem to heat up as drastically and before there was degradation of traffic in other modes as the temp increased.
I'm sure there is still room for improvement, but for now, I am happy that I can actually use my latest acquisition.
THANK YOU PAUL, and all of the development crew at muppet labs for making good on this one!
~S~
To date I had been really disappointed with how the SDS100 had performed with the San Antonio/Bexar County 800 mhz EDACS ProVoice system, completely missing upwards of 80% of traffic even with a -45 dbm average signal with the Radio Shack 800 antenna.
Having had the chance to put 2 SDS100s side by side with both beta open firmware options and a BUNCH of 436s, I was in the process of comparing 1.02.05a and 05b open and how the alpha open was better than b in regards to EDACS ProVoice performance.
For the record, alpha was better but still unacceptable.
Now comes SDS100 Firmware 1.03.01 and I am happy--no, ECSTATIC to report that the SDS100s are performing just as well as their 436/536 counterparts! The radio also doesn't seem to heat up as drastically and before there was degradation of traffic in other modes as the temp increased.
I'm sure there is still room for improvement, but for now, I am happy that I can actually use my latest acquisition.
THANK YOU PAUL, and all of the development crew at muppet labs for making good on this one!
~S~
Last edited:
I may have been premature with regard to my comments in post #22 above.
After a road trip this morning, there does seem to be some improvement with regard to P25 system performance. It seems most of the issues I mentioned in post #22 occur when monitoring from inside my house or the immediate vicinity. As soon as I am a few blocks from my house, P25 performance improves greatly, even with a rubber duck inside the vehicle.
As an added surprise, I was able to receive the Miami-Dade County Harris P25 system from central/northern Broward county. Not perfect, but I was getting conversations. This is the first time I have ever been able to receive Miami-Dade county this far north on any scanner I have tried. This system has been infamous for simulcast distortion.
After a road trip this morning, there does seem to be some improvement with regard to P25 system performance. It seems most of the issues I mentioned in post #22 occur when monitoring from inside my house or the immediate vicinity. As soon as I am a few blocks from my house, P25 performance improves greatly, even with a rubber duck inside the vehicle.
As an added surprise, I was able to receive the Miami-Dade County Harris P25 system from central/northern Broward county. Not perfect, but I was getting conversations. This is the first time I have ever been able to receive Miami-Dade county this far north on any scanner I have tried. This system has been infamous for simulcast distortion.
jasonhouk
Member
More testing was done today for the following issue as the FW update did not fix:
http://forums.radioreference.com/un...irmware-1-02-05b-open-beta-3.html#post2956805
My issues was what many other RR Users are experiencing when the SDS would stutter from CC to VC on P25 systems where the sites RSSI values that should be around -90 was actually displaying values of -45 plus.
My band-aid is as follows
1. Ensure proper NAC is entered for site/sites.
2. If the above does not eliminate the issue note sites CC and VC frequencies that are causing the stuttering issue.
A. Manually enter the frequencies in quick search mode and apply IFX (FNC + 7) for each frequency.
These steps eliminated my issues I was having in my area and YMMV.
If you still have stuttering issues after attempting the above steps, I'd then created a log and zip it to post here.
Houk
http://forums.radioreference.com/un...irmware-1-02-05b-open-beta-3.html#post2956805
My issues was what many other RR Users are experiencing when the SDS would stutter from CC to VC on P25 systems where the sites RSSI values that should be around -90 was actually displaying values of -45 plus.
My band-aid is as follows
1. Ensure proper NAC is entered for site/sites.
2. If the above does not eliminate the issue note sites CC and VC frequencies that are causing the stuttering issue.
A. Manually enter the frequencies in quick search mode and apply IFX (FNC + 7) for each frequency.
These steps eliminated my issues I was having in my area and YMMV.
If you still have stuttering issues after attempting the above steps, I'd then created a log and zip it to post here.
Houk
I'm glad you posted this because I was wondering about this too. For the past few days I've also been using the proper NAC for each P25 site I monitor and it really does feel like it does better and more solid tracking.
In other news, I'm REALLY liking the backlight behavior now more than ever. I have it set to:
Squelch: Open Squelch
Keypress: 15 Seconds
And it works as I would expect, Backlight off, LED blinks every few seconds, squelch opens, backlight turns on, stays on during transmission and when it ends, stays on for the duration of the channel delay and then turns back off, repeat.
Squelch: Open Squelch
Keypress: 15 Seconds
And it works as I would expect, Backlight off, LED blinks every few seconds, squelch opens, backlight turns on, stays on during transmission and when it ends, stays on for the duration of the channel delay and then turns back off, repeat.
troymail
Silent Key
NAC, like many other things, acts as a filter. With a NAC applied, the radio is likely to seem to receive better because it filters out voice calls where the NAC was garbled and/or not received....
To prove this, set the NAC to something invalid...
Last edited:
!
Why is it, that in the Sentinel software, some P25 systems have no option to set the P25 NAC, or the option is greyed out?
jasonhouk
Member
It is. After checking again, it seems that if you have the system type set to "P25 Trunk", you have the P25 NAC option available, but if the system type is set to "P25 X2 TDMA", there's no option to set the P25 NAC
jasonhouk
Member
Does P25 X2 TDMA use a NAC? If they do I'll submit a bug report.
Houk
Sent from my Moto G (4) using Tapatalk
Houk
Sent from my Moto G (4) using Tapatalk
Are they Phase II or X2?
I agree. This update fixed all the backlight issues. Also, reception has improved immensely. So far, no complaints.
SMBaugh2
Member
Jason I think you might have something here. I searched the NAC code and lock it in or I mean set to that code and noticed a difference. I'm still having fun with my SDS-100 and with your help and many others I'm learning day by day on how to get the best from this scanner and my Uniden Bearcat scanner is acting like a Bearcat the best in the business.
The P25 available options are:
P25 Trunk
P25 X2 TDMA
P25 One Frequency
X2 TDMA is Phase 2.
No, X2 is X2 (a MSI proprietary TDMA format very close to DMR). P25 Trunk would be the proper setting for P2 TDMA.
- Status
Similar threads
