Date   

Re: MMDVM_Bridge Timeout

Steve N4IRS
 

What network are you using now?
Please show the [DMR Network] stanza from MMDVM_Bridge.ini

On 10/26/19 5:34 PM, Dexter Harroo wrote:
OK, Lemme look for some info on connecting to BM


Re: MMDVM_Bridge Timeout

Dexter Harroo
 

OK, Lemme look for some info on connecting to BM


Re: MMDVM_Bridge Timeout

Steve N4IRS
 

Try another MASTER

On 10/26/19 5:29 PM, Dexter Harroo wrote:
so trying another TG on the same network wont make sense?


Re: MMDVM_Bridge Timeout

Dexter Harroo
 

so trying another TG on the same network wont make sense?


Re: MMDVM_Bridge Timeout

Steve N4IRS
 

MMDVM_Bridge is loosing the connection to the Master. it has nothing to do with the TG.

On 10/26/19 5:16 PM, Dexter Harroo wrote:
No didn't have to because it worked before, but i will try connecting to another TG

On Sat, Oct 26, 2019 at 4:15 PM Steve N4IRS <szingman@...> wrote:
MMDVM_ridge is loosing connection to the Master. Have you tried another Master?

On 10/26/19 4:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter



--
73
De 9Y4C
Dexter Harroo


Re: MMDVM_Bridge Timeout

Dexter Harroo
 

No didn't have to because it worked before, but i will try connecting to another TG


On Sat, Oct 26, 2019 at 4:15 PM Steve N4IRS <szingman@...> wrote:
MMDVM_ridge is loosing connection to the Master. Have you tried another Master?

On 10/26/19 4:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter



--
73
De 9Y4C
Dexter Harroo


Re: MMDVM_Bridge Timeout

Steve N4IRS
 

MMDVM_ridge is loosing connection to the Master. Have you tried another Master?

On 10/26/19 4:07 PM, Dexter Harroo wrote:
Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter


MMDVM_Bridge Timeout

Dexter Harroo
 

Hi Guys,
I have MMDVM_Bridge setup to link a DMR Talkgroup to a ysf reflector, it has been working flawlessly for quite some time, recently i started having issues with the connection where it times out.
closing DMR network
opening DMR network
Login to the master has failed, retrying network connection
closing DMR network
opening DMR network
sending autorization 
sending configuration
logged into the master successfully
Login to the master has failed, retrying network connection.


and it keeps doing that over and over again, has any one else experienced this, can someone shed some light as to what may be the issue, so far i checked my ports on the router to make sure they're opened
9Y4C
Dexter


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Steve N4IRS
 

This is off the top of my head, I do not have a test platform I want to try it on. Do pay attention to the fact that each SYSTEM in hblink.cfg has a different SSID appended to the DMRID.
I suggest you watch the logs while testing each TG. Telling us it does not work, does not work. There is a reason for logs.

BRIDGES = {
    'TG1': [
            {'SYSTEM': 'TG-1',    'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'TG-2',    'TS': 1, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'TG-3',    'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [], 'OFF': [], 'RESET': []},
        ],
    'TG2': [
            {'SYSTEM': 'TG-1',    'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'TG-2',    'TS': 1, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'TG-3',    'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
        ],
    'TG3': [
            {'SYSTEM': 'TG-1',    'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'TG-2',    'TS': 1, 'TGID': 2, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
            {'SYSTEM': 'TG-3',    'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': [], 'RESET': []},
        ]
}


On 10/25/2019 12:37 PM, Skyler Fennell wrote:
Thank you Steve for your reply. 

I’ve tried that and it does not work. It only sends traffic to one of the BM talkgroups, and sometimes the other talkgroup gets some “blips” but never gets any audio.  I did make sure they all used different local ports and tried a few different rules.py settings. 

Could you give me an example of rules.py that you think works for what you just sent me?

Thank you,
Skyler 



On Fri, Oct 25, 2019 at 10:23 AM Steve N4IRS <szingman@...> wrote:
I don't know of any reason you would need to "double vocoder" Everything I see is either AMBE or analog. I also don't see why you can't have multiple connections to BM:

[TG-1]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54001
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212301
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-2]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54002
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212302
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-3]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 62031
MASTER_IP: 310x.repeater.net
MASTER_PORT: 54000
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212303
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

