Date   

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


Re: DVSwitch Server Raspberry Pi Image

Jay
 

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


Re: 2 ysf2ysf mmdvm_bridge issue with dmr2ysf

Steve N4IRS
 

To troubleshoot this, you will need to run MB in the foreground. You will capture the live data when the crash happens.

Steve N4IRS

On 10/27/20 10:19 PM, Sylvain ve2tbu wrote:
hi All. im running 2 mbridge to link 2 different ysf reflector.working with fusion working good dn and vw without issue, i try with my dmr with openspot.. openspot dmr to ysf. it working only in 1 side. the mb1 working in my own refl is ok but accross the mb1 to mb2 the  mb2 crash and restart.I try many thing  tg change for tg 9 dmr id nothing change. i seen in my log the error message and i can see from mb1 dmr id 3022260 mb2 show 302226 so they miss something.
hers the log issue and i try to connect from dmr2ysf from ysfref1 mb2 crash i connect to ysfref2 mb1 crash so its the same issue on both side .

This software is for use on amateur radio networks only,
I: 2020-10-28 01:56:47.010 it is to be used for educational purposes only. Its use on
I: 2020-10-28 01:56:47.010 commercial networks is strictly prohibited.
I: 2020-10-28 01:56:47.010 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-10-28 01:56:47.010 MMDVM_Bridge-20200727_V1.5.9 is starting
M: 2020-10-28 01:56:47.010 Built 16:22:31 Oct 23 2020 (GitID #0ea07ac)
I: 2020-10-28 01:56:47.010 General Parameters
I: 2020-10-28 01:56:47.010     Callsign: VA2TB
I: 2020-10-28 01:56:47.010     Id: 302252
I: 2020-10-28 01:56:47.010     Duplex: no
I: 2020-10-28 01:56:47.010     Timeout: 180s
I: 2020-10-28 01:56:47.010     D-Star: disabled
I: 2020-10-28 01:56:47.010     DMR: disabled
I: 2020-10-28 01:56:47.010     YSF: enabled
I: 2020-10-28 01:56:47.010     P25: disabled
I: 2020-10-28 01:56:47.010     NXDN: disabled
I: 2020-10-28 01:56:47.010 Modem Parameters
I: 2020-10-28 01:56:47.010     Port: /dev/null
I: 2020-10-28 01:56:47.010     RX Invert: no
I: 2020-10-28 01:56:47.010     TX Invert: no
I: 2020-10-28 01:56:47.010     PTT Invert: no
I: 2020-10-28 01:56:47.010     TX Delay: 100ms
I: 2020-10-28 01:56:47.010     RX Offset: 0Hz
I: 2020-10-28 01:56:47.010     TX Offset: 0Hz
I: 2020-10-28 01:56:47.010     RX DC Offset: 0
I: 2020-10-28 01:56:47.010     TX DC Offset: 0
I: 2020-10-28 01:56:47.010     RF Level: 100.0%
I: 2020-10-28 01:56:47.010     DMR Delay: 0 (0.0ms)
I: 2020-10-28 01:56:47.010     RX Level: 50.0%
I: 2020-10-28 01:56:47.010     CW Id TX Level: 50.0%
I: 2020-10-28 01:56:47.010     D-Star TX Level: 50.0%
I: 2020-10-28 01:56:47.010     DMR TX Level: 50.0%
I: 2020-10-28 01:56:47.010     YSF TX Level: 50.0%
I: 2020-10-28 01:56:47.010     P25 TX Level: 50.0%
I: 2020-10-28 01:56:47.010     NXDN TX Level: 50.0%
I: 2020-10-28 01:56:47.010     RX Frequency: 0Hz (0Hz)
I: 2020-10-28 01:56:47.010     TX Frequency: 0Hz (0Hz)
M: 2020-10-28 01:56:47.010 Opening the MMDVM
I: 2020-10-28 01:56:47.010 Display Parameters
I: 2020-10-28 01:56:47.010     Type:
I: 2020-10-28 01:56:47.010 System Fusion Network Parameters
I: 2020-10-28 01:56:47.010     Local Address: 0
I: 2020-10-28 01:56:47.010     Local Port: 42200
I: 2020-10-28 01:56:47.010     Gateway Address: 151.80.143.185
I: 2020-10-28 01:56:47.010     Gateway Port: 42002
I: 2020-10-28 01:56:47.010     Mode Hang: 3s
M: 2020-10-28 01:56:47.010 Opening YSF network connection
I: 2020-10-28 01:56:47.014 RSSI
I: 2020-10-28 01:56:47.014     Mapping File: /dev/null
I: 2020-10-28 01:56:47.014 Loaded 0 RSSI data mapping points from /dev/null
I: 2020-10-28 01:56:47.014 DMR Id Lookups
I: 2020-10-28 01:56:47.014     File: /opt/DMRIds.dat
I: 2020-10-28 01:56:47.014     Reload: 24 hours
I: 2020-10-28 01:56:47.142 Loaded 89800 Ids to the DMR callsign lookup table
I: 2020-10-28 01:56:47.145 YSF RF Parameters
I: 2020-10-28 01:56:47.145     Low Deviation: no
I: 2020-10-28 01:56:47.145     Remote Gateway: no
I: 2020-10-28 01:56:47.145     Self Only: no
I: 2020-10-28 01:56:47.145     DSQ: no
I: 2020-10-28 01:56:47.145     Mode Hang: 10s
M: 2020-10-28 01:56:47.145 YSF, Opening INI file: DVSwitch.ini
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] txPort -> 42500
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] rxPort -> 43500
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] txWidePort -> 42500
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] exportTG -> 9
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] slot -> 2
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-10-28 01:56:47.145 YSF, Transmitting on 127.0.0.1:42500, and listening on port 43500.  Result = 1
M: 2020-10-28 01:56:47.145 MMDVM_Bridge-20200727_V1.5.9 is running
I: 2020-10-28 01:56:47.145 Started the DMR Id lookup reload thread
M: 2020-10-28 01:56:58.969 YSF, TX state = ON
I: 2020-10-28 01:56:58.969 YSF, Begin TX: src=1234567 rpt=0 dst=9 slot=2 cc=0 metadata=302226
M: 2020-10-28 01:56:58.969 YSF, No call or id found, using ini value: VA2TB     HH&
I: 2020-10-28 01:56:59.326 YSF, Narrow transmit (72 bit)
I: 2020-10-28 01:57:02.865 MMDVM_Bridge:
I: 2020-10-28 01:57:02.865 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-10-28 01:57:02.865 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-10-28 01:57:02.865 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


