Date   

Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

Eric-K6KWB
 

Andrew,
You can create another instance of MB crossmode DMR to YSF looks like this:

BMTG<->MB<->YSFreflector   - point DMR to talk group of your choice and point YSF to IP or DNS ysfreflector.

73, Eric


Re: #mmdvm_bridge #mmdvm_bridge

JJ Cummings
 

Are you using an openbridge connection or are you connecting to BM as a PEER?  Based on what you say you are doing it as a PEER, which you should not be doing.  Please create an Openbridge and go that route.

JJC

On Mon, Apr 20, 2020 at 12:42 PM <john.brazel225@...> wrote:
MMDVM Bridge running on raspberry pi3, i have allstar and echolink working, and connected to brandmeister with no problems and the bridge does exactly what it supposed to do and functions perfect, however, every Sunday night/Monday morning, it will not connect to anything. I have the pi set to reboot every night at midnight, and upon reboot, a macro will get my bridge connected back to an echolink conference...Ecxept for the wee hours of Monday morning and most of the day Monday. I have completely started over twice with fresh installs and keep coming up with the same issue. I'm just lost on this one. Any Ideas?

Thanks, 
John
KK4GXP


Re: Changelog

Steve N4IRS
 
Edited

I have posted armhf, arm64, armv6l i386 and amd64 to GitHub. (The full Monty)
Last update to github: 04/26/2020 07:37:00 EST


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Mike Zingman - N4IRR <mike.zingman@...>
Sent: Monday, April 20, 2020 1:26:28 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Changelog
 

[Edited Message Follows]

We just posted some changes to the components, here is the. changelog.  Several of these changes will require significant doc for you to use so more to come:
AB:
  • Add AGC update including new settings
        • In AB.ini you can now set usrpAgc to adjust the threshold, slope and decay of the AGC
        • "Threshold" specifies AGC Knee in dB if AGC is active.( nominal range -160 to 0dB)

        • "Slope" specifies dB reduction in output at knee from maximum output level(nominal range 0 to 10dB) 
        • "Decay" is AGC decay value in milliseconds ( nominal range 20 to 5000 milliSeconds)

      • Add reloadDatabase remote command
        • This command (issued from dvswitch.sh) will cause AB to reload its internal database of users from disk.  This is normally done once every 24h
  • Add menu command (does not popup menu on mobile)
        • Like the "macro" menu for DVSM/pyUC, the menu command loads a transient menu into the client. 
        • Unlike the "macro" command (which now popups up immediately) the menu command just loads the menu
        • This command is most useful in conjunction with the OnRegister macro
  • Support USRP ping back (NAT keep alive)
        • Allow AB to respect a reverse keep alive from the mobile client for some NAT situations
  • Multiport transmit to support better bridge creation
        • This requires a full post all by itself, but the quick description is that a comma delimited list of transmit ports is now supported by AB and MB
        • The main purpose of this is to support better bridge architectures
        • Other uses include logging and streaming 
  • Allow macro variables with substitution
        • Again a single change that requires a full post.
        • Variables are now supported in the macro section of AB.ini
        • The variables are substituted by the shell before command. execution
        • The variables allow for much more concise command line strings
        • The variables make for much more readable macro definitions
        • Less dedicated scripts will. be needed as the macro definition can be defined in the section alone
        • Variables are exported to the environment and be used by client scripts for context
  • Better ini parsing error messages
        • When an error. is encountered in the parsing of the ini files, a better error message is. generated to. help diagnose the problem
  • Add warning if call not found in database (DSTAR)
        • DSTAR/ircddbGateway is picky and wants a valid callsign to operate.
        • This warning tells you that a call can not be found in the database that matches the DMR ID/CCS7 provided in "gatewayDmrId"
  • Add name lookup and metadata export
        • Metadata exported from the USRP interface now includes the first name and callsign of the DMR ID
        • The information comes from the database file loaded by "subscriberFile"
  • Change default transferRoot to /tmp
        • Change the default so that users who fail to set this parameter still function as expected
  • Make tune command able to invoke macros
        • The dvswitch.sh tune command/AB now supports invocation of AB macros using the same syntax (*) as DVSM/pyUC
