DSDPlus NXDN - no voice audio

[Facsimile]

I have been playing round with DSDPlus (fast lane) and really like it. The only issue I am having is that I cannot hear any NXDN voice calls while honed in on the control frequency. It appears to be trunk tracking. If I manually tune to a non-control channel, it decodes but only one side of the conversation as expected. Interestingly, it appears everything is being detected and decoded, but I get no decoded audio through my speakers. I tested the same setup with my SDS100 and have had no issues. Everything is clear. I used the same antenna and coax when testing the two. Keep in mind, I have had no issues with P25, DMR, or Con+.

In my DSDPlus.frequencies file, I added the following: NEXEDGE96, 107, 1, 0, 452.3875, 0.0, 0

Everything in DSDPlus.exe is set to default including the Input, Output, Decoder, and Control drop downs. The system in question can be found here: J and K Communications Diga Talk Trunking System, Various, Indiana. What obvious key configuration am I missing?

Thanks!

 

[gh6406]

Do you have two dongles or one that supports two channels at once?

 

[LimaZulu]

In my DSDPlus.frequencies file, I added the following: NEXEDGE96, 107, 1, 0, 452.3875, 0.0, 0

You only added the control channel frequency. NXDN does not transmit channels with their frequencies (so to say) like P25 for example, so your receiver does not know what frequency is channel 514 and the rest of them. You have to add the rest of the channels from that system just like you did with CC channel.
Apart from that, you assigned CC to channel 0, where as far as I can see it's actually 192. Your line that you entered should look like that
NEXEDGE96, 107, 1, 192, 452.3875, 0.0, 0..

 

[R0am3r]

NXDN does not transmit channels with their frequencies (so to say) like P25 for example

Don't assume all NEXEDGE systems work this way. Some NEXEDGE systems use Direct Frequency Assignment (DFA) and behave like a P25 system. When you monitor a DFA system, you only need the Control Channel frequency. And before someone corrects me... the CC frequency may change periodically.

 

[Facsimile]

Do you have two dongles or one that supports two channels at once?

I have two dongles.

You only added the control channel frequency. NXDN does not transmit channels with their frequencies (so to say) like P25 for example, so your receiver does not know what frequency is channel 514 and the rest of them. You have to add the rest of the channels from that system just like you did with CC channel.
Apart from that, you assigned CC to channel 0, where as far as I can see it's actually 192. Your line that you entered should look like that
NEXEDGE96, 107, 1, 192, 452.3875, 0.0, 0..

Ok, I added the following to the .frequencies file:

NEXEDGE96, 107, 1, 115, 451.425, 0.0, 0
NEXEDGE96, 107, 1, 125, 451.55, 0.0, 0
NEXEDGE96, 107, 1, 153, 451.9, 0.0, 0
NEXEDGE96, 107, 1, 192, 452.3875, 0.0, 0
NEXEDGE96, 107, 1, 196, 452.4375, 0.0, 0
NEXEDGE96, 107, 1, 514, 451.4125, 0.0, 0

The channel activity display and the event log both show a lot of activity with aliases but still no audio. I don't know how much difference this makes but the Ch # being found using DSDPlus are 115, 125, 153, 192, 514, and 772. The last two are different than what is on the database link.

 

[dave3825]

Ok, I added the following to the .frequencies file:

NEXEDGE96, 107, 1, 115, 451.425, 0.0, 0
NEXEDGE96, 107, 1, 125, 451.55, 0.0, 0
NEXEDGE96, 107, 1, 153, 451.9, 0.0, 0
NEXEDGE96, 107, 1, 192, 452.3875, 0.0, 0
NEXEDGE96, 107, 1, 196, 452.4375, 0.0, 0
NEXEDGE96, 107, 1, 514, 451.4125, 0.0, 0

The last two are different than what is on the database link.

CH ID	Frequency
115	451.425
125	451.550
153	451.900
192	452.3875c
196	452.4375c
514	451.4125

Its early and I am still on first coffee. Looks like what you added matches what's listed in db. Don't see a 772 in what you entered or in the db. Can you post a screenshot of your channels window?

 

[LimaZulu]

Don't assume all NEXEDGE systems work this way. Some NEXEDGE systems use Direct Frequency Assignment (DFA) and behave like a P25 system. When you monitor a DFA system, you only need the Control Channel frequency. And before someone corrects me... the CC frequency may change periodically.

I do know that. But first of all Nexedge DFA is highly rare and second - that's not the scope of this thread and for the sake of simplicity don't even mention any of all other possibilities

I have two dongles.


Ok, I added the following to the .frequencies file:

NEXEDGE96, 107, 1, 115, 451.425, 0.0, 0
NEXEDGE96, 107, 1, 125, 451.55, 0.0, 0
NEXEDGE96, 107, 1, 153, 451.9, 0.0, 0
NEXEDGE96, 107, 1, 192, 452.3875, 0.0, 0
NEXEDGE96, 107, 1, 196, 452.4375, 0.0, 0
NEXEDGE96, 107, 1, 514, 451.4125, 0.0, 0