2 ysf2ysf mmdvm_bridge issue with dmr2ysf

 

hi All. im running 2 mbridge to link 2 different ysf reflector.working with fusion working good dn and vw without issue, i try with my dmr with openspot.. openspot dmr to ysf. it working only in 1 side. the mb1 working in my own refl is ok but accross the mb1 to mb2 the  mb2 crash and restart.I try many thing  tg change for tg 9 dmr id nothing change. i seen in my log the error message and i can see from mb1 dmr id 3022260 mb2 show 302226 so they miss something.
hers the log issue and i try to connect from dmr2ysf from ysfref1 mb2 crash i connect to ysfref2 mb1 crash so its the same issue on both side .

This software is for use on amateur radio networks only,
I: 2020-10-28 01:56:47.010 it is to be used for educational purposes only. Its use on
I: 2020-10-28 01:56:47.010 commercial networks is strictly prohibited.
I: 2020-10-28 01:56:47.010 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-10-28 01:56:47.010 MMDVM_Bridge-20200727_V1.5.9 is starting
M: 2020-10-28 01:56:47.010 Built 16:22:31 Oct 23 2020 (GitID #0ea07ac)
I: 2020-10-28 01:56:47.010 General Parameters
I: 2020-10-28 01:56:47.010     Callsign: VA2TB
I: 2020-10-28 01:56:47.010     Id: 302252
I: 2020-10-28 01:56:47.010     Duplex: no
I: 2020-10-28 01:56:47.010     Timeout: 180s
I: 2020-10-28 01:56:47.010     D-Star: disabled
I: 2020-10-28 01:56:47.010     DMR: disabled
I: 2020-10-28 01:56:47.010     YSF: enabled
I: 2020-10-28 01:56:47.010     P25: disabled
I: 2020-10-28 01:56:47.010     NXDN: disabled
I: 2020-10-28 01:56:47.010 Modem Parameters
I: 2020-10-28 01:56:47.010     Port: /dev/null
I: 2020-10-28 01:56:47.010     RX Invert: no
I: 2020-10-28 01:56:47.010     TX Invert: no
I: 2020-10-28 01:56:47.010     PTT Invert: no
I: 2020-10-28 01:56:47.010     TX Delay: 100ms
I: 2020-10-28 01:56:47.010     RX Offset: 0Hz
I: 2020-10-28 01:56:47.010     TX Offset: 0Hz
I: 2020-10-28 01:56:47.010     RX DC Offset: 0
I: 2020-10-28 01:56:47.010     TX DC Offset: 0
I: 2020-10-28 01:56:47.010     RF Level: 100.0%
I: 2020-10-28 01:56:47.010     DMR Delay: 0 (0.0ms)
I: 2020-10-28 01:56:47.010     RX Level: 50.0%
I: 2020-10-28 01:56:47.010     CW Id TX Level: 50.0%
I: 2020-10-28 01:56:47.010     D-Star TX Level: 50.0%
I: 2020-10-28 01:56:47.010     DMR TX Level: 50.0%
I: 2020-10-28 01:56:47.010     YSF TX Level: 50.0%
I: 2020-10-28 01:56:47.010     P25 TX Level: 50.0%
I: 2020-10-28 01:56:47.010     NXDN TX Level: 50.0%
I: 2020-10-28 01:56:47.010     RX Frequency: 0Hz (0Hz)
I: 2020-10-28 01:56:47.010     TX Frequency: 0Hz (0Hz)
M: 2020-10-28 01:56:47.010 Opening the MMDVM
I: 2020-10-28 01:56:47.010 Display Parameters
I: 2020-10-28 01:56:47.010     Type:
I: 2020-10-28 01:56:47.010 System Fusion Network Parameters
I: 2020-10-28 01:56:47.010     Local Address: 0
I: 2020-10-28 01:56:47.010     Local Port: 42200
I: 2020-10-28 01:56:47.010     Gateway Address: 151.80.143.185
I: 2020-10-28 01:56:47.010     Gateway Port: 42002
I: 2020-10-28 01:56:47.010     Mode Hang: 3s
M: 2020-10-28 01:56:47.010 Opening YSF network connection
I: 2020-10-28 01:56:47.014 RSSI
I: 2020-10-28 01:56:47.014     Mapping File: /dev/null
I: 2020-10-28 01:56:47.014 Loaded 0 RSSI data mapping points from /dev/null
I: 2020-10-28 01:56:47.014 DMR Id Lookups
I: 2020-10-28 01:56:47.014     File: /opt/DMRIds.dat
I: 2020-10-28 01:56:47.014     Reload: 24 hours
I: 2020-10-28 01:56:47.142 Loaded 89800 Ids to the DMR callsign lookup table
I: 2020-10-28 01:56:47.145 YSF RF Parameters
I: 2020-10-28 01:56:47.145     Low Deviation: no
I: 2020-10-28 01:56:47.145     Remote Gateway: no
I: 2020-10-28 01:56:47.145     Self Only: no
I: 2020-10-28 01:56:47.145     DSQ: no
I: 2020-10-28 01:56:47.145     Mode Hang: 10s
M: 2020-10-28 01:56:47.145 YSF, Opening INI file: DVSwitch.ini
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] address -> 127.0.0.1
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] txPort -> 42500
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] rxPort -> 43500
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] txWidePort -> 42500
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] fallbackID -> 1234567
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] exportTG -> 9
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] slot -> 2
M: 2020-10-28 01:56:47.145 YSF, Setting [YSF] RemotePort -> 6073
M: 2020-10-28 01:56:47.145 YSF, Transmitting on 127.0.0.1:42500, and listening on port 43500.  Result = 1
M: 2020-10-28 01:56:47.145 MMDVM_Bridge-20200727_V1.5.9 is running
I: 2020-10-28 01:56:47.145 Started the DMR Id lookup reload thread
M: 2020-10-28 01:56:58.969 YSF, TX state = ON
I: 2020-10-28 01:56:58.969 YSF, Begin TX: src=1234567 rpt=0 dst=9 slot=2 cc=0 metadata=302226
M: 2020-10-28 01:56:58.969 YSF, No call or id found, using ini value: VA2TB     HH&
I: 2020-10-28 01:56:59.326 YSF, Narrow transmit (72 bit)
I: 2020-10-28 01:57:02.865 MMDVM_Bridge:
I: 2020-10-28 01:57:02.865 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2020-10-28 01:57:02.865 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-10-28 01:57:02.865 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


