Date   

Re: YSFReflector bridged to DMR - No callsign on YSF clients #mmdvm_bridge

Andrew Lynch
 

Nope, this is a specific TG on the TGIF network, not the main one.

On Tue, Aug 13, 2019 at 1:32 PM Alec-N1AJW <alec.wasserman@...> wrote:
the TGIF YSF2DMR bridge has mysteriously started working again.  update pistar and the host should be there.  I know that's not the answer to your question but you wont have to do this since its "mysteriously" started working.


Alec
N1AJW



--
Andrew Lynch (KD0IOE)
lurch89@...


Re: YSFReflector bridged to DMR - No callsign on YSF clients #mmdvm_bridge

Alec-N1AJW
 

the TGIF YSF2DMR bridge has mysteriously started working again.  update pistar and the host should be there.  I know that's not the answer to your question but you wont have to do this since its "mysteriously" started working.


Alec
N1AJW


YSFReflector bridged to DMR - No callsign on YSF clients #mmdvm_bridge

Andrew Lynch
 

I have successfully set up a YSFReflector, and linked to a TGIF DMR talkgroup. Audio passes between the two, and the DMR ID lookup based on the MYCALL in a given Yaesu radio is working (DMR side sees the proper DMR ID of the YSF user). However, I can't seem to get callsigns to display on the Yaesu radio. I am using a Pi-Star-powered hotspot (3.14.7 I think), and the Callsigns appear on both the OLED display and on the dashboard. That leads me to think it's my hotspot not sending it along with the voice. But, I don't remember this actually working anywhere on YSF. This is my first sysop experience with YSF - I've mostly just participated on DMR, but wanted to have the option of YSF as well.

Is this expected behavior (callsign doesn't make it to the radio) or am I missing a config somewhere? I don't have a second hotspot (...yet) that I can test (have 2 YSF clients on the YSFReflector) and haven't found a guinea pig yet.

Thanks!
-Andy, KDØIOE


Re: Setting up a remote base to DMR

Vince Vielhaber
 

In my case the antenna tuner is manual, so for now I have to go fixed freq. In the future I may be able to add an auto tuner (I have several).

Another feature in ASL's remote base stuff, it has memories. Go to a certain freq, PL Tone, Offset or Simplex, ...

Vince.

On 08/12/2019 06:25 PM, Steve KC1AWV wrote:
You know as I'm thinking about it, ASL has macros for controlling a base
station built into app_rpt already. So, using DVSwitch Mobile will give
you the ability to tune and such the remote base as if you were there at
the rig. This is giving me ideas... :)

Steve KC1AWV


Re: Setting up a remote base to DMR

Steve KC1AWV
 

You know as I'm thinking about it, ASL has macros for controlling a base station built into app_rpt already. So, using DVSwitch Mobile will give you the ability to tune and such the remote base as if you were there at the rig. This is giving me ideas... :)

Steve KC1AWV


Re: Setting up a remote base to DMR

Steve KC1AWV
 

DVSwitch Mobile is the Android/iPhone client used in lieu of needing a hotspot and digital radio, and it used to be called Android IAXRPT. Using DVSwitch Mobile, you can connect to ASL, DMR, DStar, YSF, NXDN, and P25 networks. It's quite a neat piece of software!

Steve KC1AWV


Re: Setting up a remote base to DMR

Vince Vielhaber
 

The reason for the hotspot is when I'm away I can use it tethered to my fone or find an internet connection and use my DMR handheld to connect to the remote base.

I don't know what DVSwitch Mobile is. I thought I went thru all of the parts of DVSwitch, must have missed that one, or it didn't appear to apply to what I'm trying to do
.
Thanks!
Vince.

On 08/12/2019 05:38 PM, Steve KC1AWV wrote:
[Edited Message Follows]

Is there a specific need for the DMR hotspot? If you're using ASL
already, you could use DVSwitch Mobile direct to ASL and not have to
worry about converting to DMR.

Remote Base <-> ASL <-> DVSwitch Mobile

If you still wanted to go to DMR, you could do this:

Remote <-> ASL <-> Analog_Bridge <-> MMDVM_Bridge <-> hblink3 <-> Hotspot

You still need to have some sort of master server for the hotspot to log
into, hence the hblink3. You can run hblink3 on the same host as
Analog_Bridge and MMDVM_Bridge. You could even use hblink3 locally on a
PiStar hotspot, but that's some advanced configuration that would need
more research for me to understand it.

Oh, and I forgot to answer your other question. /Also, do I need to
register for an ASL node if I'm not planning on connecting to their
network?/

