Date   

Re: I have missed some major step on install

Steve N4IRS
 

Chris,
Once you installed the repository, what application did you install? "apt-get install dvswitch" ?

Steve

On 6/1/2018 9:54 AM, Chris via Groups.Io wrote:
Hi,
I am trying to get DVSwitch installed on my Debian virtual Server.

I have The ISO from ASL installed and it is working fine.

I followed the instructions from here
https://dvswitch.groups.io/g/main/topic/updated_dvswitch_repository/18971786?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,18971786

and installed the repository. Everything looked as though it installed correctly.
However, when I go look in the OPT folder I can’t find any .ini files.

I have searched high and low through all my directories.

Is there another step to install after the instructions I followed on the above mentioned link?

I have searched the threads for this info, but am afraid I am to ignorant to know WHAT to search for.

Thanks,
Chris
WB4ULK


I have missed some major step on install

Chris WB4ULK
 

Hi,
I am trying to get DVSwitch installed on my Debian virtual Server.

I have The ISO from ASL installed and it is working fine.

I followed the instructions from here
https://dvswitch.groups.io/g/main/topic/updated_dvswitch_repository/18971786?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,18971786

and installed the repository. Everything looked as though it installed correctly.
However, when I go look in the OPT folder I can’t find any .ini files.

I have searched high and low through all my directories.

Is there another step to install after the instructions I followed on the above mentioned link?

I have searched the threads for this info, but am afraid I am to ignorant to know WHAT to search for.

Thanks,
Chris
WB4ULK


Re: New ASL / Echolink <> DMR Gateway up!

Steve N4IRS
 

No, not at this time.

On 05/31/2018 07:27 PM, Roselito de los Reyes wrote:
Hi Steve,

Is there any way to translate the ASL Node ID transmitting -> person's callsign -> DMR ID?

73,

Lito

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 4:23 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] New ASL / Echolink <> DMR Gateway up!
 
Jon,
The gatewayDmrId value is what appears as the station on BM. Since ASL has no Metadata, there is now real way to extract the real transmitting station.

73, Steve

On 05/31/2018 07:18 PM, jon@... wrote:
Hey, thanks to all of you who posted your configs. 

I've now got a bridge up and running on the following:

BM TG 98003 (RedditNet)
ASL 48224
Echolink KM8V-L

And it all works!

One question:

Is there any way to control what callsign appears on Brandmeister, or will everything that comes through the bridge come through with my call?

Thanks & 73 de KM8V



Re: New ASL / Echolink <> DMR Gateway up!

Lito - WI6Y
 

Hi Steve,

Is there any way to translate the ASL Node ID transmitting -> person's callsign -> DMR ID?

73,

Lito


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 4:23 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] New ASL / Echolink <> DMR Gateway up!
 
Jon,
The gatewayDmrId value is what appears as the station on BM. Since ASL has no Metadata, there is now real way to extract the real transmitting station.

73, Steve

On 05/31/2018 07:18 PM, jon@... wrote:
Hey, thanks to all of you who posted your configs. 

I've now got a bridge up and running on the following:

BM TG 98003 (RedditNet)
ASL 48224
Echolink KM8V-L

And it all works!

One question:

Is there any way to control what callsign appears on Brandmeister, or will everything that comes through the bridge come through with my call?

Thanks & 73 de KM8V


Re: New ASL / Echolink <> DMR Gateway up!

Steve N4IRS
 

Jon,
The gatewayDmrId value is what appears as the station on BM. Since ASL has no Metadata, there is now real way to extract the real transmitting station.

73, Steve

On 05/31/2018 07:18 PM, jon@... wrote:
Hey, thanks to all of you who posted your configs. 

I've now got a bridge up and running on the following:

BM TG 98003 (RedditNet)
ASL 48224
Echolink KM8V-L

And it all works!

One question:

Is there any way to control what callsign appears on Brandmeister, or will everything that comes through the bridge come through with my call?

Thanks & 73 de KM8V


New ASL / Echolink <> DMR Gateway up!

Jon KM8V
 

Hey, thanks to all of you who posted your configs. 

I've now got a bridge up and running on the following:

BM TG 98003 (RedditNet)
ASL 48224
Echolink KM8V-L

And it all works!

One question:

Is there any way to control what callsign appears on Brandmeister, or will everything that comes through the bridge come through with my call?

Thanks & 73 de KM8V


Re: Explanation of ports and TG on one machine

Lito - WI6Y
 

Thank you for the clarification. I think the bleed over could be caused by some other experimenter other than me.

Lito


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 4:10 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
As long as the local port are different you should be fine. You may want to log into different servers also.

On 05/31/2018 07:07 PM, Roselito de los Reyes wrote:
Hi Steve,

If I had two instances of the MMDVM_Bridge serving two different TG's, is there a possibility of a bleed over the two services? This is happening with my setup and all other ports have are all different.

Lito

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 4:05 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
62031 is the port used to log into BrandMeister. That is fixed.

On 05/31/2018 06:59 PM, Roselito de los Reyes wrote:
Is that also true for the DMR Network Stanza 
port? I tried to change it to 62030 and it times out.

M: 2018-05-31 22:56:40.270 MMDVM_Bridge-20180423 is running
I: 2018-05-31 22:56:40.270 Started the DMR Id lookup reload thread
E: 2018-05-31 22:57:50.273 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:57:50.273 DMR, Closing DMR Network
M: 2018-05-31 22:57:50.273 DMR, Opening DMR Network
E: 2018-05-31 22:59:00.281 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:59:00.281 DMR, Closing DMR Network
M: 2018-05-31 22:59:00.281 DMR, Opening DMR Network


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
Yes it is. If commented out it will choose random port.

On 5/31/2018 12:51 PM, Roselito de los Reyes wrote:
Hi Steve

The Local port parameter in the System fusion network stanza is that arbitrary? Is the same statement true for port 62031 for the DMR Network Stanza?

Lito WI6Y




Re: Explanation of ports and TG on one machine

Steve N4IRS
 

As long as the local port are different you should be fine. You may want to log into different servers also.

On 05/31/2018 07:07 PM, Roselito de los Reyes wrote:
Hi Steve,

If I had two instances of the MMDVM_Bridge serving two different TG's, is there a possibility of a bleed over the two services? This is happening with my setup and all other ports have are all different.

Lito

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 4:05 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
62031 is the port used to log into BrandMeister. That is fixed.

On 05/31/2018 06:59 PM, Roselito de los Reyes wrote:
Is that also true for the DMR Network Stanza 
port? I tried to change it to 62030 and it times out.

M: 2018-05-31 22:56:40.270 MMDVM_Bridge-20180423 is running
I: 2018-05-31 22:56:40.270 Started the DMR Id lookup reload thread
E: 2018-05-31 22:57:50.273 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:57:50.273 DMR, Closing DMR Network
M: 2018-05-31 22:57:50.273 DMR, Opening DMR Network
E: 2018-05-31 22:59:00.281 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:59:00.281 DMR, Closing DMR Network
M: 2018-05-31 22:59:00.281 DMR, Opening DMR Network


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
Yes it is. If commented out it will choose random port.

On 5/31/2018 12:51 PM, Roselito de los Reyes wrote:
Hi Steve

The Local port parameter in the System fusion network stanza is that arbitrary? Is the same statement true for port 62031 for the DMR Network Stanza?

Lito WI6Y




Re: Explanation of ports and TG on one machine

Lito - WI6Y
 

Hi Steve,

If I had two instances of the MMDVM_Bridge serving two different TG's, is there a possibility of a bleed over the two services? This is happening with my setup and all other ports have are all different.

Lito


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 4:05 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
62031 is the port used to log into BrandMeister. That is fixed.

On 05/31/2018 06:59 PM, Roselito de los Reyes wrote:
Is that also true for the DMR Network Stanza 
port? I tried to change it to 62030 and it times out.

M: 2018-05-31 22:56:40.270 MMDVM_Bridge-20180423 is running
I: 2018-05-31 22:56:40.270 Started the DMR Id lookup reload thread
E: 2018-05-31 22:57:50.273 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:57:50.273 DMR, Closing DMR Network
M: 2018-05-31 22:57:50.273 DMR, Opening DMR Network
E: 2018-05-31 22:59:00.281 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:59:00.281 DMR, Closing DMR Network
M: 2018-05-31 22:59:00.281 DMR, Opening DMR Network


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
Yes it is. If commented out it will choose random port.

