Date   

Re: DMR Master Disconnects

Steve N4IRS
 

John,
As a start, Please show the [DMR] and [DMR Network] stanzas from MMDVM_Bridge.ini

Steve N4IRS

On 7/24/2019 12:28 PM, John - WB5NFC wrote:
I'm making a first run at installing ASL to DMR Bridge on a Rpi 3B+ with the latest ASL image. Install proceedes normally until I run MMDVM_Bridge in the foreground. First logon to the master server is good, but I get disconnected after about a minute. Then the cycle of connects and disconnects continues thereafter. Can someone point me in the right direction for determining the source of this behavior? Thanks in advance! John / WB5NFC

M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] TXPort -> 31100
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] RXPort -> 31103
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Slot -> 2
M: 2019-07-21 21:20:58.069 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-07-21 21:20:58.069 MMDVM_Bridge-20180423 is running
D: 2019-07-21 21:21:08.163 DMR, Sending authorisation
D: 2019-07-21 21:21:08.260 DMR, Sending configuration
M: 2019-07-21 21:21:08.363 DMR, Logged into the master successfully
W: 2019-07-21 21:22:08.475 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:23:08.480 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:23:08.480 DMR, Closing DMR Network
M: 2019-07-21 21:23:08.480 DMR, Opening DMR Network
D: 2019-07-21 21:23:18.587 DMR, Sending authorisation
D: 2019-07-21 21:23:18.685 DMR, Sending configuration
M: 2019-07-21 21:23:18.782 DMR, Logged into the master successfully
W: 2019-07-21 21:24:18.892 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:25:18.894 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:25:18.895 DMR, Closing DMR Network
M: 2019-07-21 21:25:18.895 DMR, Opening DMR Network
D: 2019-07-21 21:25:28.987 DMR, Sending authorisation
D: 2019-07-21 21:25:29.084 DMR, Sending configuration
M: 2019-07-21 21:25:29.181 DMR, Logged into the master successfully


DMR Master Disconnects

John - WB5NFC <wb5nfc@...>
 

I'm making a first run at installing ASL to DMR Bridge on a Rpi 3B+ with the latest ASL image. Install proceedes normally until I run MMDVM_Bridge in the foreground. First logon to the master server is good, but I get disconnected after about a minute. Then the cycle of connects and disconnects continues thereafter. Can someone point me in the right direction for determining the source of this behavior? Thanks in advance! John / WB5NFC

M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] TXPort -> 31100
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] RXPort -> 31103
M: 2019-07-21 21:20:58.069 DMR, Setting [DMR] Slot -> 2
M: 2019-07-21 21:20:58.069 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
M: 2019-07-21 21:20:58.069 MMDVM_Bridge-20180423 is running
D: 2019-07-21 21:21:08.163 DMR, Sending authorisation
D: 2019-07-21 21:21:08.260 DMR, Sending configuration
M: 2019-07-21 21:21:08.363 DMR, Logged into the master successfully
W: 2019-07-21 21:22:08.475 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:23:08.480 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:23:08.480 DMR, Closing DMR Network
M: 2019-07-21 21:23:08.480 DMR, Opening DMR Network
D: 2019-07-21 21:23:18.587 DMR, Sending authorisation
D: 2019-07-21 21:23:18.685 DMR, Sending configuration
M: 2019-07-21 21:23:18.782 DMR, Logged into the master successfully
W: 2019-07-21 21:24:18.892 DMR, Login to the master has failed, retrying login ...
E: 2019-07-21 21:25:18.894 DMR, Connection to the master has timed out, retrying connection
M: 2019-07-21 21:25:18.895 DMR, Closing DMR Network
M: 2019-07-21 21:25:18.895 DMR, Opening DMR Network
D: 2019-07-21 21:25:28.987 DMR, Sending authorisation
D: 2019-07-21 21:25:29.084 DMR, Sending configuration
M: 2019-07-21 21:25:29.181 DMR, Logged into the master successfully