No, and I believe the ASL image startup script allows you to set up a
private node, though I haven't done this myself.

Steve KC1AWV


Re: Setting up a remote base to DMR

Steve KC1AWV
 
Edited

Is there a specific need for the DMR hotspot? If you're using ASL already, you could use DVSwitch Mobile direct to ASL and not have to worry about converting to DMR.

Remote Base <-> ASL <-> DVSwitch Mobile

If you still wanted to go to DMR, you could do this:

Remote <-> ASL <-> Analog_Bridge <-> MMDVM_Bridge <-> hblink3 <-> Hotspot

You still need to have some sort of master server for the hotspot to log into, hence the hblink3. You can run hblink3 on the same host as Analog_Bridge and MMDVM_Bridge. You could even use hblink3 locally on a PiStar hotspot, but that's some advanced configuration that would need more research for me to understand it.

Oh, and I forgot to answer your other question. Also, do I need to register for an ASL node if I'm not planning on connecting to their network?

No, and I believe the ASL image startup script allows you to set up a private node, though I haven't done this myself.

Steve KC1AWV


Setting up a remote base to DMR

Vince Vielhaber
 

I want to set up a remote base on HF that I can access via my DMR hotspot. I have ASL asterisk installed and partially configured and I have Analog-Bridge installed (but not yet configured). The remote base is a dumb one, even tho it's capable, it won't be changing freq or anything else. This is mainly for the evening rag-chew when I'm away and eventually I'd like to add a small TG for a few friends to connect to.

I think what I need is:

Remote Base <--> ASL <--> Analog_Br <--> ? <--> DMR Hotspot

As for the ? in the above, is that going to be HBLink3?

This will NOT be connected to BM or any other public network.

Also, do I need to register for an ASL node if I'm not planning on connecting to their network?

My background: Retired after 30 years as a C/C++ programmer, been running Asterisk as a phone system for many years.

Thanks!
Vince.
--
K8ZW http://www.metalworkingfun.com http://www.hamradio.fun


Re: Callsigns Change When Going Across Bridge

Steve N4IRS
 

David,
It is the list of things to look at for the next rev of MB.

73, Steve N4IRS

On 8/10/19 3:58 PM, David wrote:
Any new information on this?

AK2L


Re: Callsigns Change When Going Across Bridge

David - AK2L
 

Any new information on this?

AK2L


Re: NOOB Setup-Configuration Help #analog_bridge #dmrlink

Steve N4IRS
 

Follow up to The issues Chris was having.
As I suspected and questioned, he had another copy of MMDVM_Bridge running. In this case, the problem showed up when a second copy of MMDVM_Bridge was executed in the foreground, the first and second copies would both try to login to BrandMeister. There is nothing wrong with 2 copies of MMDVM_Bridge running, the problem is 2 copies trying to use the same UDP ports.

These Linux commands are necessary for anyone working wit any of the DVSwitch programs.

ps -ax #show running processes
netstat -unap #show what programs are listening on what UDP ports.

Both programs need to be run as root. (sudo)

Changing the well known port and password to connect to a DMR Master, editing LAT and Long are a waste of time. I believe all BM Masters publish their login info. MOST of the time, this type of error is because you have a second copy of MB, already logged into the Master

73, Steve N4IRS


Re: NXDN Install with DVSMobile

Steve N4IRS
 

Should already be setup. Make sure NXDN Networking is enabled.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Tom Corcoran <tcorcoran@...>
Sent: Friday, August 9, 2019 3:22:58 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] NXDN Install with DVSMobile
 
Do I need to make any references to gateway in other programs... or are they already there? 
--
Tom VE3NY


Re: NXDN Install with DVSMobile

Tom Corcoran
 

Do I need to make any references to gateway in other programs... or are they already there? 
--
Tom VE3NY


Re: NXDN Install with DVSMobile

Steve N4IRS
 

That is up to you. I like putting those type of things in /opt. That way I keep all the needed programs and data together.

Steve

On 8/9/19 3:17 PM, Tom Corcoran wrote:
Oooops. Didn’t know I needed NXDNGateway. Do I get from GitHub? In which directory should it be installed? 
--
Tnx Steve ... Tom VE3NY


Re: NXDN Install with DVSMobile

Tom Corcoran
 

Oooops. Didn’t know I needed NXDNGateway. Do I get from GitHub? In which directory should it be installed? 
--
Tnx Steve ... Tom VE3NY


Re: NXDN Install with DVSMobile

Steve N4IRS
 

Do you have NXDNGateway running?
Anything in the log of the gateway.

