Date   

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

andrew delgado
 

Thanks a lot Eric, i was able to setup this,  73!


Re: Changelog

Mike Zingman - N4IRR
 

Patrick,

Thanks for the feedback.  
A great thanks go out to Moe AE4JY.  His code for AGC is awesome.  Check out the incredible discussion in this doc if you want to know more:
https://sourceforge.net/projects/cutesdr/files/doc/CuteSDR102.pdf/download


Re: Changelog

Patrick Perdue
 

I installed the new A_B yesterday morning, and enabled AGC. What a difference! Very smooth, and gets through analog a lot better with certain radios.

Thanks for the great work.


On 4/20/2020 1:26 PM, Mike Zingman - N4IRR 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

ea7jcl@...
 

Wow! Good job. Thanks


Re: Changelog

HL5KY
 
Edited

Thank you for the great work.
 
Here I have some issue with the new update. After updating binaries, I can't transmit on DSTAR. Connecting DSTAR reflector seems to be ok, as I could hear the other's voice. Pressing PTT made it red but no real TX was carried out. And in about 5~10 seconds, it became unregistered.
 
Please find the attached files, a part of MMDVM_Bridge.log and the result of './dvswitch.sh show'. As you can see, after pressing PTT, it changes to DMR by itself.
 
Joe, HL5KY.
 
p.s. TG450 is a static TG.


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

Eric-K6KWB
 

You dont need Hblink in between. 

Here is the working sample config:
MB.ini
[DMR Network]
Enable=1
Address=3103.repeater.net
Port=62031
Jitter=360
Local=62033   >>>> make sure change this, it will interfere with your first MB instance if NOT change.
Password=passw0rd
Slot1=0
Slot2=1
Debug=0
 
[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=0
GatewayAddress=ip or dns ysf reflector
GatewayPort=42000  >>>port YSFReflector

DVSwitch.ini

[DMR]
Address = 127.0.0.1             
TXPort = 35103                  
RXPort = 35100                  
Slot = 2               
[YSF]
Address = 127.0.0.1             
TXPort = 35100                  
RXPort = 35103                  
FallbackID = your id      
ExportTG = your TG               
Slot = 2 

Log in to BM self care and set the talk group.

73, Eric             


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

Steve N4IRS
 

The one to one bridge was the first method we came up with. What always bothered us was the complexity of a one to many bridge. Mike came up with a elegant "simple" way of making that happen. It is pretty much limited to "like modes" in this case, DMR, YSFn and NXDN which are all AMBE. Everything we do is to add power to the "partners" As we have said over and over "With great power, comes some complexity" (with apologies to Stan lee)

Steve, N4IRS

On 4/20/20 8:04 PM, andrew delgado via groups.io wrote:
wow thanks Steve, this is what i have in mind that i thought be working then i think that it will not work so i created a new instance but still no luck because of im mixing ports conflict :)

Thanks Steve looking forward to that kind of simple but rock setup!
Andrew
73!


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

andrew delgado
 

wow thanks Steve, this is what i have in mind that i thought be working then i think that it will not work so i created a new instance but still no luck because of im mixing ports conflict :)

Thanks Steve looking forward to that kind of simple but rock setup!
Andrew
73!


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

Steve N4IRS
 

Andrew,
I would suggest you wait a few days. We just updated to allow MB to bridge or connect to all like modes in a single instance of MB. We are putting a document in the next few days.
It will look something like this:

ASL <-> AB <-> MB <-> DMR
               | <--> YSF

(best I can do with ASCII graphics)

73, Steve N4IRS

On 4/20/20 7:40 PM, andrew delgado via groups.io wrote:
Hi all,

i was able to work successfully the both experiments ASL <> AB <> MB <> DMR using the link provided by steve n4irs, and also the YSFReflector <> MB <> DMR..

i have the idea of having a new instance but im mixing the ports or do i really need hblink3 in between? im setting this up on a single debian box.

Regards,
Andrew


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

andrew delgado
 

Hi all,

i was able to work successfully the both experiments ASL <> AB <> MB <> DMR using the link provided by steve n4irs, and also the YSFReflector <> MB <> DMR..

i have the idea of having a new instance but im mixing the ports or do i really need hblink3 in between? im setting this up on a single debian box.

Regards,
Andrew


Re: #mmdvm_bridge #mmdvm_bridge

Brad N8PC
 

that is echolink. suggestion change your time on sunday to like 2 am monday morning to reboot and that should alleviate your problem.  I run mine on a raspberry pi 4 and never rebooted unless I make a change in the system.

On 4/20/2020 3:39 PM, john.brazel225@... wrote:
I'm not sure what openbridge is? I simply followed a guide online on how to set this up. But just to clarify, the BM side of things are working, it's just that my bridge node won't connect back to the echolink conference on a Sunday/Monday reboot.


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

Steve N4IRS
 


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

lee kasen
 

How did you get the ASL<>DMR To work..


On Mon, Apr 20, 2020, 14:00 andrew delgado via groups.io <andrew_12ph=yahoo.com@groups.io> wrote:
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


Re: #mmdvm_bridge #mmdvm_bridge

john.brazel225@...
 

I'm not sure what openbridge is? I simply followed a guide online on how to set this up. But just to clarify, the BM side of things are working, it's just that my bridge node won't connect back to the echolink conference on a Sunday/Monday reboot.


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

3361 - 3380 of 9514