I like it. No guarantees, but I'll try to add it in as part of the P25 decoder upgrade.
SDRTrunk
- Thread starter DSheirer
- Start date
- Status
I like it. No guarantees, but I'll try to add it in as part of the P25 decoder upgrade.
Awesome
im pretty new to doing any kind of trunking.
did it a couple years ago with the same two dongles I have now which are both E4000's
I am very happy you chose to support these models.
my zip code is 52601 (Burlington Iowa)
im having problems configuring my two dongles.
do I need to use a "patch cable"?
here is my setup:
windows 7 64bit
asus z97i-plus (line in, mic in and speakers out) these are on rear of motherboard.
with my I7 4770K I use the onboard cpu-gpu to get sound and video over hdmi out. (this is usually my default device in windows sound manager)
(2) E4000 devices with drivers installed from zadig (WinUSB) for bulk-in interface 0's
I also have a Stereo Patch cable about 6" long and I can plug it into speaker out and mic in if needed
when I do that windows sound manager will change my default devices to those.
If I want to "hear" I have to change the default playback device to hdmi again.
anyhow that is my setup and I hope I can follow an edacs system in my area or I think there are a couple LTR's
anyhow I cant figure out how to add a "signal/control" system AND the "voice" system.
if someone could make a simple video it would be awesome.
I did search all of google for "sdrtrunk" and there are NO videos
who will be the first
did it a couple years ago with the same two dongles I have now which are both E4000's
I am very happy you chose to support these models.
my zip code is 52601 (Burlington Iowa)
im having problems configuring my two dongles.
do I need to use a "patch cable"?
here is my setup:
windows 7 64bit
asus z97i-plus (line in, mic in and speakers out) these are on rear of motherboard.
with my I7 4770K I use the onboard cpu-gpu to get sound and video over hdmi out. (this is usually my default device in windows sound manager)
(2) E4000 devices with drivers installed from zadig (WinUSB) for bulk-in interface 0's
I also have a Stereo Patch cable about 6" long and I can plug it into speaker out and mic in if needed
when I do that windows sound manager will change my default devices to those.
If I want to "hear" I have to change the default playback device to hdmi again.
anyhow that is my setup and I hope I can follow an edacs system in my area or I think there are a couple LTR's
anyhow I cant figure out how to add a "signal/control" system AND the "voice" system.
if someone could make a simple video it would be awesome.
I did search all of google for "sdrtrunk" and there are NO videos
who will be the first
There's a quick start guide for sdrtrunk located here:
https://code.google.com/p/sdrtrunk/wiki/GettingStarted
First step is to ensure that the software is recognizing both of your dongles. They will show up in the Configuration window under the Tuners branch.
You may have to adjust the PPM frequency correction for each of the dongles. Right-click on each dongle and select 'Show in main display' to show the output from that dongle in the spectral display. Then, adjust the frequency to one of the NOAA weather radio stations and adjust your PPM until the frequency display aligns with the signal you see in the display.
Second step is define a channel that you want to decode with, at a minimum, a source=tuner with the frequency of your LTR channel and decoder=LTR. Check the Enabled box, select Save and the channel should start decoding.
Left click on the decoding channel (highlights in yellow) and then click the Messages tab to see the decoded trunking messages.
sdrtrunk doesn't decode EDACS. A good choice for EDACS is Rick's Unitrunker software.
You won't need to use any patch cables. The audio is all handled internally in the software.
Denny
https://code.google.com/p/sdrtrunk/wiki/GettingStarted
First step is to ensure that the software is recognizing both of your dongles. They will show up in the Configuration window under the Tuners branch.
You may have to adjust the PPM frequency correction for each of the dongles. Right-click on each dongle and select 'Show in main display' to show the output from that dongle in the spectral display. Then, adjust the frequency to one of the NOAA weather radio stations and adjust your PPM until the frequency display aligns with the signal you see in the display.
Second step is define a channel that you want to decode with, at a minimum, a source=tuner with the frequency of your LTR channel and decoder=LTR. Check the Enabled box, select Save and the channel should start decoding.
Left click on the decoding channel (highlights in yellow) and then click the Messages tab to see the decoded trunking messages.
sdrtrunk doesn't decode EDACS. A good choice for EDACS is Rick's Unitrunker software.
You won't need to use any patch cables. The audio is all handled internally in the software.
Denny
I should have mentioned that both E4000 devices are recognized and I create a "new" profile with the correct ppm of each tuner.
from this point on is where I had been running into confusion.
for some reason I thought sdrtrunk did trunking of edac systems.
there are a couple ltr systems in my area that I can try and connect to.
so when there are (two) tuners in a system with no patch cable and no virtual cable sdrtrunk and do trunking just not edacs?
when using (two) tuners will there be "two sites" or "two systems"?
im not sure where the 2nd tuner (voice) gets used at in systems.
thanks and cant wait to try it out with it working or my config working I mean.
still cant believe there is no video yet.
who is gonna be the 1st to put one up on youtube.
very first time I put something in google and no youtube video comes up at all.
just did some testing and I do see messages showing up as you said (up above in the previous post).
how does the "Aux" tab work or what are those options for?
what advantages does the 2nd tuner offer?
when changing the "Gains" settings on the tuners it does not appear to have any affect with the E4000's I have.
the spectrum does not appear to have any affect when messing with those settings.
I tried the "Auto" master gain and I also set it to "Manual" and set all other settings to their lowest values and it does not appear to lower the levels in the "Channel Spectrum" windows
I need to get it lower as I believe it is clipping big time
Last edited:
inchcombec
Member
- Joined
- Jan 17, 2015
- Messages
- 2
- Reaction score
- 0
Hello Denny,
I'm new to playing around with SDR and was actually considering asking about one thing you just mentioned here. Are there any plans to implement EDACS in sdrtrunk or is that just not planned? As well, if it isn't planned is that due to patent/legal issues or technical issues with the software that just won't allow it to work?
I'm just aware of some EDACS radio networks in my area and it would be really nice to get it working in Linux. So far, I haven't come across any way to do so.
Your tuners are treated as a pool of resources. Each tuner can 'tune' to one or more frequencies at the same time, as long as the collective set of channels 'fit' within the bandwidth of the tuner. So, if you only had 1 tuner and you wanted to decode 10 channels that were all right next to each other, you could do that with just one tuner, as long as those 10 channels fit within the bandwidth of the tuner. If you then wanted to tune an 11th channel that was 200 kHz higher and outside of the range of the first tuner, then you would need a second tuner. In many systems, the channels aren't neatly located next to each other, thus two tuners allow you to hit 2 chunks of frequency spectrum at the same time.
If you were decoding an MPT1327 control channel with one tuner, sdrtrunk could use the first tuner to decode the control channel and then use the second tuner to chase the traffic channels that get allocated for that system.
LTR systems don't use a channel map like MPT1327 ... each channel can have an arbitrary frequency. So, sdrtrunk won't chase traffic calls on an LTR trunked system. I suppose if you knew all of the channels and frequencies that it would be possible to scan all of the channels stopping when it found a call, but sdrtrunk doesn't do that currently.
The auxiliary decoders are for decoding things like Fleetsync, MDC1200 and (now) Tait CCDI burst identifiers (ANI) and gps positions. You can find these types of signals on conventional repeaters (use NBFM decoder) or combined with LTR/Passport/LTR-Net systems.
sdrtrunk is setup to allow you to combine a primary decoder and one or more auxiliary decoders on the same channel, depending on the system that you're trying to decode.
Right click on one of your E4000 tuners and select 'Show in main display'. Then, right click on the second tuner and select 'New Display Window'. This allows you to have two spectral displays at the same time, one for each tuner, so that you can see the results when you're changing the gain settings.
I wouldn't use the Automatic gain setting. Set the gain to Manual and start out at the lowest value. Slowly increase the gain a step at a time until you see the overall noise floor start to rise and stop there. Any further increases in gain will only serve to amplify the noise and you won't get any further benefit from more gain.
Denny
Sorry, I don't have any immediate plans to add EDACS. The closest EDACS system (Oneida County) is too weak to receive at my house.
inchcombec
Member
- Joined
- Jan 17, 2015
- Messages
- 2
- Reaction score
- 0
Fair enough. I've got a little bit of programming experience, and absolutely no radio signal processing experience, but do you mind at all if I try to play around with the source code that you've already started, to try to make it work? It is very unlikely I'll actually make it work, but I've got too much time on my hands and it could be fun. If that is okay, if you know of a good place to start looking for documents on the technical operation of EDACS it would be appreciated.
someone please help this guy and the dev out.
I think sdrtrunk has huge potential across all platforms.
java is nice about that.
would love to see edacs and such to be supported.
awesome that is supports the E4000 tuner
That would be great! When you're ready, let me know and I can create an SVN branch in the project where you can store your progress until it's ready for integration. If you want to start a new thread in the Google Support group, I can help with understanding what's needed to add a new decoder.
Denny
I don't think the gain adjustments are working on the E4000's
I have tried and tried to set the main tuner's gains to lowest settings possible and in both their main channel displays it continually is off the charts.
is there something im missing?
I have tried and tried to set the main tuner's gains to lowest settings possible and in both their main channel displays it continually is off the charts.
is there something im missing?
Denny, I just read a few posts before about "tracking" (following) specific users on certain systems. Obviously this isn't possible with LTR, but is there any chance with Passport?
Yes, that's definitely possible since passport uses fixed channel maps. I have only implemented call following in mpt1327 so far and I'm not happy with the approach I used. It's expensive (cpu & memory) to create a channel and dispose it when done. I'm taking a different approach with p25 channels and will reuse the setups. Then I can replicate that approach in passport and mpt.
I checked one of my E4K dongles and the Master gain adjuster appears to work as advertised. If I set the gain to the top 2 or 3 settings, it saturates the dongle and I get replication of the FM broadcast band. But, any of the lower levels seem to work well.
Can you verify the gain adjustment on your dongle with another sdr program to see if you can isolate the issue to either your dongle or to the
sdrtrunk application?
Denny
Last edited:
Hi Denny
I see that you are making progress everyday on the P25 decoding. Is there anything functional, even partially, that we could start playing with? I can't wait to get a new downloadable build...
It's fully functional for C4FM demodulation with auto-gain and auto-frequency correction. It decodes all Trunked and Conventional messages (TDU,TDU Link Control, TSBK,confirmed and unconfirmed PDU,HDU,LDU1/2). I just added decoding of confirmed PDU messages with parsing of SNDCP context management and IPV4 & UDP packet data. I'm not sure yet if I'm going to add support for encryption and over the air rekey.
There are a few of the TDU link control and LDU voice message pieces that still need error checking and I haven't started on an mbe codec yet. That will be a separate java mixer (codec) so that it can be downloaded, compiled and added to the sdrtrunk directory by end users that want to experiment with voice decoding of sdrtrunk output for any of the protocols that use mbe.
The channel state keeps track of the call, data, etc events. I've wired the channel state to recognize most of the TSBK trunking and unconfirmed PDU packets and some of the TDU link control messages. I still have some event processing work to do on the LDU voice packets. Likewise, there's no support for traffic channel following yet.
I'm currently working on the I/Q CQPSK demodulator for LSM simulcast channels. This is going slow because I have to learn the mechanics of PSK demodulation as I go. Fortunately, gnuradio and Max's CQPSK decoder in OP25 are good examples to learn from.
You can download and compile the current code if you want to give it a try. You'll have to uncomment (remove the leading '//') the P25_PHASE1 decoder entry in the decoder enumeration class ( src/decoder/DecoderType.java ) in the getAvailableDecoders() method. This allows the P25 decoder to appear as a decoder option in the gui. Let me know and I can add a build/compile instructions page to the wiki.
I've been holding off on posting a compiled test build ... without full error correction in place, some of the messages have caused the channel state to hiccup. It doesn't crash the software, but it does throw some stack traces to the console.
Denny
We're getting very close ... the CQPSK (LSM Simulcast) demodulator is working good, but still needs some touch up. I'm going to tidy up a few things and I hope to post a first test build within a week.
Attachments
- Status