Maybe I'm missing something.
Steve N4IRS

On 10/25/2019 11:20 AM, Skyler Fennell wrote:
The thing about openbridge is I have to find someone at BM, and I've always had a hard time dealing with them and getting stuff to work, then it is a permanent connection, not something I can disconnect and edit on the fly to our communications needs. Also, support tickets are useless, I've submitted a few support tickets before on BM, and they usually just randomly disappear after 4 months of me waiting. 

I thought I would implement HBLink so I could get around double vocoding to bring in multiple talk-groups and systems such as fusion using an asterisk background, but maybe it is better just to do that and deal with the fact that call-sign translation does not happen. I can easily run multiple instances of MMDVMHost with the same 62031 outbound port at the same time, but it does not seem like HBLink will talk to BM that way. 

If there is any other way I can simply bridge Two talkgroups together using two "hotspot" instances, it would be greatly appreciated. It seems right now that I can only have 1 outbound connection to the BM network at a time on my HBlink instance. 

My Goal:
NORMAL OPERATION ( I CAN Get this to work Right now) 
ASL <---> ANALOG_BRDGE <---> HBLINK <----> BM SkyHub 310847, YSF REFLECTOR 

SEVERE WX Operation
ASL <---> ANALOG_BRIDGE <---> HBLINK <---> BM SkyHub 310847,BM Colorado WX Talkgroup, YSF Reflector

On Thu, Oct 24, 2019 at 10:32 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
Yeah I realized that after doing research after I already posted the question. I won't bridge TGIF in, I've never even messed with TGIF before.

So what is different between OpenBridge and the bridges used for repeater-1, repeater2 etc.? Could you send me a sample of openbridge? 

Even if I'm not bridging 2 brandmiester talkgroups, but say bridging to another HBLINK server on repeater-2, is my configuration right, or can you not have more than 1 repeater on different talkgroups connected to the same conference?



On Thu, Oct 24, 2019 at 10:18 AM Alec-N1AJW <alec.wasserman@...> wrote:
p.s. you can never bridge any BM TG's and TGIF TG's together.  they must remain autonomous of each other in your bridges..



Alec



Re: Bridging to multiple Brandmeister Talkgroups HBLink

Steve N4IRS
 

I would actually have to sit down and write one. I have done it with DMRlink and it's bridge. I think you want to ask in the HBlink subgroup.

On 10/25/2019 12:37 PM, Skyler Fennell wrote:
Thank you Steve for your reply. 

I’ve tried that and it does not work. It only sends traffic to one of the BM talkgroups, and sometimes the other talkgroup gets some “blips” but never gets any audio.  I did make sure they all used different local ports and tried a few different rules.py settings. 

Could you give me an example of rules.py that you think works for what you just sent me?

Thank you,
Skyler 



On Fri, Oct 25, 2019 at 10:23 AM Steve N4IRS <szingman@...> wrote:
I don't know of any reason you would need to "double vocoder" Everything I see is either AMBE or analog. I also don't see why you can't have multiple connections to BM:

[TG-1]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54001
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212301
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-2]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54002
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212302
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-3]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 62031
MASTER_IP: 310x.repeater.net
MASTER_PORT: 54000
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212303
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

Maybe I'm missing something.
Steve N4IRS

On 10/25/2019 11:20 AM, Skyler Fennell wrote:
The thing about openbridge is I have to find someone at BM, and I've always had a hard time dealing with them and getting stuff to work, then it is a permanent connection, not something I can disconnect and edit on the fly to our communications needs. Also, support tickets are useless, I've submitted a few support tickets before on BM, and they usually just randomly disappear after 4 months of me waiting. 

I thought I would implement HBLink so I could get around double vocoding to bring in multiple talk-groups and systems such as fusion using an asterisk background, but maybe it is better just to do that and deal with the fact that call-sign translation does not happen. I can easily run multiple instances of MMDVMHost with the same 62031 outbound port at the same time, but it does not seem like HBLink will talk to BM that way. 

If there is any other way I can simply bridge Two talkgroups together using two "hotspot" instances, it would be greatly appreciated. It seems right now that I can only have 1 outbound connection to the BM network at a time on my HBlink instance. 

