NXDN NEXEDGE 4800

[humblegeo]

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.

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

change it here on both lines from 0 to 1?

 

[lwvmobile]

change it here on both lines from 0 to 1?

In the bat file, any line with a @rem in front of it is never executed, those extra lines are used for example configuration start ups, so just apply the change to the one without the @rem in front of it. BTW, its also a convenient way to test changes without losing a good setup, by copy and pasting lines you want to tinker with, and putting a @rem in front of it so you can reference it and go back to it if needed.

 

[humblegeo]

In the bat file, any line with a @rem in front of it is never executed, those extra lines are used for example configuration start ups, so just apply the change to the one without the @rem in front of it. BTW, its also a convenient way to test changes without losing a good setup, by copy and pasting lines you want to tinker with, and putting a @rem in front of it so you can reference it and go back to it if needed.

done. I'll try it now.
@rem With RTL dongle
dsd-fme-lite.exe -fi -i rtl:1:453.16875M:42:0:12:70:6021 -C AVFD.csv -T -N 2> log.ans
@rem dsd-fme-lite.exe -fi -i rtl:0:453.16875M:42:0:12:70:6021 -C AVFD.csv -T

 

[humblegeo]

Interesting that the log still won't open and says Device 0 even though I have changed it to1, 2 and 3. I did go ahead and open the program and it is running. I'm hearing an occasional blip of audio come thru although not enough to understand. I do have TeamViewer still on my desktop.

 

[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

How was the signal stregnth on these frequencies? Good, bad?

 

[lwvmobile]

Interesting that the log still won't open and says Device 0 even though I have changed it to1, 2 and 3. I did go ahead and open the program and it is running. I'm hearing an occasional blip of audio come thru although not enough to understand. I do have TeamViewer still on my desktop.

Not sure why the log wouldn't open with that bat file, unless you accidentally removed the line in it to open it.

If you want me to remote in, I may be able to get on later this evening, not entirely sure. If not, perhaps Monday or Tuesday, will be busy on and off and not always able to sit down and work on it.

 

[humblegeo]

Not sure why the log wouldn't open with that bat file, unless you accidentally removed the line in it to open it.

If you want me to remote in, I may be able to get on later this evening, not entirely sure. If not, perhaps Monday or Tuesday, will be busy on and off and not always able to sit down and work on it.

We can remote. I don't have a problem with it. The signal strength on SDRPlus was good. The "in level" goes up as high as 37% but it fluctuates up and down. am hearing audio but just blips here and there. can't make it out but can tell it's voice. occasionally flashes from green to white.

I guess I'll have to setup teamviewer when the time comes. The shortcut is no longer working. always something but can be done I'm sure.

 

[lwvmobile]

Interesting that the log still won't open and says Device 0 even though I have changed it to1, 2 and 3. I did go ahead and open the program and it is running. I'm hearing an occasional blip of audio come thru although not enough to understand. I do have TeamViewer still on my desktop.

Okay, so here is what I've found out today. Due to the way squelch is handled by DSD-FME internally with the RTL dongle, any squelched audio input from it will effectively stop the entire process of DSD-FME until signal is regained. That means, that in a trunking NXDN session, it just stops after its first tuning assignment, if it can tune at all. So, for the time being, becuase trying to fix this particular piece of code for the internal RTL support is not a simple task, NXDN trunking will not work properly with the RTL dongle input since if we turn squelch off, it will constantly gain tons of false syncs and not tune properly, but if we enable squelch, all processing halts and it stops tuning.

NXDN48/96 trunking is still feasible when it is using and controlling either GQRX, SDR#, or SDR++. SDR++ is in my opinion the better of the two options as it has both the TCP sink and RIGCTL tuning client built in. If using SDR#, you have to install both the 'TCP Server' and 'GPredict' plugin to accomplish the same, and also if its communinty version, we also have to dig around and disable some of the post audio processing that one of the community plugins does in order to get clean decoding.

I can still remote in and get you set up (hopefully) with SDR# or SDR++ to trunk those NXDN systems if you'd like.