SDS100/SDS200 Tax Day Update (1.10.00)

[WX4JCW]

as Scanman is saying, i am testing on my home system today (Orange County) - wide inverted on both results in 0 D-Errors so they are about the same looks like

 

[WX4JCW]

Both running latest firmware


Sent from my iPhone using Tapatalk Pro

 

[mikewazowski]

Wow, this thread sure got derailed quickly.

Let's try to stay on-topic and if you wish to discuss something other than the update, please start a new thread.

Thanks.

 

[bravo14]

I have a log for a One Freq Trunk DMR. Seems all firmware doesn't pick up this one freq 451.6125 either on Conv or OFT. I live 1/2 block over from the place uses DMR. SDS200 show 4-5 signal bars.

 

[Ubbe]

Looks like your log file is full of PLL errors and can't tune to the frequency 99% of the time. At least that's what it looks like.
Can you make another log file when you change the 451Mhz frequency to 420MHz and then look in the file if the PLL text are gone.

/Ubbe

 

[WX4JCW]

For comparison here is my SDS200 on 2 separate OFT DMR systems both UHF and VHF

Sent from my iPhone using Tapatalk Pro

 

[devicelab]

Have a strange issue with my SDS100 and our TRBOWEST commercial wide-area-radio-network using DMR. One site (nearby mountain) works 100% perfectly, etc. Another mountain site doesn't. Frequencies/LCN/CC are correct -- verified. The SDS100 will not lock onto any traffic however. I've tried the NORMAL, INVERTED filters but haven't messed with others as yet. Yes, I've tried multiple antennas (external/internal) and have used filters -- to no avail.

I do not think this is an issue specific to this firmware -- I just haven't been able to check on this issue again. I think it has been happening for a while now. It's been a while but I believe this system/site worked 100% fine with same programming with the 436HP but that was long ago -- and I no longer have the 436HP.

PS. I can use DSD+ and sit on CC and just watch the flurry of activity. Voice channels decode perfectly fine. This is only a 5-frequency site (including control channel.) It's a very busy site.

So I'm a little stumped why this site is not decoding. Could there just be same-frequency traffic screwing with the decode? We do have a lot of DMR around here on UHF.

System: https://www.radioreference.com/apps/db/?sid=7571


Log attached.

 

[Ubbe]

Looks like a bad receiver again and you probably need to send it in for repair. It probably will come back with a note of cold solder joint or J401 replaced.

You could try to enter the control channel frequency (channel+freq+enter) and then edit the audio type to analog only and then use the menu button until you are back at the normal dislay where you are holding on to the channel. Push at the plastic below the display and see if you regain connection and hear the datasignal.

0352042 PLL,04514000
0352054 PLL,04544312
0352114 PLL,04615375
0352128 PLL,04618000
0352140 PLL,04621500
0352153 PLL,04621500
0352164 PLL,04514000
0352175 PLL,04544312
0352186 PLL,04615375
0352197 PLL,04618000
0352210 PLL,04618000

/Ubbe

 

[devicelab]

Looks like a bad receiver again and you probably need to send it in for repair. It probably will come back with a note of cold solder joint or J401 replaced.

If the receiver was bad as you suggest then wouldn't it be failing globally across the scanner? The scanner works fine everywhere else. It decodes P25, DMR, NXDN without any issues. I would think if the receiver was bad then it wouldn't be working at all -- or at least very randomly.

FWIW, here's the output from the working TRBOWEST site that's closest to me:

PS. I don't know what updated but I went to Sentinel and attempted a firmware update and something updated. I already had the 1.10 update so not sure what changed. I wasn't expecting it to update. It would be nice if Sentinel would show us what it's updating prior to actually doing the transfer.

 

[Ubbe]

The last logfile looks better. It sends the 454.397Mhz frequency to the PLL that controls the receive frequency and after 8mS it receives data and that time equals a scan rate of more than 125ch/s. The first number on each line increment with 1mS values.

0417055
0417055 Control CH PLL Set
0417055 PLL,04543937
0417055
0417055 TDMA CH: 1
0417063
0417063 FS DET: 1 FS Type: 1 Terminate: 0
0417063

There's still some other problem as it sometimes tries to do a channel change for up to 5 seconds. It is typical for bad connection between computer board and RF board.