dvswitch.sh
  • Inherit dir names from environment
        • Along with the variable support in AB, dvswitch.sh can now use AB_DIR, MMDVM_DIR and NODE_DIR from the environment
  • Use awk and not jq
        • On small machines (older Raspberry Pi) using jq would choke on large database files (DMR)
        • We moved bac to using awk which performs MUCH better and does not choke
  • Change ASL validation to a more visible node
      • Allow several commands to execute without ABInfo being present.
  • Add download and validation of user database files.
      • Support new AB commands reloadDatabase, AGC settings, etc
MB:
  • Change DMR networks on the fly.
        • The DMR tune command now support network selection.
        • The tune syntax. is PPPPP@AAAAA:###:OOOO
        • Where
          • PPPPP is the password for the DMR server
          • AAAA is the. FQDN (ip address) of the server
          • #### is the port that the DMR server is listening on
          • OOOO is any options that may be needed (XLX and DMR+)
  • Comma delimited set of transmit ports for each mode.
        • This will take a whole post to describe!  Maybe even two
        • The transmit ports in DVSWITCH.INI now take a comma delimited list of ports
        • These ports will allow you to set up single instance bridges with like mode partners with greater than two networks
      • NXDN remote command error silence (Just a bug fix)
      • DSTAR remote command was dropping into END_TX case. (just a bug fix)
  • Better error message for dvswitch.ini file parsing.
        • When an error. is found while parsing the ini files, a better error message is generated
  • DMR support for talker alias. DVSWITCH.ini has a new tag (TalkerAlias) in the DMR section.
        • This setting will be transmitted to the network on each transmission and can include your name, rig, location, etc
  • P25 Soft Id transmit and receive
        • Still a work in progress, but it is functional on decode
  • YSF split of narrow and wide TLV export to support transcode.
        • Wide mode YSF packets can now be sent to its own list of transmit ports using TXWidePort
        • This is independent of the narrow transmit ports
        • This allows you to transcode one side of YSF while keeping the other format free from conversion
  • YSF uses the latitude and longitude from MMDVM_Bridge.ini for the GPS location.
        • All transmissions will include GPS locations from the MB.ini file if non-zero
  • DSTAR slow data fix DSTAR ini file addition: message
  • Force MB to begin transmission if we did not see one (FCS bug)
  • Make MB return MMDVM and not _Unknown


#mmdvm_bridge #mmdvm_bridge

john.brazel225@...
 

MMDVM Bridge running on raspberry pi3, i have allstar and echolink working, and connected to brandmeister with no problems and the bridge does exactly what it supposed to do and functions perfect, however, every Sunday night/Monday morning, it will not connect to anything. I have the pi set to reboot every night at midnight, and upon reboot, a macro will get my bridge connected back to an echolink conference...Ecxept for the wee hours of Monday morning and most of the day Monday. I have completely started over twice with fresh installs and keep coming up with the same issue. I'm just lost on this one. Any Ideas?

Thanks, 
John
KK4GXP


AB macro changes

Mike Zingman - N4IRR
 

Analog_Bridge macros have been updated to 1) support variables and 2) execute an OnRegister macro when registering a client
 
First OnRegister.  This one is simple, every time a client (DVSM or pyUC) registers with AB the OnRegister macro (if it exists) will be executed. The macro could look like this:
 
[MACROS]
OnRegister=$DVSWITCH menu $AB_DIR/python/macros.txt
 
Why would I want to do this?  You could use the event to set up a mode specific menu for the client (like I did above) or you could reset the current TG to a known starting place or you could execute a message to the client with server status (uptime, cpu load, temp, etc).  The possibilities are endless.
 
Next are the macro variables.  Actually they are no different than environment variables that can be set directly in your macro section and then exported to any shell created when a macro executes.  The basic syntax is:
 
var MACRO_NAME = value
 
Simple.  What happens here is an environment variable is created (just like BASH).  You may then use that variable in one or many other macro commands or just let it be exported to your scripts.
 
As a simple export, you could let it define where you have placed important files in your system.  For example, if you wanted to have a single variable to define the location of your custom scripts for AB you could:
 
