Date   

Re: Blog with P25<->DMR Info

Steve N4IRS
 

I hate to say it, I have built a few. They work. Same concept as all the rest. Enable the mode in MMDVM_Bridge and Analog_Bridge and match the ports.

On 2/12/2019 1:16 PM, Russell, KV4S wrote:
Has anyone had any luck getting this type of bridge setup?

I can't seem to get working. I think my analog_bridge_p25 is the problem it never shows any traffic after it's running.

I've gone by the 927 blog without any luck.

On Thu, Jan 31, 2019 at 3:07 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io> wrote:
i did.

I made another change here are the current logs and ini's it actually looks like everything is working but the p25 dashboard does not show traffice and the nxdn dashboard do not show i'm keying up from allstar.



On Thu, Jan 31, 2019 at 2:36 PM Steve N4IRS <szingman@...> wrote:
 Russell,
Have you started at one end and tested each program one at a time in the foreground?
BTW, you can include a zip file with your message. That way someone does not have to go to an external site just to get the zip file.

Steve

On 1/31/2019 3:26 PM, Russell, KV4S wrote:
Well, I got the P25 bridge uniquely named.
hmm it still doesn't appear to be bridged?

Lates logs and inis: https://we.tl/t-wIx3y9gFLe

not sure what i'm missing?

On Wed, Jan 30, 2019 at 4:38 PM <mike@...> wrote:
OK - a couple of things... your Analog Bridges need to be uniquely named, and have uniquely named .ini files. The .ini files are different for each as well. Review the Build and Configure sections on blog.927.org for how to create the needed files and tweak the ini files. 

Also - In the log snippet you just posted, P25 is the indicated mode, but you're supplying DMR-ID info. No need to do that for the P25 ini file. 
Also v2.0: The DMR-ID in your log has an extra digit in it - 313666507 - which might be causing the BM master connection issues if that's what you're using elsewhere in the setup. 

On Wed, Jan 30, 2019 at 2:28 PM Russell, KV4S <russelljthomas@...> wrote:
I: 2019-01-30 22:25:57.822 Analog Bridge is starting
M: 2019-01-30 22:25:57.823 Setting [GENERAL] logLevel -> 2
M: 2019-01-30 22:25:57.823 Setting [GENERAL] exportMetadata -> true
M: 2019-01-30 22:25:57.823 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-01-30 22:25:57.823 Setting [GENERAL] decoderFallBack -> true
M: 2019-01-30 22:25:57.823 Setting [GENERAL] useEmulator -> true
M: 2019-01-30 22:25:57.824 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-01-30 22:25:57.824 Setting [GENERAL] outputAudioDevice -> /dev/null
M: 2019-01-30 22:25:57.824 Setting [GENERAL] inputAudioDevice -> /dev/null
M: 2019-01-30 22:25:57.824 Setting [GENERAL] useMicrophone -> false
M: 2019-01-30 22:25:57.824 Setting [GENERAL] useVox -> false
M: 2019-01-30 22:25:57.824 Setting [GENERAL] voxDecay -> 2
M: 2019-01-30 22:25:57.824 Setting [GENERAL] voxTrigger -> 200
W: 2019-01-30 22:25:57.824 Using deprecated option "server"
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] server -> 127.0.0.1
W: 2019-01-30 22:25:57.824 Using deprecated option "fromDMRPort"
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] fromDMRPort -> 34100
W: 2019-01-30 22:25:57.824 Using deprecated option "toDMRPort"
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] toDMRPort -> 34103
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] ambeMode -> P25
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] gatewayDmrId -> 3136665
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] repeaterID -> 313666507
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] txTg -> 31777
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] colorCode -> 1
W: 2019-01-30 22:25:57.824 Using deprecated option "server"
M: 2019-01-30 22:25:57.824 Setting [USRP] server -> 127.0.0.1
W: 2019-01-30 22:25:57.824 Using deprecated option "toASLPort"
M: 2019-01-30 22:25:57.824 Setting [USRP] toASLPort -> 34001
W: 2019-01-30 22:25:57.824 Using deprecated option "fromASLPort"
M: 2019-01-30 22:25:57.824 Setting [USRP] fromASLPort -> 32001
M: 2019-01-30 22:25:57.824 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-01-30 22:25:57.824 Setting [USRP] agcGain -> 5.0
M: 2019-01-30 22:25:57.824 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2019-01-30 22:25:57.824 Setting [USRP] dmrGain -> 0.17
W: 2019-01-30 22:25:57.824 Using deprecated option "server"
M: 2019-01-30 22:25:57.824 Setting [DV3000] server -> 127.0.0.1
W: 2019-01-30 22:25:57.824 Using deprecated option "port"
M: 2019-01-30 22:25:57.824 Setting [DV3000] port -> 2460
W: 2019-01-30 22:25:57.824 ioctl reset error 
W: 2019-01-30 22:25:57.824 ioctl speed error 
W: 2019-01-30 22:25:57.824 ioctl stereo error 
W: 2019-01-30 22:25:57.824 ioctl setfmt error 
M: 2019-01-30 22:25:57.824 Audio In/Out Device: /dev/null
I: 2019-01-30 22:25:57.824 Open UDP listener on 127.0.0.1:34100
I: 2019-01-30 22:25:57.824 Open USRP on 127.0.0.1:34001
M: 2019-01-30 22:25:57.824 Connecting to DV3000 hardware......
W: 2019-01-30 22:25:58.845 DV3000 not found at 127.0.0.1:2460
I: 2019-01-30 22:25:59.455 Subscriber IDs loaded: 120633
I: 2019-01-30 22:25:59.455 Default extended metadata <K2HZE>
I: 2019-01-30 22:25:59.455 Connecting to emulator on host 127.0.0.1:2470
W: 2019-01-30 22:25:59.455 Using software MBE decoder version 1.2.3
W: 2019-01-30 22:25:59.455 Using software OP25 IMBE/AMBE vocoder
I: 2019-01-30 22:25:59.456 Starting Analog_Bridge --> USRP thread
I: 2019-01-30 22:25:59.459 Open UDP listener on 127.0.0.1:32001
I: 2019-01-30 22:25:59.459 Starting USRP --> IPSC_Bridge thread

