1. main@DVSwitch.groups.io
  2. Messages
   Date   
Re: Configuring DVSwitch Mobile to access own AllStarLink node

Steve N4IRS
 

<https://dvswitch.groups.io/g/Mobile/wiki/8719>

On 11/19/2020 1:12 PM, lcm@... wrote:
I have my own AllStarLink node and I would like to use DVSwitch Mobile on Android to access it.  It seems like this is a very powerful Android app but I can't seem to find documentation to do this. Is there a step-by-step document somewhere?  I just need to know what to change on the node and how to configure the mobile app to match.

Configuring DVSwitch Mobile to access own AllStarLink node

Levi C. Maaia
 

I have my own AllStarLink node and I would like to use DVSwitch Mobile on Android to access it.  It seems like this is a very powerful Android app but I can't seem to find documentation to do this. Is there a step-by-step document somewhere?  I just need to know what to change on the node and how to configure the mobile app to match.
Re: os for Raspberry Pi

thlongan@...
 

Thank you



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Doug - W4DBG <douggooden@...>
Date: 11/18/20 10:21 PM (GMT-05:00)
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] os for Raspberry Pi




On Wed, Nov 18, 2020 at 8:50 PM thlongan via groups.io <thlongan=ptd.net@groups.io> wrote:
I am ready to try my luck and build a DMR to YSF server. I plan on using a Raspberry Pi 3 B+. What Operating System should I use and where should I download it?

--
Doug Gooden
troytrojan@...
Re: ASL to DMR - not receiving inbound traffic

Brad N8PC
 

did you set the talk group on brandmeister as static? if not it will not stay connected.

On 11/18/2020 3:55 PM, Gerry Filby wrote:
Thanks for the response Brad !

I tried that and it stopped working altogether.  I looked in /opt/MMDV_Bridge/DVSwitch.ini and TX/RX are defined:

[DMR]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 31100                  ; Port to send AMBE TLV frames to (export)

RXPort = 31103                  ; Port to listen on (import)

Slot = 2                        ; Export slot

ExportTG = 0                    ; Which TG to export

TalkerAlias = Roger Nowhere Il. DVSWITCH


So I'm assuming that needs to be reversed in Analog_Bridge.ini ? - Tx goes to Rx and visa versa:

[AMBE_AUDIO]

address = 127.0.0.1                     ; IP address of xx_Bridge

txPort = 31103                          ; Transmit TLV frames to partner on this port

rxPort = 31100                          ; Listen for TLV frames from partner on this port

ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)

minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)


I'm getting traffic from the TG 91, but only if I momentarily click my PTT on the analog side whilst a 3rd party is speaking in the TG.  If the 3rd party in the TG stops an restarts their over, I don't resume receiving their traffic from the TG.

g
Re: Coming to a browser near you

jacomms
 

😊

 

Justin Albury

J Albury Communications

justin@...

0417246791

VK2JUZ

-----------------------------------------------------------------

This email, and any attachments are for the use of the intended

recipient(s) and may contain confidential/privileged information.

If you have received this email in error, please notify the sender

immediately and then delete it. If you are not the intended recipient,

you must not copy, disclose or distribute its contents to any other

person. We do not accept any liability in connection with transmitting,

unauthorised access to, or viruses in this email and its attachments.

This notice should not be removed.

----------------------------------------------------------------------------------

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Thursday, 19 November 2020 3:33 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Coming to a browser near you

 

In the discussion of a issue with radioid.net missing some entries this weekend I posted a screenshot of a work in progress. So, since the cat is out of the bag...
This is a work in progress of the new web (HTML) client. We have no release date and the program has not even gone into beta test yet.
I'll post update info here when available.
Re: os for Raspberry Pi

VE3SP.com Andre
 

Thanks
I hope to setup on a pi also. Wht are the best directions
--
73s,   Warmest wishes to you and blessings to your family.
Andre 
Toronto, CANADA
website VE3SP.com

VE3SP.com 
Re: os for Raspberry Pi

Doug - W4DBG
 




On Wed, Nov 18, 2020 at 8:50 PM thlongan via groups.io <thlongan=ptd.net@groups.io> wrote:
I am ready to try my luck and build a DMR to YSF server. I plan on using a Raspberry Pi 3 B+. What Operating System should I use and where should I download it?

--
Doug Gooden
troytrojan@...
os for Raspberry Pi

thlongan@...
 

I am ready to try my luck and build a DMR to YSF server. I plan on using a Raspberry Pi 3 B+. What Operating System should I use and where should I download it?
Re: ASL to DMR - not receiving inbound traffic

Gerry Filby
 

Thanks for the response Brad !

