Date   

Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

Just in case, please include copies of the MB.ini and the DVSwitch.ini for each directory. Based on the fact that a normal user does not have the issue, makes me think it's a bug somewhere. I can tell you taht it will be at least a few days before it can even be looked at.
Steve

On 10/30/2020 10:52 AM, swinger72@... wrote:
Each instance running in separate folder. On mb2 i see my id 3022260 and in log mb1 crash i see 302226 ? Midsing number 


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Each instance running in separate folder. On mb2 i see my id 3022260 and in log mb1 crash i see 302226 ? Midsing number 


Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

I don't think they are trying to share .ini files since each instance of MB will need DVSwitch.ini to define a unique set of ports. Also, he reports that a normal user (not using DMR2YSF) has no problem.

On 10/30/2020 10:07 AM, k7wby@... wrote:
Looks like 2 MB's trying to run at the same time in the same namespace.


Re: #mmdvm_bridge #mmdvm_bridge

k7wby@...
 

Looks like 2 MB's trying to run at the same time in the same namespace.


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

dmr2ysf connected to fusioncanadafr ysf reflector

Her Mbridge1 CRASH
I: 2020-10-29 21:49:05.051 MMDVM_Bridge:
I: 2020-10-29 21:49:05.051 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-10-29 21:49:05.051 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-10-29 21:49:05.051 =
I: 2020-10-29 22:07:11.755 This software is for use on amateur radio networks only,
I: 2020-10-29 22:07:11.755 it is to be used for educational purposes only. Its use on
I: 2020-10-29 22:07:11.755 commercial networks is strictly prohibited.
I: 2020-10-29 22:07:11.755 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-10-29 22:07:11.755 MMDVM_Bridge-20200727_V1.5.9 is starting
M: 2020-10-29 22:07:11.755 Built 16:22:31 Oct 23 2020 (GitID #0ea07ac)
I: 2020-10-29 22:07:11.755 General Parameters
I: 2020-10-29 22:07:11.755     Callsign: VA2TB
I: 2020-10-29 22:07:11.755     Id: 302252804
I: 2020-10-29 22:07:11.755     Duplex: no
I: 2020-10-29 22:07:11.755     Timeout: 180s
I: 2020-10-29 22:07:11.755     D-Star: disabled
I: 2020-10-29 22:07:11.755     DMR: disabled
I: 2020-10-29 22:07:11.755     YSF: enabled
I: 2020-10-29 22:07:11.755     P25: disabled
I: 2020-10-29 22:07:11.755     NXDN: disabled
I: 2020-10-29 22:07:11.755 Modem Parameters
I: 2020-10-29 22:07:11.755     Port: /dev/null
I: 2020-10-29 22:07:11.755     RX Invert: no
I: 2020-10-29 22:07:11.755     TX Invert: no
I: 2020-10-29 22:07:11.755     PTT Invert: no
I: 2020-10-29 22:07:11.755     TX Delay: 100ms
I: 2020-10-29 22:07:11.755     RX Offset: 0Hz
I: 2020-10-29 22:07:11.755     TX Offset: 0Hz
I: 2020-10-29 22:07:11.755     RX DC Offset: 0
I: 2020-10-29 22:07:11.755     TX DC Offset: 0
I: 2020-10-29 22:07:11.755     RF Level: 100.0%
I: 2020-10-29 22:07:11.755     DMR Delay: 0 (0.0ms)
I: 2020-10-29 22:07:11.755     RX Level: 50.0%
I: 2020-10-29 22:07:11.755     CW Id TX Level: 50.0%
I: 2020-10-29 22:07:11.755     D-Star TX Level: 50.0%
I: 2020-10-29 22:07:11.755     DMR TX Level: 50.0%
I: 2020-10-29 22:07:11.755     YSF TX Level: 50.0%
I: 2020-10-29 22:07:11.755     P25 TX Level: 50.0%
I: 2020-10-29 22:07:11.755     NXDN TX Level: 50.0%
I: 2020-10-29 22:07:11.755     RX Frequency: 0Hz (0Hz)
I: 2020-10-29 22:07:11.756     TX Frequency: 0Hz (0Hz)
M: 2020-10-29 22:07:11.756 Opening the MMDVM
I: 2020-10-29 22:07:11.756 Display Parameters
I: 2020-10-29 22:07:11.756     Type:
I: 2020-10-29 22:07:11.756 System Fusion Network Parameters
I: 2020-10-29 22:07:11.756     Local Address: 0
I: 2020-10-29 22:07:11.756     Local Port: 3200
I: 2020-10-29 22:07:11.756     Gateway Address: 127.0.0.1
I: 2020-10-29 22:07:11.756     Gateway Port: 42000
I: 2020-10-29 22:07:11.756     Mode Hang: 3s
M: 2020-10-29 22:07:11.756 Opening YSF network connection
I: 2020-10-29 22:07:11.756 RSSI
I: 2020-10-29 22:07:11.756     Mapping File: /dev/null
I: 2020-10-29 22:07:11.756 Loaded 0 RSSI data mapping points from /dev/null
I: 2020-10-29 22:07:11.756 DMR Id Lookups
I: 2020-10-29 22:07:11.756     File: /opt/DMRIds.dat
I: 2020-10-29 22:07:11.756     Reload: 24 hours
I: 2020-10-29 22:07:11.810 Loaded 89800 Ids to the DMR callsign lookup table
I: 2020-10-29 22:07:11.810 YSF RF Parameters
I: 2020-10-29 22:07:11.810     Low Deviation: no
I: 2020-10-29 22:07:11.810     Remote Gateway: no
I: 2020-10-29 22:07:11.811     Self Only: no
I: 2020-10-29 22:07:11.811     DSQ: no
I: 2020-10-29 22:07:11.811     Mode Hang: 10s
M: 2020-10-29 22:07:11.811 YSF, Opening INI file: DVSwitch.ini
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] txPort -> 43500
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] rxPort -> 42500
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] txWidePort -> 43500
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] exportTG -> 1234
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] slot -> 2
M: 2020-10-29 22:07:11.811 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-10-29 22:07:11.811 YSF, Transmitting on 127.0.0.1:43500, and listening on port 42500.  Result = 1
M: 2020-10-29 22:07:11.811 MMDVM_Bridge-20200727_V1.5.9 is running
I: 2020-10-29 22:07:11.811 Started the DMR Id lookup reload thread
D: 2020-10-29 22:07:16.813 YSF Network Poll Sent
D: 2020-10-29 22:07:16.813 0000:  59 53 46 50 56 41 32 54 42 20 20 20 20 20          *YSFPVA2TB     *
M: 2020-10-29 22:07:19.945 YSF, TX state = ON
I: 2020-10-29 22:07:19.945 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-10-29 22:07:19.945 YSF, No call or id found, using ini value: VA2TB     ▒▒
D: 2020-10-29 22:07:20.179 YSF Network Data Sent
D: 2020-10-29 22:07:20.179 0000:  59 53 46 44 56 41 32 54 42 20 20 20 20 20 56 41    *YSFDVA2TB     VA*
D: 2020-10-29 22:07:20.179 0010:  32 54 42 20 20 20 20 20 41 4C 4C 00 00 00 00 00    *2TB     ALL.....*
D: 2020-10-29 22:07:20.179 0020:  00 00 00 D4 71 C9 63 4D 21 36 5C 9A 1A 31 21 A0    *....q.cM!6\..1!.*
D: 2020-10-29 22:07:20.179 0030:  D7 DD CF B5 90 9C 5C 4B A6 03 73 D1 4F C5 11 9A    *......\K..s.O...*
D: 2020-10-29 22:07:20.179 0040:  F7 F3 F8 F7 50 1E 53 11 8D 48 DF 23 63 C0 17 60    *....P.S..H.#c..`*
D: 2020-10-29 22:07:20.179 0050:  7F 1C 88 BA A5 E0 47 56 92 26 FF 9B B9 A8 5A BA    *......GV.&....Z.*
D: 2020-10-29 22:07:20.179 0060:  46 92 10 14 BE E5 AA 2C D3 46 B1 19 9C 75 75 A8    *F......,.F...uu.*
D: 2020-10-29 22:07:20.179 0070:  F7 7F B8 11 10 F2 C6 40 DF 08 3E E8 AB C9 91 8F    *.......@..>.....*
D: 2020-10-29 22:07:20.180 0080:  3D EF 0E 84 25 1E 49 94 64 25 86 F6 03 57 0E 22    *=...%.I.d%...W."*
D: 2020-10-29 22:07:20.180 0090:  C1 A4 13 73 F6 0D FB D5 89 01 93                   *...s.......*
D: 2020-10-29 22:07:20.266 YSF Network Data Sent
D: 2020-10-29 22:07:20.266 0000:  59 53 46 44 56 41 32 54 42 20 20 20 20 20 56 41    *YSFDVA2TB     VA*
D: 2020-10-29 22:07:20.266 0010:  32 54 42 20 20 20 20 20 41 4C 4C 00 00 00 00 00    *2TB     ALL.....*
D: 2020-10-29 22:07:20.266 0020:  00 00 02 D4 71 C9 63 4D 11 C6 5C 73 65 F2 B1 A0    *....q.cM..\se...*
D: 2020-10-29 22:07:20.266 0030:  A0 23 8E 45 93 98 C6 07 66 01 ED FA C5 05 11 6F    *.#.E....f......o*
D: 2020-10-29 22:07:20.266 0040:  BF E7 7B FC 86 E1 7B B2 8E 43 36 E4 A2 39 78 49    *..{...{..C6..9xI*
D: 2020-10-29 22:07:20.266 0050:  33 68 32 48 53 58 79 6D 7B B2 8E 43 36 E4 A2 39    *3h2HSXym{..C6..9*
D: 2020-10-29 22:07:20.267 0060:  78 49 33 68 32 A9 F0 EB FD CE 7B B2 8E 43 36 E4    *xI3h2.....{..C6.*
D: 2020-10-29 22:07:20.267 0070:  A2 39 78 49 33 68 32 18 FB 30 1A 57 59 90 AC 61    *.9xI3h2..0.WY..a*
D: 2020-10-29 22:07:20.267 0080:  14 C5 A2 39 78 4D 77 68 36 34 DF 19 46 E0 7B B2    *...9xMwh64..F.{.*
D: 2020-10-29 22:07:20.267 0090:  8E 43 36 E4 A2 39 78 49 33 68 32                   *.C6..9xI3h2*
I: 2020-10-29 22:07:20.267 YSF, Narrow transmit (72 bit)
Segmentation fault (core dumped)




Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

ok i do that tonight and i leave you both side log from mb1 and 2 .Thank s for your help. :)


Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

OK,
I need you to turn on debugging for MMDVM_Bridge2
[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=127.0.0.1
GatewayPort=4200
Debug=1

Then run MMDVM_Bridge2 in the foreground. Capture ALL of the information from the start of MMDVM_Bridge2 until the crash. Please post the results.

Steve


On 10/29/2020 3:11 PM, swinger72@... wrote:
On Thu, Oct 29, 2020 at 03:06 PM, Steve N4IRS wrote:
So, it's like this:

dmr2ysf  <-> (F1ZIT YSF Reflector) <-> MMDVM_Bridge1 <-> MMDVM_Bridge2 <-> (fusion canada fr ysfreflector) <-> user2

When dmr2ysf transmits, MMDVM_Bridge1 passes the data OK. MMDVM_Bridge2 crashes.

Do I have that correct?

On 10/29/2020 2:59 PM, swinger72@... wrote:
Ok i use mbridge 1 connected to  f1zit ysfreflector network. Mbridge 2 connected to my own  fusion canada fr ysfreflector
So  mbridge 1 and 2 run in my own server localy .mbridge1 rxport 42500tx43500 mbridge 2 rx 43500 tx 42500

 Yep correct.  If i connect dmr2ysf to F1ZIT ysfreflector  the mb2 crash. If i connect dmr2ysf to Fusioncanadafr ysfreflector so mb2 is ok and mb1 crash.


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Yes fusion ysf to ysf dn or wide work perfectly


Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

And a regular YSF user does not crash?

On 10/29/2020 3:14 PM, swinger72@... wrote:
Sorry i use the cell phone i hit the wrong button. Yes your right
When i use dmr2ysf connected to F1ZIT YSFREFLECTOR  MB1 ok and mb2 crash. If i connect dmr2ysf to fusioncanada fr ysfreflector mb 2 ok mb1 crash 


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Sorry i use the cell phone i hit the wrong button. Yes your right
When i use dmr2ysf connected to F1ZIT YSFREFLECTOR  MB1 ok and mb2 crash. If i connect dmr2ysf to fusioncanada fr ysfreflector mb 2 ok mb1 crash 


Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

Can I assume that a YSF user (no DMR2YSF) on either side, the traffic passws fine?

On 10/29/2020 3:11 PM, swinger72@... wrote:
On Thu, Oct 29, 2020 at 03:06 PM, Steve N4IRS wrote:
So, it's like this:

dmr2ysf  <-> (F1ZIT YSF Reflector) <-> MMDVM_Bridge1 <-> MMDVM_Bridge2 <-> (fusion canada fr ysfreflector) <-> user2

When dmr2ysf transmits, MMDVM_Bridge1 passes the data OK. MMDVM_Bridge2 crashes.

Do I have that correct?

On 10/29/2020 2:59 PM, swinger72@... wrote:
Ok i use mbridge 1 connected to  f1zit ysfreflector network. Mbridge 2 connected to my own  fusion canada fr ysfreflector
So  mbridge 1 and 2 run in my own server localy .mbridge1 rxport 42500tx43500 mbridge 2 rx 43500 tx 42500

 Yep correct.  If i connect dmr2ysf to F1ZIT ysfreflector  the mb2 crash. If i connect dmr2ysf to Fusioncanadafr ysfreflector so mb2 is ok and mb1 crash.


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

On Thu, Oct 29, 2020 at 03:06 PM, Steve N4IRS wrote:
So, it's like this:

dmr2ysf  <-> (F1ZIT YSF Reflector) <-> MMDVM_Bridge1 <-> MMDVM_Bridge2 <-> (fusion canada fr ysfreflector) <-> user2

When dmr2ysf transmits, MMDVM_Bridge1 passes the data OK. MMDVM_Bridge2 crashes.

Do I have that correct?

On 10/29/2020 2:59 PM, swinger72@... wrote:
Ok i use mbridge 1 connected to  f1zit ysfreflector network. Mbridge 2 connected to my own  fusion canada fr ysfreflector
So  mbridge 1 and 2 run in my own server localy .mbridge1 rxport 42500tx43500 mbridge 2 rx 43500 tx 42500

 Yep correct.  If i connect dmr2ysf to F1ZIT ysfreflector  the mb2 crash. If i connect dmr2ysf to Fusioncanadafr ysfreflector so mb2 is ok and mb1 crash.


Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

So, it's like this:

dmr2ysf  <-> (F1ZIT YSF Reflector) <-> MMDVM_Bridge1 <-> MMDVM_Bridge2 <-> (fusion canada fr ysfreflector) <-> user2

When dmr2ysf transmits, MMDVM_Bridge1 passes the data OK. MMDVM_Bridge2 crashes.

Do I have that correct?

On 10/29/2020 2:59 PM, swinger72@... wrote:
Ok i use mbridge 1 connected to  f1zit ysfreflector network. Mbridge 2 connected to my own  fusion canada fr ysfreflector
So  mbridge 1 and 2 run in my own server localy .mbridge1 rxport 42500tx43500 mbridge 2 rx 43500 tx 42500


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 
Edited

Ok i use mbridge 1 connected to  f1zit ysfreflector network. Mbridge 2 connected to my own  fusion canada fr ysfreflector
So  mbridge 1 and 2 run in my own server localy .mbridge1 ysf rxport 42500 ysf tx43500 mbridge 2 ysf rx 43500ysf tx 42500


Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

I'm not sure I'm getting this. You have 2 YSF reflectors?

On 10/29/2020 2:25 PM, swinger72@... wrote:
Thank s for the reply. Ysfreflector1 >.mbridge 1 connected to >ysfref 1. Ysfreflector 2 >mbridge 2 connecte ysfref2. I connect dmr2ysf in >ysfref1 >mb1 receive ok. Mbridge2 rx and crash so dont pass to ysfref2. Try connect dmr2ysf to >ysfref2. Mbridge 2 ok.mbridge2 > Mbrige 1 rx and crash .


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

I link mblink 1 and mbridge 2 with rx tx ysf port to link both ysfreflector 


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

Thank s for the reply. Ysfreflector1 >.mbridge 1 connected to >ysfref 1. Ysfreflector 2 >mbridge 2 connecte ysfref2. I connect dmr2ysf in >ysfref1 >mb1 receive ok. Mbridge2 rx and crash so dont pass to ysfref2. Try connect dmr2ysf to >ysfref2. Mbridge 2 ok.mbridge2 > Mbrige 1 rx and crash .


Re: #mmdvm_bridge #mmdvm_bridge

Steve N4IRS
 

Let me see if I can simplify this.
When you connect dmr2ysf through a reflector to your MB2, then your MB2 crashes with this error:

I: 2020-10-29 01:39:42.281 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-10-29 01:39:42.281 YSF, No call or id found, using ini value: VA2TB     GÖè
I: 2020-10-29 01:39:42.586 YSF, Narrow transmit (72 bit)

Have I got this right?

On 10/28/20 9:49 PM, Sylvain ve2tbu wrote:
im running 2 mmdvmbridge. 1 link my own ysfreflector. second one link another ysf reflector. the link between ysf to ysf vw or narrow work perfectly, if i connect to my own ysf reflector from dmr2ysf hotspot the mb1 show everything ok. the second one mb2 missing last dmr id digit and close and restart.if i connect my dmr2ysf to ysfreflector 2 the mb2 work ok but the same issue in mb1.ysfreflector1.lost last dmr id digit and close and restart. using mbribdge in amd64. updated the last binary check all port all config but i cannot find anything wrong.When they crash i reveive a weird message from the last line came from dmr2ysf .
I: 2020-10-29 01:39:42.281 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-10-29 01:39:42.281 YSF, No call or id found, using ini value: VA2TB     GÖè
I: 2020-10-29 01:39:42.586 YSF, Narrow transmit (72 bit)
I: 2020-10-29 01:39:46.111 MMDVM_Bridge:
I: 2020-10-29 01:39:46.111 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-10-29 01:39:46.111 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-10-29 01:39:46.111 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2020-10-29 01:39:46.111 This software is for use on amateur radio networks only,
I: 2020-10-29 01:39:46.111 it is to be used for educational purposes only. Its use on
I: 2020-10-29 01:39:46.111 commercial networks is strictly prohibited.
I: 2020-10-29 01:39:46.111 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-10-29 01:39:46.111 MMDVM_Bridge-20200727_V1.5.9 is starting
M: 2020-10-29 01:39:46.111 Built 16:22:31 Oct 23 2020 (GitID #0ea07ac)
I: 2020-10-29 01:39:46.111 General Parameters
I: 2020-10-29 01:39:46.111     Callsign: VA2TB
I: 2020-10-29 01:39:46.111     Id: 302252802
I: 2020-10-29 01:39:46.111     Duplex: no
I: 2020-10-29 01:39:46.111     Timeout: 180s
I: 2020-10-29 01:39:46.111     D-Star: disabled
I: 2020-10-29 01:39:46.111     DMR: disabled
I: 2020-10-29 01:39:46.111     YSF: enabled
I: 2020-10-29 01:39:46.111     P25: disabled
I: 2020-10-29 01:39:46.111     NXDN: disabled
I: 2020-10-29 01:39:46.111 Modem Parameters
I: 2020-10-29 01:39:46.112     Port: /dev/null
I: 2020-10-29 01:39:46.112     RX Invert: no
I: 2020-10-29 01:39:46.112     TX Invert: no
I: 2020-10-29 01:39:46.112     PTT Invert: no
I: 2020-10-29 01:39:46.112     TX Delay: 100ms
I: 2020-10-29 01:39:46.112     RX Offset: 0Hz
I: 2020-10-29 01:39:46.112     TX Offset: 0Hz
I: 2020-10-29 01:39:46.112     RX DC Offset: 0
I: 2020-10-29 01:39:46.112     TX DC Offset: 0
I: 2020-10-29 01:39:46.112     RF Level: 100.0%
I: 2020-10-29 01:39:46.112     DMR Delay: 0 (0.0ms)
I: 2020-10-29 01:39:46.112     RX Level: 50.0%
I: 2020-10-29 01:39:46.112     CW Id TX Level: 50.0%
I: 2020-10-29 01:39:46.112     D-Star TX Level: 50.0%
I: 2020-10-29 01:39:46.112     DMR TX Level: 50.0%
I: 2020-10-29 01:39:46.112     YSF TX Level: 50.0%
I: 2020-10-29 01:39:46.112     P25 TX Level: 50.0%
I: 2020-10-29 01:39:46.112     NXDN TX Level: 50.0%
I: 2020-10-29 01:39:46.112     RX Frequency: 0Hz (0Hz)
I: 2020-10-29 01:39:46.112     TX Frequency: 0Hz (0Hz)
M: 2020-10-29 01:39:46.112 Opening the MMDVM
I: 2020-10-29 01:39:46.112 Display Parameters
I: 2020-10-29 01:39:46.112     Type:
I: 2020-10-29 01:39:46.112 System Fusion Network Parameters
I: 2020-10-29 01:39:46.112     Local Address: 0
I: 2020-10-29 01:39:46.112     Local Port: 42200
I: 2020-10-29 01:39:46.112     Gateway Address: 151.80.143.185
I: 2020-10-29 01:39:46.112     Gateway Port: 42002
I: 2020-10-29 01:39:46.112     Mode Hang: 3s
M: 2020-10-29 01:39:46.112 Opening YSF network connection
I: 2020-10-29 01:39:46.114 RSSI
I: 2020-10-29 01:39:46.114     Mapping File: /dev/null
I: 2020-10-29 01:39:46.114 Loaded 0 RSSI data mapping points from /dev/null
I: 2020-10-29 01:39:46.114 DMR Id Lookups
I: 2020-10-29 01:39:46.114     File: /opt/DMRIds.dat
I: 2020-10-29 01:39:46.114     Reload: 24 hours
I: 2020-10-29 01:39:46.204 Loaded 89800 Ids to the DMR callsign lookup table
I: 2020-10-29 01:39:46.206 YSF RF Parameters
I: 2020-10-29 01:39:46.206     Low Deviation: no
I: 2020-10-29 01:39:46.206     Remote Gateway: no
I: 2020-10-29 01:39:46.206     Self Only: no
I: 2020-10-29 01:39:46.206     DSQ: no
I: 2020-10-29 01:39:46.206     Mode Hang: 10s
M: 2020-10-29 01:39:46.206 YSF, Opening INI file: DVSwitch.ini
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] txPort -> 42500
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] rxPort -> 43500
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] txWidePort -> 42500
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] exportTG -> 1234
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] slot -> 2
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-10-29 01:39:46.207 YSF, Transmitting on 127.0.0.1:42500, and listening on port 43500.  Result = 1
M: 2020-10-29 01:39:46.207 MMDVM_Bridge-20200727_V1.5.9 is running
I: 2020-10-29 01:39:46.207 Started the DMR Id lookup reload thread


#mmdvm_bridge #mmdvm_bridge

 

im running 2 mmdvmbridge. 1 link my own ysfreflector. second one link another ysf reflector. the link between ysf to ysf vw or narrow work perfectly, if i connect to my own ysf reflector from dmr2ysf hotspot the mb1 show everything ok. the second one mb2 missing last dmr id digit and close and restart.if i connect my dmr2ysf to ysfreflector 2 the mb2 work ok but the same issue in mb1.ysfreflector1.lost last dmr id digit and close and restart. using mbribdge in amd64. updated the last binary check all port all config but i cannot find anything wrong.When they crash i reveive a weird message from the last line came from dmr2ysf .
I: 2020-10-29 01:39:42.281 YSF, Begin TX: src=1234567 rpt=0 dst=1234 slot=2 cc=0 metadata=302226
M: 2020-10-29 01:39:42.281 YSF, No call or id found, using ini value: VA2TB     GÖè
I: 2020-10-29 01:39:42.586 YSF, Narrow transmit (72 bit)
I: 2020-10-29 01:39:46.111 MMDVM_Bridge:
I: 2020-10-29 01:39:46.111 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-10-29 01:39:46.111 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-10-29 01:39:46.111 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2020-10-29 01:39:46.111 This software is for use on amateur radio networks only,
I: 2020-10-29 01:39:46.111 it is to be used for educational purposes only. Its use on
I: 2020-10-29 01:39:46.111 commercial networks is strictly prohibited.
I: 2020-10-29 01:39:46.111 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-10-29 01:39:46.111 MMDVM_Bridge-20200727_V1.5.9 is starting
M: 2020-10-29 01:39:46.111 Built 16:22:31 Oct 23 2020 (GitID #0ea07ac)
I: 2020-10-29 01:39:46.111 General Parameters
I: 2020-10-29 01:39:46.111     Callsign: VA2TB
I: 2020-10-29 01:39:46.111     Id: 302252802
I: 2020-10-29 01:39:46.111     Duplex: no
I: 2020-10-29 01:39:46.111     Timeout: 180s
I: 2020-10-29 01:39:46.111     D-Star: disabled
I: 2020-10-29 01:39:46.111     DMR: disabled
I: 2020-10-29 01:39:46.111     YSF: enabled
I: 2020-10-29 01:39:46.111     P25: disabled
I: 2020-10-29 01:39:46.111     NXDN: disabled
I: 2020-10-29 01:39:46.111 Modem Parameters
I: 2020-10-29 01:39:46.112     Port: /dev/null
I: 2020-10-29 01:39:46.112     RX Invert: no
I: 2020-10-29 01:39:46.112     TX Invert: no
I: 2020-10-29 01:39:46.112     PTT Invert: no
I: 2020-10-29 01:39:46.112     TX Delay: 100ms
I: 2020-10-29 01:39:46.112     RX Offset: 0Hz
I: 2020-10-29 01:39:46.112     TX Offset: 0Hz
I: 2020-10-29 01:39:46.112     RX DC Offset: 0
I: 2020-10-29 01:39:46.112     TX DC Offset: 0
I: 2020-10-29 01:39:46.112     RF Level: 100.0%
I: 2020-10-29 01:39:46.112     DMR Delay: 0 (0.0ms)
I: 2020-10-29 01:39:46.112     RX Level: 50.0%
I: 2020-10-29 01:39:46.112     CW Id TX Level: 50.0%
I: 2020-10-29 01:39:46.112     D-Star TX Level: 50.0%
I: 2020-10-29 01:39:46.112     DMR TX Level: 50.0%
I: 2020-10-29 01:39:46.112     YSF TX Level: 50.0%
I: 2020-10-29 01:39:46.112     P25 TX Level: 50.0%
I: 2020-10-29 01:39:46.112     NXDN TX Level: 50.0%
I: 2020-10-29 01:39:46.112     RX Frequency: 0Hz (0Hz)
I: 2020-10-29 01:39:46.112     TX Frequency: 0Hz (0Hz)
M: 2020-10-29 01:39:46.112 Opening the MMDVM
I: 2020-10-29 01:39:46.112 Display Parameters
I: 2020-10-29 01:39:46.112     Type:
I: 2020-10-29 01:39:46.112 System Fusion Network Parameters
I: 2020-10-29 01:39:46.112     Local Address: 0
I: 2020-10-29 01:39:46.112     Local Port: 42200
I: 2020-10-29 01:39:46.112     Gateway Address: 151.80.143.185
I: 2020-10-29 01:39:46.112     Gateway Port: 42002
I: 2020-10-29 01:39:46.112     Mode Hang: 3s
M: 2020-10-29 01:39:46.112 Opening YSF network connection
I: 2020-10-29 01:39:46.114 RSSI
I: 2020-10-29 01:39:46.114     Mapping File: /dev/null
I: 2020-10-29 01:39:46.114 Loaded 0 RSSI data mapping points from /dev/null
I: 2020-10-29 01:39:46.114 DMR Id Lookups
I: 2020-10-29 01:39:46.114     File: /opt/DMRIds.dat
I: 2020-10-29 01:39:46.114     Reload: 24 hours
I: 2020-10-29 01:39:46.204 Loaded 89800 Ids to the DMR callsign lookup table
I: 2020-10-29 01:39:46.206 YSF RF Parameters
I: 2020-10-29 01:39:46.206     Low Deviation: no
I: 2020-10-29 01:39:46.206     Remote Gateway: no
I: 2020-10-29 01:39:46.206     Self Only: no
I: 2020-10-29 01:39:46.206     DSQ: no
I: 2020-10-29 01:39:46.206     Mode Hang: 10s
M: 2020-10-29 01:39:46.206 YSF, Opening INI file: DVSwitch.ini
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] txPort -> 42500
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] rxPort -> 43500
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] txWidePort -> 42500
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] exportTG -> 1234
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] slot -> 2
M: 2020-10-29 01:39:46.206 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-10-29 01:39:46.207 YSF, Transmitting on 127.0.0.1:42500, and listening on port 43500.  Result = 1
M: 2020-10-29 01:39:46.207 MMDVM_Bridge-20200727_V1.5.9 is running
I: 2020-10-29 01:39:46.207 Started the DMR Id lookup reload thread