Re: Can work audio from Mic In or Inline Sound for USRPAudio.py with vox control and convert to DMR?

EA5GVK Joaquin
 

Great new. Many thanks


El mar., 23 jul. 2019 a las 23:19, Steve N4IRS (<szingman@...>) escribió:
We have something in the works. It will be a little while....

On 7/23/19 5:13 PM, EA5GVK Joaquin wrote:
Show can do?
Many thx


Re: About mode YSFN in dvswicht mobile.

Mike Zingman - N4IRR
 

You can add the ip:port to your macro menu. 
It will work just fine till I do the database upload changes. 


Re: Can work audio from Mic In or Inline Sound for USRPAudio.py with vox control and convert to DMR?

Steve N4IRS
 

We have something in the works. It will be a little while....

On 7/23/19 5:13 PM, EA5GVK Joaquin wrote:
Show can do?
Many thx


Re: Can work audio from Mic In or Inline Sound for USRPAudio.py with vox control and convert to DMR?

EA5GVK Joaquin
 

Show can do?
Many thx


Re: About mode YSFN in dvswicht mobile.

EA5GVK Joaquin
 

Perfect. Many thx. Congratulations.
Great Applications
Always grateful

El mar., 23 jul. 2019 a las 19:46, Steve N4IRS (<szingman@...>) escribió:
Yes it is required for D-Star

On 7/23/2019 1:45 PM, EA5GVK Joaquin wrote:
Other Question.
For Dstar necessary is install ircddbgateway?
Many THX.


Re: About mode YSFN in dvswicht mobile.

Steve N4IRS
 

Yes it is required for D-Star

On 7/23/2019 1:45 PM, EA5GVK Joaquin wrote:
Other Question.
For Dstar necessary is install ircddbgateway?
Many THX.


Re: About mode YSFN in dvswicht mobile.

EA5GVK Joaquin
 

Other Question.
For Dstar necessary is install ircddbgateway?
Many THX.


Re: About mode YSFN in dvswicht mobile.

EA5GVK Joaquin
 

Nothing, Steve, Sorry.
Perfect working YSFN with DVSwicthmobile without YSFGateway.

Waiting and wishing, that DVSM update, to be able to automatically and manually update more YSF reflectors.
Thank you so much.


Re: About mode YSFN in dvswicht mobile.

Steve N4IRS
 

What is blocking?

On 7/23/2019 1:18 PM, EA5GVK Joaquin wrote:
On Tue, Jul 23, 2019 at 10:08 AM, Steve N4IRS wrote:
As of now, you can not update the list. This will change in later versions of DVSM.
OK understood. Thank you.
And because I get this blocking log.

I: 2019-07-23 17:17:55.440 YSF, TAG_SET_INFO: src=2145016 rpt=214501676 dst=0 slot=2 cc=1 metadata=2145016
M: 2019-07-23 17:17:55.440 YSF, Remote CMD: txTg=52.3.47.55:42000
M: 2019-07-23 17:17:55.440 Closing YSF network connection
M: 2019-07-23 17:17:55.440 Opening YSF network connection
M: 2019-07-23 17:18:00.611 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:00.611 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:02.510 YSF, received network end of transmission, 2.0 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:02.713 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:02.713 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:08.909 YSF, received network end of transmission, 6.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:09.006 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:09.006 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:09.107 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:09.209 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:09.209 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:10.311 YSF, received network end of transmission, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:10.412 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:10.412 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:10.605 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:10.707 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:10.707 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:11.007 YSF, received network end of transmission, 0.4 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:11.103 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:11.103 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:11.306 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:11.408 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:11.408 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:12.306 YSF, received network end of transmission, 1.0 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:12.407 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:12.407 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:13.402 YSF, received network end of transmission, 1.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:15.802 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:15.802 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
I: 2019-07-23 17:18:16.163 YSF, TAG_SET_INFO: src=2145016 rpt=214501676 dst=0 slot=2 cc=1 metadata=2145016
M: 2019-07-23 17:18:16.204 YSF, received network end of transmission, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:16.300 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:16.300 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:16.305 YSF, Remote CMD: txTg=disconnect