var SCRIPT_DIR = $HOME/my_dvswitch_scripts
 
And then:
 
SOME_MACRO = $SCRIPT_DIR/my_script arg1 arg2
OTHER_MACRO = $SCRIPT_DIR/other_script arg1 arg2
 
Two substitutions would happen here.  $SCRIPT_DIR would be replaced by $HOME/my_dvswitch_scripts.  And then $HOME would be replaced by the users home directory.   See how you would build these things up?
 
A more complex example. Right from my development machine:
 
var DVSWITCH=$AB_DIR/python/dvswitch.sh
var DVSWITCH_INI=$MMDVM_DIR/DVSwitch.ini
var TOAST=$DVSWITCH message
 
VERSION=$TOAST "`$DVSWITCH version`"
UPDATE=$DVSWITCH update;$TOAST "Database files have been updated"
TIME=$TOAST "Time is `date`"
TG=$TOAST "Current Talkgroup is `$DVSWITCH tune`"
 
I have created three variables which will make my life easier as I use them.  The first is a simple $DVSWITCH which is replacement for the full path to my dvswitch.sh script.  I can then use that nasty path to define a cool command $TOAST which I use to send messages to my DVSM client.  Now I know many of you are NOT BASH programmers, so I get that this a rather esoteric change to AB.  But for those of us who like to create scripts, this will make our life easier.
 
Also, don't forget that these variables are EXPORTED to your child shells when a macro is executed.  You may have noticed a change in dvswitch.sh that will take the environment variables if they exist for AB_DIR, MMDVM_DIR and NODE_DIR.  This will allow you to have several different AB.ini files each with different paths if you wanted.
 
  
Mike N4iRR
 
 


Re: Changelog

Kevin - W8KHW
 

Wow, you guys really have had cabin fever. Thank you!

Kevin
W8KHW 

On Apr 20, 2020, at 1:28 PM, Mike Zingman - N4IRR <mike.zingman@...> wrote:



[Edited Message Follows]

We just posted some changes to the components, here is the. changelog.  Several of these changes will require significant doc for you to use so more to come:
AB:
  • Add AGC update including new settings
        • In AB.ini you can now set usrpAgc to adjust the threshold, slope and decay of the AGC
        • "Threshold" specifies AGC Knee in dB if AGC is active.( nominal range -160 to 0dB)

        • "Slope" specifies dB reduction in output at knee from maximum output level(nominal range 0 to 10dB) 
        • "Decay" is AGC decay value in milliseconds ( nominal range 20 to 5000 milliSeconds)

      • Add reloadDatabase remote command
        • This command (issued from dvswitch.sh) will cause AB to reload its internal database of users from disk.  This is normally done once every 24h
  • Add menu command (does not popup menu on mobile)
        • Like the "macro" menu for DVSM/pyUC, the menu command loads a transient menu into the client. 
        • Unlike the "macro" command (which now popups up immediately) the menu command just loads the menu
        • This command is most useful in conjunction with the OnRegister macro
  • Support USRP ping back (NAT keep alive)
        • Allow AB to respect a reverse keep alive from the mobile client for some NAT situations
  • Multiport transmit to support better bridge creation
        • This requires a full post all by itself, but the quick description is that a comma delimited list of transmit ports is now supported by AB and MB
        • The main purpose of this is to support better bridge architectures
        • Other uses include logging and streaming 
  • Allow macro variables with substitution
        • Again a single change that requires a full post.
        • Variables are now supported in the macro section of AB.ini
        • The variables are substituted by the shell before command. execution
        • The variables allow for much more concise command line strings
        • The variables make for much more readable macro definitions
        • Less dedicated scripts will. be needed as the macro definition can be defined in the section alone
        • Variables are exported to the environment and be used by client scripts for context
  • Better ini parsing error messages
        • When an error. is encountered in the parsing of the ini files, a better error message is. generated to. help diagnose the problem
  • Add warning if call not found in database (DSTAR)
        • DSTAR/ircddbGateway is picky and wants a valid callsign to operate.
        • This warning tells you that a call can not be found in the database that matches the DMR ID/CCS7 provided in "gatewayDmrId"
  • Add name lookup and metadata export
        • Metadata exported from the USRP interface now includes the first name and callsign of the DMR ID
        • The information comes from the database file loaded by "subscriberFile"
  • Change default transferRoot to /tmp
        • Change the default so that users who fail to set this parameter still function as expected
  • Make tune command able to invoke macros
        • The dvswitch.sh tune command/AB now supports invocation of AB macros using the same syntax (*) as DVSM/pyUC