On Wed, Jan 30, 2019 at 4:27 PM Russell Thomas <russelljthomas@...> wrote:
never mind, i think I fixed that. 

let me keep testing and see if i get further.

On Wed, Jan 30, 2019 at 4:21 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io> wrote:
great catch i had got interrupted and did not finish setting up the second analog bridge's service file to make it start.
I started it in the foreground and it's getting this?:  2019-01-30 22:16:18.817 Repeater ID can not be the same as subscriber ID

where can i find the P25Hosts.txt and what should it be set to?


On Wed, Jan 30, 2019 at 3:49 PM <mike@...> wrote:
According the logs, you only have one instance of Analog_Bridge running. You need 2. One for DMR and one for P25 (or perhaps didn't include that log)

I also see that you're loading 17 P25 Reflectors. While probably not critical, your P25Hosts.txt only needs the localhost reflector information, as it isn't meant to connect to others... 

Network Access Control (NAC) is analogous to CTCSS for P25. 

On Wed, Jan 30, 2019 at 1:12 PM Russell, KV4S <russelljthomas@...> wrote:
I have been following the blog working on a Bridge for a fellow in NY and I don't think somethings is linked up correctly but nothing is jumping out at me in the logs.

Logs are located here for review: https://we.tl/t-LYRjUm1WpC 

let me know what i'm missing.

Also, what is NAC? 

On Tue, Jan 29, 2019 at 11:30 AM Steve N4IRS <szingman@...> wrote:
Make these both true.

On 1/29/2019 12:19 PM, Kevin N9OIG wrote:
> M: 2019-01-29 17:11:35.760 Setting [GENERAL] decoderFallBack -> false
> M: 2019-01-29 17:11:35.760 Setting [GENERAL] useEmulator -> false







Re: Blog with P25<->DMR Info

 

Has anyone had any luck getting this type of bridge setup?

I can't seem to get working. I think my analog_bridge_p25 is the problem it never shows any traffic after it's running.

I've gone by the 927 blog without any luck.


On Thu, Jan 31, 2019 at 3:07 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io> wrote:
i did.

I made another change here are the current logs and ini's it actually looks like everything is working but the p25 dashboard does not show traffice and the nxdn dashboard do not show i'm keying up from allstar.



On Thu, Jan 31, 2019 at 2:36 PM Steve N4IRS <szingman@...> wrote:
 Russell,
Have you started at one end and tested each program one at a time in the foreground?
BTW, you can include a zip file with your message. That way someone does not have to go to an external site just to get the zip file.

Steve

On 1/31/2019 3:26 PM, Russell, KV4S wrote:
Well, I got the P25 bridge uniquely named.
hmm it still doesn't appear to be bridged?

Lates logs and inis: https://we.tl/t-wIx3y9gFLe

not sure what i'm missing?

On Wed, Jan 30, 2019 at 4:38 PM <mike@...> wrote:
OK - a couple of things... your Analog Bridges need to be uniquely named, and have uniquely named .ini files. The .ini files are different for each as well. Review the Build and Configure sections on blog.927.org for how to create the needed files and tweak the ini files. 

Also - In the log snippet you just posted, P25 is the indicated mode, but you're supplying DMR-ID info. No need to do that for the P25 ini file. 
Also v2.0: The DMR-ID in your log has an extra digit in it - 313666507 - which might be causing the BM master connection issues if that's what you're using elsewhere in the setup. 

On Wed, Jan 30, 2019 at 2:28 PM Russell, KV4S <russelljthomas@...> wrote:
I: 2019-01-30 22:25:57.822 Analog Bridge is starting
M: 2019-01-30 22:25:57.823 Setting [GENERAL] logLevel -> 2
M: 2019-01-30 22:25:57.823 Setting [GENERAL] exportMetadata -> true
M: 2019-01-30 22:25:57.823 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv
M: 2019-01-30 22:25:57.823 Setting [GENERAL] decoderFallBack -> true
M: 2019-01-30 22:25:57.823 Setting [GENERAL] useEmulator -> true
M: 2019-01-30 22:25:57.824 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470
M: 2019-01-30 22:25:57.824 Setting [GENERAL] outputAudioDevice -> /dev/null
M: 2019-01-30 22:25:57.824 Setting [GENERAL] inputAudioDevice -> /dev/null
M: 2019-01-30 22:25:57.824 Setting [GENERAL] useMicrophone -> false
M: 2019-01-30 22:25:57.824 Setting [GENERAL] useVox -> false
M: 2019-01-30 22:25:57.824 Setting [GENERAL] voxDecay -> 2
M: 2019-01-30 22:25:57.824 Setting [GENERAL] voxTrigger -> 200
W: 2019-01-30 22:25:57.824 Using deprecated option "server"
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] server -> 127.0.0.1
W: 2019-01-30 22:25:57.824 Using deprecated option "fromDMRPort"
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] fromDMRPort -> 34100
W: 2019-01-30 22:25:57.824 Using deprecated option "toDMRPort"
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] toDMRPort -> 34103
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] ambeMode -> P25
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] gatewayDmrId -> 3136665
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] repeaterID -> 313666507
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] txTg -> 31777
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] txTs -> 2
M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] colorCode -> 1
W: 2019-01-30 22:25:57.824 Using deprecated option "server"
M: 2019-01-30 22:25:57.824 Setting [USRP] server -> 127.0.0.1
W: 2019-01-30 22:25:57.824 Using deprecated option "toASLPort"
M: 2019-01-30 22:25:57.824 Setting [USRP] toASLPort -> 34001
W: 2019-01-30 22:25:57.824 Using deprecated option "fromASLPort"
M: 2019-01-30 22:25:57.824 Setting [USRP] fromASLPort -> 32001
M: 2019-01-30 22:25:57.824 Setting [USRP] aslAudio -> AUDIO_USE_GAIN
M: 2019-01-30 22:25:57.824 Setting [USRP] agcGain -> 5.0
M: 2019-01-30 22:25:57.824 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN
M: 2019-01-30 22:25:57.824 Setting [USRP] dmrGain -> 0.17
W: 2019-01-30 22:25:57.824 Using deprecated option "server"
M: 2019-01-30 22:25:57.824 Setting [DV3000] server -> 127.0.0.1
W: 2019-01-30 22:25:57.824 Using deprecated option "port"
M: 2019-01-30 22:25:57.824 Setting [DV3000] port -> 2460
W: 2019-01-30 22:25:57.824 ioctl reset error 
W: 2019-01-30 22:25:57.824 ioctl speed error 
W: 2019-01-30 22:25:57.824 ioctl stereo error 
W: 2019-01-30 22:25:57.824 ioctl setfmt error 
M: 2019-01-30 22:25:57.824 Audio In/Out Device: /dev/null
I: 2019-01-30 22:25:57.824 Open UDP listener on 127.0.0.1:34100
I: 2019-01-30 22:25:57.824 Open USRP on 127.0.0.1:34001
M: 2019-01-30 22:25:57.824 Connecting to DV3000 hardware......
W: 2019-01-30 22:25:58.845 DV3000 not found at 127.0.0.1:2460
I: 2019-01-30 22:25:59.455 Subscriber IDs loaded: 120633
I: 2019-01-30 22:25:59.455 Default extended metadata <K2HZE>
I: 2019-01-30 22:25:59.455 Connecting to emulator on host 127.0.0.1:2470
W: 2019-01-30 22:25:59.455 Using software MBE decoder version 1.2.3
W: 2019-01-30 22:25:59.455 Using software OP25 IMBE/AMBE vocoder
I: 2019-01-30 22:25:59.456 Starting Analog_Bridge --> USRP thread
I: 2019-01-30 22:25:59.459 Open UDP listener on 127.0.0.1:32001
I: 2019-01-30 22:25:59.459 Starting USRP --> IPSC_Bridge thread

