SDS100/SDS200: P25/Squelch
- Thread starter Dexter2
- Start date
- Status
Ok...for the heck of it, try Use Site NAC. You have a NAC programmed in under the site?
k and yes all three Sites have an NAC, two Sites are Avoided.
Ok..try whatever site(s) give you the best signal and give it a shot...nothing to lose.
Thank you!
Attached is the log file, I believe it covers a 3-4 hour period. I only moved the radio once farther back on my office desk. The SQ is on 2 and the Site Filter was set on Global fresh out the box. I only heard 4 half conversations and 1 full conversation, the rest of the time dead in the water.
drive.google.com
Looking at the log, it looks like something went wrong, it looks like after I moved the radio in the beginning everything is gone. I don't even see the frequencies anymore. I have not been able to get the original antenna out yet.
Side note, another thing I do is match the PD/FD Systems on the Broadcastify app and to this day everything matches, though there is a 2 minute delay on the app which to me is expected. The PD works perfect, I don't have to change SQ, Filter, Site Delay anything.
log0030936.zip
drive.google.com
Looking at the log, it looks like something went wrong, it looks like after I moved the radio in the beginning everything is gone. I don't even see the frequencies anymore. I have not been able to get the original antenna out yet.
Side note, another thing I do is match the PD/FD Systems on the Broadcastify app and to this day everything matches, though there is a 2 minute delay on the app which to me is expected. The PD works perfect, I don't have to change SQ, Filter, Site Delay anything.
Last edited:
Ubbe
Member
If it encounters anothers system sfrequency it will then just mute and skip the frequency back and forth. Set it to search and if the NAC change on the display you'll know that you have another frequency in the mix. If you set a fixed NAC you'll just wonder what's going on and have no clue to why.
Do log with SQ at 0 so it will have a chance to decode the signal without the squelch making it drop out of the channel.
/Ubbe
Okay I'll redo it tomorrow with SQ at 0 and set NAC to Search. Its always been on Search until I switched it today per wearinshades when I did the log.
Ubbe
Member
The log you did now, you had the SQ set at 2 but the log shows that it scans with a rate of 10ch/s as if the squelch where open. Also when it goes from the control channel, when it actually are received, and it sends the scanner to a voice channel to follow a call, it stays there for 1 second as if the squelch was open and when it can't detect any data it goes back to the control channel. It should go back after 50mS or 100mS if there's no carrier at the voice frequency.
If it looks the same in a log with the SQ actually set at 0 then the scanner has a squelch problem. If you remove the antenna and set the squelch to 0 you should see how slow it scans through the channels and as soon as you close the squelch, normally at 2, it should speed up, if the frequencies even are shown on the display.
If you do another log then turn the squelch up to highest setting for a while and then down to 0 again, and the log should show that change. Also use IDsearch to catch all the conversations. It looks as if you had IDscan on and a conversation where started with TG20 but you didn't had that in your TG list.
In this log you have the scanner going trough the sites frequencies and it finds a carrier on 859.1125 but no data can be decoded so it continues and finds a carrier at 858.6875 that probably are an ongoing voice call but no data can be decoded and it continues to scan.
0038117 PLL,08570625
0038313 PLL,08567875
0038406 PLL,08598125
0038457 PLL,08591125
0038510 PLL,08591125
0038521 SP1 DA1: 0253 FIR2: 025A
0038536 SC1 DA1: 0253 FIR2: 025A
0039284 PLL,08586875
0039301 SC0 DA1: 0253 FIR2: 0170
0039301 PLL,08570625
0039306 SP0 DA1: 0253 FIR2: 0170
0039494 PLL,08567875
0039588 PLL,08598125
A big part of the log looks like this:
0426974 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426978 evnt_idscan_ch_change(C)
And with 4-5 seconds intervals it decodes that a voice channel 857.0625 has activity and tunes the scanner to that frequency but then goes back to control channel after 1 second when failing to decode any data.
To me it looks as if all frequencies have a very weak signal strenght and not at all like a -50dBm level that the display indicates.
Do a format of your SD card and then do Clear User Data from Sentinel and program your SD card again. Also put the latest .bin and .firm files in the firmware folder on the SD card to refresh your firmware.
drive.google.com
/Ubbe
If it looks the same in a log with the SQ actually set at 0 then the scanner has a squelch problem. If you remove the antenna and set the squelch to 0 you should see how slow it scans through the channels and as soon as you close the squelch, normally at 2, it should speed up, if the frequencies even are shown on the display.
If you do another log then turn the squelch up to highest setting for a while and then down to 0 again, and the log should show that change. Also use IDsearch to catch all the conversations. It looks as if you had IDscan on and a conversation where started with TG20 but you didn't had that in your TG list.
In this log you have the scanner going trough the sites frequencies and it finds a carrier on 859.1125 but no data can be decoded so it continues and finds a carrier at 858.6875 that probably are an ongoing voice call but no data can be decoded and it continues to scan.
0038117 PLL,08570625
0038313 PLL,08567875
0038406 PLL,08598125
0038457 PLL,08591125
0038510 PLL,08591125
0038521 SP1 DA1: 0253 FIR2: 025A
0038536 SC1 DA1: 0253 FIR2: 025A
0039284 PLL,08586875
0039301 SC0 DA1: 0253 FIR2: 0170
0039301 PLL,08570625
0039306 SP0 DA1: 0253 FIR2: 0170
0039494 PLL,08567875
0039588 PLL,08598125
A big part of the log looks like this:
0426974 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426978 evnt_idscan_ch_change(C)
And with 4-5 seconds intervals it decodes that a voice channel 857.0625 has activity and tunes the scanner to that frequency but then goes back to control channel after 1 second when failing to decode any data.
To me it looks as if all frequencies have a very weak signal strenght and not at all like a -50dBm level that the display indicates.
Do a format of your SD card and then do Clear User Data from Sentinel and program your SD card again. Also put the latest .bin and .firm files in the firmware folder on the SD card to refresh your firmware.
sds100 - Google Drive
drive.google.com
/Ubbe
The log you did now, you had the SQ set at 2 but the log shows that it scans with a rate of 10ch/s as if the squelch where open. Also when it goes from the control channel, when it actually are received, and it sends the scanner to a voice channel to follow a call, it stays there for 1 second as if the squelch was open and when it can't detect any data it goes back to the control channel. It should go back after 50mS or 100mS if there's no carrier at the voice frequency.
If it looks the same in a log with the SQ actually set at 0 then the scanner has a squelch problem. If you remove the antenna and set the squelch to 0 you should see how slow it scans through the channels and as soon as you close the squelch, normally at 2, it should speed up, if the frequencies even are shown on the display.
If you do another log then turn the squelch up to highest setting for a while and then down to 0 again, and the log should show that change. Also use IDsearch to catch all the conversations. It looks as if you had IDscan on and a conversation where started with TG20 but you didn't had that in your TG list.
In this log you have the scanner going trough the sites frequencies and it finds a carrier on 859.1125 but no data can be decoded so it continues and finds a carrier at 858.6875 that probably are an ongoing voice call but no data can be decoded and it continues to scan.
0038117 PLL,08570625
0038313 PLL,08567875
0038406 PLL,08598125
0038457 PLL,08591125
0038510 PLL,08591125
0038521 SP1 DA1: 0253 FIR2: 025A
0038536 SC1 DA1: 0253 FIR2: 025A
0039284 PLL,08586875
0039301 SC0 DA1: 0253 FIR2: 0170
0039301 PLL,08570625
0039306 SP0 DA1: 0253 FIR2: 0170
0039494 PLL,08567875
0039588 PLL,08598125
A big part of the log looks like this:
0426974 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426975 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426976 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426977 evnt_idscan_ch_change(C)
0426978 evnt_idscan_ch_change(C)
And with 4-5 seconds intervals it decodes that a voice channel 857.0625 has activity and tunes the scanner to that frequency but then goes back to control channel after 1 second when failing to decode any data.
To me it looks as if all frequencies have a very weak signal strenght and not at all like a -50dBm level that the display indicates.
Do a format of your SD card and then do Clear User Data from Sentinel and program your SD card again. Also put the latest .bin and .firm files in the firmware folder on the SD card to refresh your firmware.
sds100 - Google Drive
/Ubbe
Thank you for your insight. How do you format the SD? TG20 is indeed in my list, but what I failed to do was AVOID all the test TG's, TG17-20 are the main ones. I remember TG3 appeared but didn't want to interrupt the log. Regarding to your first paragraph is that because of the Site Hold? So if its a stronger signal it would stay longer than the 1 second?
What does SC/SP/DA/PL/FIR are all mean? Trying to see I can learn to read this log.
jonwienke
More Info Coming Soon!
You can have them in the same favorite list no problem. They just have to be programmed as separate systems.
That's what I thought it looked like it was doing and is why I suggested that. By isolating the NAC to the system you're trying to monitor, would prevent this from happening and would ignore the phantom signal. Is their another user on that specific voice frequency that's flashing? Do a license search and back track if it's in use by a conventional or trunking system. That appears to be causing the scanner much confusion.
Ubbe
Member
It's the opposite, it works the other way around. If you lock a frequency to one specific NAC, or subtone or color code or RAN, it will still be interfered from another radiosignal and will skip and mute and jump around. If you have it set to ignore or search it will accept whatever it decodes.
/Ubbe
Ubbe
Member
You can probably do that when you connect the scanner to your PC and select mass storage mode. Right click on the drive letter or the scanner name and select format. Best are to use a seperate $5 SD card interface and have it directly connected to your PC and use the program SDFormatter.
Don't avoid anything, try to monitor all TG's in the system by having no avoids and using IDsearch.
No, it's because the scanner doesn't recognise any valid datasignal, but it reacts as if there was a carrier on the frequency. If it starts to decode data it would stay longer on the frequency.
It's the signalling from the radio receiver to the computer logic in the scanner. The numbers after them tells if the squelch opened and if it sees any datasignals. I haven't tried to log with different SQ settings and monitoring data to see which values actually indicates SQ, subtone, data and so on.
The PLL, 085606250 type of information are the frequency commands that the radio receiver are tuning to. If you see multiples of the same frequency being repeated it means bad communication between radio and logic and are a telltale sign for cold solder joint in the J401 connector. But you don't have those problems.
If it still scans that slow, and you havent set the filter to auto, and you do a log with both sq set at its highest value and lowest, then it must be some other type of hardware problem in the scanner. But if you update your firmware again and reformat the SD card it should rule out any bad software data.
The number value on each line of the log are the timer. It used to be 1mS steps but it probably made the scanner put too much work in the log and it disturbed the scanners normal functions, so they now are 2mS increments.
If you see a 45-50 value difference between two PLL,xxxx it is 50x2mS=100mS per channel change, 10ch/s.
/Ubbe
I'm not sure that's correct and the reason why NAC was included in the SDS models was to prevent other P25 signals from interfering. We can't determine if the issue is intermod from another source that the op has when in one location vs the other or another P25 signal from a P25 system within range. But...if the Site is set to Use Site NAC and the "frequency jumping" that is seen on the video is resolved, then that would be a good thing. If it doesn't resolve the issue, no harm done. I haven't experienced what the op has, so just making a suggestion.
Hello all - So I just reformatted the SD, inserted the latest .bin and .firm files, I resetted all the settings and cleared data. I only reprogrammed the Transit system, nothing else is on my radio now. I did not touch anything no filters, no nac, no delays, no holds, no talkgroup avoids and did an hour log. I just brought the radio and placed it on my bed. Now that I am typing this I can hear activity loud and clear all the way from there and the SQ is on 0.
From 10:00am-10:30am SQ is on 15 (only heard one sliver of a transmission)
From 10:30am-11:00am SQ is on 0 (the very ending or beginning of three transmissions came in)
Also note TG 16 is an Encrypted channel.
The time is now 11:12am
From 10:00am-10:30am SQ is on 15 (only heard one sliver of a transmission)
From 10:30am-11:00am SQ is on 0 (the very ending or beginning of three transmissions came in)
Also note TG 16 is an Encrypted channel.
The time is now 11:12am
jonwienke
More Info Coming Soon!
Programming a NAC works exactly like programming a tone on an analog channel. If you don't program one, the scanner will try to decode/play anything it hears on the frequency. If you do program one, the scanner will check to see if the transmission matches the programmed NAC. If it does, it will try to play the traffic. If it doesn't, the scanner will resume scanning.
If there are multiple systems using a frequency and you only want to hear one, setting a NAC is a good idea. It won't prevent interference when both systems are transmitting simultaneously, but it will minimize the amount of time the scanner wastes decoding garbage from the undesired system.
One other note: encrypted transmissions can cause "flickering" between control and voice channels if you're holding on a site, or a system with only one site programmed/enabled. The control channel tells the scanner there is a transmission, so the scanner switches to the voice channel to check it out. If the call is encrypted, the scanner moves on. If there are other systems to scan, they will get scanned at that point. But if you're holding on the site, the scanner will go back to the control channel, which tells it there is a voice call, so the scanner goes back to the voice channel, and the cycle repeats until a non-encrypted transmission starts, or the encrypted transmission ends.
If there are multiple systems using a frequency and you only want to hear one, setting a NAC is a good idea. It won't prevent interference when both systems are transmitting simultaneously, but it will minimize the amount of time the scanner wastes decoding garbage from the undesired system.
One other note: encrypted transmissions can cause "flickering" between control and voice channels if you're holding on a site, or a system with only one site programmed/enabled. The control channel tells the scanner there is a transmission, so the scanner switches to the voice channel to check it out. If the call is encrypted, the scanner moves on. If there are other systems to scan, they will get scanned at that point. But if you're holding on the site, the scanner will go back to the control channel, which tells it there is a voice call, so the scanner goes back to the voice channel, and the cycle repeats until a non-encrypted transmission starts, or the encrypted transmission ends.
Ubbe
Member
It has to receive some data to be able to tell if the encryption flag are raised or perhaps the checksums doesn't match. The log goes on for ages without anything are decoded. At the end of the log it seems to start to work.
Dexter2, can you enter the control channel into Quick Save, channel+859.1125+Enter+Enter and edit at that point to audio mode Analog only. Then push the system button to start scan. Push system button and wait it for it set a hold on a system. Push system again and immediatly use the dial button to scroll thru the systems until you find the Quick save system. Now push the channel button and scroll thru the channels, if there are several, until you find that 859.1125 frequency. Set the squelch to 0 and listen to the audio.
It should be a datasignal there. Compare to the pure noise when you remove the antenna. Use the Uniden antenna to compare if the datasignal are received better. Move around with the scanner and notice if the datasignal are received better or worse.
The log shows that all your frequencies in that system are received very poorly. But the display still show a -50dBm level which is a very strong signal.
It could be the antenna connector that are bad, depends of if other systems at a comparable distance works just as bad. At least that signal strenght indication doesn't work as it should and needs to be repaired at Uniden and people have reported that when they have bad performance the signal strenght could be indicating between -60dBm to -40dBm and all was return to normal reception and signal strenght after a repair.
/Ubbe
Dexter2, can you enter the control channel into Quick Save, channel+859.1125+Enter+Enter and edit at that point to audio mode Analog only. Then push the system button to start scan. Push system button and wait it for it set a hold on a system. Push system again and immediatly use the dial button to scroll thru the systems until you find the Quick save system. Now push the channel button and scroll thru the channels, if there are several, until you find that 859.1125 frequency. Set the squelch to 0 and listen to the audio.
It should be a datasignal there. Compare to the pure noise when you remove the antenna. Use the Uniden antenna to compare if the datasignal are received better. Move around with the scanner and notice if the datasignal are received better or worse.
The log shows that all your frequencies in that system are received very poorly. But the display still show a -50dBm level which is a very strong signal.
It could be the antenna connector that are bad, depends of if other systems at a comparable distance works just as bad. At least that signal strenght indication doesn't work as it should and needs to be repaired at Uniden and people have reported that when they have bad performance the signal strenght could be indicating between -60dBm to -40dBm and all was return to normal reception and signal strenght after a repair.
/Ubbe
- Joined
- Jan 5, 2003
- Messages
- 14,304
- Reaction score
- 10,253
- Location
- Retired 40 Year Firefighter NW Tenn
I would start looking for a local tower as interference
I put the Uniden antenna back on this morning. I haven't been able to do the Quick Save yet but so far its the similar song. When I try Filters with SQ on 2 it shows different this time alittle bit: Global and Wide Invert RSSI shows -60, Invert and Wide Normal shows -116 and Normal it disappeared and Off shows -45 and i received traffic as per the usual.
When I have the Police System only everything works fine nothing touched or changed and RSSI goes between -60 and -90 but activity is crystal and if i take Filters off it goes to -45 as well. But SQ is untouched.
- Status
