YSFReflector, HBlink or HB_confbridge, and mmdvm_bridge be on same linux box


dstrobbe@...
 

ysf reflector , hblink  and mmdvm  on same linux VM
same ip   10.1.0.117
YSFreflector   registered SMS in registry


I am having problems with MMDVM_bridge setting up dmr to ysf .
mmdvm_bridge out put.
2018-12-23 11:31:30.044 General Parameters
I: 2018-12-23 11:31:30.044     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.044     Id: 1112822
I: 2018-12-23 11:31:30.044     Duplex: no
I: 2018-12-23 11:31:30.044     Timeout: 180s
I: 2018-12-23 11:31:30.044     D-Star: disabled
I: 2018-12-23 11:31:30.044     DMR: enabled
I: 2018-12-23 11:31:30.044     YSF: enabled
I: 2018-12-23 11:31:30.044     P25: disabled
I: 2018-12-23 11:31:30.044     NXDN: disabled
I: 2018-12-23 11:31:30.044 Modem Parameters
I: 2018-12-23 11:31:30.044     Port: /dev/null
I: 2018-12-23 11:31:30.044     RX Invert: no
I: 2018-12-23 11:31:30.044     TX Invert: no
I: 2018-12-23 11:31:30.044     PTT Invert: no
I: 2018-12-23 11:31:30.044     TX Delay: 100ms
I: 2018-12-23 11:31:30.045     RX Offset: 0Hz
I: 2018-12-23 11:31:30.045     TX Offset: 0Hz
I: 2018-12-23 11:31:30.045     RX DC Offset: 0
I: 2018-12-23 11:31:30.045     TX DC Offset: 0
I: 2018-12-23 11:31:30.045     RF Level: 100.0%
I: 2018-12-23 11:31:30.045     DMR Delay: 0 (0.0ms)
I: 2018-12-23 11:31:30.045     RX Level: 50.0%
I: 2018-12-23 11:31:30.045     CW Id TX Level: 50.0%
I: 2018-12-23 11:31:30.045     D-Star TX Level: 50.0%
I: 2018-12-23 11:31:30.045     DMR TX Level: 50.0%
I: 2018-12-23 11:31:30.045     YSF TX Level: 50.0%
I: 2018-12-23 11:31:30.045     P25 TX Level: 50.0%
I: 2018-12-23 11:31:30.045     NXDN TX Level: 50.0%
I: 2018-12-23 11:31:30.045     RX Frequency: 222340000Hz (222340000Hz)
I: 2018-12-23 11:31:30.045     TX Frequency: 224940000Hz (224940000Hz)
M: 2018-12-23 11:31:30.045 Opening the MMDVM
I: 2018-12-23 11:31:30.045 Display Parameters
I: 2018-12-23 11:31:30.045     Type: 
I: 2018-12-23 11:31:30.045 DMR Network Parameters
I: 2018-12-23 11:31:30.046     Address: 10.0.117
I: 2018-12-23 11:31:30.046     Port: 62031
I: 2018-12-23 11:31:30.046     Local: 62032
I: 2018-12-23 11:31:30.046     Jitter: 360ms
I: 2018-12-23 11:31:30.046     Slot 1: enabled
I: 2018-12-23 11:31:30.046     Slot 2: enabled
I: 2018-12-23 11:31:30.046     Mode Hang: 3s
I: 2018-12-23 11:31:30.046 Info Parameters
I: 2018-12-23 11:31:30.046     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.046     RX Frequency: 222340000Hz
I: 2018-12-23 11:31:30.046     TX Frequency: 224940000Hz
I: 2018-12-23 11:31:30.046     Power: 1W
I: 2018-12-23 11:31:30.046     Latitude: 41.733299deg N
I: 2018-12-23 11:31:30.046     Longitude: -50.399899deg E
I: 2018-12-23 11:31:30.046     Height: 0m
I: 2018-12-23 11:31:30.046     Location: "Iceberg, North Atlantic"
I: 2018-12-23 11:31:30.046     Description: "MMDVM_Bridge"
I: 2018-12-23 11:31:30.046     URL: "https://groups.io/g/DVSwitch"
M: 2018-12-23 11:31:30.046 DMR, Opening DMR Network
I: 2018-12-23 11:31:30.046 System Fusion Network Parameters
I: 2018-12-23 11:31:30.047     Local Address: 0
I: 2018-12-23 11:31:30.047     Local Port: 3200
I: 2018-12-23 11:31:30.047     Gateway Address: 47.206.21.33
I: 2018-12-23 11:31:30.047     Gateway Port: 42000
I: 2018-12-23 11:31:30.047     Mode Hang: 3s
M: 2018-12-23 11:31:30.047 Opening YSF network connection
I: 2018-12-23 11:31:30.047 RSSI
I: 2018-12-23 11:31:30.047     Mapping File: RSSI.dat
W: 2018-12-23 11:31:30.047 Cannot open the RSSI data file - RSSI.dat
I: 2018-12-23 11:31:30.047 DMR Id Lookups
I: 2018-12-23 11:31:30.047     File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-23 11:31:30.047     Reload: 24 hours
I: 2018-12-23 11:31:30.165 Loaded 119347 Ids to the DMR callsign lookup table
I: 2018-12-23 11:31:30.165 DMR RF Parameters
I: 2018-12-23 11:31:30.165     Id: 1112822
I: 2018-12-23 11:31:30.165     Color Code: 1
I: 2018-12-23 11:31:30.165     Self Only: no
I: 2018-12-23 11:31:30.165     Embedded LC Only: yes
I: 2018-12-23 11:31:30.165     Dump Talker Alias Data: no
I: 2018-12-23 11:31:30.165     Prefixes: 0
I: 2018-12-23 11:31:30.165     Call Hang: 3s
I: 2018-12-23 11:31:30.165     TX Hang: 3s
I: 2018-12-23 11:31:30.165     Mode Hang: 10s
M: 2018-12-23 11:31:30.165 DMR, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] TXPort -> 31100
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] RXPort -> 31103
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] Slot -> 2
M: 2018-12-23 11:31:30.166 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2018-12-23 11:31:30.166 YSF RF Parameters
I: 2018-12-23 11:31:30.166     Low Deviation: no
I: 2018-12-23 11:31:30.166     Remote Gateway: no
I: 2018-12-23 11:31:30.166     Self Only: no
I: 2018-12-23 11:31:30.166     DSQ: no
I: 2018-12-23 11:31:30.166     Mode Hang: 10s
M: 2018-12-23 11:31:30.166 YSF, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] TXPort -> 31103
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] RXPort -> 31100
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] FallbackID -> 1234567
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] ExportTG -> 1234
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Slot -> 2
M: 2018-12-23 11:31:30.166 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100.  Result = 1
M: 2018-12-23 11:31:30.167 MMDVM_Bridge-20180423 is running
I: 2018-12-23 11:31:30.167 Started the DMR Id lookup reload thread
E: 2018-12-23 11:32:40.171 DMR, Connection to the master has timed out, retrying connection
M: 2018-12-23 11:32:40.171 DMR, Closing DMR Network
M: 2018-12-23 11:32:40.171 DMR, Opening DMR Network
^CM: 2018-12-23 11:33:46.737 Closing the MMDVM
The DMR network keeps connecting and timing out   
do not see YSF connection. 


