Date   

Re: more: not connecting to BM any more

Steve N4IRS
 

One last time.
I told you to set duplex to 0 because that is the recommended method. When you asked about setting split frequencies I told you that you COULD use duplex. We strongly suggest people set the config for DMO. That is simplex so the frequencies need to match or BM will not accept the connection. As I said, if you set to duplex you have to set the frequencies to split or again, BM will not allow you to connect. As I said, if you choose to use duplex, remember we recommend people use DMO, BM treats the connection as a repeater. Repeaters have different rules from a DMO connection. A DMO connection
creates a static TG type. This TG stays until you disconnect it. For a repeater connection, the TG is timed. After a period of inactivity, the TG is disconnected. If you want to over ride this, go into selfcare and set the TG static.

Yes, the ID number you use to connect to BM can be 7 or 9 digit, if 9 digit, you can have 100 hotspot connections, each can be configured differently. The ID used to login to BM is NOT the ID that is displayed on the dashboard becaue it is not the station transmitting, that is defined in the AB.ini since an analog signal has no DMR ID. If you have a hotspot logged into to BM with an ID of 123456789 and your DMR radio is programmed with your DMR ID of 1234567, then 1234567 will be displayed on the lastheard. Corey can chime in and correct me here if I have missed something.

 I have not explained all the differences between DMO and repeater connection. In the next few weeks, we will provide a better method of connecting the BM. That is called Simple Terminal Feature Update. This protocol is what BM want us to use to connect to BM. It is a simpler connection with some features not available in DMO or repeater. It is in beta test now.

Some times the nuances of connectivity are not readily apparent. We have been connecting AllStar to DMR networks before there was a BrandMeister Network. I suggest you ask how something works, don't tell us how things work because sometimes you can't see the big picture without being around the systems for a while.

Steve N4IRS
     

On 3/15/21 7:21 PM, Ken KE2N via groups.io wrote:
OK - a while back you told me I needed to set duplex = 0 but now you are saying I can set it to either 1 or 0.  If it is set to zero, then the frequencies need to be the same.  But this is not my experience.  If I set it to 1, with different frequencies, after 5 minutes or so I can no longer bring up the connection from my DMR HT/repeater, unless I first key up the analog side. There is no error message in the log when it dies. It's like BM just stops talking to MMDVM_Bridge unless it has recently heard something going the other way. This problem does not happen with duplex=0.

As you point out, all the talk about frequencies is, of course, irrelevant to MMDVM_Bridge because its not an actual modem connected to a radio. 

The answer to my question about the ID number is that it can be either the 7 digit number or a 9 digit number.  The extra digits let me see (in self-care) which hot spot is active. But that 9 digit number does not show up in Last Heard - only 7 digits are seen. And it does not show up in the DVSwitch dashboard. Is there some other place it would show up?

DMO is a new acronym for me. Direct Mode Operation - it seems was originally intended to distinguish from Repeater Mode Operation. For DMO the radio would operate simplex with only 1 time slot - or maybe no time slots at all.  But I guess DMO has taken on additional meaning having to do with hot spots and network protocol.

Sorry for being a bit thick about this.  I am trying to increase my level of understanding in fits and starts.


Ken


Re: more: not connecting to BM any more

Ken KE2N
 

OK - a while back you told me I needed to set duplex = 0 but now you are saying I can set it to either 1 or 0.  If it is set to zero, then the frequencies need to be the same.  But this is not my experience.  If I set it to 1, with different frequencies, after 5 minutes or so I can no longer bring up the connection from my DMR HT/repeater, unless I first key up the analog side. There is no error message in the log when it dies. It's like BM just stops talking to MMDVM_Bridge unless it has recently heard something going the other way. This problem does not happen with duplex=0.

As you point out, all the talk about frequencies is, of course, irrelevant to MMDVM_Bridge because its not an actual modem connected to a radio. 

The answer to my question about the ID number is that it can be either the 7 digit number or a 9 digit number.  The extra digits let me see (in self-care) which hot spot is active. But that 9 digit number does not show up in Last Heard - only 7 digits are seen. And it does not show up in the DVSwitch dashboard. Is there some other place it would show up?