On Wed, Jan 30, 2019 at 4:27 PM Russell Thomas <russelljthomas@...> wrote:
never mind, i think I fixed that. 

let me keep testing and see if i get further.

On Wed, Jan 30, 2019 at 4:21 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io> wrote:
great catch i had got interrupted and did not finish setting up the second analog bridge's service file to make it start.
I started it in the foreground and it's getting this?:  2019-01-30 22:16:18.817 Repeater ID can not be the same as subscriber ID

where can i find the P25Hosts.txt and what should it be set to?


On Wed, Jan 30, 2019 at 3:49 PM <mike@...> wrote:
According the logs, you only have one instance of Analog_Bridge running. You need 2. One for DMR and one for P25 (or perhaps didn't include that log)

I also see that you're loading 17 P25 Reflectors. While probably not critical, your P25Hosts.txt only needs the localhost reflector information, as it isn't meant to connect to others... 

Network Access Control (NAC) is analogous to CTCSS for P25. 

On Wed, Jan 30, 2019 at 1:12 PM Russell, KV4S <russelljthomas@...> wrote:
I have been following the blog working on a Bridge for a fellow in NY and I don't think somethings is linked up correctly but nothing is jumping out at me in the logs.

Logs are located here for review: https://we.tl/t-LYRjUm1WpC 

let me know what i'm missing.

Also, what is NAC? 

On Tue, Jan 29, 2019 at 11:30 AM Steve N4IRS <szingman@...> wrote:
Make these both true.

On 1/29/2019 12:19 PM, Kevin N9OIG wrote:
> M: 2019-01-29 17:11:35.760 Setting [GENERAL] decoderFallBack -> false
> M: 2019-01-29 17:11:35.760 Setting [GENERAL] useEmulator -> false






Re: MMDVM_Bridge : connect with suffix other than -B ?

EA4GAX - Sergio
 

Ok, thank you for the answerd.


Re: MMDVM_Bridge : connect with suffix other than -B ?

Santu OTTAVI (TK1BI)
 

Yes, it seems MMDVMHost does the same thing : I didn't find how to change the suffix in the config file. I assume the suffix is automatically appended according to the frequency band.

So, this is not related to MMDVM_Bridge.

73 de TK1BI

Le 27/01/2019 à 16:29, Steve N4IRS a écrit :

Does MMDVMHost do the same thing?
Is there anything in DMRGateway log?

Steve

On 1/27/19 10:00 AM, Santu OTTAVI (TK1BI) wrote:
Hi,

I'm using MMDVM_Bridge to connect to my XLX server through DMRGateway. On the XLX dashboard, it appears as "TK5KP-B". I'd like to change the "-B" suffix to "-G". Is it possible to do that ?

Thank you in advance. 73 de TK1BI



Re: D-Star

Steve N4IRS
 

No matter what you bridge there are several pieces of software involved. The methodology is still the same.

On 2/11/19 5:22 AM, Santu OTTAVI (TK1BI) wrote:

Le 09/02/2019 à 13:14, Steve N4IRS a écrit :
D-Star is not that different from DMR in setup.
Yes, but as far as there are several software involved, there are a lot of tiny things that can make things going wrong :-)

