Topics

MMDVM Bridge logged in but not showing in Selfcare


scot forshaw
 

Hi, 
I have setup ALS MB AB as per https://4x5mg.net/2018/07/16/allstar-to-dmr-bridge/ and tried to trouble shoot using several variations...

Everything looks to be working as MMDVM_Bridge reports it has logged in correctly etc etc 

M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully

Similarly AB output is exactly the same as the examples in https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit 

Allstar is linking, Echolink is linking, the EL and ALS nodes work and I can connect tot hem via EL and even repeaters etc etc ...

It just does not show up in BM selfceare no matter what I have tried. 

Opened all the PORTS, shutdown my Pi-Star not he same LAN.

I feel that everything is there, can anyone help me understand why it is not appearing in BM so I can assign the TG ?

Many thanks in advance

Scot 2E0WWV

















M: 2020-05-17 18:50:13.131 DMR, Opening DMR Network
I: 2020-05-17 18:50:13.131 RSSI
I: 2020-05-17 18:50:13.131     Mapping File: RSSI.dat
W: 2020-05-17 18:50:13.132 Cannot open the RSSI data file - RSSI.dat
I: 2020-05-17 18:50:13.132 DMR Id Lookups
I: 2020-05-17 18:50:13.132     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-05-17 18:50:13.132     Reload: 24 hours
I: 2020-05-17 18:50:14.032 Loaded 164586 Ids to the DMR callsign lookup table
I: 2020-05-17 18:50:14.032 Started the DMR Id lookup reload thread
I: 2020-05-17 18:50:14.032 DMR RF Parameters
I: 2020-05-17 18:50:14.032     Id: 234785705
I: 2020-05-17 18:50:14.032     Color Code: 1
I: 2020-05-17 18:50:14.032     Self Only: no
I: 2020-05-17 18:50:14.032     Embedded LC Only: yes
I: 2020-05-17 18:50:14.032     Dump Talker Alias Data: no
I: 2020-05-17 18:50:14.033     Prefixes: 0
I: 2020-05-17 18:50:14.033     Call Hang: 3s
I: 2020-05-17 18:50:14.033     TX Hang: 3s
I: 2020-05-17 18:50:14.033     Mode Hang: 10s
M: 2020-05-17 18:50:14.033 DMR, Opening INI file: DVSwitch.ini
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] TXPort -> 31100
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] RXPort -> 31103
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Slot -> 2
M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully


Steve N4IRS
 

Scot,
If I had to guess, and I do since you are not posting enough of your log to see the callsign and DMR ID used to login to BM. I would guess a typo in either one of the fields.

Steve N4IRS

On 5/17/20 2:57 PM, scot forshaw wrote:
Hi, 
I have setup ALS MB AB as per https://4x5mg.net/2018/07/16/allstar-to-dmr-bridge/ and tried to trouble shoot using several variations...

Everything looks to be working as MMDVM_Bridge reports it has logged in correctly etc etc 

M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully

Similarly AB output is exactly the same as the examples in https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit 

Allstar is linking, Echolink is linking, the EL and ALS nodes work and I can connect tot hem via EL and even repeaters etc etc ...

It just does not show up in BM selfceare no matter what I have tried. 

Opened all the PORTS, shutdown my Pi-Star not he same LAN.

I feel that everything is there, can anyone help me understand why it is not appearing in BM so I can assign the TG ?

Many thanks in advance

Scot 2E0WWV

















M: 2020-05-17 18:50:13.131 DMR, Opening DMR Network
I: 2020-05-17 18:50:13.131 RSSI
I: 2020-05-17 18:50:13.131     Mapping File: RSSI.dat
W: 2020-05-17 18:50:13.132 Cannot open the RSSI data file - RSSI.dat
I: 2020-05-17 18:50:13.132 DMR Id Lookups
I: 2020-05-17 18:50:13.132     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-05-17 18:50:13.132     Reload: 24 hours
I: 2020-05-17 18:50:14.032 Loaded 164586 Ids to the DMR callsign lookup table
I: 2020-05-17 18:50:14.032 Started the DMR Id lookup reload thread
I: 2020-05-17 18:50:14.032 DMR RF Parameters
I: 2020-05-17 18:50:14.032     Id: 234785705
I: 2020-05-17 18:50:14.032     Color Code: 1
I: 2020-05-17 18:50:14.032     Self Only: no
I: 2020-05-17 18:50:14.032     Embedded LC Only: yes
I: 2020-05-17 18:50:14.032     Dump Talker Alias Data: no
I: 2020-05-17 18:50:14.033     Prefixes: 0
I: 2020-05-17 18:50:14.033     Call Hang: 3s
I: 2020-05-17 18:50:14.033     TX Hang: 3s
I: 2020-05-17 18:50:14.033     Mode Hang: 10s
M: 2020-05-17 18:50:14.033 DMR, Opening INI file: DVSwitch.ini
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] TXPort -> 31100
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] RXPort -> 31103
M: 2020-05-17 18:50:14.033 DMR, Setting [DMR] Slot -> 2
M: 2020-05-17 18:50:14.033 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2020-05-17 18:50:14.033 MMDVM_Bridge-20191105_V1.4.1 is running
D: 2020-05-17 18:50:24.059 DMR, Sending authorisation
D: 2020-05-17 18:50:24.085 DMR, Sending configuration
M: 2020-05-17 18:50:24.111 DMR, Logged into the master successfully