Date   

Anysecu / Inrico B01 BT Microphone

Jose - EA5SW
 

Hello , I have now an Anysecu B01 Bluetooth Microphone, it's a great Bluetooth mic that work very well with Zello app.
The normal BT mode connected to any mobile phone make a great Rx sound and modulation.
You need to route the audio via BT mono app, but sound good.

The buttons for PTT, SOS and select channel + and - are defined into the serial service. When you press any of the buttons the value are send via serial and received into the smartphone.

It's possible implement those serial service into dvswitch mobile to make those buttons operative?

 I think that many of these Chinese BT mics works in this way and are very good for hams.

If anyone of developers need more information or videos, please contact.




Re: YSF on mmdvm switch mobile, help setup, please

IZ4BKK <iz4bkk@...>
 

Hi Ernie
the modified sw is available for mmdvswitch mobile project?
Thanks


USRPaudio Transmitting TG / RID

Kim-Benjamin Lütkemeier
 

Hello Guys,

Its possible to change the RID or TG into the USRPaudio.py?

I make a modification that I can transmit some Wav files. It work but I will transmit File one in TG9 and file Two in TG8
Maybe I can overwrite it from Analogbridge? Also it will be nice when I can Change the RID that I can see on the Radio I will transmit from Wavefile.

Normal Analogbride transmit from 2623266 (DO1KBL) but when I transmit from Wav I will Change ID to 26232661

73
Do1KBL, Kim


USRP

Aaron Groover
 

Hey guys seem to be having a strange issue when transmitting. Just curious to what everyone has there usrp setting at. Apparently I’m having like a clicking over modulation on my side. 

Mine is currently: pic below 

Image.jpegImage.jpeg




Thank You,
Aaron Groover
K3ALG@...
(610) 379-6148


Re: YSF on mmdvm switch mobile, help setup, please

 

Wires-x gateway to wires-x gateway does not work.
Wires-x to mmdvm does not work.
Wires-x with modified mmdvm software works.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Brad N8PC <bradn8pc@...>
Sent: Friday, September 18, 2020 1:16:18 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] YSF on mmdvm switch mobile, help setup, please
 
Yaesu repeaters use wires-x. it is not the same as what is used for MMDVM for FCS and YSF chat rooms

On 9/18/2020 4:37 AM, IZ4BKK wrote:
Hi guys,
I have made a YSF setup on my rasperry's mmdvm switch mobile, and it's run fine BUT there is an issue :
When I select the "Room Italy" (my country) or another ysf room, I can trasmit only to rf MMDVM based repeaters , and not to original yaesu rf repeaters.
Someone can review my ysf setup please? Any suggestion please?
Thanks in advance and sorry for my english.

73 de iz4bkk Andrea


Re: YSF on mmdvm switch mobile, help setup, please

Brad N8PC
 

Yaesu repeaters use wires-x. it is not the same as what is used for MMDVM for FCS and YSF chat rooms

On 9/18/2020 4:37 AM, IZ4BKK wrote:
Hi guys,
I have made a YSF setup on my rasperry's mmdvm switch mobile, and it's run fine BUT there is an issue :
When I select the "Room Italy" (my country) or another ysf room, I can trasmit only to rf MMDVM based repeaters , and not to original yaesu rf repeaters.
Someone can review my ysf setup please? Any suggestion please?
Thanks in advance and sorry for my english.

73 de iz4bkk Andrea


YSF on mmdvm switch mobile, help setup, please

IZ4BKK <iz4bkk@...>
 

Hi guys,
I have made a YSF setup on my rasperry's mmdvm switch mobile, and it's run fine BUT there is an issue :
When I select the "Room Italy" (my country) or another ysf room, I can trasmit only to rf MMDVM based repeaters , and not to original yaesu rf repeaters.
Someone can review my ysf setup please? Any suggestion please?
Thanks in advance and sorry for my english.

73 de iz4bkk Andrea


#mmdvm_bridge #mmdvm_bridge

 

why is there echoing from my node ?


Re: md380-emu

Pete Fierro
 

It's an MD380 radio emulator..Make sure to have the setting to "True" from "False."It enhances the audio in most situations.

Pete
KD2ARB


On Wed, Sep 16, 2020 at 18:48, Karl Koscher
<supersat@...> wrote:
I believe it is used to emulate the MD380 firmware for its AMBE codec, avoiding the need to have a dedicated chip/USB dongle for that. It's only needed when going between systems that use the AMBE codec and those that don't (e.g., analog). 