Thanks

Steven Strobbe D.O.
KJ4FPA


Steve N4IRS
 

Steve,
Do you see a login attempt on hblink?
 Are you sure hblink is listening on 62031?

netstat -unap will show you what program is listening on what UDP port
But, be aware that the program listening to the port is python NOT hblink.py

Here is an example:

root@openbridge:/home/szingman# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:62031           0.0.0.0:*                           7356/python        
udp        0      0 0.0.0.0:62035           0.0.0.0:*                           7356/python        
udp        0      0 0.0.0.0:54001           0.0.0.0:*                           7356/python        
udp        0      0 0.0.0.0:54002           0.0.0.0:*                           7356/python        

Python is listening to UDP port 62031. OK, but which python program?
I have bolded the UDP port number and the PID.
Now let's see what is running:

root@openbridge:/home/szingman# ps ax | grep python
 7356 ?        Ss    34:17 /usr/bin/python /opt/OpenBridge/hb_confbridge.py
 8976 ?        Ss     7:41 /usr/bin/python /opt/hbmonitor/web_tables.py
31311 pts/0    S+     0:00 grep python
root@openbridge:/home/szingman#

OK, PID 7356 in my case is running  hb_confbridge.py so hb_confbridge.py is listening on UDP port 62031

Hope this helps,
Steve N4IRS


