Date   

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

 


Re: temporarily switching from AMBE to software vocoders

Patrick Perdue
 

I forgot to mention that the XLX reflector is connected to DMR through an interlink, if that matters.

On 10/24/2019 9:37 AM, Patrick Perdue via Groups.Io wrote:
Hi all:

I am using XLXD and ambed with two ThumbDV's to bridge DMR to D STAR. XLXD is on a VPS, and I have a box in my apartment with the physical vocoders. Currently, the transcoding is done by XLXD connected to my remote ambed.

I'm moving soon, and need a way to keep the translation going for a week or two. What is the best way to shove everything to software on the VPS until I am settled, and can re-establish ambed?

Thanks and 73

KE4DYI



Re: Sgefault in MMDVM_Bridge

Steve N4IRS
 

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

 


temporarily switching from AMBE to software vocoders

Patrick Perdue
 

Hi all:

I am using XLXD and ambed with two ThumbDV's to bridge DMR to D STAR. XLXD is on a VPS, and I have a box in my apartment with the physical vocoders. Currently, the transcoding is done by XLXD connected to my remote ambed.

I'm moving soon, and need a way to keep the translation going for a week or two. What is the best way to shove everything to software on the VPS until I am settled, and can re-establish ambed?

Thanks and 73

KE4DYI


Sgefault in MMDVM_Bridge

G7RPG - Peter Kendall
 

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

 


Re: ADVICE FOR USING ARDUINO2560+AMBE3000

Steve N4IRS
 

Tony,
Analog_Bridge supports the NW Digital Radio PiDV™ (formerly DV3000) and ThumbDV. You can also use AMBEServer for hardware. Analog_Bridge supports md380-emu for AMBE and built in P25 and D-Star software emulation. If you want to use your  arduino+ambe3000 with Analog_bridge I suggest you check to see if it can be used with AMBEServer.

73, Steve N4IRS

On 10/24/2019 3:55 AM, btp@... wrote:
Good Morning:
I have this situation and after hitting everything I will appreciate any advice: I'm trying to use physical ambe3000 installed on a arduino 2560. this setup works perfect on Win-Bluedv with the correct fw installed on my board as per former instructions (I commment this just fyi to get the picture the board is ok) . the point is when I connect the arduino+ambe300 setup to the RPI  (I'm using EA5GVK image), it seems the system does not detect the physical ambe and, as the screen reads (no DV3000 found...), turns to the sw emulation on port 2470. Please correct me if I'm wrong... On the txt file for ambe log located at TEMP, I can only see that the serial port is open but no reference to the ambe board, so that's another symptom that leads me to think the system does not recognize my ambe board.
Anyway the system works perfect but I'd love to see this worked out. any help or advice will be much appreciated.
REgards from Madrid,
Tony
EA4gvr
btp@...


ADVICE FOR USING ARDUINO2560+AMBE3000

btp@...
 

Good Morning:
I have this situation and after hitting everything I will appreciate any advice: I'm trying to use physical ambe3000 installed on a arduino 2560. this setup works perfect on Win-Bluedv with the correct fw installed on my board as per former instructions (I commment this just fyi to get the picture the board is ok) . the point is when I connect the arduino+ambe300 setup to the RPI  (I'm using EA5GVK image), it seems the system does not detect the physical ambe and, as the screen reads (no DV3000 found...), turns to the sw emulation on port 2470. Please correct me if I'm wrong... On the txt file for ambe log located at TEMP, I can only see that the serial port is open but no reference to the ambe board, so that's another symptom that leads me to think the system does not recognize my ambe board.
Anyway the system works perfect but I'd love to see this worked out. any help or advice will be much appreciated.
REgards from Madrid,
Tony
EA4gvr
btp@...


Re: Bridging to multiple Brandmeister Talkgroups HBLink

Skyler Fennell
 

Also, nevermind / just kidding on the TGIF. Pretend I didn't say that