I tried that and it stopped working altogether.  I looked in /opt/MMDV_Bridge/DVSwitch.ini and TX/RX are defined:

[DMR]

Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)

TXPort = 31100                  ; Port to send AMBE TLV frames to (export)

RXPort = 31103                  ; Port to listen on (import)

Slot = 2                        ; Export slot

ExportTG = 0                    ; Which TG to export

TalkerAlias = Roger Nowhere Il. DVSWITCH


So I'm assuming that needs to be reversed in Analog_Bridge.ini ? - Tx goes to Rx and visa versa:

[AMBE_AUDIO]

address = 127.0.0.1                     ; IP address of xx_Bridge

txPort = 31103                          ; Transmit TLV frames to partner on this port

rxPort = 31100                          ; Listen for TLV frames from partner on this port

ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)

minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)


I'm getting traffic from the TG 91, but only if I momentarily click my PTT on the analog side whilst a 3rd party is speaking in the TG.  If the 3rd party in the TG stops an restarts their over, I don't resume receiving their traffic from the TG.

g
Coming to a browser near you

Steve N4IRS
 

In the discussion of a issue with radioid.net missing some entries this weekend I posted a screenshot of a work in progress. So, since the cat is out of the bag...
This is a work in progress of the new web (HTML) client. We have no release date and the program has not even gone into beta test yet.
I'll post update info here when available.
Re: Dashboard for multiple instances in DVSwitch

kpappa@...
 
Edited

Problem solved.

I followed this great article : https://n2rac.com/dmr-digital-amateur-radio-setup-several-instances-dvswitch-server-3694caaf6bf1

Then : 

# cp /opt/Web_Proxy/ /opt/Web_Proxy2/ -r

 

# cp /lib/systemd/system/webproxy.service /lib/systemd/system/webproxy2.service

# nano /opt/Analog_Bridge2/Analog_Bridge.ini
and change the following : 
[GENERAL]
pcmPort = 2223
    
# nano /lib/systemd/system/webproxy2.service
and change the following :  
WorkingDirectory=/opt/Web_Proxy2
ExecStart=/usr/bin/node /opt/Web_Proxy2/proxy.js 8081 2223
    

# nano /opt/Web_Proxy2/proxy.js
and change the following :   
var wsPort = 8081,
    pcmPort = 2223;

# systemctl enable webproxy2
# systemctl start webproxy2
# systemctl status webproxy2  

Τhe above procedure ensures that RX-Monitor audio for the second instance will be independent from first instance.
Then
# cp /var/www/html/index.php /var/www/html/index2.php
#cp /var/www/html/include/browserdetect.php /var/www/html/include/browserdetect2.php
#cp /var/www/html/include/config.php /var/www/html/include/config2.php
#cp /var/www/html/include/config.php /var/www/html/include/config2.php
#cp /var/www/html/include/functions.php /var/www/html/include/functions2.php
#cp /var/www/html/include/lh.php /var/www/html/include/lh2.php
#cp /var/www/html/include/localtx.php /var/www/html/include/localtx2.php
#cp /var/www/html/include/status.php /var/www/html/include/status2.php
#cp /var/www/html/include/system.php /var/www/html/include/system2.php
#cp /var/www/html/include/tools.php /var/www/html/include/tools2.php

 

And edit recursively all "version 2" .php files (starting from index2.php) to point at second instance's locations and also all .php files references to "version 2" .php
I believe you got the point.
Second Dashboard is accessible as http://<IP-Address>/index2.php

 
Re: ASL to DMR - not receiving inbound traffic

Brad N8PC
 

Gerry in your Analog_bridge.ini under Ambe_Audio set your ports to tx=31100 Rx=31103 then it will work

On 11/17/2020 7:13 PM, Gerry Filby wrote:
Hi Folks,

I've worked through the "ASL to DMR Bridge How To" pdf and I think I have things more or less set up - I get the expected CLI output when running MMDVM_Bridge and Analog_Bridge in the foreground per the doc.

I'm connecting to TG 91 (Worlwide) in Analog_bridge.ini thusly:

[AMBE_AUDIO]

address = 127.0.0.1                     ; IP address of xx_Bridge

txPort = 31103                          ; Transmit TLV frames to partner on this port

rxPort = 31100                          ; Listen for TLV frames from partner on this port

ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this f$

minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)

 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes

gatewayDmrId = 310307899                        ; ID to use when transmitting from Analog_Bridge

repeaterID = 310307801                          ; ID of source repeater

txTg = 91                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge

txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge

colorCode = 1

