Provoice listening
- Thread starter John1984
- Start date
- Status
Welcome! Yeah you just need (1) Unitrunker, (2) DSD+ and (3) a virtual audio cable program (i.e. the free version of VB-Cable). This tutorial might help you get started. Keep in mind, with this setup Unitrunker decodes the the ANALOG EDACS talkgroups and logs all the system data (i.e. voice grants, radio affiliations etc). DSD+ ONLY decodes the Provoice Audio, it won't decode Analog EDACS TG's or display/log any EDACS system data whatsoever - that is all handled by Unitrunker.
But like I said, once you get everything configured it will work great, and you can even leave it running 24/7 to catch new talkgroups etc.
Hi Natedawg, and thank you. I'm just waiting on my rtlsdr dongles to turn up so I can have a play.
I've read the tutorial several times and I get the basic idea of it, feeding the audio from unitrunker via a virtual audio cable to dsd. I reckon I'm going to get stuck however.
Where I am we have a trunking system and it contains both analogue and digital provoice.
I know all the analogue talk groups and frequencies. I just need to learn the talk groups and frequencies for the digital channels. Would I be best using unitrunker or sdr# to track these down? Thanks again
Sent from my SM-G920I using Tapatalk
I've read the tutorial several times and I get the basic idea of it, feeding the audio from unitrunker via a virtual audio cable to dsd. I reckon I'm going to get stuck however.
Where I am we have a trunking system and it contains both analogue and digital provoice.
I know all the analogue talk groups and frequencies. I just need to learn the talk groups and frequencies for the digital channels. Would I be best using unitrunker or sdr# to track these down? Thanks again
Sent from my SM-G920I using Tapatalk
Thanks tglendye, so excited yet disappointed at the same time. Unfortunately where I am, our frequencies go up into 869mhz and this is blocked on unidens two scanners that have the provoice update
Sent from my SM-G920I using Tapatalk
Sent from my SM-G920I using Tapatalk
Howdy John,
Are you just wanting to listen live or do you want to log and record all of the traffic?
First you will want to download SDR#. Read here. This allows you to determine the ppm offset for your RTLs. Set the frequency to one of the control channels, then wait ~10 for it to warm up. Open the configure button and adjust the Frequency correcting (ppm) until you are dead center on a known frequency. Depending on which RTL you have, it'll likely be in the ballpark of 30-60. See step 13 in the above link for what this window looks like. Repeat for the other RTL. Save the numbers, you will input them into UniTrunker.
In UniTrunker, add both RTLs as receivers. In the first, input your frequency correction, enable drift correct, and select the correct "RTL Device" on the info tab. In the VCO tab, the Role will be "Signal". Both audio outputs should be unspecified. Put squelch at ~40. "Park" is the frequency of the control channel. (Note if you are unsure of the control channel, tune to all of the system channels in SDR#, you will know when you are on the control channel...). Make sure both EDACS system types are selected at the bottom in the "Signal" section. Start the receiver.
For the second receiver, select the correct device, enable drift correct, and input the frequency correction. On the VCO tab, Role is "Voice," enable deemphasis, Audio Output is to your speakers, Digital output is to your virtual audio cable (use VB cable for free), squelch around 40, enable "Analog" and "ProVoice". Start the receiver.
Your DSD+ VC.bat file should look something like this (right click and edit with notepad):
You will modify the input (-i) and output (-o) attributes according to your system setup, which will be listed when you run DSD+. Double click on the VC.bat file to run DSD.
You should be up and running. If you want to join as a premium RR member, you can download the talkgroups. If you want to have more fun, figure them out on your own.
Feel free to PM or email me.
Good luck.
Justin
Are you just wanting to listen live or do you want to log and record all of the traffic?
First you will want to download SDR#. Read here. This allows you to determine the ppm offset for your RTLs. Set the frequency to one of the control channels, then wait ~10 for it to warm up. Open the configure button and adjust the Frequency correcting (ppm) until you are dead center on a known frequency. Depending on which RTL you have, it'll likely be in the ballpark of 30-60. See step 13 in the above link for what this window looks like. Repeat for the other RTL. Save the numbers, you will input them into UniTrunker.
In UniTrunker, add both RTLs as receivers. In the first, input your frequency correction, enable drift correct, and select the correct "RTL Device" on the info tab. In the VCO tab, the Role will be "Signal". Both audio outputs should be unspecified. Put squelch at ~40. "Park" is the frequency of the control channel. (Note if you are unsure of the control channel, tune to all of the system channels in SDR#, you will know when you are on the control channel...). Make sure both EDACS system types are selected at the bottom in the "Signal" section. Start the receiver.
For the second receiver, select the correct device, enable drift correct, and input the frequency correction. On the VCO tab, Role is "Voice," enable deemphasis, Audio Output is to your speakers, Digital output is to your virtual audio cable (use VB cable for free), squelch around 40, enable "Analog" and "ProVoice". Start the receiver.
Your DSD+ VC.bat file should look something like this (right click and edit with notepad):
You will modify the input (-i) and output (-o) attributes according to your system setup, which will be listed when you run DSD+. Double click on the VC.bat file to run DSD.
You should be up and running. If you want to join as a premium RR member, you can download the talkgroups. If you want to have more fun, figure them out on your own.
Feel free to PM or email me.
Good luck.
Justin
Just to clarify, although a premium RR subscription is quite helpful for many things, I wouldn't count on getting accurate or up-to-date info re: provoice talkgroups.
Also keep in mind, Provoice does support encryption. And (unlike the newer protocols) Provoice has no encryption status bit allowing for automatic display/logging re: Encryption status of a voice grant. Therefore, you have to listen to the audio of each Provoice TG to verify whether it's listenable (keeping in mind loose lips sink ships...)
slicerwizard
Member
Looks like everyone is assuming that this is ProVoice on a trunking system. Is it?
My experience is that the current crop of TCXO dongles should be much closer. At 935 MHz, my 0.5 ppm NooElec is high by about 650 Hz (+0.7 ppm) and my 1.0 ppm RTL-SDR.com is low by about 930 Hz (-1.0 ppm). Look at multiple 800/900 MHz sites for best results unless there is a particular site for which you somehow know the exact frequency (error). The calibration of service equipment and transmitters (especially those in locations that are difficult to get to and rarely serviced) can vary surprisingly widely. When working for a local commercial two-way radio shop, I remember having to convince a local big-name manufacturer-affiliated shop (
) that their monitor was off after finding more than one of their sites to be significantly off by the same amount. Well, I buy the cheap ones! But even my NooElec is several dozen ppm off. The RTL I just got from Flight Aware is perfectly centered, however. I might buy another one to dedicate to trunking for a long term test. I always figure it is best to correct to the control channel you'll be following (which UniTrunker will do automatically, anyways). I suppose it is best to compare several frequencies if scanning multiple trunked channels or conventional scanning -- excellent point.
OP, in the even it's not a trunked system you're after, you can either fool UniTrunker by setting "Signal" role with the Audio Out to DSD+ or use SDR# to pipe the audio for each conventional channel. If there are multiple conventional channels close together, setup a signal VCO for each one in UniTrunker. If there are conventional channels out of reach of the bandwidth of two RTLs, then utilize SDR#'s scanning plugin. You'll only be able to catch one conversation per RTL and will have to figure out how to keep the 2nd RTL from stopping on the same frequency as the first.
By the way, you can run multiple instances of DSD+, just put each one in its own folder. Here's my script to turn them on easily:
The timesouts are so Win10 won't sit there and flash orange taskbar icons at you all day, like a road construction truck.
And this turns it off:
OP, in the even it's not a trunked system you're after, you can either fool UniTrunker by setting "Signal" role with the Audio Out to DSD+ or use SDR# to pipe the audio for each conventional channel. If there are multiple conventional channels close together, setup a signal VCO for each one in UniTrunker. If there are conventional channels out of reach of the bandwidth of two RTLs, then utilize SDR#'s scanning plugin. You'll only be able to catch one conversation per RTL and will have to figure out how to keep the 2nd RTL from stopping on the same frequency as the first.
By the way, you can run multiple instances of DSD+, just put each one in its own folder. Here's my script to turn them on easily:
The timesouts are so Win10 won't sit there and flash orange taskbar icons at you all day, like a road construction truck.
And this turns it off:
Thanks so much guys.
In regards to using the Provoice update for the X36 scanners, unfortunately they wont work where I am located as our frequency goes in 869Mhz and this is blocked on these scanners. I currently use a UBCD396XT and if they ever release provoice for this it would be great.
So I received the dongles today. So far I have installed SDRSharp, Unitrunker and DSD. Seems to be working as I can listen to radio with SDRSharp.
Small steps, small steps ;p
In regards to using the Provoice update for the X36 scanners, unfortunately they wont work where I am located as our frequency goes in 869Mhz and this is blocked on these scanners. I currently use a UBCD396XT and if they ever release provoice for this it would be great.
So I received the dongles today. So far I have installed SDRSharp, Unitrunker and DSD. Seems to be working as I can listen to radio with SDRSharp.
Small steps, small steps ;p
Thanks Aggie, I just want to listen to start off with and look at logging down the track when I get the hang of it!! Is it quite important to set the PPM? Do you think the digital provoice would use the same channels as the analogue?
John,
Usually the EDACS systems use the same channels for both analog and digital (Provoice) traffic. I'm sure there is a word around, but I don't know how to listen to both on the same settings with SDR#.
For digital voice decoding, I think the frequency correction is incredibly important. You need to be centered.
That's too bad the channel is in the cell band. Of course we have to be protected from ourselves, and the consumer equipment manufacturers in our country roll over dead from the slightest mandate from the feds.
Usually the EDACS systems use the same channels for both analog and digital (Provoice) traffic. I'm sure there is a word around, but I don't know how to listen to both on the same settings with SDR#.
For digital voice decoding, I think the frequency correction is incredibly important. You need to be centered.
That's too bad the channel is in the cell band. Of course we have to be protected from ourselves, and the consumer equipment manufacturers in our country roll over dead from the slightest mandate from the feds.
Regarding frequency drift correction, you will know your RTL is warmed up and stable once in SDR#, while you are fairly zoomed in on the waveform, it is completely vertical for sometime, rather than diagonal towards the direction of the shift.
You can test on a single frequency from SDR# to DSD+. Just set the audio output to your DSD+ input, but be sure to turn off "Filter Audio" under the Audio subgroup. Also turn off Audio Noise Reduction or any other filter. Adjust your bandwidth down until it covers mostly just the signal of interest in the waterfall, perhaps a little wider. Make sure the gain to DSD+ is not too hot. Use the DSD+ Source Audio window to determine a good setting. Don't let it clip. When feeding from UniTrunker, this is not an issue.
You can test on a single frequency from SDR# to DSD+. Just set the audio output to your DSD+ input, but be sure to turn off "Filter Audio" under the Audio subgroup. Also turn off Audio Noise Reduction or any other filter. Adjust your bandwidth down until it covers mostly just the signal of interest in the waterfall, perhaps a little wider. Make sure the gain to DSD+ is not too hot. Use the DSD+ Source Audio window to determine a good setting. Don't let it clip. When feeding from UniTrunker, this is not an issue.
Thanks Aggie, you are a champion. With your simple instructions I was able to get it all working last night! Yes you were right, the digital provoice uses the exact same channels as the analogue. I never even though about adjusting the bandwidth, I had better check that!!! As I say, it all works, some of its a little rusty, especially the digital. Just have to work on getting that right.
Sometimes the dsd shows this, does it mean anything?
Sometimes the dsd shows this, does it mean anything?
Attachments
That is showing decode errors. The inability to sync meas it is even worse. Does it affect the voice quality or does it occur only at the end of calls?
How does the analog voice sound? Is it clear or scratchy?
If it is degrading the voice, there are a number of approaches to try to improve it. First, what system are you trying to monitor and how close are you? Antenna modifications might improve reception. Are you using the small black antenna that ships with most of the RTLs?
Next, it might help to fine tune the gain settings. Sometimes that can yield slight improvements. Use SDR# to play around with optimum gain settings for one of the frequencies (you want the largest difference between the top of the signal of interest and the noise floor). In UniTrunker, the gain setting is roughly 10 times the scale in the SDR# configure window, I believe. Turning off auto gain in UniTrunker and forcing a good value sometimes improves things for me. It takes a lot of trial and error, though.
Finally, there are settings in DSD+ to fine tune the decoding. I've had mixed results with this. No doubt it can improve the decode; however, I disregarded this approach since the best "fine tune" varied between calls on the same system. You can give it a try if you want. There are instructions for this in the DSDPlus.txt readme file in your DSD+ folder. I think this forum page is going to have about the best description of the process I can find on here. If you want to get into it and have questions though, get back to me, and I will walk you through it.
Disregard all of this if those errors aren't occurring while they are talking. But if that is during voice traffic, then you'll want to try to fix it. I bet you thought you were done with the "fun" stuff, but it never ends...
How does the analog voice sound? Is it clear or scratchy?
If it is degrading the voice, there are a number of approaches to try to improve it. First, what system are you trying to monitor and how close are you? Antenna modifications might improve reception. Are you using the small black antenna that ships with most of the RTLs?
Next, it might help to fine tune the gain settings. Sometimes that can yield slight improvements. Use SDR# to play around with optimum gain settings for one of the frequencies (you want the largest difference between the top of the signal of interest and the noise floor). In UniTrunker, the gain setting is roughly 10 times the scale in the SDR# configure window, I believe. Turning off auto gain in UniTrunker and forcing a good value sometimes improves things for me. It takes a lot of trial and error, though.
Finally, there are settings in DSD+ to fine tune the decoding. I've had mixed results with this. No doubt it can improve the decode; however, I disregarded this approach since the best "fine tune" varied between calls on the same system. You can give it a try if you want. There are instructions for this in the DSDPlus.txt readme file in your DSD+ folder. I think this forum page is going to have about the best description of the process I can find on here. If you want to get into it and have questions though, get back to me, and I will walk you through it.
Disregard all of this if those errors aren't occurring while they are talking. But if that is during voice traffic, then you'll want to try to fix it. I bet you thought you were done with the "fun" stuff, but it never ends...
- Joined
- Apr 26, 2016
- Messages
- 19
- Reaction score
- 0
Hello. Im new to all of this. New to scanning, new to sdr, new to this thread. Complete noob. I got two SDR's. I've played in SDR#, and now I've got a couple of trunking systems monitored. Analog is easy peazy, but the provoice has been giving me absolute hell. Sometimes the voice is good, sometimes its really garbled and distorted, and everything in between, and DSD+ shows lots of errors throughout sometimes as screen captured earlier in the thread. Still using the crap antennas that came with the SDR's. I've been thinking (hoping) its just the antenna setup but I think I might have something wrong in unitrunker as well. Please feel free to correct me, but could the bandwidth being 12.5mhz on each frequency be the problem? It was the default and I just left it there, but in SDR# on analog channels if the bandwidth is too narrow it cuts out part of the transmission. Again, take pity on me in your responses, I am a stupid noob
- Status
Similar threads