On 12/23/18 7:43 AM, dstrobbe@... wrote:
ysf reflector , hblink  and mmdvm  on same linux VM
same ip   10.1.0.117
YSFreflector   registered SMS in registry


I am having problems with MMDVM_bridge setting up dmr to ysf .
mmdvm_bridge out put.
2018-12-23 11:31:30.044 General Parameters
I: 2018-12-23 11:31:30.044     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.044     Id: 1112822
I: 2018-12-23 11:31:30.044     Duplex: no
I: 2018-12-23 11:31:30.044     Timeout: 180s
I: 2018-12-23 11:31:30.044     D-Star: disabled
I: 2018-12-23 11:31:30.044     DMR: enabled
I: 2018-12-23 11:31:30.044     YSF: enabled
I: 2018-12-23 11:31:30.044     P25: disabled
I: 2018-12-23 11:31:30.044     NXDN: disabled
I: 2018-12-23 11:31:30.044 Modem Parameters
I: 2018-12-23 11:31:30.044     Port: /dev/null
I: 2018-12-23 11:31:30.044     RX Invert: no
I: 2018-12-23 11:31:30.044     TX Invert: no
I: 2018-12-23 11:31:30.044     PTT Invert: no
I: 2018-12-23 11:31:30.044     TX Delay: 100ms
I: 2018-12-23 11:31:30.045     RX Offset: 0Hz
I: 2018-12-23 11:31:30.045     TX Offset: 0Hz
I: 2018-12-23 11:31:30.045     RX DC Offset: 0
I: 2018-12-23 11:31:30.045     TX DC Offset: 0
I: 2018-12-23 11:31:30.045     RF Level: 100.0%
I: 2018-12-23 11:31:30.045     DMR Delay: 0 (0.0ms)
I: 2018-12-23 11:31:30.045     RX Level: 50.0%
I: 2018-12-23 11:31:30.045     CW Id TX Level: 50.0%
I: 2018-12-23 11:31:30.045     D-Star TX Level: 50.0%
I: 2018-12-23 11:31:30.045     DMR TX Level: 50.0%
I: 2018-12-23 11:31:30.045     YSF TX Level: 50.0%
I: 2018-12-23 11:31:30.045     P25 TX Level: 50.0%
I: 2018-12-23 11:31:30.045     NXDN TX Level: 50.0%
I: 2018-12-23 11:31:30.045     RX Frequency: 222340000Hz (222340000Hz)
I: 2018-12-23 11:31:30.045     TX Frequency: 224940000Hz (224940000Hz)
M: 2018-12-23 11:31:30.045 Opening the MMDVM
I: 2018-12-23 11:31:30.045 Display Parameters
I: 2018-12-23 11:31:30.045     Type: 
I: 2018-12-23 11:31:30.045 DMR Network Parameters
I: 2018-12-23 11:31:30.046     Address: 10.0.117
I: 2018-12-23 11:31:30.046     Port: 62031
I: 2018-12-23 11:31:30.046     Local: 62032
I: 2018-12-23 11:31:30.046     Jitter: 360ms
I: 2018-12-23 11:31:30.046     Slot 1: enabled
I: 2018-12-23 11:31:30.046     Slot 2: enabled
I: 2018-12-23 11:31:30.046     Mode Hang: 3s
I: 2018-12-23 11:31:30.046 Info Parameters
I: 2018-12-23 11:31:30.046     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.046     RX Frequency: 222340000Hz
I: 2018-12-23 11:31:30.046     TX Frequency: 224940000Hz
I: 2018-12-23 11:31:30.046     Power: 1W
I: 2018-12-23 11:31:30.046     Latitude: 41.733299deg N
I: 2018-12-23 11:31:30.046     Longitude: -50.399899deg E
I: 2018-12-23 11:31:30.046     Height: 0m
I: 2018-12-23 11:31:30.046     Location: "Iceberg, North Atlantic"
I: 2018-12-23 11:31:30.046     Description: "MMDVM_Bridge"
I: 2018-12-23 11:31:30.046     URL: "https://groups.io/g/DVSwitch"
M: 2018-12-23 11:31:30.046 DMR, Opening DMR Network
I: 2018-12-23 11:31:30.046 System Fusion Network Parameters
I: 2018-12-23 11:31:30.047     Local Address: 0
I: 2018-12-23 11:31:30.047     Local Port: 3200
I: 2018-12-23 11:31:30.047     Gateway Address: 47.206.21.33
I: 2018-12-23 11:31:30.047     Gateway Port: 42000
I: 2018-12-23 11:31:30.047     Mode Hang: 3s
M: 2018-12-23 11:31:30.047 Opening YSF network connection
I: 2018-12-23 11:31:30.047 RSSI
I: 2018-12-23 11:31:30.047     Mapping File: RSSI.dat
W: 2018-12-23 11:31:30.047 Cannot open the RSSI data file - RSSI.dat
I: 2018-12-23 11:31:30.047 DMR Id Lookups
I: 2018-12-23 11:31:30.047     File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-23 11:31:30.047     Reload: 24 hours
I: 2018-12-23 11:31:30.165 Loaded 119347 Ids to the DMR callsign lookup table
I: 2018-12-23 11:31:30.165 DMR RF Parameters
I: 2018-12-23 11:31:30.165     Id: 1112822
I: 2018-12-23 11:31:30.165     Color Code: 1
I: 2018-12-23 11:31:30.165     Self Only: no
I: 2018-12-23 11:31:30.165     Embedded LC Only: yes
I: 2018-12-23 11:31:30.165     Dump Talker Alias Data: no
I: 2018-12-23 11:31:30.165     Prefixes: 0
I: 2018-12-23 11:31:30.165     Call Hang: 3s
I: 2018-12-23 11:31:30.165     TX Hang: 3s
I: 2018-12-23 11:31:30.165     Mode Hang: 10s
M: 2018-12-23 11:31:30.165 DMR, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] TXPort -> 31100
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] RXPort -> 31103
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] Slot -> 2
M: 2018-12-23 11:31:30.166 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2018-12-23 11:31:30.166 YSF RF Parameters
I: 2018-12-23 11:31:30.166     Low Deviation: no
I: 2018-12-23 11:31:30.166     Remote Gateway: no
I: 2018-12-23 11:31:30.166     Self Only: no
I: 2018-12-23 11:31:30.166     DSQ: no
I: 2018-12-23 11:31:30.166     Mode Hang: 10s
M: 2018-12-23 11:31:30.166 YSF, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] TXPort -> 31103
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] RXPort -> 31100
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] FallbackID -> 1234567
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] ExportTG -> 1234
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Slot -> 2
M: 2018-12-23 11:31:30.166 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100.  Result = 1
M: 2018-12-23 11:31:30.167 MMDVM_Bridge-20180423 is running
I: 2018-12-23 11:31:30.167 Started the DMR Id lookup reload thread
E: 2018-12-23 11:32:40.171 DMR, Connection to the master has timed out, retrying connection
M: 2018-12-23 11:32:40.171 DMR, Closing DMR Network
M: 2018-12-23 11:32:40.171 DMR, Opening DMR Network
^CM: 2018-12-23 11:33:46.737 Closing the MMDVM
The DMR network keeps connecting and timing out   
do not see YSF connection. 


