Are the 17.6 and 17.8 instances in the same folder therefore using the same config? This problem is different from what was first reported. At first it sounded like an audio problem but now it sounds like it's a reception problem.
Network connection causing SDS200 to go deaf.
- Thread starter reedcom
- Start date
reedcom
Member
Firmware Main 1.10.00
Sub 1.02.01
From what I have been able to find is the firmware has not been updated by Uniden since April 15 of 2019
Sub 1.02.01
From what I have been able to find is the firmware has not been updated by Uniden since April 15 of 2019
- Joined
- Mar 23, 2017
- Messages
- 5
@ProScan I have the same exact issue sir and it is NOT a reception problem at all!
I scan my town with PD on digital and FD on analog on sds200 and proscan I have no reception problems until I'm connected to proscan 17.8
i'm running a moonraker base antenna in the middle of city and analog still goes deaf after 24 hours then reset then another 24 hours. Once I disconnected it's been scanning non stop with no issues.
The statements in bold sounds contradictory to me. So you are saying it's a reception problem when using ProScan 17.8. Is that correct?
Can you revert back to 17.6 to see if that works?
Does the scanner stop on any programmed channels when ProScan is connected?
Are you using the Web Server feature or RSOIP feature? If yes, can you stop those for a test?
Last edited:
reedcom
Member
reedcom
Member
Mine is also mainly VHF analog with 6 VHF DMR and one small part of a county with Oklahoma p25 800mhz. So I am not sure what the cause is. I know if I go back to 17.6 I do not have a problem. I am 3 days back on 17.6 and had no issue. On 17.8 I do not receive anything at all within 18 to 24 hours.
If anyone wants this fixed then send me a Bug Report then I'll send back test files until fixed.
So far, no one has emailed a bug report. Email me (hopefully soon so it won't hold up the next release) and I'll send out the test files until fixed.
I meant when ProScan is connected
reedcom
Member
Update : Bob sent me a updated ProScan 17.8.15. My SDS200 has been running with ProScan for 14 days with no problems.
{deleted}
@ProScan
I too am having to reboot my SDS200, on REV 19.3.0, however wondering if you know what port # the SDS200 uses to send and receive FTP via the editor?
I have my SDS200 setup at work, which is LAN'd to a ASUS (DDWRT) router, connected to an open xfinitywifi WAN client, which is then VPN'd to my home ASUS (Merlin) router via OPENVPN, and controlled with the PROSCAN software VIA URL on my server at my house, small lag but works great so far.
However, I am having trouble with the FTP Favorites Editor, and I am wondering if its a specific port I need to open on the routers.
Thank you sir!
I too am having to reboot my SDS200, on REV 19.3.0, however wondering if you know what port # the SDS200 uses to send and receive FTP via the editor?
I have my SDS200 setup at work, which is LAN'd to a ASUS (DDWRT) router, connected to an open xfinitywifi WAN client, which is then VPN'd to my home ASUS (Merlin) router via OPENVPN, and controlled with the PROSCAN software VIA URL on my server at my house, small lag but works great so far.
However, I am having trouble with the FTP Favorites Editor, and I am wondering if its a specific port I need to open on the routers.
Thank you sir!
Try reverting back to the version that worked before. If it's good then it's probably your antivirus software blocking 19.3
21
Are you trying to access the scanner FTP from outside your network? If no then I don't think doing anything in the router will help. Make sure the readable and writable usernames are different.
I'm going to bump this thread since I'm seeing the same issue. I'm about to contact Uniden with the issue as I actually own 2 SDS200's. One of them I just bought 2 months ago (New from Ham Radio Outlet) and it's exhibiting this problem. Within a day or 2 of running while connected to Ethernet and also Proscan it will lose all audio - there is no audio available over the Ethernet, the speaker or the headphone jack until I restart the SDS200. Proscan is still connected and reports that connection is fine - and will record completely empty files when a signal is received. This only happens with the newest SDS200 even though both are on the same (latest) firmware and both Proscan instances are the same version, on the same machine. I have swapped the radios and the behavior follows the radio - not the Proscan instance. I have factory reset the SDS200 and copied the same settings on the 'good' one with Sentinel and shot it onto the new one and no change. It's like the receiver (not the amp) stops outputting audio. I have also swapped the power supply on the SDS200 and put it onto a UPS to rule out extraneous power fluctuations (even though the 'good one' is not and has run for a solid year where I've never seen this behavior, not even once). Has anyone uncovered any more details on this? If I can figure out how to flash the firmware over the top of itself I'll try that just to rule that out as well. But at this point if I don't learn anything else I'm going to contact HRO and/or Uniden this week. I've spent about a month trying to troubleshoot this (it's not my first rodeo - I was in commercial product development for electronics for years) and I am not closer to resolving it. Thanks in advance for any more insight!
phd-2, Can you swap the SD card between the SDS200s to see if the problem follows?
Just acknowledging this response and I'll do that today - I'll have a pretty good idea if that has any impact within 2 days.
neilharvey94044
Member
- Joined
- Dec 14, 2020
- Messages
- 28
I've just started exploring the API the SDS200 exposes. I'm an old developer. It looks like the rtsp implementation is non-conforming to rfc2326 in at least one way. The OPTIONS request seems to set the state machine going, which from reading the spec should not be the case. The OPTIONS request should not alter the scanner's state, i.e. it should be idempotent. Attempting a second OPTIONS request gets no response and the scanner then becomes unresponsive for rtsp. So the impression I'm getting is clients must submit requests in the ideal order with no variation...e.g. OPTIONS, DESCRIBE, SETUP, and then PLAY as I've seen them do in WireShark. This is just one item I've found with the rtsp implementation, there may be others. Perhaps what's needed is the scanner supporting an out of sequence TEARDOWN request. Though maybe it does, I haven't tried it as yet.
In any case as the ProScan support account said...it's finicky.
This wouldn't surprise me at all - I was in commercial product development for almost 30 years and Unidens team does not impress me - my problem extends way beyond RTSP as I lose all audio completely - ironically the RTSP connection stays up when this happens but the audio is silent just like locally on the radio. Searching RR here I've found several people that have encountered this problem in the last few years since the SDS200 came out. That said, right now I've not had the audio go silent this week which is encouraging. The jury is still out though as it's not the longest it's gone working OK. It's just that on average it drops within 2-3 days. I'm keeping an eye on it and thanks for the input.
I know the SD card can cause strange things to happen so it would be interesting for someone that experiences loss of audio out of the scanner speaker to try another SD card. I'm not sure if the rtsp audio is making the processor and/or the SD card work harder or what.
On the rtsp implementation: It could use improvements. I know if the scanner rtsp module doesn't receive the TEARDOWN command due to the computer rebooting or a program accessing the rtsp, exits abnormally, then the rtsp audio module goes into never never land. The only way to get it back is either reinsert the USB cable then let the scanner reboot or power cycle the scanner. Uniden could have implemented a watchdog time that reinitiates the rtsp audio module if the rtsp audio is lost.
I think the engineering teams are capable. It could be they are short staffed and/or have higher priorities. I would say it has more to do with the management. We haven't heard of a replacement for UPMan. I would like to see the rtsp audio fixed along with all the missing features, and the built in web server has a lot of potential that will never come to light.
Perhaps if it starts to happen again, try another SD card and see what happens.
Similar threads
SDS100/SDS200:
Proscan WAN port forwarding