My Goal:
NORMAL OPERATION ( I CAN Get this to work Right now) 
ASL <---> ANALOG_BRDGE <---> HBLINK <----> BM SkyHub 310847, YSF REFLECTOR 

SEVERE WX Operation
ASL <---> ANALOG_BRIDGE <---> HBLINK <---> BM SkyHub 310847,BM Colorado WX Talkgroup, YSF Reflector

On Thu, Oct 24, 2019 at 10:32 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
Yeah I realized that after doing research after I already posted the question. I won't bridge TGIF in, I've never even messed with TGIF before.

So what is different between OpenBridge and the bridges used for repeater-1, repeater2 etc.? Could you send me a sample of openbridge? 

Even if I'm not bridging 2 brandmiester talkgroups, but say bridging to another HBLINK server on repeater-2, is my configuration right, or can you not have more than 1 repeater on different talkgroups connected to the same conference?



On Thu, Oct 24, 2019 at 10:18 AM Alec-N1AJW <alec.wasserman@...> wrote:
p.s. you can never bridge any BM TG's and TGIF TG's together.  they must remain autonomous of each other in your bridges..



Alec



Re: Can work audio from Mic In or Inline Sound for USRPAudio.py with vox control and convert to DMR?

EA5GVK Joaquin
 

Hi Steve.
Can you help perform this process.

Mic In SoundCard or Inline -> USRPAudio.py (with vox control) -> Analog_Bridge -> md380_emu -> MMDVM_Bridge -> DMR.
To use it for example to broadcast news or any speech that we program on our website.
Or simply to pass our SdrSharp Audio for example to DMR.

If possible I would like you to explain to me please, how can I do the main part

MIC IN or IN LINE (SoundCard) -> USRPaudio.py with vox control -> Analog_Bridg


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Skyler Fennell
 

Thank you Steve for your reply. 

I’ve tried that and it does not work. It only sends traffic to one of the BM talkgroups, and sometimes the other talkgroup gets some “blips” but never gets any audio.  I did make sure they all used different local ports and tried a few different rules.py settings. 

Could you give me an example of rules.py that you think works for what you just sent me?

Thank you,
Skyler 



On Fri, Oct 25, 2019 at 10:23 AM Steve N4IRS <szingman@...> wrote:
I don't know of any reason you would need to "double vocoder" Everything I see is either AMBE or analog. I also don't see why you can't have multiple connections to BM:

[TG-1]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54001
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212301
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-2]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54002
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212302
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-3]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 62031
MASTER_IP: 310x.repeater.net
MASTER_PORT: 54000
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212303
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

Maybe I'm missing something.
Steve N4IRS

On 10/25/2019 11:20 AM, Skyler Fennell wrote:
The thing about openbridge is I have to find someone at BM, and I've always had a hard time dealing with them and getting stuff to work, then it is a permanent connection, not something I can disconnect and edit on the fly to our communications needs. Also, support tickets are useless, I've submitted a few support tickets before on BM, and they usually just randomly disappear after 4 months of me waiting. 

I thought I would implement HBLink so I could get around double vocoding to bring in multiple talk-groups and systems such as fusion using an asterisk background, but maybe it is better just to do that and deal with the fact that call-sign translation does not happen. I can easily run multiple instances of MMDVMHost with the same 62031 outbound port at the same time, but it does not seem like HBLink will talk to BM that way. 

If there is any other way I can simply bridge Two talkgroups together using two "hotspot" instances, it would be greatly appreciated. It seems right now that I can only have 1 outbound connection to the BM network at a time on my HBlink instance. 

My Goal:
NORMAL OPERATION ( I CAN Get this to work Right now) 
ASL <---> ANALOG_BRDGE <---> HBLINK <----> BM SkyHub 310847, YSF REFLECTOR 

SEVERE WX Operation
ASL <---> ANALOG_BRIDGE <---> HBLINK <---> BM SkyHub 310847,BM Colorado WX Talkgroup, YSF Reflector

On Thu, Oct 24, 2019 at 10:32 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
Yeah I realized that after doing research after I already posted the question. I won't bridge TGIF in, I've never even messed with TGIF before.

So what is different between OpenBridge and the bridges used for repeater-1, repeater2 etc.? Could you send me a sample of openbridge? 