On 5/31/2018 12:51 PM, Roselito de los Reyes wrote:
Hi Steve

The Local port parameter in the System fusion network stanza is that arbitrary? Is the same statement true for port 62031 for the DMR Network Stanza?

Lito WI6Y



Re: Explanation of ports and TG on one machine

Steve N4IRS
 

62031 is the port used to log into BrandMeister. That is fixed.

On 05/31/2018 06:59 PM, Roselito de los Reyes wrote:
Is that also true for the DMR Network Stanza 
port? I tried to change it to 62030 and it times out.

M: 2018-05-31 22:56:40.270 MMDVM_Bridge-20180423 is running
I: 2018-05-31 22:56:40.270 Started the DMR Id lookup reload thread
E: 2018-05-31 22:57:50.273 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:57:50.273 DMR, Closing DMR Network
M: 2018-05-31 22:57:50.273 DMR, Opening DMR Network
E: 2018-05-31 22:59:00.281 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:59:00.281 DMR, Closing DMR Network
M: 2018-05-31 22:59:00.281 DMR, Opening DMR Network


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
Yes it is. If commented out it will choose random port.

On 5/31/2018 12:51 PM, Roselito de los Reyes wrote:
Hi Steve

The Local port parameter in the System fusion network stanza is that arbitrary? Is the same statement true for port 62031 for the DMR Network Stanza?

Lito WI6Y



Re: Explanation of ports and TG on one machine

Lito - WI6Y
 

Is that also true for the DMR Network Stanza 
port? I tried to change it to 62030 and it times out.

M: 2018-05-31 22:56:40.270 MMDVM_Bridge-20180423 is running
I: 2018-05-31 22:56:40.270 Started the DMR Id lookup reload thread
E: 2018-05-31 22:57:50.273 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:57:50.273 DMR, Closing DMR Network
M: 2018-05-31 22:57:50.273 DMR, Opening DMR Network
E: 2018-05-31 22:59:00.281 DMR, Connection to the master has timed out, retrying connection
M: 2018-05-31 22:59:00.281 DMR, Closing DMR Network
M: 2018-05-31 22:59:00.281 DMR, Opening DMR Network


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Thursday, May 31, 2018 10:11 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Explanation of ports and TG on one machine
 
Yes it is. If commented out it will choose random port.

On 5/31/2018 12:51 PM, Roselito de los Reyes wrote:
Hi Steve

The Local port parameter in the System fusion network stanza is that arbitrary? Is the same statement true for port 62031 for the DMR Network Stanza?

Lito WI6Y


Re: Rpi3 Bridge

Justin Morris
 

I went through and changed the stanza to match yours. It works now, I'm unsure which setting fixed the kerchunk issue. Thank you very much. On to the p25 next. 


Re: Explanation of ports and TG on one machine

Steve N4IRS
 

Yes it is. If commented out it will choose random port.

On 5/31/2018 12:51 PM, Roselito de los Reyes wrote:
Hi Steve

The Local port parameter in the System fusion network stanza is that arbitrary? Is the same statement true for port 62031 for the DMR Network Stanza?

Lito WI6Y


Explanation of ports and TG on one machine

Lito - WI6Y
 

Hi Steve

The Local port parameter in the System fusion network stanza is that arbitrary? Is the same statement true for port 62031 for the DMR Network Stanza?

Lito WI6Y


Re: Analog_Bridge.ini

Steven Blackford
 

Jeff,

  I’ve setup several of these ASL<->DMR bridges now.  Personally, I try to keep the “bridges” setup on “Private” nodes & then have them auto connect to your public node on startup once you have everything working properly.  The startup macro works great for this.  I do this so just in case a problem arises, you can always disconnect the “Private Node,” from your public node & it’s still available for people to use.  In my instance, I have my primary node 46626 as a public facing node & I tie the ASL<->DMR Bridge to a private node 1999 or 1998.     Take care & 73 de K4SQI!

 

Steve, K4SQI

 

From: Jeff Carrier
Sent: Thursday, May 31, 2018 10:18 AM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] Analog_Bridge.ini

 

Thanks Steve, 

 

I guess I scanned through the op too quickly and didn't catch that.

 

On Thu, May 31, 2018 at 7:37 AM Steve N4IRS <szingman@...> wrote:

Jeff,
You can't run USRP and Simple USB in the same node stanza at the same time. Each node stanza has a unique rxchannel.
It should look something like this:

[1999]
rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                    ; 127.0.0.1 = IP of the target application
                    ; 34001 = UDP port the target application is listening on
                    ; 32001 = UDP port ASL is listening on

duplex = 0          ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0        ; squelch tail hang time 0
althangtime = 0     ; longer squelch tail hang time 0

holdofftelem = 1    ; Hold off all telemetry when signal is present on receiver or from connected nodes
                    ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0    ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0    ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no     ; disables forcing physical half-duplex operation of main repeater while
                    ; still keeping half-duplex semantics (optional)

nounkeyct = 1       ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000     ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie   ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie    ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

[1998]
rxchannel = SimpleUSB/usb_1998    ; SimpleUSB


Same box, no problem. Same node stanza, problem.

Steve

On 5/31/2018 9:30 AM, Jeff Carrier wrote:

Steve, 

 

You mentioned something yesterday that created a question in my mind.  You said USRP and SimpleUSB can't run together on the same box.  I'm assuming that has something to do with those two channel drivers in asterisk.  My install seems to be fine less the complaints about "digital sounding audio" but I'm running Analog_Bridge, MMDVM_Bridge and P25Gateway on the same Pi as an allstar node with URIx connected running DSP.  It seems fine but does this have the potential to cause erratic behavior?

 

On Thu, May 31, 2018 at 7:20 AM Steve N4IRS <szingman@...> wrote:

We are working to simplify and standardize the configuration files across all the Partner programs. Analog_Bridge.ini is one of the oldest and needs a little facelift to better match the other partners. Though some of the parameter names are changing, the old names will be supported for a while. If you are still using the older names, you will get a warning in the Analog_Bridge log. Your configuration will continue to operate as before. I have bolded the changes parameters Here is the updated Analog_Bridge.ini:

; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.

; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.


; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

; Metadata management
subscriberFile = ./subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)

; General vocoder setup information
decoderFallBack = false                 ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server

; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31003                          ; Transmit TLV frames to partner on this port
rxPort = 31000                          ; Listen for TLV frames from partner on this port
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay (0-10000)

; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; ID of source repeater
txTg = 9                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames

; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY                  ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20                           ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1                     ; IP address of AMBEServer
rxPort = 2460                           ; Port of AMBEServer
; address = /dev/ttyUSB0                ; Device of DV3000U on this machine
; baud = 460800                         ; Baud rate of the dongle (230400 or 460800)
; serial = true                         ; Use serial=true for direct connect or serial=false for AMBEServer

 

 


Re: Updated DVSwitch repository available

Steve N4IRS
 

Try apt-get purge to remove.

On 5/31/2018 10:54 AM, Mike Swiatkowski via Groups.Io wrote:
Steve,
How come I only see the binaries for analog bridge and mmdvm bridge after I do an apt-get remove then apt-get install?  It seems the config .ini files were not installed in the /opt/analog_bridge or /opt/mmdvm_bridge the second time.  

I was doing some house cleaning and needed to install the files a second time after an uninstall so I'm wondering what I did and how to fix it.  What is the correct directory structure?

/opt/analog_bridge only contains binary?
/opt/mmdvm_bridge only contains binary
/opt/?  contains dvswitch and config files?

I only had it installed once so I forget the structure.

Mike


Re: Updated DVSwitch repository available

Mike, AA9VI
 

Steve,
How come I only see the binaries for analog bridge and mmdvm bridge after I do an apt-get remove then apt-get install?  It seems the config .ini files were not installed in the /opt/analog_bridge or /opt/mmdvm_bridge the second time.  

I was doing some house cleaning and needed to install the files a second time after an uninstall so I'm wondering what I did and how to fix it.  What is the correct directory structure?

/opt/analog_bridge only contains binary?
/opt/mmdvm_bridge only contains binary
/opt/?  contains dvswitch and config files?

I only had it installed once so I forget the structure.

Mike


Re: Rpi3 Bridge

Steve N4IRS
 

I forgot to post the sample node stanza. it is at: <https://dvswitch.groups.io/g/allstarlink/wiki/home>

Steve