Re: About mode YSFN in dvswicht mobile.

EA5GVK Joaquin
 

On Tue, Jul 23, 2019 at 10:08 AM, Steve N4IRS wrote:
As of now, you can not update the list. This will change in later versions of DVSM.
OK understood. Thank you.
And because I get this blocking log.

I: 2019-07-23 17:17:55.440 YSF, TAG_SET_INFO: src=2145016 rpt=214501676 dst=0 slot=2 cc=1 metadata=2145016
M: 2019-07-23 17:17:55.440 YSF, Remote CMD: txTg=52.3.47.55:42000
M: 2019-07-23 17:17:55.440 Closing YSF network connection
M: 2019-07-23 17:17:55.440 Opening YSF network connection
M: 2019-07-23 17:18:00.611 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:00.611 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:02.510 YSF, received network end of transmission, 2.0 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:02.713 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:02.713 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:08.909 YSF, received network end of transmission, 6.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:09.006 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:09.006 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:09.107 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:09.209 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:09.209 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:10.311 YSF, received network end of transmission, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:10.412 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:10.412 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:10.605 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:10.707 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:10.707 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:11.007 YSF, received network end of transmission, 0.4 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:11.103 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:11.103 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:11.306 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:11.408 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:11.408 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:12.306 YSF, received network end of transmission, 1.0 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:12.407 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:12.407 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:13.402 YSF, received network end of transmission, 1.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:15.802 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:15.802 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
I: 2019-07-23 17:18:16.163 YSF, TAG_SET_INFO: src=2145016 rpt=214501676 dst=0 slot=2 cc=1 metadata=2145016
M: 2019-07-23 17:18:16.204 YSF, received network end of transmission, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:18:16.300 YSF, received network data from KF4ML/DICK to ALL        at NC4CL    
I: 2019-07-23 17:18:16.300 YSF, Lookup call KF4ML returned id 3159061 -> 3159061
M: 2019-07-23 17:18:16.305 YSF, Remote CMD: txTg=disconnect


Re: About mode YSFN in dvswicht mobile.

Steve N4IRS
 

As of now, you can not update the list. This will change in later versions of DVSM.

On 7/23/2019 1:06 PM, EA5GVK Joaquin wrote:
Ok, perfect.
How can update reflectors YSF?
Any IP old.
Also please, show my log the mmdvm_bridge
I: 2019-07-23 17:04:12.733 YSF, TAG_SET_INFO: src=2145016 rpt=214501676 dst=207 slot=2 cc=1 metadata=2145016
M: 2019-07-23 17:04:12.733 YSF, Remote CMD: txTg=52.3.47.55:42000
M: 2019-07-23 17:04:12.733 Closing YSF network connection
M: 2019-07-23 17:04:12.733 Opening YSF network connection
M: 2019-07-23 17:04:17.915 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:17.915 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:25.817 YSF, received network end of transmission, 8.0 seconds, 0% packet loss, BER: 7.6%
M: 2019-07-23 17:04:25.914 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:25.914 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:26.016 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:26.112 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:26.112 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:26.716 YSF, received network end of transmission, 0.7 seconds, 0% packet loss, BER: 8.5%
M: 2019-07-23 17:04:26.813 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:26.813 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:27.016 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 7.9%
M: 2019-07-23 17:04:27.118 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:27.118 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:27.412 YSF, received network end of transmission, 0.4 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:27.514 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:27.514 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:27.611 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:27.717 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:27.717 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:28.316 YSF, received network end of transmission, 0.7 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:28.413 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:28.413 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:28.515 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:28.617 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:28.617 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:29.013 YSF, received network end of transmission, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:29.312 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:29.312 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:29.512 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:29.710 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:29.710 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:30.213 YSF, received network end of transmission, 0.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:35.515 YSF, received network data from ********** to ********** at NC4CL    
I: 2019-07-23 17:04:35.515 YSF, Lookup call  returned id 0 -> 3113042
M: 2019-07-23 17:04:37.917 YSF, received network end of transmission, 2.5 seconds, 0% packet loss, BER: 7.6%
M: 2019-07-23 17:04:38.019 YSF, received network data from ********** to ALL        at NC4CL    
I: 2019-07-23 17:04:38.019 YSF, Lookup call  returned id 0 -> 3113042
M: 2019-07-23 17:04:38.222 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 8.6%
M: 2019-07-23 17:04:38.318 YSF, received network data from ********** to ALL        at NC4CL    
I: 2019-07-23 17:04:38.318 YSF, Lookup call  returned id 0 -> 3113042


