Re: Multiple private nodes connected to different talkgroups


 

Perfect, I think that will give me plenty of homework.... I'll give it a try after the holidays! 

Thanks so much for all your help and support! 

Appreciate all you do for this hobby!

On Wed, Nov 14, 2018, 2:02 PM Steve N4IRS <szingman@... wrote:
systemctl enable analog_bridge enables the systemd unit analog_bridge.service in /lib/systemd/system. It is a test file and can be copied / edited.
It's job is the setup the environment for the program and start / stop the program
I have bolded the places you will need to change.
 
root@stn2600:~# cat /lib/systemd/system/analog_bridge.service
[Unit]
Description=Analog_Bridge for AMBE Service
# Description=Place this file in /lib/systemd/system
# Description=N4IRS 04/20/2018

# The device name should point to the
# port the mmdvm is plugged into.
# For USB ports (Arduino Due)
# BindTo=dev-ttyACM0.device
#
# To make the network-online.target available
# systemctl enable systemd-networkd-wait-online.service

After=network-online.target syslog.target netcheck.service
Wants=network-online.target

[Service]
Type=simple
StandardOutput=null
WorkingDirectory=/opt/Analog_Bridge
Environment=AnalogBridgeLogDir=/var/log/dvswitch/Analog_Bridge
# Environment=LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
Restart=always
RestartSec=3
ExecStart=/opt/Analog_Bridge/Analog_Bridge /opt/Analog_Bridge/Analog_Bridge.ini
ExecReload=/bin/kill -2 $MAINPID
KillMode=process

[Install]
WantedBy=multi-user.target

Simply copy analog_bridge.service to blabla.service in the same directory and edit to taste.
You can then:
systemctl status blabla
systemctl enable blabla
systemctl start blabla
systemctl stop blabla

The private node stanza [1999] for rpt.conf is at the top of the document https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit

73, Steve N4IRS
 
On 11/14/2018 2:45 PM, Russell, KV4S wrote:
very much so, thanks Steve.

Next question, what will these statements look like? 
systemctl enable analog_bridge
systemctl start analog_bridge
because if you copy contents the program has the same name? how does the service know which is which or maybe on linux it doesn't matter?
:/opt/Analog_Bridge$ dir 
Analog_Bridge Analog_Bridge.ini

Can you point me in the right direction for setting up a private node? do I just copy my main node stanza and make it a number like 1999, 1998 ect? Seems like there was one there but i think i overwrote it.

On Wed, Nov 14, 2018 at 10:39 AM Steve N4IRS <szingman@...> wrote:
Russell,
As per usual there is more then one way to do this. He is a simple one:
Create 4 subdirectories:
mkdir MMDVM_Bridge_TG_1234
mkdir  MMDVM_Bridge_TG_9876
mkdir Analog_Bridge_TG_1234
mkdir Analog_Bridge_TG_9876

Copy the contents of /opt/MMDVM_Bridge into the new MMDVM_Bridge directories.
Copy the contents of /opt/Analog_Bridge into the new Analog_Bridge directories.
Setup MMDVM_Bridge_TG_1234 to connect to TG 1234 on BM as normal
Setup Analog_Bridge_TG_1234 to connect to TG 1234 as normal and point it at Private node 1234

The assumption is you used the default port numbers Check your work.
Now come the change, You can not reuse the port numbers you chose for TG 1234 so:
In the MMDVM_Bridge_TG_9876 directory edit DVSwitch.ini to change the port numbers in the [DMR] stanza
Make it easy to see the change
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 36100                     ; Port to send AMBE TLV frames to (export)
RXPort = 36103                     ; Port to listen on (import)
Slot = 2                                   ; Export slot

In the Analog_Bridge_TG_9876 directory edit Analog_Bridge.ini to change the port numbers in the [AMBE_AUDIO] stanza
Match the ports use in DVSwitch.ini
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 36103                          ; Transmit TLV frames to partner on this port
rxPort = 36100                          ; Listen for TLV frames from partner on this port

As with MMDVM_Bridge <-> Analog_Bridge where you can not reuse the port numbers, It's the same for Analog_Bridge <-> ASL.
In the Analog_Bridge_TG_9876 directory edit Analog_Bridge.ini to change the port numbers in the [USRP] stanza
[USRP]
address = 127.0.0.1                     ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 38001                          ; Transmit USRP frames on this port
rxPort = 39001                          ; Listen for USRP frames on this port

Match the above port numbers for private node 9876 in rpt.conf

Does that help?

73, Steve N4IRS

On 11/14/2018 11:18 AM, Russell, KV4S wrote:
I don't have a lot of experience with private nodes but I've been working on a personal hub that is working fine with DVSwitch.

What I envision is having multiple instances of the DVSwitch (Analog/MMDVM/DVSwitch) with each instance using a different talk group. I would dedicate a private node to the different talk groups then use the main hub (public) to connect to the private nodes on the fly using  Allmon to link up the different private nodes. I would need to move the existing TG from the public hub to a private so by default nothing is linked unless I tell it to in Allmon.

I also do know how to setup multiple instances of DVSwich.

Any guidance on this?


Join main@DVSwitch.groups.io to automatically receive all group messages.