Talkover my talk groups

Pete Fierro
 

  Hi Guys

   I'm running two pi's on DV switch on DMR on two different TG's.In MMDVM.INI I have my DMR ID along with two different numbers appended at the end of my ID.(05,06)on both pi's

   I'm getting crossover every time someone is on a hotspot for some reason.If I'm  on one pi,sometimes I can hear a qso on the other pi.Is there a fix for this?IAX.CONF in allstar,the IAX port is different as well.I even went so far as to change the private node ID in RPT.CONF to read different numbers to no avail.

  On the brandmeister site I have my DMR ID's there as well as the two digits appended there too.Whats going on?

Thanks
Pete
KD2ARB


Re: md380-emu

Karl Koscher
 

I believe it is used to emulate the MD380 firmware for its AMBE codec, avoiding the need to have a dedicated chip/USB dongle for that. It's only needed when going between systems that use the AMBE codec and those that don't (e.g., analog). 


md380-emu

Aaron Groover
 

Hey guys I been running only just the bridge and MMDVM. However never really played with the 380. What exactly is it for? Multiple connects and such?



--

 

Thank You,

 

Aaron Groover

(610) 379 6148

K3ALG@...

aaron@...

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.


**This message has been composed on a mobile application. Please excuse any grammatical errors**


Re: MMDVM_Bridge segment fault issue

swinger72@...
 

Thanks looking good for 18h now. Thank s for your great work !
73 sylvain  ve2tbu


2nd DVSwitch server and port forwarding.

Derek William Haden <facebook@...>
 

I am thinking of setting up a second DVSwitch server.

I currently have port forwarding enabled on my router for the first server.
So my question is:

Would I run into problems having a 2nd server?


Re: XLX Reflector to DMR talk group bridge on server cloud issue

David Young
 

Hi Steve,
I did download the latest binaries today. 
I reinstalled both the XLX server and DVSwitch modules and updated the MMDVM_Bridge binary afterwards on a different cloud server as I was not happy with the original server operation.  After I reinstalled everything and started it up it worked for maybe 30 minutes and again stopped with those same error messages.  Interesting that in the log it states that MMDVM stopped and it automatically restarted which then caused these errors.
Now this is strange, I restarted the bridge and left the active terminal window open in SSH to view activity for just over 2 hours and it was working without errors, as soon as I closed down the SSH session the bridge stopped working and when I reconnected and looked at the log it generated the same errors.  Maybe this is a clue?
--
Dave WB6DTB


Re: DMR to Analog ASL Bridge

Steve N4IRS
 

On 9/14/2020 3:37 PM, Marshall Oldham wrote:
Okay, I know this has probably been asked many times before.

I did do a search, with lots of results that comes back, almost too much information. :)

I am wondering what the most current (easiest) way to go about building a DMR to Analog bridge is using ASL. 

I have a Raspberry Pi and a ThumbDV DV3000U.

My end goal is to be able to bridge DMR to an Analog system. 

Thanks 

Marshall - ke6pcv 


Re: MMDVM_Bridge segment fault issue

Steve N4IRS
 

I pushed the latest update to MMDVM_Bridge this morning for the AMD64 <https://github.com/DVSwitch/MMDVM_Bridge/raw/master/bin/MMDVM_Bridge.amd64>
Please replace your existing MB and retest.

Steve N4IRS

On 9/14/2020 2:28 PM, swinger72@... wrote:
Hi all. I have been riding for 2 mmdvm_bridge for 1 years already. 1 link my ysf reflector  and the other another ysf reflector . for 4 days an instance has stopped by itself and the only message is segmentation fault. I tried to rebuild without success. this instance is a copy of the original one and the original works fine. now i'm at heart i also notice that at the time of the crash which is never constant that a time lag appears.
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
;[QUANTAR]
;logFilePath = /var/log/Quantar_Bridge.log
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
;logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
;debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)

