DSD+ Fast Lane 2.165 - TCP connect error = 10061 - Trunked P25

[AB9NN]

I am running two RTL-SDR dongles on Windows 10 PC. Powered USB 3 hub into fastest USB 3 port. The _0 - RUN file, attached, is my start process. The two log files, names altered to get this system to upload them, are also attached. No audio because the TCP connection is not made. I don't see my error. Perhaps a much more knowledgeable set of TCP eyes than mine may help. The first half of the process is working well and scrolling tons of data and spewing system codes, etc. I have dutifully added frequencies, etc. to the frequencies file of DSD+. Seems to be lacking the link for the voice audio.

 

[GTR8000]

For whatever it's worth, it has been long established that these Realtek based dongles (RTL-SDR, NooElec, etc.) do not particularly like USB 3.0/3.1 ports. They prefer USB 2.0 ports and hubs. If you have a USB 2.0 port/hub available, try that instead. Obviously on some newer machines this may not be an option if only USB 3.0/3.1 ports are available.

 

[AB9NN]

For whatever it's worth, it has been long established that these Realtek based dongles (RTL-SDR, NooElec, etc.) do not particularly like USB 3.0/3.1 ports. They prefer USB 2.0 ports and hubs. If you have a USB 2.0 port/hub available, try that instead. Obviously on some newer machines this may not be an option if only USB 3.0/3.1 ports are available.

Thanks. I did try them on USB 2 ports on my PC and they did not work as was as in the current configuration - they work like a charm with FMP24 and DSD+ for all conventional frequencies and all other softwares work with them nicely including a competitive P25 trunking decoder. I would have thought I would have run in to much more trouble long ago if that really was completely true. Not calling you a lier but just laying out my results so far... Could it be some port conflict or some internal configuration issue with Windows or something other than the dongles?

 

[AB9NN]

For whatever it's worth, it has been long established that these Realtek based dongles (RTL-SDR, NooElec, etc.) do not particularly like USB 3.0/3.1 ports. They prefer USB 2.0 ports and hubs. If you have a USB 2.0 port/hub available, try that instead. Obviously on some newer machines this may not be an option if only USB 3.0/3.1 ports are available.

Would use of VB Cable be a work-around?

 

[slicerwizard]

I am running two RTL-SDR dongles on Windows 10 PC. Powered USB 3 hub into fastest USB 3 port. The _0 - RUN file, attached, is my start process. The two log files, names altered to get this system to upload them, are also attached. No audio because the TCP connection is not made. I don't see my error. Perhaps a much more knowledgeable set of TCP eyes than mine may help.

Based on your batch file, VC DSD+ can't start until VC FMP24 has exited, so there is no way for VC DSD+ to make a TCP connection to the now-nonexistent VC FMP24.

It also looks like VC FMP24 can't start until CC DSD+ terminates.

The first half of the process is working well and scrolling tons of data and spewing system codes, etc. I have dutifully added frequencies, etc. to the frequencies file of DSD+. Seems to be lacking the link for the voice audio.

Yes, it works fine because you have CC FMP24 and CC DSD+ running simultaneously.


C:\_Files\SDR - Software Defined Radio\sdrsharp-x86\dsd+FASTLANE-P25

What is that line supposed to do?

 

[AB9NN]

Light-bulb click! There was a missing CHDIR in front of that line. Inefficient I know but I was advised to run multiple folders for versions of DSD+ especially while experimenting. So, the first thing I do is change to the correct folder for the particular experiment. I also saw that I needed START commands in front of my other lines for FMP24 and DSDPlus. After I did those and re-started everything started-up normally. Graced with a quick call I saw the second instance of FMP24 come to life and the clear P25 audio decoded promptly. I started down a P25 path and wondered off into a grand adventure with conventional NXDN, FMN and DMR and did some shortcuts and figured out where to get frequencies and how to work with <EOF> and how to leave off the < to make a quick change to a ScanList for FMP24, etc.. By the time I got back to this quite some time later I didn't see the errors above. Thanks for the light-bulb! Error on original post is cleared.