I'm monitoring the TG from a separate Pi-Star hotspot's dashboard.  When there's an ongoing transmission from a 3rd party and I hit the PTT on my analog radio and release, the connection starts up and I hear 3rd party on my analog radio listening on the ASL side.  However, if the 3rd party stops transmitting and a second 3rd party begins transmitting I don't hear their transmission until I hit the PTT momentarily on my analog radio again.  Also, when I hit the PTT on my analog radio I don't see the traffic pop up on the Pi-Star dashboard.

I'm a total newb at this so just hoping for a pointer as to where to start looking.

Best,
Gerry.
W6WNG
DVSwitch running on RPI 3 A+

Richard Clemens
 

Working fine, just had to try!

Rich
User guide page 3

Richard Clemens
 

Great guide! Suggest a bit of clarity on wireless setup would be useful. Two separate sections on page 3 would help and methods 2and3 don’t seem to apply anymore.

rich
ASL to DMR - not receiving inbound traffic

Gerry Filby
 

Hi Folks,

I've worked through the "ASL to DMR Bridge How To" pdf and I think I have things more or less set up - I get the expected CLI output when running MMDVM_Bridge and Analog_Bridge in the foreground per the doc.

I'm connecting to TG 91 (Worlwide) in Analog_bridge.ini thusly:

[AMBE_AUDIO]

address = 127.0.0.1                     ; IP address of xx_Bridge

txPort = 31103                          ; Transmit TLV frames to partner on this port

rxPort = 31100                          ; Listen for TLV frames from partner on this port

ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this f$

minTxTimeMS = 2500                      ; Minimum time in MS for hang delay (0-10000)

 

; The metadata below is used when ASL is the source since it does not have any concept of digital modes

gatewayDmrId = 310307899                        ; ID to use when transmitting from Analog_Bridge

repeaterID = 310307801                          ; ID of source repeater

txTg = 91                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge

txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge

colorCode = 1

I'm monitoring the TG from a separate Pi-Star hotspot's dashboard.  When there's an ongoing transmission from a 3rd party and I hit the PTT on my analog radio and release, the connection starts up and I hear 3rd party on my analog radio listening on the ASL side.  However, if the 3rd party stops transmitting and a second 3rd party begins transmitting I don't hear their transmission until I hit the PTT momentarily on my analog radio again.  Also, when I hit the PTT on my analog radio I don't see the traffic pop up on the Pi-Star dashboard.

I'm a total newb at this so just hoping for a pointer as to where to start looking.

Best,
Gerry.
W6WNG
Re: Will DVSwitch support my Raspberry Pi 3B+ 3.5" 320x480 TFT Touch Screen

Steve N4IRS
 

Depends on what you want to do. Tell us more.

Steve N4IRS

On 11/17/2020 3:48 PM, KM4GCY@... wrote:
I build my Raspberry Pi 3 with a 3.5" 320x480 TFT Touch Screen in hopes to find an image that would support it, is DWSwitch a good solution?

Will DVSwitch support my Raspberry Pi 3B+ 3.5" 320x480 TFT Touch Screen

KM4GCY@...
 

I build my Raspberry Pi 3 with a 3.5" 320x480 TFT Touch Screen in hopes to find an image that would support it, is DWSwitch a good solution?
Dashboard for multiple instances in DVSwitch

kpappa@...
 

I have installed two functional instances on my Raspberry PI, but so far I managed to have Dashboard only for the first instance.

Any idea or anyone have implemented such a similar task ?
Re: M17 to ASL

Skyler Fennell
 

Sorry Steve (kc1awv) for bad mouthing the mode, sometimes I forget the filter, and think its a really cool project and am willing to help where I can to improve on it.

I’m guilty of it too but a lot of us take all this free open source software for granted.

Skyler 

On Mon, Nov 16, 2020 at 7:09 AM Steve N4IRS <szingman@...> wrote:

[Edited Message Follows]

No We will cross that bridge when we come to it.

On 11/15/20 11:01 AM, Skyler Fennell wrote:
Is there a solution to bridge M17 to ASL?
Re: M17 to ASL

Skyler Fennell
 

Thank you Steve, I really appreciate your work! 



On Mon, Nov 16, 2020 at 6:31 AM Steve KC1AWV <smiller+groups@...> wrote:
Skyler,

I'm sorry that your experience with M17 hasn't been as stellar as some may expect. Please, understand that the protocol is still very much in its infancy, and there are many people working on the protocol to improve it.

As of now, there are no plans by the M17 Working Group on implementing any sort of cross-mode / cross-protocol capability, as the protocol is still not finished. There are several projects working on doing so, but again these are all very much in an 'alpha' stage. If you would like to participate or know more about the progress, you may visit the website or join us on our chat channels to further the discussion there.

Thanks!

Steve KC1AWV

2301 - 2320 of 9775