On 5/31/2018 10:12 AM, kc5mmw@... wrote:
Appreciate it, That got it going, kind of. Analog is passing to dmr fine. audio needs adjusting but works. dmr to analog only causes a kerchunk to come though. watching MMDVM_Bridge it seems to be seeing the whole transmission. 


Re: Analog_Bridge.ini

Jeff Carrier
 

Thanks Steve, 

I guess I scanned through the op too quickly and didn't catch that.

On Thu, May 31, 2018 at 7:37 AM Steve N4IRS <szingman@...> wrote:
Jeff,
You can't run USRP and Simple USB in the same node stanza at the same time. Each node stanza has a unique rxchannel.
It should look something like this:

[1999]
rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                    ; 127.0.0.1 = IP of the target application
                    ; 34001 = UDP port the target application is listening on
                    ; 32001 = UDP port ASL is listening on

duplex = 0          ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0        ; squelch tail hang time 0
althangtime = 0     ; longer squelch tail hang time 0

holdofftelem = 1    ; Hold off all telemetry when signal is present on receiver or from connected nodes
                    ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0    ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0    ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no     ; disables forcing physical half-duplex operation of main repeater while
                    ; still keeping half-duplex semantics (optional)

nounkeyct = 1       ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000     ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie   ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie    ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

[1998]
rxchannel = SimpleUSB/usb_1998    ; SimpleUSB


Same box, no problem. Same node stanza, problem.

Steve


On 5/31/2018 9:30 AM, Jeff Carrier wrote:
Steve, 

You mentioned something yesterday that created a question in my mind.  You said USRP and SimpleUSB can't run together on the same box.  I'm assuming that has something to do with those two channel drivers in asterisk.  My install seems to be fine less the complaints about "digital sounding audio" but I'm running Analog_Bridge, MMDVM_Bridge and P25Gateway on the same Pi as an allstar node with URIx connected running DSP.  It seems fine but does this have the potential to cause erratic behavior?

On Thu, May 31, 2018 at 7:20 AM Steve N4IRS <szingman@...> wrote:
We are working to simplify and standardize the configuration files across all the Partner programs. Analog_Bridge.ini is one of the oldest and needs a little facelift to better match the other partners. Though some of the parameter names are changing, the old names will be supported for a while. If you are still using the older names, you will get a warning in the Analog_Bridge log. Your configuration will continue to operate as before. I have bolded the changes parameters Here is the updated Analog_Bridge.ini:

; Analog_Bridge configuration file.
;   This file should be placed in either /etc or it can be
;   supplied as a path on the Analog_Bridge command line.

; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio).  Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port.  The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.


; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

; Metadata management
subscriberFile = ./subscriber_ids.csv   ; DMR ID to callsign lookup data
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)

; General vocoder setup information
decoderFallBack = false                 ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the md380 server

; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31003                          ; Transmit TLV frames to partner on this port
rxPort = 31000                          ; Listen for TLV frames from partner on this port
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000                      ; Minimum time in MS for hang delay (0-10000)

; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 0                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 0                          ; ID of source repeater
txTg = 9                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1                           ; Color Code to assign DMR frames

; Information for USRP channel driver.  This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover).  Launch
;   each instance with its own ini file.
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001                          ; Transmit USRP frames on this port
rxPort = 34001                          ; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY                  ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20                           ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY                  ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1                     ; IP address of AMBEServer
rxPort = 2460                           ; Port of AMBEServer
; address = /dev/ttyUSB0                ; Device of DV3000U on this machine
; baud = 460800                         ; Baud rate of the dongle (230400 or 460800)
; serial = true                         ; Use serial=true for direct connect or serial=false for AMBEServer




Re: Rpi3 Bridge

Steve N4IRS
 

The sample stanza for the USRP node is the suggested settings. Check yours. Since the diagram looks like this:
BM <-> MMDVM_Bridge <-> Analog_Bridge <-> ASL
Your next log to watch is Analog_Bridge.
At the CLI prompt for ASL you can set rpt debug level 7 to see more of what is happening in ASL.

Steve

On 5/31/2018 10:12 AM, kc5mmw@... wrote:
Appreciate it, That got it going, kind of. Analog is passing to dmr fine. audio needs adjusting but works. dmr to analog only causes a kerchunk to come though. watching MMDVM_Bridge it seems to be seeing the whole transmission. 

7681 - 7700 of 9070