Date   

Re: ASL <>MMDVM<>XLX<>BM/DStar

Steve N4IRS
 

Enable=0  <------------ Should be enabled!

On 6/5/20 10:54 AM, W8DSB wrote:
So if I understand correctly this is the format, it does not seem to work just yet :(

[DMR Network]
Enable=0
Address=18.218.209.254
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0
 


Re: ASL <>MMDVM<>XLX<>BM/DStar

W8DSB
 

So if I understand correctly this is the format, it does not seem to work just yet :(

[DMR Network]
Enable=0
Address=18.218.209.254
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Options=XLX:4002
Slot1=0
Slot2=1
Debug=0
 


Re: ASL <>MMDVM<>XLX<>BM/DStar

Nomis Bayan Jr.
 

Type in wrong: should be Options=XLX:4002.....correction...

On 6/5/2020 5:37 AM, W8DSB wrote:
I think I need just a little push in the proper direction. I changed my MMDVM_Bridge.ini to read what you see below however if I watch the XLX it never connects. I tried 
Options=XLX:998 and Options=XLX:998 B but I have a feeling that I need to add something xlxd.interlink or am I just missing something.

I did remember to change my DMR ID to 7 digits

[DMR Network]
Enable=0
Address=18.218.209.254    <== my XLX IP
Port=62031
Jitter=750
Local=62032
Password=passw0rd
Options=XLX:998
Slot1=0
Slot2=1
Debug=0
 


Re: ASL <>MMDVM<>XLX<>BM/DStar

Nomis Bayan Jr.
 

Hello,

Try Option2=XLX4002                        #for module B

4001 - Module A

4002 - Module B

4003 - module C.............etc

On 6/5/2020 5:37 AM, W8DSB wrote:
I think I need just a little push in the proper direction. I changed my MMDVM_Bridge.ini to read what you see below however if I watch the XLX it never connects. I tried 
Options=XLX:998 and Options=XLX:998 B but I have a feeling that I need to add something xlxd.interlink or am I just missing something.

I did remember to change my DMR ID to 7 digits

[DMR Network]
Enable=0
Address=18.218.209.254    <== my XLX IP
Port=62031
Jitter=750
Local=62032
Password=passw0rd
Options=XLX:998
Slot1=0
Slot2=1
Debug=0
 


Re: ASL <>MMDVM<>XLX<>BM/DStar

Steve N4IRS
 

Is XLX:998 B a attempt to connect to "module B" (I'm not much of a XLX person) If so try Options=XLX:9982

On 6/5/20 8:37 AM, W8DSB wrote:
I think I need just a little push in the proper direction. I changed my MMDVM_Bridge.ini to read what you see below however if I watch the XLX it never connects. I tried 
Options=XLX:998 and Options=XLX:998 B but I have a feeling that I need to add something xlxd.interlink or am I just missing something.

I did remember to change my DMR ID to 7 digits

[DMR Network]
Enable=0
Address=18.218.209.254    <== my XLX IP
Port=62031
Jitter=750
Local=62032
Password=passw0rd
Options=XLX:998
Slot1=0
Slot2=1
Debug=0
 


Re: ASL <>MMDVM<>XLX<>BM/DStar

W8DSB
 

I think I need just a little push in the proper direction. I changed my MMDVM_Bridge.ini to read what you see below however if I watch the XLX it never connects. I tried 
Options=XLX:998 and Options=XLX:998 B but I have a feeling that I need to add something xlxd.interlink or am I just missing something.

I did remember to change my DMR ID to 7 digits

[DMR Network]
Enable=0
Address=18.218.209.254    <== my XLX IP
Port=62031
Jitter=750
Local=62032
Password=passw0rd
Options=XLX:998
Slot1=0
Slot2=1
Debug=0
 


Re: ASL_node_list.txt

Eric-K6KWB
 

Steve N4IRS,
I downloaded this the other day got error "page not found". sorry I cant remember the date looks like a week ago.
wget
https://github.com/DVSwitch/Analog_Bridge/raw/master/dvswitch.sh

73, Eric


Re: ASL <>MMDVM<>XLX<>BM/DStar

Steve N4IRS
 

MB.ini

[DMR Network]
Enable=0
Address=hblink.dvswitch.org
Port=62031
Jitter=360
Local=62032
Password=passw0rd
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

Note:

For XLK the synatax is: Options=XLX:4009

For XLX make sure you are using a 7 digit DMR ID

73, Steve N4IRS


On 6/4/20 4:18 PM, W8DSB wrote:
All, we have a PI running XLX With interlinks to BM and DV3000 to DStar.

I also have a ASL with analog_bridge <> mmdvm <> BM

i want to connect our mmdvm_bridge directly to the XLX to reduce lag and host server issues. How to i connect mmdvm_bridge directly to our clubs XLX server?

Is there a document or video for this? I tried just pointing at it but mmdvm_bridge will not log into the XLX :(


ASL <>MMDVM<>XLX<>BM/DStar

W8DSB
 

All, we have a PI running XLX With interlinks to BM and DV3000 to DStar.

I also have a ASL with analog_bridge <> mmdvm <> BM

i want to connect our mmdvm_bridge directly to the XLX to reduce lag and host server issues. How to i connect mmdvm_bridge directly to our clubs XLX server?

Is there a document or video for this? I tried just pointing at it but mmdvm_bridge will not log into the XLX :(


Re: ARM IMAGE

W8DSB
 

Scott is right when I installed DVSwitch on the arch Linux, I use Pacman. However it doesn’t sound as good as it should. I was inspired this morning and installed DVSwitch On a running allstar node that was already up at Amazon‘s web service. It turns out that sounds very good using the 380 emulator. My only issue is now that there’s a delay going between the analog repeater and the digital repeaters due to brandmeister. Sometimes it even gets choppy. I would like to connect the DVDwitch right to a XLX server running at a different Amazon cloud does anyone know how to do that? I tried just changing the server address but it seems there must be more? Maybe port numbers?


Debian Buster

Dick Smith
 

I am seeing that Buster has been renamed to Raspbian Buster, is that the one to use to start the process of setting up DVswitch?

Dick
W4RSS


Re: Some questions about dvswitch.sh and Analog_Bridge

Mike Zingman - N4IRR
 

A transcoder should NEVER receive a tune command.  Use static TG info in your gateway and BM.
If you MUST have the DMR or P25 side tuneable, then the TLV tune should be directed at the MB instances that service the network.
This is happening because the tune command sent to AB is producing an info packet (as it should).  I will see if I can suppress these if the client has not "registered" (DVSM)


radioid.net URL update in dvswitch.sh

Jeffrey [K8JTK]
 

Monday noticed a couple issues on my system, D-STAR wasn't passing audio both ways and other mode dashboards were not populating the call signs (had the numeric DMR ID).

Running the update manually:
./dvswitch.sh update
parse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
parse error: Invalid numeric literal at line 1, column 10
Error, DMR ID file does not seem to be valid

Not sure why my subscriber_ids.csv was empty if the download failed.  A manual curl to one of the urls in the "downloadDatabases" function presented me with a 302 document moved.

I saw on radioid.net they were changing their API location on July 1.

!! if you use the API or Data Dumps in scripts, modify your scripts before JULY 1st. New server for data: https://database.radioid.net !!

Maybe they meant June 1.  The 302 was pointing at the new API location.  I changed the download location for all 3 calls
from: www.radioid.net
to: database.radioid.net
Ran the update manually and all was well.

A pull of the DVSwitch-System-Builder has the old URL.  If an update is already available, it has the old url in that repo.


Re: ARM IMAGE

Ken KE2N
 

XLX does not do analog.  The reason those connections sound "perfect" is that they go from digital to digital.

When you go to analog - in particular Allstar - higher-frequency components of the DMR signal are just not encoded well at the 8k sampling rate and get distorted.   I don't know why, but Fusion in particular has a lot of energy in the range of 3500 Hz and that is a no-no for Allstar.  The AMBE modes use a vocoder - which can produce sound energy above what the Nyquist limit would dictate.  I guess they feel that emphasizing this part of the audio spectrum enhances intelligibility. But it is annoying when you go to a scheme that is encoding the audio (rather than vocoding it).


Ken
KE2N


Re: Some questions about dvswitch.sh and Analog_Bridge

Tim Payne
 

Hi Steve,

I have tried running only the 2 instances of AB and it happens when I send the dvswitch tune command. The logs I included had no MB running at all. Other tests I performed were only running the AB_P25 and then the AB_DMR along with the rest of the system and then when I ran the dvswitch command or keyed up on the radio there was no spamming of info packets. 
 
Today I though I would leave it running for a while after issuing the dvswitch tune 9999 (disconnect) running for 3 hours at 100 CPU. 

Does AB pull any setting from the DVswitch.ini file in the MB directory? 

I'll pull the Configs for those when I get to the PC tomorrow.

Thanks
Tim vk3ftzd


Re: Some questions about dvswitch.sh and Analog_Bridge

Steve N4IRS
 

Tim,
You are correct, suppressing the log does no good. We need to know what is going on.  Lets start with the DMR side of the bridge. Turn off AB_P25. I assume you are running one instance of MB. So in MB.ini disable P25 and P25 networking.
Set the log level to 1 and capture the AB and MB logs. I would also like to see your MB.ini and dvswitch.ini.

Steve N4IRS

On 6/4/2020 5:35 AM, Tim Payne wrote:
Ok thanks. I'll try it. I know that I tried setting to 4 - warning and I got the close to 100% CPU usage but of course the packets were suppressed.

Hiding the alerts doesn't necessarily mean it fixes the problem. You say you use the logs yourself. Do you see this in your logs? Is it normal to have this happening?


Re: Some questions about dvswitch.sh and Analog_Bridge

 

Hello Tim

I never look at logs.
Just look at the info on the screen.
Can see whats going on in real time.
Also see whats gone down then just restart the software.

There is always info passing back and forth from Analog_Bridge.
It will be the transcoding from dmr to p25 thats using the cpu not the info.


Re: Some questions about dvswitch.sh and Analog_Bridge

Tim Payne
 

Ok thanks. I'll try it. I know that I tried setting to 4 - warning and I got the close to 100% CPU usage but of course the packets were suppressed.

Hiding the alerts doesn't necessarily mean it fixes the problem. You say you use the logs yourself. Do you see this in your logs? Is it normal to have this happening?


Re: Some questions about dvswitch.sh and Analog_Bridge

 

In the Analog_Bridge.ini

loglevel = 2 you could change it to 0

I never change it as I use this info to see whats going on. 
As I run in terminal windows the info from the logs act like a dashboard for me.
Tx begin, Tx end, callsigns etc.


Re: #analog_bridge #analog_bridge

andrew delgado
 

i did stop the ambe server here is the logs. same error on port 31100 will close upon sending the marco ^DMR mode

I: 2020-06-04 03:23:37.362 Tune macro: *DMR will invoke "/opt/Analog_Bridge/dvswitch.sh mode DMR"
I: 2020-06-04 03:23:37.548 rxport=: 30000
M: 2020-06-04 03:23:37.549 TLV rx socket reopened for 127.0.0.1:30000
I: 2020-06-04 03:23:38.862 MESSAGE packet sent to USRP client: Setting mode to DMR
I: 2020-06-04 03:23:38.937 ambeMode = DMR, size = 72
M: 2020-06-04 03:23:38.937 Connecting to DV3000 hardware......
M: 2020-06-04 03:23:38.948 Begin DV3000 decode
I: 2020-06-04 03:23:39.009 txport=: 31103
I: 2020-06-04 03:23:39.102 rxport=: 31100
E: 2020-06-04 03:23:39.103 Can not bind port 31100, error code = 98 (Address already in use)
M: 2020-06-04 03:23:39.103 TLV rx socket reopened for 127.0.0.1:31100
I: 2020-06-04 03:23:40.345 Macro result was 0

2541 - 2560 of 9083