DMO is a new acronym for me. Direct Mode Operation - it seems was originally intended to distinguish from Repeater Mode Operation. For DMO the radio would operate simplex with only 1 time slot - or maybe no time slots at all.  But I guess DMO has taken on additional meaning having to do with hot spots and network protocol.

Sorry for being a bit thick about this.  I am trying to increase my level of understanding in fits and starts.


Ken


Re: more: not connecting to BM any more

Steve N4IRS
 

Because you are using the MMDVM protocol to connect to BrandMeister and it requires the TX and RX frequency to match for a DMO connection. It has NOTHING to do with your Analog_Repeater. If you like you can set the frequencies to match your Analog_repeater and set duplex to 1. (non DMO)

On 3/15/21 4:17 PM, Ken KE2N via groups.io wrote:
Ok ... but why do I have to make the TX and RX frequencies "match"  (set equal to each other) when, in fact, the RF end of my system uses different frequencies for the transmitter and receiver?



Ken


Re: more: not connecting to BM any more

Ken KE2N
 

Ok ... but why do I have to make the TX and RX frequencies "match"  (set equal to each other) when, in fact, the RF end of my system uses different frequencies for the transmitter and receiver?



Ken


Re: more: not connecting to BM any more

Steve N4IRS
 

The update does not force a change to the .ini you can say no.
There is no fix needed. You can look to BM as a repeater or a simplex hotspot. There are pluses and minuses with each type. You just need to set the options. Most users are DMO.
The ID in the [General] section is how you identify to the Master. I suggest you add a SSID for more finite control from the BM admin page.
The repeater ID will go away at some point. It's a leftover.
DMR Gateway is designed to allow the MMDVM hotspot user to use modified TG numbers to switch networks on the fly. MMDVM_Bridge provides switching networks without a gateway. 

On 3/15/2021 12:09 PM, Ken KE2N via groups.io wrote:
OK - so I probably made a typo in the frequency. Complicated by the unwanted ini changes from the update.

If I understand then, DVSwitch looks like a simplex hot spot from the BM side.  
So you have to tell BM you are a simplex node, even if you are a repeater  (at least until some fix is implemented).

Can you clarify if the ID in the [General] stanza should be CCS7 or the 9-digit CCS7+2  or does it matter?

The DVSwitch dashboard shows both numbers. 7-digits for GW ID and 9-digits for RPT ID.  (That is coming from AB I guess).

Am I to understand that MMDVM_Bridge, in addition to its protocol translation function, is also a DMR gateway? (or perhaps DMR does not need a gateway)?  

Thanks
Ken


PS I fixed the DSTAR error message by killing ircgatewayd and setting DSTAR enable=0 in MMDVM
I suspect the error was due to a conflict with the actual DSTAR repeater that I run at the same public IP.


Re: more: not connecting to BM any more

Ken KE2N
 

OK - so I probably made a typo in the frequency. Complicated by the unwanted ini changes from the update.

If I understand then, DVSwitch looks like a simplex hot spot from the BM side.  
So you have to tell BM you are a simplex node, even if you are a repeater  (at least until some fix is implemented).

Can you clarify if the ID in the [General] stanza should be CCS7 or the 9-digit CCS7+2  or does it matter?

The DVSwitch dashboard shows both numbers. 7-digits for GW ID and 9-digits for RPT ID.  (That is coming from AB I guess).

Am I to understand that MMDVM_Bridge, in addition to its protocol translation function, is also a DMR gateway? (or perhaps DMR does not need a gateway)?  

Thanks
Ken


PS I fixed the DSTAR error message by killing ircgatewayd and setting DSTAR enable=0 in MMDVM
I suspect the error was due to a conflict with the actual DSTAR repeater that I run at the same public IP.


hytera USB packet structure

Kev
 

Hello everybody,
I've spent the last couple of months reading through the etsi
documents trying to figure out the packet structure of the 'forward to
pc' option on a hytera radio.
Having done some detective work and comparing packets I can decode
radio ID, LLID, and extract SMS data by bit bashing. I would prefer to
actually understand the whole packet structure so I can decode it
properly rather than blindly extracting the useful data.