On 8/9/19 2:38 PM, Tom Corcoran wrote:
Can anyone see why I can't seem to connect to NXDN reflectors? Works great on DMR and YSF but drawing blanks so far on NXDN.
--
Tnx ... Tom VE3NY
(sorry if posted twice .. couldn't find original post)

Error Log

I: 2019-08-09 15:43:48.784 General Parameters
I: 2019-08-09 15:43:48.784     Callsign: VE3NY
I: 2019-08-09 15:43:48.784     Id: 3023284
I: 2019-08-09 15:43:48.784     Duplex: no
I: 2019-08-09 15:43:48.784     Timeout: 180s
I: 2019-08-09 15:43:48.784     D-Star: disabled
I: 2019-08-09 15:43:48.785     DMR: enabled
I: 2019-08-09 15:43:48.785     YSF: enabled
I: 2019-08-09 15:43:48.785     P25: disabled
I: 2019-08-09 15:43:48.785     NXDN: enabled
I: 2019-08-09 15:43:48.785 Modem Parameters
I: 2019-08-09 15:43:48.785     Port: /dev/null
I: 2019-08-09 15:43:48.785     RX Invert: no
I: 2019-08-09 15:43:48.785     TX Invert: no
I: 2019-08-09 15:43:48.785     PTT Invert: no
I: 2019-08-09 15:43:48.785     TX Delay: 100ms
I: 2019-08-09 15:43:48.785     RX Offset: 0Hz
I: 2019-08-09 15:43:48.785     TX Offset: 0Hz
I: 2019-08-09 15:43:48.785     RX DC Offset: 0
I: 2019-08-09 15:43:48.785     TX DC Offset: 0
I: 2019-08-09 15:43:48.785     RF Level: 100.0%
I: 2019-08-09 15:43:48.785     DMR Delay: 0 (0.0ms)
I: 2019-08-09 15:43:48.785     RX Level: 50.0%
I: 2019-08-09 15:43:48.785     CW Id TX Level: 50.0%
I: 2019-08-09 15:43:48.785     D-Star TX Level: 50.0%
I: 2019-08-09 15:43:48.785     DMR TX Level: 50.0%
I: 2019-08-09 15:43:48.785     YSF TX Level: 50.0%
I: 2019-08-09 15:43:48.785     P25 TX Level: 50.0%
I: 2019-08-09 15:43:48.785     NXDN TX Level: 50.0%
I: 2019-08-09 15:43:48.785     RX Frequency: 222340000Hz (222340000Hz)
I: 2019-08-09 15:43:48.785     TX Frequency: 224940000Hz (224940000Hz)
M: 2019-08-09 15:43:48.785 Opening the MMDVM
I: 2019-08-09 15:43:48.785 Display Parameters
I: 2019-08-09 15:43:48.785     Type: 
I: 2019-08-09 15:43:48.792 DMR Network Parameters
I: 2019-08-09 15:43:48.792     Address: 158.69.203.89  ; 158.69.203.89 BM  ; 74.91.125.81  TGIF
I: 2019-08-09 15:43:48.793     Port: 62031
I: 2019-08-09 15:43:48.793     Local: 62032
I: 2019-08-09 15:43:48.793     Jitter: 600ms
I: 2019-08-09 15:43:48.793     Slot 1: disabled
I: 2019-08-09 15:43:48.793     Slot 2: enabled
I: 2019-08-09 15:43:48.793     Mode Hang: 3s
I: 2019-08-09 15:43:48.793 Info Parameters
I: 2019-08-09 15:43:48.793     Callsign: VE3NY
I: 2019-08-09 15:43:48.793     RX Frequency: 222340000Hz
I: 2019-08-09 15:43:48.793     TX Frequency: 224940000Hz
I: 2019-08-09 15:43:48.793     Power: 1W
I: 2019-08-09 15:43:48.793     Latitude: 47.733299deg N
I: 2019-08-09 15:43:48.793     Longitude: -78.399902deg E
I: 2019-08-09 15:43:48.793     Height: 0m
I: 2019-08-09 15:43:48.793     Location: "Toronto, Canada"
I: 2019-08-09 15:43:48.793     Description: "MMDVM_Bridge"
I: 2019-08-09 15:43:48.793     URL: "http://QRZ.com/db/VE3NY "
M: 2019-08-09 15:43:48.793 DMR, Opening DMR Network
I: 2019-08-09 15:43:48.793 System Fusion Network Parameters
I: 2019-08-09 15:43:48.793     Local Address: 0
I: 2019-08-09 15:43:48.793     Local Port: 3200
I: 2019-08-09 15:43:48.793     Gateway Address: 96.47.95.121 
I: 2019-08-09 15:43:48.793     Gateway Port: 42001
I: 2019-08-09 15:43:48.793     Mode Hang: 3s
M: 2019-08-09 15:43:48.793 Opening YSF network connection
I: 2019-08-09 15:43:48.793 NXDN Network Parameters
I: 2019-08-09 15:43:48.793     Gateway Address: 127.0.0.1
I: 2019-08-09 15:43:48.793     Gateway Port: 14020
I: 2019-08-09 15:43:48.793     Local Address: 
I: 2019-08-09 15:43:48.793     Local Port: 14021
I: 2019-08-09 15:43:48.793     Mode Hang: 3s
M: 2019-08-09 15:43:48.793 Opening NXDN network connection
I: 2019-08-09 15:43:48.793 RSSI
I: 2019-08-09 15:43:48.793     Mapping File: RSSI.dat
W: 2019-08-09 15:43:48.793 Cannot open the RSSI data file - RSSI.dat
I: 2019-08-09 15:43:48.793 DMR Id Lookups
I: 2019-08-09 15:43:48.793     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-08-09 15:43:48.793     Reload: 24 hours
I: 2019-08-09 15:43:49.580 Loaded 140641 Ids to the DMR callsign lookup table
I: 2019-08-09 15:43:49.580 DMR RF Parameters
I: 2019-08-09 15:43:49.580 Started the DMR Id lookup reload thread
I: 2019-08-09 15:43:49.580     Id: 3023284
I: 2019-08-09 15:43:49.580     Color Code: 1
I: 2019-08-09 15:43:49.580     Self Only: no
I: 2019-08-09 15:43:49.580     Embedded LC Only: yes
I: 2019-08-09 15:43:49.580     Dump Talker Alias Data: no
I: 2019-08-09 15:43:49.580     Prefixes: 0
I: 2019-08-09 15:43:49.580     Call Hang: 3s
I: 2019-08-09 15:43:49.580     TX Hang: 3s
I: 2019-08-09 15:43:49.580     Mode Hang: 10s
M: 2019-08-09 15:43:49.580 DMR, Opening INI file: DVSwitch.ini
M: 2019-08-09 15:43:49.581 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-08-09 15:43:49.581 DMR, Setting [DMR] TXPort -> 31100
M: 2019-08-09 15:43:49.582 DMR, Setting [DMR] RXPort -> 31103
M: 2019-08-09 15:43:49.582 DMR, Setting [DMR] Slot -> 2
M: 2019-08-09 15:43:49.582 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2019-08-09 15:43:49.582 YSF RF Parameters
I: 2019-08-09 15:43:49.582     Low Deviation: no
I: 2019-08-09 15:43:49.582     Remote Gateway: no
I: 2019-08-09 15:43:49.582     Self Only: no
I: 2019-08-09 15:43:49.582     DSQ: no
I: 2019-08-09 15:43:49.582     Mode Hang: 10s
M: 2019-08-09 15:43:49.582 YSF, Opening INI file: DVSwitch.ini
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] TXPort -> 35100
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] RXPort -> 35103
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] ExportTG -> 9
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] Slot -> 2
M: 2019-08-09 15:43:49.582 YSF, Transmitting on 127.0.0.1:35100 and listening on port 35103.  Result = 1
I: 2019-08-09 15:43:49.582 NXDN Id Lookups
I: 2019-08-09 15:43:49.582     File: /var/lib/mmdvm/NXDN.csv
I: 2019-08-09 15:43:49.582     Reload: 24 hours
I: 2019-08-09 15:43:49.597 Loaded 2150 Ids to the NXDN callsign lookup table
I: 2019-08-09 15:43:49.597 NXDN RF Parameters
I: 2019-08-09 15:43:49.597 Started the NXDN Id lookup reload thread
I: 2019-08-09 15:43:49.597     Id: 570
I: 2019-08-09 15:43:49.597     RAN: 1
I: 2019-08-09 15:43:49.597     Self Only: no
I: 2019-08-09 15:43:49.597     Remote Gateway: no
I: 2019-08-09 15:43:49.597     Mode Hang: 10s
M: 2019-08-09 15:43:49.597 NXDN, Opening INI file: DVSwitch.ini
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] Address -> 127.0.0.1
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] TXPort -> 33100
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] RXPort -> 33103
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] FallbackID -> 3112488
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] NXDNFallbackID -> 12345
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] Translate -> 10=9
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] Slot -> 2
M: 2019-08-09 15:43:49.597 NXDN, NXDN TG 10 <--> TLV TG 9
M: 2019-08-09 15:43:49.597 NXDN, Transmitting on 127.0.0.1:33100 and listening on port 33103.  Result = 1
M: 2019-08-09 15:43:49.597 MMDVM_Bridge-20180423 is running
M: 2019-08-09 15:43:59.663 DMR, Logged into the master successfully
M: 2019-08-09 15:44:45.500 NXDN, Remote CMD: codec=slin
I: 2019-08-09 15:44:45.501 NXDN, Unknown command for this mode
I: 2019-08-09 15:45:10.302 NXDN, dmrToNxdn by call: 3023284
I: 2019-08-09 15:45:10.302 NXDN, TAG_SET_INFO: src=12345 rpt=302328401 dst=10 slot=2 cc=1 metadata=3023284
M: 2019-08-09 15:45:10.302 NXDN, Remote CMD: txTg=28299
M: 2019-08-09 15:45:10.303 NXDN, received RF header from JM8IXA to TG 28299
M: 2019-08-09 15:45:10.303 NXDN, received RF end of transmission, 0.1 seconds, BER: 0.0%
M: 2019-08-09 15:45:18.726 NXDN, TX state = ON
I: 2019-08-09 15:45:18.726 NXDN, dmrToNxdn by call: VE3NY
I: 2019-08-09 15:45:18.726 NXDN, Begin TX: src=3023284 rpt=302328401 dst=28299 slot=2 cc=1 metadata=VE3NY
I: 2019-08-09 15:45:18.726 NXDN, (3023284, 28299) -> (570, 28299)
M: 2019-08-09 15:45:18.726 NXDN, received RF header from VE3NY to TG 28299
M: 2019-08-09 15:45:20.725 NXDN, TX state = OFF
M: 2019-08-09 15:45:20.726 NXDN, received RF end of transmission, 2.0 seconds, BER: 6.0%
M: 2019-08-09 15:45:24.809 NXDN, TX state = ON
I: 2019-08-09 15:45:24.809 NXDN, dmrToNxdn by call: VE3NY
I: 2019-08-09 15:45:24.809 NXDN, Begin TX: src=3023284 rpt=302328401 dst=28299 slot=2 cc=1 metadata=VE3NY
I: 2019-08-09 15:45:24.809 NXDN, (3023284, 28299) -> (570, 28299)
M: 2019-08-09 15:45:24.809 NXDN, received RF header from VE3NY to TG 28299
M: 2019-08-09 15:45:26.859 NXDN, TX state = OFF
M: 2019-08-09 15:45:26.859 NXDN, received RF end of transmission, 2.2 seconds, BER: 1.6%
M: 2019-08-09 15:47:23.335 NXDN, TX state = ON
I: 2019-08-09 15:47:23.335 NXDN, dmrToNxdn by call: VE3NY
I: 2019-08-09 15:47:23.335 NXDN, Begin TX: src=3023284 rpt=302328401 dst=28299 slot=2 cc=1 metadata=VE3NY
I: 2019-08-09 15:47:23.335 NXDN, (3023284, 28299) -> (570, 28299)
M: 2019-08-09 15:47:23.335 NXDN, received RF header from VE3NY to TG 28299
M: 2019-08-09 15:47:25.350 NXDN, TX state = OFF
M: 2019-08-09 15:47:25.350 NXDN, received RF end of transmission, 2.1 seconds, BER: 1.4%