dvswitch.sh
  • Inherit dir names from environment
        • Along with the variable support in AB, dvswitch.sh can now use AB_DIR, MMDVM_DIR and NODE_DIR from the environment
  • Use awk and not jq
        • On small machines (older Raspberry Pi) using jq would choke on large database files (DMR)
        • We moved bac to using awk which performs MUCH better and does not choke
  • Change ASL validation to a more visible node
      • Allow several commands to execute without ABInfo being present.
  • Add download and validation of user database files.
      • Support new AB commands reloadDatabase, AGC settings, etc
MB:
  • Change DMR networks on the fly.
        • The DMR tune command now support network selection.
        • The tune syntax. is PPPPP@AAAAA:###:OOOO
        • Where
          • PPPPP is the password for the DMR server
          • AAAA is the. FQDN (ip address) of the server
          • #### is the port that the DMR server is listening on
          • OOOO is any options that may be needed (XLX and DMR+)
  • Comma delimited set of transmit ports for each mode.
        • This will take a whole post to describe!  Maybe even two
        • The transmit ports in DVSWITCH.INI now take a comma delimited list of ports
        • These ports will allow you to set up single instance bridges with like mode partners with greater than two networks
      • NXDN remote command error silence (Just a bug fix)
      • DSTAR remote command was dropping into END_TX case. (just a bug fix)
  • Better error message for dvswitch.ini file parsing.
        • When an error. is found while parsing the ini files, a better error message is generated
  • DMR support for talker alias. DVSWITCH.ini has a new tag (TalkerAlias) in the DMR section.
        • This setting will be transmitted to the network on each transmission and can include your name, rig, location, etc
  • P25 Soft Id transmit and receive
        • Still a work in progress, but it is functional on decode
  • YSF split of narrow and wide TLV export to support transcode.
        • Wide mode YSF packets can now be sent to its own list of transmit ports using TXWidePort
        • This is independent of the narrow transmit ports
        • This allows you to transcode one side of YSF while keeping the other format free from conversion
  • YSF uses the latitude and longitude from MMDVM_Bridge.ini for the GPS location.
        • All transmissions will include GPS locations from the MB.ini file if non-zero
  • DSTAR slow data fix DSTAR ini file addition: message
  • Force MB to begin transmission if we did not see one (FCS bug)
  • Make MB return MMDVM and not _Unknown


Re: Changelog

JJ Cummings
 

Awesome work Mike!


On Mon, Apr 20, 2020 at 11:28 AM Mike Zingman - N4IRR <mike.zingman@...> wrote:

[Edited Message Follows]