0411825 Control CH PLL Set
0411825 PLL,04543937
0412084 SC0 DA1: 0253 FIR2: 0176
0412084 evnt_idscan_ch_change(C)
0412084 evnt_idscan_ch_change(C)
.
.
0416774 evnt_idscan_ch_change(C)
0416774 evnt_idscan_ch_change(C)
0416775 evnt_idscan_ch_change(C)
0416819 PLL,04543937
0416822 SP0 DA1: 0253 FIR2: 06E8
0416824 SP1 DA1: 0253 FIR2: 06E8
0416840 SC1 DA1: 01EF FIR2: 06E8
0416970
0416970 FS DET: 1 FS Type: 1 Terminate: 0
0416970

Sometimes it takes 260 mS for the PLL to go to the assigned frequency.

0417290 Work CH PLL Set
0417290 PLL,04523500
0417295 SP0 DA1: 0253 FIR2: B7EF
0417295 SC0 DA1: 0253 FIR2: B7EF
0417299 SP1 DA1: 0253 FIR2: B7EF
0417560 SC1 DA1: 00FA FIR2: B2B5
0417560 evnt_idscan_sigrec(V)
0417658
0417658 TDMA CH: 0
0417658 FS DET: 1 FS Type: 2 Terminate: 0

There's some serious problems with your scanner.

/Ubbe

 

[kruser]

/Ubbe

What do you think Ubee, the CN301 connector that some repair tickets say has been replaced or cold solder joints for others as to the real issue.

I wonder if CN301 is really defective as in a bad connector choice or do you think the cold solder joints are really just the solder joints that affix CN301 to the RF board or the mating connector, CN401 to the logic board is really the problem and the actual connector is fine. Then some entire radios are replaced. I wonder if the troubleshooting by some techs shows different possible failures when the failures may all really be the same problem.

I know one thing, most failures that involve repairs seem to be either the connector or cold solder joints but both seem to involve the area around CN301 as evidenced by your suggestion of applying pressure above the battery cover on the rear or just below the display from the front. Both would apply pressure around the area of CN301.
Applying pressure does seem to correct things as can be seen by odd or false to proper RSSI values when pressure is applied or removed.

My connector numbers could be off but they are the connector several report being replaced on their repair tickets.

 

[devicelab]

There's some serious problems with your scanner.

I'm going to try a complete reset to defaults and then program just one site manually and see what happens.

 

[devicelab]

Well something is def weird Ubbe. I wiped the data and reset my user settings. I did custom search from 454 to 455 and for whatever reason on 454.43125 the scanner is deaf. If I tune to 454.39375 then all is perfect. Filter is off. Now I did play with the filters a bit and inverted seemed to improve it very slightly but still not good.

Funny thing is... I did the same test with my BCD325P2 and it's getting 3-4 bars near the window on a rubber duck! /sigh

Off to Uniden it goes...

 

[kruser]

Well something is def weird Ubbe. I wiped the data and reset my user settings. I did custom search from 454 to 455 and for whatever reason on 454.43125 the scanner is deaf. If I tune to 454.39375 then all is perfect. Filter is off. Now I did play with the filters a bit and inverted seemed to improve it very slightly but still not good.

Funny thing is... I did the same test with my BCD325P2 and it's getting 3-4 bars near the window on a rubber duck! /sigh

Off to Uniden it goes...

Just as a test, see what happens with 454.43125 when you enable IFX on that frequency.

 

[devicelab]

Just as a test, see what happens with 454.43125 when you enable IFX on that frequency.

No change.

Update: So I reverted back to the 1.05/1.01.05 firmware and while it still doesn't work -- it does seem to be picking up the RF better.

Also a quick note that if I do press (hard) on the bottom center of the LCD then the RSSI meter briefly lights up fully -- but we're talking like 1/2 sec. I can't get it to stay like that or even have it be intermittent.

If my unit has some defect then the joint must have worked itself 98% free.

 

[nick223]

is there anyway to find the the older firmware files to revert back? I had good reception on a p25 simulcast system before i updated to this firmware now with this firmware im not picking the system up. Just trying to troubleshoot.

 

[bravo14]

Check this link out fw - Google Drive

is there anyway to find the the older firmware files to revert back? I had good reception on a p25 simulcast system before i updated to this firmware now with this firmware im not picking the system up. Just trying to troubleshoot.

 

[Ubbe]

Check that all service types are enabled. I've had the service types reset to the default of only 8 being enabled after an upgrade.

/Ubbe

 

[seth21w]

Can I revert the sub firmware back to original on the sds200? For testing?

 

[bravo14]

Can I revert the sub firmware back to original on the sds200? For testing?

I believe you can.