NXDN Install with DVSMobile

Tom Corcoran
 

Can anyone see why I can't seem to connect to NXDN reflectors? Works great on DMR and YSF but drawing blanks so far on NXDN.
--
Tnx ... Tom VE3NY
(sorry if posted twice .. couldn't find original post)

Error Log

I: 2019-08-09 15:43:48.784 General Parameters
I: 2019-08-09 15:43:48.784     Callsign: VE3NY
I: 2019-08-09 15:43:48.784     Id: 3023284
I: 2019-08-09 15:43:48.784     Duplex: no
I: 2019-08-09 15:43:48.784     Timeout: 180s
I: 2019-08-09 15:43:48.784     D-Star: disabled
I: 2019-08-09 15:43:48.785     DMR: enabled
I: 2019-08-09 15:43:48.785     YSF: enabled
I: 2019-08-09 15:43:48.785     P25: disabled
I: 2019-08-09 15:43:48.785     NXDN: enabled
I: 2019-08-09 15:43:48.785 Modem Parameters
I: 2019-08-09 15:43:48.785     Port: /dev/null
I: 2019-08-09 15:43:48.785     RX Invert: no
I: 2019-08-09 15:43:48.785     TX Invert: no
I: 2019-08-09 15:43:48.785     PTT Invert: no
I: 2019-08-09 15:43:48.785     TX Delay: 100ms
I: 2019-08-09 15:43:48.785     RX Offset: 0Hz
I: 2019-08-09 15:43:48.785     TX Offset: 0Hz
I: 2019-08-09 15:43:48.785     RX DC Offset: 0
I: 2019-08-09 15:43:48.785     TX DC Offset: 0
I: 2019-08-09 15:43:48.785     RF Level: 100.0%
I: 2019-08-09 15:43:48.785     DMR Delay: 0 (0.0ms)
I: 2019-08-09 15:43:48.785     RX Level: 50.0%
I: 2019-08-09 15:43:48.785     CW Id TX Level: 50.0%
I: 2019-08-09 15:43:48.785     D-Star TX Level: 50.0%
I: 2019-08-09 15:43:48.785     DMR TX Level: 50.0%
I: 2019-08-09 15:43:48.785     YSF TX Level: 50.0%
I: 2019-08-09 15:43:48.785     P25 TX Level: 50.0%
I: 2019-08-09 15:43:48.785     NXDN TX Level: 50.0%
I: 2019-08-09 15:43:48.785     RX Frequency: 222340000Hz (222340000Hz)
I: 2019-08-09 15:43:48.785     TX Frequency: 224940000Hz (224940000Hz)
M: 2019-08-09 15:43:48.785 Opening the MMDVM
I: 2019-08-09 15:43:48.785 Display Parameters
I: 2019-08-09 15:43:48.785     Type: 
I: 2019-08-09 15:43:48.792 DMR Network Parameters
I: 2019-08-09 15:43:48.792     Address: 158.69.203.89  ; 158.69.203.89 BM  ; 74.91.125.81  TGIF
I: 2019-08-09 15:43:48.793     Port: 62031
I: 2019-08-09 15:43:48.793     Local: 62032
I: 2019-08-09 15:43:48.793     Jitter: 600ms
I: 2019-08-09 15:43:48.793     Slot 1: disabled
I: 2019-08-09 15:43:48.793     Slot 2: enabled
I: 2019-08-09 15:43:48.793     Mode Hang: 3s
I: 2019-08-09 15:43:48.793 Info Parameters
I: 2019-08-09 15:43:48.793     Callsign: VE3NY
I: 2019-08-09 15:43:48.793     RX Frequency: 222340000Hz
I: 2019-08-09 15:43:48.793     TX Frequency: 224940000Hz
I: 2019-08-09 15:43:48.793     Power: 1W
I: 2019-08-09 15:43:48.793     Latitude: 47.733299deg N
I: 2019-08-09 15:43:48.793     Longitude: -78.399902deg E
I: 2019-08-09 15:43:48.793     Height: 0m
I: 2019-08-09 15:43:48.793     Location: "Toronto, Canada"
I: 2019-08-09 15:43:48.793     Description: "MMDVM_Bridge"
I: 2019-08-09 15:43:48.793     URL: "http://QRZ.com/db/VE3NY "
M: 2019-08-09 15:43:48.793 DMR, Opening DMR Network
I: 2019-08-09 15:43:48.793 System Fusion Network Parameters
I: 2019-08-09 15:43:48.793     Local Address: 0
I: 2019-08-09 15:43:48.793     Local Port: 3200
I: 2019-08-09 15:43:48.793     Gateway Address: 96.47.95.121 
I: 2019-08-09 15:43:48.793     Gateway Port: 42001
I: 2019-08-09 15:43:48.793     Mode Hang: 3s
M: 2019-08-09 15:43:48.793 Opening YSF network connection
I: 2019-08-09 15:43:48.793 NXDN Network Parameters
I: 2019-08-09 15:43:48.793     Gateway Address: 127.0.0.1
I: 2019-08-09 15:43:48.793     Gateway Port: 14020
I: 2019-08-09 15:43:48.793     Local Address: 
I: 2019-08-09 15:43:48.793     Local Port: 14021
I: 2019-08-09 15:43:48.793     Mode Hang: 3s
M: 2019-08-09 15:43:48.793 Opening NXDN network connection
I: 2019-08-09 15:43:48.793 RSSI
I: 2019-08-09 15:43:48.793     Mapping File: RSSI.dat
W: 2019-08-09 15:43:48.793 Cannot open the RSSI data file - RSSI.dat
I: 2019-08-09 15:43:48.793 DMR Id Lookups
I: 2019-08-09 15:43:48.793     File: /var/lib/mmdvm/DMRIds.dat
I: 2019-08-09 15:43:48.793     Reload: 24 hours
I: 2019-08-09 15:43:49.580 Loaded 140641 Ids to the DMR callsign lookup table
I: 2019-08-09 15:43:49.580 DMR RF Parameters
I: 2019-08-09 15:43:49.580 Started the DMR Id lookup reload thread
I: 2019-08-09 15:43:49.580     Id: 3023284
I: 2019-08-09 15:43:49.580     Color Code: 1
I: 2019-08-09 15:43:49.580     Self Only: no
I: 2019-08-09 15:43:49.580     Embedded LC Only: yes
I: 2019-08-09 15:43:49.580     Dump Talker Alias Data: no
I: 2019-08-09 15:43:49.580     Prefixes: 0
I: 2019-08-09 15:43:49.580     Call Hang: 3s
I: 2019-08-09 15:43:49.580     TX Hang: 3s
I: 2019-08-09 15:43:49.580     Mode Hang: 10s
M: 2019-08-09 15:43:49.580 DMR, Opening INI file: DVSwitch.ini
M: 2019-08-09 15:43:49.581 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2019-08-09 15:43:49.581 DMR, Setting [DMR] TXPort -> 31100
M: 2019-08-09 15:43:49.582 DMR, Setting [DMR] RXPort -> 31103
M: 2019-08-09 15:43:49.582 DMR, Setting [DMR] Slot -> 2
M: 2019-08-09 15:43:49.582 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2019-08-09 15:43:49.582 YSF RF Parameters
I: 2019-08-09 15:43:49.582     Low Deviation: no
I: 2019-08-09 15:43:49.582     Remote Gateway: no
I: 2019-08-09 15:43:49.582     Self Only: no
I: 2019-08-09 15:43:49.582     DSQ: no
I: 2019-08-09 15:43:49.582     Mode Hang: 10s
M: 2019-08-09 15:43:49.582 YSF, Opening INI file: DVSwitch.ini
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] TXPort -> 35100
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] RXPort -> 35103
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] FallbackID -> 3112488
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] ExportTG -> 9
M: 2019-08-09 15:43:49.582 YSF, Setting [YSF] Slot -> 2
M: 2019-08-09 15:43:49.582 YSF, Transmitting on 127.0.0.1:35100 and listening on port 35103.  Result = 1
I: 2019-08-09 15:43:49.582 NXDN Id Lookups
I: 2019-08-09 15:43:49.582     File: /var/lib/mmdvm/NXDN.csv
I: 2019-08-09 15:43:49.582     Reload: 24 hours
I: 2019-08-09 15:43:49.597 Loaded 2150 Ids to the NXDN callsign lookup table
I: 2019-08-09 15:43:49.597 NXDN RF Parameters
I: 2019-08-09 15:43:49.597 Started the NXDN Id lookup reload thread
I: 2019-08-09 15:43:49.597     Id: 570
I: 2019-08-09 15:43:49.597     RAN: 1
I: 2019-08-09 15:43:49.597     Self Only: no
I: 2019-08-09 15:43:49.597     Remote Gateway: no
I: 2019-08-09 15:43:49.597     Mode Hang: 10s
M: 2019-08-09 15:43:49.597 NXDN, Opening INI file: DVSwitch.ini
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] Address -> 127.0.0.1
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] TXPort -> 33100
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] RXPort -> 33103
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] FallbackID -> 3112488
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] NXDNFallbackID -> 12345
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] Translate -> 10=9
M: 2019-08-09 15:43:49.597 NXDN, Setting [NXDN] Slot -> 2
M: 2019-08-09 15:43:49.597 NXDN, NXDN TG 10 <--> TLV TG 9
M: 2019-08-09 15:43:49.597 NXDN, Transmitting on 127.0.0.1:33100 and listening on port 33103.  Result = 1
M: 2019-08-09 15:43:49.597 MMDVM_Bridge-20180423 is running
M: 2019-08-09 15:43:59.663 DMR, Logged into the master successfully
M: 2019-08-09 15:44:45.500 NXDN, Remote CMD: codec=slin
I: 2019-08-09 15:44:45.501 NXDN, Unknown command for this mode
I: 2019-08-09 15:45:10.302 NXDN, dmrToNxdn by call: 3023284
I: 2019-08-09 15:45:10.302 NXDN, TAG_SET_INFO: src=12345 rpt=302328401 dst=10 slot=2 cc=1 metadata=3023284
M: 2019-08-09 15:45:10.302 NXDN, Remote CMD: txTg=28299
M: 2019-08-09 15:45:10.303 NXDN, received RF header from JM8IXA to TG 28299
M: 2019-08-09 15:45:10.303 NXDN, received RF end of transmission, 0.1 seconds, BER: 0.0%
M: 2019-08-09 15:45:18.726 NXDN, TX state = ON
I: 2019-08-09 15:45:18.726 NXDN, dmrToNxdn by call: VE3NY
I: 2019-08-09 15:45:18.726 NXDN, Begin TX: src=3023284 rpt=302328401 dst=28299 slot=2 cc=1 metadata=VE3NY
I: 2019-08-09 15:45:18.726 NXDN, (3023284, 28299) -> (570, 28299)
M: 2019-08-09 15:45:18.726 NXDN, received RF header from VE3NY to TG 28299
M: 2019-08-09 15:45:20.725 NXDN, TX state = OFF
M: 2019-08-09 15:45:20.726 NXDN, received RF end of transmission, 2.0 seconds, BER: 6.0%
M: 2019-08-09 15:45:24.809 NXDN, TX state = ON
I: 2019-08-09 15:45:24.809 NXDN, dmrToNxdn by call: VE3NY
I: 2019-08-09 15:45:24.809 NXDN, Begin TX: src=3023284 rpt=302328401 dst=28299 slot=2 cc=1 metadata=VE3NY
I: 2019-08-09 15:45:24.809 NXDN, (3023284, 28299) -> (570, 28299)
M: 2019-08-09 15:45:24.809 NXDN, received RF header from VE3NY to TG 28299
M: 2019-08-09 15:45:26.859 NXDN, TX state = OFF
M: 2019-08-09 15:45:26.859 NXDN, received RF end of transmission, 2.2 seconds, BER: 1.6%
M: 2019-08-09 15:47:23.335 NXDN, TX state = ON
I: 2019-08-09 15:47:23.335 NXDN, dmrToNxdn by call: VE3NY
I: 2019-08-09 15:47:23.335 NXDN, Begin TX: src=3023284 rpt=302328401 dst=28299 slot=2 cc=1 metadata=VE3NY
I: 2019-08-09 15:47:23.335 NXDN, (3023284, 28299) -> (570, 28299)
M: 2019-08-09 15:47:23.335 NXDN, received RF header from VE3NY to TG 28299
M: 2019-08-09 15:47:25.350 NXDN, TX state = OFF
M: 2019-08-09 15:47:25.350 NXDN, received RF end of transmission, 2.1 seconds, BER: 1.4%