We just posted some changes to the components, here is the. changelog.  Several of these changes will require significant doc for you to use so more to come:
AB:
  • Add AGC update including new settings
        • In AB.ini you can now set usrpAgc to adjust the threshold, slope and decay of the AGC
        • "Threshold" specifies AGC Knee in dB if AGC is active.( nominal range -160 to 0dB)

        • "Slope" specifies dB reduction in output at knee from maximum output level(nominal range 0 to 10dB) 
        • "Decay" is AGC decay value in milliseconds ( nominal range 20 to 5000 milliSeconds)

      • Add reloadDatabase remote command
        • This command (issued from dvswitch.sh) will cause AB to reload its internal database of users from disk.  This is normally done once every 24h
  • Add menu command (does not popup menu on mobile)
        • Like the "macro" menu for DVSM/pyUC, the menu command loads a transient menu into the client. 
        • Unlike the "macro" command (which now popups up immediately) the menu command just loads the menu
        • This command is most useful in conjunction with the OnRegister macro
  • Support USRP ping back (NAT keep alive)
        • Allow AB to respect a reverse keep alive from the mobile client for some NAT situations
  • Multiport transmit to support better bridge creation
        • This requires a full post all by itself, but the quick description is that a comma delimited list of transmit ports is now supported by AB and MB
        • The main purpose of this is to support better bridge architectures
        • Other uses include logging and streaming 
  • Allow macro variables with substitution
        • Again a single change that requires a full post.
        • Variables are now supported in the macro section of AB.ini
        • The variables are substituted by the shell before command. execution
        • The variables allow for much more concise command line strings
        • The variables make for much more readable macro definitions
        • Less dedicated scripts will. be needed as the macro definition can be defined in the section alone
        • Variables are exported to the environment and be used by client scripts for context
  • Better ini parsing error messages
        • When an error. is encountered in the parsing of the ini files, a better error message is. generated to. help diagnose the problem
  • Add warning if call not found in database (DSTAR)
        • DSTAR/ircddbGateway is picky and wants a valid callsign to operate.
        • This warning tells you that a call can not be found in the database that matches the DMR ID/CCS7 provided in "gatewayDmrId"
  • Add name lookup and metadata export
        • Metadata exported from the USRP interface now includes the first name and callsign of the DMR ID
        • The information comes from the database file loaded by "subscriberFile"
  • Change default transferRoot to /tmp
        • Change the default so that users who fail to set this parameter still function as expected
  • Make tune command able to invoke macros
        • The dvswitch.sh tune command/AB now supports invocation of AB macros using the same syntax (*) as DVSM/pyUC
dvswitch.sh
  • Inherit dir names from environment
        • Along with the variable support in AB, dvswitch.sh can now use AB_DIR, MMDVM_DIR and NODE_DIR from the environment
  • Use awk and not jq
        • On small machines (older Raspberry Pi) using jq would choke on large database files (DMR)
        • We moved bac to using awk which performs MUCH better and does not choke
  • Change ASL validation to a more visible node
      • Allow several commands to execute without ABInfo being present.
  • Add download and validation of user database files.
      • Support new AB commands reloadDatabase, AGC settings, etc
MB:
  • Change DMR networks on the fly.
        • The DMR tune command now support network selection.
        • The tune syntax. is PPPPP@AAAAA:###:OOOO
        • Where
          • PPPPP is the password for the DMR server
          • AAAA is the. FQDN (ip address) of the server
          • #### is the port that the DMR server is listening on
          • OOOO is any options that may be needed (XLX and DMR+)
  • Comma delimited set of transmit ports for each mode.
        • This will take a whole post to describe!  Maybe even two
        • The transmit ports in DVSWITCH.INI now take a comma delimited list of ports
        • These ports will allow you to set up single instance bridges with like mode partners with greater than two networks
      • NXDN remote command error silence (Just a bug fix)
      • DSTAR remote command was dropping into END_TX case. (just a bug fix)
  • Better error message for dvswitch.ini file parsing.
        • When an error. is found while parsing the ini files, a better error message is generated
  • DMR support for talker alias. DVSWITCH.ini has a new tag (TalkerAlias) in the DMR section.
        • This setting will be transmitted to the network on each transmission and can include your name, rig, location, etc
  • P25 Soft Id transmit and receive
        • Still a work in progress, but it is functional on decode
  • YSF split of narrow and wide TLV export to support transcode.
        • Wide mode YSF packets can now be sent to its own list of transmit ports using TXWidePort
        • This is independent of the narrow transmit ports
        • This allows you to transcode one side of YSF while keeping the other format free from conversion
  • YSF uses the latitude and longitude from MMDVM_Bridge.ini for the GPS location.
        • All transmissions will include GPS locations from the MB.ini file if non-zero
  • DSTAR slow data fix DSTAR ini file addition: message
  • Force MB to begin transmission if we did not see one (FCS bug)
  • Make MB return MMDVM and not _Unknown


Changelog

Mike Zingman - N4IRR
 
Edited

