Welcome to DVSwitch
Purpose
1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
Mission Statement/Position
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
|
Re: Usrp and dvswitch on windows
Billy
The usrp on windows can be used with the dvswitch server, you just need to put in the correct ip address and appropriate details needed. All this information is in the text config file.
But the dvswitch server would need to be on a raspberry pi
|
|
|
|
Re: HBmontorHelp
Bob kc2cwt
Thank for trying to help out .. I am just start all over
KC2CWT Bob Schneider (914)497-5502 Carmel NY 10512
------ Original Message ------
From: "Doug - W4DBG" <douggooden@...>
Sent: 5/15/2022 9:48:12 PM
Subject: Re: [DVSwitch] HBmontorHelp
|
|
|
|
Re: HBmontorHelp
Ok Bob, I was hoping to get you going. Hopefully someone can add some information but I am not sure what road you should go down next. 73
On Sun, May 15, 2022 at 8:45 PM Bob kc2cwt <kc2cwt@...> wrote:
--
Doug Gooden troytrojan@...
|
|
|
|
Re: HBmontorHelp
Bob kc2cwt
Jinja2 2.11.3
KC2CWT Bob Schneider (914)497-5502 Carmel NY 10512
------ Original Message ------
From: "Doug - W4DBG" <douggooden@...>
Sent: 5/15/2022 9:42:07 PM
Subject: Re: [DVSwitch] HBmontorHelp
|
|
|
|
Re: HBmontorHelp
What version of Jinja are you running?
On Sun, May 15, 2022 at 8:39 PM Bob kc2cwt <kc2cwt@...> wrote:
--
Doug Gooden troytrojan@...
|
|
|
|
Re: HBmontorHelp
Bob kc2cwt
i ran it this time from /opt/HBmontor Dir and got this :/opt/HBmonitor# python3 monitor.py
Traceback (most recent call last):
File "monitor.py", line 60, in <module>
from jinja2 import Environment, PackageLoader, select_autoescape
File "/usr/local/lib/python3.7/dist-packages/jinja2/__init__.py", line 12, in <module>
from .environment import Environment
File "/usr/local/lib/python3.7/dist-packages/jinja2/environment.py", line 25, in <module>
from .defaults import BLOCK_END_STRING
File "/usr/local/lib/python3.7/dist-packages/jinja2/defaults.py", line 3, in <module>
from .filters import FILTERS as DEFAULT_FILTERS # noqa: F401
File "/usr/local/lib/python3.7/dist-packages/jinja2/filters.py", line 13, in <module>
from markupsafe import soft_unicode
ImportError: cannot import name 'soft_unicode' from 'markupsafe' (/usr/local/lib/python3.7/dist-packages/markupsafe/__init__.py)
KC2CWT Bob Schneider (914)497-5502 Carmel NY 10512
------ Original Message ------
From: "Doug - W4DBG" <douggooden@...>
Sent: 5/15/2022 9:37:11 PM
Subject: Re: [DVSwitch] HBmontorHelp
|
|
|
|
Re: HBmontorHelp
The ‘monitor.py’ has ‘ around it. Not sure why. Try mv ‘monitor.py’ monitor.py Then python3 monitor.py
On Sun, May 15, 2022 at 8:34 PM Bob kc2cwt <kc2cwt@...> wrote:
--
Doug Gooden troytrojan@...
|
|
|
|
Re: HBmontorHelp
Bob kc2cwt
I get this But its thair ~# python3 monitor.py
python3: can't open file 'monitor.py': [Errno 2] No such file or directory
KC2CWT Bob Schneider (914)497-5502 Carmel NY 10512
------ Original Message ------
From: "Doug - W4DBG" <douggooden@...>
Sent: 5/15/2022 9:32:20 PM
Subject: Re: [DVSwitch] HBmontorHelp
|
|
|
|
Re: HBmontorHelp
Can you run it in the foreground? cd /opt/HBMonitor python3 monitor.py And see what errors you get? Doug W4DBG
On Sun, May 15, 2022 at 8:30 PM Bob kc2cwt <kc2cwt@...> wrote:
--
Doug Gooden troytrojan@...
|
|
|
|
HBmontorHelp
Bob kc2cwt
looking for some help with HBmontor wen i use systemctl start hbmon
I get the err below If some could point out the fail point as i am just not seeing it Thanks . ● hbmon.service - HBMonitor
Loaded: loaded (/lib/systemd/system/hbmon.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-05-15 21:22:43 EDT; 324ms ago
Process: 822 ExecStart=/usr/bin/python3 /opt/HBmonitor/monitor.py (code=exited, status=1/FAILURE)
Main PID: 822 (code=exited, status=1/FAILURE)
KC2CWT Bob Schneider (914)497-5502 Carmel NY 10512
|
|
|
|
Re: What if you could build a AllStar bridge without having to build a AllStar node?
On 16/5/22 5:32 am, Patrick Perdue wrote:
One would presume that if you're running a link, you'd work out such details with the AllStar node owner (unless you ARE the owner, in which case you'd just fix it). :) -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: What if you could build a AllStar bridge without having to build a AllStar node?
On 15/5/22 9:07 pm, Steve N4IRS wrote:
As of today, only ulaw. We are looking at other codec support. I'm notFor me, ulaw is all I need. When running links, I want to use as little compression as possible, because I know audio is likely to hit one of the high compression vocoders (*MBE, Codec2 etc) somewhere in the network. It is unlikely I'd use another codec here. These days, there's few scenarios where you really have to conserve bandwidth - the only one I can think of is a metered Internet connection with a small data cap, which is getting rarer these days. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: What if you could build a AllStar bridge without having to build a AllStar node?
Patrick Perdue
Yeah, I meant "does it matter" in context that currently only ULAW is supported, so there is no codec priority. I have come across some nodes in the wild that only negotiate using G726-AAL2 for some reason. Don't know how prevalent this is over all, though.
On 5/15/2022 7:07 AM, Steve N4IRS
wrote:
As of today, only ulaw. We are looking at other codec support. I'm not sure I understand the "does it matter" Does it matter if it supports other codecs?
|
|
|
|
YSF-N Ref. <-> NXDN Ref.: No continous transmission from YSF to NXDN
#mmdvm_bridge
Stephan DG1BGS
Hi all,
We are currently playing different approaches to bridge our YSF Reflector with our NXDN Reflector. We have a working setup that bridges NXDN to our XLX Server which is also linked to the YSF Reflector. However, we would like to directly bridge the YSF Reflector and NXDN Reflector. This is what our setup looks like (all instances running on the same server):  MMDVM_Bridge.ini [System Fusion] Enable=1 [NXDN] Enable=1 RAN=1 Id=3227 [System Fusion Network] Enable=1 LocalAddress=0 LocalPort=3200 GatewayAddress=127.0.0.1 GatewayPort=42000 Debug=0 [NXDN Network] Enable=1 LocalAddress=127.0.0.1 Debug=0 LocalPort=14021 GatewayAddress=127.0.0.1 GatewayPort=14020 DVSwitch.ini [NXDN] address = 127.0.0.1 txPort = 35103 rxPort = 35100 fallbackID = 262034 nxdnFallbackID = 3227 slot = 2 RemotePort = 6075 [YSF] address = 127.0.0.1 txPort = 35100 rxPort = 35103 txWidePort = 35105 fallbackID = 262034 exportTG = 20421 slot = 2 RemotePort = 6073 What is perfectly working is NXDN to YSF. But when we want to transmit YSF to NXDN, the stream is not continuous. The NXDN side still kes up and shows the callsign, but no audio and all transmissions are being displayed with a duration of 0.5 seconds. This behaviour is also reflected by the MMDVM-Bridge.log: NXDN to YSF (all ok) M: 2022-05-14 00:33:47.677 NXDN, received network transmission from 9V1LH to TG 20421 M: 2022-05-14 00:33:47.682 YSF, TX state = ON I: 2022-05-14 00:33:47.683 YSF, Begin TX: src=5250014 rpt=0 dst=20421 slot=2 cc=0 metadata=9V1LH I: 2022-05-14 00:33:48.013 YSF, Narrow transmit (72 bit) M: 2022-05-14 00:33:51.829 NXDN, network watchdog has expired, 2.2 seconds M: 2022-05-14 00:33:51.829 YSF, TX state = OFF YSF to NXDN (not OK) M: 2022-05-14 00:34:30.864 YSF, received network data from 9V1LH to ALL at 2622-DL I: 2022-05-14 00:34:30.864 YSF, Lookup call 9V1LH returned id 5250014 -> 5250014 M: 2022-05-14 00:34:30.864 NXDN, TX state = ON I: 2022-05-14 00:34:30.864 NXDN, dmrToNxdn by call: 9V1LH I: 2022-05-14 00:34:30.864 NXDN, Begin TX: src=5250014 rpt=0 dst=20421 slot=2 cc=0 metadata=9V1LH I: 2022-05-14 00:34:30.864 NXDN, (5250014, 20421) -> (36135, 20421) M: 2022-05-14 00:34:30.864 NXDN, received RF header from 9V1LH to TG 20421 M: 2022-05-14 00:34:31.241 YSF, received network data from 9V1LH to ALL at 2622-DL I: 2022-05-14 00:34:31.241 YSF, Lookup call 9V1LH returned id 5250014 -> 5250014 M: 2022-05-14 00:34:31.241 NXDN, TX state = ON I: 2022-05-14 00:34:31.242 NXDN, dmrToNxdn by call: 9V1LH I: 2022-05-14 00:34:31.242 NXDN, Begin TX: src=5250014 rpt=0 dst=20421 slot=2 cc=0 metadata=9V1LH I: 2022-05-14 00:34:31.242 NXDN, (5250014, 20421) -> (36135, 20421) M: 2022-05-14 00:34:31.242 NXDN, received RF header from 9V1LH to TG 20421 M: 2022-05-14 00:34:31.348 YSF, received network data from 9V1LH to ALL at 2622-DL I: 2022-05-14 00:34:31.348 YSF, Lookup call 9V1LH returned id 5250014 -> 5250014 M: 2022-05-14 00:34:31.348 NXDN, TX state = ON I: 2022-05-14 00:34:31.348 NXDN, dmrToNxdn by call: 9V1LH I: 2022-05-14 00:34:31.348 NXDN, Begin TX: src=5250014 rpt=0 dst=20421 slot=2 cc=0 metadata=9V1LH I: 2022-05-14 00:34:31.348 NXDN, (5250014, 20421) -> (36135, 20421) M: 2022-05-14 00:34:31.348 NXDN, received RF header from 9V1LH to TG 20421 M: 2022-05-14 00:34:31.407 YSF, received network data from 9V1LH to ALL at 2622-DL I: 2022-05-14 00:34:31.407 YSF, Lookup call 9V1LH returned id 5250014 -> 5250014 [...] M: 2022-05-14 00:34:33.398 NXDN, TX state = ON I: 2022-05-14 00:34:33.398 NXDN, dmrToNxdn by call: 9V1LH I: 2022-05-14 00:34:33.398 NXDN, Begin TX: src=5250014 rpt=0 dst=20421 slot=2 cc=0 metadata=9V1LH I: 2022-05-14 00:34:33.398 NXDN, (5250014, 20421) -> (36135, 20421) M: 2022-05-14 00:34:33.398 NXDN, received RF header from 9V1LH to TG 20421 M: 2022-05-14 00:34:34.888 YSF, received network end of transmission (expired), 0.1 seconds, 0% packet loss, BER: 0.0% M: 2022-05-14 00:34:34.888 NXDN, TX state = OFF M: 2022-05-14 00:34:34.889 NXDN, received RF end of transmission, 0.1 seconds, BER: 0.0% Any help is highly appreciated. vy 73 & 55 de Stephan 9V1LH / DG1BGS
|
|
|
|
Re: What if you could build a AllStar bridge without having to build a AllStar node?
As of today, only ulaw. We are looking at other codec support. I'm
not sure I understand the "does it matter" Does it matter if it
supports other codecs?
toggle quoted messageShow quoted text
On 5/15/22 02:55, Patrick Perdue wrote:
|
|
|
|
Re: What if you could build a AllStar bridge without having to build a AllStar node?
Patrick Perdue
What is the codec priority here? Does it support anything other than ulaw, I.E. SLIN or G726-AAL2? In other words, does it matter?
On 5/14/2022 4:21 PM, Steve N4IRS
wrote:
|
|
|
|
Re: What if you could build a AllStar bridge without having to build a AllStar node?
; IAX_Bridge configuration file.
; This file should be placed in either /etc or it can be
; supplied as a path on the IAX_Bridge command line.
[IAX] ; IAX Bridge configuration section
call = N0CALL ; Node callsign (exported with metadata)
node = 123456 ; This nodes number
regServerAddress = register.allstarlink.org ; URL of the registration server or empty if not wanted
password = 101010 ; ASL node password
startNode = 0 ; Initial node number to tune to
usrpAddress = 127.0.0.1 ; Address of the USRP listener (typically AB or AR)
rXPort = 32001 ; Port to listen on (import)
tXPort = 34001 ; Port to send USRP frames to (export)
iaxPort = 4569 ; port number to listen for IAX connects
statsEnabled = 1 ; Report stats to AllstarLink.org
keyQueryEnabled = 1 ; Issue key query (K?) requests to see who is transmitting
timeoutSeconds = 180 ; Transmission timeout (both directions)
logLevel = 3 ; IAXB log level (1=debug, 5=Errors only)
displayLevel = 1 ; Log level for console output
logFilePath = /var/log/dvswitch/IAX_Bridge.log ; Where to place the log file
[nodes]
; Note, if you are using automatic update for allstar link nodes,
; no allstar link nodes should be defined here. Only place a definition
; for your local nodes, and private (off of allstar link) nodes here.
1999 = radio@....0.1:4570/1999,NONE ; example private node
[MACROS]
; Where the macros are
; xxxx=yyyy
; xxxx is the dial string to match
; yyyy is the command line to execute
; xxxx must be preceded by a *
; xxxx can be any string (alphanumeric)
; yyyy is the command to execute
; yyyy will replace xxxx in the dial string
; arguments follow the macro name with a # delimiter
OnConnect=osascript -e 'display notification "Connected to $@" with title "IAX_Bridge"';say "Connected to $@"
OnDisconnect=osascript -e 'display notification "Disconnected" with title "IAX_Bridge"'
OnTelemetry=osascript -e 'display notification "Telemetry: $@" with title "IAX_Bridge"'
hello=osascript -e 'display notification "hello"'
|
|
|
|
Re: DVSwitch YSF
Steve, I have my YSF working now. Not sure if this was part of the issue or not but I wanted to share for your Situational Awareness. I rebooted my node serval times. Each time is was having problems with YSF, My YSF ASL node was registered to West1-b.allstarlink.org. The last reboot, when the YSF bridge starting working, it registered at central.allstarlink.org.
Maybe nothing; Maybe the answer.
Brett KB5YZB
From: Williams, Brett
Sent: Thursday, May 12, 2022 9:32 AM To: main@DVSwitch.groups.io Subject: RE: [DVSwitch] DVSwitch YSF
Thanks Steve, your knowledge and help is very much appreciated. For my YSF issue, everting looks correct that I can see (as it used to work a few weeks ago). With that, I did the latest HAMVOIP update about 3 weeks ago. Could that have caused any issues with my YSF bridge not connecting ?
Thanks Brett KB5YZB
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Nick via groups.io
Thanks Steve, its back to the drawing board for me... Suggestions welcome.
|
|
|
|
Re: DVSwitch YSF
After a reboot; here is the log file.
I: 2022-05-12 17:58:48.473 MMDVM_Bridge: I: 2022-05-12 17:58:48.473 Portions Copyright (C) 2018, 2019, 2020, 2021 DVSwitch, INAD. I: 2022-05-12 17:58:48.473 Hacks by Mike N4IRR and Steve N4IRS I: 2022-05-12 17:58:48.473 = I: 2022-05-12 17:59:36.275 This software is for use on amateur radio networks only, I: 2022-05-12 17:59:36.275 it is to be used for educational purposes only. Its use on I: 2022-05-12 17:59:36.275 commercial networks is strictly prohibited. I: 2022-05-12 17:59:36.275 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2022-05-12 17:59:36.275 MMDVM_Bridge-20210520_V1.6.8 is starting M: 2022-05-12 17:59:36.275 Built 07:13:59 May 28 2021 (GitID #3cfcf23) I: 2022-05-12 17:59:36.275 General Parameters I: 2022-05-12 17:59:36.275 Callsign: KB5YZB I: 2022-05-12 17:59:36.275 Id: 314152505 I: 2022-05-12 17:59:36.275 Duplex: no I: 2022-05-12 17:59:36.275 Timeout: 180s I: 2022-05-12 17:59:36.275 D-Star: disabled I: 2022-05-12 17:59:36.275 DMR: enabled I: 2022-05-12 17:59:36.275 YSF: enabled I: 2022-05-12 17:59:36.275 P25: disabled I: 2022-05-12 17:59:36.275 NXDN: disabled I: 2022-05-12 17:59:36.275 Modem Parameters I: 2022-05-12 17:59:36.275 Port: /dev/null I: 2022-05-12 17:59:36.275 RX Invert: no I: 2022-05-12 17:59:36.275 TX Invert: no I: 2022-05-12 17:59:36.275 PTT Invert: no I: 2022-05-12 17:59:36.275 TX Delay: 100ms I: 2022-05-12 17:59:36.275 RX Offset: 0Hz I: 2022-05-12 17:59:36.276 TX Offset: 0Hz I: 2022-05-12 17:59:36.276 RX DC Offset: 0 I: 2022-05-12 17:59:36.276 TX DC Offset: 0 I: 2022-05-12 17:59:36.276 RF Level: 100.0% I: 2022-05-12 17:59:36.276 DMR Delay: 0 (0.0ms) I: 2022-05-12 17:59:36.276 RX Level: 50.0% I: 2022-05-12 17:59:36.276 CW Id TX Level: 50.0% I: 2022-05-12 17:59:36.276 D-Star TX Level: 50.0% I: 2022-05-12 17:59:36.276 DMR TX Level: 50.0% I: 2022-05-12 17:59:36.276 YSF TX Level: 50.0% I: 2022-05-12 17:59:36.276 P25 TX Level: 50.0% I: 2022-05-12 17:59:36.276 NXDN TX Level: 50.0% I: 2022-05-12 17:59:36.276 RX Frequency: 447Hz (447Hz) I: 2022-05-12 17:59:36.276 TX Frequency: 442Hz (442Hz) M: 2022-05-12 17:59:36.276 Opening the MMDVM I: 2022-05-12 17:59:36.276 Display Parameters I: 2022-05-12 17:59:36.276 Type: I: 2022-05-12 17:59:36.276 DMR Network Parameters I: 2022-05-12 17:59:36.276 Address: 3103.repeater.net I: 2022-05-12 17:59:36.276 Port: 62031 I: 2022-05-12 17:59:36.276 Local: 62032 I: 2022-05-12 17:59:36.276 Jitter: 360ms I: 2022-05-12 17:59:36.276 Slot 1: disabled I: 2022-05-12 17:59:36.276 Slot 2: enabled I: 2022-05-12 17:59:36.276 Mode Hang: 3s I: 2022-05-12 17:59:36.302 Info Parameters I: 2022-05-12 17:59:36.302 Callsign: KB5YZB I: 2022-05-12 17:59:36.302 RX Frequency: 447Hz I: 2022-05-12 17:59:36.302 TX Frequency: 447Hz I: 2022-05-12 17:59:36.302 Power: 20W I: 2022-05-12 17:59:36.302 Latitude: 39.695343deg N I: 2022-05-12 17:59:36.302 Longitude: -104.703728deg E I: 2022-05-12 17:59:36.302 Height: 30m I: 2022-05-12 17:59:36.302 Location: "Aurora, Co" I: 2022-05-12 17:59:36.302 Description: "MMDVM_Bridge" I: 2022-05-12 17:59:36.302 URL: "https://groups.io/g/DVSwitch" M: 2022-05-12 17:59:36.302 DMR, Opening DMR Network I: 2022-05-12 17:59:36.302 System Fusion Network Parameters I: 2022-05-12 17:59:36.302 Local Address: 127.0.0.1 I: 2022-05-12 17:59:36.302 Local Port: 3200 I: 2022-05-12 17:59:36.302 Gateway Address: 127.0.0.1 I: 2022-05-12 17:59:36.302 Gateway Port: 4200 I: 2022-05-12 17:59:36.302 Mode Hang: 3s M: 2022-05-12 17:59:36.302 Opening YSF network connection I: 2022-05-12 17:59:36.302 RSSI I: 2022-05-12 17:59:36.302 Mapping File: /dev/null I: 2022-05-12 17:59:36.302 Loaded 0 RSSI data mapping points from /dev/null I: 2022-05-12 17:59:36.302 DMR Id Lookups I: 2022-05-12 17:59:36.302 File: /opt/DMRIds.dat I: 2022-05-12 17:59:36.302 Reload: 24 hours I: 2022-05-12 17:59:36.303 Loaded 1 Ids to the DMR callsign lookup table I: 2022-05-12 17:59:36.303 DMR RF Parameters I: 2022-05-12 17:59:36.303 Started the DMR Id lookup reload thread I: 2022-05-12 17:59:36.303 Id: 314152505 I: 2022-05-12 17:59:36.303 Color Code: 1 I: 2022-05-12 17:59:36.303 Self Only: no I: 2022-05-12 17:59:36.303 Embedded LC Only: yes I: 2022-05-12 17:59:36.303 Dump Talker Alias Data: no I: 2022-05-12 17:59:36.303 Prefixes: 0 I: 2022-05-12 17:59:36.303 Call Hang: 3s I: 2022-05-12 17:59:36.303 TX Hang: 3s I: 2022-05-12 17:59:36.303 Mode Hang: 10s M: 2022-05-12 17:59:36.303 DMR, Opening INI file: DVSwitch.ini M: 2022-05-12 17:59:36.303 DMR, Setting [DMR] address -> 127.0.0.1 M: 2022-05-12 17:59:36.304 DMR, Setting [DMR] txPort -> 31100 M: 2022-05-12 17:59:36.304 DMR, Setting [DMR] rxPort -> 31103 M: 2022-05-12 17:59:36.304 DMR, Setting [DMR] slot -> 2 M: 2022-05-12 17:59:36.304 DMR, Setting [DMR] exportTG -> 0 M: 2022-05-12 17:59:36.304 DMR, Setting [DMR] hangTimerInFrames -> 0 M: 2022-05-12 17:59:36.304 DMR, Setting [DMR] talkerAlias -> %callsign %location %description M: 2022-05-12 17:59:36.304 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103. Result = 1 I: 2022-05-12 17:59:36.304 YSF RF Parameters I: 2022-05-12 17:59:36.304 Low Deviation: no I: 2022-05-12 17:59:36.304 Remote Gateway: no I: 2022-05-12 17:59:36.304 Self Only: no I: 2022-05-12 17:59:36.304 DSQ: no I: 2022-05-12 17:59:36.304 Mode Hang: 10s M: 2022-05-12 17:59:36.304 YSF, Opening INI file: DVSwitch.ini M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] address -> 127.0.0.1 M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] txPort -> 41100 M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] rxPort -> 41103 M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] txWidePort -> 35105 M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] fallbackID -> 3141525 M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] exportTG -> 9 M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] slot -> 2 M: 2022-05-12 17:59:36.304 YSF, Setting [YSF] RemotePort -> 6073 M: 2022-05-12 17:59:36.305 YSF, Transmitting on 127.0.0.1:41100, and listening on port 41103. Result = 1 M: 2022-05-12 17:59:36.305 MMDVM_Bridge-20210520_V1.6.8 is running M: 2022-05-12 17:59:46.432 DMR, Logged into the master successfully: 3103.repeater.net:62031 M: 2022-05-12 17:59:56.470 YSF, TX state = ON I: 2022-05-12 17:59:56.470 YSF, Begin TX: src=3141525 rpt=314152569 dst=9 slot=1 cc=1 metadata=KB5YZB I: 2022-05-12 17:59:56.568 YSF, Narrow transmit (72 bit) M: 2022-05-12 18:00:00.185 YSF, TX state = OFF
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Thursday, May 12, 2022 10:26 AM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] DVSwitch YSF
Check the logs when you try to connect. /var/log/mmdvm
From: Brett KB5YZB via groups.io
Thanks Steve, your knowledge and help is very much appreciated. For my YSF issue, everting looks correct that I can see (as it used to work a few weeks ago). With that, I did the latest HAMVOIP update about 3 weeks ago. Could that have caused any issues with my YSF bridge not connecting ?
Thanks Brett KB5YZB
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Nick via groups.io
Thanks Steve, its back to the drawing board for me... Suggestions welcome.
|
|
|
|
Re: DVSwitch YSF
Check the logs when you try to connect. /var/log/mmdvm
From: Brett KB5YZB via groups.io
Sent: Thursday, May 12, 2022 11:32 AM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] DVSwitch YSF
Thanks Steve, your knowledge and help is very much appreciated. For my YSF issue, everting looks correct that I can see (as it used to work a few weeks ago). With that, I did the latest HAMVOIP update about 3 weeks ago. Could that have caused any issues with my YSF bridge not connecting ?
Thanks Brett KB5YZB
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Nick via groups.io
Thanks Steve, its back to the drawing board for me... Suggestions welcome.
|
|
|