Even if I'm not bridging 2 brandmiester talkgroups, but say bridging to another HBLINK server on repeater-2, is my configuration right, or can you not have more than 1 repeater on different talkgroups connected to the same conference?



On Thu, Oct 24, 2019 at 10:18 AM Alec-N1AJW <alec.wasserman@...> wrote:
p.s. you can never bridge any BM TG's and TGIF TG's together.  they must remain autonomous of each other in your bridges..



Alec


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Steve N4IRS
 
Edited

I don't know of any reason you would need to "double vocoder" Everything I see is either AMBE or analog. I also don't see why you can't have multiple connections to BM:

[TG-1]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54001
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212301
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-2]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54002
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212302
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

[TG-3]
MODE: PEER
ENABLED: True
LOOSE: False
EXPORT_AMBE: False
IP:
PORT: 54003
MASTER_IP: 310x.repeater.net
MASTER_PORT: 62031
PASSPHRASE: homebrew
CALLSIGN: W1ABC
RADIO_ID: 311212303
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 1

Maybe I'm missing something.
Steve N4IRS


On 10/25/2019 11:20 AM, Skyler Fennell wrote:
The thing about openbridge is I have to find someone at BM, and I've always had a hard time dealing with them and getting stuff to work, then it is a permanent connection, not something I can disconnect and edit on the fly to our communications needs. Also, support tickets are useless, I've submitted a few support tickets before on BM, and they usually just randomly disappear after 4 months of me waiting. 
 
I thought I would implement HBLink so I could get around double vocoding to bring in multiple talk-groups and systems such as fusion using an asterisk background, but maybe it is better just to do that and deal with the fact that call-sign translation does not happen. I can easily run multiple instances of MMDVMHost with the same 62031 outbound port at the same time, but it does not seem like HBLink will talk to BM that way. 
 
If there is any other way I can simply bridge Two talkgroups together using two "hotspot" instances, it would be greatly appreciated. It seems right now that I can only have 1 outbound connection to the BM network at a time on my HBlink instance. 
 
My Goal:
NORMAL OPERATION ( I CAN Get this to work Right now) 
ASL <---> ANALOG_BRDGE <---> HBLINK <----> BM SkyHub 310847, YSF REFLECTOR 
 
SEVERE WX Operation
ASL <---> ANALOG_BRIDGE <---> HBLINK <---> BM SkyHub 310847,BM Colorado WX Talkgroup, YSF Reflector

On Thu, Oct 24, 2019 at 10:32 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
Yeah I realized that after doing research after I already posted the question. I won't bridge TGIF in, I've never even messed with TGIF before.
 
So what is different between OpenBridge and the bridges used for repeater-1, repeater2 etc.? Could you send me a sample of openbridge? 
 
Even if I'm not bridging 2 brandmiester talkgroups, but say bridging to another HBLINK server on repeater-2, is my configuration right, or can you not have more than 1 repeater on different talkgroups connected to the same conference?
 
 

On Thu, Oct 24, 2019 at 10:18 AM Alec-N1AJW <alec.wasserman@...> wrote:
p.s. you can never bridge any BM TG's and TGIF TG's together.  they must remain autonomous of each other in your bridges..



Alec


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Skyler Fennell
 

The thing about openbridge is I have to find someone at BM, and I've always had a hard time dealing with them and getting stuff to work, then it is a permanent connection, not something I can disconnect and edit on the fly to our communications needs. Also, support tickets are useless, I've submitted a few support tickets before on BM, and they usually just randomly disappear after 4 months of me waiting. 

I thought I would implement HBLink so I could get around double vocoding to bring in multiple talk-groups and systems such as fusion using an asterisk background, but maybe it is better just to do that and deal with the fact that call-sign translation does not happen. I can easily run multiple instances of MMDVMHost with the same 62031 outbound port at the same time, but it does not seem like HBLink will talk to BM that way. 

If there is any other way I can simply bridge Two talkgroups together using two "hotspot" instances, it would be greatly appreciated. It seems right now that I can only have 1 outbound connection to the BM network at a time on my HBlink instance. 

My Goal:
NORMAL OPERATION ( I CAN Get this to work Right now) 
ASL <---> ANALOG_BRDGE <---> HBLINK <----> BM SkyHub 310847, YSF REFLECTOR 

