DSD+ was working on P25, but not now?

[drsprite]

I've been using DSD+ for about a year on my feed, and on Saturday it stopped working.

I'm using DSD+ 1.101pt

I had assumed I had a hardware failure, so I replaced the RTL-SDR this morning, and it's the same problem. When the frequency goes active in SDR#, DSD+ throws a lot of errors.

Like ERR3, ERR4, Invalid DUID, etc.

After turning the gain up on my RTL-SDR to 100%, DSD+ is *trying* to decode it, and I can hear a glimpse of a voice, but then nothing and a lot of digital tones come through.

The frequency is using P25 with no trunking.

The one thing I do know is that it's not a problem with the hardware since I'm seeing the same thing from before and after..

Is it possible DSD+ needs to be updated?

I'm at a loss trying to fix my feed. Any suggestions on what to check for?

 

[MaximusTheGreat]

Maybe they went Encrypted as a result of your feeds to the public. The moment they flipped 5hr switch you won't decode anything. That's the only conclusion that I can think of based on your scenario.

 

[drsprite]

That was what I was thinking too. I can decode some transmissions, but not all.

Any thoughts on how to confirm if it's encrypted?

EDIT: Actually. I just plugged in a new antenna into the replacement RTL-SDR, and with the gain at 100%, I am getting better results. Not sure what changed, but if it was encrypted, then I wouldn't get anything, right?

I believe they have a repeater near my location, so I suppose they could have having a problem, and I'm trying to catch the transmission off their other tower further away

 

[MaximusTheGreat]

To my knowledge, I would say is by having a digital scanner sit on the frequency . With that scanner you would be able to either see on the screen or hear a selectable noise of Encryption being used.

I myself enjoy this hobby as much as anyone. Feeding Public Service to the General Public is a huge time bomb ready to explode in one's face. You could've enjoyed your hard work of setting up DSD+ and listen to them whenever you wanted. But now that you decided to feed it, you screwed yourself and others in your area from not listening to what's going on. That's being GREEDY. Feeders are DESTROYING our hobby. Yes, I'm a feeder. But I feed HAM bands. I feed something that's not going to piss anyone off.

I hope this adds to the "Lesson Learned" that departments will not put up with the general public listening to them. By the way, general public does not cover HAMs or Scanner Enthusiasts. It covers Dee Jones with an Android and a scanner app.

 

[drsprite]

Thanks for the help. It seems you're passionate about this, and I will not be your target. Also, I re-read your statement, and I did mention they're using P25, so that confirms they're already using encryption. Something I've been used to for a year or longer.

Anyways, if anyone else has anything more constructive to add, without attacks, I'd appreciate it.

 

[dave3825]

That was what I was thinking too. I can decode some transmissions, but not all.

Any thoughts on how to confirm if it's encrypted?

Look in the dsd event window.

I get this on a dmr system. Its saying encrypted group call on slot 2

+DMR slot2 BS VC6
Slot2: Enc GC TG=304201 RID=31146

What system are you monitoring?

 

[drsprite]

Look in the dsd event window.

I get this on a dmr system. Its saying encrypted group call on slot 2

+DMR slot2 BS VC6
Slot2: Enc GC TG=304201 RID=31146

What system are you monitoring?

I'm monitoring the local PD.

Sorry, I knew it was encrypted. They're using P25. I was thinking they went trunked, but they didn't.

In the Event Log I see the Group call, the TG and RIDs. I'm just seeing a lot more errors than I used to and not as much of a success rate at decoding. And I had to crank the gain to 100%.

So part of me is wondering if they're experiencing trouble on their equipment, and I'm picking up on that with my changes.

 

[slicerwizard]

Errors have nothing to do with encryption. An accurate answer requires a raw audio sample, if you're willing to provide one.

 

[drsprite]

Errors have nothing to do with encryption. An accurate answer requires a raw audio sample, if you're willing to provide one.

Sure, just a standard wav file from DSD+, or do I need to run a special command flag to get the raw audio? Or no DSD+, and just raw audio from SDR#?

Just making sure I understand

 

[MaximusTheGreat]

Also, I re-read your statement, and I did mention they're using P25, so that confirms they're already using encryption.

You maybe confused a tad but Just to clarify, P25 is a Digital Mode. P25 either Phase 1 or Phase 2, comes in non Encrypted and Encrypted. What determines if it's Encrypted or not, is the Department or Agency of that system.

If your able to hear P25 clearly or garbled then it's non Encrypted. P25 Encrypted can not be decrypted by average computing machines.

P25 can not be picked up with an analog scanner. P25 can be picked up with a digital scanner or DSD.

 

[M105]

P25 is digital but not necessarily encrypted. Don't confuse digital modes with encryption. Also, Slicerwizard is correct that encryption will not stop DSD+ from decoding data or cause it to throw errors.
---
Back to your problem. Check your settings on SDR#. Make sure audio filtering is turned off. For whatever reason my copy of SDR# will forget its settings sometimes after closing.
---
I'll second the motion on not feeding scanner traffic to the public. I use RadioFeed but with a password for my own remote use as well as a few trusted friends.

 

[slicerwizard]

Sure, just a standard wav file from DSD+, or do I need to run a special command flag to get the raw audio? Or no DSD+, and just raw audio from SDR#?

Just making sure I understand

Just press 'R' in DSD+ to start/stop recording. 5 or 10 seconds of voice traffic should do.

 

[br0adband]

*snip*

Seriously?