Thanks

Steven Strobbe D.O.
KJ4FPA


dstrobbe@...
 


STEVE
it appears it is listening

root@debian:/var/lib/mmdvm# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1048/minissdpd      
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 0.0.0.0:56720           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           1452/qemu-arm-stati 
udp        0      0 0.0.0.0:42003           0.0.0.0:*                           536/./YSFReflector  
udp        0      0 0.0.0.0:42010           0.0.0.0:*                           1458/P25Gateway     
udp        0      0 0.0.0.0:42011           0.0.0.0:*                           1457/P25Parrot      
udp        0      0 0.0.0.0:42020           0.0.0.0:*                           1458/P25Gateway     
udp        0      0 0.0.0.0:40502           0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 10.1.0.117:62031        0.0.0.0:*                           21442/python        
udp        0      0 0.0.0.0:62032           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:631             0.0.0.0:*                           6271/cups-browsed   
udp        0      0 0.0.0.0:3200            0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           531/avahi-daemon: r 
udp        0      0 0.0.0.0:60696           0.0.0.0:*                           531/avahi-daemon: r 
udp6       0      0 :::33604                :::*                                531/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                531/avahi-daemon: r 
root@debian:/var/lib/mmdvm# ps ax | grep python
21442 pts/1    S+     0:05 python ./hblink.py
30667 pts/5    S+     0:00 grep python
 