We just posted some changes to the components, here is the. changelog.  Several of these changes will require significant doc for you to use so more to come:
AB:
  • Add AGC update including new settings
        • In AB.ini you can now set usrpAgc to adjust the threshold, slope and decay of the AGC
        • "Threshold" specifies AGC Knee in dB if AGC is active.( nominal range -160 to 0dB)

        • "Slope" specifies dB reduction in output at knee from maximum output level(nominal range 0 to 10dB) 
        • "Decay" is AGC decay value in milliseconds ( nominal range 20 to 5000 milliSeconds)

      • Add reloadDatabase remote command
        • This command (issued from dvswitch.sh) will cause AB to reload its internal database of users from disk.  This is normally done once every 24h
  • Add menu command (does not popup menu on mobile)
        • Like the "macro" menu for DVSM/pyUC, the menu command loads a transient menu into the client. 
        • Unlike the "macro" command (which now popups up immediately) the menu command just loads the menu
        • This command is most useful in conjunction with the OnRegister macro
  • Support USRP ping back (NAT keep alive)
        • Allow AB to respect a reverse keep alive from the mobile client for some NAT situations
  • Multiport transmit to support better bridge creation
        • This requires a full post all by itself, but the quick description is that a comma delimited list of transmit ports is now supported by AB and MB
        • The main purpose of this is to support better bridge architectures
        • Other uses include logging and streaming 
  • Allow macro variables with substitution
        • Again a single change that requires a full post.
        • Variables are now supported in the macro section of AB.ini
        • The variables are substituted by the shell before command. execution
        • The variables allow for much more concise command line strings
        • The variables make for much more readable macro definitions
        • Less dedicated scripts will. be needed as the macro definition can be defined in the section alone
        • Variables are exported to the environment and be used by client scripts for context
  • Better ini parsing error messages
        • When an error. is encountered in the parsing of the ini files, a better error message is. generated to. help diagnose the problem
  • Add warning if call not found in database (DSTAR)
        • DSTAR/ircddbGateway is picky and wants a valid callsign to operate.
        • This warning tells you that a call can not be found in the database that matches the DMR ID/CCS7 provided in "gatewayDmrId"
  • Add name lookup and metadata export
        • Metadata exported from the USRP interface now includes the first name and callsign of the DMR ID
        • The information comes from the database file loaded by "subscriberFile"
  • Change default transferRoot to /tmp
        • Change the default so that users who fail to set this parameter still function as expected
  • Make tune command able to invoke macros
        • The dvswitch.sh tune command/AB now supports invocation of AB macros using the same syntax (*) as DVSM/pyUC
dvswitch.sh
  • Inherit dir names from environment
        • Along with the variable support in AB, dvswitch.sh can now use AB_DIR, MMDVM_DIR and NODE_DIR from the environment
  • Use awk and not jq
        • On small machines (older Raspberry Pi) using jq would choke on large database files (DMR)
        • We moved bac to using awk which performs MUCH better and does not choke
  • Change ASL validation to a more visible node
      • Allow several commands to execute without ABInfo being present.
  • Add download and validation of user database files.
      • Support new AB commands reloadDatabase, AGC settings, etc
MB:
  • Change DMR networks on the fly.
        • The DMR tune command now support network selection.
        • The tune syntax. is PPPPP@AAAAA:###:OOOO
        • Where
          • PPPPP is the password for the DMR server
          • AAAA is the. FQDN (ip address) of the server
          • #### is the port that the DMR server is listening on
          • OOOO is any options that may be needed (XLX and DMR+)
  • Comma delimited set of transmit ports for each mode.
        • This will take a whole post to describe!  Maybe even two
        • The transmit ports in DVSWITCH.INI now take a comma delimited list of ports
        • These ports will allow you to set up single instance bridges with like mode partners with greater than two networks
      • NXDN remote command error silence (Just a bug fix)
      • DSTAR remote command was dropping into END_TX case. (just a bug fix)
  • Better error message for dvswitch.ini file parsing.
        • When an error. is found while parsing the ini files, a better error message is generated
  • DMR support for talker alias. DVSWITCH.ini has a new tag (TalkerAlias) in the DMR section.
        • This setting will be transmitted to the network on each transmission and can include your name, rig, location, etc
  • P25 Soft Id transmit and receive
        • Still a work in progress, but it is functional on decode
  • YSF split of narrow and wide TLV export to support transcode.
        • Wide mode YSF packets can now be sent to its own list of transmit ports using TXWidePort
        • This is independent of the narrow transmit ports
        • This allows you to transcode one side of YSF while keeping the other format free from conversion
  • YSF uses the latitude and longitude from MMDVM_Bridge.ini for the GPS location.
        • All transmissions will include GPS locations from the MB.ini file if non-zero
  • DSTAR slow data fix DSTAR ini file addition: message
  • Force MB to begin transmission if we did not see one (FCS bug)
  • Make MB return MMDVM and not _Unknown


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

