NXDN NEXEDGE 4800

[lwvmobile]

Just curious, if I recorded some raw data of a NXDN trunked system with DSDPlus and sent it to you, would that help you in any way?

Not at this point. The ideal environment would honestly be a linux desktop remote with a busy NXDN48 or NXDN96 trunking system (with multiple channels, not a single channel trunking setup), SDR++, and VS Codium so I could code changes on the fly based on observations made in that moment. The report I've had so far on NXDN trunking is that it'll tune to the voice channel, but never returns to the control channel. Unfortunately, wav files aren't going to help me in this regard.

While I do not know the DSD FME author in any way, I would be more concerned with the CoinManage guy in my pc.

Well, thanks in your faith in me, but I'm not one to pry somebody after the initial offer. I have a feeling this may turn out to be not be a trunking system, just a normal NXDN conventional frequency/frequencies.

radioreference may be wrong about it being a NXDN site

I still think its an NXDN48 system based on the emissions and info available, I just don't think its a trunking system (that it doesn't have a dedicated full time control channel, that is). If its set up like the local-ish NXDN for Fire Rescue here, they have a few frequencies, but none of them are trunked, they are just there for coverage of different munincipalities and unincorporated areas of the county. It doesn't even beacon out like some NXDN conventional systems do, it just starts up when it starts up.

 

[KevinC]

Not at this point. The ideal environment would honestly be a linux desktop remote with a busy NXDN48 or NXDN96 trunking system (with multiple channels, not a single channel trunking setup), SDR++, and VS Codium so I could code changes on the fly based on observations made in that moment. The report I've had so far on NXDN trunking is that it'll tune to the voice channel, but never returns to the control channel. Unfortunately, wav files aren't going to help me in this regard.


Well, thanks in your faith in me, but I'm not one to pry somebody after the initial offer. I have a feeling this may turn out to be not be a trunking system, just a normal NXDN conventional frequency/frequencies.


I still think its an NXDN48 system based on the emissions and info available, I just don't think its a trunking system (that it doesn't have a dedicated full time control channel, that is). If its set up like the local-ish NXDN for Fire Rescue here, they have a few frequencies, but none of them are trunked, they are just there for coverage of different munincipalities and unincorporated areas of the county. It doesn't even beacon out like some NXDN conventional systems do, it just starts up when it starts up.

If it’s the system linked on the first page of this thread then it is definitely trunked.

 

[lwvmobile]

If it’s the system linked on the first page of this thread then it is definitely trunked.

Well, it could be a reception issue then, if some of these threads are any indication.

Long shot question....Atascocita VFD?

Anyone down near Houston using a BCD996P2 to monitor the Atascocita FD? I'm programming a new radio for a buddy down there so won't be able to double check that it works before I ship it to him. Just looking for any tips or gotchas with their NXDN trunking system.... many thanks...

forums.radioreference.com

Houston area NXDN help

Trying to program SDS 200 for fire and ems on NXDN. I have the NXDN add on in the scanner. Need help trying to program the frequencies that are NXDN. Are they trunked or single freq? How do i do this. Thanks.

forums.radioreference.com

 

[KevinC]

Well, it could be a reception issue then, if some of these threads are any indication.

Long shot question....Atascocita VFD?

Anyone down near Houston using a BCD996P2 to monitor the Atascocita FD? I'm programming a new radio for a buddy down there so won't be able to double check that it works before I ship it to him. Just looking for any tips or gotchas with their NXDN trunking system.... many thanks...

forums.radioreference.com

Houston area NXDN help

Trying to program SDS 200 for fire and ems on NXDN. I have the NXDN add on in the scanner. Need help trying to program the frequencies that are NXDN. Are they trunked or single freq? How do i do this. Thanks.

forums.radioreference.com

If I’m upstairs I can sometimes hear it. I discovered it a couple of years ago but since it’s weak out my way I never gave it much attention.

 

[lwvmobile]

If I’m upstairs I can sometimes hear it. I discovered it a couple of years ago but since it’s weak out my way I never gave it much attention.

Ah, okay. About how far away are you from their vicinity, line of sight?

 

[KevinC]

Ah, okay. About how far away are you from their vicinity, line of sight?

40 miles. I should have qualified my reply. Upstairs using a portable I can sometimes hear it. My permanent antenna can always hear it, but I’m highly filtered and a little amplified.

 

[merlin]

I have been using DSD+ Fastlane and does well on NXDN48 sites.
Takes a bit of patience while DSD builds its files.
Starting is quite easy. Use your control frequency in FMPxx.bat
Start that, then start 1R.bat. Hot keys in the active window help a lot
I think Fastlane is well worth the $25.
Text documents cover multiple SDR dongles.
Cheers

 

[humblegeo]

I have been using DSD+ Fastlane and does well on NXDN48 sites.
Takes a bit of patience while DSD builds its files.
Starting is quite easy. Use your control frequency in FMPxx.bat
Start that, then start 1R.bat. Hot keys in the active window help a lot
I think Fastlane is well worth the $25.
Text documents cover multiple SDR dongles.
Cheers

I saw a pretty good youtube video on that but it was like 1 hour and 45 minutes to get it all loaded and setup.

 

[GTR8000]

Just looking at that site again, and just realized they don't have channel numbers for that NXDN48 system, so I'm wondering if its a trunked system, or if its just 4 conventional frequencies listed. If its a trunked system, we would have to do a little leg work to figure out the channel numbers so they could be mapped properly in the csv file.