SEVERE WX Operation
ASL <---> ANALOG_BRIDGE <---> HBLINK <---> BM SkyHub 310847,BM Colorado WX Talkgroup, YSF Reflector

On Thu, Oct 24, 2019 at 10:32 AM Skyler Fennell via Groups.Io <electricity440=gmail.com@groups.io> wrote:
Yeah I realized that after doing research after I already posted the question. I won't bridge TGIF in, I've never even messed with TGIF before.

So what is different between OpenBridge and the bridges used for repeater-1, repeater2 etc.? Could you send me a sample of openbridge? 

Even if I'm not bridging 2 brandmiester talkgroups, but say bridging to another HBLINK server on repeater-2, is my configuration right, or can you not have more than 1 repeater on different talkgroups connected to the same conference?



On Thu, Oct 24, 2019 at 10:18 AM Alec-N1AJW <alec.wasserman@...> wrote:
p.s. you can never bridge any BM TG's and TGIF TG's together.  they must remain autonomous of each other in your bridges..



Alec


Re: MMDVM_Bridge segfaulting on RPi 1B with Debian Buster

Ben KE8CGS
 

Florian,
I ran into something like this previously. What happened for me was the CPU was v6 and the code is compiled for minimum of v7 architecture. Instant segfault. If you run a debugger on it you’ll likely see an invalid instruction reported. I think the tool chain and CPU target advanced somewhere…

73 Ben KE8CGS

On Oct 24, 2019, at 4:26 PM, Florian Wolters <florian@florian-wolters.de> wrote:

Dear folks,

I am trying to rund MMDVM_Bridge on a RPi 1B with Debian Buster. The
binary exits with a Segementation Fault right after start. Nothing else
on the screen/console.
Is this binary not supposed to be run on that old hardware?

vy73 de Florian DF2ET






MMDVM_Bridge segfaulting on RPi 1B with Debian Buster

Florian Wolters
 

Dear folks,

I am trying to rund MMDVM_Bridge on a RPi 1B with Debian Buster. The
binary exits with a Segementation Fault right after start. Nothing else
on the screen/console.
Is this binary not supposed to be run on that old hardware?

vy73 de Florian DF2ET


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Skyler Fennell
 

Yeah I realized that after doing research after I already posted the question. I won't bridge TGIF in, I've never even messed with TGIF before.

So what is different between OpenBridge and the bridges used for repeater-1, repeater2 etc.? Could you send me a sample of openbridge? 

Even if I'm not bridging 2 brandmiester talkgroups, but say bridging to another HBLINK server on repeater-2, is my configuration right, or can you not have more than 1 repeater on different talkgroups connected to the same conference?



On Thu, Oct 24, 2019 at 10:18 AM Alec-N1AJW <alec.wasserman@...> wrote:
p.s. you can never bridge any BM TG's and TGIF TG's together.  they must remain autonomous of each other in your bridges..



Alec


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Alec-N1AJW
 

p.s. you can never bridge any BM TG's and TGIF TG's together.  they must remain autonomous of each other in your bridges..



Alec


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Alec-N1AJW
 

Use Open Bridge in HBlink.cfg.  Submit a support Ticket to BM and give them the TG's you want from BM.   These will then always be avail on TS1 once the bridge is made.  provide ip of your hblink, your callsign and id used and the tgs.   then you can just use the rules as you wish to bridge the talkgroups.


Alec
N1AJW


Re: Sgefault in MMDVM_Bridge

G7RPG - Peter Kendall
 

Hi Steve, nothing really. The second I transmit into the FCS reflector via another route, MMDVM_Bridge bombs out.

loglevel=1

I: 2019-10-24 15:04:39.512 Started the DMR Id lookup reload thread
M: 2019-10-24 15:04:39.512 YSF, Opening INI file: DVSwitch.ini
M: 2019-10-24 15:04:39.512 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-10-24 15:04:39.512 YSF, Setting [YSF] TXPort -> 35200
M: 2019-10-24 15:04:39.512 YSF, Setting [YSF] RXPort -> 35203
M: 2019-10-24 15:04:39.512 YSF, Setting [YSF] FallbackID -> 2345153
M: 2019-10-24 15:04:39.512 YSF, Setting [YSF] ExportTG -> 23526
M: 2019-10-24 15:04:39.512 YSF, Setting [YSF] Slot -> 2
M: 2019-10-24 15:04:39.512 YSF, Transmitting on 127.0.0.1:35200 and listening on port 35203.  Result = 1
M: 2019-10-24 15:04:39.512 MMDVM_Bridge-20180423 is running
Segmentation fault
root@ambe-dmr:/opt/MMDVM_Bridge_YSF#