andrew delgado
 
Edited

Hi Ernie!

Thanks for the inputs, where can i find sample config file or documentation about hblink connecting or bridging to YSF and DMR?

Thanks!
Andrew


Re: ASL <> DMR <> YSF inquiry? #mmdvm_bridge

 

Asl<>AB<>MB<>Hblink3<>MB<>YSFReflector


ASL <> DMR <> YSF inquiry? #mmdvm_bridge

andrew delgado
 

Hello!

how can i do this setup? ASL <> DMR <> YSF
what are the tools do i need?

i was able to setup ASL <> DMR now how can i add YSF reflector to have it ASL<>DMR <> YSF? what tools to i need?

Thanks!
Andrew


D-Star info from G4LKX

Steve N4IRS
 

This message contains important information that I want disseminated far and wide please.

I have been approached by the people who run aprs.fi and REF001/REF030 (not the same people) about problems being caused by hotspots. This is down to usage and I hope that people will act on this information:

1. APRS, it is important that when configuring your hotspot, that you ensure that the suffix used for accessing aprs.fi is unique. For example if you use more than one hotspot, then ensure that for every mode and for every hotspot, the aprs.fi access callsign is unique. This is usually done by specifying a unique suffix to the callsign used by the hotspot. If more than one hotspot attempts to access aprs.fi with the same callsign+suffix combination, the first one is thrown off, and the new one connects. In the meantime the original one tries to connect and throw the new one off. This can happen multiple times per second, and is causing problems for them. Please, please, please, look at your configurations and if you have a duplicate, change one of them.

2. REF001/REF030, apparently the network load on these D-Star reflectors is now very high due to the number of hotspots connecting and staying connected. Could you please consider changing your gateway configuration so that you disconnect after a certain period of inactivity (this means local RF activity) so that they aren't overloaded. I know we like to listen out for activity, but we must also realise that D-Star popular reflectors const money to run, and that includes network and processor usage. A quick look at their dashboards will reveal the problem, they're huge.

Jonathan  G4KLX


Re: #analog_bridge #analog_bridge #analog_bridge

Steve N4IRS
 

On 4/19/20 7:41 AM, Philippe wrote:
Help me to make working the application tx and Rx


#analog_bridge #analog_bridge #analog_bridge

 

Help me to make working the application tx and Rx


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Josep
 

Ea3abn@...



Enviado desde mi dispositivo Samsung


-------- Mensaje original --------
De: EA5GVK Joaquin <ea5gvk@...>
Fecha: 18/04/2020 11:52 (GMT+01:00)
Para: main@DVSwitch.groups.io
Asunto: Re: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

DVLINK V9 IS HERE.
INCLUDES NEW DVSWITCH, SINGLE USER AND MULTIUSER WITH AMBE PHYSICAL SERVER, HBLINK IMPROVED, AND A GREAT NEW "HOTSPOTS" SINGLE AND MULTIUSER TO HAVE YOUR DMOS, HOTSPOT, MMDVM REPEATERS IN THE SAME IMAGE.
 (Thanks to the great work of my friend EA7JCL&EA5GVK)

 LINK INFO & DOWNLOAD: http://ea5gvk-dmr.zigor.es/2020/04/18/aqui-os-presento-a-dvlink-v9-con-muchas-novedades/