Re: About mode YSFN in dvswicht mobile.

EA5GVK Joaquin
 

Ok, perfect.
How can update reflectors YSF?
Any IP old.
Also please, show my log the mmdvm_bridge
I: 2019-07-23 17:04:12.733 YSF, TAG_SET_INFO: src=2145016 rpt=214501676 dst=207 slot=2 cc=1 metadata=2145016
M: 2019-07-23 17:04:12.733 YSF, Remote CMD: txTg=52.3.47.55:42000
M: 2019-07-23 17:04:12.733 Closing YSF network connection
M: 2019-07-23 17:04:12.733 Opening YSF network connection
M: 2019-07-23 17:04:17.915 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:17.915 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:25.817 YSF, received network end of transmission, 8.0 seconds, 0% packet loss, BER: 7.6%
M: 2019-07-23 17:04:25.914 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:25.914 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:26.016 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:26.112 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:26.112 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:26.716 YSF, received network end of transmission, 0.7 seconds, 0% packet loss, BER: 8.5%
M: 2019-07-23 17:04:26.813 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:26.813 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:27.016 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 7.9%
M: 2019-07-23 17:04:27.118 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:27.118 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:27.412 YSF, received network end of transmission, 0.4 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:27.514 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:27.514 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:27.611 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:27.717 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:27.717 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:28.316 YSF, received network end of transmission, 0.7 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:28.413 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:28.413 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:28.515 YSF, received network end of transmission, 0.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:28.617 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:28.617 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:29.013 YSF, received network end of transmission, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:29.312 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:29.312 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:29.512 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:29.710 YSF, received network data from KJ4ZEF     to ALL        at NC4CL    
I: 2019-07-23 17:04:29.710 YSF, Lookup call KJ4ZEF returned id 1137098 -> 1137098
M: 2019-07-23 17:04:30.213 YSF, received network end of transmission, 0.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-07-23 17:04:35.515 YSF, received network data from ********** to ********** at NC4CL    
I: 2019-07-23 17:04:35.515 YSF, Lookup call  returned id 0 -> 3113042
M: 2019-07-23 17:04:37.917 YSF, received network end of transmission, 2.5 seconds, 0% packet loss, BER: 7.6%
M: 2019-07-23 17:04:38.019 YSF, received network data from ********** to ALL        at NC4CL    
I: 2019-07-23 17:04:38.019 YSF, Lookup call  returned id 0 -> 3113042
M: 2019-07-23 17:04:38.222 YSF, received network end of transmission, 0.3 seconds, 0% packet loss, BER: 8.6%
M: 2019-07-23 17:04:38.318 YSF, received network data from ********** to ALL        at NC4CL    
I: 2019-07-23 17:04:38.318 YSF, Lookup call  returned id 0 -> 3113042


Re: About mode YSFN in dvswicht mobile.

Steve N4IRS
 

MMDVM_Bridge does not use YSFGateway. The GatewayAddress and GatewayPort will define what you connect to on startup. To connect to a reflector after DVSM, AB and MB are started put the IP:port or FQDN:port in a macro. DVSM includes a list of reflectors also.