Re: YSF > ASL using XLXd reflector

k7wby@...
 

Steve, thanks for the repsonse. My first attempt was without the gateway using only MB, which as you say, works. I wasn't able to do YSF Passthrough but I knew G4KLX's YSFGateway could do it. I've managed to get that up and running now and all is good.  This is all an experiment to see what I might do if my back haul failed. I needed a fail over that I can bring up remotely via ssh. This will get the job done. DVSwitch is quite versatile and I thank you for streamlining it for us.


Re: One TG in Analog Bridge

Steve N4IRS
 

dvswitch.sh tune 9

On 10/27/20 7:23 PM, Aaron Groover wrote:

Is there a way to just set a basic TG for example “9” and be able to talk on what static TG we are on either on the BM or TGIF selfcare dash? Or do we have to constantly change it and restart analog bridge?

 

 

 

--

 

Thank You,

 

Aaron Groover

(610) 379 6148

K3ALG@...

agroover@...

 

The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

 



One TG in Analog Bridge

Aaron Groover
 

Is there a way to just set a basic TG for example “9” and be able to talk on what static TG we are on either on the BM or TGIF selfcare dash? Or do we have to constantly change it and restart analog bridge?

 

 

 

--

 

Thank You,

 

Aaron Groover

(610) 379 6148