When I tested with ircddbgateway, XLX did not process the DCS connection request packet ! Investigating is still on the todo list :-)


Re: D-Star

Santu OTTAVI (TK1BI)
 

Le 09/02/2019 à 13:14, Steve N4IRS a écrit :
D-Star is not that different from DMR in setup.
Yes, but as far as there are several software involved, there are a lot of tiny things that can make things going wrong :-)

When I tested with ircddbgateway, XLX did not process the DCS connection request packet ! Investigating is still on the todo list :-)


DVSWITCH Hops?

Doug - W4DBG
 

I have recently had an issue with a user with the following setup:

Analog Radio <> Allstar Node <> DVSwitch Programs <>YSFGateway <> YSFReflector

The issue I had is that Yaesu's WiresX system that is an RF-Link from the YSF Reflector did not "accept" the traffic. In other words the "Local"light came on in the WiresX software but it did not send the traffic out to the WiresX room.

Is this because the data is losing too much data?

What the user should have done is connect directly to the Allstar node already connected to the system but users will be users.

As a network administrator I just don't want one sided conversations if I can come up with a solution.

Thanks!

Doug
W4DBG

--
Doug Gooden
troytrojan@...


Re: STM32-DVM V1 RX Audio level

Steve N4IRS
 

If I remember correctly it should be 3V peak to peak. Get as close as you can without going over.

On 2/9/19 10:44 PM, Skyler Fennell wrote:
I apologize if there is an answer somewhere else, but I just pulled out my old STM32 Version 1.0 without the RX Clip LED and need to set levels.

Below (I hope the photo went through) is the diagram of the RX circuit including  TP1, and TP2. Does anybody have documentation on what voltage needs to be present at TP2 with my discriminator audio?

Also, I'm curious what causes some radio receivers to have inverted, and others non-inverted data out of the discriminator audio port.

image.png

Thank You,
Skyler


STM32-DVM V1 RX Audio level

Skyler Fennell
 

I apologize if there is an answer somewhere else, but I just pulled out my old STM32 Version 1.0 without the RX Clip LED and need to set levels.

Below (I hope the photo went through) is the diagram of the RX circuit including  TP1, and TP2. Does anybody have documentation on what voltage needs to be present at TP2 with my discriminator audio?

Also, I'm curious what causes some radio receivers to have inverted, and others non-inverted data out of the discriminator audio port.

image.png

Thank You,
Skyler


DMR to ASL

K4VL
 

OK I can see activity on both Analog_Bridge and MMDVM_Bridge when I run them both in the foreground. I am not seeing anything on CLI and not seeing anything happen on Allmon that this ASL build is connected to. It looks to me that when I key my radio the signal is going to my hotspot, to brandmeister, to MMDVM_Bridge, to Analog Bridge. I am not getting anything to ASL. Any thoughts as to what I have done wrong?


Re: dvswitch.ini multiple instances

Steve KC1AWV
 

What OS are you using?

I'm running three servers. Two with Debian 9, one for my ASL hub, one for my XLX reflector. I have one Pi set up as an ASL node for a DStar bridge locally.

i coped it to where the program is running modified it for what I needed but when the node logged into brandmeister it kept trying to talk on the TG that was listed in the home directories ini not where i was telling it mmdvm's ini? does that make sense? 

I think I understand what you're saying. Were you running MMDVM_Bridge from the /home directory on console for that instance or were you starting a service? It sounds like you were running it in the foreground on the console, which means that whatever directory you were running MMDVM_Bridge from was the working directory, even if the .ini file was called from a different folder.

Example - say, pwd tells me I'm in /home/MMDVM_Bridge-Test. I run ./MMDVM_Bridge /opt/MMDVM_Bridge-Test2/MMDVM_Bridge.ini so, MMDVM_Bridge runs the .ini file from that different folder, BUT the DVSwitch.ini file is called from the working directory - in this case, /home/MMDVM_Bridge-Test. That's why in the .service file, there's a WorkingDirectory env variable, so it runs the correct instance of MMDVM_Bridge that will call the DVSwitch.ini from the same folder.

Which means, that even if you ran a specific .ini file for MMDVM_Bridge, it was running the DVSwitch.ini in the directory you launched it MMDVM_Bridge from, and the ports were loaded for a different instance that may have already been running, forwarding your data to the wrong instance of MMDVM_Bridge. Try launching MMDVM_Bridge from the directory that has the correct DVSwitch.ini file you need if you're running it in the foreground.

I think that's what's happening there.

On Sat, Feb 9, 2019 at 3:37 AM Russell, KV4S <russelljthomas@...> wrote:
I understand what you are saying. the directories make the difference not the file names. I've tried it with just distinct folder names then renaming the files in the folders, I've tried it both ways.

What OS are you using?

What I'm experiencing goes against how I think it's supposed to work and even what you are saying.

I've mainly been experimenting with a personl bridge on a PI where i have different talk groups linked to different private nodes and one DMR to YSF bridge.
I'm changing the ports in the dvswitch.inis like I should be no port duplication on what's being used.
I'm thinking something is conflicting. For example i downloaded an mmdvm ini from a server i worked on from someone else. I had it in the home directory.
i coped it to where the program is running modified it for what I needed but when the node logged into brandmeister it kept trying to talk on the TG that was listed in the home directories ini not where i was telling it mmdvm's ini? does that make sense? Also, i made my talk group static set it in brandmeister dashboard but it was making a dynamic tg to the other bridge in the cloud that had nothing to do with what was on the pi other that the ini i downloaded was in the /home directory.
when i deleted the home directories ini and restarted mmdvm that problem with the dashboard went away.
I'm making copies of everything, mmdvm, analog, and md380 each instance is in a unique folder, each file has a unique name except the dvswitch.ini.
same goes for all the services. I have the md380 on different ports as well.
I'm not saying it's perfect but I feel like I've done a pretty good job of making sure evething is setup like it should be. this conflict with audio and the bm dashboad is making me thing maybe there is a bug going on somewhere? maybe it's something weird with the PI OS?



