DSD+ Problem

[DigitalRain]

I have been having problems with I think the DSD+ 1.5 - A few night ago it was working beautifully and now most of the voice that comes over is distorted and then ever so often it comes in clear. Not sure what went wrong. In my screen shot below when it says Pro voice and then has a comb of number and letter is when it is distorted but when it just say pro voice alone that's when it's clear.

Not sure what's going on.

 

[wbswetnam]

I've had the same problem lately monitoring a local police dispatch frequency on DMR. It has happened on two very different set ups: a laptop computer running Windows 10 with an SDR dongle and SDR#, as well as a desktop computer running Windows 7 fed by a tapped scanner. Both computers are running the latest public version of DSD+. For me it has been intermittent. At the moment, I have the laptop / dongle set up going and it seems to be fine. That may change later though. Strange...

 

[DigitalRain]

It is strange, because like I said a few nights ago, it was perfect. And what else is odd is that if I watch a channel pop up on the grid the DSD+ will start but seems like it takes awhile for the sound to show up. TO much of a delay I would say. I have 100 % signal and I'm spot on the control channel on SDR # - So I don't know - it's frustrating. And it's running on Windows 10.

 

[wbswetnam]

If mine starts acting up again, I'll post a screenshot of it for comparison.

 

[DSDPlus]

The raw audio does not look very good. The top one looks noisy and the bottom one looks noisy and off frequency (or being interfered with by an adjacent channel signal)

If DSD+ decoding is bad or delayed, shut down DSD+, stop sampling in SDR#, restart sampling in SDR#, then run DSD+.

 

[DaveNF2G]

Yes, I agree that the difference between the two source audio scopes looks very much like a frequency change.

 

[DigitalRain]

Now I'm having a problem with the Signal side. Keeps saying - Could not open.
I can't figure that one out.

 

[DigitalRain]

The raw audio does not look very good. The top one looks noisy and the bottom one looks noisy and off frequency (or being interfered with by an adjacent channel signal)

If DSD+ decoding is bad or delayed, shut down DSD+, stop sampling in SDR#, restart sampling in SDR#, then run DSD+.

Not sure if i am sampling in SDR# - I try to tune there as best as I can. Then bring up Unitrunker and Start DSD+ the sound wave in the screen shot has always looked like that. A few nights ago it was working perfect DSD+ was clear without Errors. And now I can't get the Signal side to work keeps saying could not open. So I don' t know what I did. From success to nothing. Frustrating.

 

[hans_test]

What sample rate do you use in sdr#? dsd und dsd+ only work correct in my opinion with 2,56 msps.

Regards,

Dietmar

 

[DaveNF2G]

I would try rebooting and starting Unitrunker first. SDRSharp does not give up control of the dongle when it shuts down. In fact, sometimes it remains in Task Manager as an active process for several minutes after shutdown.

 

[dooshorama]

I would try rebooting and starting Unitrunker first. SDRSharp does not give up control of the dongle when it shuts down.

i have not experienced this. even shutting down SDR# is not required.
try switching the Source to something else, i.e. RTL-SDR (TCP). or unplug the dongle and plug it back in.

 

[DigitalRain]

I have SDR# running at the lowest possible MPS and the same on Unitrunker. But now I get no signal on "signal" dongle.

I've tried uninstalling Unitrunker and reinstalling it.

Also reinstalling Zadig thinking that the dongles werent being picked up.

I've tried to delete receivers and Unitrunker seems to crash and when I bring it back up the

Receivers are still there, nothing deleted.

with SDR# I can't seem to find the control channel I need. On the graph it's not showing up when I put the frequency in and hit play. I tried to adjust it but still it does not show up.

 

[Sanscanman]

Are the tuners corrected for in SDR#, and when you use them in Unitrunker ?

 

[DigitalRain]

They were and now some how I lost them. I know it works because I can put a frequency in of a radio station and it comes in fine, but as soon as I change frequency to the control channel for the system I want to monitor its just not there.
And I know the control channel hasn't changed

 

[Sanscanman]

how many tuners are you using?

 

[DigitalRain]

TWO

 

[Sanscanman]

ok do you think there is a chance that some how Unitrunker has reversed your voice and signal receivers, and thrown your PPM corrections off, or do both receivers have the same Correction values after they have warmed up?

 

[DigitalRain]

No reverse but sometime I have to change 1 to 2 and 2 to 1 -meaning changing antennas from antenna 1 to 2 and 2 to 1. but both have the same correction

 

[Sanscanman]

ok I would pull out one of your dongles, and then open SDR# tune the control channel and verify that your PPM corrections are still valid. if not open the gear icon and adjust the correction until you are as close to center as possible, not the correction, write it on a piece of tape and stick it to the dongle. then pull out that dongle and insert the other one and repeat the procedure again.

Close SDR and open Unitrunker. open you signal receiver and verify your ppm correction, set the squelch and drift correct for the receiver. hit start and see if it opens your system window. Next insert the other dongle, and make sure it s selected correctly in Unitrunker, again verify that the PPM correction setting matches the tuner, and again set the squelch and drift correction options and start it. verify that it is tuning to the correct channels and then start DSD and see what you get.

That should work for you as long as the receivers are corrected for, and there is nothing wrong with your drivers or the dongles themselves.

 

[DigitalRain]

OK I will give that a try. thank you for your help.