Steve N4IRS
 

What does the the hblink log show?

On 12/23/18 10:17 AM, dstrobbe@... wrote:

STEVE
it appears it is listening

root@debian:/var/lib/mmdvm# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1048/minissdpd      
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:31100           0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:31103           0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 0.0.0.0:56720           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:2470            0.0.0.0:*                           1452/qemu-arm-stati 
udp        0      0 0.0.0.0:42003           0.0.0.0:*                           536/./YSFReflector  
udp        0      0 0.0.0.0:42010           0.0.0.0:*                           1458/P25Gateway     
udp        0      0 0.0.0.0:42011           0.0.0.0:*                           1457/P25Parrot      
udp        0      0 0.0.0.0:42020           0.0.0.0:*                           1458/P25Gateway     
udp        0      0 0.0.0.0:40502           0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 10.1.0.117:62031        0.0.0.0:*                           21442/python        
udp        0      0 0.0.0.0:62032           0.0.0.0:*                           30509/./MMDVM_Bridg 
udp        0      0 0.0.0.0:631             0.0.0.0:*                           6271/cups-browsed   
udp        0      0 0.0.0.0:3200            0.0.0.0:*                           1453/MMDVM_Bridge   
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           531/avahi-daemon: r 
udp        0      0 0.0.0.0:60696           0.0.0.0:*                           531/avahi-daemon: r 
udp6       0      0 :::33604                :::*                                531/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                531/avahi-daemon: r 
root@debian:/var/lib/mmdvm# ps ax | grep python
21442 pts/1    S+     0:05 python ./hblink.py
30667 pts/5    S+     0:00 grep python
 


dstrobbe@...
 

Steve
I found my error in th ini file on a port for my ysf reflector    ie  should be 42003 not 42000

But now when i transmit from drm   i hear about 3-4 sec of audio from fusion   then stops but carrier still continues...    

Audio cuts out.   will not return for can not be heard agian for a serveral transmits ..   ?  cut off timer????
 no audio will be heard from ysf transmit to dmr

MMDVM-bridge output  on transmit from dmr   intermitant audio heard

I: 2018-12-23 23:20:29.494 YSF, Begin TX: src=1112822 rpt=0 dst=31664 slot=2 cc=0 metadata=KJ4FPA
 
I: 2018-12-23 23:20:29.557 YSF, Narrow transmit (72 bit)
M: 2018-12-23 23:20:34.656 DMR Slot 2, received network end of voice transmission, 5.5 seconds, 4% packet loss, BER: 0.0%
M: 2018-12-23 23:20:34.665 YSF, TX state = OFF
M: 2018-12-23 23:20:56.316 DMR Slot 2, received network voice header from KJ4FPA to TG 31664
M: 2018-12-23 23:20:56.316 YSF, TX state = ON
I: 2018-12-23 23:20:56.316 YSF, Begin TX: src=1112822 rpt=0 dst=31664 slot=2 cc=0 metadata=KJ4FPA
 
I: 2018-12-23 23:20:56.376 YSF, Narrow transmit (72 bit)
M: 2018-12-23 23:21:01.118 DMR Slot 2, received network end of voice transmission, 5.2 seconds, 4% packet loss, BER: 0.1%
M: 2018-12-23 23:21:01.118 YSF, TX state = OFF