On Fri, Feb 8, 2019 at 9:20 PM Steve KC1AWV <smiller@...> wrote:

[Edited Message Follows]

I'll give you an example,
 
I have two DMR connections, one for BM and one for XLX.
 
I have two folders, /opt/MMDVM_Bridge-BM and /opt/MMDVM_Bridge-XLX
 
In the service files, mmdvm_bridge-bm.service has a WorkingDirectory=/opt/MMDVM_Bridge-BM and the system runs the DVSwitch.ini file in that folder for my BM setup
And, mmdvm_bridge-xlx.service has a WorkingDirectory=/opt/MMDVM_Bridge-XLX and the system runs the DVSwitch.ini file in that folder for my XLX setup.
 
I didn't have to rename files, just the folders.

On Fri, Feb 8, 2019, 10:09 PM Steve KC1AWV <smiller@... wrote:
If you copy all the MMDVM_Bridge files from one folder to another, you do not need to rename any of the files. Just rename the folders. In the service files, changing the WorkingDirectory line to the folder you renamed, it will make the system run the DVSwitch.ini file in that folder.

On Fri, Feb 8, 2019, 7:44 PM Russell, KV4S <russelljthomas@... wrote:
Steve,
 
thanks for the response, yes i'm making new service files and naming them accordingly and changing the contents to reflect the new paths.
 
my question is around the dvswitch.ini file if i make a dvswitch_TGXXXX.ini
how do i tell mmdvm_bridge to use it.
 
if i simply rename it the log shows unable to fine dvswitch.ini

On Fri, Feb 8, 2019 at 5:17 PM Steve KC1AWV <smiller@...> wrote:
 - I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
Correct. You will also have to make a copy of the existing mmdvm_bridge.service file in /lib/systemd/system with a new name (like mmdvm_bridge-tgxxxxx) and change the line
 
WorkingDirectory=/opt/MMDVM_Bridge
 
to reflect the folder name for the unique instance of MMDVM_Bridge for it to read the correct DVSwitch.ini file. Then, start the new service using the new name you gave the copied service file.
 

On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.
 
However the DVSwitch.ini remains the same.
 
after seeing this in the comments
 
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.
 
I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
would it be added in the mmdvm_bridge_TGXXXX service file somewhere?
 
any suggestions?

 

 



--
Steve Miller
KC1AWV

 

 

 

 



--
Steve Miller
KC1AWV


Re: D-Star

K4VL
 

Thanks enjoy the ham fest 


On Sat, Feb 9, 2019, 6:14 AM Steve N4IRS <szingman@... wrote:
D-Star is not that different from DMR in setup. Change from DMR to D-Star in AB.ini and point at the D-Star ports in DV.ini. Add ircddbgateway. Enable D-Star in MB.ini Stir and let simmer for 30 minutes.

I am working on a complete set of sample files for use with DVSwitch Mobile that may help.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Charles Wiant via Groups.Io <kd8itc=aol.com@groups.io>
Sent: Friday, February 8, 2019 9:58:31 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] D-Star
 

Hello I am in the same boat got bridge running with dmr no problem looking for documentation for setting up DSTAR. Thank You Charles any help would be appreciated .


Re: D-Star

Steve N4IRS
 

D-Star is not that different from DMR in setup. Change from DMR to D-Star in AB.ini and point at the D-Star ports in DV.ini. Add ircddbgateway. Enable D-Star in MB.ini Stir and let simmer for 30 minutes.

I am working on a complete set of sample files for use with DVSwitch Mobile that may help.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Charles Wiant via Groups.Io <kd8itc@...>
Sent: Friday, February 8, 2019 9:58:31 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] D-Star
 

Hello I am in the same boat got bridge running with dmr no problem looking for documentation for setting up DSTAR. Thank You Charles any help would be appreciated .


Re: dvswitch.ini multiple instances

Steve N4IRS
 

In the service file (actually systemd unit file, also edit the execute line with the proper path to the executable and ini file.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve KC1AWV <smiller@...>
Sent: Friday, February 8, 2019 10:09:19 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] dvswitch.ini multiple instances
 
If you copy all the MMDVM_Bridge files from one folder to another, you do not need to rename any of the files. Just rename the folders. In the service files, changing the WorkingDirectory line to the folder you renamed, it will make the system run the DVSwitch.ini file in that folder.

On Fri, Feb 8, 2019, 7:44 PM Russell, KV4S <russelljthomas@... wrote:
Steve,

thanks for the response, yes i'm making new service files and naming them accordingly and changing the contents to reflect the new paths.

my question is around the dvswitch.ini file if i make a dvswitch_TGXXXX.ini
how do i tell mmdvm_bridge to use it.

if i simply rename it the log shows unable to fine dvswitch.ini

On Fri, Feb 8, 2019 at 5:17 PM Steve KC1AWV <smiller@...> wrote:
 - I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?

Correct. You will also have to make a copy of the existing mmdvm_bridge.service file in /lib/systemd/system with a new name (like mmdvm_bridge-tgxxxxx) and change the line

WorkingDirectory=/opt/MMDVM_Bridge

to reflect the folder name for the unique instance of MMDVM_Bridge for it to read the correct DVSwitch.ini file. Then, start the new service using the new name you gave the copied service file.


On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.

However the DVSwitch.ini remains the same.

after seeing this in the comments

; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?

would it be added in the mmdvm_bridge_TGXXXX service file somewhere?

any suggestions?



--
Steve Miller
KC1AWV


Re: dvswitch.ini multiple instances

Steve N4IRS
 