Re: DVSwitch Server Raspberry Pi Image

Steve N4IRS
 

Jay,
Keeping the .ini files up to date can me a problem. We have two issues we deal with when defining the .ini files. First is progress. Over time, Mike and I will have a discussion about the tags in a section. for example In Analog_Bridge.ini The [USRP] section there was a tag:
"aslAudio" This made sense at the time because the first implementation of Analog_Bridge was to connect to AllStar. Over time, we expanded the capability to include transcode and DVSwitch Mobile. A user building a transcoder would be confused by "aslAudio" After a lot of discussion we decided to rename it to "usrpAudio". A more generic name. As of today Analog_Bridge accepts both. At some point in the future AB will generate a error and force people to use the new tag. I can tell you a lot of thought goes into renaming a tag as we consider the impact on the installed base. The second issue is additions (and subtractions) We are constantly adding features to the DVSwitch components. Sometimes these feature require new tags or even complete sections. If people want to use the new feature, they need the new section.

Should we build a ini file converter? Yes, and it has been discussed as part of a larger script effort. As we find the need to supplement the components, we have added scripting. dvswitch.sh is a perfect example of that. It has become the way to manage and query Analog_Bridge and MMDVM_Bridge as well as the gateways. At some point when we can catch our breath, new scripts will be added to address the issue.

For now, it's up to the user to update the .ini files manually. One last thing I want to point out. Over time we refine programs and configuration files. We also refine our language. We no longer refer to Analog_Bridge MMDVM_Bridge and Quantar_Bridge as partners. They are now components. We hope this better describes what they do. You may also notice that throughout this message I did not use the word stanza. Stanza came from Asterisk and we felt the proper name was section. I will continue to refer to a section in a .ini file by using the brackets [USRP]

So, a very long message to say, you have to update the ini files yourself. I used this opportunity to explain our methods. I hope you are still awake. ;)

73, Steve N4IRS      

On 10/28/2020 8:08 AM, Jay wrote:
Steve, and All

Thanks so much for doing this.  I have been building Pi Images for DVSwitch from the beginning and I cannot count the number of times I have built images from scratch.  I realize that I could get to a certain point and save the image, but i am always worried that I do not the latest of something, especially INI files.  This is a huge step forward in my mind.

That does bring up a question.  The binaries are quite easy to keep up to date.  Is there a method to keep  INI files current without losing existing entries.  I have never found one but over time the "stanzas" have changed and some keywords.

I enjoyed the video and keep them coming.  This is what Ham Radio is all about.

--

jb   N4NQY

2281 - 2300 of 9595