mmdvm_bridge output from  ysf transmit  to dmr      no audio heard. 
M: 2018-12-23 23:28:00.722 YSF, received network data from KJ4FPA     to *****F5ACr at KJ4FPA    
I: 2018-12-23 23:28:00.722 YSF, Lookup call KJ4FPA returned id 1112822 -> 1112822
M: 2018-12-23 23:28:00.727 DMR, TX state = ON
I: 2018-12-23 23:28:00.727 DMR, Begin TX: src=1112822 rpt=0 dst=1234 slot=2 cc=0 metadata=KJ4FPA
D: 2018-12-23 23:28:01.427 V/D Mode 2 Data, DT1
D: 2018-12-23 23:28:01.427 0000:  19 22 62 5F 29 52 38 51 56 34                      *."b_)R8QV4*
D: 2018-12-23 23:28:01.520 V/D Mode 2 Data, DT2
D: 2018-12-23 23:28:01.520 0000:  57 6E 47 7F 6C 20 6B 20 03 2F                      *WnG.l k ./*
D: 2018-12-23 23:28:02.226 V/D Mode 2 Data, DT1
D: 2018-12-23 23:28:02.226 0000:  19 22 62 5F 29 52 38 51 56 34                      *."b_)R8QV4*
D: 2018-12-23 23:28:02.320 V/D Mode 2 Data, DT2
D: 2018-12-23 23:28:02.320 0000:  57 6E 47 7F 6C 20 6B 20 03 2F                      *WnG.l k ./*
M: 2018-12-23 23:28:02.928 YSF, received network end of transmission, 2.3 seconds, 0% packet loss, BER: 0.0%
M: 2018-12-23 23:28:02.933 DMR, TX state = OFF

steve   much harder than i thought

thanks
 


dstrobbe@...
 

Steve:

I hear only about 3 seconds of clear fusion  audio on my fusion radio  then audio stops i do see  a digital signal still being recieved on fusion radio and if i listen to it on fm side will hear the digital transmittion .        ysf to dmr works fine.  will hear everything.

on the mmdvm_bridge console i see  data being sent on ysf to dmr with good audio  ie 
M: 2018-12-23 23:28:00.722 YSF, received network data from KJ4FPA     to *****F5ACr at KJ4FPA    
I: 2018-12-23 23:28:00.722 YSF, Lookup call KJ4FPA returned id 1112822 -> 1112822
M: 2018-12-23 23:28:00.727 DMR, TX state = ON
I: 2018-12-23 23:28:00.727 DMR, Begin TX: src=1112822 rpt=0 dst=1234 slot=2 cc=0 metadata=KJ4FPA
D: 2018-12-23 23:28:01.427 V/D Mode 2 Data, DT1
D: 2018-12-23 23:28:01.427 0000:  19 22 62 5F 29 52 38 51 56 34                      *."b_)R8QV4*
D: 2018-12-23 23:28:01.520 V/D Mode 2 Data, DT2
D: 2018-12-23 23:28:01.520 0000:  57 6E 47 7F 6C 20 6B 20 03 2F                      *WnG.l k ./*
D: 2018-12-23 23:28:02.226 V/D Mode 2 Data, DT1
D: 2018-12-23 23:28:02.226 0000:  19 22 62 5F 29 52 38 51 56 34                      *."b_)R8QV4*
D: 2018-12-23 23:28:02.320 V/D Mode 2 Data, DT2
D: 2018-12-23 23:28:02.320 0000:  57 6E 47 7F 6C 20 6B 20 03 2F                      *WnG.l k ./*
M: 2018-12-23 23:28:02.928 YSF, received network end of transmission, 2.3 seconds, 0% packet loss, BER: 0.0%
M: 2018-12-23 23:28:02.933 DMR, TX state = OFF


dmr to ysf  log shows   2-3 seconds of good audio       should i see data like on the ysf to drm transmition
I: 2018-12-23 23:20:56.376 YSF, Narrow transmit (72 bit)
M: 2018-12-23 23:21:01.118 DMR Slot 2, received network end of voice transmission, 5.2 seconds, 4% packet loss, BER: 0.1%
M: 2018-12-23 23:21:01.118 YSF, TX state = OFF


andrew delgado
 

I have similar issues , it is fine when im using ft2dr,  YSF to DMR is fine but when DMR to YSF and im using FT2DR it is also fine and i noticed its switching from VW to DN. but if im using my ftm400 and ftm100 i have similar issues the 1st sec will have audio then it drop no audio will receive.

On Thursday, 27 December 2018, 12:06:52 AM GMT+8, <dstrobbe@...> wrote:


Steve:

I hear only about 3 seconds of clear fusion  audio on my fusion radio  then audio stops i do see  a digital signal still being recieved on fusion radio and if i listen to it on fm side will hear the digital transmittion .        ysf to dmr works fine.  will hear everything.

on the mmdvm_bridge console i see  data being sent on ysf to dmr with good audio  ie 
M: 2018-12-23 23:28:00.722 YSF, received network data from KJ4FPA     to *****F5ACr at KJ4FPA    
I: 2018-12-23 23:28:00.722 YSF, Lookup call KJ4FPA returned id 1112822 -> 1112822
M: 2018-12-23 23:28:00.727 DMR, TX state = ON
I: 2018-12-23 23:28:00.727 DMR, Begin TX: src=1112822 rpt=0 dst=1234 slot=2 cc=0 metadata=KJ4FPA
D: 2018-12-23 23:28:01.427 V/D Mode 2 Data, DT1
D: 2018-12-23 23:28:01.427 0000:  19 22 62 5F 29 52 38 51 56 34                      *."b_)R8QV4*
D: 2018-12-23 23:28:01.520 V/D Mode 2 Data, DT2
D: 2018-12-23 23:28:01.520 0000:  57 6E 47 7F 6C 20 6B 20 03 2F                      *WnG.l k ./*
D: 2018-12-23 23:28:02.226 V/D Mode 2 Data, DT1
D: 2018-12-23 23:28:02.226 0000:  19 22 62 5F 29 52 38 51 56 34                      *."b_)R8QV4*
D: 2018-12-23 23:28:02.320 V/D Mode 2 Data, DT2
D: 2018-12-23 23:28:02.320 0000:  57 6E 47 7F 6C 20 6B 20 03 2F                      *WnG.l k ./*
M: 2018-12-23 23:28:02.928 YSF, received network end of transmission, 2.3 seconds, 0% packet loss, BER: 0.0%
M: 2018-12-23 23:28:02.933 DMR, TX state = OFF


dmr to ysf  log shows   2-3 seconds of good audio       should i see data like on the ysf to drm transmition
I: 2018-12-23 23:20:56.376 YSF, Narrow transmit (72 bit)
M: 2018-12-23 23:21:01.118 DMR Slot 2, received network end of voice transmission, 5.2 seconds, 4% packet loss, BER: 0.1%
M: 2018-12-23 23:21:01.118 YSF, TX state = OFF


dstrobbe@...
 

andrew:
I am using ftm-100D    
DID you find a fix or it just does not work?
I spent many hours trying different config. but always came out with same result. 


steve strobbe.


andrew delgado
 

Hi Steve,

No i still have the issue. it is fine when im using ft2dr but not with ftm100 and frm400


Last update that i read was theres a bug that they will send a patch or fix. waiting for that.

73!
Andrew


On Friday, 28 December 2018, 4:49:10 AM GMT+8, <dstrobbe@...> wrote:


andrew:
I am using ftm-100D    
DID you find a fix or it just does not work?
I spent many hours trying different config. but always came out with same result. 


steve strobbe.


Steve N4IRS
 

I do not have a time frame yet.

On 12/29/18 8:00 AM, andrew delgado via Groups.Io wrote:
Hi Steve,

No i still have the issue. it is fine when im using ft2dr but not with ftm100 and frm400


Last update that i read was theres a bug that they will send a patch or fix. waiting for that.

73!
Andrew


On Friday, 28 December 2018, 4:49:10 AM GMT+8, <dstrobbe@...> wrote:


andrew:
I am using ftm-100D    
DID you find a fix or it just does not work?
I spent many hours trying different config. but always came out with same result. 


steve strobbe.