Maybe post a debug file then it will help out not just YOU! It will help out everyone instead of just saying I am having the same issue.
- Status
Dafe1er
Member
ROFLMAO
Last edited:
Dafe1er
Member
Let us see if this works for ya Upman
DMR CAP+ LCN finder ran for several says, reported that ALL LCN's were found, saved them and when I went back to view them, they were all set to "0" still and the system will not track; doesn't seem to be an issue on the Whistler TRX-1; hearing lots of traffic on that radio where the SDS100 is a dust collector still... There also have been zero changes to VHF / UHF reception issues and frontend overload in a rural environment; but yes, the LSM works in trunked systems just fine, so I don't need to hear how others aren't having issues because it works great on systems like MPSCS and others in Michigan aren't complaining but yet folks in NY, NJ, and other areas that use allot of VHF / UHF conventional systems are having issues; even a few noted below and in other recent posts. Side-by-side the BCD436HP, the SDS100 is useless in the VHF / UHF range and the BCD436HP isn't having these issues.
Da1fer: Thank you for the log. What specific system and symptoms?
Dafe1er
Member
Orange County system located here: https://www.radioreference.com/apps/db/?ctid=2886
Problems are showing information while they transmit but no audio of any kind comes out. I confirmed the audio was working on another scanner but haven't looked to see if the information displayed on the SDS was correct against the other scanner as I did not think of that. I will try to get it this evening when out that way.
I have retested the LCN channel finder on two other systems and confirm that it is working in this firmware; not sure why it failed on the first system but I reran it and it saved the LCN's this time; however, aside from this the other issues still exist.
[FONT="]According to RRDB, DMR OFTs in Orange County are below.[/FONT][FONT="]
[/FONT][FONT="]155.370 MHz Slot 1 Orange SO 1[/FONT][FONT="]
[/FONT][FONT="]155.685 MHz Slot 1 Orange SO 2[/FONT][FONT="]
[/FONT][FONT="]155.685 MHz Slot 2 Orange SO 3[/FONT][FONT="]
[/FONT][FONT="]154.055 MHz Slot 1 Orange Sch Bus[/FONT][FONT="]
[/FONT][FONT="]However, per the attached logs these channels are not even being scanned.[/FONT][FONT="]
[/FONT]
For poops and giggles I put a par vhf153 marine filter in line and adjusted it to where 152mhz pager brought the RSSI on 152.48mhz from -75db to -95 db and I receive the vhf band ALMOST perfectly....including 151.085 DOT and 153..0125 with an rssi of only -90
Best vhf I have seen is an rssi of -85 State Police and a federal border patrol repeater on 163.725 that when active knocks signal from -85rssi to -102rssi through the vhf spectrum and everything goes to encrypt including national weather service on 162,400 mhz...then when that border patrol repeater unkeys its back to normal rssi of -90...
Best vhf I have seen is an rssi of -85 State Police and a federal border patrol repeater on 163.725 that when active knocks signal from -85rssi to -102rssi through the vhf spectrum and everything goes to encrypt including national weather service on 162,400 mhz...then when that border patrol repeater unkeys its back to normal rssi of -90...
Last edited:
Dafe1er
Member
Upman, let us see if these have anything in them for you. I ran a scan last night and never heard a peep out of the scanner while doing so. I tried to watch the screen but was working while it was running so I'm not sure about the information showing up still.
I tried to post two other files from the debug run and the site says they are too big for uploading.
I tried to post two other files from the debug run and the site says they are too big for uploading.
For testing, it is best to limit scanning to just the channels that exhibit the issue. Otherwise, it can both obfuscate any issue and also cause there to be much more information than necessary to try to troubleshoot (which makes troubleshooting very difficult).
Dafe1er
Member
I will try again this evening. I will let it sit on the Orange favorites list on the Sheriff channel only and see what comes of it.
Ubbe
Member
Text files can be huge in size but if you zip them they become extremly small and much easier to upload without breaking the limit.
/Ubbe
476.5625 NYC debug file
Heres my debug file for poor reception on 476mhz NYC Manhattan,citywide,etc
I am 10 miles from NYC and the SDS-100 can get only -103dbm signal which is not consistent.
Very simple quick reception on 3-4 scanlists.
Bcd-396xt loud and clear same antenna.
Heres my debug file for poor reception on 476mhz NYC Manhattan,citywide,etc
I am 10 miles from NYC and the SDS-100 can get only -103dbm signal which is not consistent.
Very simple quick reception on 3-4 scanlists.
Bcd-396xt loud and clear same antenna.
Last firmware update
Just a quick question... I bought my SDS100 about 2 weeks ago. Downloaded the latest firmware update when I plugged the scanner in. 1.05.00 Main / 1.01.05 is what the scanner is showing. I see that the latest is 1.05.01 Main / 1.01.05. My question is, are both firmware's the same? Last update I see was in August.
The NAC issue was addressed in 1.05.01 Main / 1.01.05 so it says on Uniden website. With the 1.05.00 Main / 1.01.05 showing on my scanner after the update, the NAC seems to be resolved with the option of ingnoring or not ingnoring the NAC. I do have that option now in my scanner.
Thanks!!!
Kevin
WA2KM
Just a quick question... I bought my SDS100 about 2 weeks ago. Downloaded the latest firmware update when I plugged the scanner in. 1.05.00 Main / 1.01.05 is what the scanner is showing. I see that the latest is 1.05.01 Main / 1.01.05. My question is, are both firmware's the same? Last update I see was in August.
The NAC issue was addressed in 1.05.01 Main / 1.01.05 so it says on Uniden website. With the 1.05.00 Main / 1.01.05 showing on my scanner after the update, the NAC seems to be resolved with the option of ingnoring or not ingnoring the NAC. I do have that option now in my scanner.
Thanks!!!
Kevin
WA2KM
jasonhouk
Member
1.05.01 was a public beta released here:
https://forums.radioreference.com/uniden-tech-support/375723-firmware-1-05-01m-public-beta.html
Houk
Oh, okay.... I was confused because on the Uniden firmware site I saw that back in August it looked like 1.05.01 Main / 1.01.05 was released to Sentinal for download..... That is why I was curiuos why when I downloaded the August update into the scanner is did not show 1.05.01 Main / 1.01.05 but showed the 1.05.00 Main / 1.01.05 instead.
Yahoo 
Not a member don't want to be a member of yahoo spam group. No thank you.
Notice to anyone that doesn't know, you sign up and someone hacks your email account. So heads up to all the scanner guys and girls.
https://money.cnn.com/2017/10/03/technology/business/yahoo-breach-3-billion-accounts/index.html
I am talking about the SDS-100 Wiki page or upman's page which has the 996xt,P2,Bcd-436,536hp, and even yes the BC246T ,remember that great scanner?
Not a member don't want to be a member of yahoo spam group. No thank you.
Notice to anyone that doesn't know, you sign up and someone hacks your email account. So heads up to all the scanner guys and girls.
https://money.cnn.com/2017/10/03/technology/business/yahoo-breach-3-billion-accounts/index.html
I am talking about the SDS-100 Wiki page or upman's page which has the 996xt,P2,Bcd-436,536hp, and even yes the BC246T ,remember that great scanner?
Last edited:
seth21w
Member
Has anyone tried mix and matching the earlier sub firmwares with newer main firmware or is it even possible?
- Status