This may or may not apply to the system being discussed in this thread, but as you're developing software for these systems, it's worth pointing out that some NXDN systems are DFA (Direct Frequency Assignment). We've discovered that if we put those channel numbers in the RRDB, it breaks the ability for Uniden scanners to properly trunk track those systems, and so the CH ID's are likely to be all zeroes for DFA systems in the database.

 

[humblegeo]

I've identified what I think are the basic frequencies in use by using SDRSharp. 453.16874 453.170 453.500 453.250 but In the process of trying to get SDRTrunk back working (it was only starting 1 of my 3 dongles for some reason) I had to unplug and plug back in my dongles several times, I changed the frequencies in AVFD CSV file but now when I start the log is says failed to open rtlsdr device 0

 

[lwvmobile]

I've identified what I think are the basic frequencies in use by using SDRSharp. 453.16874 453.170 453.500 453.250 but In the process of trying to get SDRTrunk back working (it was only starting 1 of my 3 dongles for some reason) I had to unplug and plug back in my dongles several times, I changed the frequencies in AVFD CSV file but now when I start the log is says failed to open rtlsdr device 0

Well, SDRTrunk, DSD-FME, and SDRSharp can't all use the same dongle at the same time, so probably oen of them tying it up.

 

[humblegeo]

Well, SDRTrunk, DSD-FME, and SDRSharp can't all use the same dongle at the same time, so probably oen of them tying it up.

Ok appreciate it. I don't have any of those other programs running. I'LL check it out. Maybe restart the computer from scratch and then try and start DSD-FME again. I'll let you know later. Thanks for all the help today.

 

[dave3825]

453.16874

Probably a typo but that freq should be 453.16875

 

[humblegeo]

Rebooted computer with nothing else running and tried to start 3 - tail-the-console-log first but it's still having a problem starting rtlsdr device 0. I currently have 3 rtlsdr dongles plugged in and they work fine in SDRTrunk. I changed the serial numbers on 2 of them weeks ago to help differentiate which one was connected to which antenna. Serial number end in 00000001, 00000102, 00000103. If I can get past this issue, I think I'll be good to go.

 

[dave3825]

Did you ever run Zadig and install those drivers for the dongles? I believe you do not want to see them in device manager as bulk in devices. This is what mine look like on this pc.

 

[humblegeo]

Did you ever run Zadig and install those drivers for the dongles? I believe you do not want to see them in device manager as bulk in devices. This is what mine look like on this pc.

View attachment 136694

I did run Zadig to initially install them. I don't know why things have changed now. They do still show up in SDRTrunk under TUNERS with the serial numbers that I changed them to. I just got a 4th Dongle delivered yesterday. The new Black V3 Blog Dongle that I will be needing to install and setup. Maybe I better try and redo them all with Zadig if I can remember how to do that. Thanks

 

[dave3825]

Search Zadig on this site. I honestly have not done it in some time and do not want to advise you the wrong method. Some people say to choose the bulk in device and others say to choose the composite device. Either way, if done incorrectly, some programs will see the dongle and some will not.

SDRtrunk help

I have followed a guy on youtube to install sdrtrunk software. started programme but get message saying No reciever found. using windows 10. Any help would be great.

forums.radioreference.com

 

[humblegeo]

Search Zadig on this site. I honestly have not done it in some time and do not want to advise you the wrong method. Some people say to choose the bulk in device and others say to choose the composite device. Either way, if done incorrectly, some programs will see the dongle and some will not.

SDRtrunk help

I have followed a guy on youtube to install sdrtrunk software. started programme but get message saying No reciever found. using windows 10. Any help would be great.

forums.radioreference.com

Ok appreciate that. I also have a powered USB hub that I will probably try and run all 4 dongles on which might complicate things even further but sounds like that better be my next thing to sort out before I continue with DSD-FME, SDRPlus, SDRTrunk or any of it. Maybe when I changed the serial numbers on the dongles a week ago, might have caused the issue.

 

[dave3825]

Just make sure you only have one dongle plugged in at a time. I think when they show as what I posted they will be recognized in all sdr applications.

 

[lwvmobile]

Rebooted computer with nothing else running and tried to start 3 - tail-the-console-log first but it's still having a problem starting rtlsdr device 0. I currently have 3 rtlsdr dongles plugged in and they work fine in SDRTrunk. I changed the serial numbers on 2 of them weeks ago to help differentiate which one was connected to which antenna. Serial number end in 00000001, 00000102, 00000103. If I can get past this issue, I think I'll be good to go.

Okay, so, I think others touched on this, but if not mistaken, in Windows, depending on how the Zadig driver was installed (on composite or on the bulk in interface) the rtl device index at 0 isn't available, but the subsequent numbers will be. So, in other words, in the bat file you are using to launch with the rtl string, you will want to change the number from 0 to 1, or 2, or 3 to tell it which device to use. So, in other words, you may want to change the line in the bat file that is launching from:

dsd-fme-lite.exe -fi -i rtl:0:453.16875M:42:0:12:70:6021 -C AVFD.csv -T -N 2> log.ans

to

dsd-fme-lite.exe -fi -i rtl:1:453.16875M:42:0:12:70:6021 -C AVFD.csv -T -N 2> log.ans

-i rtl:0:453.16875M:42:0:12:70:6021 <--change that to a 1, or 2, depending on which dongle you wish to use.