Re: DV3000 Use

EA4GAX - Sergio
 
Edited

Hi Steve, I have it as you say, but I don't know if Ambe 3000 is acting, how do I know if it's active?
I see on console this message:

under certain conditions; see the file ``LICENSE'' for details. I: 2019-08-09 15:09:45.288 Subscriber IDs loaded: 0 I: 2019-08-09 15:09:45.288 Default extended metadata <my id> I: 2019-08-09 15:09:45.288 Connecting to emulator on host IP:port I: 2019-08-09 15:09:45.328 Using hardware AMBE vocoder

I think yes to be connet


Re: DV3000 Use

Steve N4IRS
 

Tom,
It depends on how you have the DV3000 connected. If directly connected and NOT using AMBEserver:

[DV3000]
; address = 127.0.0.1                  ; IP address of AMBEServer
; rxPort = 2460                        ; Port of AMBEServer
address = /dev/ttyUSB0                 ; Device of DV3000U on this machine
baud = 460800                          ; Baud rate of the dongle (230400 or 460800)
serial = true                          ; Use serial=true for direct connect or serial=false for AMBEServer


If directly connected and using AMBEserver

[DV3000]
address = 127.0.0.1                  ; IP address of AMBEServer
rxPort = 2460                        ; Port of AMBEServer
; address = /dev/ttyUSB0             ; Device of DV3000U on this machine
; baud = 460800                      ; Baud rate of the dongle (230400 or 460800)
serial = false                       ; Use serial=true for direct connect or serial=false for AMBEServer



On 8/9/2019 12:58 PM, Tom Corcoran wrote:
Steve(s),

tnx for info. very helpful in understanding how bits fit together. Does this mean that for dstar.ini, I need to "uncomment" first 2 lines?

[DV3000]
; address = 127.0.0.1                  ; IP address of AMBEServer
; rxPort = 2460                            ; Port of AMBEServer


--
Tom VE3NY

5181 - 5200 of 9891