Looking at the opposite MMDVM_Bridge

I: 2019-10-24 15:03:00.731 Started the DMR Id lookup reload thread
M: 2019-10-24 15:03:00.731 YSF, Opening INI file: DVSwitch.ini
M: 2019-10-24 15:03:00.731 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-10-24 15:03:00.731 YSF, Setting [YSF] TXPort -> 35203
M: 2019-10-24 15:03:00.731 YSF, Setting [YSF] RXPort -> 35200
M: 2019-10-24 15:03:00.731 YSF, Setting [YSF] FallbackID -> 2345153
M: 2019-10-24 15:03:00.731 YSF, Setting [YSF] ExportTG -> 23526
M: 2019-10-24 15:03:00.731 YSF, Setting [YSF] Slot -> 2
M: 2019-10-24 15:03:00.731 YSF, Transmitting on 127.0.0.1:35203 and listening on port 35200.  Result = 1
M: 2019-10-24 15:03:00.731 MMDVM_Bridge-20180423 is running
M: 2019-10-24 15:03:11.151 YSF, TX state = ON
I: 2019-10-24 15:03:11.151 YSF, Begin TX: src=2345153 rpt=0 dst=23526 slot=2 cc=0 metadata=HUBNet
I: 2019-10-24 15:03:11.263 YSF, Narrow transmit (72 bit)
M: 2019-10-24 15:03:13.569 YSF, TX state = OFF
M: 2019-10-24 15:03:22.002 YSF, received network data from G7RPG      to ALL        at FCS004-77
D: 2019-10-24 15:03:22.672 V/D Mode 2 Data, DT1
D: 2019-10-24 15:03:22.672 0000:  7D 22 62 5F 29 50 30 50 50 50                      *}"b_)P0PPP*
D: 2019-10-24 15:03:22.769 V/D Mode 2 Data, DT2
D: 2019-10-24 15:03:22.769 0000:  30 76 58 1C 6C 20 1C 20 03 DE                      *0vX.l . ..*
M: 2019-10-24 15:03:24.670 YSF, network watchdog has expired, 1.3 seconds, 0% packet loss, BER: 2.6%
M: 2019-10-24 15:04:44.278 YSF, received network data from G7RPG      to ALL        at FCS004-77
D: 2019-10-24 15:04:44.962 V/D Mode 2 Data, DT1
D: 2019-10-24 15:04:44.962 0000:  7E 22 62 5F 29 50 30 50 50 50                      *~"b_)P0PPP*
D: 2019-10-24 15:04:45.049 V/D Mode 2 Data, DT2
D: 2019-10-24 15:04:45.049 0000:  30 76 58 1C 6C 20 1C 20 03 DF                      *0vX.l . ..*
M: 2019-10-24 15:04:46.658 YSF, network watchdog has expired, 1.0 seconds, 0% packet loss, BER: 1.0%


Peter

On 24/10/2019 14:42, Steve N4IRS wrote:
Peter,
Thanks for the report. Can you show what was in the log before the crash. 

Steve N4IRS


Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of G7RPG - Peter Kendall <g7rpg@...>
Sent: Thursday, October 24, 2019 9:37:25 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Sgefault in MMDVM_Bridge
 

I've been experimenting using two instances of MMDVM_Bridge to connect a YSF reflector to an FCS reflector.

This is the setup

 

FCS <> YSFGateway <> MMDVM_Bridge <> MMDVM_Bridge <> YSFReflecor

All starts up fine but as soon as any traffic flows from the FCS reflector MMDVM_Bridge on that side of the link crashes instantly with this error

MMDVM_Bridge[8410]: segfault at 0 ip b7459b06 sp bfc61b04 error 4 in libc-2.24.so[b73db000+1b1000]

I've tried it on ARM and X64 with the same results.

Any ideas ?



73
Peter

G7RPG

 

4861 - 4880 of 9882