MMDVM_Birdge will find MMDVM.ini in 2 ways.
If you just run ./MMDVM_Bridge it will look for the MMDVM.ini in the /etc directory  if you have MMDVM_Bridge and MMDVM.ini in the same directory, run ./MMDVM_Bridge MMDVM.ini

It comes down to, Linux needs to know where the program is and MMDVM_Bridge needs to know where MMDVM.ini is.

MMDVM_Bridge will look for DVSwitch in the same directory as MB.

This is the best I can do typing on a phone.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Russell, KV4S <russelljthomas@...>
Sent: Friday, February 8, 2019 10:36:49 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] dvswitch.ini multiple instances
 
I understand what you are saying. the directories make the difference not the file names. I've tried it with just distinct folder names then renaming the files in the folders, I've tried it both ways.

What OS are you using?

What I'm experiencing goes against how I think it's supposed to work and even what you are saying.

I've mainly been experimenting with a personl bridge on a PI where i have different talk groups linked to different private nodes and one DMR to YSF bridge.
I'm changing the ports in the dvswitch.inis like I should be no port duplication on what's being used.
I'm thinking something is conflicting. For example i downloaded an mmdvm ini from a server i worked on from someone else. I had it in the home directory.
i coped it to where the program is running modified it for what I needed but when the node logged into brandmeister it kept trying to talk on the TG that was listed in the home directories ini not where i was telling it mmdvm's ini? does that make sense? Also, i made my talk group static set it in brandmeister dashboard but it was making a dynamic tg to the other bridge in the cloud that had nothing to do with what was on the pi other that the ini i downloaded was in the /home directory.
when i deleted the home directories ini and restarted mmdvm that problem with the dashboard went away.
I'm making copies of everything, mmdvm, analog, and md380 each instance is in a unique folder, each file has a unique name except the dvswitch.ini.
same goes for all the services. I have the md380 on different ports as well.
I'm not saying it's perfect but I feel like I've done a pretty good job of making sure evething is setup like it should be. this conflict with audio and the bm dashboad is making me thing maybe there is a bug going on somewhere? maybe it's something weird with the PI OS?



On Fri, Feb 8, 2019 at 9:20 PM Steve KC1AWV <smiller@...> wrote:

[Edited Message Follows]

I'll give you an example,
 
I have two DMR connections, one for BM and one for XLX.
 
I have two folders, /opt/MMDVM_Bridge-BM and /opt/MMDVM_Bridge-XLX
 
In the service files, mmdvm_bridge-bm.service has a WorkingDirectory=/opt/MMDVM_Bridge-BM and the system runs the DVSwitch.ini file in that folder for my BM setup
And, mmdvm_bridge-xlx.service has a WorkingDirectory=/opt/MMDVM_Bridge-XLX and the system runs the DVSwitch.ini file in that folder for my XLX setup.
 
I didn't have to rename files, just the folders.

On Fri, Feb 8, 2019, 10:09 PM Steve KC1AWV <smiller@... wrote:
If you copy all the MMDVM_Bridge files from one folder to another, you do not need to rename any of the files. Just rename the folders. In the service files, changing the WorkingDirectory line to the folder you renamed, it will make the system run the DVSwitch.ini file in that folder.

On Fri, Feb 8, 2019, 7:44 PM Russell, KV4S <russelljthomas@... wrote:
Steve,
 
thanks for the response, yes i'm making new service files and naming them accordingly and changing the contents to reflect the new paths.
 
my question is around the dvswitch.ini file if i make a dvswitch_TGXXXX.ini
how do i tell mmdvm_bridge to use it.
 
if i simply rename it the log shows unable to fine dvswitch.ini

On Fri, Feb 8, 2019 at 5:17 PM Steve KC1AWV <smiller@...> wrote:
 - I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
Correct. You will also have to make a copy of the existing mmdvm_bridge.service file in /lib/systemd/system with a new name (like mmdvm_bridge-tgxxxxx) and change the line
 
WorkingDirectory=/opt/MMDVM_Bridge
 
to reflect the folder name for the unique instance of MMDVM_Bridge for it to read the correct DVSwitch.ini file. Then, start the new service using the new name you gave the copied service file.
 

On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.
 
However the DVSwitch.ini remains the same.
 
after seeing this in the comments
 
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.
 
I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
would it be added in the mmdvm_bridge_TGXXXX service file somewhere?
 
any suggestions?

 

 



--
Steve Miller
KC1AWV

 

 

 

 


Re: dvswitch.ini multiple instances

Jonathan Herman
 

Hey Russel, just finished building it and it looks like all the configurations all took so once i repoint my dns for my work site I'll try it again. Turns out I missed one huge step and that was copying the 1999 stanza from the group, not sure how I skipped over that when I was reading but it was the first thing I noticed when I started working on it again.

On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.

However the DVSwitch.ini remains the same.

after seeing this in the comments

; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?

would it be added in the mmdvm_bridge_TGXXXX service file somewhere?

any suggestions?


Re: dvswitch.ini multiple instances

Peter M0NWI
 

You’ve done the obvious and changed the Ip port numbers you’re using for the second instance?
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Russell, KV4S <russelljthomas@...>
Sent: 09 February 2019 03:36:49
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] dvswitch.ini multiple instances
 
I understand what you are saying. the directories make the difference not the file names. I've tried it with just distinct folder names then renaming the files in the folders, I've tried it both ways.

What OS are you using?

What I'm experiencing goes against how I think it's supposed to work and even what you are saying.

