Ok Thanks again for your help. 73 Bill N3JHS

#brandmeister

Bill, You don't need a repeater ID for a bridge. Using your DMR ID for a TG number is just fine. Look in Analog_Bridge.ini for this: [AMBE_AUDIO] minTxTimeMS = 2500 ; Analog -> Digital Minimum time in

#brandmeister

Thanks! That fixed the issue. Not sure how that got deleted. I'm using my DMR ID as the talk group. This seams to work until someone on my allstar or DMR has a bad connection and drop the connection t

#brandmeister

Your network should look like this: [DMR Network] Port=62031 Local=62032 Plus all your other settings.

#brandmeister

Changed the port I: 2021-03-23 17:03:32.441 General Parameters I: 2021-03-23 17:03:32.441 Callsign: N3JHS I: 2021-03-23 17:03:32.441 Id: 314210310 I: 2021-03-23 17:03:32.441 Duplex: no I: 2021-03-23 1

#brandmeister

See my message about the port and local port.

#brandmeister

M: 2021-03-23 16:52:25.359 MMDVM_Bridge-20200309_V1.5.1 is starting M: 2021-03-23 16:52:25.359 Built 19:52:05 May 16 2020 (GitID #fcd30b9) I: 2021-03-23 16:52:25.359 General Parameters I: 2021-03-23 1

#brandmeister

Well, The log file says it's running. Did you change anything with the program?

#brandmeister

-bash: ./MMDVM_Bridge: cannot execute binary file: Exec format error Im on Pi if that makes any differance.

#brandmeister

Bill, You sent this for your config: [DMR Network] Enable=1 Address=3103.repeater.net Jitter=360 Local=62031 <--------------------------- Should be 62032 Password=mypassword # for DMR+ see https://git

#brandmeister

Based on the log, I think MB has a problem with the config. Not sure what. I would: systemctl stop mmdvm_bridge cd /opt/MMDVM_Bridge ./MMDVM_Bridge MMDVM_Bridge.ini show the result, to the end. Steve

#brandmeister

On Tue, Mar 23, 2021 at 09:29 AM, Steve N4IRS wrote: I would like to see the log where MB is trying to connect to BM.

#brandmeister

OK, Your settings look good. I would like to see the log where MB is trying to connect to BM.

#brandmeister

log file: I: 2021-03-23 15:56:02.904 Callsign: N3JHS I: 2021-03-23 15:56:02.904 Id: 3142103 I: 2021-03-23 15:56:02.904 Duplex: no I: 2021-03-23 15:56:02.904 Timeout: 180s I: 2021-03-23 15:56:02.905 D-

#brandmeister

Set duplex = 0 frequencies to simplex make sure callsign and dmrID point to correct user. What does the log show?

#brandmeister

I am no longer able to connect to brandmister, I checked with brandmister and I am not blocked. I did enable my password and changed the MMDVM_bridge.ini file. I did fix the frequency in the file also

#brandmeister

As previously noted, BM-DMR Selfcare password is needed for the BM servers. At the initial login and configuration, this is asked for and works. I notice for the BM Macro and in DMR the BM TG a standa

#brandmeister

I wonder if they have finally cracked down on all the non-RF modes of getting on? I got a similar issue, but I’ve found it to only happen on group 3100. What happens is that you might get the first tr

#brandmeister #mmdvm_bridge #analog_bridge

Hmm, I've never seen that problem. All of my hotspots, instances of DVSwitch, etc connect to the same BM master. But each one has a different 2 digit suffix on its login ID.

#brandmeister #mmdvm_bridge #analog_bridge

You can check if your node is connecting to Brandmeister by logging on to the Brandmeister.network home page. Entering your logon/password (BM password not Hotspot password) and clicking on My Hotspot

#brandmeister #mmdvm_bridge #analog_bridge