Steve N4IRS

On 7/23/2019 12:56 PM, EA5GVK Joaquin wrote:
I am testing the different modes of the dvswitch mobile. in DMR and NXDN so far all right and fabulous applications.
Now I am testing with YSFN (fusion) mode.
I want to ask two questions.
Should the YSFGateway work too?

If I do not configure the YSFGateway and leave it fixed, it works perfectly in that YSF Reflector. but it doesn't let me change it.

Different Configuration MMDVM_Bridge.ini

Without YSFGateway
[System Fusion Network]
Enable = 1
LocalAddress = 0
LocalPort = 3200
GatewayAddress = ysfreflector.dvswitch.org
GatewayPort = 42166
Debug = 0

But working with YSFGateway doesn't let it change
Configuration with YSFGateway
[System Fusion Network]
Enable = 1
LocalAddress = 127.0.0.1
LocalPort = 3200
GatewayAddress = 127.0.0.1
GatewayPort = 4200
Debug = 0


About mode YSFN in dvswicht mobile.

EA5GVK Joaquin
 

I am testing the different modes of the dvswitch mobile. in DMR and NXDN so far all right and fabulous applications.
Now I am testing with YSFN (fusion) mode.
I want to ask two questions.
Should the YSFGateway work too?

If I do not configure the YSFGateway and leave it fixed, it works perfectly in that YSF Reflector. but it doesn't let me change it.

Different Configuration MMDVM_Bridge.ini

Without YSFGateway
[System Fusion Network]
Enable = 1
LocalAddress = 0
LocalPort = 3200
GatewayAddress = ysfreflector.dvswitch.org
GatewayPort = 42166
Debug = 0

But working with YSFGateway doesn't let it change
Configuration with YSFGateway
[System Fusion Network]
Enable = 1
LocalAddress = 127.0.0.1
LocalPort = 3200
GatewayAddress = 127.0.0.1
GatewayPort = 4200
Debug = 0


Re: CHANGE MODE IN DVSWICHT MOBILE, REPORT PROBLEM, RESTART ANALOG_BRIDGE.

Steve N4IRS
 

Good to hear.
We will push a proper fix to github later this weekend. If all goes well, next we will remove the need to restart AB to change modes.

73, Steve N4IRS

On 7/20/19 12:23 PM, EA5GVK Joaquin wrote:
Yes perfectly working change mode now.
Manyt thx Steve
Add in ea5gvkanalog.service it command

[Unit]
Description=Analog_Bridge Service
# Description=Place this file in /lib/systemd/system
# Description=N4IRS 04/20/2018

# The device name should point to the
# port the mmdvm is plugged into.
# For USB ports (Arduino Due)
# BindTo=dev-ttyACM0.device
#
# To make the network-online.target available
# systemctl enable systemd-networkd-wait-online.service

After=network-online.target syslog.target netcheck.service
Wants=network-online.target

[Service]
Type=simple
StandardOutput=null
WorkingDirectory=/opt/EA5GVK/Analog_Bridge
Environment=AnalogBridgeLogDir=/var/log/dvswitch7
# Environment=LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
Restart=always
RestartSec=3
ExecStart=/opt/EA5GVK/Analog_Bridge/Analog_Bridge /opt/EA5GVK/Analog_Bridge/Analog_Bridge.ini
ExecReload=/bin/kill -2 $MAINPID
KillMode=process
KillSignal=SIGKILL

[Install]
WantedBy=multi-user.target


Re: CHANGE MODE IN DVSWICHT MOBILE, REPORT PROBLEM, RESTART ANALOG_BRIDGE.

EA5GVK Joaquin
 

Yes perfectly working change mode now.
Manyt thx Steve
Add in ea5gvkanalog.service it command

[Unit]
Description=Analog_Bridge Service
# Description=Place this file in /lib/systemd/system
# Description=N4IRS 04/20/2018