I've mainly been experimenting with a personl bridge on a PI where i have different talk groups linked to different private nodes and one DMR to YSF bridge.
I'm changing the ports in the dvswitch.inis like I should be no port duplication on what's being used.
I'm thinking something is conflicting. For example i downloaded an mmdvm ini from a server i worked on from someone else. I had it in the home directory.
i coped it to where the program is running modified it for what I needed but when the node logged into brandmeister it kept trying to talk on the TG that was listed in the home directories ini not where i was telling it mmdvm's ini? does that make sense? Also, i made my talk group static set it in brandmeister dashboard but it was making a dynamic tg to the other bridge in the cloud that had nothing to do with what was on the pi other that the ini i downloaded was in the /home directory.
when i deleted the home directories ini and restarted mmdvm that problem with the dashboard went away.
I'm making copies of everything, mmdvm, analog, and md380 each instance is in a unique folder, each file has a unique name except the dvswitch.ini.
same goes for all the services. I have the md380 on different ports as well.
I'm not saying it's perfect but I feel like I've done a pretty good job of making sure evething is setup like it should be. this conflict with audio and the bm dashboad is making me thing maybe there is a bug going on somewhere? maybe it's something weird with the PI OS?



On Fri, Feb 8, 2019 at 9:20 PM Steve KC1AWV <smiller@...> wrote:

[Edited Message Follows]

I'll give you an example,
 
I have two DMR connections, one for BM and one for XLX.
 
I have two folders, /opt/MMDVM_Bridge-BM and /opt/MMDVM_Bridge-XLX
 
In the service files, mmdvm_bridge-bm.service has a WorkingDirectory=/opt/MMDVM_Bridge-BM and the system runs the DVSwitch.ini file in that folder for my BM setup
And, mmdvm_bridge-xlx.service has a WorkingDirectory=/opt/MMDVM_Bridge-XLX and the system runs the DVSwitch.ini file in that folder for my XLX setup.
 
I didn't have to rename files, just the folders.

On Fri, Feb 8, 2019, 10:09 PM Steve KC1AWV <smiller@... wrote:
If you copy all the MMDVM_Bridge files from one folder to another, you do not need to rename any of the files. Just rename the folders. In the service files, changing the WorkingDirectory line to the folder you renamed, it will make the system run the DVSwitch.ini file in that folder.

On Fri, Feb 8, 2019, 7:44 PM Russell, KV4S <russelljthomas@... wrote:
Steve,
 
thanks for the response, yes i'm making new service files and naming them accordingly and changing the contents to reflect the new paths.
 
my question is around the dvswitch.ini file if i make a dvswitch_TGXXXX.ini
how do i tell mmdvm_bridge to use it.
 
if i simply rename it the log shows unable to fine dvswitch.ini

On Fri, Feb 8, 2019 at 5:17 PM Steve KC1AWV <smiller@...> wrote:
 - I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
Correct. You will also have to make a copy of the existing mmdvm_bridge.service file in /lib/systemd/system with a new name (like mmdvm_bridge-tgxxxxx) and change the line
 
WorkingDirectory=/opt/MMDVM_Bridge
 
to reflect the folder name for the unique instance of MMDVM_Bridge for it to read the correct DVSwitch.ini file. Then, start the new service using the new name you gave the copied service file.
 

On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.
 
However the DVSwitch.ini remains the same.
 
after seeing this in the comments
 
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.
 
I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
would it be added in the mmdvm_bridge_TGXXXX service file somewhere?
 
any suggestions?

 

 



--
Steve Miller
KC1AWV

 

 

 

 


Re: dvswitch.ini multiple instances

 

I understand what you are saying. the directories make the difference not the file names. I've tried it with just distinct folder names then renaming the files in the folders, I've tried it both ways.

What OS are you using?

What I'm experiencing goes against how I think it's supposed to work and even what you are saying.

I've mainly been experimenting with a personl bridge on a PI where i have different talk groups linked to different private nodes and one DMR to YSF bridge.
I'm changing the ports in the dvswitch.inis like I should be no port duplication on what's being used.
I'm thinking something is conflicting. For example i downloaded an mmdvm ini from a server i worked on from someone else. I had it in the home directory.
i coped it to where the program is running modified it for what I needed but when the node logged into brandmeister it kept trying to talk on the TG that was listed in the home directories ini not where i was telling it mmdvm's ini? does that make sense? Also, i made my talk group static set it in brandmeister dashboard but it was making a dynamic tg to the other bridge in the cloud that had nothing to do with what was on the pi other that the ini i downloaded was in the /home directory.
when i deleted the home directories ini and restarted mmdvm that problem with the dashboard went away.
I'm making copies of everything, mmdvm, analog, and md380 each instance is in a unique folder, each file has a unique name except the dvswitch.ini.
same goes for all the services. I have the md380 on different ports as well.
I'm not saying it's perfect but I feel like I've done a pretty good job of making sure evething is setup like it should be. this conflict with audio and the bm dashboad is making me thing maybe there is a bug going on somewhere? maybe it's something weird with the PI OS?



On Fri, Feb 8, 2019 at 9:20 PM Steve KC1AWV <smiller@...> wrote:

[Edited Message Follows]

I'll give you an example,
 
I have two DMR connections, one for BM and one for XLX.
 
I have two folders, /opt/MMDVM_Bridge-BM and /opt/MMDVM_Bridge-XLX
 
In the service files, mmdvm_bridge-bm.service has a WorkingDirectory=/opt/MMDVM_Bridge-BM and the system runs the DVSwitch.ini file in that folder for my BM setup
And, mmdvm_bridge-xlx.service has a WorkingDirectory=/opt/MMDVM_Bridge-XLX and the system runs the DVSwitch.ini file in that folder for my XLX setup.
 
I didn't have to rename files, just the folders.

On Fri, Feb 8, 2019, 10:09 PM Steve KC1AWV <smiller@... wrote:
If you copy all the MMDVM_Bridge files from one folder to another, you do not need to rename any of the files. Just rename the folders. In the service files, changing the WorkingDirectory line to the folder you renamed, it will make the system run the DVSwitch.ini file in that folder.