The channel activity display and the event log both show a lot of activity with aliases but still no audio. I don't know how much difference this makes but the Ch # being found using DSDPlus are 115, 125, 153, 192, 514, and 772. The last two are different than what is on the database link.

First I am not sure if this is a major thing in DSD but do round frequencies to the fifth sign after decimal point.
And second but most important how is your DSD configured - passive digital monitor, two dongle trunk tracker or combined CC/VC monitor?

 

[Facsimile]

CH ID	Frequency
115	451.425
125	451.550
153	451.900
192	452.3875c
196	452.4375c
514	451.4125

Its early and I am still on first coffee. Looks like what you added matches what's listed in db. Don't see a 772 in what you entered or in the db. Can you post a screenshot of your channels window?

The 772 and comes from what the control channel gives me. It automatically shows up here:

I do know that. But first of all Nexedge DFA is highly rare and second - that's not the scope of this thread and for the sake of simplicity don't even mention any of all other possibilities

First I am not sure if this is a major thing in DSD but do round frequencies to the fifth sign after decimal point.
And second but most important how is your DSD configured - passive digital monitor, two dongle trunk tracker or combined CC/VC monitor?

I have it set as Combined CC/VC monitor.

 

[Facsimile]

Well I just don't understand it. It works now. I plugged in my headphones just to give it a try and it worked. Unplugged my headphones and voilà speakers now work and can hear everything. Sorry to waste everyone's time.

Still curious though as to why 772 shows up as a channel? How would I find the frequency to this channel since it is not documented?

 

[dave3825]

Still curious though as to why 772 shows up as a channel?

How would I find the frequency to this channel since it is not documented?

Look at the 3 licenses associated with that site. See if they contain any other freqs other than the 6 listed in the db.

FCC Callsigns:	WPSP939 WPTD404 WQAT691

 

[LimaZulu]

It seems that some it was audio device related issue that you had Glad you found it

Channel 772 may be a result from bad frame decoding. I happens to me as well from time to time during extended decoding sessions Or of course it could be undocumented channel. How to find it....scan for it You could read this thread and try to use those calculations to map the missing channel. Just keep in mind that based on license, channels may not always stick to those formulas.

 

[cg]

If you seem to still miss some traffic, I think there is an error in the DB and also a missing freq (at least one)
Ch 514 is likely 461.4125 and not 451.4125
Ch 772 is likely 464.6375
Both are valid licensed channels for that location based on the licenses posted. Calculated with 450.0000=Ch 1, 460.0000=ch 401 and step of .0125

 

[R0am3r]

I do know that. But first of all Nexedge DFA is highly rare and second - that's not the scope of this thread and for the sake of simplicity don't even mention any of all other possibilities

So you posted something that you knew was incorrect? I am not sure how this helps.

 

[LimaZulu]

So you posted something that you knew was incorrect? I am not sure how this helps.

Not that I am obligated to give you any explanation but just to be polite I'll do it.
It is obvious that the system posted here is not DFA. If you can't understand why, let me just say that if it was DFA this thread wouldn't exist Another sign that's not the case - did you ever see the link leading to the system with all the info in the db? Want more? There were obvious mistake in the configuration files
Believe me, there are way too many possibilities that weren't even barely scratched. Why not try to explain them? Otherwise I don't see how YOUR post helps

 

[R0am3r]

Wow - you really don't get it. Your post (#3) about NXDN was incorrect. That is a fact. Instead owning your error, you made up excuses about DFA systems ("Nexedge DFA is highly rare"). Now you want to conflate DFA systems with more gibberish about the system the OP was trying to monitor. Here is a hint - I don't care about DFA systems. I used it for proof as to why your post was incorrect. Maybe you should read posts #3 and 4 again. Hopefully you will see why my post helps.

 

[LimaZulu]

What I do not understand is why when someone is confused, some other guy, "sir-I-know-a-lot", always is trying to complicate things even more, just like you did. My posts were all pointed to a certain questions of the OP without entering unnecessary details and other possibilities that clearly are not the case, where you clearly entered the thread, made a few posts not helping the OP but instead demonstrate how big your knowledge is.
If you don't think my posts here help, just skip reading them or you can use report button. Knowing hat you have a choice, please make yours, keep calm take your pills and keep the spam away!
Cheers!

 

[GTR8000]

An argument about DFA systems in a thread where the system in question is clearly not DFA. And the issue was solved. Good grief.

LZ - Perhaps next time you should say "Most NXDN systems do not transmit the frequency information over the air..."

R0am3r - C'mon man, let it go, you made your point and you knew this thread had nothing to do with DFA from the first post

 

[Forts]

Also check your bandwidth in FMP24. From your screenshot you have it set to 9.5. For NXDN it should be 4 (and 7.6 for DMR).