.REMEMBER THE DVLINK PHILOSOPHY IS TO HELP THE AMATEUR RADIO OPERATOR TO APPROACH DIGITAL RADIO WITH GUARANTEES FOR HIM AND THE DIGITAL NETWORKS AND NOT THE CONTRARY. DVLINK USES THIRD-PARTY SOFTWARE WITHOUT MODIFICATION AND WITH ORIGINAL CONFIGURATIONS OF ITS CREATORS.
- SUPPORT IN SPANISH, WE ARE WORKING FOR ENGLISH AND FRENCH LANGUAGES.
TECHNICAL SUPPORT WITH TELEGRAM GROUP
JOIN: https://t.me/joinchat/AveYRFJCxSbhKbI2ti1_Og

Thanks to the DVSwitch and HBLINK team, without your software, we would be sadder.
Thanks to Steve, Cort and all the DVSwitch and HBLINK team, for your great work.


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

EA5GVK Joaquin
 

DVLINK V9 IS HERE.
INCLUDES NEW DVSWITCH, SINGLE USER AND MULTIUSER WITH AMBE PHYSICAL SERVER, HBLINK IMPROVED, AND A GREAT NEW "HOTSPOTS" SINGLE AND MULTIUSER TO HAVE YOUR DMOS, HOTSPOT, MMDVM REPEATERS IN THE SAME IMAGE.
 (Thanks to the great work of my friend EA7JCL&EA5GVK)

 LINK INFO & DOWNLOAD: http://ea5gvk-dmr.zigor.es/2020/04/18/aqui-os-presento-a-dvlink-v9-con-muchas-novedades/

.REMEMBER THE DVLINK PHILOSOPHY IS TO HELP THE AMATEUR RADIO OPERATOR TO APPROACH DIGITAL RADIO WITH GUARANTEES FOR HIM AND THE DIGITAL NETWORKS AND NOT THE CONTRARY. DVLINK USES THIRD-PARTY SOFTWARE WITHOUT MODIFICATION AND WITH ORIGINAL CONFIGURATIONS OF ITS CREATORS.
- SUPPORT IN SPANISH, WE ARE WORKING FOR ENGLISH AND FRENCH LANGUAGES.
TECHNICAL SUPPORT WITH TELEGRAM GROUP
JOIN: https://t.me/joinchat/AveYRFJCxSbhKbI2ti1_Og

Thanks to the DVSwitch and HBLINK team, without your software, we would be sadder.
Thanks to Steve, Cort and all the DVSwitch and HBLINK team, for your great work.


Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ? #mmdvm_bridge

Uli
 

Yes that was me yesterday on your Reflector testing.
Can you post you MMDVM_Bridge.ini and your DVSwitch.ini so that I can compare it to mine?
Maybe that gives a hint where the problem lies.

Uli


Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ? #mmdvm_bridge

Tito Lopez - YN1OB
 

Ah so you are the one that is connected to the reflector.  Cool. So it works fine.
 The problem is on my end. 


On Fri, Apr 17, 2020 at 10:11 AM Uli <g90@...> wrote:
@Tito: I have put your YSF Reflector IP into my MMDVM_Bridge.ini file rebooted and did a few tests. It works fine, I get audio in both directions.
Did you open up in your router port 42000 UDP pointing to the IP of your RPI with the MMDVM_Bridge running on it?

Uli


Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ? #mmdvm_bridge

Uli
 

@Tito: I have put your YSF Reflector IP into my MMDVM_Bridge.ini file rebooted and did a few tests. It works fine, I get audio in both directions.
Did you open up in your router port 42000 UDP pointing to the IP of your RPI with the MMDVM_Bridge running on it?

Uli


Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ? #mmdvm_bridge

Uli
 

@Tito: Did you open up all necessary ports on your router? That was one of my problems in the first place that prevented the connection
Try to run something like   tail -f /var/log/mmdvm/MMDVM_Bridge-2020-04-17.log    (replace the date with the current date) to display a live log and check what is going on
Now take a DMR HT and a C4fm HT key up and check whats shown in the livelog

@Steve: I have no clue why the DVSwitch system builder did not work. It might have been a user rights problem or it did not like the raspbian stretch lite, but I don´t know for sure.
When I have time, I´ll give it another try.

Uli

3381 - 3400 of 9520