On Fri, Feb 8, 2019, 7:44 PM Russell, KV4S <russelljthomas@... wrote:
Steve,
 
thanks for the response, yes i'm making new service files and naming them accordingly and changing the contents to reflect the new paths.
 
my question is around the dvswitch.ini file if i make a dvswitch_TGXXXX.ini
how do i tell mmdvm_bridge to use it.
 
if i simply rename it the log shows unable to fine dvswitch.ini

On Fri, Feb 8, 2019 at 5:17 PM Steve KC1AWV <smiller@...> wrote:
 - I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
Correct. You will also have to make a copy of the existing mmdvm_bridge.service file in /lib/systemd/system with a new name (like mmdvm_bridge-tgxxxxx) and change the line
 
WorkingDirectory=/opt/MMDVM_Bridge
 
to reflect the folder name for the unique instance of MMDVM_Bridge for it to read the correct DVSwitch.ini file. Then, start the new service using the new name you gave the copied service file.
 

On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.
 
However the DVSwitch.ini remains the same.
 
after seeing this in the comments
 
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.
 
I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
would it be added in the mmdvm_bridge_TGXXXX service file somewhere?
 
any suggestions?

 

 



--
Steve Miller
KC1AWV

 

 

 

 


Re: dvswitch.ini multiple instances

Steve KC1AWV
 
Edited

I'll give you an example,
 
I have two DMR connections, one for BM and one for XLX.
 
I have two folders, /opt/MMDVM_Bridge-BM and /opt/MMDVM_Bridge-XLX
 
In the service files, mmdvm_bridge-bm.service has a WorkingDirectory=/opt/MMDVM_Bridge-BM and the system runs the DVSwitch.ini file in that folder for my BM setup
And, mmdvm_bridge-xlx.service has a WorkingDirectory=/opt/MMDVM_Bridge-XLX and the system runs the DVSwitch.ini file in that folder for my XLX setup.
 
I didn't have to rename files, just the folders.

On Fri, Feb 8, 2019, 10:09 PM Steve KC1AWV <smiller@... wrote:
If you copy all the MMDVM_Bridge files from one folder to another, you do not need to rename any of the files. Just rename the folders. In the service files, changing the WorkingDirectory line to the folder you renamed, it will make the system run the DVSwitch.ini file in that folder.

On Fri, Feb 8, 2019, 7:44 PM Russell, KV4S <russelljthomas@... wrote:
Steve,
 
thanks for the response, yes i'm making new service files and naming them accordingly and changing the contents to reflect the new paths.
 
my question is around the dvswitch.ini file if i make a dvswitch_TGXXXX.ini
how do i tell mmdvm_bridge to use it.
 
if i simply rename it the log shows unable to fine dvswitch.ini

On Fri, Feb 8, 2019 at 5:17 PM Steve KC1AWV <smiller@...> wrote:
 - I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
Correct. You will also have to make a copy of the existing mmdvm_bridge.service file in /lib/systemd/system with a new name (like mmdvm_bridge-tgxxxxx) and change the line
 
WorkingDirectory=/opt/MMDVM_Bridge
 
to reflect the folder name for the unique instance of MMDVM_Bridge for it to read the correct DVSwitch.ini file. Then, start the new service using the new name you gave the copied service file.
 

On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.
 
However the DVSwitch.ini remains the same.
 
after seeing this in the comments
 
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.
 
I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?
 
would it be added in the mmdvm_bridge_TGXXXX service file somewhere?
 
any suggestions?

 

 



--
Steve Miller
KC1AWV

 

 

 

 


Re: dvswitch.ini multiple instances

Steve KC1AWV
 

If you copy all the MMDVM_Bridge files from one folder to another, you do not need to rename any of the files. Just rename the folders. In the service files, changing the WorkingDirectory line to the folder you renamed, it will make the system run the DVSwitch.ini file in that folder.


On Fri, Feb 8, 2019, 7:44 PM Russell, KV4S <russelljthomas@... wrote:
Steve,

thanks for the response, yes i'm making new service files and naming them accordingly and changing the contents to reflect the new paths.

my question is around the dvswitch.ini file if i make a dvswitch_TGXXXX.ini
how do i tell mmdvm_bridge to use it.

if i simply rename it the log shows unable to fine dvswitch.ini

On Fri, Feb 8, 2019 at 5:17 PM Steve KC1AWV <smiller@...> wrote:
 - I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?

Correct. You will also have to make a copy of the existing mmdvm_bridge.service file in /lib/systemd/system with a new name (like mmdvm_bridge-tgxxxxx) and change the line

WorkingDirectory=/opt/MMDVM_Bridge

to reflect the folder name for the unique instance of MMDVM_Bridge for it to read the correct DVSwitch.ini file. Then, start the new service using the new name you gave the copied service file.


On Fri, Feb 8, 2019 at 5:24 PM Russell, KV4S <russelljthomas@...> wrote:
Bueller? ;)

On Thu, Feb 7, 2019, 2:26 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io wrote:
I need some help I've been experiences audio disappearing whenever I try setting up multiple instances of MMDVM. It works fine when using one instance but when I add a second or more that's when the issue appears. I've been duplicating the MMDVM_Bridge folder and calling it MMDVM_Bridge_TGXXXX. In the duplicated folder I make the program and ini also represent the name changed.

However the DVSwitch.ini remains the same.

after seeing this in the comments

; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

I'm thinking i need to make my DVSwitch.ini unique on the other instaces as well but i don't know how to do it for the environment variable?

would it be added in the mmdvm_bridge_TGXXXX service file somewhere?

any suggestions?



--
Steve Miller
KC1AWV

6001 - 6020 of 9203