K3ALG@...

agroover@...

 

The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

 


Re: YSF > ASL using XLXd reflector

Steve N4IRS
 

Are you connecting to a DMR or YSF XLX connection? MB can connect directly to a YSF reflector without need for YSFGateway or to a XLX DMR reflector.

On 10/27/20 4:41 PM, k7wby@... wrote:
Hi folks, so I have MB > XLXd and the xlx dashboard shows the connection as a Repeater/Node of K7wBY B and the channel is blank. I tried adding Options=XLX:4008 to see if it would come up on Channel H but that didn't seem to work. I suspect that I'm going to need to run YSFGateway and then point MB to the gateway.


YSF > ASL using XLXd reflector

k7wby@...
 

Hi folks, so I have MB > XLXd and the xlx dashboard shows the connection as a Repeater/Node of K7wBY B and the channel is blank. I tried adding Options=XLX:4008 to see if it would come up on Channel H but that didn't seem to work. I suspect that I'm going to need to run YSFGateway and then point MB to the gateway.


Re: Some basic dv switch questions, hoping you can help

Steve N4IRS
 

Huh?

On 10/26/2020 2:47 PM, lee kasen wrote:
Get a pi i use the pi3b and an mmdvm hat (Google it) then www. pi-star. Co. Uk.(no spaces)  youtube or ham radio concepts (seting up a mmdvm) and have fun. You may want to get a dmr radio tyt md 380 is the one i have. (learn how to work code plug) hope that gets you started 

On Sat, Oct 24, 2020, 17:12 Jed Barton <jedbarton@...> wrote:
Hey guys,

Jed.n1jbc here.  So, i'm brand new to this dvswitch thing, and
honestly it seems pretty cool.
So, the furthest i've gotten with it, is hooking it up to my allstar
node, using a network radio.  I'm using an Inrico t-320 network radio,
and have dvswitch installed on it, and am connecting it to my allstar
node.  It works great.
Now it's time to expand it further.  I've been told that i can run
dmr, and other digital modes if i put a pi together.  So i'm at that
point where i want to go to that next step.  What do i need to do?
I'm going to have a lot of questions here.

Cheers,

Jed







Re: Some basic dv switch questions, hoping you can help

lee kasen
 

Get a pi i use the pi3b and an mmdvm hat (Google it) then www. pi-star. Co. Uk.(no spaces)  youtube or ham radio concepts (seting up a mmdvm) and have fun. You may want to get a dmr radio tyt md 380 is the one i have. (learn how to work code plug) hope that gets you started 


On Sat, Oct 24, 2020, 17:12 Jed Barton <jedbarton@...> wrote:
Hey guys,

Jed.n1jbc here.  So, i'm brand new to this dvswitch thing, and
honestly it seems pretty cool.
So, the furthest i've gotten with it, is hooking it up to my allstar
node, using a network radio.  I'm using an Inrico t-320 network radio,
and have dvswitch installed on it, and am connecting it to my allstar
node.  It works great.
Now it's time to expand it further.  I've been told that i can run
dmr, and other digital modes if i put a pi together.  So i'm at that
point where i want to go to that next step.  What do i need to do?
I'm going to have a lot of questions here.

Cheers,

Jed






Re: M17 Support #mmdvm_bridge

Steve N4IRS
 

Thanks.
Mike and I talked about supporting CW, but maybe not MCW. ;)

Steve

On 10/26/2020 10:54 AM, k7wby@... wrote:
Good plan Steve, with over 75 digital modes currently available it would be an insane project to try to accommodate them all. 


Re: M17 Support #mmdvm_bridge

k7wby@...
 

Good plan Steve, with over 75 digital modes currently available it would be an insane project to try to accommodate them all. 


Re: M17 Support #mmdvm_bridge

Steve N4IRS
 

Maybe in the future. We will see if it really gets any use.

On 10/26/2020 8:49 AM, Roby IV3JDV wrote:

Hi Steve, are you planning to support the new M17 protocol?


Roby IV3JDV


2581 - 2600 of 9882