On Wed, Oct 23, 2019 at 10:40 PM Skyler F <electricity440@...> wrote:
I have a need to bridge in another DMR brandmeister talk-group into an HBLink DMR server. This is to connect a Colorado repeater network to a weather net, and I have permission on both talk-groups. I hope this isn't against BM's terms of service, I would like an answer anyways just for educational purposes because I will eventually do this between TGIF and BM in the future once I have permission from TGIF.  

GOAL:
TALKGROUP_2_BRANDMEISTER  <---->  TALKGROUP_1_HBLINK  <----> TALKGROUP_1_BRANDMEISTER

On my HBLink.cfg, I have created 3 stanzas. MASTER1, REPEATER1, and REPEATER2. 
Repeater 1 and Repeater 2 are both connected to the brandmeister network using a different local port and DMR ID.

HBLINK.CFG Important STANZAS:

[MASTER-1]

MODE: MASTER

ENABLED: True

REPEAT: True

MAX_PEERS: 10

EXPORT_AMBE: False

IP:

PORT: 62030

PASSPHRASE: passw0rd

GROUP_HANGTIME: 0

#This was set to 5

USE_ACL: True

REG_ACL: DENY:1

SUB_ACL: DENY:1

TGID_TS1_ACL: PERMIT:ALL

TGID_TS2_ACL: PERMIT:ALL


[REPEATER-1]

MODE: PEER

ENABLED: True

LOOSE: False

EXPORT_AMBE: False

IP:

PORT: 54009

MASTER_IP: 64.94.238.196

MASTER_PORT: 62031

PASSPHRASE: passw0rd

CALLSIGN: W0SKY

RADIO_ID: my_id_02

COLORCODE: 1

SLOTS: 3

GROUP_HANGTIME: 0

(omitted the rest of the not importatn stuff)


[REPEATER-2]

MODE: PEER

ENABLED: True

LOOSE: False

EXPORT_AMBE: False

IP:

PORT: 54008

MASTER_IP: 64.94.238.196

MASTER_PORT: 62031

PASSPHRASE: passw0rd

CALLSIGN: W0SKY

RADIO_ID: my_id_03

COLORCODE: 1

SLOTS: 3

GROUP_HANGTIME: 0

(omitted the rest of the not importatn stuff)


RULES.PY. I've tried it both ways, but either way it will ONLY bridge to ONE Talkgroup, it will not chose both:

First Attempt:

BRIDGES = {

    'TEST': [

            {'SYSTEM': 'MASTER-1',    'TS': 2, 'TGID': TALKGROUP_1_HBLINK,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

            {'SYSTEM': 'REPEATER-1',    'TS': 2, 'TGID': TALKGROUP_1_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

           {'SYSTEM': 'REPEATER-2',    'TS': 2, 'TGID': TALKGROUP_2_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

        ]

Audio only routes between TALKGROUP_1_HBLINK and one of the brandmeister talkgroups, not both. Trying each one individually works fine. 

Second Attempt:

BRIDGES = {

    'TEST': [

            {'SYSTEM': 'MASTER-1',    'TS': 2, 'TGID': TALKGROUP_1_HBLINK,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

            {'SYSTEM': 'REPEATER-1',    'TS': 2, 'TGID': TALKGROUP_1_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

        ],


    'TESTA': [

            {'SYSTEM': 'MASTER-1',    'TS': 2, 'TGID': TALKGROUP_1_HBLINK,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},


           {'SYSTEM': 'REPEATER-2',    'TS': 2, 'TGID': TALKGROUP_2_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

        ]

}


Also, if it matters, the HBLINK TG 1 is equal to the BM TG 1. I can make them different.



Bridging to multiple Brandmeister Talkgroups HBLink

Skyler Fennell
 

I have a need to bridge in another DMR brandmeister talk-group into an HBLink DMR server. This is to connect a Colorado repeater network to a weather net, and I have permission on both talk-groups. I hope this isn't against BM's terms of service, I would like an answer anyways just for educational purposes because I will eventually do this between TGIF and BM in the future once I have permission from TGIF.  

GOAL:
TALKGROUP_2_BRANDMEISTER  <---->  TALKGROUP_1_HBLINK  <----> TALKGROUP_1_BRANDMEISTER

On my HBLink.cfg, I have created 3 stanzas. MASTER1, REPEATER1, and REPEATER2. 
Repeater 1 and Repeater 2 are both connected to the brandmeister network using a different local port and DMR ID.

HBLINK.CFG Important STANZAS:

[MASTER-1]

MODE: MASTER

ENABLED: True

REPEAT: True

MAX_PEERS: 10

EXPORT_AMBE: False

IP:

PORT: 62030

PASSPHRASE: passw0rd

GROUP_HANGTIME: 0

#This was set to 5

USE_ACL: True

REG_ACL: DENY:1

SUB_ACL: DENY:1

TGID_TS1_ACL: PERMIT:ALL

TGID_TS2_ACL: PERMIT:ALL


[REPEATER-1]

MODE: PEER

ENABLED: True

LOOSE: False

EXPORT_AMBE: False

IP:

PORT: 54009

MASTER_IP: 64.94.238.196

MASTER_PORT: 62031

PASSPHRASE: passw0rd

CALLSIGN: W0SKY

RADIO_ID: my_id_02

COLORCODE: 1

SLOTS: 3

GROUP_HANGTIME: 0

(omitted the rest of the not importatn stuff)


[REPEATER-2]

MODE: PEER

ENABLED: True

LOOSE: False

EXPORT_AMBE: False

IP:

PORT: 54008

MASTER_IP: 64.94.238.196

MASTER_PORT: 62031

PASSPHRASE: passw0rd

CALLSIGN: W0SKY

RADIO_ID: my_id_03

COLORCODE: 1

SLOTS: 3

GROUP_HANGTIME: 0

(omitted the rest of the not importatn stuff)


RULES.PY. I've tried it both ways, but either way it will ONLY bridge to ONE Talkgroup, it will not chose both:

First Attempt:

BRIDGES = {

    'TEST': [

            {'SYSTEM': 'MASTER-1',    'TS': 2, 'TGID': TALKGROUP_1_HBLINK,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

            {'SYSTEM': 'REPEATER-1',    'TS': 2, 'TGID': TALKGROUP_1_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

           {'SYSTEM': 'REPEATER-2',    'TS': 2, 'TGID': TALKGROUP_2_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

        ]

Audio only routes between TALKGROUP_1_HBLINK and one of the brandmeister talkgroups, not both. Trying each one individually works fine. 

Second Attempt:

BRIDGES = {

    'TEST': [

            {'SYSTEM': 'MASTER-1',    'TS': 2, 'TGID': TALKGROUP_1_HBLINK,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

            {'SYSTEM': 'REPEATER-1',    'TS': 2, 'TGID': TALKGROUP_1_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

        ],


    'TESTA': [

            {'SYSTEM': 'MASTER-1',    'TS': 2, 'TGID': TALKGROUP_1_HBLINK,    'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},


           {'SYSTEM': 'REPEATER-2',    'TS': 2, 'TGID': TALKGROUP_2_BRANDMEISTER, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE',  'ON': [2,], 'OFF': [9,10], 'RESET': []},

        ]

}


Also, if it matters, the HBLINK TG 1 is equal to the BM TG 1. I can make them different.



Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

F/W3PO <w3po.vq9po@...>
 

success!!!
Thank you very much Russel
73 de Pat W3PO in the Philippines for the winter.


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

F/W3PO <w3po.vq9po@...>
 

Well thank you Russel
I will try with vnc viewer. Never used it before but I think I can figure it out.

73 de Pat W3PO

On Tue, 22 Oct 2019, 6:34 am Russell, KV4S, <russelljthomas@...> wrote:
i got mine working by using VNC Viewer to see the desktop then run this in a terminal window 
sudo ircddbgatewayconfig  
it took about 3-4 minutes for this to come up for me.
it wouldn't let me do it from an ssh window remotely.
i think it's the dplus authentication it had my callsign with a C just make it your callsign and dstar should work.

On Mon, Oct 21, 2019 at 5:26 PM F/W3PO <w3po.vq9po@...> wrote:
hello all 
update DMR works but I have the same issue as KV2S on Dstar. No problem on rx but nothing is transmitted.
when on DVswitch mobile the app shows transmit and the ptt is red plus the timer is counting up.
I have check on the dstar dashboard and my signal does not register and obviously no audio coming out.
Thank you in advance for any hints or help
Cheers de Pat W3PO 


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

 

i got mine working by using VNC Viewer to see the desktop then run this in a terminal window 
sudo ircddbgatewayconfig  
it took about 3-4 minutes for this to come up for me.
it wouldn't let me do it from an ssh window remotely.
i think it's the dplus authentication it had my callsign with a C just make it your callsign and dstar should work.

On Mon, Oct 21, 2019 at 5:26 PM F/W3PO <w3po.vq9po@...> wrote:
hello all 
update DMR works but I have the same issue as KV2S on Dstar. No problem on rx but nothing is transmitted.
when on DVswitch mobile the app shows transmit and the ptt is red plus the timer is counting up.
I have check on the dstar dashboard and my signal does not register and obviously no audio coming out.
Thank you in advance for any hints or help
Cheers de Pat W3PO 


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

F/W3PO <w3po.vq9po@...>
 

hello all 
update DMR works but I have the same issue as KV2S on Dstar. No problem on rx but nothing is transmitted.
when on DVswitch mobile the app shows transmit and the ptt is red plus the timer is counting up.
I have check on the dstar dashboard and my signal does not register and obviously no audio coming out.
Thank you in advance for any hints or help
Cheers de Pat W3PO 


Re: BM to XLX via MMDVM_Bridge - Doc version 2.0

Jamie R. Cid <jay@...>
 

Hello,

Does this require dongles for transcoding? I ask as I get perfect audio from DMR to DSTAR without them but no audio from DSTAR to DMR.

https://docs.google.com/document/d/1n17cx_9elLJoMmcQWM0_XOm2dicKdIC6ar_0S16904A

Thanks!!


Re: A newbei Question about NXDN <--> DMR

Jake Litwin
 

I have built a NXDN to DMR bridge using the NXDN Reflector, NXDN Gateway and the MMDVM Bridge. I'm getting a weird error in the logs. Folks on DMR can hear the NXDN Reflector but nothing comes back to NXDN from DMR. I figured this error might have something to do with it and not sure what this means. 

M: 2019-10-19 16:40:10.147 DMR Slot 2, received network end of voice transmission, 40.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-10-19 16:40:10.148 NXDN, TX state = OFF
M: 2019-10-19 16:40:14.745 DMR Slot 2, received network voice header from N7VDR to TG 420
M: 2019-10-19 16:40:14.745 NXDN, TX state = ON
I: 2019-10-19 16:40:14.745 NXDN, dmrToNxdn by call: N7VDR
I: 2019-10-19 16:40:14.745 NXDN, Begin TX: src=3108345 rpt=0 dst=420 slot=2 cc=0 metadata=N7VDR
I: 2019-10-19 16:40:14.745 NXDN, (3108345, 420) -> (8344, 420)
W: 2019-10-19 16:40:40.795 DMR, Login to the master has failed, retrying login ...
E: 2019-10-19 16:40:41.823 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
M: 2019-10-19 16:40:42.221 DMR Slot 2, network watchdog has expired, 53.5 seconds, 2% packet loss, BER: 0.0%
E: 2019-10-19 16:40:42.917 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
E: 2019-10-19 16:40:43.920 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
E: 2019-10-19 16:40:45.019 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
E: 2019-10-19 16:40:46.119 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
E: 2019-10-19 16:40:47.222 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
E: 2019-10-19 16:40:48.315 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
E: 2019-10-19 16:40:49.323 DMR Network buffer overflow, clearing the buffer. (55 >= 47)
E: 2019-10-19 16:40:50.418 DMR Network buffer overflow, clearing the buffer. (55 >= 47)

4281 - 4300 of 9288