# The device name should point to the
# port the mmdvm is plugged into.
# For USB ports (Arduino Due)
# BindTo=dev-ttyACM0.device
#
# To make the network-online.target available
# systemctl enable systemd-networkd-wait-online.service

After=network-online.target syslog.target netcheck.service
Wants=network-online.target

[Service]
Type=simple
StandardOutput=null
WorkingDirectory=/opt/EA5GVK/Analog_Bridge
Environment=AnalogBridgeLogDir=/var/log/dvswitch7
# Environment=LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
Restart=always
RestartSec=3
ExecStart=/opt/EA5GVK/Analog_Bridge/Analog_Bridge /opt/EA5GVK/Analog_Bridge/Analog_Bridge.ini
ExecReload=/bin/kill -2 $MAINPID
KillMode=process
KillSignal=SIGKILL

[Install]
WantedBy=multi-user.target


Re: CHANGE MODE IN DVSWICHT MOBILE, REPORT PROBLEM, RESTART ANALOG_BRIDGE.

Steve N4IRS
 

Do the Temporary fix

On 7/20/19 11:57 AM, EA5GVK Joaquin wrote:
In Debian 10 busted 64 bits.

servidor@blasmakers:~$ sudo cat /etc/debian_version
10.0
servidor@blasmakers:~$

And Ubuntu 32 bits.
show
buster/sid

In raspberry now, no working.

My ea5gvkanalog.service is:
[Unit]
Description=Analog_Bridge Service
# Description=Place this file in /lib/systemd/system
# Description=N4IRS 04/20/2018

# The device name should point to the
# port the mmdvm is plugged into.
# For USB ports (Arduino Due)
# BindTo=dev-ttyACM0.device
#
# To make the network-online.target available
# systemctl enable systemd-networkd-wait-online.service

After=network-online.target syslog.target netcheck.service
Wants=network-online.target

[Service]
Type=simple
StandardOutput=null
WorkingDirectory=/opt/EA5GVK/Analog_Bridge
Environment=AnalogBridgeLogDir=/var/log/dvswitch7
# Environment=LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
Restart=always
RestartSec=3
ExecStart=/opt/EA5GVK/Analog_Bridge/Analog_Bridge /opt/EA5GVK/Analog_Bridge/Analog_Bridge.ini
ExecReload=/bin/kill -2 $MAINPID
KillMode=process

[Install]
WantedBy=multi-user.target



Re: CHANGE MODE IN DVSWICHT MOBILE, REPORT PROBLEM, RESTART ANALOG_BRIDGE.

EA5GVK Joaquin
 

In Debian 10 busted 64 bits.

servidor@blasmakers:~$ sudo cat /etc/debian_version
10.0
servidor@blasmakers:~$

And Ubuntu 32 bits.
show
buster/sid

In raspberry now, no working.

My ea5gvkanalog.service is:
[Unit]
Description=Analog_Bridge Service
# Description=Place this file in /lib/systemd/system
# Description=N4IRS 04/20/2018

# The device name should point to the
# port the mmdvm is plugged into.
# For USB ports (Arduino Due)
# BindTo=dev-ttyACM0.device
#
# To make the network-online.target available
# systemctl enable systemd-networkd-wait-online.service

After=network-online.target syslog.target netcheck.service
Wants=network-online.target

[Service]
Type=simple
StandardOutput=null
WorkingDirectory=/opt/EA5GVK/Analog_Bridge
Environment=AnalogBridgeLogDir=/var/log/dvswitch7
# Environment=LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
Restart=always
RestartSec=3
ExecStart=/opt/EA5GVK/Analog_Bridge/Analog_Bridge /opt/EA5GVK/Analog_Bridge/Analog_Bridge.ini
ExecReload=/bin/kill -2 $MAINPID
KillMode=process

[Install]
WantedBy=multi-user.target

5361 - 5380 of 9820