The packet does at first appear to be a standard etsi packet,
containing all the blocks.
The issue I'm having is the documents and all open source software I
can find deal with the air side blocks, not a network packet.

Take for example the first 8 bits in the packet : "00001001", which
could be any of the following :
1) 1001 = Idle Data
2) Privacy Flag=0, Reserved Flag=0 and FLCO=001001 making up the first
line in a Full LC header.
3) 001001=8 bit ISO/IEC 8859-7
4) 1001 = SAP 9 = Short Data Services over PDP

Without figuring out some basics, like blocktype I can't work out
which interleaving to use (bptc, hamming etc)

Then there is the LLID. All ETSI documents say it should be
24bits+24bits, but I see the CAI in each address making it 28 or 32
bits for each.

I've attached a text file with some example recieved data split into
colums to make comparision easier for myself.

Im not asking for a full packet decode (although I wouldn't say no!),
just a push in the right direction on how to figure out the packet
type (It must be the first thing transmitted right?)
I realise this isn't a DVSwitch question, but I cant think of a more
knowledgeable group of people on the DMR protocol. If you think there
would be a better place to ask this, please let me know!

Thank you for taking the time to read this, I really hope you can help.

Regards
Kev


Re: Registration of Dv Switch

Steve N4IRS
 

OK,
Thank you.

On 3/15/2021 10:33 AM, g6luu alan wrote:
Using DvSwitch.img on my own Rpi2 , on own Network


Re: Registration of Dv Switch

g6luu alan
 

Using DvSwitch.img on my own Rpi2 , on own Network


Re: Registration of Dv Switch

Steve N4IRS
 

Are you using your own server or someone else?

On 3/15/2021 10:02 AM, g6luu alan wrote:
DVSwitch Server (USRP) 

Been 'resetting' and working now, not sure what 'changed' but all good now
Fantastic Network ! Like it a lot . 73 alan


Re: Registration of Dv Switch

g6luu alan
 
Edited

DVSwitch Server (USRP) 

Been 'resetting' and working now, not sure what 'changed' but all good now
Got a lot of RX Data coming down from , i guess, the Network ?
Fantastic Network ! Like it a lot . 73 alan


Re: Emulator timed out on encode!

G4WXN@...
 

I have decided I am flogging a dead horse here, so have decided to start again, and use the Rpi image 2020-10-31-DVSwitch-Server-lite.img
I am assuming that is the most up to date version?
--
Derek

G4WXN


P25 to DMR bridge using DVSwitch Server

David Young
 

Trying to understand how to use the new DVSwitch-Server to bridge from P25 to DMR.  Using the old DVSwitch bridging, two instances of Analog_Bridge were required, which I assume is still necessary but DVSwitch-Server seems to only auto-start one instance of Analog_Bridge.  The second I have been starting manually.  I think I am missing something here.  How do I setup DVSwitch-Server to auto start two instances of Analog_Bridge?  I have been using the primary Analog_Bridge with it's .ini file (Analog_Bridge.ini) setup for the P25 side and then I add another instance of Analog_Bridge in the same default folder named Analog_Bridge_DMR with it's associated .ini file (Analog_Bridge_DMR.ini).  The DMR side Analog_Bridge I have been manually starting which is where I think I am missing the correct procedure.  Doing the P25 to DMR bridge this way works, but I do run into problems usually after it runs for some time (sometimes afew hours and some times a day or so), then either it stops running or the audio gets distorted with very long latency.  When I look at the server stats I see a very large amount of disk IO operations and the CPU usage goes upward over 50% which seems excessive as I am only running two bridges on the server, P25 and NXDN, both to DMR.  I also noted that the Analog_Bridge_DMR.log generating messages which say MMDVM success constantly which is causing the log file to grow quite large.  I have changed the logging from the default of 2 (message) to 0 (None) which stops these messages.  The primary Analog_Bridge.log file does not do this.

I am sure I must not be following the correct setup to bridge P25 to DMR with DVSwitch-Server, help?

--
Dave WB6DTB


Re: Connection Issue to BM

N4UPC - Scott
 

Fixed.  I must have misunderstood about the DUPLEX=1.

Thanks!

73
Scott,
N4UPC



On 3/14/2021 6:50 PM, Steve N4IRS wrote:
Set Duplex = 0

On 3/14/21 7:41 PM, N4UPC - Scott via groups.io wrote:

---

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

[Info]
RXFrequency=222340000
TXFrequency=222340000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=USA
Description=Bridge
URL=https://www.dodropin.net

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=/dev/null
Trace=0
Debug=0

[D-Star]
Enable=1
Module=B

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=0

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=xxxxxxx
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=4200
Debug=0

[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0

[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


---



73
Scott,
N4UPC



On 3/14/2021 6:37 PM, Steve N4IRS wrote:
Show MMDVM_Bridge.ini

On 3/14/21 7:36 PM, N4UPC - Scott via groups.io wrote:
Also RX/TX freq is the same.

73,
Scott
N4UPC



On Sun, Mar 14, 2021 at 18:33, N4UPC - Scott via groups.io <n4upc@...> wrote:
All,

My DVSwitch system as suddenly stopped connecting to BM.  I've made the changes to the MMDVM_Bridge file as previously noted:

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

Still no joy.  All I get in the MMDVM_Bridge.log is:

E: 2021-03-14 23:31:05.954 DMR, Master is closing down
M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network
M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network
E: 2021-03-14 23:31:16.167 DMR, Master is closing down
M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network
M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network
E: 2021-03-14 23:31:26.373 DMR, Master is closing down
M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network
M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network

I also did an upgrade and rebooted the system afterward.  Stumped!

--
73
Scott,
N4UPC










Re: Connection Issue to BM

Steve N4IRS
 

Set Duplex = 0

On 3/14/21 7:41 PM, N4UPC - Scott via groups.io wrote:

---

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

[Info]
RXFrequency=222340000
TXFrequency=222340000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=USA
Description=Bridge
URL=https://www.dodropin.net

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=/dev/null
Trace=0
Debug=0

[D-Star]
Enable=1
Module=B

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=0

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=xxxxxxx
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=4200
Debug=0

[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0

[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


---



73
Scott,
N4UPC



On 3/14/2021 6:37 PM, Steve N4IRS wrote:
Show MMDVM_Bridge.ini

On 3/14/21 7:36 PM, N4UPC - Scott via groups.io wrote:
Also RX/TX freq is the same.

73,
Scott
N4UPC



On Sun, Mar 14, 2021 at 18:33, N4UPC - Scott via groups.io <n4upc@...> wrote:
All,

My DVSwitch system as suddenly stopped connecting to BM.  I've made the changes to the MMDVM_Bridge file as previously noted:

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

Still no joy.  All I get in the MMDVM_Bridge.log is:

E: 2021-03-14 23:31:05.954 DMR, Master is closing down
M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network
M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network
E: 2021-03-14 23:31:16.167 DMR, Master is closing down
M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network
M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network
E: 2021-03-14 23:31:26.373 DMR, Master is closing down
M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network
M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network

I also did an upgrade and rebooted the system afterward.  Stumped!

--
73
Scott,
N4UPC









Re: Connection Issue to BM

N4UPC - Scott
 


---

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

[Info]
RXFrequency=222340000
TXFrequency=222340000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=USA
Description=Bridge
URL=https://www.dodropin.net

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/var/log/mmdvm
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=/dev/null
Trace=0
Debug=0

[D-Star]
Enable=1
Module=B

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0

[System Fusion]
Enable=0

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=xxxxxxx
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=4200
Debug=0

[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0

[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


---



73
Scott,
N4UPC



On 3/14/2021 6:37 PM, Steve N4IRS wrote:
Show MMDVM_Bridge.ini

On 3/14/21 7:36 PM, N4UPC - Scott via groups.io wrote:
Also RX/TX freq is the same.

73,
Scott
N4UPC



On Sun, Mar 14, 2021 at 18:33, N4UPC - Scott via groups.io <n4upc@...> wrote:
All,

My DVSwitch system as suddenly stopped connecting to BM.  I've made the changes to the MMDVM_Bridge file as previously noted:

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

Still no joy.  All I get in the MMDVM_Bridge.log is:

E: 2021-03-14 23:31:05.954 DMR, Master is closing down
M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network
M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network
E: 2021-03-14 23:31:16.167 DMR, Master is closing down
M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network
M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network
E: 2021-03-14 23:31:26.373 DMR, Master is closing down
M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network
M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network

I also did an upgrade and rebooted the system afterward.  Stumped!

--
73
Scott,
N4UPC








Re: Connection Issue to BM

Steve N4IRS
 

Show MMDVM_Bridge.ini

On 3/14/21 7:36 PM, N4UPC - Scott via groups.io wrote:
Also RX/TX freq is the same.

73,
Scott
N4UPC



On Sun, Mar 14, 2021 at 18:33, N4UPC - Scott via groups.io <n4upc@...> wrote:
All,

My DVSwitch system as suddenly stopped connecting to BM.  I've made the changes to the MMDVM_Bridge file as previously noted:

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

Still no joy.  All I get in the MMDVM_Bridge.log is:

E: 2021-03-14 23:31:05.954 DMR, Master is closing down
M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network
M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network
E: 2021-03-14 23:31:16.167 DMR, Master is closing down
M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network
M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network
E: 2021-03-14 23:31:26.373 DMR, Master is closing down
M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network
M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network

I also did an upgrade and rebooted the system afterward.  Stumped!

--
73
Scott,
N4UPC







Re: Connection Issue to BM

N4UPC - Scott
 

Also RX/TX freq is the same.

73,
Scott
N4UPC



On Sun, Mar 14, 2021 at 18:33, N4UPC - Scott via groups.io <n4upc@...> wrote:
All,

My DVSwitch system as suddenly stopped connecting to BM.  I've made the changes to the MMDVM_Bridge file as previously noted:

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

Still no joy.  All I get in the MMDVM_Bridge.log is:

E: 2021-03-14 23:31:05.954 DMR, Master is closing down
M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network
M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network
E: 2021-03-14 23:31:16.167 DMR, Master is closing down
M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network
M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network
E: 2021-03-14 23:31:26.373 DMR, Master is closing down
M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network
M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network

I also did an upgrade and rebooted the system afterward.  Stumped!

--
73
Scott,
N4UPC






Re: Connection Issue to BM

Steve N4IRS
 

On 3/14/21 7:33 PM, N4UPC - Scott via groups.io wrote:
All,

My DVSwitch system as suddenly stopped connecting to BM.  I've made the changes to the MMDVM_Bridge file as previously noted:

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

Still no joy.  All I get in the MMDVM_Bridge.log is:

E: 2021-03-14 23:31:05.954 DMR, Master is closing down
M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network
M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network
E: 2021-03-14 23:31:16.167 DMR, Master is closing down
M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network
M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network
E: 2021-03-14 23:31:26.373 DMR, Master is closing down
M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network
M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network

I also did an upgrade and rebooted the system afterward.  Stumped!

--
73
Scott,
N4UPC





Connection Issue to BM

N4UPC - Scott
 

All,

My DVSwitch system as suddenly stopped connecting to BM.  I've made the changes to the MMDVM_Bridge file as previously noted:

[General]
Callsign=N4UPC
#Id=316235620
Id=3162356
Timeout=180
Duplex=1

Still no joy.  All I get in the MMDVM_Bridge.log is:

E: 2021-03-14 23:31:05.954 DMR, Master is closing down
M: 2021-03-14 23:31:05.954 DMR, Closing DMR Network
M: 2021-03-14 23:31:05.954 DMR, Opening DMR Network
E: 2021-03-14 23:31:16.167 DMR, Master is closing down
M: 2021-03-14 23:31:16.167 DMR, Closing DMR Network
M: 2021-03-14 23:31:16.167 DMR, Opening DMR Network
E: 2021-03-14 23:31:26.373 DMR, Master is closing down
M: 2021-03-14 23:31:26.373 DMR, Closing DMR Network
M: 2021-03-14 23:31:26.373 DMR, Opening DMR Network

I also did an upgrade and rebooted the system afterward.  Stumped!

--
73
Scott,
N4UPC



1041 - 1060 of 9882