; Configure the DMR Partner
; Audio format is AMBE 72 bit
;[DMR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
;[DSTAR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;ExportTG = 9                    ; Which TG to export
;Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
;[NXDN]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database
;Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
;Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
;[P25]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 43500                  ; Port to send AMBE TLV frames to (export)
RXPort = 42500                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG =  1234                 ; Which TG to export
Slot = 2                        ; Export slot



[General]
Callsign=F1ZIT-L
Id=302252899
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge2
URL=

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

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

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

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

[D-Star]
Enable=0
Module=C

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

[System Fusion]
Enable=1

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=12345

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

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

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3299
GatewayAddress=127.0.0.1
GatewayPort=42000
Debug=0

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

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






DMR to Analog ASL Bridge

Marshall Oldham
 

Okay, I know this has probably been asked many times before.

I did do a search, with lots of results that comes back, almost too much information. :)

I am wondering what the most current (easiest) way to go about building a DMR to Analog bridge is using ASL. 

I have a Raspberry Pi and a ThumbDV DV3000U.

My end goal is to be able to bridge DMR to an Analog system. 

Thanks 

Marshall - ke6pcv 


MMDVM_Bridge segment fault issue

swinger72@...
 
Edited

Hi all. I have been riding for 2 mmdvm_bridge for 1 years already. 1 link my ysf reflector  and the other another ysf reflector . for 4 days an instance has stopped by itself and the only message is segmentation fault. I tried to rebuild without success. this instance is a copy of the original one and the original works fine. now i'm at heart i also notice that at the time of the crash which is never constant that a time lag appears.
; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
;[QUANTAR]
;logFilePath = /var/log/Quantar_Bridge.log
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
;logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
;debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)

; Configure the DMR Partner
; Audio format is AMBE 72 bit
;[DMR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
;[DSTAR]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;ExportTG = 9                    ; Which TG to export
;Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
;[NXDN]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                  ; Port to send AMBE TLV frames to (export)
;RXPort =                   ; Port to listen on (import)
;FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
;NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database
;Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
;Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
;[P25]
;Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
;TXPort =                   ; Port to send AMBE TLV frames to (export)
;RXPort =                  ; Port to listen on (import)
;Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 43500                  ; Port to send AMBE TLV frames to (export)
RXPort = 42500                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG =  1234                 ; Which TG to export
Slot = 2                        ; Export slot



[General]
Callsign=F1ZIT-L
Id=302252899
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge2
URL=

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

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

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

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

[D-Star]
Enable=0
Module=C

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

[System Fusion]
Enable=1

[P25]
Enable=0
NAC=293

[NXDN]
Enable=0
RAN=1
Id=12345

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

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

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3299
GatewayAddress=127.0.0.1
GatewayPort=42000
Debug=0

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

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





Re: XLX Reflector to DMR talk group bridge on server cloud issue

Steve N4IRS
 

1: yes
2: yes, just in case, I built the most current amd64 binary this morning.
3: will try to look at logs later today.

Steve N4IRS

On 9/14/20 1:42 AM, David Young wrote:
Ok,  I read through the earlier posts on using DVSwitch to bridge XLX reflector to DMR talk group.  Per what I read there was an addition made to MMDVM_Bridge which when using DVSwitch would allow bridging without using DMRGateway.  It appears from the post thread that the changes were only made to the MMDVM_Bridge binary which is used for a Raspberry Pi.  I am trying to bridge XLX to TGIF DMR talk group from a cloud server using the MMDVM_Bridge binary updated to the latest version available for AMD_64 without using DMRGateway.  I have copied the new DVSwitch.ini file which includes the additional entry lines in the DMR standza and when I configure the bridge using separate copies of MMDVM_Bridge in different folders with two different DVSwitch.ini files, one for each MMDVM_Bridge it appears to work as I hoped.  Here's my problem, after some period of time and in the log files included in this post that time period is approximately 2.5 hours, MMDVM shuts down and I get an error message upon MMDVM restarting automatically stating "cannot bind the UDP address, err 98" and next line states "cannot open listener port 31103".  These same error messages also show up in the log for the XLX MMDVM_Bridge.  I have tried changing the DVSwitch ports 31100 and 31103 to 31600 and 31603, but get the same results after running for some time period.  So my questions are:
1.  Have the updates stated in earlier posts made for MMDVM_Bridge for Raspberry Pi systems been made also to MMDVM_Bridge for amd_64?
2.  If not, will the amd_64 MMDVM_Bridge binary be updated sometime soon?
3.  If they have already been updated, any suggestions on how to fix the above errors from occurring?

Dave

--
Dave WB6DTB

1941 - 1960 of 9151